https://bugs.kde.org/show_bug.cgi?id=376341
--- Comment #37 from Nate Graham ---
Your issue is 100% sure to be something else, as the original report is over
five years old and the code has changed completely. We track bug reports by
root cause, not symptoms, and unfortunately with multi-monitor
https://bugs.kde.org/show_bug.cgi?id=376341
Julius R. changed:
What|Removed |Added
CC||c3i8zv...@mozmail.com
--- Comment #36 from Julius R
https://bugs.kde.org/show_bug.cgi?id=376341
Nate Graham changed:
What|Removed |Added
Resolution|--- |FIXED
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=376341
rasmus.oltro...@energymeteo.de changed:
What|Removed |Added
CC||rasmus.oltrogge@energymeteo
https://bugs.kde.org/show_bug.cgi?id=376341
MartinG changed:
What|Removed |Added
CC||grons...@gmail.com
--
You are receiving this mail be
https://bugs.kde.org/show_bug.cgi?id=376341
--- Comment #33 from Lamdarer ---
I(In reply to Lamdarer from comment #32)
I guess turning off automatic input selection really fixes it.
Though I sometimes have other problems with my screens after sleep mode(e.g.
Blackscreen(except for the mouse curso
https://bugs.kde.org/show_bug.cgi?id=376341
Kristoffer Gahlin changed:
What|Removed |Added
CC||stoffepoj...@gmail.com
--
You are receivin
https://bugs.kde.org/show_bug.cgi?id=376341
Lamdarer changed:
What|Removed |Added
CC||lamda...@mailbox.org
--- Comment #32 from Lamdarer
https://bugs.kde.org/show_bug.cgi?id=376341
--- Comment #31 from Sergey ---
I don't remember when last time it was reproducible for me on Gentoo Linux
(always fresh).
But I noticed another problem. I have dualboot with Windows and sometimes after
rebooting from Windows to Gentoo my laptop display
https://bugs.kde.org/show_bug.cgi?id=376341
Sebastian Kügler changed:
What|Removed |Added
Assignee|se...@kde.org |kscreen-bugs-n...@kde.org
--
You are receiv
https://bugs.kde.org/show_bug.cgi?id=376341
bjoe...@arcor.de changed:
What|Removed |Added
CC||bjoe...@arcor.de
--
You are receiving this m
https://bugs.kde.org/show_bug.cgi?id=376341
Daniel changed:
What|Removed |Added
CC||daniel-other+kdebug@dadosch
|
https://bugs.kde.org/show_bug.cgi?id=376341
Will Marler changed:
What|Removed |Added
CC||will.mar...@gmail.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=376341
--- Comment #30 from M. Raymond Vaughn ---
I hesitate to make a claim so quickly, but... it is entirely possible that
plasmashell/kscreen are doing exactly what they are supposed to.
On the machine with symptoms, I have been forcing my displays to swit
https://bugs.kde.org/show_bug.cgi?id=376341
--- Comment #29 from M. Raymond Vaughn ---
Dear KDE bug wranglers,
May I ask what the current disposition of this bug is, and whether there is
anything at all I can do to help resolve it? My research indicates the problem
is widespread on a variety of
https://bugs.kde.org/show_bug.cgi?id=376341
M. Raymond Vaughn changed:
What|Removed |Added
CC||nethers...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=376341
Milton Hagler changed:
What|Removed |Added
CC||milton...@gmail.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=376341
--- Comment #28 from Sergey ---
just reproduced it again..
so not fixed..
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=376341
--- Comment #27 from Sergey ---
yep. seems to work properly
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=376341
--- Comment #26 from Sergey ---
I currently use Plasma 5.14.5, KDE Frameworks 5.54.0 but I'm not sure how long.
I'll try to disable my scripts and check.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=376341
--- Comment #25 from smihael ---
This seems to not be an issue anymore using KDE neon 5.14 with Plasma 5.14.5,
KDE Frameworks 5.54.0 and generic Linux 4.15.0 kernel.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=376341
--- Comment #24 from hoshiyamazak...@gmail.com ---
(In reply to hoshiyamazaki01 from comment #23)
> Appears to affect wayland too.
Distro I use is Arch Linux.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=376341
hoshiyamazak...@gmail.com changed:
What|Removed |Added
CC||hoshiyamazak...@gmail.com
--- Commen
https://bugs.kde.org/show_bug.cgi?id=376341
Sergey changed:
What|Removed |Added
Ever confirmed|0 |1
Status|REPORTED|CONF
https://bugs.kde.org/show_bug.cgi?id=376341
--- Comment #21 from Sergey ---
xrandr shell script seems to work good.
Bug I just rewrote it based on this
https://askubuntu.com/questions/183516/how-do-i-detect-when-my-system-wakes-up-from-suspend-via-dbus-or-similar-in-a-py
def handle_sleep_callbac
https://bugs.kde.org/show_bug.cgi?id=376341
--- Comment #20 from Sergey ---
I found it easier to have a small script with
xrandr --output LVDS-1 --primary --auto --left-of HDMI-2
so after resume I can press alt+f2 and start it.
In other words this bug is not that critical for me anymore.
Proba
https://bugs.kde.org/show_bug.cgi?id=376341
--- Comment #19 from Sergey ---
same problem with openSUSE Tumbleweed
kscreen-5.14.1
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=376341
--- Comment #18 from Sergey ---
any developers here? any idea what code can I check to try to fix?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=376341
--- Comment #17 from Sergey ---
I just compared ~/.local/share/kscreen/56e40e2cebeace281ad87eb77d19cacd with
and without the bug. The only difference is in the offset of my second monitor.
It's set to 0 when has to be 1920.
--
You are receiving this m
https://bugs.kde.org/show_bug.cgi?id=376341
--- Comment #16 from Sergey ---
it happended again. so no miracles. it's still broken.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=376341
--- Comment #15 from Sergey ---
Just tried another thing. Removed all the kde/plasma files I was able to find
in ~/, ~/.config, ~/.local, ~/.cache. Put my laptop to sleep for whole night.
In the morning it's restored properly.
The only difference, pre
https://bugs.kde.org/show_bug.cgi?id=376341
--- Comment #14 from Sergey ---
Well. after longer delay I still see this bug.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=376341
--- Comment #13 from Sergey ---
Hm I'm not sure but just did one test. Removed everything from
~/.local/share/kscreen, closed lid and then waited 5+ mins, opened lid and the
screen restored correctly!
No new files in ~/.local/share/kscreen, just that o
https://bugs.kde.org/show_bug.cgi?id=376341
--- Comment #12 from Sergey ---
Just in case
rion@dizzynb ~ $ cat ~/.local/share/kscreen/56e40e2cebeace281ad87eb77d19cacd
[
{
"enabled": true,
"id": "e998bf1b7cde6dafb866ed2bdb0e5cfc",
"metadata": {
"fullname": "
https://bugs.kde.org/show_bug.cgi?id=376341
--- Comment #11 from Sergey ---
Just gave it another shot after 1.5 years with xfce.
Still same way buggy.
5.14.1 is here
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=376341
--- Comment #10 from Sergey ---
It seems another workaround is to switch to cosole and type there pm-suspend
to go to sleep.
Resumed in console monitors are recognized properly by DE then.
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=376341
--- Comment #9 from smihael ---
The workaround described by Sergey works for me usually too. I was still
unable to test with Neon, but I'm afraid it is hardware specific problem.
On 28 February 2017 at 06:54, Sergey wrote:
> https://bugs.kde.org/show
https://bugs.kde.org/show_bug.cgi?id=376341
--- Comment #8 from Sergey ---
Forgot to say.
My extra monitor usually has a small delay to init. May it somehow affects
Plasma.
Also weird effects after resume a pretty much random for me. for example: both
monitors become in sync for ome reason, wall
https://bugs.kde.org/show_bug.cgi?id=376341
Sergey changed:
What|Removed |Added
CC||rion...@gmail.com
--- Comment #7 from Sergey ---
I ha
https://bugs.kde.org/show_bug.cgi?id=376341
--- Comment #6 from Sebastian Kügler ---
Another option would be the Neon Live image. Thanks for the configuration
files!
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=376341
--- Comment #5 from smihael ---
Attached you will find all files from ~/.local/share/kscreen/
I give quite a lot of presentations in different lecture rooms so there are
many screen files, but the problem is occurring mainly with screen
c3ec4764bde5c8a
https://bugs.kde.org/show_bug.cgi?id=376341
--- Comment #4 from Sebastian Kügler ---
Thanks for the bugreport!
Could you attach the files in ~/.local/share/kscreen/* to this bugreport? The
problem may be either in plasmashell or in kscreen, so we need to check if
kscreen gets the positioning of
https://bugs.kde.org/show_bug.cgi?id=376341
--- Comment #3 from smihael ---
Created attachment 103975
--> https://bugs.kde.org/attachment.cgi?id=103975&action=edit
desired configuration
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=376341
--- Comment #2 from smihael ---
Created attachment 103974
--> https://bugs.kde.org/attachment.cgi?id=103974&action=edit
appletsrc
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=376341
--- Comment #1 from smihael ---
Created attachment 103973
--> https://bugs.kde.org/attachment.cgi?id=103973&action=edit
plasmashell
PlasmaRunnerManager and KFileDialog Settings are hidden for privacy reasons
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=376341
Martin Gräßlin changed:
What|Removed |Added
Component|general |common
Product|kwin
46 matches
Mail list logo
