I can't reproduce it locally on Fedora, but I found a potential issue with undefined behavior, could you please see if you can try https://invent.kde.org/plasma-mobile/plasma-settings/-/merge_requests/150

I see a lot of org.kde.breeze being missing, are you sure qqc2-breeze-style is installed? It should be a hard dependency of plasma-mobile

Do you have the full log? I think it's unlikely org.kde.breeze wouldn't be found if qqc2-breeze-style is installed

No landscape/portrait switch (does plasma-mobile suppose that?)

The quicksetting is only for turning on/off auto-rotate if that's supported on the device (through iio-sensor-proxy). Otherwise switching between landscape/portrait needs to be done through Settings -> Display

Stopping the service indeed does appear to fix it

I've been able to now reproduce it in Phosh too pretty reliably:

1. Use the phone for a bit
2. Run sudo loginctl suspend over ssh
3. Wake the phone and use it for a few seconds, then it locks up

I have plasma mobile also installed on the drive during this test as well, I will try again tomorrow with a fresh flash to check if this issue occurs.

I spoke too soon, it's probably not related to iio-sensor-proxy since I disabled the service and still get system lockup a few seconds after waking from suspend with these logs:

[Jul 27 00:35:22] daemon dbus-daemon[1796]: [system] Activating service name='org.freedesktop.nm_dispatcher' requested by ':1.3' (uid=0 pid=2006 comm="/usr/sbin/NetworkManager -n") (using servicehelper) 
[Jul 27 00:35:22] daemon dbus-daemon[1796]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' 
[Jul 27 00:35:23] daemon supervise-daemon[4990]: Child command line: /usr/bin/hexagonrpcd -f /dev/fastrpc-adsp -d adsp -s -R /usr/share/qcom/sdm670/Google/sargo  
[Jul 27 00:35:23] daemon supervise-daemon[1020]: /usr/bin/hexagonrpcd, pid 4990, exited with return code 4 
[Jul 27 00:35:25] user pulseaudio[3804]: [pulseaudio] alsa-ucm.c: Failed to set verb HiFi 
[Jul 27 00:35:25] user pulseaudio[3804]: [pulseaudio] udev-util.c: Failed to get card object. 
[Jul 27 00:35:25] user pulseaudio[3804]: [pulseaudio] module-alsa-card.c: Failed to find a working profile. 
[Jul 27 00:35:25] user pulseaudio[3804]: [pulseaudio] module.c: Failed to load module "module-alsa-card" (argument: "device_id="0" name="platform-sound" card_name="alsa_card.platform-sound" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes avoid_resampling=no card_properties="module-udev-detect.discovered=1""): initialization failed. 
[Jul 27 00:35:25] daemon supervise-daemon[5003]: Child command line: /usr/bin/hexagonrpcd -f /dev/fastrpc-adsp -d adsp -s -R /usr/share/qcom/sdm670/Google/sargo

I followed logs with logread, and here are the final logs before the system freezes:

[Jul 27 00:28:17] daemon supervise-daemon[1019]: /usr/bin/hexagonrpcd, pid 7911, exited with return code 4 
[Jul 27 00:28:17] daemon supervise-daemon[7913]: Child command line: /usr/libexec/iio-sensor-proxy  
[Jul 27 00:28:17] daemon supervise-daemon[2734]: /usr/libexec/iio-sensor-proxy, pid 7913, exited with return code 0 
[Jul 27 00:28:18] user pulseaudio[5269]: [pulseaudio] alsa-ucm.c: Failed to set verb HiFi 
[Jul 27 00:28:18] user pulseaudio[5269]: [pulseaudio] udev-util.c: Failed to get card object. 
[Jul 27 00:28:18] user pulseaudio[5269]: [pulseaudio] module-alsa-card.c: Failed to find a working profile. 
[Jul 27 00:28:18] user pulseaudio[5269]: [pulseaudio] module.c: Failed to load module "module-alsa-card" (argument: "device_id="0" name="platform-sound" card_name="alsa_card.platform-sound" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes avoid_resampling=no card_properties="module-udev-detect.discovered=1""): initialization failed. 
[Jul 27 00:28:19] daemon supervise-daemon[7924]: Child command line: /usr/bin/hexagonrpcd -f /dev/fastrpc-adsp -d adsp -s -R /usr/share/qcom/sdm670/Google/sargo  
[Jul 27 00:28:19] daemon supervise-daemon[1019]: /usr/bin/hexagonrpcd, pid 7924, exited with return code 4 
[Jul 27 00:28:19] daemon supervise-daemon[2734]: /usr/libexec/iio-sensor-proxy, pid 7944, terminated by signal 11 <<<<<<<<

Perhaps it has something to do with the sensors that got enabled recently? Since iio-sensor-proxy segfaults

Describe your issue

The entire Pixel 3a appears to lockup and stop responding after some amount of usage. I can't reliably figure out a way to trigger the lock up, but I have observed it to happen sometimes coming back from suspend (after about a few seconds where it works), on a fresh boot after a few minutes, launching apps, etc.

Of note is that this appears to have started happening in the past two weeks on edge. I don't experience this issue on v24.06. It makes me suspect some package update recently may have caused it.

I could only so far trigger this with Plasma Mobile, I am not sure if it's a Plasma issue or it's exacerbated by Plasma's heavier use of the GPU over other DEs (UPDATE: I just experienced this issue while in gdm, not logged into any session so it's probably not Plasma specific). Of note is that I only encounter this lockup issue on the Pixel 3a specifically, and not on my OnePlus 6.

What's the expected behaviour?

The device does not lockup.

What's the current behaviour?

After some usage, the entire device locks up, with even SSH being unresponsive. I can't switch to the TTY either.

How to reproduce your issue?

Use the device for a bit with Plasma Mobile, and you will probably experience it.

What device are you using?

google-sargo

On what postmarketOS version did you encounter the issue?

• edge (master branch)

• v24.06

• v23.12 (supported until 2024-07-16)

• 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)

2024-07-25

Additional information

Please let me know what sort of logs I can get to help debug this issue.

espidev (2d449db3) at 22 Jul 06:31

Thanks!

espidev (774689b0) at 22 Jul 04:03

espidev (708b526f) at 22 Jul 00:20

It's currently hardcoded to Qt5 even if we are only building against Qt 6.

This now switches uses the correct version depending on what it's built against.

espidev (ec06a65b) at 22 Jul 00:16

This is actually the intended behaviour of that settings module, it only shows connections that have already been added (and has the option of manually adding connections). You probably want to use Wi-Fi tray button on the panel to the bottom right.

espidev (7e08e7fe) at 09 Apr 17:34

6.0.3.1 is released now