You are not logged in.
Hi All,
I googled through whole newbie corner and several other forums, almost memorized related archwiki articles.
I apologize for raising the topic again, but...
xfce4 does not start when invoked by slim through .xinitrc
The only error message in /var/log/slim.log is:
slim: open_session: Unable to open session: Message did not receive a reply (timeout by message bus)
However, startxfce4 perfectly invokes xfce4 when run from console.
What's more interesting:
$ ps ax | grep dbus-daemon
464 ? Ss 0:00 dbus-daemon --system
$ ck-list-sessions
$
Here're notable configuration lines:
$ cat /etc/rc.conf | grep ^DAEMONS
DAEMONS=(syslog-ng dbus network crond slim)
$ cat /etc/slim.conf | grep ^login_cmd
login_cmd exec /bin/bash -login ~/.xinitrc %session
$ cat .xinitrc
exec startxfce4
$ ls -la .xinitrc
-rwx-xr-x 1 diaword users 316 Jun 28 13:20 .xinitrc
$ cat /etc/group | grep dbus
dbus:x:81:diaword
Please, could you suggest where else should I have a look / what to read / what to try?
Thanks everyone in advance for your time.
W B R
Offline
Do you have the consolekit package installed? And why are you in the dbus group?
Post your /etc/inittab.
I have made a personal commitment not to reply in topics that start with a lowercase letter. Proper grammar and punctuation is a sign of respect, and if you do not show any, you will NOT receive any help (at least not from me).
Offline
startx works? maybe it's something in your .xinitrc
Offline
This may be obvious, but worth double checking: are you fully up-to-date (eg slim 1.3.3-5).
The inclusion of console-kit in slim is pretty recent - as you can tell from the flurry of recent threads on it. If you happen to have an older version of slim, that could explain these results.
"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" - Richard Stallman
Offline
@DSpider, consolekit is installed:
$ pacman -Qs consolekit
local/consolekit 0.4.6-4
A framework for defining and tracking users, login sessions, and seats
I added myself to dbus group checking if permissions might be the case. No luck -- it does not give any changes to system behavior.
/etc/inittab is unchanged after system set-up, I'm starting with runlevel 3.
$ cat /etc/inittab
#
# /etc/inittab
#
# Runlevels:
# 0 Halt
# 1(S) Single-user
# 2 Not used
# 3 Multi-user
# 4 Not used
# 5 X11
# 6 Reboot
## Only one of the following two lines can be uncommented!
# Boot to console
id:3:initdefault:
# Boot to X11
#id:5:initdefault:
rc::sysinit:/etc/rc.sysinit
rs:S1:wait:/etc/rc.single
rm:2345:wait:/etc/rc.multi
rh:06:wait:/etc/rc.shutdown
su:S:wait:/sbin/sulogin -p
# -8 options fixes umlauts problem on login
c1:2345:respawn:/sbin/agetty -8 -s 38400 tty1 linux
c2:2345:respawn:/sbin/agetty -8 -s 38400 tty2 linux
c3:2345:respawn:/sbin/agetty -8 -s 38400 tty3 linux
c4:2345:respawn:/sbin/agetty -8 -s 38400 tty4 linux
c5:2345:respawn:/sbin/agetty -8 -s 38400 tty5 linux
c6:2345:respawn:/sbin/agetty -8 -s 38400 tty6 linux
# Serial Virtual Console for KVM and others VMs
#s0:2345:respawn:/sbin/agetty -8 -s 9600 ttyS0 linux
# Hypervisor Virtual Console for Xen and KVM
#h0:2345:respawn:/sbin/agetty -8 -s 38400 hvc0 linux
ca::ctrlaltdel:/sbin/shutdown -t3 -r now
# Example lines for starting a login manager
x:5:respawn:/usr/bin/xdm -nodaemon
#x:5:respawn:/usr/sbin/gdm -nodaemon
#x:5:respawn:/usr/bin/kdm -nodaemon
#x:5:respawn:/usr/bin/slim >/dev/null 2>&1
# End of file
Last edited by DiaWorD (2012-06-28 12:14:08)
W B R
Offline
@pulce, startx from console works fine. my whole .xinitrc is one-liner
exec startxfce4
.
W B R
Offline
@Trilby,
Everything is up-to-date -- this is just-installed box.
$ pacman -Qs dbus
local/dbus 1.6.0-1
Freedesktop.org message bus system
local/dbus-core 1.6.0-5
Freedesktop.org message bus system
local/dbus-glib 0.100-1
GLib bindings for DBUS
$ pacman -Qs slim
local/slim 1.3.3-5
Desktop-independent graphical login manager for X11
Last edited by DiaWorD (2012-06-28 12:14:55)
W B R
Offline
Do you get the same error if you to start slim from inittab instead of rc.conf?
Offline
@pulce, startx from console works fine. my whole .xinitrc is one-liner
exec startxfce4
.
I got your problem several weeks ago, and I solve it with this method.
Apple hater. Panda lover.
Offline
Same conf here (but using inittab), same error.
Offline
@pulse, haven't tried this setup, but suppose it is not an issue of xfce4 - .xinitrc seems not to execute due to this problem with slim being unable to connect to dbus
W B R
Offline
yes, i guess that's the actual problem, but i don't have a good knowledge of SLiM, so i'm just telling you the steps i would do in your place. Anyway, right now i am clueless, sorry.
Offline
Anyway, thank you and everyone in the thread for your time I really appreciate it.
W B R
Offline
I have exactly the same problem with a pc I just installed
Offline
I was wondering, what if you try another DE or a WM?
Offline
Hey! This in inittab is not correct when using slim as daemon;
x:5:respawn:/usr/bin/xdm -nodaemon
I mean, two login managers?
Last edited by swanson (2012-06-28 14:55:01)
Offline
Note that in his inittab, the default runlevel is 3 so xdm is never lauched from there. I don't know if slim is supposed to work properly when started from the daemons array while booting to runlevel 3, but he should definitely fix that.
Offline
Sry, my mistake. Before systemd I started slim from initab ok.
Offline
It seems the problem affets not only slim. I tried kdm, and besides the session started, i got an error messenge:
Warning: cannot open ConsoleKit session:Unable to open session:Message did not receive a reply (timed out by message bus)
Here is the relevant part of kdm.log:
kdmgreet(1980) KdmPixmap::definePixmap: Cannot find wallpaper "Ariya"
klauncher(1986) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
kdeinit4: Communication error with launcher. Exiting!
kdmgreet(1980)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"kdmgreet(1980)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
arguments to ck_connector_get_cookie() were incorrect, assertion "connector != NULL" failed in file ck-connector.c line 583.
BTW, dbus is initialized via rc.conf.
So, it looks like last dbus upgrade changed things a little bit...
Offline
https://bugs.archlinux.org/task/30468
Is this a simular issue?
Offline
Hi,
I made a clean Arch installation yesterday and there is the same issue here.
Temporary solution (that works for me) is to downgrade both dbus and dbus-core to 1.4.20.
I have downloaded them from http://arm.konnichi.com/
dbus in extra, dbus-core in core
You can try.
Offline
Even though downgrading worked for you this time, it should not be the solution. The correct way would be to file a bug report to the appropriate channel.
There's no such thing as a stupid question, but there sure are a lot of inquisitive idiots !
Offline
Hi All, thanks for your time and attention.
inittab was untouched, it is the same as packaged one.
Slim perfectly supports running from DAEMONS, can be confirmed by wiki https://wiki.archlinux.org/index.php/SLiM#Enabling_SLiM
Also looks like this issue is confirmed for various init styles and display managers.
Again, thanks to everyone, waiting for the fix in dbus :-)
W B R
Offline
There is a new version available on the SLiM homepage,1.3.4.
Anybody tried it yet?
http://developer.berlios.de/project/sho … up_id=2663
Last edited by jordz (2012-06-28 17:51:37)
Offline
I just wanted to note, downgrading dbus also fixed the problem I was having in XFCE where I couldn't shut down, suspend or restart the computer from the XFCE menu. So I think a bug report does need to be filed somewhere, but I'm not sure where, and I'm not sure exactly how to describe the problem in a technically meaningful way.
Offline