STEPS TO REPRODUCE 1. Log into an account with sudo privileges and open KDE Partition Manager 2. Close/Skip the pop-up window that asks for the user password 3. Click the "Refresh Devices" button 4. Another pop-up window that asks for the user password will appear. Enter the correct password SOFTWARE/OS VERSIONS Operating System: EndeavourOS KDE Plasma Version: 6.4.2 KDE Frameworks Version: 6.16.0 Qt Version: 6.9.1 Kernel Version: 6.12.37-1-lts (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION Here is what is shown in the terminal, if I open the app from konsole and reproduce the bug: ❯ partitionmanager Loaded backend plugin: "pmsfdiskbackendplugin" "Using backend plugin: pmsfdiskbackendplugin (1)" "Scanning devices..." [1] 4289 segmentation fault (core dumped) partitionmanager In addition, skipping the password prompt a second time and clicking on "Refresh Devices" again, the app crashes without the password prompt even appearing. Again, with a segmentation fault.
Hmm, doesn't crash here. Hard to tell what happens from just 4289 segmentation fault (core dumped) You need install debug symbols and get the full backtrace.
(In reply to Andrius Štikonas from comment #1) > Hmm, doesn't crash here. > > Hard to tell what happens from just 4289 segmentation fault (core dumped) > You need install debug symbols and get the full backtrace. Thanks for replying and sorry for the delay in my response How do I "install debug symbols and get the full backtrace?" I did try running partitionmanager with gdb but I don't remember seeing anything relevant
(In reply to Robi from comment #2) > (In reply to Andrius Štikonas from comment #1) > > Hmm, doesn't crash here. > > > > Hard to tell what happens from just 4289 segmentation fault (core dumped) > > You need install debug symbols and get the full backtrace. > > Thanks for replying and sorry for the delay in my response > How do I "install debug symbols and get the full backtrace?" > I did try running partitionmanager with gdb but I don't remember seeing > anything relevant That is distro dependent... I'm not familiar with Endeavour OS but assuming it's close to Arch, this should be helpful to you: https://wiki.archlinux.org/title/Debugging/Getting_traces
(In reply to Andrius Štikonas from comment #3) Alright here's (what I think is relevant from) the backtrace "Using backend plugin: pmsfdiskbackendplugin (1)" "Scanning devices..." [New Thread 0x7fff8ffff6c0 (LWP 3199)] getting temp failed for "/dev/nvme0n1" : No such file or directory getting powered on time failed for "/dev/nvme0n1" : No such file or directory getting power cycles failed for "/dev/nvme0n1" : No such file or directory unknown file system type "" on "/dev/nvme0n1p1" Thread 1 "partitionmanage" received signal SIGSEGV, Segmentation fault. Downloading 185.96 K source file /usr/src/debug/glib2/build/../glib/glib/gmain.c g_source_get_name (source=source@entry=0x15562c880) at ../glib/glib/gmain.c:2145 2145 g_return_val_if_fail (g_atomic_int_get (&source->ref_count) > 0, NULL);
(In reply to Robi from comment #4) > (In reply to Andrius Štikonas from comment #3) > > Alright here's (what I think is relevant from) the backtrace > > "Using backend plugin: pmsfdiskbackendplugin (1)" > "Scanning devices..." > [New Thread 0x7fff8ffff6c0 (LWP 3199)] > getting temp failed for "/dev/nvme0n1" : No such file or directory > getting powered on time failed for "/dev/nvme0n1" : No such file or > directory > getting power cycles failed for "/dev/nvme0n1" : No such file or directory > unknown file system type "" on "/dev/nvme0n1p1" > > Thread 1 "partitionmanage" received signal SIGSEGV, Segmentation fault. > Downloading 185.96 K source file > /usr/src/debug/glib2/build/../glib/glib/gmain.c > g_source_get_name (source=source@entry=0x15562c880) at > ../glib/glib/gmain.c:2145 > 2145 g_return_val_if_fail (g_atomic_int_get (&source->ref_count) > 0, > NULL); Strange, that is not even in partition manager source code, that's in Glib. And glib is not even a direct dependency of partitionmanager, it's two or more layers down in the dependency chain.
(In reply to Andrius Štikonas from comment #5) So it's best I report this to the Arch maintainer of the partitionmanager package?
(In reply to Robi from comment #6) > (In reply to Andrius Štikonas from comment #5) > > So it's best I report this to the Arch maintainer of the partitionmanager > package? I think so, perhaps also search for this g_return_val_if_fail in their bug tracker
*** Bug 507650 has been marked as a duplicate of this bug. ***