Bug 507650 - SIGSEGV (Address Boundary Error) consistently on 'Refresh Devices'
Summary: SIGSEGV (Address Boundary Error) consistently on 'Refresh Devices'
Status: RESOLVED DUPLICATE of bug 506989
Alias: None
Product: partitionmanager
Classification: Applications
Component: general (other bugs)
Version First Reported In: 25.04.3
Platform: Arch Linux Linux
: NOR crash
Target Milestone: ---
Assignee: Andrius Štikonas
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-07-29 21:33 UTC by ericlondres
Modified: 2025-07-29 22:45 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description ericlondres 2025-07-29 21:33:33 UTC
SUMMARY
partitionmanager crashes with SIGSEGV (Address Boundary Error) every time I open the application and select 'Refresh Devices.'

STEPS TO REPRODUCE
1. Start partitionmanager
2. Click the 'Refresh Devices' button
3. 

OBSERVED RESULT
The application crashes immediately, with the following printed to my terminal:

kf.coreaddons: "Could not find plugin kpmcore/"
Could not create instance of plugin   ""
Loaded backend plugin:  "pmsfdiskbackendplugin"
KCrash: Application 'partitionmanager' crashing... crashRecursionCounter = 2
fish: Job 1, 'partitionmanager' terminated by signal SIGSEGV (Address boundary error)

EXPECTED RESULT
Normal application operations, such as refreshing devices


SOFTWARE/OS VERSIONS
libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
Operating System: Arch Linux 
KDE Plasma Version: 6.4.3
KDE Frameworks Version: 6.16.0
Qt Version: 6.9.1
Kernel Version: 6.15.8-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 12 × Intel® Core™ i7-8750H CPU @ 2.20GHz
Memory: 80 GiB of RAM (78.2 GiB usable)
Graphics Processor 1: Mesa Intel® UHD Graphics 630
Graphics Processor 2: llvmpipe

ADDITIONAL INFORMATION
I tried running the application through gdb in DrKonqi to get a backtrace, but the error changed to a Segmentation Fault instead of Address Boundary Error. I am not sure if this is useful, but this is the backtrace I got:

#0  g_source_get_name (source=source@entry=0x35564d0a0) at ../glib/glib/gmain.c:2145
#1  0x00007ffff5908896 in g_main_dispatch (context=0x7fffe8000f00) at ../glib/glib/gmain.c:3405
#2  0x00007ffff5909cd7 in g_main_context_dispatch_unlocked (context=0x7fffe8000f00)
    at ../glib/glib/gmain.c:4249
#3  g_main_context_iterate_unlocked
    (context=context@entry=0x7fffe8000f00, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at ../glib/glib/gmain.c:4314
#4  0x00007ffff5909ee5 in g_main_context_iteration (context=0x7fffe8000f00, may_block=1)
    at ../glib/glib/gmain.c:4379
#5  0x00007ffff5e3c5e2 in QEventDispatcherGlib::processEvents (this=0x555555628140, flags=...)
    at /usr/src/debug/qt6-base/qtbase/src/corelib/kernel/qeventdispatcher_glib.cpp:399
#6  0x00007ffff5b744b6 in QEventLoop::processEvents (this=0x7fffffffd3e0, flags=...)
    at /usr/src/debug/qt6-base/qtbase/src/corelib/kernel/qeventloop.cpp:104
#7  QEventLoop::exec (this=0x7fffffffd3e0, flags=...)
    at /usr/src/debug/qt6-base/qtbase/src/corelib/kernel/qeventloop.cpp:186
#8  0x00007ffff5b6c7c1 in QCoreApplication::exec ()
    at /usr/src/debug/qt6-base/qtbase/src/corelib/kernel/qcoreapplication.cpp:1449
#9  0x00007ffff6cfc66a in QApplication::exec ()
    at /usr/src/debug/qt6-base/qtbase/src/widgets/kernel/qapplication.cpp:2570
#10 0x000055555557dbf6 in main (argc=<optimized out>, argv=<optimized out>)
    at /usr/src/debug/partitionmanager/partitionmanager-25.04.3/src/main.cpp:143
Comment 1 Andrius Štikonas 2025-07-29 22:44:48 UTC

*** This bug has been marked as a duplicate of bug 506989 ***
Comment 2 Andrius Štikonas 2025-07-29 22:45:26 UTC
Hmm, probably Arch issue. This is the second crash in glib (which is not even a direct dependency of partitionmanager) and both reports were on Arch.