[KScreen] [Bug 371417] screens not (re-)actived after (un-)docking cycles of a notebook

[Bug Janitor Service]

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

Bug Janitor Service  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

--- Comment #5 from Bug Janitor Service  ---
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!

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

[KScreen] [Bug 371417] screens not (re-)actived after (un-)docking cycles of a notebook

[Bug Janitor Service]

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

--- Comment #4 from Bug Janitor Service  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

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

[KScreen] [Bug 371417] screens not (re-)actived after (un-)docking cycles of a notebook

[Nate Graham]

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

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org
 Resolution|--- |WAITINGFORINFO
 Status|CONFIRMED   |NEEDSINFO

--- Comment #3 from Nate Graham  ---
Thank you for the bug report. Unfortunately we were not able to get to it yet.
Can we ask you to please see if you can reproduce the issue with Plasma 5.25 or
5.26?

If you can, please change the status to CONFIRMED when replying. Thanks a lot!

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

[KScreen] [Bug 371417] screens not (re-)actived after (un-)docking cycles of a notebook

[bugzilla_noreply]

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

azr...@googlemail.com changed:

   What|Removed |Added

 CC||azr...@googlemail.com

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

[KScreen] [Bug 371417] screens not (re-)actived after (un-)docking cycles of a notebook

[Sebastian Kügler]

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

Sebastian Kügler  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #2 from Sebastian Kügler  ---
Thanks, much clearer now. Unfortunately, it's nothing I can test or reproduce,
as my docking station and laptop can only handle one external monitor, and I
don't use NVidia hardware either.

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

[KScreen] [Bug 371417] screens not (re-)actived after (un-)docking cycles of a notebook

[OlafLostViking via KDE Bugzilla]

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

OlafLostViking  changed:

   What|Removed |Added

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

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

[KScreen] [Bug 371417] screens not (re-)actived after (un-)docking cycles of a notebook

[OlafLostViking via KDE Bugzilla]

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

OlafLostViking  changed:

   What|Removed |Added

 CC||olaf.the.lost.viking@gmail.
   ||com

--- Comment #1 from OlafLostViking  ---
Created attachment 101684
  --> https://bugs.kde.org/attachment.cgi?id=101684=edit
kscreen.log while the described problem happened

The failure should be around 20.10.2016 08:07.

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