Description of problem: /etc/gdm/PostLogin/Default does not get executed Version-Release number of selected component (if applicable): 2.22.0-5 How reproducible: Always Steps to Reproduce: 1. Create executable script /etc/gdm/PostLogin/Default 2. 3. Actual results: Script is not executed Expected results: Script should be executed Additional info:
Yeah same problem here. I've used /etc/gdm/Init/Default /etc/gdm/PostLogin/Default and /etc/X11/xinit/Xsession to start synergy (clients and servers) since (gdm replaced xdm in) F7, but it stopped working properly somewhere in F8... FWIW, I've attached a diff showing how I start synergyc on my laptop. The result of /etc/gdm/Init/Default not executing is the 'killall synergyc' in /etc/X11/xinit/Xsession failing: $ head .xsession-errors synergyc(2075): Operation not permitted synergyc: no process killed ...
Created attachment 309676 [details] diffs for my synergy setup Shows my modifications to /etc/gdm/Init/Default /etc/gdm/PostLogin/Default /etc/X11/xinit/Xsession to auto-start synergyc on gdm init and restart (as user rather than root) on login.
I'd like to confirm this as well.
I have the same problem, neither the PreSession nor PostSession scripts run. I believe the same problem is reported in this bug: https://bugzilla.redhat.com/show_bug.cgi?id=453483 I've asked about this in the fedora email list and several people promise that their Defaults do execute, so we need a little debugging help. The version of gdm supplied with Fedora 9 has very minimal documentation, no gdmsetup, and no evident route for debugging. My system was upgraded from F7 to F8, and then to F9, and it is entirely possible some package that gdm may want to use is missing. There are no error messages, however.
I think those scripts aren't run in 2.22.0. This is fixed in 2.24.0 Since 2.24.0 is mostly bug fixes since 2.22.0, we may want to push it to F9.
I downloaded the gdm 2.20 from F8 and installed it in place of 2.22 on F9 and now the Default scripts DO run again. I tried the F10 version of gdm, but installing it drew in a whole bunch of other packages--plymouth and others--and after installing the system would not display a GUI at all at start time. The cursor would show, but the background was blank. It was the same symptom I had when I tried the slim gdm, and only later did I learn that slim gdm was looking for a background image that did not exist on my system. I could fix slim by putting a default.jpg in the right spot or changing slim, but I could not get a similar fix from gdm-2.24 from F10. But I'm happy enough to run old gdm, just bummed that I wasted a week trying to figure out what the hell is going on. pj ps. Slim is promising, but not very polished yet and I couldn't quite understand all of the configuration to run a script on behalf of $USER in $HOME. Docs are still sketchy. Since gdm was able to do that, I have sought to try to fix it.
I'm using fc10 Beta with gnome 2.24.0-10, and still has the same problem
I guess we'll need to figure out why it isn't working in 2.24 before we do an update.
This is still broken in Fedora 10 (final), as is Bug #453483 https://bugzilla.redhat.com/show_bug.cgi?id=453483 , which is very similar to this one.
okay let's consolidate the two.
*** Bug 453483 has been marked as a duplicate of this bug. ***
Any updates or information on this would be useful. This seems like some pretty basic functionality to be broken. It appears to work successfully for some people, but I've tried it on some fresh installs and it does not execute.
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle. Changing version to '11'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
With Fedora 11 (2.6.29.4-167.fc11.x86_64) and GDM (2.26.1-10.fc11), I've got this: /etc/gdm/PostLogin/Default script is executed, but var are not correctly set: HOME=/var/lib/gdm # should be <user home-dir>, not <gdm home-dir> LOGIN= # not set yet! This script is important in order to modify environment: for example creating the home-dir before using it! I'm blocked with Fedora 11 here.
I'm hitting this too. I'm a bit bemused by why this would be still unresolved. I need to check $LOGNAME or $USER or something to check who's trying to log in, but it's always coming out as gdm. Could this please get looked at? It is a major bug. James
This bug was reported nearly two years ago, and as of yet there's not a single comment from the maintainer. I know this is free software and everything, but really there is no point maintaining a package if you aren't going to respond to the bug reports. Jon, can you please either fix or reassign to someone else? James
We fixed this upstream: http://git.gnome.org/browse/gdm/commit/?id=e33ee9d9b23c103ac25b6fdb53fe8c074de0de53 which will be land in Fedora 13. I'm going to close this out. If you guys would like to see this show up in a F11 update, reopen.
(In reply to comment #17) > We fixed this upstream: > > http://git.gnome.org/browse/gdm/commit/?id=e33ee9d9b23c103ac25b6fdb53fe8c074de0de53 > > which will be land in Fedora 13. I'm going to close this out. If you guys > would like to see this show up in a F11 update, reopen. Thanks for that. Is that the right link? It seems to be talking about getting PATH set right. Does it solve both problems noted here: (1) executing the scripts; (2) getting LOGNAME set correctly? I for one would greatly appreciate an F11 update (and F12 too)--I think this is a serious bug, and one that warrants fixing on all supported releases. That said, I could tolerate a workaround--if you can tell me an easy way to identify the user who is trying to log in, that would solve my problem. James
1) was handled in an earlier commit before F11 This commit handles 2. I can do an update.
(In reply to comment #19) > 1) was handled in an earlier commit before F11 > > This commit handles 2. > > I can do an update. Thank you. Updates for F11 and F12 would be great. James
gdm-2.26.1-15.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/gdm-2.26.1-15.fc11
Fedora 12 is going to be a little harder, because it has some pending backport work that needs to be finished. Let me know that the F11 packages ares working properly, and then I'll look into F12.
That's really good. Thanks--working fine in F11. Would be great to get F12 fixes too. I have just added #573452, which I am pretty sure is unrelated, but I mention it just in case. The problem there is happening with the previous gdm, but also with this newer build. James
gdm-2.26.1-15.fc11 has been pushed to the Fedora 11 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update gdm'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/gdm-2.26.1-15.fc11
gdm-2.28.2-3.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/gdm-2.28.2-3.fc12
gdm-2.28.2-3.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update gdm'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/gdm-2.28.2-3.fc12
gdm-2.28.2-3.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.
I am using Fedora 12 and the problem is still there.
Ignore my comment. I have made an error in my test. It's executed and $HOME is set. Only $LOGIN is empty
I think you want $LOGNAME rather than $LOGIN (assuming you want the username of whoever is trying to log on). James