FS#18327 - [qt] Menus broken in qt 4.6.1-1 for multi-head setups
Attached to Project:
Arch Linux
Opened by Jeff Cook (cookiecaper) - Sunday, 14 February 2010, 10:23 GMT
Last edited by Andrea Scarpino (BaSh) - Sunday, 11 April 2010, 11:22 GMT
Opened by Jeff Cook (cookiecaper) - Sunday, 14 February 2010, 10:23 GMT
Last edited by Andrea Scarpino (BaSh) - Sunday, 11 April 2010, 11:22 GMT
|
Details
Description:
When click on a menu on the top menu bar in applications that use qt 4.6.1 while the application is not on the main screen, no menu appears. Instead, the menu button is indented like a menu is open, but the menu does not open. If moved to the main screen, menus work fine for me, but reports are some wonkiness there for others. I am using awesomewm, and this bug may be specific to that. Additional info: * package version(s) 4.6.1-1 x86_64 There is a forum thread here: http://bbs.archlinux.org/viewtopic.php?id=90720 where others have reported the same issue. Steps to reproduce: Install qt 4.6.1-1 on a multi-head setup Open a QT application like Google Earth or Marble Put the application on a secondary screen Click a menu Observe that no menu appears |
This task depends upon
Closed by Andrea Scarpino (BaSh)
Sunday, 11 April 2010, 11:22 GMT
Reason for closing: Fixed
Additional comments about closing: awesome 3.4.4-1
Sunday, 11 April 2010, 11:22 GMT
Reason for closing: Fixed
Additional comments about closing: awesome 3.4.4-1

Forgot to mention that I'm using the nvidia driver on a GeForce
GTX 285.

Does this also happen with nv, vesa or nouveau drivers? However,
this should be reported upstream then. There is nothing I could do
about it here. (I don't have a multi monitor setup anyway)

Could be a bug in xorg-server. The final commit upstream mentions
something with gradient and solid fill pictures with Xinerama.
I'll see if I can update xorg-server today, there's a new release
candidate for 1.7.5.

Reported upstream to qt at
http://bugreports.qt.nokia.com/browse/QTBUG-8189

Bug reported to awesomewm at
http://awesome.naquadah.org/bugs/index.php?do=details&task_id=732

Is this fixed with xorg-server 1.7.5? There's several
Xinerama-related fixes in that version.

Note that a workaround in upstream awesome has been issued and is
part of 3.4.4.

Sounds like not a lot to do but wait on upstream here. It seems
clear there's ways for apps to work around this, and some already
are, but upstream qt needs to make the real fix.