gdm versions 2.6.x have never allowed any login except to gnome failsafe, and the xsession error file says it could not execute '/etc/X11/gdm/Xsession'. I looked at the Xsession file and it is a .c source file. Previous versions of gdm, eg 2.4.x, has a !/bin/sh script file there. Reproducible: Always Steps to Reproduce: 1. USE="~x86" emerge gdm 2. gdm 3. select any gnome login except failsafe (from botton session menu) 4. try to login as usual Actual Results: An error message that it could not login, and would you like to view the errors files, then I said yes, and it said it couldn't execute Xsession, and no wonder, since its a 'c' file. Expected Results: Gdm should have just logged me in to my default gnome desktop. This bug has been here forever; I've just grown accustomed to selecting 'failsafe' when I log in. Shouldn't someone else have noticed? I couldn't find any other bug report on this issue, although a few other reports have suggested that one just copy the 'Xsession' file from /usr/portage.../gdm/... to /etc/X11/gdm, but those were for an earlier 2.4 release of gdm. This 2.6 release has the same 'c' file in /usr/portage/gnome-base/gdm/files/2.6.0/Xsession, so there's no help from just copying it into /etc/X11/gdm.
what do you mean with a 'c' file ? an executable ? thats allright, it's a shell script
No, I mean a file that contains 'c' code, and _should_ be a .c file somewhere until it is compiled and linked. Heres 'head -n 20 /etc/X11/gdm/Xsession' : #include <stdio.h> #include <stdlib.h> #include <string.h> #include "../config.h" #include "../mp_msg.h" #include "../cpudetect.h" #include "img_format.h" #include "mp_image.h" #include "vf.h" #include "../libvo/fastmemcpy.h" struct metrics { /* difference: total, even lines, odd lines */ int d, e, o; /* noise: temporal, spacial (current), spacial (past) */ int t, s, p;
your checkout is messed up, this is certainly not the file in cvs & you couldve checked that yourself by checking viewcvs. Anyway, just for reference attach your full 'Xsession' please.
Created attachment 41498 [details] emerged /usr/portage/gnome-base/gdm/files/2.6.0/Xsession 'emerge sync' gave this gdm Xsession file.
What 'checkout' is messed up? I got my file from 'emerge sync' and I haven't used cvs yet. If I can get this file via 'emerge sync' then maybe this bug is an emerge bug and not a gdm bug, but its still pretty messed up. Here is the 'ls -l' of my /usr/portage/gnome-base/gdm/files/2.6.0: total 13 -rwxr-xr-x 1 root root 6198 Aug 8 06:08 Xsession -rw-r--r-- 1 root root 301 Aug 8 06:08 custom.desktop drwxr-xr-x 2 root root 136 Aug 8 06:08 pam.d drwxr-xr-x 3 root root 80 Aug 8 06:08 security and the full Xsession file is attached.
'checkout' as in 'sync' obviously and if its alright in cvs it's a problem either with your mirror or your machine, not much i can do anything about. If it's really a mirror problem (!not your machine!) then you can maybe file a bug about the mirror, but i doubt it because you are the only one reporting it. Just delete your portdir and do a fresh resync.
Thanks, but I figured out from your last post that a rm and resync would probably fix the problem, and it did.