Date: Wed, 29 Mar 2006 16:54:21 -0600 From: Paul Schmehl <pauls@utdallas.edu> To: freebsd-questions@freebsd.org Subject: More problems with xorg Message-ID: <BFE11B1EBE75E4E41D0962AD@utd59514.utdallas.edu>
next in thread | raw e-mail | index | archive | help
Now that I finally got xinerama working again (by using MergeFB as an Option for my Radeon card), another problem has cropped up. The screensaver isn't running, and when I lock the workstation, I can't get a prompt to unlock. The screen goes to the unlock screen with no prompt. dbus is running: root@hostname# dbus-launch DBUS_SESSION_BUS_ADDRESS='unix:path=/var/tmp/dbus-KbuylYjLnz,guid=500b2b44f8f2f2b68c02568f0755f200'; DBUS_SESSION_BUS_PID=851; and the socket exists, but there's an extra one: root@hostname# ls /var/tmp/dbus-* /var/tmp/dbus-KbuylYjLnz /var/tmp/dbus-mHCgjDCXI2 which claims to be in use: root@hostname# dbus-cleanup-sockets Cleaned up 0 sockets in /var/tmp; 2 sockets are still in use; 0 in unknown state but gnome-screensaver can't find the socket: root@hostname# gnome-screensaver-command gnome-screensaver-Message: Failed to connect to the D-BUS daemon: Unable to dete rmine the address of the message bus If I export the session bus address in the terminal, then gnome-screensaver-command can connect, and it tells me screensaver is not running: root@hostname# export DBUS_SESSION_BUS_ADDRESS=unix:path=/var/tmp/dbus-KbuylYjLnz root@hostname# gnome-screensaver-command gnome-screensaver-Message: Screensaver is not running! Here's log entries germane to screensaver: root@hostname# grep screensaver /var/log/* | less /var/log/setuid.today:2103930 -r-sr-sr-x 1 root wheel 73512 Mar 11 00:28:00 2006 /usr/X11R6/libexec/gnome-screensaver-dialog /var/log/setuid.yesterday:2103930 -r-sr-sr-x 1 root wheel 73512 Mar 11 00:28:00 2006 /usr/X11R6/libexec/gnome-screensaver-dialog And to gdm: /var/log/messages:Mar 29 13:54:16 utd59514 gdm[673]: Error reinitilizing server /var/log/messages:Mar 29 16:14:56 utd59514 gdm[678]: Error reinitilizing server There's nothing else in the logs (AFAICT) to give me a clue what might be wrong. If I lock the desktop, I have to restart gdm (Ctrl-Alt-Backspace) to get functionality back, and the console says "gdm[pid]: Error reinitializing properly". Any suggestions as to what to look at next would be appreciated. Paul Schmehl (pauls@utdallas.edu) Adjunct Information Security Officer The University of Texas at Dallas http://www.utdallas.edu/ir/security/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BFE11B1EBE75E4E41D0962AD>