msm8916-samsung-a5: apps no longer start after upgrade to gtk4.0-9999.4.14.0-r0 in phosh
Describe your issue
What's the expected behaviour?
Different apps should start in phosh.
What's the current behaviour?
Phosh crashes when user tries to start an app.
How to reproduce your issue?
Start for example terminal or settings app in phosh.
What device are you using?
samsung-a5 (msm8916) with linux 6.6.0.
I have not tried with newer kernel (yet).
On what postmarketOS version did you encounter the issue?
-
edge ( master
branch) -
v23.12
-
v23.06
(supported until 2024-01-18) -
I confirm that the issue still is present after running sudo apk upgrade -a
On what environment did you encounter the issue?
Environments
-
GNOME Shell on Mobile -
Phosh -
Plasma Mobile -
Sxmo (Wayland/Sway) Please post the output of sxmo_version.sh
-
Other: Please fill out
How did you get postmarketOS image?
-
from https://images.postmarketos.org -
I built it using pmbootstrap -
It was preinstalled on my device
What's the build date of the image? (in yyyy-mm-dd format)
Additional information
When crash happens dmesg shows:
[ 146.221250] msm_mdp 1a01000.display-controller: [drm:hangcheck_handler [msm]] *ERROR* 3.0.6.0: hangcheck detected gpu lockup rb 0!
[ 146.221616] msm_mdp 1a01000.display-controller: [drm:hangcheck_handler [msm]] *ERROR* 3.0.6.0: completed fence: 662
[ 146.221955] msm_mdp 1a01000.display-controller: [drm:hangcheck_handler [msm]] *ERROR* 3.0.6.0: submitted fence: 668
[ 146.222157] msm_mdp 1a01000.display-controller: [drm:recover_worker [msm]] *ERROR* 3.0.6.0: hangcheck recover!
[ 146.222281] msm_mdp 1a01000.display-controller: [drm:recover_worker [msm]] *ERROR* 3.0.6.0: offending task: kgx (/usr/bin/kgx --gapplication-service)
[ 146.226893] revision: 307 (3.0.6.0)
[ 146.226918] rb 0: fence: 663/668
[ 146.226928] rptr: 4790
[ 146.226933] rb wptr: 4876
[ 146.226939] CP_SCRATCH_REG0: 0
[ 146.226944] CP_SCRATCH_REG1: 0
[ 146.226950] CP_SCRATCH_REG2: 662
[ 146.226956] CP_SCRATCH_REG3: 0
[ 146.226961] CP_SCRATCH_REG4: 0
[ 146.226967] CP_SCRATCH_REG5: 0
[ 146.226973] CP_SCRATCH_REG6: 0
[ 146.226978] CP_SCRATCH_REG7: 0
[ 148.221220] msm_mdp 1a01000.display-controller: [drm:hangcheck_handler [msm]] *ERROR* 3.0.6.0: hangcheck detected gpu lockup rb 0!
[ 148.221648] msm_mdp 1a01000.display-controller: [drm:hangcheck_handler [msm]] *ERROR* 3.0.6.0: completed fence: 665
[ 148.221930] msm_mdp 1a01000.display-controller: [drm:hangcheck_handler [msm]] *ERROR* 3.0.6.0: submitted fence: 668
[ 148.222262] msm_mdp 1a01000.display-controller: [drm:recover_worker [msm]] *ERROR* 3.0.6.0: hangcheck recover!
[ 148.222466] msm_mdp 1a01000.display-controller: [drm:recover_worker [msm]] *ERROR* 3.0.6.0: offending task: kgx (/usr/bin/kgx --gapplication-service)
[ 148.222679] revision: 307 (3.0.6.0)
[ 148.222699] rb 0: fence: 666/668
[ 148.222714] rptr: 64
[ 148.222724] rb wptr: 104
[ 148.222733] CP_SCRATCH_REG0: 0
[ 148.222744] CP_SCRATCH_REG1: 0
[ 148.222755] CP_SCRATCH_REG2: 665
[ 148.222766] CP_SCRATCH_REG3: 0
[ 148.222777] CP_SCRATCH_REG4: 0
[ 148.222787] CP_SCRATCH_REG5: 0
[ 148.222798] CP_SCRATCH_REG6: 0
[ 148.222808] CP_SCRATCH_REG7: 0
[ 148.721681] rfkill: input handler enabled
Downgrading gtk4 from gtk4.0-9999.4.14.0-r0 to gtk4.0-9999.4.13.6-r0 fixes the issue.
Ping at maintainers @Minecrell and @minlexx
hacker420 reported on matrix that same issue (or very similar issue) happens on j5x as well, so maybe several msm8916 are affected.
Edited by Henrik Grimler