Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

kde: home-manager failing to set Plasma wallpaper, not connected to D-Bus server #422

Closed
foxf4ce opened this issue Jun 11, 2024 · 3 comments · Fixed by #708
Closed

kde: home-manager failing to set Plasma wallpaper, not connected to D-Bus server #422

foxf4ce opened this issue Jun 11, 2024 · 3 comments · Fixed by #708
Labels
bug Something isn't working properly

Comments

@foxf4ce
Copy link

foxf4ce commented Jun 11, 2024

I'm using NixOS 24.05 and Plasma 6 and I'm running into an error which causes my home-manager service to fail when starting up my computer. Rebuilding in Plasma works fine. This issue seems almost identical to #340, but I'm getting a different error ("Not connected to D-Bus server" rather than "The name is not activatable"). So I'm not sure if this is a different issue or not.

Here is the log of systemctl status home-manager-avat.service.

× home-manager-avat.service - Home Manager environment for avat
     Loaded: loaded (/etc/systemd/system/home-manager-avat.service; enabled; preset: enabled)
     Active: failed (Result: exit-code) since Tue 2024-06-11 15:15:44 EDT; 1min 19s ago
    Process: 733 ExecStart=/nix/store/7i0d80cp7l2f3kzphp2pgl75f8k9bqal-hm-setup-env /nix/store/ncsxin9fydixgc>
   Main PID: 733 (code=exited, status=255/EXCEPTION)
         IP: 0B in, 0B out
        CPU: 762ms

Jun 11 15:15:43 baron hm-activate-avat[733]: Creating home file links in /home/avat
Jun 11 15:15:44 baron hm-activate-avat[733]: Activating onFilesChange
Jun 11 15:15:44 baron hm-activate-avat[733]: Activating reloadSystemd
Jun 11 15:15:44 baron hm-activate-avat[733]: User systemd daemon not running. Skipping reload.
Jun 11 15:15:44 baron hm-activate-avat[733]: Activating stylixLookAndFeel
Jun 11 15:15:44 baron hm-activate-avat[1175]: An error occurred while attempting to set the Plasma wallpaper:
Jun 11 15:15:44 baron hm-activate-avat[1175]: Not connected to D-Bus server
Jun 11 15:15:44 baron systemd[1]: home-manager-avat.service: Main process exited, code=exited, status=255/EXC>
Jun 11 15:15:44 baron systemd[1]: home-manager-avat.service: Failed with result 'exit-code'.
Jun 11 15:15:44 baron systemd[1]: Failed to start Home Manager environment for avat.

@danth
Copy link
Owner

danth commented Jun 12, 2024

I think this is the same problem: it's just starting so early that the D-Bus server isn't running at all, whereas in the issue you linked, D-Bus is running but KDE isn't connected on the other end.

@trueNAHO trueNAHO added the bug Something isn't working properly label Jun 12, 2024
@hasrthur
Copy link

I also have this issue so had to disable kde target. The interesting thing is that it worked the first time I logged into to freshly installed kde/plasma environment. It's only after I started setting things up manually and with plasma-manager help did I notice that home manager could not start.

I am using plasma 6. Though did this stylix target ever work then? Or was this problem introduced with 6 version of plasma only?

@danth
Copy link
Owner

danth commented Sep 2, 2024

The Stylix target is not fully adapted for Plasma 6 yet; however, this issue already existed with Plasma 5 too.

trueNAHO pushed a commit that referenced this issue Jan 3, 2025
…708)

Replace the systemd unit with a more robust AutostartScript for theme
application during Plasma startup, ensuring D-Bus and session
availability without breaking Home Manager activation.

Closes: #340
Closes: #350
Closes: #422
Link: #708

Co-authored-by: rkuklik <[email protected]>
Tested-by: lordkekz <[email protected]>
Tested-by: rkuklik <[email protected]>
Reviewed-by: NAHO <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working properly
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants