Created attachment 980572 [details]
Screenshot show erroneous full-height menu
Description of problem:
Using qt applications, including clementine (bundled) and bitcoin-qt (binary download) on a multi-screen display (laptop plus big monitor), pull-down menus sometimes take the full height of the screen. It's quite random: usually sliding to another menu and back fixes it.
Other times the menus don't display at all; this failure mode seems to be 100% reproducible if I have my big monitor plugged in, and the application is displaying to my laptop screen.
Version-Release number of selected component (if applicable):
Up-to-date Fedora 21 install: qt is at qt-4.8.6-18.fc21.x86_64
Most of the time
Steps to Reproduce:
1. Open a qt application
2. Click on a drop-down menu
Menu takes up full height of display. See attachment.
Menu takes up only as much space as it needs.
Toshiba Portege R700-1DF
[root@rocinante ~]# lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 02)
I am getting this same issue under Fedora 20. It occurs with qt applications (e.g. calibre, qgis, nixnote) under Gnome. I have multi-monitor display with an HDMI tv as the secondary monitor (1920x1080 vs primary display 1024x768).
* Menu issues as describe above: menus will not post at all on primary display and will take up full height on secondary display and in the wrong horizontal position; need to 'sneak up on' menus to actually use them as trying to move to a menu item will often trip a different menu. Happens predictably, 100% of the time.
* The Qt applications will often start on the secondary display (which is often powered off and it looks like the application did not start).
* Even after application is moved to primary display, dialogs will often post to secondary display (which again, when display is off, looks like application froze).
$ lspci |grep VGA
01:00.0 VGA compatible controller: NVIDIA Corporation GK104 [GeForce GTX 760 OEM] (rev a1)
qt is 4.8.6 release 30.
If I go to Display Settings and Turn Off the secondary display, menus will post on the primary display, usually correctly, only occasionally going full height.
running gnome-shell, i'm seeing menu issues on a secondary screen
with all Qt based applications i tried, both in Fedora 21 and Fedora 22,
and in earlier releases too: QtCreator (using Qt 5),
KDevelop 4.7 (using Qt 4), K3B.
usually this means the menus pop up not below the menu bar but vertically
in the middle of the secondary screen, where the "top" edge of the primary
screen would be. i've seen menus not pop up anywhere visible at all too.
workaround for me is to use the Gnome Settings Display config to
move the secondary screen such that its top edge is lower than the
top edge of the primary screen.
the problematic screen configuration looks like the reporter's attached screenshot.
GTK+2/3 applications have no problems with this setup.
forgot to mention: i'm using this screen configuration with top edge
of secondary screen above top edge of primary screen because it makes
the top-left corner of the secondary screen "active" so that
moving the pointer there brings up gnome-shell's overhead view.
if the secondary screen top edge is lower then that doesn't work
as the pointer moves to the primary screen.
This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. 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'
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 21 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.
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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
Thank you for reporting this bug and we are sorry it could not be fixed.
sp flash tool for linux x86_64 (tool for re-flashing devices with mediatek soc)
also goldendict has missing menus when i have connected monitor.
when running on laptop without monitor i have menus available and clicable.
this is how lightdm setup screen.
i use windowmaker.
[indy@dhcp-10-40-0-152 ~]$ cat /etc/lightdm/display_setup.sh
# xrandr --setprovideroutputsource modesetting NVIDIA-0
xrandr --output DP2-2 --right-of eDP1
when i move/start application (see comment above) to/on eDP1 (laptop's primary display) i have menus, when i move or start application on 2nd display, menus disappear. after moving back to primary display menu 're-appears'.
even this is workaround, should be nice to have it fixed.
after update to WindowMaker 0.95.7 problem disappeared.
in windowmaker is:
"wmaker: Restore multi screen functionality by reverting wrong commits"
which probably resolved problem.
So fixed by WindowMaker update
WindowMaker-0.95.7-1.fc22 wmweather+-2.15-4.fc22 has been submitted as an update to Fedora 22. https://bodhi.fedoraproject.org/updates/FEDORA-2015-7cc4eebd4a
bugzilla asked me to comment on this bug
unfortunately i don't still have an F22 system handy to test on, as everything got upgraded to F23.
I can confirm that I haven't seen this problem for a long time, so it must have been fixed either by F23 or a published update.
Closing this bug now.
Thanks to those involved in fixing for your efforts!