Bug 1442227 - Gnome session hangs, systemctl restart gdm hangs as well
Summary: Gnome session hangs, systemctl restart gdm hangs as well
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gdm
Version: 25
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-04-13 19:58 UTC by Christophe de Dinechin
Modified: 2017-12-12 10:18 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-12 10:18:32 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Screen shot after systemctl restart gdm (2.65 MB, image/jpeg)
2017-04-13 19:58 UTC, Christophe de Dinechin
no flags Details

Description Christophe de Dinechin 2017-04-13 19:58:50 UTC
Created attachment 1271535 [details]
Screen shot after systemctl restart gdm

Description of problem:

On two different machines, I had some hangs with black screen and live mouse. On one machine, I had this almost systematically after screen blanking / screen lock, to the point that I disabled screen blanking entirely (I wish this machine could auto-lock, even if it does not contain any sensitive material). On another machine, it was after logging out to attempt to clear an issue with vino-server.

In both cases, I attempted to restart gdm with "systemctl restart gdm". I was unsuccessful every time (4 attempts total). In all cases, the restart fails, and you end up with a text console showing boot messages, see attachment. The last one is "Stopping User Manager for UID 42". Ctrl-Alt-Fn does not work at that stage.

Running systemctl status gdm shows gdm still running, an assertion and an error message with "too many open files". ps -ef | grep gdm shows that the original gdm process is still running, although I have no graphical login.

● gdm.service - GNOME Display Manager
   Loaded: loaded (/usr/lib/systemd/system/gdm.service; enabled; vendor preset: enabled)
   Active: active (running) since Thu 2017-04-13 20:35:24 CEST; 1h 11min ago
 Main PID: 5025 (gdm)
    Tasks: 3 (limit: 4915)
   CGroup: /system.slice/gdm.service
           └─5025 /usr/sbin/gdm

Apr 13 20:38:00 muse.dinechin.org gdm[5025]: Unable to kill session worker process
Apr 13 20:38:01 muse.dinechin.org gdm[5025]: Child process -18189 was already dead.
Apr 13 20:38:01 muse.dinechin.org gdm[5025]: Child process 18181 was already dead.
Apr 13 20:38:01 muse.dinechin.org gdm[5025]: Unable to kill session worker process
Apr 13 20:38:01 muse.dinechin.org gdm[5025]: GdmDisplay: display lasted 0.382937 seconds
Apr 13 20:38:01 muse.dinechin.org gdm[5025]: Could not start command '/usr/libexec/gdm-session-worker': Too many open files
Apr 13 20:38:01 muse.dinechin.org gdm[5025]: GLib: g_child_watch_add_full: assertion 'pid > 0' failed
Apr 13 20:38:01 muse.dinechin.org gdm[5025]: Child process -18215 was already dead.
Apr 13 20:38:01 muse.dinechin.org gdm[5025]: Child process 18207 was already dead.
Apr 13 20:38:01 muse.dinechin.org gdm[5025]: Unable to kill session worker process

In all cases, the machine is "live" can be reached normally using ssh.

Using such a connection do to a "killall gdm" results in a flashing login screen alternating between login and boot console, see https://www.youtube.com/watch?v=hjpwRAz3vaw. Control-Alt-Fn does not work well at that stage either.

Version-Release number of selected component (if applicable):

gdm.x86_64                                             1:3.22.1-1.fc25                                             @anaconda



How reproducible: Always (in the screen blanking case)


Steps to Reproduce:
1. Wait until screen lock appears
2. Try to login
3. See that the screen is black with moving mouse cursor, but no login textbox
4. ssh to the machine, attempt "systemctl restart gdm"
5. ssh to the machine, attempt "killall gdm"

Actual results:

No clean way to restart gdm


Expected results:

gdm shuts down and restart, possible to login again.


Additional info:

Screen shot, see attachment.
Flashing screen, sss https://www.youtube.com/watch?v=hjpwRAz3vaw

Comment 1 Fedora End Of Life 2017-11-16 18:54:22 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 2 Fedora End Of Life 2017-12-12 10:18:32 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.