Bug 482446 - With panels set to show only tasks from the current screen, Plasma sometimes crashes in TaskManager::WaylandTasksModel::requestActivate() when clicking on task manager button after disconnecting/reconnecting a screen
Summary: With panels set to show only tasks from the current screen, Plasma sometimes ...
Status: CONFIRMED
Alias: None
Product: plasmashell
Classification: Plasma
Component: Task Manager and Icons-Only Task Manager widgets (other bugs)
Version First Reported In: master
Platform: openSUSE Linux
: NOR crash
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: drkonqi, multiscreen, qt6, wayland-only
: 490910 495575 (view as bug list)
Depends on:
Blocks:
 
Reported: 2024-03-05 08:41 UTC by Jure Repinc
Modified: 2025-01-21 15:51 UTC (History)
8 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report: https://crash-reports.kde.org/organizations/kde/issues/5640


Attachments
New crash information added by DrKonqi (133.71 KB, text/plain)
2024-03-05 08:41 UTC, Jure Repinc
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jure Repinc 2024-03-05 08:41:39 UTC
Application: plasmashell (6.0.80)

Qt Version: 6.6.2
Frameworks Version: 6.0.0
Operating System: Linux 6.7.6-1-default x86_64
Windowing System: Wayland
Distribution: "openSUSE Tumbleweed"
DrKonqi: 6.0.80 [CoredumpBackend]

-- Information about the crash:
I have two screens and one is connected through AVR. When AVR gets turned on/off the screen configuration is updated (probably because of HDMI audio changes where audio gets switched between AVR output and TV screen output). When this happens windows get rearrangen between the screen (sometimes some windows don't end up on the screen they were before). I also have two panels with two task manager widgets one on each screen. They are set to show only buttons for windows from current screen. But after this rearrangement happens it happened that window was only on one screen but the button for it was shown on both task manager widgets (as if the window was on two screens at the same time which is quite impossible I would say). I tried to minimize windows and drag them around so that they would hopefully update the task manager diplay, but it did not help. When I clicked ona button for such a window on the task manager plasma crashed.

The reporter is unsure if this crash is reproducible.

-- Backtrace (Reduced):
#5  wl_proxy_get_version (proxy=0xffa6571dff030000) at ../src/wayland-client.c:2248
#6  0x00007f7205dbd4f3 in org_kde_plasma_window_set_state (state=1, flags=1, org_kde_plasma_window=0xffa6571dff030000) at /usr/src/debug/plasma-workspace-6.0.80git.20240302T004916~3fbc6c79/build/libtaskmanager/wayland-plasma-window-management-client-protocol.h:777
#7  QtWayland::org_kde_plasma_window::set_state(unsigned int, unsigned int) (this=<optimized out>, state=1, flags=1) at /usr/src/debug/plasma-workspace-6.0.80git.20240302T004916~3fbc6c79/build/libtaskmanager/qwayland-plasma-window-management.cpp:236
#8  TaskManager::WaylandTasksModel::requestActivate(QModelIndex const&) (this=<optimized out>, index=<optimized out>) at /usr/src/debug/plasma-workspace-6.0.80git.20240302T004916~3fbc6c79/libtaskmanager/waylandtasksmodel.cpp:955
#9  0x00007f7205d726b3 in TaskManager::AbstractTasksProxyModelIface::requestActivate(QModelIndex const&) (index=<optimized out>, this=<optimized out>) at /usr/src/debug/plasma-workspace-6.0.80git.20240302T004916~3fbc6c79/libtaskmanager/abstracttasksproxymodeliface.cpp:24


Reported using DrKonqi
Comment 1 Jure Repinc 2024-03-05 08:41:40 UTC
Created attachment 166417 [details]
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.
Comment 2 roworu 2024-03-16 00:35:23 UTC
Hello. Im also experiencing this bug, but with two displays connected via DP to Nvidia card.
Not only icons messing after screen blanking due to timeout, but also display refresh rate on second screen resets to lowest variables and making it the "Primary"
Is there any additional info I could provide to help?
Comment 3 roworu 2024-03-16 01:00:36 UTC
Or could that be connected to another bug related to system unresponsiveness after display off and on?: 
https://bugs.kde.org/show_bug.cgi?id=448866
Comment 4 Nicolas Fella 2024-03-28 21:11:58 UTC
#5  wl_proxy_get_version (proxy=0xffa6571dff030000) at ../src/wayland-client.c:2248
#6  0x00007f7205dbd4f3 in org_kde_plasma_window_set_state (state=1, flags=1, org_kde_plasma_window=0xffa6571dff030000) at /usr/src/debug/plasma-workspace-6.0.80git.20240302T004916~3fbc6c79/build/libtaskmanager/wayland-plasma-window-management-client-protocol.h:777
#7  QtWayland::org_kde_plasma_window::set_state(unsigned int, unsigned int) (this=<optimized out>, state=1, flags=1) at /usr/src/debug/plasma-workspace-6.0.80git.20240302T004916~3fbc6c79/build/libtaskmanager/qwayland-plasma-window-management.cpp:236
#8  TaskManager::WaylandTasksModel::requestActivate(QModelIndex const&) (this=<optimized out>, index=<optimized out>) at /usr/src/debug/plasma-workspace-6.0.80git.20240302T004916~3fbc6c79/libtaskmanager/waylandtasksmodel.cpp:955
#9  0x00007f7205d726b3 in TaskManager::AbstractTasksProxyModelIface::requestActivate(QModelIndex const&) (index=<optimized out>, this=<optimized out>) at /usr/src/debug/plasma-workspace-6.0.80git.20240302T004916~3fbc6c79/libtaskmanager/abstracttasksproxymodeliface.cpp:24
#10 TaskManager::AbstractTasksProxyModelIface::requestActivate(QModelIndex const&) (this=<optimized out>, index=<optimized out>) at /usr/src/debug/plasma-workspace-6.0.80git.20240302T004916~3fbc6c79/libtaskmanager/abstracttasksproxymodeliface.cpp:14
#11 0x00007f7205d726b3 in TaskManager::AbstractTasksProxyModelIface::requestActivate(QModelIndex const&) (index=<optimized out>, this=<optimized out>) at /usr/src/debug/plasma-workspace-6.0.80git.20240302T004916~3fbc6c79/libtaskmanager/abstracttasksproxymodeliface.cpp:24
#12 TaskManager::AbstractTasksProxyModelIface::requestActivate(QModelIndex const&) (this=<optimized out>, index=<optimized out>) at /usr/src/debug/plasma-workspace-6.0.80git.20240302T004916~3fbc6c79/libtaskmanager/abstracttasksproxymodeliface.cpp:14
#13 0x00007f7205d726b3 in TaskManager::AbstractTasksProxyModelIface::requestActivate(QModelIndex const&) (index=..., this=0x5627f380d940) at /usr/src/debug/plasma-workspace-6.0.80git.20240302T004916~3fbc6c79/libtaskmanager/abstracttasksproxymodeliface.cpp:24
#14 TaskManager::AbstractTasksProxyModelIface::requestActivate(QModelIndex const&) (this=this@entry=0x5627f380d940, index=...) at /usr/src/debug/plasma-workspace-6.0.80git.20240302T004916~3fbc6c79/libtaskmanager/abstracttasksproxymodeliface.cpp:14
#15 0x00007f7205d8963c in TaskManager::TaskGroupingProxyModel::requestActivate(QModelIndex const&) (index=..., this=0x5627f3810f40) at /usr/src/debug/plasma-workspace-6.0.80git.20240302T004916~3fbc6c79/libtaskmanager/taskgroupingproxymodel.cpp:907
#16 TaskManager::TaskGroupingProxyModel::requestActivate(QModelIndex const&) (this=0x5627f3810f40, index=...) at /usr/src/debug/plasma-workspace-6.0.80git.20240302T004916~3fbc6c79/libtaskmanager/taskgroupingproxymodel.cpp:900
#17 0x00007f7205d8ebd5 in TaskManager::TasksModel::requestActivate(QModelIndex const&) (index=<optimized out>, this=<optimized out>) at /usr/src/debug/plasma-workspace-6.0.80git.20240302T004916~3fbc6c79/libtaskmanager/tasksmodel.cpp:1508
#18 TaskManager::TasksModel::requestActivate(QModelIndex const&) (this=<optimized out>, index=<optimized out>) at /usr/src/debug/plasma-workspace-6.0.80git.20240302T004916~3fbc6c79/libtaskmanager/tasksmodel.cpp:1505
#19 0x00007f7205d78954 in TaskManager::TasksModel::qt_metacall(QMetaObject::Call, int, void**) (this=0x5627f37ea3e0, _c=QMetaObject::InvokeMetaMethod, _id=35, _a=0x7ffc2d316c38) at /usr/src/debug/plasma-workspace-6.0.80git.20240302T004916~3fbc6c79/build/libtaskmanager/taskmanager_autogen/EWIEGA46WW/moc_tasksmodel.cpp:1308
#20 0x00007f7212b19bd3 in QQmlObjectOrGadget::metacall(QMetaObject::Call, int, void**) const (this=0x7ffc2d316ef0, type=QMetaObject::InvokeMetaMethod, index=<optimized out>, argv=<optimized out>) at /usr/src/debug/qtdeclarative-everywhere-src-6.6.2/src/qml/qml/qqmlobjectorgadget.cpp:14
#21 0x00007f72129fbc2d in QV4::CallMethod (callType=<optimized out>, callArgs=<optimized out>, engine=<optimized out>, argTypes=<optimized out>, argCount=<optimized out>, returnType=..., index=<optimized out>, object=<optimized out>) at /usr/include/qt6/QtCore/qvarlengtharray.h:84
#22 QV4::CallPrecise(QQmlObjectOrGadget const&, QQmlPropertyData const&, QV4::ExecutionEngine*, QV4::CallData*, QMetaObject::Call) (object=<optimized out>, data=<optimized out>, engine=<optimized out>, callArgs=<optimized out>, callType=<optimized out>) at /usr/src/debug/qtdeclarative-everywhere-src-6.6.2/src/qml/jsruntime/qv4qobjectwrapper.cpp:1850
#23 0x00007f7212a040b1 in operator() (__closure=<optimized out>) at /usr/src/debug/qtdeclarative-everywhere-src-6.6.2/src/qml/jsruntime/qv4qobjectwrapper.cpp:2753
#24 operator()<QV4::QObjectMethod::callInternal(const QV4::Value*, const QV4::Value*, int) const::<lambda()> > (call=<optimized out>, __closure=<synthetic pointer>) at /usr/src/debug/qtdeclarative-everywhere-src-6.6.2/src/qml/jsruntime/qv4qobjectwrapper.cpp:2730
#25 QV4::QObjectMethod::callInternal(QV4::Value const*, QV4::Value const*, int) const (this=0x7ffc2d316fb0, thisObject=<optimized out>, argv=0x7f72041bf648, argc=1) at /usr/src/debug/qtdeclarative-everywhere-src-6.6.2/src/qml/jsruntime/qv4qobjectwrapper.cpp:2753
#26 0x00007f7212a19899 in QV4::Runtime::CallPropertyLookup::call(QV4::ExecutionEngine*, QV4::Value const&, unsigned int, QV4::Value*, int) (engine=0x5627f03c1910, base=..., index=<optimized out>, argv=0x7f72041bf648, argc=1) at /usr/src/debug/qtdeclarative-everywhere-src-6.6.2/src/qml/jsruntime/qv4runtime.cpp:1511
#27 0x00007f71e0819f92 in  ()
#28 0x00007ffc2d317270 in  ()
#29 0x0000000000000000 in  ()
Comment 5 cwo 2024-07-28 08:13:06 UTC
*** Bug 490910 has been marked as a duplicate of this bug. ***
Comment 6 Nate Graham 2024-10-30 15:52:20 UTC
*** Bug 495575 has been marked as a duplicate of this bug. ***
Comment 7 Jaak Ristioja 2025-01-18 13:57:00 UTC
I got an identical backtrace from a crash from interaction with the task manager. Plasmashell version 6.2.4 on a Gentoo laptop with only one display, no other screens were physically attached/disconnected. Drkonqi refers to a std::unique_ptr<char[]>:

Application: plasmashell (plasmashell), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr<char []> = {get() = 0x0}
[KCrash Handler]
#4  wl_proxy_get_version (proxy=0x6f006a002f0065) at ../wayland-1.23.1/src/wayland-client.c:2317
#5  0x00007fbc91f89fb8 in org_kde_plasma_window_set_state (org_kde_plasma_window=0x6f006a002f0065, flags=1, state=1) at /var/tmp/portage/kde-plasma/plasma-workspace-6.2.4/work/plasma-workspace-6.2.4_build/libtaskmanager/wayland-plasma-window-management-client-protocol.h:869
#6  QtWayland::org_kde_plasma_window::set_state (this=<optimized out>, flags=1, state=1) at /var/tmp/portage/kde-plasma/plasma-workspace-6.2.4/work/plasma-workspace-6.2.4_build/libtaskmanager/qwayland-plasma-window-management.cpp:255
#7  0x00007fbc91f135b4 in TaskManager::AbstractTasksProxyModelIface::requestActivate (this=<optimized out>, index=<optimized out>) at /var/tmp/portage/kde-plasma/plasma-workspace-6.2.4/work/plasma-workspace-6.2.4/libtaskmanager/abstracttasksproxymodeliface.cpp:24
#8  TaskManager::AbstractTasksProxyModelIface::requestActivate (this=<optimized out>, index=<optimized out>) at /var/tmp/portage/kde-plasma/plasma-workspace-6.2.4/work/plasma-workspace-6.2.4/libtaskmanager/abstracttasksproxymodeliface.cpp:14
#9  0x00007fbc91f135b4 in TaskManager::AbstractTasksProxyModelIface::requestActivate (this=<optimized out>, index=<optimized out>) at /var/tmp/portage/kde-plasma/plasma-workspace-6.2.4/work/plasma-workspace-6.2.4/libtaskmanager/abstracttasksproxymodeliface.cpp:24
#10 TaskManager::AbstractTasksProxyModelIface::requestActivate (this=<optimized out>, index=<optimized out>) at /var/tmp/portage/kde-plasma/plasma-workspace-6.2.4/work/plasma-workspace-6.2.4/libtaskmanager/abstracttasksproxymodeliface.cpp:14
#11 0x00007fbc91f135b4 in TaskManager::AbstractTasksProxyModelIface::requestActivate (this=<optimized out>, index=<optimized out>) at /var/tmp/portage/kde-plasma/plasma-workspace-6.2.4/work/plasma-workspace-6.2.4/libtaskmanager/abstracttasksproxymodeliface.cpp:24
#12 TaskManager::AbstractTasksProxyModelIface::requestActivate (this=<optimized out>, index=<optimized out>) at /var/tmp/portage/kde-plasma/plasma-workspace-6.2.4/work/plasma-workspace-6.2.4/libtaskmanager/abstracttasksproxymodeliface.cpp:14
#13 0x00007fbc91f27db9 in TaskManager::TaskGroupingProxyModel::requestActivate (this=0x55bef1301f60, index=...) at /var/tmp/portage/kde-plasma/plasma-workspace-6.2.4/work/plasma-workspace-6.2.4/libtaskmanager/taskgroupingproxymodel.cpp:907
#14 TaskManager::TaskGroupingProxyModel::requestActivate (this=0x55bef1301f60, index=...) at /var/tmp/portage/kde-plasma/plasma-workspace-6.2.4/work/plasma-workspace-6.2.4/libtaskmanager/taskgroupingproxymodel.cpp:900
#15 0x00007fbc91f377aa in TaskManager::TasksModel::requestActivate (this=<optimized out>, index=<optimized out>) at /var/tmp/portage/kde-plasma/plasma-workspace-6.2.4/work/plasma-workspace-6.2.4/libtaskmanager/tasksmodel.cpp:1508
#16 TaskManager::TasksModel::requestActivate (this=<optimized out>, index=<optimized out>) at /var/tmp/portage/kde-plasma/plasma-workspace-6.2.4/work/plasma-workspace-6.2.4/libtaskmanager/tasksmodel.cpp:1505
#17 0x00007fbc91f0ed2f in TaskManager::TasksModel::qt_metacall (this=0x55bef133f3d0, _c=<optimized out>, _id=35, _a=0x7fff27195168) at /var/tmp/portage/kde-plasma/plasma-workspace-6.2.4/work/plasma-workspace-6.2.4_build/libtaskmanager/taskmanager_autogen/EWIEGA46WW/moc_tasksmodel.cpp:971
#18 0x00007fbcf375b313 in QQmlObjectOrGadget::metacall (this=this@entry=0x7fff27195440, type=type@entry=QMetaObject::InvokeMetaMethod, index=<optimized out>, index@entry=136, argv=<optimized out>) at /var/tmp/portage/dev-qt/qtdeclarative-6.8.1/work/qtdeclarative-everywhere-src-6.8.1/src/qml/qml/qqmlobjectorgadget.cpp:14
Comment 8 TraceyC 2025-01-21 15:51:16 UTC
Marking confirmed since there are at least 2 people with identical backtraces