Hi,

After recent update of gdm-2.20.11-i486-72.3.txz, a user can login only after restarting the computer. After first time login, if you log out and again try to login, it is not possible to login to any user account including the root account.

But the gdm-2.20.11-i486-72.2.txz package does not have this problem.

Anand

Hi,
Even worse here, couldn't even login after a shutdown. It seemed not to accept the password. Logged in in textmode, tried to startx but then I got :


and some more about fatal server errors

The files were there though. So I removed the new gdm package and reinstalled the 72.2 and things are back to normal (I hope)

Blackbird

I've been having exactly Blackbird's same problem since the gmd package update; glad it wasn't just my system to be allergic to the upgrade.

please could you specify which gdm package ?

I confirm this problem with previous package (72.2), but it's suppoesed to be fixed with latest gdm-2.20.11-i486-72.3.txz

tell me

JP

Hi JP,

Last time I could successfully log into my machine was on June 2nd evening; on that occasion I also recall updating gdm. The subsequent time I tried logging in was yesterday evening, to no avail; I therefore presume -- it's my home laptop I'm talking about, and now I'm at work -- I had upgraded to gdm-2.20.11-i486-72.3, which is now causing me troubles.

I'll double-check the above information later this evening, but am pretty convinced it is accurate.

The only new dot is /etc/X11/gdm/costum.conf.new

---------------------------------------------
Anyway I can confirm this problem
If you log out there is no way to log in again, you have to reboot or
go to console init 3 log and startx
I never post this problem as I have new slack X and I did supose the problem was my update.
I just remove plymouth and keep using gdm-2.20.11-i486-72.2

Hi,
The trouble started with upgrading to gdm-2.20.11-i486-72.3.txz , the upgrade of June 2nd. With 72.2 it works fine.

Blackbird

Please try with plymouth disabled at boot time, I had similar problems and after uninstalling plymouth the issue with GDM has gone.

chmod 644 /etc/rc.d/rc.splash

??

chmod 644 /etc/rc.splash will work as well, but only if you restart the system. If you just switch to rl 3 stop plymouth and the restart gdm it won't work.

Obviously the system has to be restarted

So obvious that I didn't specify it

JP

LOL, what I mean is, that it doesn't help stopping plymouth once it has be run, the gdm issue is only no problem if plymouth doesn't start at all.

the problem started first when I told gdm to stop plymouthd in the PostLogin gdm script (version 72.2).

I changed this in version 72.3 by moving the code to the /etc/X11/gdm/PreSession/Default script, and then no more login problem since.

We need to find a solution about this..

Please could you try to move the code ( ... rc.splash stop ... ) from PreSession/Default xinitrc.xfce and tell me what happens ?

Also, maybe it's the way I stop plymouthd in rc.splash ...

(I can't work on the problem since it's not reproducible here with gdm 72.3)

Cheers
JP

Uninstalling plymouth and shutting down didn't help here, had to go back to gdm-72.2 to be able to log in again. For some reason the password is not accepted, it behaves the same as when you give a wrong password, asks for the username again.

Blackbird

hum ...

the problem you have in 72.3 and that you solve with 72.2 is the problem I had in 72.2 and that I solved with 72.3...

So the problem may be elsewhere

JP