Odd issue with pipewire/current Manjaro and GPD Pocket 1:
Insertion of headphone jack will successfully toggle to headphones and mute PC speaker.
But upon resume from suspend, the sound defaults to PC speaker, and even reinsertion of headphone jack will no longer toggle to headphones.
Audio mixer says the headphones are unplugged and so far, the only way to rectify things is to manually toggle in Audio mixer/Port between Headphone and Speaker, which will eventually result in “Headphones (plugged in)”
Further complication is in Audio mixer/output devices, the only listing is a combined “Built-in Audio Headphones + Speaker,” so I can’t yet find a terminal command to force the correct toggle.
so first uninstall this leftover: pamac remove pulseaudio-alsa
you are running the 5.18 kernel, which is going to be end of life, so install the 5.19 for example, reboot and try with it
I very much appreciate you sticking with this. I’m now working with 5.10 kernel (which just successfully resumed from its second suspend)
[jake@p1 ~]$ journalctl -b0 -p4 --no-pager
Sep 26 14:31:14 p1 kernel: esrt: ESRT header is not in the memory map.
Sep 26 14:31:14 p1 kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Sep 26 14:31:14 p1 kernel: cherryview-pinctrl: probe of INT33FF:04 failed with error -61
Sep 26 14:31:14 p1 kernel: Expanded resource Reserved due to conflict with PCI Bus 0000:00
Sep 26 14:31:14 p1 kernel: hpet: number irqs doesn't agree with number of timers
Sep 26 14:31:16 p1 kernel: Goodix-TS i2c-GDIX1001:00: supply AVDD28 not found, using dummy regulator
Sep 26 14:31:16 p1 kernel: Goodix-TS i2c-GDIX1001:00: supply VDDIO not found, using dummy regulator
Sep 26 14:31:16 p1 kernel: hci_uart_bcm serial0-0: supply vbat not found, using dummy regulator
Sep 26 14:31:16 p1 kernel: hci_uart_bcm serial0-0: supply vddio not found, using dummy regulator
Sep 26 14:31:16 p1 kernel: rt5645 i2c-10EC5645:00: supply avdd not found, using dummy regulator
Sep 26 14:31:16 p1 kernel: rt5645 i2c-10EC5645:00: supply cpvdd not found, using dummy regulator
Sep 26 14:31:16 p1 kernel: Bluetooth: hci0: BCM: firmware Patch file not found, tried:
Sep 26 14:31:16 p1 kernel: Bluetooth: hci0: BCM: 'brcm/BCM4356A2.hcd'
Sep 26 14:31:16 p1 kernel: Bluetooth: hci0: BCM: 'brcm/BCM.hcd'
Sep 26 14:31:17 p1 kernel: brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4356-pcie for chip BCM4356/2
Sep 26 14:31:17 p1 kernel: brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4356-pcie for chip BCM4356/2
Sep 26 14:31:17 p1 kernel: brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4356/2 wl0: Aug 29 2019 02:05:27 version 7.35.180.197 (r722171 CY) FWID 01-4c8512f9
Sep 26 14:31:18 p1 systemd[506]: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555)
Sep 26 14:31:18 p1 systemd[517]: tuptime.service: Failed to determine user credentials: No such process
Sep 26 14:31:18 p1 systemd[517]: tuptime.service: Failed at step USER spawning /usr/bin/tuptime: No such process
Sep 26 14:31:18 p1 systemd[1]: tuptime.service: Failed with result 'exit-code'.
Sep 26 14:31:18 p1 systemd[1]: Failed to start Tuptime service.
Sep 26 14:31:19 p1 kernel: kauditd_printk_skb: 74 callbacks suppressed
Sep 26 14:31:20 p1 colord[733]: failed to get edid data: EDID length is too small
Sep 26 14:31:23 p1 lightdm[1117]: gkr-pam: no password is available for user
Sep 26 14:31:23 p1 systemd-xdg-autostart-generator[1128]: /home/jake/.config/autostart/Rt_St=Delete.desktop:9: Unknown key name 'RunHook' in section 'Desktop Entry', ignoring.
Sep 26 14:31:23 p1 systemd-xdg-autostart-generator[1128]: /home/jake/.config/autostart/Sound.desktop:9: Unknown key name 'RunHook' in section 'Desktop Entry', ignoring.
Sep 26 14:31:23 p1 systemd-xdg-autostart-generator[1128]: /home/jake/.config/autostart/Calibrate.desktop:9: Unknown key name 'RunHook' in section 'Desktop Entry', ignoring.
Sep 26 14:31:23 p1 systemd-xdg-autostart-generator[1128]: Configuration file /home/jake/.config/autostart/xfce-pbw.sh is marked executable. Please remove executable permission bits. Proceeding anyway.
Sep 26 14:31:23 p1 systemd-xdg-autostart-generator[1128]: /home/jake/.config/autostart/xfce-pbw.sh:2: Assignment outside of section. Ignoring.
Sep 26 14:31:23 p1 systemd-xdg-autostart-generator[1128]: /home/jake/.config/autostart/xfce-pbw.sh:3: Assignment outside of section. Ignoring.
Sep 26 14:31:23 p1 systemd-xdg-autostart-generator[1128]: /home/jake/.config/autostart/xfce-pbw.sh:4: Assignment outside of section. Ignoring.
Sep 26 14:31:23 p1 systemd-xdg-autostart-generator[1128]: /home/jake/.config/autostart/xfce-pbw.sh:5: Assignment outside of section. Ignoring.
Sep 26 14:31:23 p1 systemd-xdg-autostart-generator[1128]: /home/jake/.config/autostart/xfce-pbw.sh:6: Assignment outside of section. Ignoring.
Sep 26 14:31:23 p1 systemd-xdg-autostart-generator[1128]: /home/jake/.config/autostart/xfce-pbw.sh:7: Assignment outside of section. Ignoring.
Sep 26 14:31:23 p1 systemd-xdg-autostart-generator[1128]: /home/jake/.config/autostart/USB Automount.desktop:9: Unknown key name 'RunHook' in section 'Desktop Entry', ignoring.
Sep 26 14:31:23 p1 systemd-xdg-autostart-generator[1128]: /home/jake/.config/autostart/Blank.desktop:9: Unknown key name 'RunHook' in section 'Desktop Entry', ignoring.
Sep 26 14:31:23 p1 systemd-xdg-autostart-generator[1128]: /home/jake/.config/autostart/xcape.desktop:9: Unknown key name 'RunHook' in section 'Desktop Entry', ignoring.
Sep 26 14:31:23 p1 systemd-xdg-autostart-generator[1128]: /home/jake/.config/autostart/Suspend.desktop:9: Unknown key name 'RunHook' in section 'Desktop Entry', ignoring.
Sep 26 14:31:23 p1 systemd-xdg-autostart-generator[1128]: /home/jake/.config/autostart/Login_Rain.desktop:9: Unknown key name 'RunHook' in section 'Desktop Entry', ignoring.
Sep 26 14:31:23 p1 systemd-xdg-autostart-generator[1128]: Configuration file /home/jake/.config/autostart/xfce-panel-workaround.desktop is marked executable. Please remove executable permission bits. Proceeding anyway.
Sep 26 14:31:24 p1 lightdm[1117]: gkr-pam: couldn't unlock the login keyring.
Sep 26 14:31:26 p1 pipewire[1210]: mod.rt: Can't find xdg-portal: (null)
Sep 26 14:31:26 p1 pipewire[1210]: mod.rt: found session bus but no portal
Sep 26 14:31:26 p1 pipewire-pulse[1212]: mod.rt: Can't find xdg-portal: (null)
Sep 26 14:31:26 p1 pipewire-pulse[1212]: mod.rt: found session bus but no portal
Sep 26 14:31:26 p1 kernel: kauditd_printk_skb: 29 callbacks suppressed
Sep 26 14:31:26 p1 pipewire[1210]: mod.rt: RTKit error: org.freedesktop.DBus.Error.AccessDenied
Sep 26 14:31:26 p1 pipewire[1210]: mod.rt: could not make thread 1221 realtime using RTKit: Permission denied
Sep 26 14:31:26 p1 pipewire-pulse[1212]: mod.rt: RTKit error: org.freedesktop.DBus.Error.AccessDenied
Sep 26 14:31:26 p1 pipewire-pulse[1212]: mod.rt: could not make thread 1225 realtime using RTKit: Permission denied
Sep 26 14:31:26 p1 wireplumber[1211]: Failed to set scheduler settings: Operation not permitted
Sep 26 14:31:30 p1 upowerd[1314]: energy_full (29.631000) is greater than energy_full_design (24.055500)
Sep 26 14:31:30 p1 upowerd[1314]: USB power supply /sys/devices/pci0000:00/808622C1:06/i2c-6/i2c-INT34D3:00/cht_wcove_ext_chgr/i2c-7/i2c-bq24190/power_supply/bq24190-charger without usb_type property, please report
Sep 26 14:31:30 p1 tumblerd[1345]: Failed to load plugin "tumbler-gepub-thumbnailer.so": libgepub-0.6.so.0: cannot open shared object file: No such file or directory
Sep 26 14:31:32 p1 kernel: kauditd_printk_skb: 1 callbacks suppressed
Sep 26 14:31:45 p1 kernel: intel_sst_acpi 808622A8:00: sst: Busy wait failed, cant send this msg
Sep 26 14:31:45 p1 kernel: intel_sst_acpi 808622A8:00: sst: Busy wait failed, cant send this msg
Sep 26 14:31:45 p1 pipewire[1210]: spa.alsa: hw:chtrt5645: snd_pcm_avail after recover: Broken pipe
Sep 26 14:32:16 p1 systemd[1589]: tuptime-cron.service: Failed to determine user credentials: No such process
Sep 26 14:32:16 p1 systemd[1589]: tuptime-cron.service: Failed at step USER spawning /usr/bin/tuptime: No such process
Sep 26 14:32:16 p1 systemd[1590]: tuptime.service: Failed to determine user credentials: No such process
Sep 26 14:32:16 p1 systemd[1590]: tuptime.service: Failed at step USER spawning /usr/bin/tuptime: No such process
Sep 26 14:32:16 p1 systemd[1]: tuptime-cron.service: Failed with result 'exit-code'.
Sep 26 14:32:16 p1 systemd[1]: Failed to start Tuptime scheduled execution service.
Sep 26 14:32:16 p1 systemd[1]: tuptime.service: Failed with result 'exit-code'.
Sep 26 14:32:16 p1 systemd[1]: Failed to start Tuptime service.
Sep 26 14:35:29 p1 systemd[1674]: tuptime-cron.service: Failed to determine user credentials: No such process
Sep 26 14:35:29 p1 systemd[1675]: tuptime.service: Failed to determine user credentials: No such process
Sep 26 14:35:29 p1 systemd[1675]: tuptime.service: Failed at step USER spawning /usr/bin/tuptime: No such process
Sep 26 14:35:29 p1 systemd[1674]: tuptime-cron.service: Failed at step USER spawning /usr/bin/tuptime: No such process
Sep 26 14:35:29 p1 systemd[1]: tuptime.service: Failed with result 'exit-code'.
Sep 26 14:35:29 p1 systemd[1]: Failed to start Tuptime service.
Sep 26 14:35:29 p1 systemd[1]: Dependency failed for Tuptime scheduled execution service.
Sep 26 14:35:29 p1 systemd[1]: tuptime-cron.service: Failed with result 'exit-code'.
Sep 26 14:40:30 p1 systemd[1780]: tuptime-cron.service: Failed to determine user credentials: No such process
Sep 26 14:40:30 p1 systemd[1780]: tuptime-cron.service: Failed at step USER spawning /usr/bin/tuptime: No such process
Sep 26 14:40:30 p1 systemd[1781]: tuptime.service: Failed to determine user credentials: No such process
Sep 26 14:40:30 p1 systemd[1781]: tuptime.service: Failed at step USER spawning /usr/bin/tuptime: No such process
Sep 26 14:40:30 p1 systemd[1]: tuptime-cron.service: Failed with result 'exit-code'.
Sep 26 14:40:30 p1 systemd[1]: Failed to start Tuptime scheduled execution service.
Sep 26 14:40:30 p1 systemd[1]: tuptime.service: Failed with result 'exit-code'.
Sep 26 14:40:30 p1 systemd[1]: Failed to start Tuptime service.
Sep 26 16:30:47 p1 kernel: scsi host0: runtime PM trying to activate child device host0 but parent (2-4:1.0) is not active
Sep 26 16:30:47 p1 kernel: scsi target0:0:0: runtime PM trying to activate child device target0:0:0 but parent (host0) is not active
Sep 26 16:30:47 p1 kernel: sd 0:0:0:0: runtime PM trying to activate child device 0:0:0:0 but parent (target0:0:0) is not active
Sep 26 16:30:47 p1 systemd[1912]: tuptime-cron.service: Failed to determine user credentials: No such process
Sep 26 16:30:47 p1 systemd[1912]: tuptime-cron.service: Failed at step USER spawning /usr/bin/tuptime: No such process
Sep 26 16:30:47 p1 systemd[1919]: tuptime.service: Failed to determine user credentials: No such process
Sep 26 16:30:47 p1 systemd[1919]: tuptime.service: Failed at step USER spawning /usr/bin/tuptime: No such process
Sep 26 16:30:47 p1 systemd[1]: tuptime-cron.service: Failed with result 'exit-code'.
Sep 26 16:30:47 p1 systemd[1]: Failed to start Tuptime scheduled execution service.
Sep 26 16:30:47 p1 systemd[1]: tuptime.service: Failed with result 'exit-code'.
Sep 26 16:30:47 p1 systemd[1]: Failed to start Tuptime service.
Sep 26 16:31:00 p1 kernel: intel_sst_acpi 808622A8:00: sst: Busy wait failed, cant send this msg
Sep 26 16:31:45 p1 xdg-desktop-por[2186]: Failed to get application states: GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list
Sep 26 16:35:26 p1 systemd[4007]: tuptime-cron.service: Failed to determine user credentials: No such process
Sep 26 16:35:26 p1 systemd[4008]: tuptime.service: Failed to determine user credentials: No such process
Sep 26 16:35:26 p1 systemd[4008]: tuptime.service: Failed at step USER spawning /usr/bin/tuptime: No such process
Sep 26 16:35:26 p1 systemd[4007]: tuptime-cron.service: Failed at step USER spawning /usr/bin/tuptime: No such process
Sep 26 16:35:26 p1 systemd[1]: tuptime.service: Failed with result 'exit-code'.
Sep 26 16:35:26 p1 systemd[1]: Failed to start Tuptime service.
Sep 26 16:35:26 p1 systemd[1]: Dependency failed for Tuptime scheduled execution service.
Sep 26 16:35:26 p1 systemd[1]: tuptime-cron.service: Failed with result 'exit-code'.
Sep 26 16:39:03 p1 kernel: intel_sst_acpi 808622A8:00: sst: Busy wait failed, cant send this msg
Sep 26 16:40:31 p1 systemd[6500]: tuptime-cron.service: Failed to determine user credentials: No such process
Sep 26 16:40:31 p1 systemd[6500]: tuptime-cron.service: Failed at step USER spawning /usr/bin/tuptime: No such process
Sep 26 16:40:31 p1 systemd[6501]: tuptime.service: Failed to determine user credentials: No such process
Sep 26 16:40:31 p1 systemd[6501]: tuptime.service: Failed at step USER spawning /usr/bin/tuptime: No such process
Sep 26 16:40:31 p1 systemd[1]: tuptime-cron.service: Failed with result 'exit-code'.
Sep 26 16:40:31 p1 systemd[1]: Failed to start Tuptime scheduled execution service.
Sep 26 16:40:31 p1 systemd[1]: tuptime.service: Failed with result 'exit-code'.
Sep 26 16:40:31 p1 systemd[1]: Failed to start Tuptime service.
Sep 26 16:45:08 p1 kernel: intel_sst_acpi 808622A8:00: sst: Busy wait failed, cant send this msg
Sep 26 16:45:31 p1 systemd[9190]: tuptime-cron.service: Failed to determine user credentials: No such process
Sep 26 16:45:31 p1 systemd[9190]: tuptime-cron.service: Failed at step USER spawning /usr/bin/tuptime: No such process
Sep 26 16:45:31 p1 systemd[9191]: tuptime.service: Failed to determine user credentials: No such process
Sep 26 16:45:31 p1 systemd[9191]: tuptime.service: Failed at step USER spawning /usr/bin/tuptime: No such process
Sep 26 16:45:31 p1 systemd[1]: tuptime-cron.service: Failed with result 'exit-code'.
Sep 26 16:45:31 p1 systemd[1]: Failed to start Tuptime scheduled execution service.
Sep 26 16:45:31 p1 systemd[1]: tuptime.service: Failed with result 'exit-code'.
Sep 26 16:45:31 p1 systemd[1]: Failed to start Tuptime service.
Sep 26 16:50:26 p1 systemd[11526]: tuptime-cron.service: Failed to determine user credentials: No such process
Sep 26 16:50:26 p1 systemd[11526]: tuptime-cron.service: Failed at step USER spawning /usr/bin/tuptime: No such process
Sep 26 16:50:26 p1 systemd[11527]: tuptime.service: Failed to determine user credentials: No such process
Sep 26 16:50:26 p1 systemd[11527]: tuptime.service: Failed at step USER spawning /usr/bin/tuptime: No such process
Sep 26 16:50:26 p1 systemd[1]: tuptime-cron.service: Failed with result 'exit-code'.
Sep 26 16:50:26 p1 systemd[1]: Failed to start Tuptime scheduled execution service.
Sep 26 16:50:26 p1 systemd[1]: tuptime.service: Failed with result 'exit-code'.
Sep 26 16:50:26 p1 systemd[1]: Failed to start Tuptime service.
Sep 26 16:55:31 p1 systemd[13526]: tuptime-cron.service: Failed to determine user credentials: No such process
Sep 26 16:55:31 p1 systemd[13526]: tuptime-cron.service: Failed at step USER spawning /usr/bin/tuptime: No such process
Sep 26 16:55:31 p1 systemd[13527]: tuptime.service: Failed to determine user credentials: No such process
Sep 26 16:55:31 p1 systemd[13527]: tuptime.service: Failed at step USER spawning /usr/bin/tuptime: No such process
Sep 26 16:55:31 p1 systemd[1]: tuptime-cron.service: Failed with result 'exit-code'.
Sep 26 16:55:31 p1 systemd[1]: Failed to start Tuptime scheduled execution service.
Sep 26 16:55:31 p1 systemd[1]: tuptime.service: Failed with result 'exit-code'.
Sep 26 16:55:31 p1 systemd[1]: Failed to start Tuptime service.
Sep 26 17:23:58 p1 kernel: scsi host0: runtime PM trying to activate child device host0 but parent (2-4:1.0) is not active
Sep 26 17:23:58 p1 kernel: scsi target0:0:0: runtime PM trying to activate child device target0:0:0 but parent (host0) is not active
Sep 26 17:23:58 p1 kernel: sd 0:0:0:0: runtime PM trying to activate child device 0:0:0:0 but parent (target0:0:0) is not active
Sep 26 17:23:58 p1 systemd[15053]: tuptime-cron.service: Failed to determine user credentials: No such process
Sep 26 17:23:58 p1 systemd[15053]: tuptime-cron.service: Failed at step USER spawning /usr/bin/tuptime: No such process
Sep 26 17:23:58 p1 systemd[15055]: tuptime.service: Failed to determine user credentials: No such process
Sep 26 17:23:58 p1 systemd[15055]: tuptime.service: Failed at step USER spawning /usr/bin/tuptime: No such process
Sep 26 17:23:58 p1 systemd[1]: tuptime-cron.service: Failed with result 'exit-code'.
Sep 26 17:23:58 p1 systemd[1]: Failed to start Tuptime scheduled execution service.
Sep 26 17:23:58 p1 systemd[1]: tuptime.service: Failed with result 'exit-code'.
Sep 26 17:23:58 p1 systemd[1]: Failed to start Tuptime service.
what is that tuptime service? you have a lot of those logs there …
didnt find anything except:
also can you check after suspend if your audio hardware is being detected with: inxi -A
according to the inxi output above it isnt…
and are you dual booting with win? if yes, is fast startup disabled?
I’m so appreciative of your help, but I’m bailing out and I don’t want to waste any more of your time.
I’ve managed to move my machines to Manjaro–from the Chuwi Minibook 8 to Surface Pro6 (with secure boot, even)–but Manjaro and and the GPD Pocket 1 will not play nice.
Not only am I struggling with sound issues (pulseaudio did not connect; pipewire, as you know, presented its own problems), but deeper issues of failures-of-suspend and now repeated blank-screen-upon-boot make me concede. Especially since said problems do not present on other Linux flavors.
Que sera sera–I’m sticking with Manjaro wherever I can, but not here.
Again, I’m so appreciative of your help, but some devices are apparently not meant for Manjaro.