Strange GNOME 46 wayland behaviour on freshly installed system

zamonary1 · 2024-03-26 08:00:53

I didn't really wanted to go on forums but i am experiencing these kind of issues for the first time.
I have never used wayland before
When you boot up the system and log on in session with gnome on wayland the screen just freezes and system stops responding to any inputs (like ctrl+alt+F2). Only after pressing the power button linux starts shutting down.
If you instead select gnome on xorg it just loads a bit longer than expected (around 15 seconds) and works as normal.
What's interesting is that when you exit the xorg session and try to enter wayland again wayland works absolutely normal.

i3 10105f
rx580 2048sp
16gb ddr4
gnome 46

I can provide any logs and open for suggestions.

Vash63 · 2024-03-26 09:06:38

I'm seeing the same on an older install after upgrading to 46 final. Strangely, 46rc from gnome-testing branch worked fine, but after migrating to the final release it stopped working.

I didn't really see anything interesting in the logs. If I ctrl+alt+f3 I can switch back to GDM and it has given up on the login and I can try again (which fails) or select a different DE.

Edit: Saw this thread: https://bbs.archlinux.org/viewtopic.php?id=294189

This was my issue as well, I had an old `libgdm-plymouth` that didn't work anymore.

Last edited by Vash63 (2024-03-26 09:20:42)

seth · 2024-03-31 16:10:00

@zamonary1, reposting counts as bumping…

We'll need a system journal

sudo journalctl -b | curl -F 'file=@-' 0x0.st

from the xorg login (at least) and when wayland fails, don't reboot w/ the power button, at least not by pushing it until the system reboots.
A short press, frenetic use of ctrl+alt+del or https://wiki.archlinux.org/title/Keyboa … el_(SysRq) will preserve the journal that you can post as well after the reboot

sudo journalctl -b -1 | curl -F 'file=@-' 0x0.st

zamonary1 · 2024-04-02 14:35:05

After xorg login
http://0x0.st/Xz3d.txt
I don't have a sysrq key on my keyboard and i am not entirely sure what to do after system hangs. Can you give me more instructions please?

seth · 2024-04-02 15:23:54

It's typically the print key.
The wiki explains how to enable the sysrq and what shortcuts to use (REISUB should not be used unconditionally but is usually and here what you want)

The posted log has only an X11 login and what sticks out is

апр 02 17:14:25 archlinux otd-daemon[1698]: [Detect:Info]        Found tablet 'XP-Pen Star G640'

Do you have any issues w/o that device?

zamonary1 · 2024-04-04 17:59:14

After disconnecting the tablet before system boot gnome wayland behaves practically the same.
I tried to get SysRq key combinations on linux mint but my keyboard doesn't react to them and i really think that it is because my cheap ass chinese keyboard changes the lighting effects with fn+prtscr

seth · 2024-04-04 20:54:38

Did you add "sysrq_always_enabled=1" to the https://wiki.archlinux.org/title/Kernel_parameters ?
The SysRq will NOT require you to press the Fn key!
Otherwise, do you have a $5 office supply keyboard?

Arch Linux

#1 2024-03-26 08:00:53

Strange GNOME 46 wayland behaviour on freshly installed system

#2 2024-03-26 09:06:38

Re: Strange GNOME 46 wayland behaviour on freshly installed system

#3 2024-03-31 16:10:00

Re: Strange GNOME 46 wayland behaviour on freshly installed system

#4 2024-04-02 14:35:05

Re: Strange GNOME 46 wayland behaviour on freshly installed system

#5 2024-04-02 15:23:54

Re: Strange GNOME 46 wayland behaviour on freshly installed system

#6 2024-04-04 17:59:14

Re: Strange GNOME 46 wayland behaviour on freshly installed system

#7 2024-04-04 20:54:38

Re: Strange GNOME 46 wayland behaviour on freshly installed system

Board footer