Bug 698358 - metacity (menus( become unusable after a few clicks
Summary: metacity (menus( become unusable after a few clicks
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: metacity
Version: 15
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Owen Taylor
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-20 17:50 UTC by Jurgen Kramer
Modified: 2011-05-14 10:25 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-05-14 10:25:01 UTC
Type: ---


Attachments (Terms of Use)

Description Jurgen Kramer 2011-04-20 17:50:20 UTC
Description of problem:
When browsing around through the menu's metacity stops responding to mouse clicks (both left and right) after a short while. Only the volume control/NM and date/time respond to mouse clicks.

Version-Release number of selected component (if applicable):
metacity-2.32-0-1.git20110228.fc15.x86_64

How reproducible:
allways

Steps to Reproduce:
1. Login to GNOME3
2. Casually browse/click around
3. System no longer
  
Actual results:
System no longer responds to mouse clicks, the menu's are no longer accessible.


Expected results:
System keeps responding/menus still work 

Additional info:
This can easily be reproduces as follows:
Applications->Internet->Firefox->mouse right click->Add this launcher to panel.
Firefox gets added to the panel, menus no longer accessible, no response to mouse clicks. Only the volume control/NM and date/time respond to mouse clicks.

btw I am testing F15 Beta with KVM could be this problem is related to KVM/libvirt and friends instead of F15 itself.

Comment 1 Jurgen Kramer 2011-04-20 18:00:28 UTC
Another VM (F14) on the same machine does not exhibit this behaviour so it is probably not KVM/libvirt related. 

When I hover over the no longer functioning Menu items and launch icons as expected balloon will pop up explaining the meaning as usual. Clicking on them no longer works.

Comment 2 Jurgen Kramer 2011-05-14 10:25:01 UTC
Problem no longer there with the current RC.


Note You need to log in before you can comment on or make changes to this bug.