https://bugs.kde.org/show_bug.cgi?id=340267
Vitaliy Gorbunov changed:
What|Removed |Added
CC|
https://bugs.kde.org/show_bug.cgi?id=340267
David Edmundson changed:
What|Removed |Added
CC|
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
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
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
https://bugs.kde.org/show_bug.cgi?id=340267
David Reid changed:
What|Removed |Added
CC||dlr...@gmail.com
--
You are
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
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
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
https://bugs.kde.org/show_bug.cgi?id=340267
Christoph Cullmann changed:
What|Removed |Added
CC|cullm...@kde.org|
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=340267
David Edmundson changed:
What|Removed |Added
Resolution|--- |FIXED
https://bugs.kde.org/show_bug.cgi?id=340267
Bart changed:
What|Removed |Added
CC||bart...@yahoo.com
--- Comment #68
https://bugs.kde.org/show_bug.cgi?id=340267
David Edmundson changed:
What|Removed |Added
CC|
https://bugs.kde.org/show_bug.cgi?id=340267
David Edmundson changed:
What|Removed |Added
CC|
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
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
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
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
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
https://bugs.kde.org/show_bug.cgi?id=340267
lbug...@gmail.com changed:
What|Removed |Added
CC||lbug...@gmail.com
--- Comment #60 from
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
https://bugs.kde.org/show_bug.cgi?id=340267
Konrad Materka changed:
What|Removed |Added
CC||kmate...@wp.pl
--
You are
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
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
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
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
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
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
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
https://bugs.kde.org/show_bug.cgi?id=340267
Michael Butash changed:
What|Removed |Added
CC||mich...@butash.net
---
https://bugs.kde.org/show_bug.cgi?id=340267
Christoph Feck changed:
What|Removed |Added
CC||cf...@kde.org
--- Comment #50
https://bugs.kde.org/show_bug.cgi?id=340267
carl changed:
What|Removed |Added
CC||cxx...@gmail.com
--
You are
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
https://bugs.kde.org/show_bug.cgi?id=340267
Bob Wya changed:
What|Removed |Added
CC||bob.mt@gmail.com
--
You
https://bugs.kde.org/show_bug.cgi?id=340267
Paul changed:
What|Removed |Added
CC|
https://bugs.kde.org/show_bug.cgi?id=340267
Josiah Barber changed:
What|Removed |Added
CC|
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
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
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
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
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
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?
--
https://bugs.kde.org/show_bug.cgi?id=340267
Oleg Sidorkin changed:
What|Removed |Added
CC||osidor...@gmail.com
--
https://bugs.kde.org/show_bug.cgi?id=340267
Soren Harward changed:
What|Removed |Added
CC||stharw...@gmail.com
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
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.
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
https://bugs.kde.org/show_bug.cgi?id=340267
Xapient changed:
What|Removed |Added
CC||xapi...@gmx.net
--- Comment #37
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
https://bugs.kde.org/show_bug.cgi?id=340267
Christoph changed:
What|Removed |Added
CC||w...@psitrax.de
--
You are
https://bugs.kde.org/show_bug.cgi?id=340267
Robert Grasböck changed:
What|Removed |Added
CC||m...@djtulan.com
--
You
https://bugs.kde.org/show_bug.cgi?id=340267
valdi...@gmail.com changed:
What|Removed |Added
CC||valdi...@gmail.com
--- Comment #35 from
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.
https://bugs.kde.org/show_bug.cgi?id=340267
Stephan Diestelhorst changed:
What|Removed |Added
CC|
https://bugs.kde.org/show_bug.cgi?id=340267
Thiago Oliveira changed:
What|Removed |Added
CC||strat...@gmail.com
---
https://bugs.kde.org/show_bug.cgi?id=340267
BW changed:
What|Removed |Added
CC||b.weggenmann+...@gmail.com
--
https://bugs.kde.org/show_bug.cgi?id=340267
E. Hakan Duran changed:
What|Removed |Added
CC||ehakandu...@gmail.com
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
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
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
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.
https://bugs.kde.org/show_bug.cgi?id=340267
James Hanks changed:
What|Removed |Added
CC||jhanks1...@gmail.com
---
https://bugs.kde.org/show_bug.cgi?id=340267
Dmitry Nezhevenko changed:
What|Removed |Added
CC||d...@inhex.net
--
You are
https://bugs.kde.org/show_bug.cgi?id=340267
Wellington changed:
What|Removed |Added
CC|
https://bugs.kde.org/show_bug.cgi?id=340267
mich...@karbach.org changed:
What|Removed |Added
CC||mich...@karbach.org
--- Comment #25 from
https://bugs.kde.org/show_bug.cgi?id=340267
Kristian Karl changed:
What|Removed |Added
CC|
66 matches
Mail list logo