Bug 1384837 - New windows/tooltips open outside the visible screen or with offset
Summary: New windows/tooltips open outside the visible screen or with offset
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-desktop
Version: 25
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-14 08:45 UTC by Cajus Pollmeier
Modified: 2017-12-12 10:57 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-12 10:57:51 UTC
Type: Bug


Attachments (Terms of Use)

Description Cajus Pollmeier 2016-10-14 08:45:52 UTC
Description of problem:

At some point, applications like Firefox, Chrome, vlc, etc. start to open new windows outside the visible screen. You can them press "Alt+Space" and choose "Move window" to get them back to the visible area. I can't tell you what "some point" is. It just started some time ago and persists until now.

This behaviour is persistent now on my system and it's getting somehow boring to always move windows back on screen.

Please see "Additional infos" on more information about the setup.


Version-Release number of selected component (if applicable):

As I don't know which exact component of the stock F24 desktop is responsible for managing and storing window positions, I'm not sure what to list here. I'm using an up-to-date F24 with the stock GNOME desktop / X11.


How reproducible:

Example 1:

Steps to Reproduce:
1. Open Firefox
2. Klick on the address line and start to type something which is in the history

Actual results:

The address popup (the combobox which is made of the address line and the history URLs/proposals) opens somewhere outside Firefox.

This happens with other pull down menus, too. If you've no luck, parts of it are outside the screen, so you can't see the current state of checks.

Expected results:

It opens under the address line.


Example 2:

Steps to Reproduce:
1. Open Chrome (external from google)
2. Browse somewhere
3. Press F12 for the developer tools or open a new browser window in general

Actual results:

Optically nothing happens. After pressing the "Windows" key to get the window summary for the current workspace, you see that the developer tool window opened actually. You can move that window into the visible screen area.

Expected results:

The window opens on the connected screen.


Example 3:

Steps to Reproduce:
1. Open VLC (external from rpmfusion) 
2. Open the settings window

Actual results:

Optically nothing happens. After pressing the "Windows" key to get the window summary for the current workspace, you see that the settings window opened actually. You can't move that window into the visible screen area, because it is somewhat attached to it's parent window. I don't know a workaround for using it that way, so this one is more critical.

Expected results:

The window opens on the connected screen and I'm able to modify settings.


Additional info:

The system is a notebook with a build in high-dpi display. I'm using it "on the road" with the internal display with "gsettings set org.gnome.desktop.interface scaling-factor 2". When I'm at work, it is attached to a *non* high-dpi display, while the internal screen is disabled in the GNOME display manager.

It would be nice if they could be used at the same time, but using mixed DPI settings gave much headache currently and I never managed to get it work for more than a minute.

The described behaviour happens on both displays.

Comment 1 Cajus Pollmeier 2016-10-17 10:07:01 UTC
This happens also to stock apps like empathy. If I open empathy, the roster window is outside the visible screen each time. I've always to move it back.

Comment 2 Cajus Pollmeier 2016-11-23 17:58:21 UTC
Using X11 (wayland doesn't seem to perform well with the built-in Intel HD Graphics 520).

Comment 3 Fedora End Of Life 2017-11-16 18:37:09 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. 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 EOL if it remains open with a Fedora  'version'
of '25'.

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.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 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 this bug is closed as described in the policy above.

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 4 Fedora End Of Life 2017-12-12 10:57:51 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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.