You are not logged in.
Hi, after some update a couple of weeks ago (I don't remember exactly), slim fails to start after boot. I use systemd and just had enabled the slim.service file that is included in the package. After boot, I can login on the tty and then restart the slim.service, and everything works.
In the slim.log file it says:
Fatal server error:
no screens found
[...]
Giving up.
slim: unable to connect to X server
/usr/bin/xauth: file /var/run/slim.auth does not existIt seems like slim is started before X, since everything works when I restart the service manually. What is causing this problem and how can I solve it?
Best regards and thanks,
Jan Oliver
Offline
How does your slim.servcie look like? Mine;
/usr/lib/systemd/system/slim.service
[Unit]
Description=SLiM Simple Login Manager
After=systemd-user-sessions.service
[Service]
ExecStart=/usr/bin/slim -nodaemon
[Install]
WantedBy=graphical.targetDo you still use rc.conf for anything? For example slim? What does journactl | grep slim say? And systemd-analyze?
Offline
journalctl is currently not working, I have to dig into that as well.
My slim.service looks exactly the same.
I don't really know how to draw information from systemd-analyze... Is it not just for the purpose of benchmarking/timing the start of services or so?
Offline
I think systemd-analyze would give a nice overview of started services as it lists them.
Offline
Oh, sorry I meant systemd-analyze blame , of course. (I'm on my netbook with ol' rc.conf)
Offline
oliarch ~ sudo systemd-analyze blame
2460ms net-auto-wireless.service
243ms rsyslog.service
239ms sshd.service
183ms console-kit-log-system-start.service
136ms systemd-logind.service
124ms console-kit-daemon.service
119ms systemd-udev-trigger.service
99ms systemd-sysctl.service
82ms systemd-readahead-replay.service
80ms systemd-vconsole-setup.service
63ms systemd-user-sessions.service
62ms systemd-remount-fs.service
58ms systemd-readahead-collect.service
55ms sys-kernel-debug.mount
43ms dev-sda2.swap
43ms dev-mqueue.mount
42ms dev-hugepages.mount
26ms systemd-tmpfiles-setup.service
20ms srv.mount
13ms tmp.mount
12ms systemd-udev.service
10ms boot.mount
9ms home.mountoliarch ~ sudo journalctl --no-pager -a | grep slim
Jun 24 14:25:01 oliarch systemd[1]: slim.service: main process exited, code=exited, status=1
Jun 24 14:25:01 oliarch systemd[1]: Unit slim.service entered failed state.Offline
I'm no expert on systemd, but it looks ok to me. Is your slim updated? How do you start your session manager? It might be a question of console-kit since slim from version 1.3.x has new built in support for console-kit and it's no longer necessary to add console-kit to .xinitrc. Just a thought ...
Offline
Something like
systemctl status slim.service will give you more info on your problem i think
if you run it as root it also gives you log messages
Last edited by 89c51 (2012-06-24 11:06:02)
Offline
I'm no expert on systemd, but it looks ok to me. Is your slim updated? How do you start your session manager? It might be a question of console-kit since slim from version 1.3.x has new built in support for console-kit and it's no longer necessary to add console-kit to .xinitrc. Just a thought ...
I am pretty sure I load it the right way;
login_cmd exec ck-launch-session dbus-launch /bin/bash -login ~/.xinitrc %sessionin .xinitrc I only use "exec i3"
systemctl status doesn't help. ![]()
Offline
I don't nthink this is necessary; ck-launch-session anymore. And note that systemd already started a console-kit servcice/session. As I said, slim version 1.3.x handels console-kit by itself. What does ck-list-session say? Before your manual start and after?
EDIT; From my slim.conf;
login_cmd exec /bin/bash -login ~/.xinitrc %session(You might try without dbus-launch as well, )
EDIT #2: ck-list-sessions
(My netbook is too small to type on)
Last edited by swanson (2012-06-24 11:42:35)
Offline