search

danth / stylix

System-wide colorscheming and typography for NixOS
https://stylix.danth.me/
MIT License
902 stars 105 forks source link

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

Open Fireb3rt opened 2 weeks ago

Fireb3rt commented 2 weeks ago

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 commented 2 weeks ago

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.