After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 583759 - Can drag panel to smaller edge, making it impossible to drag back
Can drag panel to smaller edge, making it impossible to drag back
Status: RESOLVED OBSOLETE
Product: gnome-panel
Classification: Other
Component: panel
2.26.x
Other All
: Normal normal
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-05-25 00:19 UTC by Josh Triplett
Modified: 2020-11-06 20:22 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26



Description Josh Triplett 2009-05-25 00:19:42 UTC
Please describe the problem:
If you drag the GNOME panel from its existing position to a smaller
edge of the screen, the reduced space may mean the panel no longer has
any empty space to grab to drag it back.


Steps to reproduce:
Have a panel on the long edge of the screen with a few launchers, a clock, a tray, and a window list with several windows open, such that you don't have much space left in the panel.  Drag the panel from the long edge of the screen to the short edge of the screen.

Actual results:
The panel no longer has any free space to grab and drag the panel back.

Expected results:


Does this happen every time?


Other information:
Comment 1 Josh Triplett 2009-05-25 00:20:08 UTC
Originally reported as Debian bug 505808: http://bugs.debian.org/505808
Comment 2 André Klapper 2020-11-06 20:22:53 UTC
bugzilla.gnome.org is being replaced by gitlab.gnome.org. We are closing all old bug reports in Bugzilla which have not seen updates for many years.

If you can still reproduce this issue in a currently supported version of GNOME (currently that would be 3.38), then please feel free to report it at https://gitlab.gnome.org/GNOME/gnome-panel/-/issues/

Thank you for reporting this issue and we are sorry it could not be fixed.