Bug 111045

Summary: bottom panel sometimes get stuck in visible mode
Product: [Fedora] Fedora Reporter: Marc Williams <marcjw53>
Component: gnome-panelAssignee: Mark McLoughlin <markmc>
Status: CLOSED DUPLICATE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 1CC: bart.martens, leonard-rh-bugzilla
Target Milestone: ---   
Target Release: ---   
Hardware: athlon   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-02-21 19:00:12 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Marc Williams 2003-11-26 17:52:57 UTC 
Description of problem:
I have my bottom panel set for Autohide and it mostly works fine.  But
it sometimes gets stuck in visible mode and won't go back to being
hidden unless I right click somewhere on the panel.

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

How reproducible:
Not very.  It happens a couple or more times/day but I haven't figured
out how to reproduce the exact sequence.

Steps to Reproduce:
1.  I haven't figured out how to exactly reproduce this.
2.
3.
  
Actual results:


Expected results:


Additional info:
It does seem to happen more if I have one of my windows (Firebird,
gedit, etc) set at maximized and then inadvertently touch the mouse
down to the screen bottom causing the panel to pop up.  But as I said
earlier, this doesn't happen all the time or even usually.  Just
sometimes.
Comment 1 Marc Williams 2003-12-01 20:47:47 UTC 
Aha!!  I found out how to reproduce this bug!

With the bottom panel in Autohide mode and hidden, *quickly* touch the
bottom of the screen.  The panel will appear and not go back on its own.
Comment 2 Bart Martens 2004-02-06 20:57:09 UTC 
A patch for this problem is attached to bug 104178.
Comment 3 Leonard den Ottolander 2004-02-13 18:36:26 UTC 
That means this report is essentially a DUPLICATE.
Comment 4 Bart Martens 2004-02-16 06:15:57 UTC 
Marc, do you agree that this bug is a duplicate of bug #104178 ?
Comment 5 Marc Williams 2004-02-16 13:28:20 UTC 
Yes, it would seem to be.
Comment 6 Miloslav Trmac 2004-02-17 19:39:19 UTC 

*** This bug has been marked as a duplicate of 104178 ***
Comment 7 Red Hat Bugzilla 2006-02-21 19:00:12 UTC 
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.