[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps

[Vitaliy Gorbunov via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=340267

Vitaliy Gorbunov  changed:

   What|Removed |Added

 CC||vit.gorbu...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps

[David Edmundson via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=340267

David Edmundson  changed:

   What|Removed |Added

 CC||perenque@gmail.com

--- Comment #76 from David Edmundson  ---
*** Bug 369183 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps

[Dainius Masiliūnas via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=340267

--- Comment #75 from Dainius Masiliūnas  ---
For what it's worth, after updating to Plasma 5.7.3 (still on Qt 5.6.1), I no
longer get any crashes when I put my DisplayPort monitor to sleep. So I can
indeed consider this issue fixed now.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps

[Michael Butash via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=340267

--- Comment #74 from Michael Butash  ---
Relevant note - the middle display that acted weird mostly was set to be the
primary display as well.  Prior, it acted like the task bar was polarized to
pretty much anything *but* it, but really odd disconnecting that one caused the
most odd effect, possibly due to being set as the primary.

I get lots of really odd compositing issues, mostly due to being a gigantic
framebuffer some video cards seem to not handle well ala 11520x2160.  I suspect
at times gpu processing contributes to weirdness, but not sure the graphic
diversity of the folks developing the platforms on.  I'm using AMD.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps

[Michael Butash via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=340267

--- Comment #73 from Michael Butash  ---
Running 5.7.2+p16.04+git* as of last night seems to be far better behaved,
putting windows back after shutting down my tv/displays, as well as
hard-disconnecting each.

Oddly though, I got weirdness when I was disconnecting each display in a test. 
Went sort of like this:

1) Disconnected far right display, port 0
  - display removed, migrated windows and desktop to adjacent displays
normally, worked as expected.
2) Disconnected middle display, port 1
  - Display removed, migrated windows, but wallpaper went blank on one of the
two remaining displays, and kwin seemed to fall out of compositing mode with
cairo-dock showing banded lines as a sign of compositing being off/broken. 
Plugged it back in, and it moved everything back with full wallpapers normally
as I would expect.
3) Disconnected Left display, port 2
  - Display removed, migrated windows and desktop to adjacent displays, behaved
normally.
4) Disconnected Left display, port 2 again, was going to test removing
multiples
  - Display removed and all screens went blank, none initializing and displays
showing no connected input sources.  Reconnected port 2, and all displays came
back.

Needless to say, it *sort of* works, but inconsistent.  Definitely an
improvement, but still seems to leave something to be desired.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps

[David Reid via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=340267

David Reid  changed:

   What|Removed |Added

 CC||dlr...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps

[Xapient via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=340267

--- Comment #72 from Xapient  ---
(In reply to Michael Butash from comment #70)

the behaviour you described concerning the plasma panel (taskbar) seems to be
fixed in plasma 5.7.3
i am using kubuntu with #neon repository and my panel stopped switching screens
...

the plasma-desktop-containment still has a problem with screens that go to
sleep and wake up again..   it sometimes stays black/inactive on one of the
screens..

because i think this is a different bug i openend another ticket here:
https://bugs.kde.org/show_bug.cgi?id=366207

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps

[Bart via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=340267

--- Comment #71 from Bart  ---
Created attachment 100444
  --> https://bugs.kde.org/attachment.cgi?id=100444=edit
drkonqi-screen

Not sure if this helps to show what the problem is, but when my desktop goes on
screen-saver, I get this error messages. The longer my screen stays in saver,
the more messages I get (you can see that there were 17 this time.)

If there is any other output I can provide, I'm glad to do so.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps

[Michael Butash via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=340267

--- Comment #70 from Michael Butash  ---
It is really confusing where to begin to troubleshoot it, as I can't tell how
much is related to kwin, plasmashell, or libqt underneath.  Especially the
first time having to dig into KDE behind the scenes, but I've really loved the
5.x generation enough to want to try to fix this.

The only thing I will still add, that seems loosely related is that when I do
get kwin to crash, which is now happening more, it still seems to lose its
sense of identity among applications bound to which display.  When triggered,
things like the wall papers shuffle every time monitors come and go, or when
kwin crashes in particular.  

Also my taskbar can never figure out what display to end up on despite what I
set the primary display to.  It does at first, but then, doesn't after time,
really almost randomly lands, but never where it's supposed to - very odd. 
Almost like a non-obvious display index is getting broken, but at qt, plasma,
or kwin, not sure as they all seem to use/contribute in some way.  Plasmoids as
well acted oddly, crashing, ghosting between displays, etc.  

All seem related to core multi-monitor function, as unplugging just one,
reshuffles things, fixing some, breaking/shuffling others.  Finding the root of
that "shuffling" or random landing of apps on display among identities seems
key.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps

[Christoph Cullmann via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=340267

Christoph Cullmann  changed:

   What|Removed |Added

 CC|cullm...@kde.org|

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps

[David Edmundson via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=340267

David Edmundson  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 CC||k...@davidedmundson.co.uk
 Status|REOPENED|RESOLVED

--- Comment #69 from David Edmundson  ---
Comment #56 is a different crash (dupe of 351507)

Comments #61 #62 and #63 are a completely different crash. (dupes of
https://bugs.kde.org/show_bug.cgi?id=343576) 

This has been reopened, but now the bug is a confusing mess.

I'm closing this as it it literally impossible to see what's what, and I don't
think there's anything new in here.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps

[Bart via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=340267

Bart  changed:

   What|Removed |Added

 CC||bart...@yahoo.com

--- Comment #68 from Bart  ---
+1 
I have the same issues, seems like a pretty nasty bug to resolve?

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps

[David Edmundson via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=340267

David Edmundson  changed:

   What|Removed |Added

 CC||jasonbailey1...@gmail.com
 CC||leon.bauer@gamesbestprice.c
   ||om

--- Comment #66 from David Edmundson  ---
*** Bug 366176 has been marked as a duplicate of this bug. ***

--- Comment #67 from David Edmundson  ---
*** Bug 365885 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps

[David Edmundson via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=340267

David Edmundson  changed:

   What|Removed |Added

 CC||jasonbailey1...@gmail.com

--- Comment #66 from David Edmundson  ---
*** Bug 366176 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps

[Xapient via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=340267

--- Comment #65 from Xapient  ---
(In reply to Michael Butash from comment #64)
> Mine has been surprisingly stable since upgrading to 5.7.2 and qt 5.7.0.  No
> crashes, all 3 being shut on and off in various orders, left off, and back
> on the next day.  It'd always be toast by morning and broken while off.

i also run the same software versions (kde neon) and turning a monitor off for
10 seconds and then on again seems to work for me too ! 

but going away for an hour and then coming back and waking up my screens (only
the screens go to sleep not the whole system) and plasma greets me with one
working screen and one black screen without a desktop containment (plasma panel
is still there but the rest is black and doesn't react to rightclicks)

so it seems something got fixed - but not everything :-(

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps

[Michael Butash via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=340267

--- Comment #64 from Michael Butash  ---
Mine has been surprisingly stable since upgrading to 5.7.2 and qt 5.7.0.  No
crashes, all 3 being shut on and off in various orders, left off, and back on
the next day.  It'd always be toast by morning and broken while off.

Not sure if related to the multi-monitors in some way, but still seems unstable
with longer use sessions over time.  I used window dimming + transparency, and
after 2 days of monitors on and off, was still functional, but windows wouldn't
un-dim and un-transparent when focused on.  Restarting kwin with shift-alt-f12
fixed it, but seems to start doing it again later.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=340267

--- Comment #63 from lbug...@gmail.com ---
Comment on attachment 100336
  --> https://bugs.kde.org/attachment.cgi?id=100336
Crash log

Crash happened after waking my monitor from sleep. Can be reproduced by waiting
or turning them off and back on. Using plasmashell 5.7 and Qt 5.6.1

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=340267

--- Comment #62 from lbug...@gmail.com ---
Comment on attachment 100336
  --> https://bugs.kde.org/attachment.cgi?id=100336
Crash log

Crash happened after waking my Monitors from sleep. Can be reliably reproduced
simply by turning the screen off and back on.
Using plasmashell 5.7 and Qt 5.6.1 on openSUSE Tumbleweed

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=340267

--- Comment #61 from mich...@karbach.org ---
Comment on attachment 100336
  --> https://bugs.kde.org/attachment.cgi?id=100336
Crash log

>Application: Plasma (plasmashell), signal: Segmentation fault
>Using host libthread_db library "/lib64/libthread_db.so.1".
>[Current thread is 1 (Thread 0x7f967013b8c0 (LWP 2376))]
>
>Thread 31 (Thread 0x7f95ae7f5700 (LWP 2700)):
>[KCrash Handler]
>#6  0x001b in ?? ()
>#7  0x7f95b7e97557 in Plotter::render (this=0x175d280) at 
>/usr/src/debug/kdeclarative-5.24.0/src/qmlcontrols/kquickcontrolsaddons/plotter.cpp:652
>#8  0x7f9669ff624c in QtPrivate::QSlotObjectBase::call (a=0x7f95ae7f4b10, 
>r=0x175d280, this=) at 
>../../src/corelib/kernel/qobject_impl.h:124
>#9  QMetaObject::activate (sender=sender@entry=0x4a5d020, 
>signalOffset=, local_signal_index=local_signal_index@entry=6, 
>argv=argv@entry=0x0) at kernel/qobject.cpp:3715
>#10 0x7f9669ff6757 in QMetaObject::activate 
>(sender=sender@entry=0x4a5d020, m=m@entry=0x7f966e22b1e0 
>, 
>local_signal_index=local_signal_index@entry=6, argv=argv@entry=0x0) at 
>kernel/qobject.cpp:3595
>#11 0x7f966ddf8133 in QQuickWindow::beforeRendering 
>(this=this@entry=0x4a5d020) at .moc/moc_qquickwindow.cpp:488
>#12 0x7f966ddfc69e in QQuickWindowPrivate::renderSceneGraph 
>(this=this@entry=0x2c815d0, size=...) at 
>/usr/src/debug/qtdeclarative-opensource-src-5.6.1/src/quick/items/qquickwindow.cpp:406
>#13 0x7f966ddce62f in QSGRenderThread::syncAndRender 
>(this=this@entry=0x228c7f0) at 
>/usr/src/debug/qtdeclarative-opensource-src-5.6.1/src/quick/scenegraph/qsgthreadedrenderloop.cpp:623
>#14 0x7f966ddd3bac in QSGRenderThread::run (this=0x228c7f0) at 
>/usr/src/debug/qtdeclarative-opensource-src-5.6.1/src/quick/scenegraph/qsgthreadedrenderloop.cpp:704
>#15 0x7f9669df12d8 in QThreadPrivate::start (arg=0x228c7f0) at 
>thread/qthread_unix.cpp:341
>#16 0x7f9668ee5474 in start_thread () from /lib64/libpthread.so.0
>#17 0x7f96696f63ed in clone () from /lib64/libc.so.6
>
>Thread 30 (Thread 0x7f93eeaec700 (LWP 783)):
>#0  0x7f9668eeb09f in pthread_cond_wait@@GLIBC_2.3.2 () from 
>/lib64/libpthread.so.0
>#1  0x7f9669df218b in QWaitConditionPrivate::wait 
>(time=18446744073709551615, this=0x474bb10) at 
>thread/qwaitcondition_unix.cpp:136
>#2  QWaitCondition::wait (this=this@entry=0x2dac2c8, 
>mutex=mutex@entry=0x2dac2c0, time=time@entry=18446744073709551615) at 
>thread/qwaitcondition_unix.cpp:208
>#3  0x7f966ddd33f5 in QSGRenderThreadEventQueue::takeEvent (wait=true, 
>this=0x2dac2b8) at 
>/usr/src/debug/qtdeclarative-opensource-src-5.6.1/src/quick/scenegraph/qsgthreadedrenderloop.cpp:236
>#4  QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0x2dac240) 
>at 
>/usr/src/debug/qtdeclarative-opensource-src-5.6.1/src/quick/scenegraph/qsgthreadedrenderloop.cpp:684
>#5  0x7f966ddd3cea in QSGRenderThread::run (this=0x2dac240) at 
>/usr/src/debug/qtdeclarative-opensource-src-5.6.1/src/quick/scenegraph/qsgthreadedrenderloop.cpp:713
>#6  0x7f9669df12d8 in QThreadPrivate::start (arg=0x2dac240) at 
>thread/qthread_unix.cpp:341
>#7  0x7f9668ee5474 in start_thread () from /lib64/libpthread.so.0
>#8  0x7f96696f63ed in clone () from /lib64/libc.so.6
>
>Thread 29 (Thread 0x7f93ef2ed700 (LWP 29935)):
>#0  0x7f9668eeb09f in pthread_cond_wait@@GLIBC_2.3.2 () from 
>/lib64/libpthread.so.0
>#1  0x7f9669df218b in QWaitConditionPrivate::wait 
>(time=18446744073709551615, this=0x40eded0) at 
>thread/qwaitcondition_unix.cpp:136
>#2  QWaitCondition::wait (this=this@entry=0x36852e8, 
>mutex=mutex@entry=0x36852e0, time=time@entry=18446744073709551615) at 
>thread/qwaitcondition_unix.cpp:208
>#3  0x7f966ddd33f5 in QSGRenderThreadEventQueue::takeEvent (wait=true, 
>this=0x36852d8) at 
>/usr/src/debug/qtdeclarative-opensource-src-5.6.1/src/quick/scenegraph/qsgthreadedrenderloop.cpp:236
>#4  QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0x3685260) 
>at 
>/usr/src/debug/qtdeclarative-opensource-src-5.6.1/src/quick/scenegraph/qsgthreadedrenderloop.cpp:684
>#5  0x7f966ddd3cea in QSGRenderThread::run (this=0x3685260) at 
>/usr/src/debug/qtdeclarative-opensource-src-5.6.1/src/quick/scenegraph/qsgthreadedrenderloop.cpp:713
>#6  0x7f9669df12d8 in QThreadPrivate::start (arg=0x3685260) at 
>thread/qthread_unix.cpp:341
>#7  0x7f9668ee5474 in start_thread () from /lib64/libpthread.so.0
>#8  0x7f96696f63ed in clone () from /lib64/libc.so.6
>
>Thread 28 (Thread 0x7f93feffc700 (LWP 6989)):
>#0  0x7f9668eeb09f in pthread_cond_wait@@GLIBC_2.3.2 () from 
>/lib64/libpthread.so.0
>#1  0x7f9669df218b in QWaitConditionPrivate::wait 
>(time=18446744073709551615, this=0x4eaf1e0) at 
>thread/qwaitcondition_unix.cpp:136
>#2  QWaitCondition::wait (this=this@entry=0x23b3278, 
>mutex=mutex@entry=0x23b3270, time=time@entry=18446744073709551615) at 
>thread/qwaitcondition_unix.cpp:208
>#3  0x7f966ddd33f5 in 

[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=340267

lbug...@gmail.com changed:

   What|Removed |Added

 CC||lbug...@gmail.com

--- Comment #60 from lbug...@gmail.com ---
Created attachment 100336
  --> https://bugs.kde.org/attachment.cgi?id=100336=edit
Crash log

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps

[Konrad Materka via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=340267

--- Comment #59 from Konrad Materka  ---
I have the same back trace but in different situation. Probably cause is the
same. In my situation it is always reproducible. It happens when I disable and
enable screen again when it was affected by:
https://bugs.kde.org/show_bug.cgi?id=353975 (screen is active but just black -
no background or any other plasma widgets).

I know that it might be different situation, but my guess is that during screen
initialization it tries to delete old configuration that was not fully
initialized. Can it happen when configuration of the same monitor changes
quickly?

Running Neon User 5.7.1 with latest stable Plasma 5.7.1, Qt 5.7


Crash is from here:
#7  0x0043fe1f in ShellCorona::addOutput (this=0x7a3040,
screen=0x43b8bb0) at /workspace/build/shell/shellcorona.cpp:862
QAction *removeAction =
containment->actions()->action(QStringLiteral("remove"));
if (removeAction) {
removeAction->deleteLater();
}
#6  Plasma::Applet::actions (this=this@entry=0x0) at
/workspace/build/src/plasma/applet.cpp:607
KActionCollection *Applet::actions() const
{
return d->actions;
}

Variable d must be already deallocated or not initialized. Is it possible that
containment is not fully initialized or it is a dangling pointer? After quick
look at the code I was not able to find such situation.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps

[Konrad Materka via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=340267

Konrad Materka  changed:

   What|Removed |Added

 CC||kmate...@wp.pl

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps

[Kristian Karl via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=340267

--- Comment #58 from Kristian Karl  ---
I'm running the latest from the NEON repo (http://archive.neon.kde.org/unstable
xenial main), and the problems described in the bug report are fixed.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps

[Michael Butash via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=340267

--- Comment #57 from Michael Butash  ---
Are there any repo's about with 5.6.x components for testing?  I found ubuntu's
landing-11 overlay with 5.6.0, but it seems more broken than 5.5 default with
kubuntu 16.04.

Otherwise, is there a recommended method of rebuilding the packages to test
someone can point me at?  Has there been any progress from the other reports
that have identified the problem yet?

I'm at the point I just leave the monitors on most nights, but they create a
lot of heat and power usage that i'd love to just flip them off without having
to reboot daily as a result to stabilize things.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps

[Marco Martin via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=340267

--- Comment #56 from Marco Martin  ---
again, pasting BT inline :)

Thread 1 (Thread 0x7fb6687cf900 (LWP 29453)):
[KCrash Handler]
#6  0x7fb666924d10 in Plasma::Applet::actions() const (this=this@entry=0x0)
at /usr/src/debug/plasma-framework-5.22.0/src/plasma/applet.cpp:611
#7  0x00440e73 in
ShellCorona::addOutput(QSharedPointer const&)
(this=this@entry=0xc2ab20, output=...) at
/usr/src/debug/plasma-workspace-5.6.4/shell/shellcorona.cpp:909
#8  0x00440fef in ShellCorona::outputEnabledChanged() (this=0xc2ab20)
at /usr/src/debug/plasma-workspace-5.6.4/shell/shellcorona.cpp:802
#9  0x7fb6624d124c in QMetaObject::activate(QObject*, int, int, void**)
(a=0x7fffc8cdb0c0, r=0xc2ab20, this=) at
../../src/corelib/kernel/qobject_impl.h:124
#10 0x7fb6624d124c in QMetaObject::activate(QObject*, int, int, void**)
(sender=0x100f4b0, signalOffset=, local_signal_index=, argv=) at kernel/qobject.cpp:3715
#11 0x7fb6675df104 in
KScreen::Output::apply(QSharedPointer const&) () at
/usr/lib64/libKF5Screen.so.7
#12 0x7fb6675c3406 in
KScreen::Config::apply(QSharedPointer const&) () at
/usr/lib64/libKF5Screen.so.7
#13 0x7fb6675cfc26 in
KScreen::ConfigMonitor::Private::updateConfigs(QSharedPointer
const&) () at /usr/lib64/libKF5Screen.so.7
#14 0x7fb6675d172d in
KScreen::ConfigMonitor::Private::edidReady(QDBusPendingCallWatcher*) () at
/usr/lib64/libKF5Screen.so.7
#15 0x7fb6624d124c in QMetaObject::activate(QObject*, int, int, void**)
(a=0x7fffc8cdb500, r=0xe88040, this=) at
../../src/corelib/kernel/qobject_impl.h:124
#16 0x7fb6624d124c in QMetaObject::activate(QObject*, int, int, void**)
(sender=0x10016d0, signalOffset=,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fffc8cdb500)
at kernel/qobject.cpp:3715
#17 0x7fb6624d1757 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) (sender=, m=m@entry=0x7fb6635136c0
,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fffc8cdb500)
at kernel/qobject.cpp:3595
#18 0x7fb6632f8a1f in
QDBusPendingCallWatcher::finished(QDBusPendingCallWatcher*) (this=, _t1=) at .moc/moc_qdbuspendingcall.cpp:152
#19 0x7fb6632f8b18 in QDBusPendingCallWatcher::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) (this=) at
qdbuspendingcall.cpp:488
#20 0x7fb6632f8b18 in QDBusPendingCallWatcher::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) (_o=, _c=,
_id=, _a=) at .moc/moc_qdbuspendingcall.cpp:83
#21 0x7fb6624d1cf9 in QObject::event(QEvent*) (this=0x10016d0, e=) at kernel/qobject.cpp:1256
#22 0x7fb663679aec in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=, receiver=0x10016d0, e=0x7fb64403f590) at
kernel/qapplication.cpp:3804
#23 0x7fb66367ef8f in QApplication::notify(QObject*, QEvent*)
(this=0x7fffc8cdbbf0, receiver=0x10016d0, e=0x7fb64403f590) at
kernel/qapplication.cpp:3561
#24 0x7fb6624a3a20 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x10016d0, event=event@entry=0x7fb64403f590) at
kernel/qcoreapplication.cpp:1015
#25 0x7fb6624a599c in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) (event=0x7fb64403f590, receiver=) at
kernel/qcoreapplication.h:225
#26 0x7fb6624a599c in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) (receiver=receiver@entry=0x0, event_type=event_type@entry=0,
data=0xb149f0) at kernel/qcoreapplication.cpp:1650
#27 0x7fb6624a5e58 in QCoreApplication::sendPostedEvents(QObject*, int)
(receiver=receiver@entry=0x0, event_type=event_type@entry=0) at
kernel/qcoreapplication.cpp:1508
#28 0x7fb6624f96c3 in postEventSourceDispatch(GSource*, GSourceFunc,
gpointer) (s=0xb7e930) at kernel/qeventdispatcher_glib.cpp:270
#29 0x7fb65e25ee57 in g_main_context_dispatch () at
/usr/lib64/libglib-2.0.so.0
#30 0x7fb65e25f0c0 in  () at /usr/lib64/libglib-2.0.so.0
#31 0x7fb65e25f16c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#32 0x7fb6624f9acf in
QEventDispatcherGlib::processEvents(QFlags)
(this=0xb973d0, flags=...) at kernel/qeventdispatcher_glib.cpp:417
#33 0x7fb6624a176a in
QEventLoop::exec(QFlags)
(this=this@entry=0x7fffc8cdbaa0, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:204
#34 0x7fb6624a9f6c in QCoreApplication::exec() () at
kernel/qcoreapplication.cpp:1285
#35 0x7fb6629f2b6c in QGuiApplication::exec() () at
kernel/qguiapplication.cpp:1607
#36 0x7fb663676b25 in QApplication::exec() () at
kernel/qapplication.cpp:2979
#37 0x0041d9ec in main(int, char**) (argc=,
argv=) at
/usr/src/debug/plasma-workspace-5.6.4/shell/main.cpp:139

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps

[Dainius Masiliūnas via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=340267

--- Comment #55 from Dainius Masiliūnas  ---
Created attachment 99797
  --> https://bugs.kde.org/attachment.cgi?id=99797=edit
plasmashell-20160702-094825.kcrash

Tested with Qt 5.6.1, still crashes. See attached log.
The Plasma version is 5.6.4.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps

[Michael Butash via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=340267

--- Comment #54 from Michael Butash  ---
Interestingly enough I installed kde-backports and dist-upgraded to pull down
plasma 5.6.5, but that kept qt at 5.5.1.  I gave it a stress test flipping my
3x displays on and off in various orders, and it's behaving a far sight better
than it had, and hasn't crashed.  

The only anomalies now so far currently is it still doesn't put the displays
back in the right places and offsets, which results in me having to move them
about to realign after the third on/off and it doesn't always move the kde
panel to the primary display, sometimes even flickering back and forth.

I'm going to see if I can find where to get libqt5 in 5.6.1 or higher too, but
this seems to indicate it isn't entirely a Qt problem.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps

[Soren Harward via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=340267

--- Comment #53 from Soren Harward  ---
(In reply to Christoph Feck from comment #50)
> Can you please test with Qt 5.6.1 ?

Still getting crashes in plasmashell with qt-5.6.1 and plasma-5.6.5, though
less frequently.  Now it seems to happen only when the displays are turned off
for an extended period of time; I'll do some more testing and see if I can
figure out exactly how long "an extended period of time" actually is.

krunner and kwin_x11 also crashed frequently before qt-5.6.1 and plasma-5.6.5,
and haven't done so since.

The xrandr command I listed in comment #41 doesn't cause plasmashell to crash
anymore, but when I run it the panel moves back and forth between monitors
unpredictably, even when I set one of the outputs as "--primary" in xrandr, and
even when widgets are locked.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=340267

--- Comment #52 from mich...@karbach.org ---
Me too, I know it is off-topic, but I have switched all desktops (7) in my work
group, from KDE to gnome. It is unbelievable that such an important bug is not
fixed in more than one year.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps

[Michael Butash via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=340267

Michael Butash  changed:

   What|Removed |Added

 CC||mich...@butash.net

--- Comment #51 from Michael Butash  ---
Nastiness, stuck with older qt in ubuntu 16.04, had to stop using kde since it
forced all sorts of oddities around qt-based anything with 3x 4k hdmi tv's that
would come and go when I'd power them off for the night (no dpms-ish features
for hdmi it seems).  Plasma guys blame qt, but they thrash and die in many ugly
ways as a result that seem unnatural despite inadequacies in qt like this.  

Really liked plasma otherwise, but had to go back to something that worked. 
I'm finding cinnamon doesn't suck with modern mesa/radeon drivers vs
proprietary fglrx+compositing hell.  We need this fix asap in older kde distros
for mobility and big-4k-tv love again.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps

[Christoph Feck via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=340267

Christoph Feck  changed:

   What|Removed |Added

 CC||cf...@kde.org

--- Comment #50 from Christoph Feck  ---
Can you please test with Qt 5.6.1 ?

Recent backtraces are bug 351507, but the original issue might also be fixed
with newest Qt.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps

[carl via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=340267

carl  changed:

   What|Removed |Added

 CC||cxx...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps

[Dainius Masiliūnas via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=340267

--- Comment #49 from Dainius Masiliūnas  ---
Created attachment 99081
  --> https://bugs.kde.org/attachment.cgi?id=99081=edit
plasmashell-20160519-192638.kcrash.txt

Confirmed, Plasma still crashes when the monitor is turned off with Qt 5.6. A
new crash log from DrKonqi is attached.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps

[Bob Wya via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=340267

Bob Wya  changed:

   What|Removed |Added

 CC||bob.mt@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps

[Paul via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=340267

Paul  changed:

   What|Removed |Added

 CC||spamproof707-bugs-kde@yahoo
   ||.com

--- Comment #48 from Paul  ---
This was first reported on 2014 and still no fix, on a Long Term Release no
less.

I can confirm this is still present on Plasma 5.5.5 and Qt 5.5.1 and Kubuntu
16.04, using two monitors with displayport and nvidia-364. Whenever the
monitors go to sleep and wake up, plasma is dead and no bug report window
appears nor does it restart. Like comment 40 mentioned alt + f2, killall
plasmashell and kstart plasmashell restores the interface.

Sometimes the dual monitor setup gets messed up as well and you have to redo
it.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps

[Josiah Barber via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=340267

Josiah Barber  changed:

   What|Removed |Added

 CC||josiah.bar...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps

[Xapient via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=340267

--- Comment #47 from Xapient  ---
i just testet qt5.6.0 - still the same..  plasma thinks the sleeping screen is
gone forever .. 
i cant reproduce this everytime..  

tried to reconfigure the screens but nothing ...  only restarting plasma helps

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps

[Xapient via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=340267

--- Comment #46 from Xapient  ---
is this the same bug and reason for this behaviour? 

https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1548766

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps

[Xapient via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=340267

--- Comment #45 from Xapient  ---
well.. it is no displayport issue either..  i'm using dvi and hdmi ports and
the same thing happens..

a monitor goes to sleep (or is turned off) and plasma says bye bye (on
dualscreen it sometimes happens that one of the two screens still shows the
background and is reacting to rightclick.. that's the weirdest thing of all - a
partial crash? )


i'm really stuck here..  on 3 notebooks and 8 dell machines i testet the newest
version there is no problem at all...

so what exactly is the reason for this bug ? !  and why didn't it happen on
kubuntu 15.10 ?

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps

[E . Hakan Duran via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=340267

--- Comment #44 from E. Hakan Duran  ---
On Monday, April 25, 2016 8:25:26 PM CDT Soren Harward via KDE Bugzilla wrote:
> https://bugs.kde.org/show_bug.cgi?id=340267
> 
> --- Comment #43 from Soren Harward  ---
> (In reply to Xapient from comment #42)
> 
> > could this be an intel driver issue after all?
> 
> No.  I'm using the amdgpu drivers.

No, I am using Nvidia drivers.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps

[Soren Harward via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=340267

--- Comment #43 from Soren Harward  ---
(In reply to Xapient from comment #42)
> could this be an intel driver issue after all?

No.  I'm using the amdgpu drivers.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps

[Xapient via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=340267

--- Comment #42 from Xapient  ---
i just tried it with another pc and HDMI connection..  same problem..  the only
thing those two pcs have in common is the intelHD graphics card...could
this be an intel driver issue after all?

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps

[Oleg Sidorkin via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=340267

Oleg Sidorkin  changed:

   What|Removed |Added

 CC||osidor...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps

[Soren Harward via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=340267

Soren Harward  changed:

   What|Removed |Added

 CC||stharw...@gmail.com
 Resolution|UPSTREAM|---
 Status|RESOLVED|REOPENED

--- Comment #41 from Soren Harward  ---
Still crashing with plasmashell 5.6.3 and Qt 5.6.0.  Running the following
crashes plasmashell every single time:

$ xrandr --output DisplayPort-2 --off --output DisplayPort-3 --off && sleep 0.2
&& xrandr --output DisplayPort-2 --preferred --output DisplayPort-3 --preferred
--right-of DisplayPort-2

If I bring up krunner using +, krunner immediately crashes (this
didn't happen before 5.6.3), which makes restarting plasmashell is even more
difficult :(

Upstream seems to think the underlying Qt bug is fixed (
https://bugreports.qt.io/browse/QTBUG-42985 ), so it looks like this is
something that needs to be addressed in KDE-land.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps

[Xapient via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=340267

--- Comment #40 from Xapient  ---
@root:   this only delivers plasma 5.5.5 which is already in the default repos
and doesn't solve the problem :(

the moment one of the screens powers down plasma crashes and does not restart.

hitting alt+f2 (starting krunner) and executing "killall plasmashell" and then
"plasmashell" now restarts the plasmashell properly..

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps

[rооt via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=340267

--- Comment #39 from rооt  ---
Xapient Try this ppa
https://launchpad.net/~kubuntu-ppa/+archive/ubuntu/staging-plasma
it works for me
and may help you

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps

[Xapient via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=340267

--- Comment #38 from Xapient  ---
i have to correct myself...  in my case it absolutely doesn't matter if i
disconnect(poweroff) a DVI or HDMI or DisplayPort screen.. plasma crashes
everytime!

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps

[Xapient via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=340267

Xapient  changed:

   What|Removed |Added

 CC||xapi...@gmx.net

--- Comment #37 from Xapient  ---
plasma 5.5.4 (kubuntu 16.04) 
qt 5.5.1

everytime one of the two monitors goes to sleep plasma crashes..  kwin is still
working so i'm able to continue with my work but plasma is not respawning and
i'm not able to restart it..  
no error message whatsoever.


if this is resolved in upstream (as mentioned in the description)  i really
hope they will somehow backport the bugfix otherwise kubuntu 16.04 will not
support displayport monitors at all..  this is an absolut no-go

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps

[Christoph via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=340267

--- Comment #36 from Christoph  ---
kwin 5.6.1
plasmashell 5.6.1

kscreen.xcb.helper / kscreen.xrandr treats the monitor in DisplayPort which is
in PowerSafe as disconnected and resets my monitor-config. Widgets are moved to
the MainScreen.
Mousemove activates the screen after a short flickering, sometimes plasmashell
crashes.
All widgets / taskbar remain on the MainScreen.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps

[Christoph via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=340267

Christoph  changed:

   What|Removed |Added

 CC||w...@psitrax.de

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps

[Robert Grasböck via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=340267

Robert Grasböck  changed:

   What|Removed |Added

 CC||m...@djtulan.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=340267

valdi...@gmail.com changed:

   What|Removed |Added

 CC||valdi...@gmail.com

--- Comment #35 from valdi...@gmail.com ---
With Qt 5.6.0 it's much better: so far I never got it to crash that hard that
the whole session is crashed, but plasma (plasmashell) is still crashes, even
in KDE 5.6.0.


#0  0x760da270 in Plasma::Applet::actions() const () from
/usr/lib/libKF5Plasma.so.5
#1  0x004460ce in ?? ()
#2  0x0044625f in ?? ()
#3  0x71c74bae in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/libQt5Core.so.5
#4  0x76da43bf in
KScreen::Output::apply(QSharedPointer const&) () from
/usr/lib/libKF5Screen.so.7
#5  0x76d85f85 in
KScreen::Config::apply(QSharedPointer const&) () from
/usr/lib/libKF5Screen.so.7
#6  0x76d91fa6 in
KScreen::ConfigMonitor::Private::updateConfigs(QSharedPointer
const&) ()
   from /usr/lib/libKF5Screen.so.7
#7  0x76d93e71 in
KScreen::ConfigMonitor::Private::edidReady(QDBusPendingCallWatcher*) () from
/usr/lib/libKF5Screen.so.7
#8  0x71c74bae in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/libQt5Core.so.5
#9  0x72a86e1f in
QDBusPendingCallWatcher::finished(QDBusPendingCallWatcher*) () from
/usr/lib/libQt5DBus.so.5
#10 0x72a86f18 in ?? () from /usr/lib/libQt5DBus.so.5
#11 0x71c75659 in QObject::event(QEvent*) () from
/usr/lib/libQt5Core.so.5
#12 0x72df968c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/libQt5Widgets.so.5
#13 0x72dfe8f6 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/libQt5Widgets.so.5
#14 0x71c48518 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib/libQt5Core.so.5
#15 0x71c4a3da in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /usr/lib/libQt5Core.so.5
#16 0x71c9d883 in ?? () from /usr/lib/libQt5Core.so.5
#17 0x7fffeda0dd87 in g_main_context_dispatch () from
/usr/lib/libglib-2.0.so.0
#18 0x7fffeda0dfe0 in ?? () from /usr/lib/libglib-2.0.so.0
#19 0x7fffeda0e08c in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#20 0x71c9dcab in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#21 0x71c466fa in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#22 0x71c4eb7c in QCoreApplication::exec() () from
/usr/lib/libQt5Core.so.5
#23 0x0041c176 in ?? ()
#24 0x712c7710 in __libc_start_main () from /usr/lib/libc.so.6
#25 0x0041c2d9 in _start ()

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps

[Aleix Pol via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=340267

--- Comment #34 from Aleix Pol  ---
@Thiago: Update to Qt 5.6 when it's available

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps

[Stephan Diestelhorst via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=340267

Stephan Diestelhorst  changed:

   What|Removed |Added

 CC||stephan.diestelhorst@gmail.
   ||com

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps

[Thiago Oliveira via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=340267

Thiago Oliveira  changed:

   What|Removed |Added

 CC||strat...@gmail.com

--- Comment #33 from Thiago Oliveira  ---
One year has been passed since the first entry in the bug track and no solution
so far... :(

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps

[BW via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=340267

BW  changed:

   What|Removed |Added

 CC||b.weggenmann+...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps

[E . Hakan Duran via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=340267

E. Hakan Duran  changed:

   What|Removed |Added

 CC||ehakandu...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=340267

--- Comment #29 from mich...@karbach.org ---
(In reply to Dainius Masiliūnas from comment #28)
> It should be resolved in Qt 5.6. It's not surprising that it's not working
> for those on the 5.5 branch.

Does it mean, it won't be fixed in 5.5, which probably means it won't be fixed
in OS 42.1, due to a major software update? 

Actually, I do not only have this reproducible crash with DP, I also have
occasionally problems with HDMI, which after resuming from suspend stays black.
But switching to another windowmanger, like gnome or entlightment, everything
works pretty well.  

For this reason I have switched the windowmanager, also because KDE5 plasma has
a bug which prevents to restore the complete desktop state, which is also yet
not resolved.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps

[James Hanks via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=340267

--- Comment #31 from James Hanks  ---
Bloody hell, I don't understand how QT could be released with a bug like this,
much less the developers being unconcerned about fixing it.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps

[Dainius Masiliūnas via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=340267

--- Comment #32 from Dainius Masiliūnas  ---
(In reply to James Hanks from comment #31)
> Bloody hell, I don't understand how QT could be released with a bug like
> this, much less the developers being unconcerned about fixing it.

I don't understand why it was released that way either, but they were quite
concerned with fixing it. After all, the bug is priority P1: Critical. They
just couldn't fix it (probably too many points of failure to account for). IIRC
it's not even really fixed in Qt 5.6, it was just reverted to lying that the
screen exists, like in previous Qt versions, which prevents the crashing.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps

[Dainius Masiliūnas via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=340267

--- Comment #28 from Dainius Masiliūnas  ---
It should be resolved in Qt 5.6. It's not surprising that it's not working for
those on the 5.5 branch.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps

[James Hanks via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=340267

James Hanks  changed:

   What|Removed |Added

 CC||jhanks1...@gmail.com

--- Comment #27 from James Hanks  ---
I am using OpenSuse Leap 42.1 (Plasma 5.4.3, QT 5.5.1 and Plasma crashes
without fail every time I disconnect/power off a VGA monitor from my laptop.
Furthermore, I cannot generate crash reports because the attempts to load
symbol packages fail. I hope this gets fixed soon.. I love Plasma 5, but this
is really maddening.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps

[Dmitry Nezhevenko via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=340267

Dmitry Nezhevenko  changed:

   What|Removed |Added

 CC||d...@inhex.net

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps

[Wellington via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=340267

Wellington  changed:

   What|Removed |Added

 CC||wellingtonwall...@yahoo.com
   ||.br

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps

[via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=340267

mich...@karbach.org changed:

   What|Removed |Added

 CC||mich...@karbach.org

--- Comment #25 from mich...@karbach.org ---
I observe a similar problem with openSUSE Leap 42.1 and KDE Plasma 5.4. I have
updated from openSUSE 13.2 with KDE 4 and now have this annoying bug. Indeed I
do have this only with Displayport and not with HDMI. As soon as I switch off
the monitor and switch on, my control panel is gone. Every time with no
exception.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps

[Kristian Karl via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=340267

Kristian Karl  changed:

   What|Removed |Added

 CC||kristian.hermann.karl@gmail
   ||.com

-- 
You are receiving this mail because:
You are watching all bug changes.