Bug 97815 - Unresponsive weston with flickering image after hibernation
Summary: Unresponsive weston with flickering image after hibernation
Alias: None
Product: Wayland
Classification: Unclassified
Component: weston (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium enhancement
Assignee: Wayland bug list
QA Contact:
Depends on:
Reported: 2016-09-15 08:46 UTC by Siarhei
Modified: 2018-06-08 23:54 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Description Siarhei 2016-09-15 08:46:20 UTC
Distribution: Arch Linux
Hardware: AMD E-450 APU with Radeon 6320 HD
Kernel: 4.7.2
Weston: 1.11.0

Description: After resuming from hibernation (systemctl hibernate), weston's image flickers but display mouse cursor or totally garbaged with random noise.

Quitck-Fix: Switch to another VT, then suspend and resume machine (systemctl suspend, not systemctl hibernate this time), switch back to weston's VT.

There is similar behaviour mentioned in another weston's issue:

Steps to reproduce:
- Launch weston (dbus-launch --exit-with-session=weston)
- Run hibernation (systemctl hibernate)
- Resume from hibernation
- You see weston session's image, or just random noise, that flickers when mouse is moved. It depends on boot, that you can see normal cursor point, but no more.
Looks like clicking upon launcher icons, runs those applications, but the picture
is corrupted.

Here you can see logs from weston, as well as dmesg and systemd messages related to suspend and hibenation, the weston config added too:
Comment 1 GitLab Migration User 2018-06-08 23:54:47 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/wayland/weston/issues/81.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.