Bug 837737

Summary:	GNOME 42? on wayland fails to display video
Product:	Gentoo Linux	Reporter:	Joseph <gentoo_bugzilla>
Component:	Current packages	Assignee:	Gentoo Linux Gnome Desktop Team <gnome>
Status:	RESOLVED WONTFIX
Severity:	normal	CC:	gentoo_bugzilla
Priority:	Normal
Version:	unspecified
Hardware:	AMD64
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---
Attachments:	logs from starting gdm & shutting down /etc/portage directory emerge --info output kernel .config diff (gentoo-sources) world file diff updated emerge --info

Description Joseph 2022-04-11 01:01:53 UTC

Some time in the last few weeks, I upgraded some packages that caused gdm to stop displaying video. It acts like the video is working (according to the logs, attached). However, nothing is displayed to the screen. Until the last few weeks, this was working properly. I suspect it's related to GNOME 42. I tried to mask gdm 42 and systemd 250.4-r1. However neither solved the problem. My guess is that it's somehow related to GNOME 42 on wayland (it looks like the packages were bumped, though the GNOME meta package was not).

Video device is intel. I was able to work around it by using lightdm, which started GNOME under X11, which works.

Reproducible: Always

Steps to Reproduce:
1. Upgrade gnome + wayland to latest version on intel
2. start gdm
3.
Actual Results:  
Empty screen

Expected Results:  
GDM login screen

Comment 1 Joseph 2022-04-11 01:04:48 UTC

Created attachment 769937 [details]
logs from starting gdm & shutting down

Comment 2 Joseph 2022-04-11 01:05:06 UTC

Created attachment 769940 [details]
/etc/portage directory

Comment 3 Joseph 2022-04-11 01:06:53 UTC

I will point out that not only does this not show video, but I see a static cursor at the top left of the screen (looks like it never stopped being in text mode), and I can't switch to another VT. I have to use the power button. So after a bit of a pause, the logs attached show me shutting down the system with the power button.

Comment 4 Mike Gilbert gentoo-dev

2022-04-11 17:59:39 UTC

Please provide emerge --info and change the status back to UNCONFIRMED.

Comment 5 Joseph 2022-04-11 18:33:28 UTC

Created attachment 770141 [details]
emerge --info output

Comment 6 Joseph 2022-04-11 18:34:42 UTC

(I added "portland" to the USE vars this morning, in case that matters)

Comment 7 Joseph 2022-04-14 19:37:02 UTC

I've tried it again (there was a firmware update and a kernel update) but still no joy. Booting into a kernel that previously used to work (last 5.16 kernel) also doesn't work.

Comment 8 Joseph 2022-04-22 23:51:53 UTC

Wayland is now working. I'm not certain what I changed to do it, precisely. I don't know precisely what I changed, as I was changing a bunch of stuff at once.

I've attached a diff on .config and the world file, and an up-to-date emerge --info

Comment 9 Joseph 2022-04-22 23:52:36 UTC

Created attachment 773339 [details, diff]
kernel .config diff (gentoo-sources)

Comment 10 Joseph 2022-04-22 23:53:40 UTC

Created attachment 773342 [details, diff]
world file diff

Comment 11 Joseph 2022-04-22 23:54:06 UTC

Created attachment 773345 [details]
updated emerge --info

Comment 12 Joseph 2022-04-22 23:55:05 UTC

I also ran emerge -e gnome until it stopped at gcc. I don't think it did anything, but it's possible.

Comment 13 Joseph 2024-05-07 20:58:14 UTC

I made it work again by blowing away $HOME. I'm not sure what the deal was.