Signal: 11 (SEGV) plasma-plasmashell.service

   Message: Process 946 (plasmashell) of user 1000 dumped core.
            
            Stack trace of thread 946:
            #0  0x00007fe8be3e8e20 n/a (libQt6Core.so.6 + 0x5e8e20)
            ELF object binary architecture: AMD x86-64

Got this crash with really helpful stack trace, did any one get the same thing already? Just asking before digging into it?

I also encourage you to observe any other posts regarding the update.

<Some original text redacted.>

2 Likes

$ coredumpctl debug

(gdb) bt

Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00007fe8be3e8e20 in QtPrivate::QMetaTypeInterfaceWrapper<QFlagsQt::WindowState >::metaType () from /usr/lib/libQt6Core.so.6
[Current thread is 1 (Thread 0x7fe8b90439c0 (LWP 946))]
(gdb) bt
#0 0x00007fe8be3e8e20 in QtPrivate::QMetaTypeInterfaceWrapper<QFlagsQt::WindowState >::metaType () at /usr/lib/libQt6Core.so.6
#1 0x00007fe8be14b583 in QPersistentModelIndex::row (this=) at /usr/src/debug/qt6-base/qtbase/src/corelib/itemmodels/qabstractitemmodel.cpp:511
#2 QItemSelectionRange::top (this=) at /usr/src/debug/qt6-base/qtbase/src/corelib/itemmodels/qitemselectionmodel.h:31
#3 QItemSelectionRange::intersects (this=0x7ffde0251d70, other=…) at /usr/src/debug/qt6-base/qtbase/src/corelib/itemmodels/qitemselectionmodel.cpp:187
#4 0x00005620865c4dc0 in ??? ()
#5 0x00005620870b3b50 in ??? ()
#6 0x0000000000000000 in ??? ()

(gdb) info registers
rax 0x7fe8be3d9b18 140637600848664
rbx 0x7ffde0251d70 140728363982192
rcx 0x7fe8bce71770 140637578401648
rdx 0x0 0
rsi 0x7fe8b4022e00 140637429181952
rdi 0x7ffde0251d70 140728363982192
rbp 0x5620870ae630 0x5620870ae630
rsp 0x7ffde0251d28 0x7ffde0251d28
r8 0x0 0
r9 0x7fe8be20fac0 140637598972608
r10 0x562085ab9f40 94697681559360
r11 0x5acde567b9527b3 408946129205798835
r12 0x5620865c4dc0 94697693138368
r13 0x14 20
r14 0x56208716d430 94697705362480
r15 0x562085d88cc0 94697684503744
rip 0x7fe8be3e8e20 0x7fe8be3e8e20 <QtPrivate::QMetaTypeInterfaceWrapper<QFlagsQt::WindowState >::metaType>
eflags 0x10246 [ PF ZF IF RF ]
cs 0x33 51
ss 0x2b 43
ds 0x0 0
es 0x0 0
fs 0x0 0
gs 0x0 0
fs_base 0x7fe8b90439c0 140637513202112
gs_base 0x0 0

I havent noticed a similar error from any other posts… but I wonder if you performed the refresh steps (clear items from .config and .cache) like here: https://wiki.archlinux.org/title/KDE#Configuration_related

I did not, for now I wont do it just to see if it can be reproduced. Also its not a locking or some flickering it’s a crash, it shouldn’t do that because of some crap in .config and .cache files.

But its plasmashell … which gets all kinds of hints from files in those paths.
(~/.config/plasmashellrc for example)

still it should not crash whole WM with a bug in libQt6Core.so, but if it will help with anything:

$ cat ~/.config/plasmashellrc
[PlasmaViews][Panel 3]
floating=1

[PlasmaViews][Panel 3][Defaults]
thickness=44

[Updates]
performed=/usr/share/plasma/shells/org.kde.plasma.desktop/contents/updates/keyboardlayout_migrateiconsetting.js,/usr/share/plasma/shells/org.kde.plasma.desktop/contents/updates/systemloadviewer_systemmonitor.js,/usr/share/plasma/shells/org.kde.plasma.desktop/contents/updates/digitalclock_migrate_font_settings.js,/usr/share/plasma/shells/org.kde.plasma.desktop/contents/updates/maintain_existing_desktop_icon_sizes.js,/usr/share/plasma/shells/org.kde.plasma.desktop/contents/updates/digitalclock_rename_timezonedisplay_key.js,/usr/share/plasma/shells/org.kde.plasma.desktop/contents/updates/unlock_widgets.js,/usr/share/plasma/shells/org.kde.plasma.desktop/contents/updates/keyboardlayout_remove_shortcut.js,/usr/share/plasma/shells/org.kde.plasma.desktop/contents/updates/move_desktop_layout_config.js,/usr/share/plasma/shells/org.kde.plasma.desktop/contents/updates/no_middle_click_paste_on_panels.js,/usr/share/plasma/shells/org.kde.plasma.desktop/contents/updates/containmentactions_middlebutton.js,/usr/share/plasma/shells/org.kde.plasma.desktop/contents/updates/mediaframe_migrate_useBackground_setting.js,/usr/share/plasma/shells/org.kde.plasma.desktop/contents/updates/klipper_clear_config.js,/usr/share/plasma/shells/org.kde.plasma.desktop/contents/updates/folderview_fix_recursive_screenmapping.js,/usr/share/plasma/shells/org.kde.plasma.desktop/contents/updates/digitalclock_migrate_showseconds_setting.js,/usr/share/plasma/shells/org.kde.plasma.desktop/contents/updates/migrate_font_weights.js

Posted on qt forum: topic 156764 sigsegv-qtprivate-qmetatypeinterfacewrapper-qflagsqt-windowstate-metatype, any reason why there are no links allowed in this forum?

Well I’ve checked the qtbase, wrote them on the forum (like they’ll need a hint from the gdb bt) anyway I can’t do anything about it, I’ll just wait for reply (don’t think I’ll get one), the s**t I wrote:

this is the return -1 in the code below right? dont see any register full of 0xff’s, something optimized? Are we missing a check in metaType () for -1?, the qabstractitemmodel.cpp:511 :
int QPersistentModelIndex::row() const
{
if (d)
return d->index.row();
return -1;
}

where am I wrong?

hmm missed that


Moderator edit: In the future, please use proper formatting: [HowTo] Post command output and file content as formatted text