Date: Fri, 19 Dec 2003 00:45:35 -0500 From: Joe Marcus Clarke <marcus@marcuscom.com> To: Tom McLaughlin <tmclaugh@sdf.lonestar.org> Cc: freebsd-gnome@freebsd.org Subject: Re: gdmflexiserver crashes X Message-ID: <1071812734.30952.12.camel@shumai.marcuscom.com> In-Reply-To: <1071802604.58179.20.camel@compass> References: <1071802604.58179.20.camel@compass>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-T0/Yy1+HQGZrGz623nWS Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Thu, 2003-12-18 at 21:56, Tom McLaughlin wrote: > Hi everyone, I've been running into issues when trying to run > gdmflexiserver or gdmflexiserver -xnest with gnome 2.4.1 from ports.=20 > 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: >=20 > Dec 18 21:34:56 compass gdm[57837]: GDM file gdm.c: line 2852 (N/A): > Cannot run setegid to 92 >=20 >=20 > 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. Known bug: http://bugzilla.gnome.org/show_bug.cgi?id=3D127780. I think this has to do with the following commit: Thu Sep 25 11:23:24 2003 George Lebl <jirka@5z.com> = =20 * daemon/errorgui.c, daemon/slave.c: be even analer (is that a word?) about the setuid stuff here (it can't actually fail, but just in case, we're being paranoid) Also reset the environment and desetuid for the setup program even though that's not really needed. I'd add your info to the bug as it's definitely lacking some details. Joe >=20 > [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* >=20 > 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. >=20 > Tom >=20 > (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?) >=20 > ______________________________________________________________________ > _______________________________________________ > freebsd-gnome@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-gnome > To unsubscribe, send any mail to "freebsd-gnome-unsubscribe@freebsd.org" --=20 PGP Key : http://www.marcuscom.com/pgp.asc --=-T0/Yy1+HQGZrGz623nWS Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQA/4pB+b2iPiv4Uz4cRAh1uAJ9RYifPbqXJoqIKYiKNLls2bk3LuwCfTDeU Xc2jCyWY0bE4R6/TiqY5wq0= =XPuh -----END PGP SIGNATURE----- --=-T0/Yy1+HQGZrGz623nWS--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1071812734.30952.12.camel>