https://bugs.kde.org/show_bug.cgi?id=355528
--- Comment #15 from michael.mcter...@gmail.com ---
For anyone finding this bug, the following comments from KDE developer 'sebas'
may be of interest: https://lwn.net/Articles/668712/
It sounds like we have to wait for Wayland for a fix.
I
https://bugs.kde.org/show_bug.cgi?id=355528
Adrian Piotrowicz changed:
What|Removed |Added
CC||nex...@nxstudio.pl
---
https://bugs.kde.org/show_bug.cgi?id=355528
--- Comment #12 from aappdde...@gmail.com ---
I have discovered recently that under some scenarios where I am unable to
project or connect to an external monitor because the monitor does not
physically show up in Display Settings, that running xrandr
https://bugs.kde.org/show_bug.cgi?id=355528
--- Comment #13 from Nick Cross ---
Interesting ; I've found that calling "kscreen-console bug" often makes it pick
up the extra display and turn it on.
My scenario is the laptop is suspended, I wake it up, plugin it into the dock
and
https://bugs.kde.org/show_bug.cgi?id=355528
--- Comment #11 from Murat Ursavaş ---
Please don't go that harsh on devs. There is a regression, no denial of that.
But the main responsible might not be the KDE devs.
Take a look at Martin's blog post:
https://bugs.kde.org/show_bug.cgi?id=355528
--- Comment #10 from cher...@aip.de ---
I wonder if KDE devs ever give talks at conferences with their Laptop then
they would know how frustrating this bug is. Severity should be changed to
"grave".
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=355528
--- Comment #9 from Eric S ---
Also, it's frustrating not to be able to vote for this.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=355528
Nick Cross changed:
What|Removed |Added
CC||k...@goots.org
--
You are
https://bugs.kde.org/show_bug.cgi?id=355528
Marcin Śliwiński changed:
What|Removed |Added
CC||drst...@wp.pl
--- Comment #7
https://bugs.kde.org/show_bug.cgi?id=355528
--- Comment #6 from Murat Ursavaş ---
Unfortunately dealing with drivers didn't help. I've installed some missing
display drivers and the behavior is still there. And this time I got the app
launcher in the wrong place
https://bugs.kde.org/show_bug.cgi?id=355528
cher...@aip.de changed:
What|Removed |Added
CC||cher...@aip.de
--- Comment #3 from
https://bugs.kde.org/show_bug.cgi?id=355528
--- Comment #4 from cher...@aip.de ---
The 2nd issue is also reported here https://bugs.kde.org/show_bug.cgi?id=356725
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=355528
aappdde...@gmail.com changed:
What|Removed |Added
CC||aappdde...@gmail.com
--- Comment #2 from
13 matches
Mail list logo