FS#32298 - [thunar, firefox, xorg-server] problems with context menu using Multipointer X

Attached to Project: Arch Linux
Opened by Gleb (user_1000) - Tuesday, 30 October 2012, 13:35 GMT
Last edited by Andreas Radke (AndyRTR) - Saturday, 23 February 2013, 13:02 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Tobias Powalowski (tpowa)
Jan de Groot (JGC)
Andreas Radke (AndyRTR)
Ionut Biru (wonder)
Evangelos Foutras (foutrelis)
Architecture i686
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: When using MPX, thunar and firefox will only let the first cursor close a context menu or select an item from a menu, no matter what cursor opened the menu.


Additional info:
* package version(s)
thunar 1.4.0-2
firefox 16.0.2-1
xorg-server 1.13.0-3


Steps to reproduce (thunar):
1. Create second pointer as written in https://wiki.archlinux.org/index.php/Multi-pointer_X
2. Start thunar;
3. Using second pointer right click on any file or folder intending for exampe rename it;
4. Note that it's impossible to use context menu and close it using secondary pointer;
5. It possible to close context menu only using primary pointer.

Steps to reproduce (firefox)
1. Create second pointer;
2. Start firefox;
3. Open any web page;
4. Using primary pointer select some text intending to copy it then perform right click calling context menu;
5. Note that some times it leads to same results as thunar application; Also often using secondary pointer impossible to use menus Files, History, Bookmarks etc. The menu is opened but normally impossible to select item and close the menu.

The problem is suspected to be Upstram Bugs because there is similar bug registred as confirmed on launchpad:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/576234
This task depends upon

Closed by  Andreas Radke (AndyRTR)
Saturday, 23 February 2013, 13:02 GMT
Reason for closing:  Upstream
Comment by Jan de Groot (JGC) - Monday, 17 December 2012, 11:38 GMT
Did anyone push this report upstream, or do you expect that this will fix itself magically?

Loading...