No wayland since 20210920
Hi, wayland/plasma doesn't start any more after on my venerable HD5450 since 20210920. It freezes immediately after startup with a black screen and a static mouse pointer. VT switching doesn't work. Recovery via SysRq-e is possible. It's reproducible: Wayland works again after rolling back; re-installation of > 3000 packages results in wayland freezing. Both IceWM and plasma on X11 are working. Is anybody else experiencing such a problem with wayland? I can't find any error messages. Is there a possibility to enable extra logging at startup of wayland or plasmashell? Thanks Bernhard
wayland/plasma doesn't start any more after on my venerable HD5450 since 20210920. It freezes immediately after startup with a black screen and a static mouse pointer. VT switching doesn't work. Recovery via SysRq-e is possible. It's reproducible: Wayland works again after rolling back; re-installation of > 3000 packages results in wayland freezing. Both IceWM and plasma on X11 are working.
I turned out that I shot in my own foot: - I set umask to 0022 globally weeks ago. - 20210920 reinstalled fetchmsttfonts. - Files /usr/share/fonts/truetype/fonts.* were updated without being world-readable. - Xwayland couldn't find the default font any more and blocked during start up. BTW: kwin_wayland was able to run without Xwayland. Sorry for the noise & have fun Bernhard
On Thu, 2021-09-30 at 14:27 +0200, Bernhard Held wrote:
wayland/plasma doesn't start any more after on my venerable HD5450 since 20210920. It freezes immediately after startup with a black screen and a static mouse pointer. VT switching doesn't work. Recovery via SysRq-e is possible. It's reproducible: Wayland works again after rolling back; re-installation of > 3000 packages results in wayland freezing. Both IceWM and plasma on X11 are working.
I turned out that I shot in my own foot:
- I set umask to 0022 globally weeks ago. - 20210920 reinstalled fetchmsttfonts. - Files /usr/share/fonts/truetype/fonts.* were updated without being world-readable. - Xwayland couldn't find the default font any more and blocked during start up. BTW: kwin_wayland was able to run without Xwayland.
We used to have similar issues/bugs regarding to glib schema compilatin which took the users umask into account (eg boo#1131761). Of course one can argue that the system SHOULD honor the users wishes, but as we had too many issues there, we ended up doing: # Too many users complain about schemas compiled with wrong permissions # when in fact the system just honours there umask setting # subshell restores umask for paranoia mode %define compile_schemas \ (umask 022 && %{_bindir}/glib-compile-schemas %{_datadir}/glib-2.0/schemas) And using this compile_schemas as the new filetrigger. Since then, no more problems. Something similar might be very valid for the font cache updating triggers (Wherever they might live). I'd recommend filing a bug, so this can at least be considered by the maintainers. Cheers, Dominique
Am 2021-09-30 um 14:27 schrieb Bernhard Held:
wayland/plasma doesn't start any more after on my venerable HD5450 since 20210920. It freezes immediately after startup with a black screen and a static mouse pointer. VT switching doesn't work. Recovery via SysRq-e is possible. It's reproducible: Wayland works again after rolling back; re-installation of > 3000 packages results in wayland freezing. Both IceWM and plasma on X11 are working.
I turned out that I shot in my own foot:
- I set umask to 0022 globally weeks ago. - 20210920 reinstalled fetchmsttfonts. - Files /usr/share/fonts/truetype/fonts.* were updated without being world-readable. - Xwayland couldn't find the default font any more and blocked during start up. BTW: kwin_wayland was able to run without Xwayland.
Sorry for the noise & have fun
Still thank you for sharing the resolution to your problem report. This is a good opportunity for others to learn in case they run into similar problems. And also it supports that Tumbleweed is fine per se ;) Have fun, Oliver
On Sep 30 2021, Bernhard Held wrote:
- I set umask to 0022 globally weeks ago.
022 only removes write permission, not read permission. Did you mean 066? Andreas. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different."
On 30.09.21 at 15:04, Andreas Schwab wrote:
On Sep 30 2021, Bernhard Held wrote:
- I set umask to 0022 globally weeks ago.
022 only removes write permission, not read permission. Did you mean 066?
Andreas.
You'r eright, I mixed the masks: 0022 is the standard mask. I set it to 0026 causing trouble. Bernhard
participants (4)
-
Andreas Schwab -
Bernhard Held -
Dominique Leuenberger / DimStar -
Oliver Kurz