Bug 475480

Summary:	Plasma crashed after interacting with Wi-Fi
Product:	[I don't know] kde	Reporter:	Qanety <vorobyov.dimka>
Component:	general	Assignee:	Unassigned bugs <unassigned-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	crash	CC:	nate
Priority:	NOR	Keywords:	drkonqi
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Debian stable
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	New crash information added by DrKonqi

Description Qanety 2023-10-11 18:57:41 UTC

Application: plasmashell (5.27.5)

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

-- Information about the crash:
Plasma crashed after interacting with Wi-Fi. For a while, my Wi-Fi suddenly turned off, so after reconnecting it, I decided to turn it off to protect myself. But after Plasma crashed.

The reporter is unsure if this crash is reproducible.

-- Backtrace (Reduced):
#5  0x00007fb46e277c86 in QtQml::qmlExecuteDeferred(QObject*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
#6  0x00007fb46e749059 in QQuickTransition::prepare(QList<QQuickStateAction>&, QList<QQmlProperty>&, QQuickTransitionManager*, QObject*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5
#7  0x00007fb46e73e997 in QQuickTransitionManager::transition(QList<QQuickStateAction> const&, QQuickTransition*, QObject*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5
#8  0x00007fb46ccdd50d in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x00007fb46d962fae in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.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 Qanety 2023-10-11 18:57:43 UTC

Created attachment 162227 [details]
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.

Comment 2 Nate Graham 2023-10-12 20:19:10 UTC


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