Bug 352488

Summary:	kded5 crash when plugging external monitor
Product:	[Plasma] KScreen	Reporter:	Loïc Yhuel <loic.yhuel>
Component:	common	Assignee:	Daniel Vrátil <dvratil>
Status:	RESOLVED WORKSFORME
Severity:	crash	CC:	elmatyf, nate
Priority:	NOR
Version:	5.4.0
Target Milestone:	---
Platform:	Fedora RPMs
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Loïc Yhuel 2015-09-09 17:14:26 UTC

#5  0x00007f520e3dcc50 in KScreen::Output::id() const (this=0x0) at ../../src/output.cpp:146
#6  0x00007f5207df351d in Generator::laptop(QMap<int, QSharedPointer<KScreen::Output> >&) (this=this@entry=0x22008a0, connectedOutputs=...) at ../../kded/generator.cpp:436
#7  0x00007f5207df495b in Generator::idealConfig(QSharedPointer<KScreen::Config> const&) (this=0x22008a0, currentConfig=...) at ../../kded/generator.cpp:106
#8  0x00007f5207de0f2f in KScreenDaemon::applyIdealConfig() (this=this@entry=0x2054130) at ../../kded/daemon.cpp:177
#9  0x00007f5207de12bb in KScreenDaemon::applyConfig() (this=0x2054130) at ../../kded/daemon.cpp:158
#10 0x00000035008b1fe7 in QMetaObject::activate(QObject*, int, int, void**) (a=0x7fffedc83110, r=0x2054130, this=<optimized out>) at ../../src/corelib/kernel/qobject_impl.h:124
#11 0x00000035008b1fe7 in QMetaObject::activate(QObject*, int, int, void**) (sender=sender@entry=0x205a6b0, signalOffset=<optimized out>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at kernel/qobject.cpp:3703
#12 0x00000035008b2957 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=sender@entry=0x205a6b0, m=m@entry=0x3500cc98c0 <QTimer::staticMetaObject>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at kernel/qobject.cpp:3583
#13 0x0000003500931820 in QTimer::timeout(QTimer::QPrivateSignal) (this=this@entry=0x205a6b0) at .moc/moc_qtimer.cpp:197

Note that I'm testing https://bugs.freedesktop.org/show_bug.cgi?id=91929 to fix hotplug events, so "Note the modelist is left unchanged" suggests perhaps mode might be NULL in Generator::biggestOutput, which would explain biggest holding a NULL pointer.

Reproducible: Sometimes

Steps to Reproduce:
Plug external monitor

Comment 1 Matias Fernandez 2015-10-22 17:04:08 UTC

I'm having a similar problem: https://bugs.kde.org/show_bug.cgi?id=354197

Comment 2 Justin Zobel 2021-03-10 00:32:20 UTC

Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.

Comment 3 Nate Graham 2022-11-08 19:07:35 UTC

No response; closing.