GDM not starting up correctly, DBUS related?

life · 2011-03-02 21:44:17

Hi all,

- Clean install
- dbus daemon starts in rc.conf
- Starting /etc/rc.d/gdm start

In /var/log/gdm/\:0-slave.log I get:

gdm-simple-slave[3812]: WARNING: Unable to open session: The name org.freedesktop.ConsoleKit was not provided by any .service files

gdm-simple-slave[3812]: WARNING: Could not spawn command: Failed to execute child process "/usr/bin/dbus-launch" (Permission denied)
gdm-simple-slave[3812]: WARNING: Unable to launch D-Bus daemon: Failed to execute child process "/usr/bin/dbus-launch" (Permission denied)
gdm-simple-slave[3812]: WARNING: Could not spawn command: Failed to execute child process "/usr/bin/gnome-session" (Permission denied)
gdm-simple-slave[3812]: WARNING: Could not start command '/usr/bin/gnome-session --autostart=/usr/share/gdm/autostart/LoginWindow/': Failed to execute child process "/usr/bin/gnome-session" (Permission denied)

And then it just sits there with the watch as a cursor.

I then used .xinitrc and startx with:

exec ck-launch-session gnome-session

In /var/log/messages I get:

gnome-session[6915]: WARNING: Could not connect to ConsoleKit: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

How can I get gdm and dbus to behave?

defears · 2011-03-03 03:22:58

It says it can't find consolekit. So install it. And just make sure dbus is first in rc.conf. (Just in case.)

life · 2011-03-03 07:56:00

consolekit is installed, and so is the dbus config for it:

[root@emily~]# pacman -Q consolekit
consolekit 0.4.3-2

[root@emily ~]# ls -l /etc/dbus-1/system.d/ConsoleKit.conf
-rw-r--r-- 1 root root 7305 Feb 1 22:15 /etc/dbus-1/system.d/ConsoleKit.conf

dbus is first (after syslog) in rc.conf.

My dbus installation seems fubar, and I have no idea how to debug it next.

mandog · 2011-03-03 11:18:55

You have added yourself to the appropriate groups and setup your users correctly I seem to recall something like this about 4 years ago when did my 1st install or did mess up my innitab file just thoughts. no I think it was GDM no user password.

wonder · 2011-03-03 11:22:06

it says it couldn't run consolekit and a lot more binaries. you should start your research based on that.

is not dbus related, is something wrong with your system.

life · 2011-03-03 11:30:44

I am added to these groups:

[life@emily ~]$ groups
lp wheel network video audio optical floppy storage power life

X, gnome and pulseaudio all run. Except that none of those can get to DBUS. So I have no automounting and no gdm login.

wonder, definitely is something wrong with my system. Hence why I'm trying to fix it :-)

I still get a feeling that the system dbus is not starting up correctly.

mandog · 2011-03-03 14:45:06

If its any help this is my group list
root:x:0:root
bin:x:1:root,bin,daemon
daemon:x:2:root,bin,daemon
sys:x:3:root,bin
adm:x:4:root,daemon
tty:x:5:
disk:x:6:root
lp:x:7:daemon,kelvin
mem:x:8:
kmem:x:9:
wheel:x:10:root,kelvin
ftp:x:11:
mail:x:12:
uucp:x:14:
log:x:19:root,kelvin
locate:x:21:
rfkill:x:24:
smmsp:x:25:
http:x:33:
games:x:50:kelvin
network:x:90:kelvin
video:x:91:kelvin
audio:x:92:kelvin
optical:x:93:hal,kelvin
floppy:x:94:hal
storage:x:95:hal,kelvin
scanner:x:96:kelvin
power:x:98:kelvin
nobody:x:99:
users:x:100:kelvin
dbus:x:81:kelvin
avahi:x:84:
lxdm:x:121:kelvin
hal:x:82:kelvin
gdm:x:120:kelvin
camera:x:97:kelvin
cdemu:x:1000:kelvin
usbmux:x:140:kelvin
vboxusers:x:108:kelvin

life · 2011-03-03 20:11:58

mandog, thank you for the list.

My dbus/policykit installation is still broken. This is a clean install with no edits:

[root@emily life]# ck-list-sessions
** (ck-list-sessions:4004): WARNING **: Failed to get list of seats: The name org.freedesktop.ConsoleKit was not provided by any .service files

I installed hal, and it refuses to start up. It does start up DBUS, seemingly successful:

DAEMONS=(!syslog-ng rsyslogd hal network netfs crond)

I then tried running hald in debug mode:

[root@emily /]# /usr/sbin/hald --daemon=no --verbose=yes
22:05:34.865 hald.c:673: hal 0.5.14
22:05:34.865 hald.c:674: using child timeout 250s
22:05:34.865 hald.c:739: Will not daemonize
22:05:34.865 hald_dbus.c:5444: local server is listening at unix:abstract=/var/run/hald/dbus-kplOH1H1BB,guid=315daa1fd4b2baf93bccd77a0000009a
22:05:34.867 hald_runner.c:304: Runner has pid 3996
Runner started - allowed paths are '/usr/lib/hal:/usr/lib/hal/scripts:/usr/bin'
22:05:34.867 hald_runner.c:184: runner connection is 0x8154448
22:05:34.870 osspec.c:393: Unable to open /proc/mdstat: No such file or directory

** (process:3995): WARNING **: Failed to add monitor on '/usr/share/hal/fdi/preprobe': Permission denied

** (process:3995): WARNING **: Failed to add monitor on '/etc/hal/fdi/preprobe': Permission denied

** (process:3995): WARNING **: Failed to add monitor on '/usr/share/hal/fdi/information': Permission denied

** (process:3995): WARNING **: Failed to add monitor on '/etc/hal/fdi/information': Permission denied

** (process:3995): WARNING **: Failed to add monitor on '/usr/share/hal/fdi/policy': Permission denied

** (process:3995): WARNING **: Failed to add monitor on '/etc/hal/fdi/policy': Permission denied
20:05:34.871 mmap_cache.c:126: Regenerating fdi cache..
Could not get password database information for UID of current process: User "???" unknown or no memory to allocate password entry

Could not get password database information for UID of current process: User "???" unknown or no memory to allocate password entry

20:05:34.872 hald_runner.c:888: Error running 'hald-generate-fdi-cache': org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
20:05:34.872 mmap_cache.c:104: In regen_cache_cb exit_type=2, return_code=0
20:05:34.872 mmap_cache.c:153: fdi cache regeneration failed!
20:05:34.872 mmap_cache.c:156: fdi cache generation done
20:05:34.872 mmap_cache.c:278: cache mtime is 0
*** [DIE] osspec.c:osspec_init():449 : Unable to read /proc/mounts

mandog · 2011-03-04 14:17:56

You must put dbus as the 1st deamom then hal Dbus must start 1st
as per mine
DAEMONS=(dbus hal @syslog-ng @network @netfs gdm @alsa @cups @crond)

Last edited by mandog (2011-03-04 14:29:07)

wonder · 2011-03-04 14:22:17

hal is really not needed for gnome since 1 and a half year ago

mandog · 2011-03-04 14:33:23

wonder wrote:

hal is really not needed for gnome since 1 and a half year ago

that may be true if you do not want multiple partitions to automount in the correct order hal can do that very successfully also a lot of programs still need hal.

life · 2011-03-04 14:59:34

mandog, I used that configuration too. Then I used the hal-starts-up-dbus options. Both does start up dbus, but not hal.

wonder, I am trying to find the smallest possible test case to get dbus to work. HAL as part of the system startup seems to be my best bet.

i.e. I want something to test that dbus is usable without starting any X based applications.

Maki · 2011-03-05 17:47:47

i have a quite similar problem, i had an arch64 bit system and reverted to arch32. Everything went fine except i couldn't run kde apps because of service not found dbus problems, added a new user and now kde works, but trying to run kde apps as root fails with the same problem, and i can't shutdown or reboot via kdm.

mandog · 2011-03-06 02:03:05

Maki wrote:

i have a quite similar problem, i had an arch64 bit system and reverted to arch32. Everything went fine except i couldn't run kde apps because of service not found dbus problems, added a new user and now kde works, but trying to run kde apps as root fails with the same problem, and i can't shutdown or reboot via kdm.

If its KDE you are using to run apps as root you need to use "kdesu appname" I run Gnome, KDE4, LXDE distros all 64bt I use KDE apps in gnome LXDE and vice verser with out problem I have not altered any default setting these are all recent separate installs. Make sure you are in the group power, to shutdown kde

Maki · 2011-03-06 04:50:28

i have fixed my problem by running sudo rm -rf /var/tmp/kdecache-*. maybe try if gnome uses a similar directory.
and now power off works but i have the consolekit problem now .

edit. i solved it by following this http://chakra-project.org/bbs/viewtopic.php?pid=551, just create a consolekit daemon.

Last edited by Maki (2011-03-06 06:05:15)

life · 2011-03-06 12:27:42

Maki wrote:

i have fixed my problem by running sudo rm -rf /var/tmp/kdecache-*. maybe try if gnome uses a similar directory.
and now power off works but i have the consolekit problem now .
edit. i solved it by following this http://chakra-project.org/bbs/viewtopic.php?pid=551, just create a consolekit daemon.

Thanks Maki. I have a deeper problem I think.

life · 2011-03-06 12:46:37

For some reason, the dbus user can not open the files it needs when running the dbus-daemon --system command:

I traced the daemon with this:

[root@emily ~]# strace -e trace=file -p 14934 # The dbus-daemon --system PID

When I do ck-list-sessions as root, I get:

access("/var/run/console/root", F_OK)   = -1 EACCES (Permission denied)
open("/proc/15544/cmdline", O_RDONLY)   = -1 EACCES (Permission denied)
open("/usr/local/share/dbus-1/system-services", O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY|O_CLOEXEC) = -1 EACCES (Permission denied)
open("/usr/share/dbus-1/system-services", O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY|O_CLOEXEC) = -1 EACCES (Permission denied)

With the /usr/share/dbus-1/system-services/org.freedesktop.ConsoleKit.service not available to the dbus user, it won't be possible to do ConsoleKit actions, I assume.

When I do ck-list-sessions as a user, I get:

open("/etc/passwd", O_RDONLY|O_CLOEXEC) = -1 EACCES (Permission denied)

Why would that be? The whole world can at the very least open /etc/passwd. Why would the dbus user not be able to?

Some more data points:

[life@emily ~]# grep dbus /etc/group
dbus:x:81:gdm
[life@emily ~]# grep dbus /etc/passwd
dbus:x:81:81:System message bus:/:/bin/false

The dbus user exists and seems to exist correctly.

life · 2011-03-13 17:25:00

A fresh, net install solved this. I installed via the "existing linux" route. I don't know how that might break things, but it probably did.

For posterity:

After installing consolekit, ck-list-sessions should work.

If it does not, your installation is borked.

Arch Linux

#1 2011-03-02 21:44:17

GDM not starting up correctly, DBUS related?

#2 2011-03-03 03:22:58

Re: GDM not starting up correctly, DBUS related?

#3 2011-03-03 07:56:00

Re: GDM not starting up correctly, DBUS related?

#4 2011-03-03 11:18:55

Re: GDM not starting up correctly, DBUS related?

#5 2011-03-03 11:22:06

Re: GDM not starting up correctly, DBUS related?

#6 2011-03-03 11:30:44

Re: GDM not starting up correctly, DBUS related?

#7 2011-03-03 14:45:06

Re: GDM not starting up correctly, DBUS related?

#8 2011-03-03 20:11:58

Re: GDM not starting up correctly, DBUS related?

#9 2011-03-04 14:17:56

Re: GDM not starting up correctly, DBUS related?

#10 2011-03-04 14:22:17

Re: GDM not starting up correctly, DBUS related?

#11 2011-03-04 14:33:23

Re: GDM not starting up correctly, DBUS related?

#12 2011-03-04 14:59:34

Re: GDM not starting up correctly, DBUS related?

#13 2011-03-05 17:47:47

Re: GDM not starting up correctly, DBUS related?

#14 2011-03-06 02:03:05

Re: GDM not starting up correctly, DBUS related?

#15 2011-03-06 04:50:28

Re: GDM not starting up correctly, DBUS related?

#16 2011-03-06 12:27:42

Re: GDM not starting up correctly, DBUS related?

#17 2011-03-06 12:46:37

Re: GDM not starting up correctly, DBUS related?

#18 2011-03-13 17:25:00

Re: GDM not starting up correctly, DBUS related?

Board footer