[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off

[OlafLostViking via KDE Bugzilla]

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

OlafLostViking  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=371417

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

[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off

[OlafLostViking via KDE Bugzilla]

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

--- Comment #30 from OlafLostViking  ---
Hi Sebas,

first thank you very much for the work. I really don't want you to get this
wrong and I fully understand that you are scanning through a lot of bug reports
and it takes time to understand each of them. (Especially considering my bad
English from time to time ;-) )

But I (personally) think that closing the bug because of too many details is
not the best solution. If I would have written "Yes, doesn't work with 5.8.2."
and that's it, would that have been better? So I tried around a long time to
find a way to provoke this bug and attached the logfile. To make it easier for
you to see what was happening in the log that lead to the crash I described
what I did. If you are not interested in that, wouldn't it work to just ignore
it and jump to the marked "2nd pause", where the crash happened - as written at
the beginning?

There are no problems with specific apps, as the broken images happen on
multiple ones and only after kscreen "did things" ;-). So this wasn't a "Please
fix the app." but a "Look, Kscreen(??) does something that leads to problems at
many other places." The same goes with Plasma which takes the information vom
libkscreen, I guess. Of course, nobody wants you to take care of that! It was
just mentioned so that you could guess what kscreen is doing wrong at that
point in time.

So in the end I do not know what else I could write in a new bug report but
"Crashes when (un-)docking." and attaching the very same log as above (there
was no kscreen.log at the beginning which is why I started with kscreen-console
and xrandr logs).

I tried it on bug #371417 - I hope it helps.

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

[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off

[Sebastian Kügler via KDE Bugzilla]

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

Sebastian Kügler  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |INVALID
 Status|NEEDSINFO   |RESOLVED

--- Comment #29 from Sebastian Kügler  ---
@Olaf

> At this point I decided you will probably not even read all the things I wrote
> down until now and stopped playing around. I hope this is somehow useful for
> debugging. I will attach the kscreen.log file and screen photos soon.

That's unfortunately correct. You have by now put so much information into this
bugreport that it's a pain and very inefficient to sift through. I have to
filter out the relevant bits from your huge swathes of text, and often, I need
to read a bugreport multiple times. You can imagine what a huge waste of time
it becomes then. I wonder, if you know it's not useful, why you put so much
(unrelated) info in it.

So, for your understanding:
- I'm interested in problems with resolution, position and enablement of
outputs, these problems fall under kscreen
- if you have problems with applications, file a bug against the app, leave the
info out here
- if you've problems with the plasmashell (panels location, containment
location, etc.), file a bug against plasmashell (there's a Multiscreen
component)

In order to keep my bug triaging life manageable, I'm closing this bugreport,
asking you to file a new one, with *only* the relevant information.

Thanks for your cooperation, it's really appreciated.

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

[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off

[Simone Gaiarin via KDE Bugzilla]

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

--- Comment #28 from Simone Gaiarin  ---
I have a similar problem. Basically when waking the notebook up after undocking
(or docked to a different docking station with different moitors) mess the
configuration. Undocking and redocking restore the configuration in some cases.

I can provide a log if the one provided by the other user are not enough.

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

[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off

[OlafLostViking via KDE Bugzilla]

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

OlafLostViking  changed:

   What|Removed |Added

Version|5.5.4   |5.8.2

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

[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off

[OlafLostViking via KDE Bugzilla]

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

--- Comment #27 from OlafLostViking  ---
Created attachment 101655
  --> https://bugs.kde.org/attachment.cgi?id=101655=edit
screen photo showing the broken weather applet

Actually... I just saw the picture is quite bad. Basically, the white are looks
just like the qupzilla and profile pics background. It is the weather applet
from http://kde-apps.org/content/show.php/Weather+Widget?content=169572

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

[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off

[OlafLostViking via KDE Bugzilla]

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

--- Comment #26 from OlafLostViking  ---
Created attachment 101654
  --> https://bugs.kde.org/attachment.cgi?id=101654=edit
screen photo showing the broken qupzilla workspace

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

[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off

[OlafLostViking via KDE Bugzilla]

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

--- Comment #25 from OlafLostViking  ---
Created attachment 101653
  --> https://bugs.kde.org/attachment.cgi?id=101653=edit
screen photo showing the broken profile pics

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

[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off

[OlafLostViking via KDE Bugzilla]

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

--- Comment #24 from OlafLostViking  ---
Created attachment 101652
  --> https://bugs.kde.org/attachment.cgi?id=101652=edit
the automatically created kscreen.log

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

[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off

[OlafLostViking via KDE Bugzilla]

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

--- Comment #23 from OlafLostViking  ---
(Very) long story short: yes. I updated to 5.8.2 and I already saw many
improvements! Thank you! But the problem is still there.

BTW (I don't know if we need [another] bug report for that): when playing
around with multiple screen in the kscreen GUI, they something jump around
(when getting activated) and ruin any sorting work done up unto this point.

So, tighten your seatbelts, here it comes...  I will now give some kind of
diary (with terrible unprecise times as I just counted in my head) of what I
did and append the kscreen.log file that was created during that time. Please
do at least scan over the whole text, as the problems with the
panels/wallpapers and the window's movements _could_ perhaps give you an idea
(at least I hope so). I will change the docking stations later in the text and
the black-out happens after the second "pause".

* updated to Plasma 5.8.2
* "fixed" my desktop settings
* logged out
* deleted .local/share/kscreen/* on the console
* rebooted _in_ docking station WORK
  - WORK has a primary screen on Displayport DP-2 and a vertically rotated
secondary on DVI DP-1
  - the internal LVDS-0 screen has to be shut off because DELL was creative
when wiring the CPU internal and the mobile GeForce to the ports
  - SDDM shows login screen on LVDS-0 and the secondary screen DP-1 (not
rotated, understandably)
* logged in
  - keeps the screen configuration of SDDM
  - panel and wallpaper are shown correctly on the primary screen (still
LVDS-0)
  - on the secondary screen (DP-1) the default wallpaper is shown
* use kscreen to switch LVDS-0 off, set DP-2 as active primary and DP-1 as
active secondary (rotated by 90 deg)
  - the switching works almost immediately (of course no atomic modesetting
yet)
* set my own wallpaper on the secondary screen (DP-1)
* undock from docking station WORK
  - LVDS-0 get activated quite fast, all seems okay
* redock into WORK
  - setting up the screens takes a very short time (no atomic) but everything
seems to work
* undock again
  - the screen setup looks fine
  - my active browser gets moved out of the screen (I cannot see it anymore
despite on the panel)
* redock into WORK
  - screen setup is fine
  - panel is okay, but the wallpaper on the secondary screen is now the default
wallpaper
* undock
  - the browser window, which was moved out of the view earlier, is now
centered on screen (here I may add that I did not touch the GUI while doing
this docking-undocking cycles)
* redock into WORK
  - now it takes several seconds (my guess was 10-12) for the new setup to
start  <
  - screen setup is fine
  - the panel is now very narrow and on the secondary screen (DP-1)
  - there is NO wallpaper or anything else (like cashew/hamburger) on this
secondary screen; I also cannot right click on the black area (the panel is
responsive) <
* undock
  - screen setup is fine
  - panel is fine again
  - now, the afore mentioned browser window is half-way shifted (to the right
side) out of the visible desktop
* redock into WORK
  - primary screen is fine
  - secondary is showing the default wallpaper
* set the wallpaper to my own
* put notebook into sleep mode while still docked
* wake it up while still docked in WORK
  - lockscreen shows up correctly (new in 5.8.2! :-) ) on primary and secondary
(incl. rotation) screen
* put it into sleep
* wake it up
  - now the profile pics in the lockscreen are messed up (white area with a few
coloured sprinkles - I will add a photo if I don't forget later when attaching
files)
  - rest seems to be fine
* put it into sleep in docking station WORK
* undock!
* wake it up outside of docking station
  - profile pics are still messed up, rest seems fine
* redock into WORK
  - screen setup is fine
  - wallpapers are fine
  - but the panel is now on the wrong/secondary screen
* undock from WORK
  - the screen stays "half-black" for a surprisingly long time, but plasma
fills the missing part up, eventually
  - panel also takes several seconds to appear
* put notebook to sleep (still not docked)
* wake it up after docking it into WORK
  - SDDM appears on internal screen (LVDS-0) with broken profile pics (as
described above)
  - LVDS-0 shuts off
  - Secondary screen (DP-1) shows screenlocker with _working_ profile pics
  - Primary screen (DP-2) is black (no screenlocker!) while still showing the
mouse cursor
* login
  - screen setup is fine
  - my weather widget in the plasma panel as well as the website view of the
Qupzilla browser now show the same "coloured-sprinkels-on-white-ground"
background as the profile pics
  - qupzilla can be fixed by resizing, the weather applet works again after
some time (I guess after an update)
  - wallpaper is back to the default
* setting the wallpaper to mine again

== I really needed to go back to my work here ;-). So there is a pause of
"strange" things in the kscreen.log

* put notebook 

[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off

[OlafLostViking via KDE Bugzilla]

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

--- Comment #22 from OlafLostViking  ---
Sometimes. (I know, very helpfui. It happened once or twice this week, if I
remember correctly.)

Just now after docking the internal screen was shut off (which took two or
three seconds), the secondary external monitor was showing the lockscreen, the
primary was not (albeit it was powered on). After logging in, both were active.
Undocking worked, redocking it (taking again a few seconds) messed Plasma up
(panel on the wrong screen, far too small, wallpaper replaced by default
wallpaper, windows all on different screens with random sizes). Doing the cycle
again led to the panel being on the correct screen, the wallpaper on the
secondary screen is still the default wallpaper. After changing the wallpaper
on the secondary screen, I retried: The third try took over six or seven
seconds to shut off the LVDS (I first thought it hangs). The wallpapers of both
external screens are fine, the windows messed up and the panel again shifted
(and shrinked) to the secondary screen. To not make it an endless loop: The
fourth and last try reset the wallpaper again, but the panel was fine.

I will now delete the kscreen files again and re-start with a clean config as I
am now using 5.8.1.

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

[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off

[Sebastian Kügler via KDE Bugzilla]

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

Sebastian Kügler  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 Status|UNCONFIRMED |NEEDSINFO

--- Comment #21 from Sebastian Kügler  ---
Does this still happen with Plasma 5.8?

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

[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off

[OlafLostViking via KDE Bugzilla]

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

--- Comment #20 from OlafLostViking  ---
I have no idea why kscreen is forgetting the correct settings as they are
available in the config files (deleting the config files makes it work with a
standard setup - see below - again).

BTW: This behaviour is reproducible since the update that lead to this
situation. So whenever I come to the docking station at work, my screens turn
black. I found out undocking the laptop activates the internal display again.
But deleting the kscreen configs in this running system and then re-docking the
laptop leads to a complete lockup (the internal screen freezes, the other
screens are not changed, hard reboot needed).

After a reboot SDDM is using the (X11?) standard config (as always) with the
first external screen and the internal screen active (this machine only
supports two active screens) which is also used by the desktop then. Plasma
fails to recognize the correct setup and only uses one screen (sometimes even
with a default wallpaper instead of my personal one...?), but a restart of
plasma fixes that. :-/

In the end this means I have to reboot my laptop whenever sitting down at my
desk (annoying as I have a fully enrcrypted harddisk with two-factor
authentication ;-) ).

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

[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off

[Martin Gräßlin via KDE Bugzilla]

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

--- Comment #19 from Martin Gräßlin  ---
Given the xrandr output it seems like two external screens are connected, but
not configured (?). They don't have a position and the X-Server screen size
only matches the internal size.

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

[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off

[Simone Gaiarin via KDE Bugzilla]

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

Simone Gaiarin  changed:

   What|Removed |Added

 CC||simg...@gmail.com

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

[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off

[OlafLostViking via KDE Bugzilla]

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

--- Comment #18 from OlafLostViking  ---
The problem described in comment #15 just happened again. This time, I switched
to a console after  hard rebooting and dumped a simple "xrandr" and
"kscreen-console" output. Perhaps it's helpful.

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

[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off

[OlafLostViking via KDE Bugzilla]

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

--- Comment #17 from OlafLostViking  ---
Created attachment 100346
  --> https://bugs.kde.org/attachment.cgi?id=100346=edit
kscreen-console.log

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

[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off

[OlafLostViking via KDE Bugzilla]

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

--- Comment #16 from OlafLostViking  ---
Created attachment 100345
  --> https://bugs.kde.org/attachment.cgi?id=100345=edit
xrandr.log

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

[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off

[OlafLostViking via KDE Bugzilla]

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

--- Comment #15 from OlafLostViking  ---
Okay, let's try it ;-)

At home, the laptop was running inside a docking station with the internal LVDS
and an external screen active. I put it to sleep and woke it up again at work
inside another docking station with two external screen connected (due to the
machine's architecture only two displays can be used at the same time; the LVDS
has to stay inactive at work).

Here the laptop shortly showed the kscreenlocker before shutting off the
internal display but not activating the external ones. Even switching to a
kernel console wasn't possible anymore.

Each following reboot SDDM was showing on the internal screen as well as the
"first" external one (which, btw., is rotated - SDDM doesn't know that, of
course). After logging in, all screens turned and stayed black. Switching to a
kernel console WAS possible at that point in time (on the LVDS).

Rebooting outside of the docking station, the desktop came up normaly. Deleting
the .local/share/kscreen folder made it possible again to put the laptop into
the docking station without it turning off the screens.

Having a look at the kscreen GUI now revealed that kscreen thinks the secondary
external screen has NO resolution... Simply clicking on Unify Outputs two times
made it recognize the correct resolutions again. (Perhaps kscreen should NOT
change anything when it is unsure about the system's state so that the user
isn't left with no screen active at all.)

Switching to the wanted setup with the primary external display active and
rotated, the secondary active and the internal inactive now worked. Even though
Plasma couldn't handle the primary screen and had to be restarted to get my
wallpaper (but that's nothing new and for another bug report one day).

Before putting the laptop to sleep, I let xev run:

$ xev | tee xev.log
# suspend
# steps described above
$ grep RR xev.log 
RRNotify event, serial 41, synthetic NO, window 0xa1,
subtype XRROutputPropertyChangeNotifyEvent
RRScreenChangeNotify event, serial 41, synthetic NO, window 0xa1,
rotation RR_Rotate_0
RRNotify event, serial 41, synthetic NO, window 0xa1,
subtype XRROutputChangeNotifyEvent
rotation RR_Rotate_0
connection RR_Disconnected, subpixel_order SubPixelUnknown
RRScreenChangeNotify event, serial 41, synthetic NO, window 0xa1,
rotation RR_Rotate_0
RRNotify event, serial 41, synthetic NO, window 0xa1,
subtype XRROutputChangeNotifyEvent
rotation RR_Rotate_0
connection RR_Connected, subpixel_order SubPixelUnknown
RRScreenChangeNotify event, serial 41, synthetic NO, window 0xa1,
rotation RR_Rotate_0
RRNotify event, serial 41, synthetic NO, window 0xa1,
subtype XRROutputChangeNotifyEvent
rotation RR_Rotate_0
connection RR_Connected, subpixel_order SubPixelUnknown
RRScreenChangeNotify event, serial 174, synthetic NO, window 0xa1,
$ 

The whole xev.log is available for one year at https://paste.kde.org/pn9e0snkc

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

[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off

[OlafLostViking via KDE Bugzilla]

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

--- Comment #14 from OlafLostViking  ---
"Unfortunately" I have to say, the error no longer appears all the time (newest
packages from kf, apps, plasma) but only from time to time (or kwin just
crashes and reloads - so no data loss in that specific case. However, the main
culprit in messing up the screens became Plasma.).

I'll still try to remember checking xev and will report back, if I find
something - I just wanted to ACK so that the report doesn't get closed because
of a missing answer.

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

[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off

[OlafLostViking via KDE Bugzilla]

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

OlafLostViking  changed:

   What|Removed |Added

  Attachment #97285|0   |1
is obsolete||

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

[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off

[OlafLostViking via KDE Bugzilla]

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

--- Comment #12 from OlafLostViking  ---
Created attachment 97328
  --> https://bugs.kde.org/attachment.cgi?id=97328=edit
output of "loginctl session-status"

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

[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off

[OlafLostViking via KDE Bugzilla]

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

--- Comment #11 from OlafLostViking  ---
Created attachment 97327
  --> https://bugs.kde.org/attachment.cgi?id=97327=edit
output of "kscreen-console bug"

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

[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off

[OlafLostViking via KDE Bugzilla]

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

OlafLostViking  changed:

   What|Removed |Added

  Attachment #97288|output of "kscreen outputs" |output of "kscreen-console"
description||

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

[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off

[OlafLostViking via KDE Bugzilla]

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

OlafLostViking  changed:

   What|Removed |Added

  Attachment #97326|output of "kscreen config"  |output of "kscreen-console
description||config"

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

[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off

[OlafLostViking via KDE Bugzilla]

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

OlafLostViking  changed:

   What|Removed |Added

  Attachment #97287|output of "kscreen json"|output of "kscreen-console
description||json"

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

[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off

[OlafLostViking via KDE Bugzilla]

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

OlafLostViking  changed:

   What|Removed |Added

  Attachment #97285|output of "kscreen" |output of "kscreen-console"
description||

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

[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off

[OlafLostViking via KDE Bugzilla]

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

--- Comment #10 from OlafLostViking  ---
Created attachment 97326
  --> https://bugs.kde.org/attachment.cgi?id=97326=edit
output of "kscreen config"

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

[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off

[Ben Cooksley via KDE Bugzilla]

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

--- Comment #8 from Ben Cooksley  ---
The content of attachment 97284 has been deleted for the following reason:

Deleted per request of uploader.

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

[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off

[Ben Cooksley via KDE Bugzilla]

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

--- Comment #9 from Ben Cooksley  ---
The content of attachment 97283 has been deleted for the following reason:

Deleted per request of uploader.

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

[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off

[Ben Cooksley via KDE Bugzilla]

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

--- Comment #7 from Ben Cooksley  ---
The content of attachment 97286 has been deleted for the following reason:

Deleted per request of uploader.

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

[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off

[OlafLostViking via KDE Bugzilla]

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

--- Comment #6 from OlafLostViking  ---
Created attachment 97288
  --> https://bugs.kde.org/attachment.cgi?id=97288=edit
output of "kscreen outputs"

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

[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off

[OlafLostViking via KDE Bugzilla]

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

--- Comment #5 from OlafLostViking  ---
Created attachment 97287
  --> https://bugs.kde.org/attachment.cgi?id=97287=edit
output of "kscreen json"

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

[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off

[OlafLostViking via KDE Bugzilla]

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

--- Comment #4 from OlafLostViking  ---
Created attachment 97286
  --> https://bugs.kde.org/attachment.cgi?id=97286=edit
output of "kscreen config"

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

[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off

[OlafLostViking via KDE Bugzilla]

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

--- Comment #3 from OlafLostViking  ---
Created attachment 97285
  --> https://bugs.kde.org/attachment.cgi?id=97285=edit
output of "kscreen"

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

[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off

[OlafLostViking via KDE Bugzilla]

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

--- Comment #2 from OlafLostViking  ---
Created attachment 97284
  --> https://bugs.kde.org/attachment.cgi?id=97284=edit
output of "kscreen bug"

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

[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off

[OlafLostViking via KDE Bugzilla]

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

--- Comment #1 from OlafLostViking  ---
Created attachment 97283
  --> https://bugs.kde.org/attachment.cgi?id=97283=edit
output of kscreen

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