Date: Thu, 18 Dec 2003 21:56:44 -0500 From: Tom McLaughlin <tmclaugh@sdf.lonestar.org> To: freebsd-gnome@freebsd.org Subject: gdmflexiserver crashes X Message-ID: <1071802604.58179.20.camel@compass>
next in thread | raw e-mail | index | archive | help
--=-A/A+jri4neLoIUayAeAb Content-Type: text/plain Content-Transfer-Encoding: 7bit Hi everyone, I've been running into issues when trying to run gdmflexiserver or gdmflexiserver -xnest with gnome 2.4.1 from ports. When I run gdmflexiserver the monitor flickers like it is taking me to a new screen but the monitor stays dark. I have to ctrl+alt+f9 back to my original display. If I run gdmflexiserver -xnest then X and gdm actually crash and drop me to a console. Using gdmflexiserver -xnest also produces the following error in /var/log/messages: Dec 18 21:34:56 compass gdm[57837]: GDM file gdm.c: line 2852 (N/A): Cannot run setegid to 92 I see that the gdm binaries are not setgid and are owned by root. I can run both commands fine if I am logged into gnome as root which leads me to believ that this is a permission problem. [tom@compass tom]$ ls -al /usr/X11R6/bin/|grep gdm -r-xr-xr-x 1 root wheel 264 Dec 15 00:41 gdm* -r-xr-xr-x 1 root wheel 215916 Dec 15 00:41 gdm-binary* lrwxr-xr-x 1 root wheel 15 Dec 15 00:41 gdmXnest@ -> gdmXnestchooser -r-xr-xr-x 1 root wheel 43048 Dec 15 00:41 gdmXnestchooser* -r-xr-xr-x 1 root wheel 69568 Dec 15 00:41 gdmchooser* -r-xr-xr-x 1 root wheel 36584 Dec 15 00:41 gdmflexiserver* -r-xr-xr-x 1 root wheel 130392 Dec 15 00:41 gdmgreeter* -r-xr-xr-x 1 root wheel 102804 Dec 15 00:41 gdmlogin* -r-xr-xr-x 1 root wheel 30592 Dec 15 00:41 gdmphotosetup* -r-xr-xr-x 1 root wheel 69960 Dec 15 00:41 gdmsetup* -r-xr-xr-x 1 root wheel 1664 Dec 15 00:41 gdmthemetester* I have only had this problem after building gnome 2.4.1 from ports. I did not have this problem in gnome 2.4.0 and this machine's current incarnation never had gnome 2.4.0 installed since I first thought this was a problem with the port upgrade and something from the old port conflicting with the new port. (Still getting used to ports here.) I have attached the log from XFree that corresponds to the crash. Thanks for any help. Tom (P.S. While I was looking for the correct log to attach I noticed that I have :0.log, :20.log, XFree86.0.log, and XFree86.20.log. Can someone explain the naming convention? Why do I have two 0 and two 20 logs?) --=-A/A+jri4neLoIUayAeAb Content-Disposition: attachment; filename=":20.log" Content-Type: text/plain; name=":20.log"; charset= Content-Transfer-Encoding: 7bit xnest warning: unhandled event --=-A/A+jri4neLoIUayAeAb--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1071802604.58179.20.camel>