Bug 1397471 - With GNOME wayland session, computer freezes on login
Summary: With GNOME wayland session, computer freezes on login
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gdm
Version: 25
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-22 15:32 UTC by Jean-François Fortin Tam
Modified: 2017-12-12 10:26 UTC (History)
4 users (show)

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


Attachments (Terms of Use)
journalctl output (18.00 KB, text/plain)
2016-11-22 15:50 UTC, Jean-François Fortin Tam
no flags Details

Description Jean-François Fortin Tam 2016-11-22 15:32:29 UTC
00:02.0 VGA compatible controller: Intel Corporation Iris Graphics 6100 (rev 09)

Upgraded my F24 intel-based laptop to F25 today, and it boots fine up to GDM... but as soon as you launch the normal wayland-based "GNOME Shell" user session, it freezes completely. The mouse cursor sits right in the middle of the screen on top of the dark gray background, and cannot be moved. The computer does not respond to keyboard input including ctrl+alt+F1/F2/F3/etc. A hard poweroff is required by pressing the power button (it seems systemd detects it and does a somewhat clean shutdown, though).

Logging in with the "GNOME on X" session works fine.

Comment 1 Jean-François Fortin Tam 2016-11-22 15:50:28 UTC
Created attachment 1222755 [details]
journalctl output

Simplified journalctl output, from the moment my user is authentified until I press the power switch. I took out networkmanager-related and telepathy-related entries.

Note that I am not running with SELinux enabled.

Comment 3 Jean-François Fortin Tam 2016-11-23 02:50:48 UTC
The problem also affected my radeon-based workstation.

I think I found the culprit in my case: https://extensions.gnome.org/extension/690/easyscreencast/ will cause the shell lockup if you haven't upgraded this extension to the latest version (requiring disabling the extension, upgrading then enabling it). So if anybody has that extension active while going to the new GNOME on Wayland version, they are likely to encounter this issue.

Comment 4 Phillip Schichtel 2017-06-13 17:26:49 UTC
I can confirm this on Archlinux with GNOME 3.24.
Even after the update of the extension, enabling it froze my desktop for a moment.

Comment 5 Fedora End Of Life 2017-11-16 19:47:07 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 6 Fedora End Of Life 2017-12-12 10:26:51 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.