Bug 475035

Summary:	Plasma Crashed & Restarted After Reboot and Login
Product:	[Plasma] plasmashell	Reporter:	Eric R <aer0usa>
Component:	general	Assignee:	Plasma Bugs List <plasma-bugs>
Status:	RESOLVED DUPLICATE
Severity:	crash	CC:	kde, nate
Priority:	NOR	Keywords:	drkonqi
Version:	5.27.8
Target Milestone:	1.0
Platform:	Neon
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	New crash information added by DrKonqi

Description Eric R 2023-09-29 23:36:59 UTC

Application: plasmashell (5.27.8)

Qt Version: 5.15.10
Frameworks Version: 5.110.0
Operating System: Linux 6.2.0-33-generic x86_64
Windowing System: X11
Distribution: KDE neon 5.27
DrKonqi: 5.27.8 [CoredumpBackend]

-- Information about the crash:
I had just rebooted KDE Neon, and logged in. Plasma crashed after the desktop image showed, but before the panel showed.

The reporter is unsure if this crash is reproducible.

-- Backtrace (Reduced):
#6  0x00007f4e928e7738 in std::__atomic_base<QThreadData*>::load(std::memory_order) const (__m=std::memory_order_relaxed, this=0x159) at /usr/include/c++/11/bits/atomic_base.h:818
#7  std::atomic<QThreadData*>::load(std::memory_order) const (__m=std::memory_order_relaxed, this=0x159) at /usr/include/c++/11/atomic:578
#8  QAtomicOps<QThreadData*>::loadRelaxed<QThreadData*>(std::atomic<QThreadData*> const&) (_q_value=<error reading variable: Cannot access memory at address 0x159>) at ../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:239
#9  QBasicAtomicPointer<QThreadData>::loadRelaxed() const (this=0x159) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:248
#10 QObject::thread() const (this=this@entry=0x55676e240930) at kernel/qobject.cpp:1520


Reported using DrKonqi

Comment 1 Eric R 2023-09-29 23:37:00 UTC

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

DrKonqi auto-attaching complete backtrace.

Comment 2 Eric R 2023-09-30 01:57:02 UTC

I have rebooted a couple times since this reported crash, and I have not been able to reproduce it. The second of those reboots was after an update by Discover.

Comment 3 Nate Graham 2023-10-11 19:26:57 UTC


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