After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 756039 - gdm don't perform virtual console swich after login with proprietary nvidia drivers
gdm don't perform virtual console swich after login with proprietary nvidia d...
Status: RESOLVED DUPLICATE of bug 754814
Product: gdm
Classification: Core
Component: general
3.18.x
Other Linux
: Normal critical
: ---
Assigned To: GDM maintainers
GDM maintainers
Depends on:
Blocks:
 
 
Reported: 2015-10-04 11:50 UTC by Óscar García Amor
Modified: 2015-10-07 19:43 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Óscar García Amor 2015-10-04 11:50:54 UTC 
Today I perform an update to latest GDM (gdm 3.18.0), after reboot machine I enter login/password, the screen goes to gray (fade off my picture and the textbox) and infinite wait.

I have to manual swich to second virtual console.

I try deleting all user data (new user) and the behaviour is the same.

The GDM log says:
oct 04 13:28:00 hell systemd[1]: Starting GNOME Display Manager...
oct 04 13:28:00 hell systemd[1]: Started GNOME Display Manager.
oct 04 13:28:01 hell gdm[467]: GdmDisplay: display lasted 1,435673 seconds
oct 04 13:28:01 hell gdm[467]: Child process -597 was already dead.
oct 04 13:28:01 hell gdm[467]: Child process 526 was already dead.
oct 04 13:28:01 hell gdm[467]: Unable to kill session worker process
oct 04 13:28:14 hell gdm-password][1032]: pam_unix(gdm-password:session): session opened for user ogarcia by (uid=0)
Comment 1 Ray Strode [halfline] 2015-10-05 14:36:33 UTC 
does hitting escape work too? sounds like a dupe of bug 754814
Comment 2 Óscar García Amor 2015-10-05 18:23:35 UTC 
Yes, maybe a dupe of bug 754814 cause pressing escape key do the work too.
Comment 3 Óscar García Amor 2015-10-07 12:47:06 UTC 
I observed a new behaviour.

If you wait one or two minutes before perform the login, then works perfect.
Comment 4 Ray Strode [halfline] 2015-10-07 19:43:07 UTC 

*** This bug has been marked as a duplicate of bug 754814 ***