Bug 472592

Summary: Desktop crashed on network manager icon click
Product: [Plasma] plasmashell Reporter: evgeny <me>
Component: generic-crashAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED DUPLICATE    
Severity: crash CC: ben, qydwhotmail
Priority: NOR Keywords: drkonqi
Version: 5.27.5   
Target Milestone: 1.0   
Platform: Debian stable   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: New crash information added by DrKonqi

Description evgeny 2023-07-24 19:22:45 UTC
Application: plasmashell (5.27.5)

Qt Version: 5.15.8
Frameworks Version: 5.103.0
Operating System: Linux 6.1.0-10-amd64 x86_64
Windowing System: X11
Distribution: Debian GNU/Linux 12 (bookworm)
DrKonqi: 5.27.5 [CoredumpBackend]

-- Information about the crash:
I was connected to Wi-Fi + OpenVPN.
Then I attached ethernet cable. 
Few seconds later, I opened the networks panel in the statusbar, and that was the moment when it crashed.

The reporter is unsure if this crash is reproducible.

-- Backtrace (Reduced):
#13 0x00007f773f9ca808 in QDBusArgument::beginMap() const () from /lib/x86_64-linux-gnu/libQt5DBus.so.5
[...]
#15 0x00007f773f9cf8a5 in QDBusMetaType::demarshall(QDBusArgument const&, int, void*) () from /lib/x86_64-linux-gnu/libQt5DBus.so.5
[...]
#17 0x00007f773eedd6f0 in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x00007f773fb62fae in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#19 0x00007f773eeb16f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5


Reported using DrKonqi
This report was filed against 'kde' because the product 'plasmashell' could not be located in Bugzilla. Add it to drkonqi's mappings file!
Comment 1 evgeny 2023-07-24 19:22:46 UTC
Created attachment 160507 [details]
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.
Comment 2 Fushan Wen 2023-08-06 03:50:49 UTC
https://bugreports.qt.io/browse/QTBUG-88498

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