In Wayland, can't wake up monitor after it has gone black

Bug #1983175 reported by Coeur Noir
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
mutter (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

Hi,

sorry I don't know if it's about GDM or else.

Ubuntu 22.04.1 LTS
jammy
Linux 5.15.0-41-generic x86_64 x86_64
ubuntu / wayland
installed DE's are :
ubuntu.desktop ubuntu-xorg.desktop

My system is set to turn screen black after some minutes. And after some other minutes later, it locks the screen → no sleep nor hibernate involved ( even if sleep and hibernate are ok on that machine. )

On Xorg, after screen's gone black, any mouse or keyboard solicitation fires up again the screen, as expected.

On Wayland, after screen's gone black, any mouse or keyboard solicitation just does nothing, screen stays black.

BUT

keyboard is not turned off : only thing that works for « waking up » the screen is
key-combo [ ctrl ] + [ alt ] + [ F1 ]

If of any interest :
django@ASGARD:~$ sudo lshw -c video
[sudo] Mot de passe de django :
  *-display
       description: VGA compatible controller
       produit: Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller
       fabricant: Intel Corporation
       identifiant matériel: 2
       information bus: pci@0000:00:02.0
       nom logique: /dev/fb0
       version: 06
       bits: 64 bits
       horloge: 33MHz
       fonctionnalités: msi pm vga_controller bus_master cap_list rom fb
       configuration : depth=32 driver=i915 latency=0 resolution=1920,1080
       ressources : irq:33 mémoire:f7800000-f7bfffff mémoire:e0000000-efffffff portE/S:f000(taille=64) mémoire:c0000-dffff
django@ASGARD:~$

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thanks for the bug report.

Next time the bug occurs, please:

1. Wait 10 seconds.

2. Reboot.

3. Run:

   journalctl -b-1 > prevboot.txt

4. Attach the resulting text file here.

affects: gdm3 (Ubuntu) → mutter (Ubuntu)
tags: added: jammy
tags: added: wayland wayland-session
tags: added: i915
Changed in mutter (Ubuntu):
status: New → Incomplete
Revision history for this message
Coeur Noir (coeur-noir) wrote :

Well I did not forget.

The joke is, I did not encounter the « bug » since.

Maybe some regular update solved the thing ?

Mutter, mesa, gnome-shell, gdm… there had been a few updates for them since, so who knows ?

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

No problem. The bug will automatically close after 2 months if no further comments are added.

Revision history for this message
Coeur Noir (coeur-noir) wrote :

Mmm…

I had « the bug » once yesterday.

Maybe I can narrow down a bit its context.

After using some sessions on the machine ( meaning : all sessions work and I'm able to switch between all of them, using « change user » ) I went back to the login screen where one can chose an user. But I had to left office a moment, an hour maybe, so leaving computer with that login screen on ( the one that shows after clicking on « change user » )

Back at the office, screen is black, which seems normal
but typing anything on keyboard or moving mouse or clicking blindly did not wake up screen.

And this time [ ctrl ] + [ alt ] + [ F1 ] did nothing.

So I hit the [ sleep ] key on the keyboard, putting computer in …sleep, of course.
Waking it up, still nothing on screen but hitting [ ctrl ] + [ alt ] + [ F1 ] brought me back the login screen.

Does this help to pinpoint a culprit ?

[ sorry, I forgot about the log, I'll try to think about it next it happens. If it happens. ]

Xorg sessions, by the way these days.

Revision history for this message
Coeur Noir (coeur-noir) wrote :

Mmmm… maybe around 17:00 there's some strange things, see attached file.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1968040, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

Revision history for this message
Coeur Noir (coeur-noir) wrote :

Ok thanks for pointing to a possible workaround :-)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.