I've got latest official (I mean nothing masked...) gnome2 installed. When I try to login in a nested window (menu applications --> System tools --> new login in a nested window) the gdm login screen appears. then I can't use keys l,s,y,q in my username nor in my password because these keys (normally used with alt) make respectively the language, session, system, quit dialog boxes appear even if alt key is not pressed ! I don't have this problem in not nested login screen. I tried these keys with all modifiers, always the same behaviour, --> can't use nested logins... Arnaud
Sounds more like an X problem to me, what X server are you using. If you run xdm (or kdm if you have it) instead of gdm, do you see the same problem ?
I'm seeing this at work, too, with GNOME2. At home with GNOME2.1 I don't see that behaviour. I don't know though, if it was there with GNOME2. What I don't understand is why this bug is of minor severity.
It's not easy to reproduce that using xdm, (btw, I don't have kdm...) the gnome menu item launches gdmflexiserver --xnest, which reuqires gdm to be already started which is not because as you asked I used xdm ... Now I could launch an gnome-session into an xnest, there the keyboard behaviour is fine ... And severity is minor because I can run everything, it's just annoying to have no gui to perform tasks as other users ... I admit it could be more that minor, change it to the appropriate please ! :) Arnaud
Yeah i figured out the standard gdm xnest item uses a bit diff system. The severity was a misclick i think when i posted my other comment, thought it doesnt have much priority to me. Basicly i don't have a clue, i can't reproduce the problem. If you run the nest command from a term, do you get any ouput ? Something in .gnomerc_error maybe ?
running gdmflexiserver --xnest on the cmd line doesn't output anything, and nothing in .gnomerc-error about that... this guy on the forum seemed to have the same problem btw ... : http://forums.gentoo.org/viewtopic.php?t=16017&highlight=nested ... I've got no reply from him...
Interesting. With the upgrade you guys mean the switch from gnome2-r1 to gnome2-r2 right ? But gdm didn't get upgraded there, only gnome-panel, gnome-desktop and gnome-session. With a bit of work you could see if one of these packs mixed things up.
I think I've got the latest gnome2 installed... I've got : ACCEPT_KEYWORDS="~x86" in my make.conf so I think I've got the latest gnome... Maybe should I recompile if so please specify how (I broke my first gnome installe with a reemerge ...)
First of all, with ~x86 you agree to use unstable marked packages (thats not the case here btw, i unmasked these already). You should be aware of this and casual users should not use this keyword imo, only when specifically wanting to test a certain package or really needing it. Please be aware of this. Second an emerge of gnome should not be able to b0rk harm your install in any way. Third, just emerge the one but latest version of the named packages and see if the problem still exists. Then upgrade them one by one to the latest version again and see which package causes the problem (if one of them does, it might be not at all related).
so, first I perfectly know what ~x86 does and means, I'm not complaining about anything, I had to use that flag. Enough of that I think. Now, I tried to emerge the 3 packages back to their older version, that is : gnome-panel 2.0.9 gnome-desktop 2.0.8 gnome-session 2.0.7 using "emerge =gnome-panel-2.0.9" when I had 2.0.10 installed and so on... after a reboot (needed for something else) an "emerge -s gnome-panel" reported: * gnome-base/gnome-panel Latest version available: 2.0.10 Latest version installed: 2.0.10 Homepage: http://www.gnome.org/ Description: The Panel for Gnome2 that even after emerging 2.0.9, same for the 2 other packages. Maybe I did a mistake, please tell me about it... at that point, still the same bug. I've done as if the result of "emerge -s pkg" was normal, that is emerged in that order gnome-session, gnome-panel, gnome-desktop. between each emerge I checked and saw that the bug wasn't fixed by the reemerge. think that's all for today...
Hmmm you didn't clean up the old (in this case newer) version of gnome-* probably, it might have reported wrong because of that. But you could try clean them out first and then emerge the old version. Anyway, because the forum thread suggested it started with the gnome update i would just like to test if that had anything todo with it. I have nothing else to work on.
so, now I've got : ghort@ghort666:~> emerge -s gnome-desktop 2:50:40 Searching... [ Results for search key : gnome-desktop ] [ Applications found : 1 ] * gnome-base/gnome-desktop Latest version available: 2.0.9 Latest version installed: 2.0.8 Homepage: http://www.gnome.org/ Description: Libraries for the gnome desktop that is not part of the UI ghort@ghort666:~> emerge -s gnome-session 2:50:47 Searching... [ Results for search key : gnome-session ] [ Applications found : 1 ] * gnome-base/gnome-session Latest version available: 2.0.8 Latest version installed: 2.0.7 Homepage: http://www.gnome.org/ Description: the Gnome2 session manager ghort@ghort666:~> emerge -s gnome-panel 2:50:50 Searching... [ Results for search key : gnome-panel ] [ Applications found : 1 ] * gnome-base/gnome-panel Latest version available: 2.0.10 Latest version installed: 2.0.9 Homepage: http://www.gnome.org/ Description: The Panel for Gnome2 and still the same bug. Now some questions : 2.0.10 is a new gnome-panel (with bugfixes and maybe new features) from gnome team or is it a new ebuild? In case it is new ebuild, should I try older ebuilds ? how ? Should I try earlier versions ? really enough for tonight!
Those are new stable gnome versions of those packages. Gentoo specific sub-updates come by revisions (-r*). Well, if that worked ok (or rather it didn't), then we can eliminate it as a possible cause. Now where to go from here :)
Is this still a problem, even with the latest (masked) gdm ebuild ?
if you mean gdm 2.4.0.11-r1, it doesn't work... If you mean another, either I rsynced with a not so up-to-date rsync mirror... or it is masked with ~x86... Which is correct?
Ok, whats the status here. Hows it with gdm-2.4.0.12 ?
Good news, it works now ! Could anyone else who had this bug confirm ? I'll let you close the bug ...
closing...
