Plexamp crashing?

Hello Garuda forum friends,

I use plexamp as my desktop music player, and have been using it on Garuda for about a year, originally installed via

paru plexamp-appimage

AUR (en) - plexamp-appimage

Additional information that i am not sure is relevant: plexamp knows it’s a version behind (4.12 on AUR vs 4.13 from the official site) and the app tries to update itself with a new appimage when it closes, which isn’t allowed. I don’t think this is important, because whatever error causes plexamp to erroneously shutdown surely isn’t related to it trying (and expectedly failing) to get a new version post-shutdown – but you will see lines in the journalctl showing how it tries to update.

Starting today, Plexamp’s been crashing on me without warning a few minutes after I launch it.
journalctl says all this about it:

> Nov 03 14:11:23 veltas-prime kernel: plexamp[19816]: segfault at 0 ip 0000000000000000 sp 00007ffe0c8fe8a8 error 14 likely on CPU 9 (core >
> Nov 03 14:11:23 veltas-prime kernel: Code: Unable to access opcode bytes at 0xffffffffffffffd6.
> Nov 03 14:11:23 veltas-prime systemd-coredump[26638]: Process 19816 (plexamp) of user 1000 terminated abnormally with signal 11/SEGV, proc>
> Nov 03 14:11:23 veltas-prime systemd[1]: Created slice Slice /system/systemd-coredump.
> Nov 03 14:11:23 veltas-prime systemd[1]: Started Process Core Dump (PID 26638/UID 0).
> Nov 03 14:11:24 veltas-prime systemd-coredump[26639]: [🡕] **Process 19816 (plexamp) of user 1000 dumped core.**
>
>
>
> **Module libnxegl.so without build-id.**
> **Stack trace of thread 19816:**
> **#0 0x0000000000000000 n/a (n/a + 0x0)**
> **#1 0x00005590f6582b5d n/a (/tmp/.mount_PlexamDWTIQ7/plexamp + 0x3248b5d)**
> **#2 0x00005590f6582840 n/a (/tmp/.mount_PlexamDWTIQ7/plexamp + 0x3248840)**
> **#3 0x00005590f653460e n/a (/tmp/.mount_PlexamDWTIQ7/plexamp + 0x31fa60e)**
> **#4 0x00005590f65341fe n/a (/tmp/.mount_PlexamDWTIQ7/plexamp + 0x31fa1fe)**
> **#5 0x00005590fa0f76a1 n/a (/tmp/.mount_PlexamDWTIQ7/plexamp + 0x6dbd6a1)**
> **#6 0x00005590f64c400b n/a (/tmp/.mount_PlexamDWTIQ7/plexamp + 0x318a00b)**
> **#7 0x00005590fcd2cb8c n/a (/tmp/.mount_PlexamDWTIQ7/plexamp + 0x99f2b8c)**
> **#8 0x00005590f90829dd n/a (/tmp/.mount_PlexamDWTIQ7/plexamp + 0x5d489dd)**
> **#9 0x00005590f909e371 n/a (/tmp/.mount_PlexamDWTIQ7/plexamp + 0x5d64371)**
> **#10 0x00005590f909e985 n/a (/tmp/.mount_PlexamDWTIQ7/plexamp + 0x5d64985)**
> **#11 0x00005590f90fdbae n/a (/tmp/.mount_PlexamDWTIQ7/plexamp + 0x5dc3bae)**
> **#12 0x00007f2cc3906f8d n/a (libglib-2.0.so.0 + 0x5ef8d)**
> **#13 0x00007f2cc3908657 n/a (libglib-2.0.so.0 + 0x60657)**
> **#14 0x00007f2cc3908865 g_main_context_iteration (libglib-2.0.so.0 + 0x60865)**
> **#15 0x00005590f90fd255 n/a (/tmp/.mount_PlexamDWTIQ7/plexamp + 0x5dc3255)**
> **#16 0x00005590f909f0e5 n/a (/tmp/.mount_PlexamDWTIQ7/plexamp + 0x5d650e5)**
> **#17 0x00005590f906460a n/a (/tmp/.mount_PlexamDWTIQ7/plexamp + 0x5d2a60a)**
> **#18 0x00005590fcc57d13 n/a (/tmp/.mount_PlexamDWTIQ7/plexamp + 0x991dd13)**
> **#19 0x00005590f5b287fb n/a (/tmp/.mount_PlexamDWTIQ7/plexamp + 0x27ee7fb)**
> **#20 0x00005590f5b294a9 n/a (/tmp/.mount_PlexamDWTIQ7/plexamp + 0x27ef4a9)**
> **#21 0x00005590f5b2a914 n/a (/tmp/.mount_PlexamDWTIQ7/plexamp + 0x27f0914)**
> **#22 0x00005590f5b2812d n/a (/tmp/.mount_PlexamDWTIQ7/plexamp + 0x27ee12d)**
> **#23 0x00005590f5b28236 n/a (/tmp/.mount_PlexamDWTIQ7/plexamp + 0x27ee236)**
> **#24 0x00005590f5812469 n/a (/tmp/.mount_PlexamDWTIQ7/plexamp + 0x24d8469)**
> **#25 0x00007f2cc2427675 n/a (libc.so.6 + 0x27675)**
> **#26 0x00007f2cc2427729 __libc_start_main (libc.so.6 + 0x27729)**
> **#27 0x00005590f541c02a n/a (/tmp/.mount_PlexamDWTIQ7/plexamp + 0x20e202a)**
> **ELF object binary architecture: AMD x86-64**
> Nov 03 14:11:24 veltas-prime systemd[1]: systemd-coredump@0-1-26638_26639-0.service: Deactivated successfully.
> Nov 03 14:11:24 veltas-prime systemd[1]: systemd-coredump@0-1-26638_26639-0.service: Consumed 555ms CPU time, 509.4M memory peak.
> Nov 03 14:11:24 veltas-prime env[19426]: [19426:1103/141124.115120:ERROR:gpu_process_host.cc(993)] GPU process exited unexpectedly: exit_c>
> Nov 03 14:11:24 veltas-prime env[19426]: Error: GPU process (undefined) crashed (139) :frowning:
> Nov 03 14:11:24 veltas-prime env[19426]: Quitting…
> Nov 03 14:11:24 veltas-prime env[26647]: WARNING: radv is not a conformant Vulkan implementation, testing use only.
> Nov 03 14:11:24 veltas-prime env[19426]: Auto install update on quit
> Nov 03 14:11:24 veltas-prime env[19426]: Install: isSilent: true, isForceRunAfter: false
> Nov 03 14:11:24 veltas-prime env[19426]: Error: Error: EACCES: permission denied, unlink ‘/usr/bin/Plexamp.AppImage’
> Nov 03 14:11:24 veltas-prime env[19426]: at unlinkSync (node:fs:1883:3)
> Nov 03 14:11:24 veltas-prime env[19426]: at h.doInstall (/tmp/.mount_PlexamDWTIQ7/resources/app.asar/main.js:2:191563)
> Nov 03 14:11:24 veltas-prime env[19426]: at h.install (/tmp/.mount_PlexamDWTIQ7/resources/app.asar/main.js:2:204010)
> Nov 03 14:11:24 veltas-prime env[19426]: at /tmp/.mount_PlexamDWTIQ7/resources/app.asar/main.js:2:204446
> Nov 03 14:11:24 veltas-prime env[19426]: at App. (/tmp/.mount_PlexamDWTIQ7/resources/app.asar/main.js:2:209854)
> Nov 03 14:11:24 veltas-prime env[19426]: at Object.onceWrapper (node:events:632:26)
> Nov 03 14:11:24 veltas-prime env[19426]: at App.emit (node:events:529:35)
> Nov 03 14:11:24 veltas-prime systemd[1]: tmp-.mount_PlexamDWTIQ7.mount: Deactivated successfully.
> Nov 03 14:11:24 veltas-prime systemd[3597]: **app-plexamp@eec1b11bf5b44959b8ee3bc56d90d7ee.service: Consumed 10.384s CPU time, 803.3M memory**>
> Nov 03 14:11:44 veltas-prime rtkit-daemon[6443]: Supervising 3 threads of 3 processes of 1 users.

From the journalctl excerpt above, the line that stands out to my untrained eyes is
terminated abnormally with signal 11/SEGV
I found the following web pages describing Signal 11 -

https://www.liquidweb.com/blog/signal11/

I am not really sure how to proceed with troubleshooting… could it really be a hardware issue with my RAM? Plexamp is the only thing I’ve seen crash, and only today. Maybe some library issue? I’m not sure what I am guessing at.

The other line from journalctl above that has me curious is about the gpu crash?

Nov 03 14:11:24 veltas-prime env[19426]: [19426:1103/141124.115120:ERROR:gpu_process_host.cc(993)] GPU process exited unexpectedly: exit_c>
Nov 03 14:11:24 veltas-prime env[19426]: Error: GPU process (undefined) crashed (139) :frowning:

I’m not sure if that is indicating some additional or root problem with the GPU or if this is just a natural subsequent outcome of the preceding plexamp crash…

Exit Code 139 Explained: Common Causes and How to Fix It this page seems to suggest that the 139 exit code on the GPU process happens because of the earlier segmentation fault, so I guess the gpu crash is not a problem, plexamp crashing is the root cause and this is a side effect?

What do you all think?

As is tradition, I include my inxi output as well:

System:
> Kernel: 6.17.6-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 15.2.1 clocksource: tsc
> avail: hpet,acpi_pm parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
> root=UUID=066c8b02-56dc-42d3-9c15-b57c1602f35e rw rootflags=subvol=@ quiet loglevel=3
> Desktop: KDE Plasma v: 6.5.1 tk: Qt v: N/A info: frameworks v: 6.19.0 wm: kwin_wayland vt: 1
> dm: SDDM Distro: Garuda base: Arch Linux
> Machine:
> Type: Desktop System: ASUS product: N/A v: N/A serial: 
> Mobo: ASUSTeK model: ROG STRIX X670E-A GAMING WIFI v: Rev 1.xx serial: 
> part-nu: SKU uuid:  UEFI: American Megatrends v: 1415 date: 05/16/2023
> Battery:
> Device-1: ps-controller-battery-d0:bc:c1:f4:6e:0b model: N/A serial: N/A charge: N/A status: full
> CPU:
> Info: model: AMD Ryzen 9 7950X3D bits: 64 type: MT MCP arch: Zen 4 gen: 4 level: v4 note: check
> built: 2022+ process: TSMC n5 (5nm) family: 0x19 (25) model-id: 0x61 (97) stepping: 2
> microcode: 0xA60120A
> Topology: cpus: 1x dies: 2 clusters: 2x1 cores: 16 threads: 32 tpc: 2 smt: enabled cache:
> L1: 1024 KiB desc: d-16x32 KiB; i-16x32 KiB L2: 16 MiB desc: 16x1024 KiB L3: 128 MiB
> desc: 1x32 MiB, 1x96 MiB
> Speed (MHz): avg: 4695 min/max: 417/5763 boost: enabled scaling: driver: amd-pstate-epp
> governor: powersave cores: 1: 4695 2: 4695 3: 4695 4: 4695 5: 4695 6: 4695 7: 4695 8: 4695
> 9: 4695 10: 4695 11: 4695 12: 4695 13: 4695 14: 4695 15: 4695 16: 4695 17: 4695 18: 4695
> 19: 4695 20: 4695 21: 4695 22: 4695 23: 4695 24: 4695 25: 4695 26: 4695 27: 4695 28: 4695
> 29: 4695 30: 4695 31: 4695 32: 4695 bogomips: 268803
> Flags-basic: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
> Vulnerabilities: 
> Graphics:
> Device-1: Advanced Micro Devices \[AMD/ATI\] Navi 48 \[Radeon RX 9070/9070 XT/9070 GRE\] vendor: XFX
> driver: amdgpu v: kernel arch: RDNA-4 code: Navi-4x process: TSMC n4 (4nm) built: 2025+ pcie:
> gen: 5 speed: 32 GT/s lanes: 16 ports: active: DP-1,DP-2 empty: DP-3,HDMI-A-1,Writeback-1
> bus-ID: 03:00.0 chip-ID: 1002:7550 class-ID: 0300
> Display: wayland server: X.org v: 1.21.1.20 with: Xwayland v: 24.1.9 compositor: kwin_wayland
> driver: X: loaded: amdgpu unloaded: modesetting,radeon alternate: fbdev,vesa dri: radeonsi
> gpu: amdgpu d-rect: 3440x2880 display-ID: 0
> Monitor-1: DP-1 pos: bottom model: Dell AW3423DWF serial:  built: 2023 res:
> mode: 3440x1440 hz: 100 scale: 100% (1) dpi: 109 gamma: 1.2 size: 800x337mm (31.5x13.27")
> diag: 868mm (34.2") modes: max: 3440x1440 min: 720x400
> Monitor-2: DP-2 pos: primary,top model: Dell AW3418DW serial:  built: 2017 res:
> mode: 3440x1440 hz: 100 scale: 100% (1) dpi: 109 gamma: 1.2 size: 798x335mm (31.42x13.19")
> diag: 865mm (34.1") modes: max: 3440x1440 min: 640x480
> API: EGL v: 1.5 platforms: device: 1 drv: swrast gbm: drv: kms_swrast surfaceless: drv: swrast
> wayland: drv: swrast x11: drv: swrast inactive: device-0
> API: OpenGL v: 4.5 vendor: mesa v: 25.2.6-arch1.1 glx-v: 1.4 direct-render: yes
> renderer: llvmpipe (LLVM 21.1.4 256 bits) device-ID: ffffffff:ffffffff memory: 61.05 GiB
> unified: yes display-ID: :1.0
> API: Vulkan v: 1.4.328 layers: 9 device: 0 type: cpu name: llvmpipe (LLVM 21.1.4 256 bits)
> driver: mesa llvmpipe v: 25.2.6-arch1.1 (LLVM 21.1.4) device-ID: 10005:0000 surfaces: N/A
> Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo de: kscreen-console,kscreen-doctor
> gpu: lact wl: wayland-info x11: xdpyinfo, xprop, xrandr
> Audio:
> Device-1: Advanced Micro Devices \[AMD/ATI\] Navi 48 HDMI/DP Audio driver: snd_hda_intel v: kernel
> pcie: gen: 5 speed: 32 GT/s lanes: 16 bus-ID: 03:00.1 chip-ID: 1002:ab40 class-ID: 0403
> Device-2: XMOS Eversolo DAC-Z8 driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 2.0
> speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-1:2 chip-ID: 20b1:30fd class-ID: 0300
> Device-3: Kingston HyperX QuadCast driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 1.1
> speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-2:3 chip-ID: 0951:16df class-ID: 0300
> serial: 
> Device-4: Sony DualSense wireless controller (PS5) driver: playstation,snd-usb-audio,usbhid
> type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-4:4 chip-ID: 054c:0ce6
> class-ID: 0300
> Device-5: Walmart AB13X Headset Adapter driver: hid-generic,snd-usb-audio,usbhid type: USB
> rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 3-5.4:7 chip-ID: 001f:0b21 class-ID: 0300
> serial: 
> API: ALSA v: k6.17.6-zen1-1-zen status: kernel-api tools: N/A
> Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
> Server-2: PipeWire v: 1.4.9 status: active with: 1: pipewire-pulse status: active
> 2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
> tools: pactl,pw-cat,pw-cli,wpctl
> Network:
> Device-1: MEDIATEK MT7922 802.11ax PCI Express Wireless Network Adapter vendor: Foxconn
> driver: mt7921e v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1 bus-ID: 0b:00.0 chip-ID: 14c3:0616
> class-ID: 0280
> IF: wlp11s0 state: down mac: 
> Device-2: Intel Ethernet I225-V vendor: ASUSTeK driver: igc v: kernel pcie: gen: 2
> speed: 5 GT/s lanes: 1 port: N/A bus-ID: 0c:00.0 chip-ID: 8086:15f3 class-ID: 0200
> IF: eno1 state: up speed: 1000 Mbps duplex: full mac: 
> Device-3: Sony DualSense wireless controller (PS5) driver: playstation,snd-usb-audio,usbhid
> type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-4:4 chip-ID: 054c:0ce6
> class-ID: 0300
> Device-4: Realtek RTL8153 Gigabit Ethernet Adapter driver: r8152 type: USB rev: 3.2
> speed: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 bus-ID: 4-5.3:4 chip-ID: 0bda:8153 class-ID: 0000
> serial: 
> IF: enp18s0u5u3 state: up speed: 1000 Mbps duplex: full mac: 
> Info: services: NetworkManager,systemd-timesyncd
> Bluetooth:
> Device-1: Foxconn / Hon Hai Wireless_Device driver: btusb v: 0.8 type: USB rev: 2.1
> speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-9:5 chip-ID: 0489:e0e2 class-ID: e001
> serial: 
> Report: btmgmt ID: hci0 rfk-id: 0 state: up address:  bt-v: 5.2 lmp-v: 11 status:
> discoverable: no pairing: no class-ID: 6c0104
> Drives:
> Local Storage: total: 4.55 TiB used: 1.44 TiB (31.6%)
> SMART Message: Unable to run smartctl. Root privileges required.
> ID-1: /dev/nvme0n1 maj-min: 259:2 vendor: Samsung model: SSD 960 EVO 1TB size: 931.51 GiB
> block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: 
> fw-rev: 3B7QCXE7 temp: 43.9 C scheme: GPT
> ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: Samsung model: SSD 980 PRO 2TB size: 1.82 TiB
> block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 tech: SSD serial: 
> fw-rev: 5B2QGXA7 temp: 33.9 C scheme: GPT
> ID-3: /dev/nvme2n1 maj-min: 259:1 vendor: Samsung model: SSD 980 PRO 2TB size: 1.82 TiB
> block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 tech: SSD serial: 
> fw-rev: 5B2QGXA7 temp: 33.9 C scheme: GPT
> Partition:
> ID-1: / raw-size: 931.22 GiB size: 931.22 GiB (100.00%) used: 177.54 GiB (19.1%) fs: btrfs
> dev: /dev/nvme0n1p2 maj-min: 259:6
> ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%) used: 664 KiB (0.2%) fs: vfat
> dev: /dev/nvme0n1p1 maj-min: 259:5
> ID-3: /home raw-size: 931.22 GiB size: 931.22 GiB (100.00%) used: 177.54 GiB (19.1%) fs: btrfs
> dev: /dev/nvme0n1p2 maj-min: 259:6
> ID-4: /var/log raw-size: 931.22 GiB size: 931.22 GiB (100.00%) used: 177.54 GiB (19.1%)
> fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:6
> ID-5: /var/tmp raw-size: 931.22 GiB size: 931.22 GiB (100.00%) used: 177.54 GiB (19.1%)
> fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:6
> Swap:
> Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
> ID-1: swap-1 type: zram size: 62.51 GiB used: 0 KiB (0.0%) priority: 100 comp: zstd
> avail: lzo-rle,lzo,lz4,lz4hc,deflate,842 dev: /dev/zram0
> Sensors:
> System Temperatures: cpu: 47.6 C mobo: 40.2 C gpu: amdgpu temp: 44.0 C mem: 44.0 C
> Fan Speeds (rpm): N/A gpu: amdgpu fan: 0
> Info:
> Memory: total: 64 GiB available: 62.51 GiB used: 6.73 GiB (10.8%)
> Processes: 576 Power: uptime: 11m states: freeze,mem,disk suspend: deep avail: s2idle
> wakeups: 0 hibernate: platform avail: shutdown, reboot, suspend, test_resume image: 24.97 GiB
> services: org_kde_powerdevil, power-profiles-daemon, upowerd Init: systemd v: 258
> default: graphical tool: systemctl
> Packages: pm: pacman pkgs: 1342 libs: 356 tools: octopi,paru pm: rpm pkgs: 0 Compilers:
> clang: 21.1.4 gcc: 15.2.1 Client: Unknown Client: electron inxi: 3.3.39
> Garuda (2.11.1-1):
> System install date:     2025-05-28
> Garuda release:          250308
> Last full system update: 2025-11-03
> Is partially upgraded:   No
> Relevant software:       snapper NetworkManager dracut garuda-hardware-profile-standard garuda-hardware-profile-standard-x11
> Windows dual boot:       No/Undetected
> Failed units:
> — System Health Check Report —
> 24/25 checks run in 0.78 seconds ⌛
> Powered by garuda-health 🦅
>
> ✅ System health check passed. No issues found.

Please, next time

  • Format terminal output (including your garuda-inxi) as a code block by clicking the preformatted text button (</>) , or put three tildes (~) above and below the text
3 Likes

sorry - I think I mistook the quotes for that format. Thank you for editing the post to comply.

1 Like

Question, have you tried executing the .AppImage package directly without installing the package? Does that terminate unexpectedly as well? You should be able to launch the AppImage file and it will give you the option to “Run once”.

1 Like

I will try this.

I see plexamp.appimage at /usr/bin/plexamp.appimage

I’ve run it now by executing that file directly, enjoying some tunes – and after a couple minutes it closed/crashed just like before.

Here’s the newest journalctl output from this experiment:

Nov 03 14:44:52 veltas-prime systemd-coredump[134948]: Process 128584 (plexamp) of user 1000 terminated abnormally with signal 11/SEGV, pr>
Nov 03 14:44:52 veltas-prime systemd[1]: Started Process Core Dump (PID 134948/UID 0).
Nov 03 14:44:53 veltas-prime systemd-coredump[134949]: [🡕] Process 128584 (plexamp) of user 1000 dumped core.

Module libnxegl.so without build-id.
Stack trace of thread 128584:
#0  0x0000000000000000 n/a (n/a + 0x0)
#1  0x00005607ed389b5d n/a (/tmp/.mount_PlexamawndL1/plexamp + 0x3248b5d)
#2  0x00005607ed389840 n/a (/tmp/.mount_PlexamawndL1/plexamp + 0x3248840)
#3  0x00005607ed33b60e n/a (/tmp/.mount_PlexamawndL1/plexamp + 0x31fa60e)
#4  0x00005607ed33b1fe n/a (/tmp/.mount_PlexamawndL1/plexamp + 0x31fa1fe)
#5  0x00005607f0efe6a1 n/a (/tmp/.mount_PlexamawndL1/plexamp + 0x6dbd6a1)
#6  0x00005607ed2cb00b n/a (/tmp/.mount_PlexamawndL1/plexamp + 0x318a00b)
#7  0x00005607f3b33b8c n/a (/tmp/.mount_PlexamawndL1/plexamp + 0x99f2b8c)
#8  0x00005607efe899dd n/a (/tmp/.mount_PlexamawndL1/plexamp + 0x5d489dd)
#9  0x00005607efea5371 n/a (/tmp/.mount_PlexamawndL1/plexamp + 0x5d64371)
#10 0x00005607efea5985 n/a (/tmp/.mount_PlexamawndL1/plexamp + 0x5d64985)
#11 0x00005607eff04bae n/a (/tmp/.mount_PlexamawndL1/plexamp + 0x5dc3bae)
#12 0x00007f4dc0f06f8d n/a (libglib-2.0.so.0 + 0x5ef8d)
#13 0x00007f4dc0f08657 n/a (libglib-2.0.so.0 + 0x60657)
#14 0x00007f4dc0f08865 g_main_context_iteration (libglib-2.0.so.0 + 0x60865)
#15 0x00005607eff04255 n/a (/tmp/.mount_PlexamawndL1/plexamp + 0x5dc3255)
#16 0x00005607efea60e5 n/a (/tmp/.mount_PlexamawndL1/plexamp + 0x5d650e5)
#17 0x00005607efe6b60a n/a (/tmp/.mount_PlexamawndL1/plexamp + 0x5d2a60a)
#18 0x00005607f3a5ed13 n/a (/tmp/.mount_PlexamawndL1/plexamp + 0x991dd13)
#19 0x00005607ec92f7fb n/a (/tmp/.mount_PlexamawndL1/plexamp + 0x27ee7fb)
#20 0x00005607ec9304a9 n/a (/tmp/.mount_PlexamawndL1/plexamp + 0x27ef4a9)
#21 0x00005607ec931914 n/a (/tmp/.mount_PlexamawndL1/plexamp + 0x27f0914)
#22 0x00005607ec92f12d n/a (/tmp/.mount_PlexamawndL1/plexamp + 0x27ee12d)
#23 0x00005607ec92f236 n/a (/tmp/.mount_PlexamawndL1/plexamp + 0x27ee236)
#24 0x00005607ec619469 n/a (/tmp/.mount_PlexamawndL1/plexamp + 0x24d8469)
#25 0x00007f4dbfa27675 n/a (libc.so.6 + 0x27675)
#26 0x00007f4dbfa27729 __libc_start_main (libc.so.6 + 0x27729)
#27 0x00005607ec22302a n/a (/tmp/.mount_PlexamawndL1/plexamp + 0x20e202a)
ELF object binary architecture: AMD x86-64
Nov 03 14:44:53 veltas-prime systemd[1]: systemd-coredump@1-4097-134948_134949-0.service: Deactivated successfully.
Nov 03 14:44:53 veltas-prime systemd[1]: systemd-coredump@1-4097-134948_134949-0.service: Consumed 559ms CPU time, 492.3M memory peak.
Nov 03 14:44:53 veltas-prime Plexamp.AppImage[127237]: [127237:1103/144453.148401:ERROR:gpu_process_host.cc(993)] GPU process exited unexp>
Nov 03 14:44:53 veltas-prime Plexamp.AppImage[127237]: Error: GPU process (undefined) crashed (139) :(
Nov 03 14:44:53 veltas-prime Plexamp.AppImage[127237]: Quitting...
Nov 03 14:44:53 veltas-prime Plexamp.AppImage[134956]: WARNING: radv is not a conformant Vulkan implementation, testing use only.
Nov 03 14:44:53 veltas-prime Plexamp.AppImage[127237]: Auto install update on quit
Nov 03 14:44:53 veltas-prime Plexamp.AppImage[127237]: Install: isSilent: true, isForceRunAfter: false
Nov 03 14:44:53 veltas-prime Plexamp.AppImage[127237]: Error: Error: EACCES: permission denied, unlink '/usr/bin/Plexamp.AppImage'
Nov 03 14:44:53 veltas-prime Plexamp.AppImage[127237]:     at unlinkSync (node:fs:1883:3)
Nov 03 14:44:53 veltas-prime Plexamp.AppImage[127237]:     at h.doInstall (/tmp/.mount_PlexamawndL1/resources/app.asar/main.js:2:191563)
Nov 03 14:44:53 veltas-prime Plexamp.AppImage[127237]:     at h.install (/tmp/.mount_PlexamawndL1/resources/app.asar/main.js:2:204010)
Nov 03 14:44:53 veltas-prime Plexamp.AppImage[127237]:     at /tmp/.mount_PlexamawndL1/resources/app.asar/main.js:2:204446
Nov 03 14:44:53 veltas-prime Plexamp.AppImage[127237]:     at App.<anonymous> (/tmp/.mount_PlexamawndL1/resources/app.asar/main.js:2:20985>
Nov 03 14:44:53 veltas-prime Plexamp.AppImage[127237]:     at Object.onceWrapper (node:events:632:26)
Nov 03 14:44:53 veltas-prime Plexamp.AppImage[127237]:     at App.emit (node:events:529:35)
Nov 03 14:44:53 veltas-prime systemd[1]: tmp-.mount_PlexamawndL1.mount: Deactivated successfully.
Nov 03 14:44:53 veltas-prime systemd[3597]: app-\x2fusr\x2fbin\x2fPlexamp.AppImage@c6d4e21328754567b1b93bbb9db2cf06.service: Consumed 8.82>

I have another thought that occurred to me.

The journalCTLs for the coredump mention: Module libnxegl.so without build-id
That sounds very specific doesnt it?

I use Nomachine to remote into a few other devices in my home network nomachine · main · Chaotic-AUR / PKGBUILDs · GitLab

I noticed this morning it prompted me to update it.

searching the net for libnxegl.so …

I wonder if this might be part of my culprit.

I just now went into NoMachine’s settings and disabled its “check for updates” or “apply updates” options. I figure i should never let it update itself, and should only let garuda-update pull an updated package when appropriate.

Then in my terminal I did a

sudo pacman -S -yy nomachine

as I understand from what i’ve read of pacman help, that should replace & reinstall it even if it thinks the current package is already present, and so i suppose maybe undo whatever update nomachine attempted on its own previously.

Next, I opened Plexamp again and am waiting a few minutes to see if it crashes again… I will report back in a few minutes for either outcome.

Also please let me know if this makes you think of anything I might need to consider. I feel like I know just enough about running my PC that I am potentially dangerous…

edit – we’ve passed the few minutes open threshold where i’d expect to see a crash! So I think this actually was my issue.

I will be vigilant about apps which try to update themselves, like nomachine telling me “hey there’s a new version, update?” and I will only trust pacman & garuda-update ever more.

1 Like

How does a Linux user fix a broken system? With a sudo and a smile. :laughing:

2 Likes

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.