RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1027152 - Windows doesn't occur on their original location after undocking and docking notebook
Summary: Windows doesn't occur on their original location after undocking and docking ...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: gnome-shell
Version: 7.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: rc
: ---
Assignee: Florian Müllner
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-06 09:48 UTC by Branislav Náter
Modified: 2020-12-15 07:28 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-12-15 07:28:11 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Branislav Náter 2013-11-06 09:48:27 UTC 
Description of problem:
I'm running system on laptop and I'm using two monitor setup, regular monitor and laptop display. Regular monitor is the primary one. When I undock laptop, all windows from primary monitor move to laptop display, which is expected. But when I get laptop back to dock, all windows stay on laptop screen. This is pretty annoying. I have to move all windows to their original location.

Version-Release number of selected component (if applicable):
gnome-shell-3.8.4-2.fc19
gnome-shell-3.8.4-10.el7

How reproducible:
always

Steps to Reproduce:
1. see description

Additional info:
I'm running Fedora 19 but same issue appear on rhel-7.
Comment 1 RHEL Program Management 2014-03-22 06:33:42 UTC 
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Comment 3 Michal Domonkos 2015-05-14 10:05:02 UTC 
This seems to work fine on GNOME-3.14 except that it doesn't with the very first undock/dock event since the gnome session start.  Reproducer:

1. In GNOME, set up a layout such that both the laptop's display and an external display is used
2. Make the external display primary
3. Open two windows and place one on each screen
4. Undock and dock
6. Notice how both windows remain on the laptop's display (incorrect behavior)
7. Move one of them back to the external display
8. Undock and dock
9. Now the windows are placed in their original locations, i.e. one of them being on the external display (correct behavior)

Logging out and in again, the same scenario is repeated.
Comment 4 Michal Domonkos 2015-08-07 10:03:45 UTC 
Revisiting this issue, it actually turns out to be pretty random in terms of reproducibility.  I would say it depends on whether the secondary display is ready at the time gnome-shell tries to restore individual windows.  So if the display on which a window was before undocking doesn't activate fast enough on docking, the window will just end up on the display which is already active.
Comment 6 RHEL Program Management 2020-12-15 07:28:11 UTC 
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Note You need to log in before you can comment on or make changes to this bug.