Created attachment 156497 [details] first joournalctl log SUMMARY It happens e.g. after unlocking wallet from kwalletmanager, but it happens with other apps, too: app remains responsive, but top and bottom bars are stuck. As no touch gesture is there to close apps and/or reset the shell, only workaround I've found is to press power button for ~3seconds, log out to the login manager and then log back in. Please find attached some logs: common message seems to be kwin_core: Could not find window with uuid "{...}" SOFTWARE/OS VERSIONS Linux: 6.1-sunxi64 KDE Plasma Version: 5.26.90 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION Device: OG PP
Created attachment 156498 [details] second journalctl log
Created attachment 156499 [details] third journalctl log
Created attachment 156500 [details] fourth journalctl log
Tried also resetting shell settings [1] and starting plasma-mobile as a stand-alone service instead of from phog login manager, it still freezes from time to time. It's not even a memory issue: last time it froze, I checked the memory consumption trough serial console. It does not seem completely full.. marco@mobian:~$ free -m total used free shared buff/cache available Mem: 2994 1585 759 219 950 1409 Swap: 255 0 255 [1] https://invent.kde.org/plasma/plasma-mobile/-/wikis/Shell-Debugging-Tips#resetting-shell-settings
Created attachment 156512 [details] photo of device when plasma-mobile is frozen Included a photo of the device when plasma-mobile is frozen: in this example, telegram-desktop is fullscreen, I can scroll up and down, get into conversations, but I cannot use plasma's top&bottom bar. Please note, plasma's bar are blue, while normally those are grey. It looks like plasma freezes during app's splash screen.
(In reply to Marco Mattiolo from comment #5) > Created attachment 156512 [details] > photo of device when plasma-mobile is frozen > > Included a photo of the device when plasma-mobile is frozen: in this > example, telegram-desktop is fullscreen, I can scroll up and down, get into > conversations, but I cannot use plasma's top&bottom bar. Please note, > plasma's bar are blue, while normally those are grey. It looks like plasma > freezes during app's splash screen. You mention the app splash screen, there was a fix added recently regarding that (for Plasma 5.27.1), but it was for crashing: https://invent.kde.org/plasma/plasma-mobile/-/commit/b37605849795cc421361ed1663cf6781255b3f8d I have not yet been able to replicate this freezing issue, I'll keep looking
Hi Devin! This issue is frustrating, haven't found a way to trigger it reliably so far... It's not limited to the splash screen and it does not freeze on every splash screen, but it just happened again and I'm able to add some context. The session was running without issues, no problem in opening/closing and switching between apps, then I had telegram-desktop, kwalletmanager and nheko open, I closed nheko, pressed the square in the bottom bar and plasma froze, screen lose contrast (gray scale instead of colour) and never came back, I had to press power button for 3 seconds and log out. Clock was at 21.33, that is useful to check log: feb 20 21:33:20 mobian plasmashell[2704]: [2023-02-20 21:33:20.930] [qml] [warning] QObject::connect(TimelineModel, TimelineFilter): invalid nullptr parameter (:0, ) feb 20 21:33:20 mobian plasmashell[2704]: [2023-02-20 21:33:20.930] [qml] [warning] QObject::connect(TimelineModel, TimelineFilter): invalid nullptr parameter (:0, ) feb 20 21:33:20 mobian plasmashell[2704]: [2023-02-20 21:33:20.930] [qml] [warning] QObject::connect(QAbstractItemModel, TimelineFilter): invalid nullptr parameter (:0, ) feb 20 21:33:22 mobian plasmashell[2704]: [2023-02-20 21:33:22.581] [net] [error] sync error: (parser: [json.exception.parse_error.101] parse error at line 1, column 1: syntax error while parsing value - unexpected end of input; expected '[', '{', or a literal: ) feb 20 21:33:23 mobian systemd[816]: app-nheko-e8abf70b8e144034bd8bfdd4ea49084a.scope: Consumed 21.247s CPU time. feb 20 21:33:40 mobian dbus-daemon[458]: [system] Activating service name='org.kde.powerdevil.backlighthelper' requested by ':1.72' (uid=1000 pid=1377 comm="/usr/lib/aarch64-linux-gnu/libexec/org_kde_powerde") (using servicehelper) feb 20 21:33:40 mobian dbus-daemon[458]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper' feb 20 21:33:45 mobian systemd-logind[473]: Power key pressed short. feb 20 21:33:46 mobian dbus-daemon[865]: [session uid=1000 pid=865] Activating service name='org.kde.LogoutPrompt' requested by ':1.24' (uid=1000 pid=995 comm="/usr/bin/ksmserver") feb 20 21:33:47 mobian dbus-daemon[865]: [session uid=1000 pid=865] Successfully activated service 'org.kde.LogoutPrompt' Another question: in the logs I often find plasmashell[2080]: QBuffer::seek: Invalid pos: -118765761 a lot of those lines, are those relevant? About the splashscreen commit, IIRC 5.27.1 should be tagged tomorrow, then I will directly test the package to be uploaded to Debian in a couple of days, thank you for pointing it out!
Created attachment 156550 [details] fifth journalctl log, freeze happens at 21.33 time
Hmm, would be interesting to figure out what causes " QBuffer::seek: Invalid pos:" (I don't get that on other distros), but I don't think it'd be related. I see some crashes there that would need further investigation...
After upgrading to plasma-mobile 5.27.1, this issue seems to be vanished, at least for a stress test of a few minutes I've just done. Let me check this for some further days...
(In reply to Marco Mattiolo from comment #10) > After upgrading to plasma-mobile 5.27.1, this issue seems to be vanished, at > least for a stress test of a few minutes I've just done. > Let me check this for some further days... I was too fast, it's still happening on 5.27.1
Created attachment 156930 [details] another photo of frozen plasma-mobile Took another photo of plasma-mobile being frozen, maybe the previous photo was misleading about it being limited to splash screens: it froze in the task switcher, then further touch interaction got the screen to gray scale, that AFAIK is the usual behavior when a freeze is recognized... Just guessing, could this be related to animations? Closing/switching tasks involves some animation, as does splash screen when launching an app... could you please recommend a way to disable animations to test this hypothesis?
There isn't a direct way to disable animations, but you can try going into the Settings->Shell->animation and toggle it, which controls certain animations. I wonder though if the issue you are having is with pipewire, since that's what the task switcher uses for previews.
This issue seems to get solved with following upgrade Start-Date: 2023-03-02 19:23:33 Commandline: apt upgrade Requested-By: marco (1000) Upgrade: breeze:arm64 (4:5.26.90-1, 4:5.27.0-1), kwayland-integration:arm64 (5.26.90-1, 5.27.0-1), libksysguardsensorfaces1:arm64 (4:5.26.90-1, 4:5.27.0-1), plasma-workspace:arm64 (4:5.26.90-1, 4:5.27.0-1), plasma-systemmonitor:arm64 (5.26.90-1, 5.27.0-1), desktop-base:arm64 (12.0.2, 12.0.3), libtss2-tcti-cmd0:arm64 (3.2.1-2, 3.2.1-3), tzdata:arm64 (2022g-5, 2022g-7), libtaskmanager6abi1:arm64 (4:5.26.90-1, 4:5.27.0-1), libkpipewiredmabuf5:arm64 (5.26.90-2, 5.27.0-1), pipewire-pulse:arm64 (0.3.65-2, 0.3.65-3), libtss2-tcti-device0:arm64 (3.2.1-2, 3.2.1-3), kscreen:arm64 (4:5.26.90-1, 4:5.27.0-1), libc-ares2:arm64 (1.18.1-1+b2, 1.18.1-2), libkpipewire5:arm64 (5.26.90-2, 5.27.0-1), libkpipewirerecord5:arm64 (5.26.90-2, 5.27.0-1), libpam-kwallet5:arm64 (5.26.90-1, 5.27.0-1), libavahi-common-data:arm64 (0.8-8, 0.8-9), libksysguardsystemstats1:arm64 (4:5.26.90-1, 4:5.27.0-1), libavahi-core7:arm64 (0.8-8, 0.8-9), systemsettings:arm64 (4:5.26.90-1, 4:5.27.0-1), xdg-desktop-portal-kde:arm64 (5.26.90-1, 5.27.0-1), libweather-ion7:arm64 (4:5.26.90-1, 4:5.27.0-1), libtss2-tcti-swtpm0:arm64 (3.2.1-2, 3.2.1-3), plasma-workspace-wayland:arm64 (4:5.26.90-1, 4:5.27.0-1), kwrited:arm64 (4:5.26.90-1, 4:5.27.0-1), libkf5screen8:arm64 (4:5.26.90-3, 4:5.27.0-1), liboxygenstyleconfig5-5:arm64 (4:5.26.90-1, 4:5.27.0-1), libpowerdevilcore2:arm64 (4:5.26.90-1, 4:5.27.0-1), layer-shell-qt:arm64 (5.26.90-1, 5.27.0-1), libtiff6:arm64 (4.5.0-4, 4.5.0-5), ksystemstats:arm64 (5.26.90-1, 5.27.0-1), libavdevice59:arm64 (7:5.1.2-2, 7:5.1.2-3), ffmpeg:arm64 (7:5.1.2-2, 7:5.1.2-3), avahi-daemon:arm64 (0.8-8, 0.8-9), kde-config-gtk-style:arm64 (4:5.26.90-1, 4:5.27.0-1), kde-style-oxygen-qt5:arm64 (4:5.26.90-1, 4:5.27.0-1), pipewire:arm64 (0.3.65-2, 0.3.65-3), kde-config-screenlocker:arm64 (5.26.90-1, 5.27.0-1), powerdevil:arm64 (4:5.26.90-1, 4:5.27.0-1), libtss2-mu0:arm64 (3.2.1-2, 3.2.1-3), khotkeys:arm64 (4:5.26.90-1, 4:5.27.0-1), mutter-common:arm64 (43.2-6, 43.3-3), libpam-kwallet-common:arm64 (5.26.90-1, 5.27.0-1), plasma-workspace-data:arm64 (4:5.26.90-1, 4:5.27.0-1), libpostproc56:arm64 (7:5.1.2-2, 7:5.1.2-3), plasma-browser-integration:arm64 (5.26.90-1, 5.27.0-1), libprocessui9:arm64 (4:5.26.90-1, 4:5.27.0-1), gawk:arm64 (1:5.1.0-1, 1:5.2.1-2), kwin-style-breeze:arm64 (4:5.26.90-1, 4:5.27.0-1), libkf5screen-bin:arm64 (4:5.26.90-3, 4:5.27.0-1), libfuse3-3:arm64 (3.13.0-2, 3.14.0-2), libkscreenlocker5:arm64 (5.26.90-1, 5.27.0-1), libsnappy1v5:arm64 (1.1.9-2, 1.1.9-3), ksshaskpass:arm64 (4:5.26.90-1, 4:5.27.0-1), plasma-integration:arm64 (5.26.90-1, 5.27.0-1), libavcodec59:arm64 (7:5.1.2-2, 7:5.1.2-3), libspa-0.2-bluetooth:arm64 (0.3.65-2, 0.3.65-3), plasma-disks:arm64 (5.26.90-1, 5.27.0-1), libprocesscore9:arm64 (4:5.26.90-1, 4:5.27.0-1), milou:arm64 (4:5.26.90-1, 4:5.27.0-1), khotkeys-data:arm64 (4:5.26.90-1, 4:5.27.0-1), fuse3:arm64 (3.13.0-2, 3.14.0-2), plasma-nano:arm64 (5.26.90-1, 5.27.0-1), libtss2-tctildr0:arm64 (3.2.1-2, 3.2.1-3), libavutil57:arm64 (7:5.1.2-2, 7:5.1.2-3), liboxygenstyle5-5:arm64 (4:5.26.90-1, 4:5.27.0-1), libtss2-tcti-mssim0:arm64 (3.2.1-2, 3.2.1-3), kde-config-sddm:arm64 (4:5.26.90-1, 4:5.27.0-1), libcolorcorrect5:arm64 (4:5.26.90-1, 4:5.27.0-1), pipewire-bin:arm64 (0.3.65-2, 0.3.65-3), libswscale6:arm64 (7:5.1.2-2, 7:5.1.2-3), libpowerdevilui5:arm64 (4:5.26.90-1, 4:5.27.0-1), plasma-thunderbolt:arm64 (5.26.90-1, 5.27.0-1), plasma-vault:arm64 (5.26.90-1, 5.27.0-1), libavahi-common3:arm64 (0.8-8, 0.8-9), oxygen-sounds:arm64 (4:5.26.90-1, 4:5.27.0-1), kde-style-breeze:arm64 (4:5.26.90-1, 4:5.27.0-1), breeze-cursor-theme:arm64 (4:5.26.90-1, 4:5.27.0-1), plasma-nm:arm64 (4:5.26.90-1, 4:5.27.0-1), plasma-pa:arm64 (4:5.26.90-1, 4:5.27.0-1), breeze-gtk-theme:arm64 (5.26.90-1, 5.27.0-1), libsdl2-2.0-0:arm64 (2.26.2+dfsg-1, 2.26.3+dfsg-1), libtss2-sys1:arm64 (3.2.1-2, 3.2.1-3), liblayershellqtinterface5:arm64 (5.26.90-1, 5.27.0-1), libspa-0.2-modules:arm64 (0.3.65-2, 0.3.65-3), qml-module-org-kde-pipewire:arm64 (5.26.90-2, 5.27.0-1), libavahi-glib1:arm64 (0.8-8, 0.8-9), sudo:arm64 (1.9.12p2-1, 1.9.13p1-1), qml-module-org-kde-qqc2breezestyle:arm64 (5.26.90-1, 5.27.0-1), libswresample4:arm64 (7:5.1.2-2, 7:5.1.2-3), plasma-desktop-data:arm64 (4:5.26.90-1, 4:5.27.0-1), libksgrd9:arm64 (4:5.26.90-1, 4:5.27.0-1), unzip:arm64 (6.0-27, 6.0-28), libgnutls30:arm64 (3.7.8-5, 3.7.9-1), libavformat59:arm64 (7:5.1.2-2, 7:5.1.2-3), polkit-kde-agent-1:arm64 (4:5.26.90-1, 4:5.27.0-1), libnotificationmanager1:arm64 (4:5.26.90-1, 4:5.27.0-1), libkfontinstui5:arm64 (4:5.26.90-1, 4:5.27.0-1), libpipewire-0.3-modules:arm64 (0.3.65-2, 0.3.65-3), libkf5sysguard-data:arm64 (4:5.26.90-1, 4:5.27.0-1), libksysguardformatter1:arm64 (4:5.26.90-1, 4:5.27.0-1), libkfontinst5:arm64 (4:5.26.90-1, 4:5.27.0-1), libtss2-esys-3.0.2-0:arm64 (3.2.1-2, 3.2.1-3), kde-cli-tools-data:arm64 (4:5.26.90-1, 4:5.27.0-1), libplasma-geolocation-interface5:arm64 (4:5.26.90-1, 4:5.27.0-1), liblcms2-2:arm64 (2.14-1+b1, 2.14-2), libksysguardsensors1:arm64 (4:5.26.90-1, 4:5.27.0-1), libavahi-client3:arm64 (0.8-8, 0.8-9), qml-module-org-kde-ksysguard:arm64 (4:5.26.90-1, 4:5.27.0-1), powerdevil-data:arm64 (4:5.26.90-1, 4:5.27.0-1), libkworkspace5-5:arm64 (4:5.26.90-1, 4:5.27.0-1), libkf5screen-data:arm64 (4:5.26.90-3, 4:5.27.0-1), plasma-desktop:arm64 (4:5.26.90-1, 4:5.27.0-1), libkf5screendpms8:arm64 (4:5.26.90-3, 4:5.27.0-1), kde-cli-tools:arm64 (4:5.26.90-1, 4:5.27.0-1), libavfilter8:arm64 (7:5.1.2-2, 7:5.1.2-3), libpipewire-0.3-0:arm64 (0.3.65-2, 0.3.65-3) End-Date: 2023-03-02 19:26:56 Will keep it monitored for a few days more, before closing... Btw, even if pipewire is included in this upgrade, the change is relevant only for install/upgrades, not for its behavior... [1] [1] https://tracker.debian.org/news/1421852/accepted-pipewire-0365-3-source-into-unstable/
It never happened again after the upgrade mentioned in Comment 14: closing.