GNOME Bugzilla – Bug 152962
Floating Panel Cannot be accessed
Last modified: 2004-12-22 21:47:04 UTC
Please describe the problem: I'm using Gnome in Libranet 2.8.1. In Yelp 2.2.8 it says it is Gnome 2.0. I selected the Floating Panel, then, with the panel in the "vertical" position, in "properties", I unchecked the "Show hide buttons" AND the "Arrows on hide buttons". It is placed just above the lower panel. The panel became a thin line 17mm long and 1mm thick that is not accessable. I cannot select it for "Properties", to add anything to it, or to kill it. I have searched for hours to find its repository to delete it, but I can't find it. If this is not a bug, could you please tell me where it is defined so I can remove it. Steps to reproduce: 1. Select a Floating Panel 2. Move it "vertically" oriented to a location at the upper edge of the lower panel. 3. Uncheck the "Show hide buttons" and the "Arrows on hide buttons". Actual results: The panel becomes a thin line 17mm long and 1mm wide that cannot be accessed. Expected results: I would expect that I could access the panel to add apps to, access the "properties" function etc. Does this happen every time? I do know because I'm afraid to do it again because I do not want any more panel residuals stuck on my desktop. Other information: I want to know in what directory these panels are defined so that I can go in and delete the offending residual panel. Thank you very much! I appreciate the Gnome Desktop because it has overcome deficiencies I found with KDE, Libranet, and IceWM Window Managers. I'm thrilled with what I can do with the "Drawers" and "Floating Panels". One aside: I was at first dismayed to find I could not edit the properties of the Desktop Applications until I realized I could create them first in the panel, edit as necessary, and then drag to the Desktop. That would be a good thing to emphasize in the Helps.
*** Bug 152963 has been marked as a duplicate of this bug. ***
This is fixed since GNOME 2.4. You should probably upgrade if possible. *** This bug has been marked as a duplicate of 82642 ***