You are not logged in.
See solution at bottom of this post...
Ok this isn't a normal slim login issue with a bad config.
Currently I run xfce4+xfwm with slim as my login manager.
Using parted-magic the other night to first copy the root partition to an external drive as a backup i went ahead and wiped my swap and root partition, edited fstab and grub.cfg and eventually replaced the intramfs and kernel with some recent backups as the originals kept me hung at the uresume hook i had been using(i use a swap file but have disabled it for the time being). Long story short i have got it booting back to login with startx working partially. slim on the other hand drops me to a blank screen with the "x" cursor after login. I know copying recursively an entire / file system isn't the best practice however i couldn't seem to get rsync to do it. I was able to preserve the symlinks and most likely i feel it's a change in permissions/ownership somewhere. I've done this once before similarly and was able to recovery completely. Here's relevant lines for .xinitrc, rc.conf, and the output of "startx &> foo.log
rc.conf daemons: (dbus slim @wicd @bluetooth @preload) Note:slim is omitted for the moment as i am running startx until it can be fixed.
.xinitrc line that is executed:
exec dbus-launch startxfce4
Note:Currently the neither --with-ck-launch nor ck-launch-session do not resolve the issue when added to .xinitrc. I am still have to type my password to restart, poweroff etc and currently mount or recognize external drives as well as connect to bluetooth devices now.
foo.log output:
X.Org X Server 1.12.3
Release Date: 2012-07-09
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.4.4-3-ARCH x86_64
Current Operating System: Linux 1018p-Asus 3.4.6-1-ARCH #1 SMP PREEMPT Fri Jul 20 08:21:26 CEST 2012 x86_64
Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=e608a89b-9380-4c00-a856-5da71149ecb8 ro quiet
Build Date: 09 July 2012 03:59:39PM
Current version of pixman: 0.26.2
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: Sat Jul 21 20:32:00 2012
(==) Using config directory: "/etc/X11/xorg.conf.d"
/usr/bin/startxfce4: X server already running on display :0
(xfsettingsd:9569): xfsettingsd-WARNING **: Failed to get the _NET_NUMBER_OF_DESKTOPS property.
N: [pulseaudio] main.c: User-configured server at {fea792649eb6ea4bd869238b00000f3d}unix:/tmp/pulse-2N7LZIxIgzrn/native, which appears to be local. Probing deeper.
(polkit-gnome-authentication-agent-1:9565): polkit-gnome-1-WARNING **: Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ExecFailed: Failed to execute program /usr/lib/dbus-1.0/dbus-daemon-launch-helper: Success
(tilda:9615): Gdk-CRITICAL **: IA__gdk_drawable_get_display: assertion `GDK_IS_DRAWABLE (drawable)' failed
(tilda:9615): Gdk-CRITICAL **: _gdk_x11_window_get_toplevel: assertion `GDK_IS_WINDOW (window)' failed
(tilda:9615): Gdk-WARNING **: gdk_window_set_user_time called on non-toplevel
(tilda:9615): Gdk-CRITICAL **: IA__gdk_drawable_get_display: assertion `GDK_IS_DRAWABLE (drawable)' failed
(tilda:9615): Gdk-CRITICAL **: _gdk_x11_window_get_toplevel: assertion `GDK_IS_WINDOW (window)' failed
(tilda:9615): Gdk-WARNING **: gdk_window_set_user_time called on non-toplevel
(Thunar:9555): GVFS-RemoteVolumeMonitor-WARNING **: remote volume monitor with dbus name org.gtk.Private.UDisks2VolumeMonitor is not supported
(gedit:10629): GVFS-RemoteVolumeMonitor-WARNING **: remote volume monitor with dbus name org.gtk.Private.UDisks2VolumeMonitor is not supported
(gedit:10826): GVFS-RemoteVolumeMonitor-WARNING **: remote volume monitor with dbus name org.gtk.Private.UDisks2VolumeMonitor is not supported
[11207:11219:3792606066:ERROR:object_proxy.cc(489)] Failed to call method: org.freedesktop.DBus.Error.Spawn.ExecFailed: Failed to execute program /usr/lib/dbus-1.0/dbus-daemon-launch-helper: Success
Gkr-Message: secret service operation failed: The name org.freedesktop.secrets was not provided by any .service files
(thunar-volman:24892): GVFS-RemoteVolumeMonitor-WARNING **: remote volume monitor with dbus name org.gtk.Private.UDisks2VolumeMonitor is not supported
thunar-volman: Unsupported USB device type.
(thunar-volman:24895): GVFS-RemoteVolumeMonitor-WARNING **: remote volume monitor with dbus name org.gtk.Private.UDisks2VolumeMonitor is not supported
thunar-volman: Unsupported USB device type.
(thunar-volman:24899): GVFS-RemoteVolumeMonitor-WARNING **: remote volume monitor with dbus name org.gtk.Private.UDisks2VolumeMonitor is not supported
thunar-volman: Unsupported input device type.
(thunar-volman:24900): GVFS-RemoteVolumeMonitor-WARNING **: remote volume monitor with dbus name org.gtk.Private.UDisks2VolumeMonitor is not supported
thunar-volman: Unsupported input device type.
(thunar-volman:24901): GVFS-RemoteVolumeMonitor-WARNING **: remote volume monitor with dbus name org.gtk.Private.UDisks2VolumeMonitor is not supported
(thunar-volman:24902): GVFS-RemoteVolumeMonitor-WARNING **: remote volume monitor with dbus name org.gtk.Private.UDisks2VolumeMonitor is not supported
(thunar-volman:24903): GVFS-RemoteVolumeMonitor-WARNING **: remote volume monitor with dbus name org.gtk.Private.UDisks2VolumeMonitor is not supported
(thunar-volman:24904): GVFS-RemoteVolumeMonitor-WARNING **: remote volume monitor with dbus name org.gtk.Private.UDisks2VolumeMonitor is not supported
(thunar-volman:24905): GVFS-RemoteVolumeMonitor-WARNING **: remote volume monitor with dbus name org.gtk.Private.UDisks2VolumeMonitor is not supported
thunar-volman: Unsupported USB device type.
(thunar-volman:24906): GVFS-RemoteVolumeMonitor-WARNING **: remote volume monitor with dbus name org.gtk.Private.UDisks2VolumeMonitor is not supported
thunar-volman: Unsupported USB device type.
(thunar-volman:29473): GVFS-RemoteVolumeMonitor-WARNING **: remote volume monitor with dbus name org.gtk.Private.UDisks2VolumeMonitor is not supported
(thunar-volman:29474): GVFS-RemoteVolumeMonitor-WARNING **: remote volume monitor with dbus name org.gtk.Private.UDisks2VolumeMonitor is not supported
thunar-volman: Unsupported USB device type.
thunar-volman: Unsupported USB device type.
(thunar-volman:29477): GVFS-RemoteVolumeMonitor-WARNING **: remote volume monitor with dbus name org.gtk.Private.UDisks2VolumeMonitor is not supported
thunar-volman: Unsupported USB device type.
(thunar-volman:29478): GVFS-RemoteVolumeMonitor-WARNING **: remote volume monitor with dbus name org.gtk.Private.UDisks2VolumeMonitor is not supported
thunar-volman: Unsupported USB device type.
(thunar-volman:29486): GVFS-RemoteVolumeMonitor-WARNING **: remote volume monitor with dbus name org.gtk.Private.UDisks2VolumeMonitor is not supported
(thunar-volman:29487): GVFS-RemoteVolumeMonitor-WARNING **: remote volume monitor with dbus name org.gtk.Private.UDisks2VolumeMonitor is not supported
thunar-volman: Unknown block device type.
thunar-volman: Unknown block device type.
(tilda:9615): Gdk-CRITICAL **: IA__gdk_drawable_get_display: assertion `GDK_IS_DRAWABLE (drawable)' failedSolution:
The problem was with /var/lock . backing up the directory then removing it allowed me to reinstall "filesystem" with pacman. I ran one of the scripts posted here: https://bbs.archlinux.org/viewtopic.php?pid=263443 inorder to reinstall everything since at the time I didn't know where the issue was comming from. when filesystem failed and halted the installation it gave an error trying to install about overwriting /var/lock. removing it allowed pacman to create the symlink again. now everything
runs fine. apparently it was the symlink I missed when copying recusively. Note: the pacman database wasn't either present nor accessible(not sure which) so some of methods for reinstalling everything didn't work or couldn't pull up my currently installed packages. at least that was my case. the slim login problem was due to the location of the slim.lock file in /var/lock/.
#rm /var/lock
#pacman -S filesystem
done. It was simpler than I thought. searching for the problem's source was what took so long for me.
Last edited by Thme (2012-07-22 18:13:14)
"Hidden are the ways for those who pass by, for light is perished and darkness comes into being." Nephthys:
Ancient Egyptian Coffin Texts
Offline