Bug 742053 - KDE: windows remain out of the screen after removing the external display
Summary: KDE: windows remain out of the screen after removing the external display
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kde-workspace
Version: 18
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Daniel Vrátil
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 825677 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-09-28 21:15 UTC by Qji
Modified: 2015-11-02 01:36 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-02-05 22:42:35 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
KDE Software Compilation 248748 0 None None None 2012-06-26 12:01:21 UTC

Description Qji 2011-09-28 21:15:55 UTC
Description of problem:

After removing an external display (in multi display environment with KDE) the windows on the external display don't move to the remaining screen area and these windows will be unreachable. These windows still work, I see these on the task bar, but they are invisible.
If screen locked in this state, the login screen will be invisible also (but usable if I type without seeing the login window)

Version-Release number of selected component (if applicable):
Fedora 15 without any KDE releated extra packages.

How reproducible:

Steps to Reproduce:
1. Plug in external monitor and configure it (not as a clone)
2. Open some windows to the new screen area
3. Plug out the external monitor. The screen size and monitor configuration will

Actual results:
Some windows are unreachable.

Expected results:
All of the windows should be inside of the visible screen.

Additional info:
I have an Dell Latitude E6400 laptop with Intel video card.

Comment 1 Martin Bříza 2012-06-26 11:58:58 UTC
*** Bug 825677 has been marked as a duplicate of this bug. ***

Comment 2 Martin Bříza 2012-06-26 12:01:21 UTC
Based on the duplicate report, I confirm this bug to be present in Fedora 16 in KDE SC 4.8.3.
Adding the external tracker here to be more visible.

Comment 3 Fedora End Of Life 2013-01-16 13:26:05 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 4 Fedora End Of Life 2013-02-13 14:14:10 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 5 Kevin Kofler 2013-04-01 22:34:34 UTC
Pahan, you reopened this against Rawhide, does this mean this still happens with KScreen? (In Rawhide, KScreen replaces kcm_randr.)

Comment 6 Fedora End Of Life 2013-04-03 19:19:53 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19

Comment 7 Pavel Alexeev 2013-04-14 19:55:40 UTC
Sorry, I have not test it on rawhide. Change to 18. There it always reproduced.

Comment 8 Kevin Kofler 2013-04-14 20:30:13 UTC
So can you try with kscreen on Fedora 18? (Just install kscreen and restart your KDE Plasma session, then you should be running kscreen automatically.)

Comment 9 Pavel Alexeev 2013-04-29 11:03:31 UTC
It works different, but still not correct:
1) On plugin external monitor no any splash appeared allowing inplace configure it as it was done before.
2) But after setup screens its remembered positions as I see and configuration restored automatically. So, may be 1 indeed not needed now.
3) *Main problem persist. After disconnect external monitor which was primary (contain KDE panels) monitor of notebook absent all that panels and still "xrandr --auto" required to fix it.*

Comment 10 Martin Bříza 2013-04-29 11:29:12 UTC
Pavel,

I think the splash is fixed in upstream and will be included in some future release.

To the problem with not remembering the window positions:
Please try removing your $HOME/.kde/share/apps/kscreen/* (this will reset your screen configuration) and setting both configurations again.
I was experiencing issue similar to yours because an older version of kscreen saved my laptop screen with external monitor turned off as moved away from the start of the display (e.g. it didn't start at 0x0 but let's say 1920x600). This caused the virtual screen to be larger than the display itself (e.g 3840x1680) and the windows to be outside the actual displayed part of the screen.

You can also check your configuration files in the folder I mentioned, they are saved in readable JSON format.

Comment 11 Pavel Alexeev 2013-05-16 07:28:07 UTC
Yes, it seams works now.
Thank you very much!

Comment 12 Fedora End Of Life 2013-12-21 14:57:22 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 13 Fedora End Of Life 2014-02-05 22:42:35 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.