Bug 467507 - plasma-mobile fails to start on PP after kwin's commit eef9bd5c with "libkwinglutils: Shaders are not supported"
Summary: plasma-mobile fails to start on PP after kwin's commit eef9bd5c with "libkwin...
Status: RESOLVED FIXED
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: 5.27.2
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-03-17 20:48 UTC by Marco Mattiolo
Modified: 2023-03-19 15:29 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
photo of PP when plasma-mobile does not start on kwin 5.27.2 (65.57 KB, image/jpeg)
2023-03-17 20:48 UTC, Marco Mattiolo
Details
journalctl log of PP when starting plasma-mobile on kwin 5.27.2 (189.65 KB, text/plain)
2023-03-17 20:49 UTC, Marco Mattiolo
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Marco Mattiolo 2023-03-17 20:48:18 UTC
Created attachment 157373 [details]
photo of PP when plasma-mobile does not start on kwin 5.27.2

SUMMARY
Hi and thank you for developing kwin!
On my OG PP with Mobian bookworm, plasma-mobile 5.27.2 is no more working since kwin 5.27.2 hit the testing repo. Please note, plasma-mobile 5.27.2 was working correctly on top of kwin 5.26.90 and downgrading kwin back to 5.26.90 reverts back to a working state. Additionally, another Mobian user reported this on Matrix on their Pinetab.

After logging in, a white rectangle in the top right corner appears on top of black background. Nothing else happens, GUI never appears.
By comparing the journalctl log with a previous one, the following line seems new
mar 12 21:10:59 mobian kwin_wayland_wrapper[977]: libkwinglutils: Shaders are not supported

Furthermore, by git bisecting kwin, problems starts happening after commit eef9bd5c [1].
Looks to me, that commit is identifying if some low-spec devices are present, thus setting some flags to disable features which run smoothly on higher-spec systems only. Driver for OG PP video rendering (Lima) is also mentioned in that commit.

Just guessing, that commit is setting device as unable to do a bunch of things (including shaders, as of error message), but it's failing to keep some other part of kwin from triggering those things?

Is there a way to tell plasma-mobile to not use shaders, like [2] for blur? That could be a temporary workaround

[1] https://invent.kde.org/plasma/kwin/-/commit/eef9bd5c4e564e9cbca6188c52cb3cee5ab9c825
[2] https://invent.kde.org/plasma-mobile/plasma-phone-settings/-/blob/master/etc/xdg/kwinrc#L6

SOFTWARE/OS VERSIONS
Linux: 6.1-sunxi64
KDE Plasma Version: 5.27.2
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8
Comment 1 Marco Mattiolo 2023-03-17 20:49:23 UTC
Created attachment 157374 [details]
journalctl log of PP when starting plasma-mobile on kwin 5.27.2
Comment 2 Zamundaaa 2023-03-19 01:01:10 UTC
This is fixed in 5.27.3
Comment 3 Marco Mattiolo 2023-03-19 14:12:30 UTC
(In reply to Zamundaaa from comment #2)
> This is fixed in 5.27.3

Thank you for your feedback! To be sure, the relevant commit is 64d682a6 [1] , right?
I'm asking because Debian is now in hard freeze for upcoming bookworm release: 5.27.3 will not be accepted, but I will ask kwin's maintainer for cherry-picking the commit to fix this...

[1] https://invent.kde.org/plasma/kwin/-/commit/64d682a646d111a0250bbe3bff77ef0cead91403
Comment 4 Zamundaaa 2023-03-19 15:29:26 UTC
yes, that's the one