After Installing Systemd, Slim Fails To Load Desktop.

Slim freezes doing nothing. I had to use startx to start desktop. slim.service is enabled btw.

$ systemctl status slim

  1. #1 by Scott Ferguson on November 12th, 2013 - 9:39 pm

    Which Debian release?
    What DE?
    Any error log info?

    NOTE: slim is not a DM so *if* you are using xdm/gdm/kdm (but not Openbox) try:-
    $ DM=$(ls /etc/init.d/ | grep dm);su -c “service $DM start” (or “sudo service $DM start” if you have sudo installed) instead of startx

    Sorry don’t have access till this evening to the Wheezy systemd OpenBox laptop – but I “think” I just installed systemd and ran “systemctl enable slim.service” and everything just worked next boot. I may have modified ~/.xinitrc to allow for DM choices but I’ll have to check.

    Kind regards

  2. #2 by Scott Ferguson on November 13th, 2013 - 12:27 am

    $ su -c “grep ‘WW\|EE\|NI\|??’ /var/log/Xorg.0.log”

    or if you use sudo:-
    $ sudo grep ‘WW\|EE\|NI\|??’ /var/log/Xorg.0.log)

    Then I’d go through:-
    $ su -c “dpkg-reconfigure systemd slim $DM [etc]” (use sudo instead of su -c as appropriate)

    I’ll check my setup when I get back to the office and post here if I
    find anything relevant.

    Kind regards

  3. #3 by Ralf Mardorf on November 13th, 2013 - 3:18 am


    Why doesn’t it show that it is enabled?

    [rocketmouse@archlinux ~]$ systemctl status alice alice.service – Alice PPPoE
    Loaded: loaded (/usr/lib/systemd/system/alice.service; enabled)
    Active: active (exited) since Wed 2013-11-13 08:22:19 CET; 1h 32min ago
    Process: 334 ExecStart=/etc/rc.d/alice start (code=exited, status=0/SUCCESS)
    Main PID: 334 (code=exited, status=0/SUCCESS)
    CGroup: /system.slice/alice.service
    โ””โ”€486 /usr/sbin/pppd call provider

    [rocketmouse@archlinux ~]$ systemctl status NetworkManager NetworkManager.service – Network Manager
    Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; disabled)
    Active: inactive (dead)

  4. #4 by Scott Ferguson on November 13th, 2013 - 3:45 am

    That indicates a problem. Probably in X somewhere. (I’ll have to research that). Are you using nvidia and relying on /etc/X11/xorg.conf?

    My mistake [] means optional (in my occult shorthand)

    subsitute $DM for your display manager if you have one ($ ls /etc/init.d
    | grep dm)

    subsitute [etc] for any other packages involved in your display e.g. openbox xorg packages etc

    try just:-
    # dpkg-reconfigure systemd slim

    and see how that works, if it changes nothing try reconfiguring some of the other packages (could be the problem is xauth, alternatives or similar)

    do a:-
    $ dpkg –get-selections | more and look for likely packages to reconfigure.

    Kind regards

  5. #5 by Ralf Mardorf on November 13th, 2013 - 3:51 am

    Perhaps you should take a look at the service file.

    $ cat /etc/init.d/slim

    I’m using lightdm on another distro, that’s why the path does differ:

    $ cat /usr/lib/systemd/system/lightdm.service
    Description=Light Display Manager Documentation=man:lightdm(1)
    Conflicts=getty@tty1.service After=systemd-user-sessions.service getty@tty1.service plymouth-quit.service

    ExecStart=/usr/bin/lightdm Restart=always IgnoreSIGPIPE=no BusName=org.freedesktop.DisplayManager


  6. #6 by Scott Ferguson on November 13th, 2013 - 4:48 am

    256MB of RAM just to prove that new software gives new life to old hardware). No /etc/X11/xorg.conf video is the Savage chipset

    slim 1.3.4-2 i386
    systemd 44-11+deb7u4 i386
    openbox 3.5.0-7 i386

    scott@t22:~$ systemctl status slim Failed to get D-Bus connection: No connection to service manager.

    Hmmmm…. works fine though

    /etc/slim.conf (edited to remove unneeded info):-
    default_path /usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games default_xserver /usr/bin/X11/X
    xserver_arguments -nolisten tcp halt_cmd /sbin/shutdown -h now reboot_cmd /sbin/shutdown -r now console_cmd /usr/bin/xterm -C -fg white -bg black +sb -T
    “Console login” -e /bin/sh -c “/bin/cat /etc/; exec /bin/login”
    xauth_path /usr/bin/X11/xauth authfile /var/run/slim.auth login_cmd exec /bin/bash -login /etc/X11/Xsession %session sessions default,startxfce4,openbox,ion3,icewm,wmaker,blackbox,awesome screenshot_cmd scrot /root/slim.png welcome_msg Welcome to %host shutdown_msg The system is halting… reboot_msg The system is rebooting… current_theme debian-joy lockfile /var/run/slim.lock logfile /var/log/slim.log

    . /etc/X11/Xsession

    exec /usr/bin/X -nolisten tcp “$@”

    No ~/.xinitrc (removed it when I replaced blackbox it with minimal LXDE
    and Openbox)

    $ cat /etc/default/grub | grep -v “#” | more GRUB_DEFAULT=0
    GRUB_INIT_TUNE=”480 440 1″

    Let me know if there are any other conf files or information that might be useful.

    Kind regards

  7. #7 by Scott Ferguson on November 13th, 2013 - 4:54 am

    Maybe I’m just not thinking

    Oh wait… I keep confusing “maybe” with “definitely” :/

    You are correct, slim is a window manager. Revise that advice to “ensure you don’t have another window manager installed” (“$ ls /etc/init.d | grep dm” to check)


  8. #8 by Ralf Mardorf on November 13th, 2013 - 5:00 am

  9. #9 by Ralf Mardorf on November 13th, 2013 - 5:12 am

    What DE do you use? If it’s GNOME, you should care about GNOME keyring.

  10. #10 by Scott Ferguson on November 13th, 2013 - 5:42 am

    scott@t22:~$ systemctl status slim Failed to issue method call: Unit name slim is not valid. ?

    scott@t22:~$ systemctl status console-kit-log-system-start.service console-kit-log-system-start.service – Console System Startup Logging
    Loaded: loaded
    (/lib/systemd/system/console-kit-log-system-start.service; static)
    Active: active (exited) since Thu, 14 Nov 2013 00:38:02 +1100;
    10min ago
    Process: 699 ExecStart=/usr/sbin/ck-log-system-start
    (code=exited, status=0/SUCCESS)
    CGroup: name=systemd:/system/console-kit-log-system-start.service

    lightdm does (also) work with systemd – at least on this laptop using Wheezy/backports i386

    Just_Me should (maybe) also check to see if systemd-sysv is installed
    (*backup* first).

    I’m not sure why I was getting dbus errors earlier, could be the x2goserver (which has a habit of segfaulting occasionally).

    scott@t22:~$ systemctl list-units –type=target UNIT LOAD ACTIVE SUB JOB DESCRIPTION loaded active active Basic System loaded active active Encrypted Volumes loaded active active Login Prompts loaded active active Graphical Interface loaded active active Local File Systems (Pre) loaded active active Local File Systems loaded active active Multi-User loaded active active Remote File Systems (Pre) loaded active active Remote File Systems loaded active active Sockets loaded active active Sound Card loaded active active Swap loaded active active System Initialization loaded active active Syslog

    LOAD = Reflects whether the unit definition was properly loaded. ACTIVE = The high-level unit activation state, i.e. generalization of SUB. SUB = The low-level unit activation state, values depend on unit type. JOB = Pending job for the unit.

    14 units listed. Pass –all to see inactive units, too.

    scott@t22:~$ systemd-analyze blame
    15629ms fail2ban.service
    11370ms x2goserver.service
    9449ms slim.service
    8931ms NetworkManager.service
    7960ms console-kit-daemon.service
    7462ms bootlogs.service
    7379ms ssh.service
    4877ms systemd-logind.service
    4107ms acpi-fakekey.service
    3545ms keyboard-setup.service
    3257ms cron.service
    2638ms lvm2.service
    2399ms atd.service
    2234ms anacron.service
    2006ms hdparm.service
    1446ms polkitd.service
    1402ms udev.service
    1392ms acpi-support.service
    1374ms networking.service
    1312ms saned.service
    1195ms sys-kernel-security.mount
    1126ms rpcbind.service
    1119ms dev-mqueue.mount
    1056ms sys-kernel-debug.mount
    1055ms dev-hugepages.mount
    1030ms run-lock.mount
    1022ms run-user.mount
    997ms screen-cleanup.service
    996ms systemd-modules-load.service
    875ms kbd.service
    874ms console-setup.service
    867ms cups.service
    789ms systemd-tmpfiles-setup.service
    768ms alsa-utils.service
    565ms console-kit-log-system-start.service
    500ms nfs-common.service
    409ms udev-trigger.service
    322ms udisks.service
    313ms systemd-sysctl.service
    272ms systemd-user-sessions.service
    251ms motd.service
    238ms cryptsetup@sda5_crypt.service
    207ms systemd-remount-api-vfs.service
    171ms exim4.service
    159ms pppd-dns.service
    101ms boot.mount
    33ms remount-rootfs.service

    scott@t22:~$ cat /usr/lib/systemd/user/

  11. #11 by Scott Ferguson on November 13th, 2013 - 5:54 am

    It’s a minimal LXDE using Openbox on that laptop.

    Good point

    scott@t22:~$ dpkg –get-selections | grep gnome gir1.2-gnomebluetooth-1.0 install gnome-bluetooth install gnome-icon-theme install gnome-keyring install libgnome-bluetooth10 install libgnome-keyring-common install libgnome-keyring0:i386 install libpam-gnome-keyring install libsoup-gnome2.4-1:i386 install network-manager-gnome install policykit-1-gnome install

    Kind regards

  12. #12 by Curt on November 13th, 2013 - 7:09 am

    Or if you want to use neither one:

    grep …. /var/log/Xorg.0.log

    On my machine at least, it doesn’t require elevated privileges to read the Xorg log file.

    curty@einstein:~$ ls -l /var/log/Xorg.0.log
    -rw-r–r– 1 root root 44775 Nov 13 12:39 /var/log/Xorg.0.log

(will not be published)
Subscribe to comments feed