https://bugs.kde.org/show_bug.cgi?id=364044
Andrew Crouthamel changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=364044
Andrew Crouthamel changed:
What|Removed |Added
Keywords||triaged
--- Comment #15 from Andrew
https://bugs.kde.org/show_bug.cgi?id=364044
--- Comment #14 from Andreas Cord-Landwehr ---
... and here the output after resumed from suspend-to-ram:
kscreen-console bug
kscreen-console(11252)/(default) main: START: Requesting Config
kscreen-console(11252)/(default)
https://bugs.kde.org/show_bug.cgi?id=364044
--- Comment #13 from Andreas Cord-Landwehr ---
Hi, the problem is still present with Plasma 5.8. Here the output with both
screens working:
$ kscreen-console bug
kscreen-console(10856)/(default) main: START: Requesting Config
https://bugs.kde.org/show_bug.cgi?id=364044
--- Comment #12 from Sebastian Kügler ---
Could you confirm or deny if it's fixed in 5.8?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=364044
Simone Gaiarin changed:
What|Removed |Added
CC|simg...@gmail.com |
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=364044
--- Comment #11 from Andreas Cord-Landwehr ---
Sorry for the late reply, had a long struggle with the kscreen kcm not starting
up correctly (finally turned out to be caused by a mix of loaded Qt libs with
different SO
https://bugs.kde.org/show_bug.cgi?id=364044
--- Comment #10 from Simone Gaiarin ---
I had a similar problem, though disabling and reenabling in kscreen didn't
help. Kernel 4.7 solved the problem for me.
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=364044
Sebastian Kügler changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=364044
Simone Gaiarin changed:
What|Removed |Added
CC||simg...@gmail.com
--
You
https://bugs.kde.org/show_bug.cgi?id=364044
--- Comment #8 from Sebastian Kügler ---
I've found a bug when enabling outputs. Information about crtcs was outdated,
which meant outputs failed to enable in certain cases, and were subsequently
disabled. We're now querying the crtcs
https://bugs.kde.org/show_bug.cgi?id=364044
--- Comment #7 from Andreas Cord-Landwehr ---
I can still reproduce this issue with this patch. Do you need updated
information?
My Qt now is 5.7.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=364044
--- Comment #6 from Sebastian Kügler ---
Git commit 54ec74901a0fea1601f76278d6e04af4fbd4b74d by Sebastian Kügler.
Committed on 14/06/2016 at 12:34.
Pushed by sebas into branch 'master'.
more creative output type detection in xrandr
https://bugs.kde.org/show_bug.cgi?id=364044
--- Comment #5 from Andreas Cord-Landwehr ---
Via kickoff -> Leave -> Suspend
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=364044
Sebastian Kügler changed:
What|Removed |Added
Status|UNCONFIRMED |CONFIRMED
Ever
https://bugs.kde.org/show_bug.cgi?id=364044
--- Comment #2 from Andreas Cord-Landwehr ---
Hi Sebas, restarting kded5 makes no change when I am in the state after
resuming on one monitor does not get a signal.
Output of kscreen-console bug:
cordlandwehr@weatherwax:/tmp$
16 matches
Mail list logo