You are not logged in.
http://bbs.archlinux.org/viewtopic.php?id=71991
I've had a rough time these past few days and I posted earlier on Arch64 forums thinking it was just architecture thing but as it turns out after my reinstallation of Arch to 64 bit again (First i686, then 64, then i686 and now 64 again) I finally got it to work but this time Gnome is a pain in the ass, it didn't work with KDE either but KDE never gave me an error or gave me an option to failsafe into the OS.
$HOME/.xsession-errors:
/etc/gdm/Xsession: Beginning session setup...
/etc/gdm/Xsession: Setup done, will execute: /usr/bin/ssh-agent -- gnome-session
gnome-session[3898]: WARNING: Could not connect to ConsoleKit: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
gnome-session[3898]: CRITICAL: dbus_g_connection_get_connection: assertion `gconnection' failed
process 3898: arguments to dbus_connection_send_with_reply_and_block() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 3298.
This is normally a bug in some application using the D-Bus library.
D-Bus not built with -rdynamic so unable to print a backtrace
gnome-session[3898]: ******************* START ********************************
gnome-session[3898]: Frame 0: gnome-session [0x4192d7]
gnome-session[3898]: Frame 1: gnome-session [0x419426]
gnome-session[3898]: Frame 2: /lib/libc.so.6 [0x7f3cbc493ec0]
gnome-session[3898]: Frame 3: /lib/libc.so.6(gsignal+0x35) [0x7f3cbc493e45]
gnome-session[3898]: Frame 4: /lib/libc.so.6(abort+0x19a) [0x7f3cbc4952aa]
gnome-session[3898]: Frame 5: /usr/lib/libdbus-1.so.3 [0x7f3cbef6ab95]
gnome-session[3898]: Frame 6: /usr/lib/libdbus-1.so.3 [0x7f3cbef66a5d]
gnome-session[3898]: Frame 7: /usr/lib/libdbus-1.so.3(dbus_connection_send_with_reply_and_block+0x198) [0x7f3cbef50a88]
gnome-session[3898]: Frame 8: gnome-session [0x41203c]
gnome-session[3898]: Frame 9: gnome-session [0x412140]
gnome-session[3898]: Frame 10: gnome-session [0x41a5b0]
gnome-session[3898]: Frame 11: gnome-session [0x41aa8f]
gnome-session[3898]: Frame 12: /lib/libc.so.6(__libc_start_main+0xfd) [0x7f3cbc48055d]
gnome-session[3898]: Frame 13: gnome-session [0x40aef9]
gnome-session[3898]: ******************* END **********************************/var/log/gdm/:0.log.3
X.Org X Server 1.6.1
Release Date: 2009-4-14
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.29-ARCH x86_64
Current Operating System: Linux deuklin 2.6.29-ARCH #1 SMP PREEMPT Sat May 9 14:09:36 CEST 2009 x86_64
Build Date: 15 April 2009 11:01:49AM
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Tue May 12 08:55:10 2009
(==) Using config file: "/etc/X11/xorg.conf"
dlopen: libdrm.so.2: cannot open shared object file: No such file or directory
(EE) Failed to load /usr/lib/xorg/modules/extensions//libdri.so
(EE) Failed to load module "dri" (loader failed, 7)
(EE) Failed to load module "freetype" (module does not exist, 0)
dlopen: libdrm.so.2: cannot open shared object file: No such file or directory
(EE) Failed to load /usr/lib/xorg/modules/extensions//libdri2.so
(EE) Failed to load module "dri2" (loader failed, 7)
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
> Ignoring extra symbols
Errors from xkbcomp are not fatal to the X serverJust a point here is that I've had the exact same software installed the same day that I reinstalled and this error did not occur but after formatting my partition with ext4 and testing Arch64 it did. But it did with 32bit as well, there were tons of errors.
I've read about this ConsoleKit error in a few posts here but nothing seems to indicate a fix or anything and since I'm using Gnome now I didn't find anything on it just about KDE.
I can safely use "Failsafe Gnome" without startup scripts but I want it to work without any problems and I don't know if the "dri" thing is related to the ConsoleKit thing with GDM.
I installed it via FTP and had the latest updates as soon as I've installed, so if this is just something that is happening to me right now or alot of other people, please give us hints or anything that could solve this?
If you read my Arch64 thread you know that stuff stopped working for me, first the network (it turns out I had to boot Windows inbetween installing Arch for my network even to start and that sounds ridicilous if it depends on another operating system starting the device because in Windows the network card was turned on with a green light wherein Arch after installing it didn't. I reformated my partitions and changed it again, installed Windows again and tried it out and then installed Arch. It worked, and then I mixed around with KDE and after five minutes of using "startx" (the only thing working) I decided to reinstall with Gnome, but then the network didn't start again (tried booting about ten times) and then I just thought "Let's start windows first so it turns on" and when I just booted Windows and immiedatiely restarted it and booted with the Arch CD, network was available again. Strange? Or is this a period of instability for Arch?
But when I got my network to start, appearantly Keyboard and mouse wasn't working because Xorg forgot to install the drivers when I installed the full group of Xorg so I had to fix that and now it's giving me this error.
Offline
Without a dbus socket, dbus probably isn't running. It's supposed to be started automatically when a program needs it. Check to see that it is installed and running:
pacman -Q dbus
pgrep -l dbus
Dbus won't run without hal, so hal should be in:
tail /etc/rc.conf
Are any of your partitions full?
df -h
For the other error, it looks like libdrm isn't installed, but I don't think you need it if you're running the nvidia driver.
Your xorg.conf and Xorg.0.log would also be useful. Also check dmesg for errors.
And see if /etc/rc.d/dbus is marked executable.
Last edited by fphillips (2009-05-12 18:27:41)
Offline
pacman -Q dbus
dbus 1.2.4.6permissive-1
pgrep -l dbus
17445 dbus-launch
17446 dbus-daemon
hal isn't in the daemon list (but I believe I did have it running while using KDE, can try it again)
no disk is full, just partitioned a 320 gb harddrive so there's plenty of space.
none 1006M 0 1006M /dev/shm
shows up at 0% on df -h
should dbus be in "daemon" list as well? cause I've never had it there before and neither on my other Arch computer.
Offline
ok. adding Hal to daemon list after syslogd worked, but I'm defiantly sure that this did not work with KDE and KDM!
thanks for the help. gonna check if there's any errors anyway that it justs ignores.
Offline
No, dbus should not be the daemon list.
That /dev/shm is "shared memory," a ramdisk, likely from the live CD environment you were running at the time.
Offline