krunner dies when second monitor is attached, before startup of machine

[Uqbar]

How to reproduce:

1. attach external monitor to HDMI port
2. turn machine on
3. wait for KDE login (sddm)
4. enter credentials

What happens:

A dialog notifies about krunner having died unexpectedly.
After you hit "OK" everything goes on normally

Expected bahavior:
Normal operations (that is, no krunner death)

It happens ALWAYS.
It doesn't happen when:

1. I use the laptop screen alone
2. I plug the external monitor after login.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: plasma-workspace 4:5.4.2-0ubuntu1
ProcVersionSignature: Ubuntu 4.2.0-23.28-lowlatency 4.2.6
Uname: Linux 4.2.0-23-lowlatency x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CurrentDesktop: KDE
Date: Thu Jan 7 10:09:00 2016
InstallationDate: Installed on 2015-10-23 (75 days ago)
InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: plasma-workspace
UpgradeStatus: No upgrade log present (probably fresh install)

[Flames_in_Paradise (ellisistfroh-deactivatedaccount)]

hi!

Did U search on the KDE-bugbase, for "krunner" ?

Step2 - https://bugs.kde.org/component-report.cgi?product=krunner

Looks like this has been adressed there already:

(https://bugs.kde.org/show_bug.cgi?id=353129)

<OT> Hint: put the cursor into the search-field at the KDE-bugbase webpage. Go to the search-field in your browser. Add the bugbase to your search options Get easier acces though to it <OT>.

[Flames_in_Paradise (ellisistfroh-deactivatedaccount)]

hi!

Did U search on the KDE-bugbase, for "krunner" ?

Step2 - https://bugs.kde.org/component-report.cgi?product=krunner

Looks like this has been adressed there already:

(https://bugs.kde.org/show_bug.cgi?id=353129)

<OT> Hint: put the cursor into the search-field at the KDE-bugbase webpage. Go to the search-field in your browser. Add the bugbase to your search options Get easier acces though to it <OT>.

[Uqbar (uqbar)]

Nope. I searched into Launchpad alone: that'd not be the first time such bugs have been introduced by the packager.
The bug has been "created" and "reported" upstream, not addressed (in the sense worked on/solved) at all.

[Flames_in_Paradise (ellisistfroh-deactivatedaccount)]

Please don't feel refused, but I really don't think this has to do with packaging. Especially then you could add yourself to the mentioned bug-report on KDE.

For two reasons:
- draw more attention on this bug
- given the opportunity you can grant valuable debug information, it may help to resolve it with faster speed.

Hence I'm not in the position to justify about the priorities that developers have, having said so I'm not even aware if it will be fixed in a newer version of Kubuntu (aka Development-Release 16.04). And I've definetly justified my expectations in regards to getting fixes in STS-releases with a lifecycle of just 9 month. Whereas I would think this needed a mentioning in Release-Notes, as this should not simply be bypassed and left aside since evermore users have a multi-monitor setuo-environment - though the dev doesn't. Maybe we should poke him that this is even possible within a testing environment VirtualBox? :-)

It's also an unreveilled secret (but true) that the underlying Qt-Version has great influence on this. So personally I'm looking for the landing of Qt-5.6 in Xenial 16.04. If needed I can pass on more information on this. Wily has just disqualiyfied at this early stage of swapping from KDE4 to KDE5 with multi-monitor setup env. But it doesn't exlude testing & bug-reporting.

I could not dare to have the my laptop in the Docking-Station in an unreliable condition - so I stayed there with 14.04. It's not perfect but sufficient. And since it's older HW I need to run it in OpenGLES. LTS-Versions are ALWAYS the one+only recommondation for production-environment.

After years of being a Kubuntu-USER (with all ups & downs), I've come to the conclusion that the greatest efforts are achieved if U take part in early testing-LTS+1. If possible, things can be patched backwards or SRU-ed then. -> (bug #1531499 - Backport request SDDM 0.13 (needs some more sorting out b4fore it can happen) This seems to be the package in question, since thats the stage where it happens, for my thinking.

Having written quite more than what belongs in a bug-report - since I felt it's fair to share on certain items of "frustration" in bug-reports too - Coming to a conclusion : Dev' are not the most communicative people - solutions maybe having background activities -which are not visible - (not even communicated) AND they have to "household" their level of energy like anybody else - apart from the fact that we all put in a certain amount of leisure-time to keep the FOSS - ideals running.

search-item: https://bugs.kde.org/component-report.cgi?product=plasmashell

This bugreport could also reference: (https://bugs.kde.org/show_bug.cgi?id=355582)

P.S.:
<OT> with reference to your LP-profile - With a certain love to sailing it would justfy smooth seas as boring | <OT>