Bug 489638 - Plasma crashed in Klipper::showPopupMenu() when trying to open Klipper paste menu with keyboard shortcut Meta+V
Summary: Plasma crashed in Klipper::showPopupMenu() when trying to open Klipper paste ...
Status: RESOLVED DUPLICATE of bug 490791
Alias: None
Product: plasmashell
Classification: Plasma
Component: Clipboard (show other bugs)
Version: master
Platform: openSUSE Linux
: NOR crash
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2024-07-02 23:06 UTC by Jure Repinc
Modified: 2024-08-01 12:57 UTC (History)
15 users (show)

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


Attachments
New crash information added by DrKonqi (141.98 KB, text/plain)
2024-07-02 23:06 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-07-02 23:06:02 UTC
Application: plasmashell (6.1.80)

Qt Version: 6.7.2
Frameworks Version: 6.4.0
Operating System: Linux 6.9.7-1-default x86_64
Windowing System: Wayland
Distribution: "openSUSE Tumbleweed"
DrKonqi: 6.1.80 [CoredumpBackend]

-- Information about the crash:
I had Yakuake window open and tried to paste some previously copied text into it so I pressed the keyboard combination Meta+V to open the Klipper paste menu, At this point Plasma crashed and restartet itself.

The reporter is unsure if this crash is reproducible.

-- Backtrace (Reduced):
#5  std::__atomic_base<int>::fetch_add (__m=std::memory_order_acq_rel, __i=1, this=0x153850f0000) at /usr/include/c++/13/bits/atomic_base.h:633
#6  QAtomicOps<int>::ref<int> (_q_value=<error reading variable: Cannot access memory at address 0x153850f0000>, _q_value=<optimized out>) at /usr/src/debug/qtbase-everywhere-src-6.7.2/src/corelib/thread/qatomic_cxx11.h:259
[...]
#8  QtSharedPointer::ExternalRefCountData::getAndRef (obj=obj@entry=0x5571645f9690) at /usr/src/debug/qtbase-everywhere-src-6.7.2/src/corelib/tools/qsharedpointer.cpp:1456
#9  0x00007f1362a33ae0 in QWeakPointer<QObject>::QWeakPointer<QObject, true> (ptr=0x5571645f9690, this=<optimized out>) at /usr/src/debug/qtbase-everywhere-src-6.7.2/src/corelib/tools/qsharedpointer_impl.h:733
#10 QWeakPointer<QObject>::assign<QObject> (ptr=0x5571645f9690, this=0x55716640d7e0) at /usr/src/debug/qtbase-everywhere-src-6.7.2/src/corelib/tools/qsharedpointer_impl.h:728


Reported using DrKonqi
Comment 1 Jure Repinc 2024-07-02 23:06:03 UTC
Created attachment 171309 [details]
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.
Comment 2 Nate Graham 2024-07-03 17:26:36 UTC
Is this on a multi-screen setup?
Comment 3 Jure Repinc 2024-07-03 21:54:01 UTC
Yes, dual screen:
Output: 1 DVI-D-1
        enabled
        connected
        priority 2
        DVI
        Modes:  0:1680x1050@60*!  1:1280x1024@75  2:1280x1024@60  3:1440x900@60  4:1280x960@60  5:1280x800@60  6:1152x864@75  7:1280x720@60  8:1024x768@75  9:1024x768@70  10:1024x768@60  11:832x624@75  12:800x600@75  13:800x600@72  14:800x600@60  15:800x600@56  16:640x480@75  17:640x480@73  18:640x480@67  19:640x480@60  20:720x400@70  21:1280x1024@60  22:1024x768@60  23:1280x800@60  24:1600x900@60  25:1368x768@60  26:1280x720@60 
        Geometry: 0,380 1120x700
        Scale: 1.5
        Rotation: 1
        Overscan: 0
        Vrr: incapable
        RgbRange: unknown
        HDR: incapable
        Wide Color Gamut: incapable
        ICC profile: none
        Color profile source: sRGB
Output: 2 HDMI-A-1
        enabled
        connected
        priority 1
        HDMI
        Modes:  0:3840x2160@60*!  1:4096x2160@60  2:4096x2160@60  3:4096x2160@50  4:4096x2160@30  5:4096x2160@30  6:4096x2160@25  7:4096x2160@24  8:4096x2160@24  9:3840x2160@60  10:3840x2160@60  11:3840x2160@50  12:3840x2160@30  13:3840x2160@30  14:3840x2160@25  15:3840x2160@24  16:3840x2160@24  17:1920x1200@60  18:1920x1080@60  19:1920x1080@60  20:1920x1080@60  21:1920x1080@50  22:1920x1080@30  23:1920x1080@30  24:1920x1080@25  25:1920x1080@24  26:1920x1080@24  27:1920x1080@24  28:1600x1200@60  29:1680x1050@60  30:1400x1050@60  31:1280x1024@75  32:1280x1024@60  33:1440x900@60  34:1280x960@60  35:1280x800@60  36:1152x864@75  37:1280x720@60  38:1280x720@60  39:1280x720@50  40:1024x768@75  41:1024x768@70  42:1024x768@60  43:832x624@75  44:800x600@75  45:800x600@72  46:800x600@60  47:800x600@56  48:720x576@50  49:720x576@50  50:720x480@60  51:720x480@60  52:720x480@60  53:720x480@60  54:640x480@75  55:640x480@73  56:640x480@60  57:640x480@60  58:640x480@60  59:720x400@70  60:1600x1200@60  61:1280x1024@60  62:1024x768@60  63:2560x1600@60  64:1920x1200@60  65:1280x800@60  66:3840x2160@60  67:3200x1800@60  68:2880x1620@60  69:2560x1440@60  70:1920x1080@60  71:1600x900@60  72:1368x768@60  73:1280x720@60 
        Geometry: 1120,0 1920x1080
        Scale: 2
        Rotation: 1
        Overscan: 0
        Vrr: incapable
        RgbRange: unknown
        HDR: incapable
        Wide Color Gamut: incapable
        ICC profile: none
        Color profile source: sRGB
Comment 4 Holden 2024-07-03 22:02:41 UTC
(In reply to Nate Graham from comment #2)
> Is this on a multi-screen setup?

Not OP but I've seen this intermittent crash recently in tumbleweed as well, starting with 6.1.1 I believe. In my case, I'm almost always on a multi-screen setup so it's hard to say if it occurs on a single screen setup. It's seemingly pretty random when it occurs. Coincidentally, I was searching bug reports for why I can't paste code into Qt Creator and saw this. Might be related.
Comment 5 MBR 2024-07-04 18:16:37 UTC
for me it sometimes crashes on first opening of the paste menu, but crashes *always* if I open the paste menu with ctrl V and then press ctrl V again
Comment 6 aronkvh 2024-07-06 12:10:26 UTC
(In reply to Holden from comment #4)
> (In reply to Nate Graham from comment #2)
> > Is this on a multi-screen setup?
> 
> Not OP but I've seen this intermittent crash recently in tumbleweed as well,
> starting with 6.1.1 I believe. In my case, I'm almost always on a
> multi-screen setup so it's hard to say if it occurs on a single screen
> setup. It's seemingly pretty random when it occurs. Coincidentally, I was
> searching bug reports for why I can't paste code into Qt Creator and saw
> this. Might be related.

I get the same crash when using an external monitor. Happens almost every time I press meta+V, but isn't reproducible every time.
If I open Klipper on the laptop screen, it will open properly on the external monitor for a while afterwards.
Comment 7 Eduard 2024-07-07 16:10:35 UTC
I can confirm a serious crash on pressing the Windows-key + V.
_Not_ using multi-monitor here, just my a Legion 5 Pro laptop screen.

A couple important things here:
> It does not happen every time.
> When it happens, it tends to repeat every time I press these hotkeys again.
> It does not happen when clicking on the clipboard tool itself via the panel.
> The crash is pretty serous: At first glance, it looks mostly like the taskbar panel and desktop disappear (it looks like these try to restart but that does not succeed every time. But then when I logout with Ctrl+Alt+Del and then login again from my LigthDM display manager again, the screen becomes black again, and my entire system freezes. I need to hard reset my laptop. Ctrl+Alt+F<number> key combination to go switch to a TTY does not work anymore.

I am using Arch Linux, Plasma desktop 6.1.2
Comment 8 Eduard 2024-07-07 18:10:35 UTC
I can now also add that I can simply reproduce the issue in a QEMU/KVM virtual machine as well. Again an Arch Linux guest (with testing repos enabled).

For what I notice it does not cause as bad problems as on my bare metal system as it seems, but still the desktop shows a restart with a black moment.

One thing I now also realize, is that especially after, or even during displaying the a desktop overview (by Super+W or Super+G), the problem to happen a lot more often (still not every time though).
Comment 9 thePanz 2024-07-08 09:02:50 UTC
Might be related to: https://bugs.kde.org/show_bug.cgi?id=489259 ?
Comment 10 Gabriel Barros 2024-07-08 18:34:58 UTC
Happens from time to time. Usually after copying a URL from firefox addressbar, but I cannot reproduce. It only happens after i've been copying and pasting for a while. I think sleeping and restoring have something to do with it, but again, cannot reproduce. I do use a external monitor from time to time, but I do not think that is related as I happens when i haven't touched the hdmi cable for days.

I have never saw drKonqui noticing it! kwin just restart.

Operating System: Arch Linux 
KDE Plasma Version: 6.1.2
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.2
Kernel Version: 6.9.7-arch1-1 (64-bit)
Graphics Platform: Wayland

$ pacman -Ss plasma | g installed
3:extra/bluedevil 1:6.1.2-1 (plasma) [installed]
5:extra/breeze 6.1.2-1 (plasma) [installed]
7:extra/breeze-gtk 6.1.2-1 (plasma) [installed]
13:extra/discover 6.1.2-1 (plasma) [installed]
15:extra/drkonqi 6.1.2-1 (plasma) [installed]
19:extra/kaccounts-integration 24.05.2-1 [installed]
21:extra/kactivitymanagerd 6.1.2-1 (plasma) [installed]
23:extra/kclock 24.05.2-1 (kde-applications kde-utilities) [installed]
25:extra/kde-cli-tools 6.1.2-1 (plasma) [installed]
27:extra/kde-gtk-config 6.1.2-1 (plasma) [installed]
29:extra/kdecoration 6.1.2-1 (plasma) [installed]
31:extra/kdeplasma-addons 6.1.2-1 (plasma) [installed]
33:extra/keysmith 24.05.2-1 (kde-applications kde-utilities) [installed]
35:extra/kgamma 6.1.2-1 (plasma) [installed]
37:extra/kglobalacceld 6.1.2-1 (plasma) [installed]
39:extra/kinfocenter 6.1.2-1 (plasma) [installed]
41:extra/kmenuedit 6.1.2-1 (plasma) [installed]
43:extra/kpipewire 6.1.2-1 (plasma) [installed]
45:extra/krdp 6.1.2-1 (plasma) [installed]
47:extra/krecorder 24.05.2-1 (kde-applications kde-utilities) [installed]
49:extra/kscreen 6.1.2-1 (plasma) [installed]
51:extra/kscreenlocker 6.1.2-1 (plasma) [installed]
53:extra/ksshaskpass 6.1.2-1 (plasma) [installed]
55:extra/ksystemstats 6.1.2-1 (plasma) [installed]
59:extra/kwallet-pam 6.1.2-1 (plasma) [installed]
61:extra/kwayland 6.1.2-1 (plasma) [installed]
63:extra/kweather 24.05.2-1 (kde-applications kde-utilities) [installed]
65:extra/kwin 6.1.2-1 (plasma) [installed]
67:extra/kwrited 6.1.2-1 (plasma) [installed]
69:extra/layer-shell-qt 6.1.2-1 (plasma) [installed]
71:extra/libkscreen 6.1.2-1 (plasma) [installed]
73:extra/libksysguard 6.1.2-1 (plasma) [installed]
75:extra/libplasma 6.1.2-1 (plasma) [installed]
79:extra/milou 6.1.2-1 (plasma) [installed]
81:extra/ocean-sound-theme 6.1.2-1 (plasma) [installed]
83:extra/oxygen 6.1.2-1 (plasma) [installed]
85:extra/oxygen-sounds 6.1.2-1 (plasma) [installed]
87:extra/plasma-activities 6.1.2-1 (plasma) [installed]
89:extra/plasma-activities-stats 6.1.2-1 (plasma) [installed]
93:extra/plasma-browser-integration 6.1.2-1 (plasma) [installed]
95:extra/plasma-desktop 6.1.2-1 (plasma) [installed]
97:extra/plasma-disks 6.1.2-1 (plasma) [installed]
99:extra/plasma-firewall 6.1.2-1 (plasma) [installed]
103:extra/plasma-integration 6.1.2-1 (plasma) [installed]
105:extra/plasma-meta 6.1-1 [installed]
107:extra/plasma-nm 6.1.2-1 (plasma) [installed]
109:extra/plasma-pa 6.1.2-1 (plasma) [installed]
115:extra/plasma-systemmonitor 6.1.2-1 (plasma) [installed]
117:extra/plasma-thunderbolt 6.1.2-1 (plasma) [installed]
119:extra/plasma-vault 6.1.2-1 (plasma) [installed]
123:extra/plasma-welcome 6.1.2-1 (plasma) [installed]
125:extra/plasma-workspace 6.1.2-1 (plasma) [installed]
127:extra/plasma-workspace-wallpapers 6.1.2-1 (plasma) [installed]
131:extra/plasma5support 6.1.2-1 (plasma) [installed]
137:extra/polkit-kde-agent 6.1.2-1 (plasma) [installed]
139:extra/powerdevil 6.1.2-1 (plasma) [installed]
141:extra/print-manager 1:6.1.2-1 (plasma) [installed]
145:extra/qqc2-breeze-style 6.1.2-1 (plasma) [installed]
147:extra/sddm-kcm 6.1.2-1 (plasma) [installed]
149:extra/systemsettings 6.1.2-1 (plasma) [installed]
155:extra/xdg-desktop-portal-kde 6.1.2-1 (plasma) [installed]
Comment 11 Gabriel Barros 2024-07-08 18:38:37 UTC
(In reply to thePanz from comment #9)
> Might be related to: https://bugs.kde.org/show_bug.cgi?id=489259 ?

Do not think so. I can hold Meta+V and the window keeps flashing forever. I cannot make it crash this way alone.

I also never saw the log-off like Eduard (and from other reporters also not seeing it, I think Eduard might be tying their xsession to kwin somehow so the session is lost when it restart? is that even possible?)
Comment 12 Eduard 2024-07-11 23:55:18 UTC
(In reply to Gabriel Barros from comment #11)
> (In reply to thePanz from comment #9)
> > Might be related to: https://bugs.kde.org/show_bug.cgi?id=489259 ?
> 
> Do not think so. I can hold Meta+V and the window keeps flashing forever. I
> cannot make it crash this way alone.
> 
> I also never saw the log-off like Eduard (and from other reporters also not
> seeing it, I think Eduard might be tying their xsession to kwin somehow so
> the session is lost when it restart? is that even possible?)

Hi Gabriel I think you kind of have a point.
Meanwhile, after replying here I have switched from using my LightDM display manager to using SDDM, because of more general stability issues which I experienced when logging into into a Plasma Wayland session.
Possibly it's all related to the problems described here - I was not fully aware of that though, but this is what I am starting to think right now based on your question.

I know LightDM still runs on X11, while it looks like SDDM uses Wayland, or at least by default now (I noticed that the X11 DPI scaling setting for SDDM has no effect on it for example).

The reason I was using LightDM in the first place is because my switch to actually using KDE Plasma as my daily desktop on this Arch system is pretty new.
I have been using Xfce on this laptop all the time and it's still installed (which is fine). Other desktops did I all have on other installed systems that I boot less often and in virtual machines.

The biggest issue that I turned out to experience was that at a regular base my system completely froze when login into Plasma, so bad that it became totally unresponsive (TTY switch not working).
On the many other moments where login succeeded the login happened with a kind of slowness and black screen moment, not nice.
With also having a Wayland display manager running, that issue seems to be solved, not only no crashes anymore, but not that rough transition anymore.

Are there also generally known issues around this that you or someone else know about? For example some graphical resources related conflict between X display manager and the Wayland desktop? Just a guess.
Comment 13 Petrov Egor 2024-07-13 10:31:11 UTC
Same.
Single monitor setup
OS: openSUSE Tumbleweed 20240711
KDE Plasma Version: 6.1.2
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.2
Kernel Version: 6.9.7-1-default (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 4600H with Radeon Graphics
Graphics Processor: AMD Radeon Graphics
Comment 14 TraceyC 2024-07-15 14:41:37 UTC
Setting to confirmed since multiple people have reported the same issue
Comment 15 Nate Graham 2024-07-22 22:02:58 UTC
Thread 1 (Thread 0x7f135e1d8b00 (LWP 8070)):
[KCrash Handler]
#5  std::__atomic_base<int>::fetch_add (__m=std::memory_order_acq_rel, __i=1, this=0x153850f0000) at /usr/include/c++/13/bits/atomic_base.h:633
#6  QAtomicOps<int>::ref<int> (_q_value=<error reading variable: Cannot access memory at address 0x153850f0000>, _q_value=<optimized out>) at /usr/src/debug/qtbase-everywhere-src-6.7.2/src/corelib/thread/qatomic_cxx11.h:259
#7  QBasicAtomicInteger<int>::ref (this=0x153850f0000) at /usr/src/debug/qtbase-everywhere-src-6.7.2/src/corelib/thread/qbasicatomic.h:47
#8  QtSharedPointer::ExternalRefCountData::getAndRef (obj=obj@entry=0x5571645f9690) at /usr/src/debug/qtbase-everywhere-src-6.7.2/src/corelib/tools/qsharedpointer.cpp:1456
#9  0x00007f1362a33ae0 in QWeakPointer<QObject>::QWeakPointer<QObject, true> (ptr=0x5571645f9690, this=<optimized out>) at /usr/src/debug/qtbase-everywhere-src-6.7.2/src/corelib/tools/qsharedpointer_impl.h:733
#10 QWeakPointer<QObject>::assign<QObject> (ptr=0x5571645f9690, this=0x55716640d7e0) at /usr/src/debug/qtbase-everywhere-src-6.7.2/src/corelib/tools/qsharedpointer_impl.h:728
#11 QPointer<QScreen>::operator= (p=0x5571645f9690, this=0x55716640d7e0, this=<optimized out>, p=<optimized out>) at /usr/src/debug/qtbase-everywhere-src-6.7.2/src/corelib/kernel/qpointer.h:71
#12 QWindowPrivate::connectToScreen (this=0x55716640d690, screen=0x5571645f9690) at /usr/src/debug/qtbase-everywhere-src-6.7.2/src/gui/kernel/qwindow.cpp:490
#13 0x00007f1362a39305 in QWindowPrivate::setTopLevelScreen (this=0x55716640d690, newScreen=0x5571645f9690, recreate=<optimized out>) at /usr/src/debug/qtbase-everywhere-src-6.7.2/src/gui/kernel/qwindow.cpp:515
#14 0x00007f13645f9b73 in QWidgetPrivate::setScreen (this=0x557165e6a8d0, screen=0x5571645f9690) at /usr/src/debug/qtbase-everywhere-src-6.7.2/src/widgets/kernel/qwidget.cpp:2440
#15 0x00007f136476ff08 in QMenuPrivate::popup(QPoint const&, QAction*, std::function<QPoint (QSize const&)>) (this=0x557165e6a8d0, p=..., atAction=atAction@entry=0x0, positionFunction=...) at /usr/src/debug/qtbase-everywhere-src-6.7.2/src/widgets/widgets/qmenu.cpp:2343
#16 0x00007f136477010e in QMenu::popup (this=this@entry=0x557165e64a10, p=..., atAction=atAction@entry=0x0) at /usr/src/debug/qtbase-everywhere-src-6.7.2/src/widgets/widgets/qmenu.cpp:2313
#17 0x00007f13396dbee4 in Klipper::showPopupMenu (this=0x557165d88f90, menu=0x557165e64a10) at /usr/src/debug/plasma-workspace-6.1.80git.20240630T094540~c68c9de3/klipper/klipper.cpp:316
#18 0x00007f13621e7f90 in QtPrivate::QSlotObjectBase::call (a=0x7ffceaf4d220, r=0x557165d88f90, this=0x557165e60530) at /usr/src/debug/qtbase-everywhere-src-6.7.2/src/corelib/kernel/qobjectdefs_impl.h:469
#19 doActivate<false> (sender=0x557165e63f20, signal_index=7, argv=0x7ffceaf4d220) at /usr/src/debug/qtbase-everywhere-src-6.7.2/src/corelib/kernel/qobject.cpp:4086
#20 0x00007f1362d374f2 in QAction::triggered (this=this@entry=0x557165e63f20, _t1=<optimized out>) at /usr/src/debug/qtbase-everywhere-src-6.7.2/build/src/gui/Gui_autogen/include/moc_qaction.cpp:480
#21 0x00007f1362d3a0e4 in QAction::activate (this=0x557165e63f20, event=<optimized out>) at /usr/src/debug/qtbase-everywhere-src-6.7.2/src/gui/kernel/qaction.cpp:1102
#22 0x00007f13621e7f90 in QtPrivate::QSlotObjectBase::call (a=0x7ffceaf4d3e0, r=0x7f1364bffcc0 <_ZZN13QGlobalStaticIN14QtGlobalStatic6HolderIN12_GLOBAL__N_116Q_QGS_s_instanceEEEE8instanceEvE6holder.lto_priv.0>, this=0x557164b257b0) at /usr/src/debug/qtbase-everywhere-src-6.7.2/src/corelib/kernel/qobjectdefs_impl.h:469
#23 doActivate<false> (sender=0x557164b28d20, signal_index=3, argv=0x7ffceaf4d3e0) at /usr/src/debug/qtbase-everywhere-src-6.7.2/src/corelib/kernel/qobject.cpp:4086
#24 0x00007f1364bf372f in OrgKdeKglobalaccelComponentInterface::globalShortcutPressed (_t3=<optimized out>, _t2=<optimized out>, _t1=<optimized out>, this=<optimized out>) at /usr/src/debug/kglobalaccel-6.4.0git.20240618T012458~10f89e8/build/src/moc_kglobalaccel_component_interface.cpp:255
#25 OrgKdeKglobalaccelComponentInterface::qt_static_metacall (_o=_o@entry=0x557164b28d20, _c=_c@entry=QMetaObject::InvokeMetaMethod, _id=_id@entry=0, _a=_a@entry=0x7ffceaf4d5a8) at /usr/src/debug/kglobalaccel-6.4.0git.20240618T012458~10f89e8/build/src/moc_kglobalaccel_component_interface.cpp:165
#26 0x00007f1364bf41b0 in OrgKdeKglobalaccelComponentInterface::qt_metacall (this=0x557164b28d20, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0x7ffceaf4d5a8) at /usr/src/debug/kglobalaccel-6.4.0git.20240618T012458~10f89e8/build/src/moc_kglobalaccel_component_interface.cpp:236
#27 0x00007f1363f86aef in QDBusConnectionPrivate::deliverCall (this=0x7f1358001670, object=0x557164b28d20, msg=..., metaTypes=<optimized out>, slotIdx=5) at /usr/src/debug/qtbase-everywhere-src-6.7.2/src/dbus/qdbusintegrator.cpp:1007
#28 0x00007f13621d1e1b in QObject::event (this=0x557164b28d20, e=0x7f135809bd80) at /usr/src/debug/qtbase-everywhere-src-6.7.2/src/corelib/kernel/qobject.cpp:1452
#29 0x00007f13645c2f6e in QApplicationPrivate::notify_helper (this=<optimized out>, receiver=0x557164b28d20, e=0x7f135809bd80) at /usr/src/debug/qtbase-everywhere-src-6.7.2/src/widgets/kernel/qapplication.cpp:3287
#30 0x00007f136218ec30 in QCoreApplication::notifyInternal2 (receiver=0x557164b28d20, event=0x7f135809bd80) at /usr/src/debug/qtbase-everywhere-src-6.7.2/src/corelib/kernel/qcoreapplication.cpp:1142
#31 0x00007f136218ec69 in QCoreApplication::sendEvent (receiver=<optimized out>, event=<optimized out>) at /usr/src/debug/qtbase-everywhere-src-6.7.2/src/corelib/kernel/qcoreapplication.cpp:1583
#32 0x00007f136218ef90 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x5571645d2550) at /usr/src/debug/qtbase-everywhere-src-6.7.2/src/corelib/kernel/qcoreapplication.cpp:1940
#33 0x00007f13623c2fe3 in postEventSourceDispatch (s=0x5571646b1cb0) at /usr/src/debug/qtbase-everywhere-src-6.7.2/src/corelib/kernel/qeventdispatcher_glib.cpp:244
#34 0x00007f13612fc740 in g_main_dispatch (context=0x7f1358000f00) at ../glib/gmain.c:3344
#35 g_main_context_dispatch_unlocked (context=context@entry=0x7f1358000f00) at ../glib/gmain.c:4152
#36 0x00007f13612fe388 in g_main_context_iterate_unlocked (context=context@entry=0x7f1358000f00, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at ../glib/gmain.c:4217
#37 0x00007f13612fea3c in g_main_context_iteration (context=0x7f1358000f00, may_block=1) at ../glib/gmain.c:4282
#38 0x00007f13623c1adc in QEventDispatcherGlib::processEvents (this=0x5571645e8e40, flags=...) at /usr/src/debug/qtbase-everywhere-src-6.7.2/src/corelib/kernel/qeventdispatcher_glib.cpp:394
#39 0x00007f13621993db in QEventLoop::exec (this=0x7ffceaf4db70, flags=...) at /usr/src/debug/qtbase-everywhere-src-6.7.2/src/corelib/global/qflags.h:34
#40 0x00007f1362192bb6 in QCoreApplication::exec () at /usr/src/debug/qtbase-everywhere-src-6.7.2/src/corelib/global/qflags.h:74
#41 0x00007f13629e7e2c in QGuiApplication::exec () at /usr/src/debug/qtbase-everywhere-src-6.7.2/src/gui/kernel/qguiapplication.cpp:1926
#42 0x00007f13645bfff5 in QApplication::exec () at /usr/src/debug/qtbase-everywhere-src-6.7.2/src/widgets/kernel/qapplication.cpp:2555
#43 0x000055713d419e55 in main (argc=<optimized out>, argv=<optimized out>) at /usr/src/debug/plasma-workspace-6.1.80git.20240630T094540~c68c9de3/shell/main.cpp:188
Comment 16 Nate Graham 2024-07-24 18:52:17 UTC
*** Bug 464989 has been marked as a duplicate of this bug. ***
Comment 17 David Edmundson 2024-08-01 11:31:49 UTC

*** This bug has been marked as a duplicate of bug 490791 ***