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 709623 - login hangs, if user is logged in on a tty
login hangs, if user is logged in on a tty
Status: RESOLVED FIXED
Product: gdm
Classification: Core
Component: general
3.10.x
Other Linux
: Normal major
: ---
Assigned To: GDM maintainers
GDM maintainers
Depends on:
Blocks:
 
 
Reported: 2013-10-08 09:53 UTC by Peter
Modified: 2014-11-13 09:07 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
journalctl -b -l --no-pager (5.97 KB, text/plain)
2013-10-08 09:53 UTC, Peter
Details

Description Peter 2013-10-08 09:53:35 UTC
Created attachment 256712 [details]
journalctl -b -l --no-pager

Hello!

Since gdm-3.10.0 it is not possible to login with gdm to GNOME, if the user is already logged in on a tty.

Steps to reproduce:
1. Boot up, until gdm shows login-screen
2. Ctrl+Alt+Fx # switch to random choosen virtual-terminal
3. Login with user and passwd at getty/login
4. Alt+F1 # switch to gdm
5. Login with user and passwd at gdm
7. Screen becomes completely gray and stays gray
8. One CPU-Core loops (some kind of race-condition with another process?) now at 100% with the process 'gnome-shell'

That shouldn't happen :-)
To some degree this bugs is really curious. Maybe there is a special unknown condition required to trigger this. During development this bug must be triggered a thousand times?

System is an up-to-date Archlinux.

Thank you
Comment 1 Peter 2013-10-08 09:55:42 UTC
I'm sorry. The journalctl output was generated after reboot with "journalctl -l --no-pager" without "-b".
Comment 2 Peter 2013-10-08 12:48:00 UTC
https://bugzilla.redhat.com/show_bug.cgi?id=985506

Affects Fedora 19 and GNOME-3.8 but it sounds similiar. Could some weird $LANG value the reason? Mine is "en_US.UTF8".
Comment 3 Peter 2013-10-13 10:03:03 UTC
I now relativley sure that this is not caused by the issues mentioned in the link above. However, since the upgrade to gnome-session-3.10.1 the problem didn't occured again.

http://ftp.gnome.org/pub/GNOME/sources/gnome-session/3.10/gnome-session-3.10.1.news
https://bugzilla.gnome.org/show_bug.cgi?id=709221

I will try to reproduce the problem during the next days, if I can't reproduce it I will closed this bug.
Comment 4 Peter 2013-11-26 15:54:32 UTC
Sadly this problem seems still to exist. I just didn't happend for some time.
Comment 5 Kamil Páral 2013-11-28 10:08:33 UTC
I can reproduce this with gnome-shell-3.10.2.1-2.fc20.x86_64. Happened on a third attempt.
Comment 6 Peter 2014-11-13 09:07:56 UTC
Didn't happen for long time.