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 160549 - Panel applets and icons get relocated after a screen resize
Panel applets and icons get relocated after a screen resize
Status: RESOLVED DUPLICATE of bug 137473
Product: gnome-panel
Classification: Other
Component: panel
2.8.x
Other All
: Normal normal
: ---
Assigned To: Panel Maintainers
Panel Maintainers
: 305629 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2004-12-06 00:10 UTC by Patrick Wagstrom
Modified: 2015-03-24 13:00 UTC
See Also:
GNOME target: ---
GNOME version: 2.7/2.8



Description Patrick Wagstrom 2004-12-06 00:10:37 UTC
Please describe the problem:
When using XRandR to resize the desktop, the panel sometimes forgets where it
placed it applets, launchers, and the such.  For example, after resizing to a
lower resolution and back again, my Applications menu now sits about 400 pixels
from the left of the screen.  It is still "locked" in that position.

Steps to reproduce:
1. Start up GNOME in normal higher resolution (1400x1050 in my case)
2. Switch to 1024x768 and give a presentation (1 hour or so)
3. Switch back to 1400x1050 and see how the menus have moved over and the first
couple of hundred pixels of the panel are unused.


Actual results:
Menus and applets are moved around on the panel.

Expected results:
The applets should remember their position on relative terms or something like
that.  If I switch resolution, I should not have my applets and launchers all
moving, it's just annoying.

Does this happen every time?
This happens most of the time when I resize the panel.  Usually it requires me
to stay in the lower resolution mode for an extended period of time.  Restarting
doesn't fix it because I'm assuming the changes are automatically saved.

Other information:
This could possibly be related to bug 141372 which describes icons moving when
new icons are placed on the panel.
Comment 1 Gero 2005-02-04 18:35:39 UTC
Confirmed for Gnome 2.9.90
Unfortunately, I cannot change the status to CONFIRMED...
Comment 2 Rod Butcher 2005-02-06 01:50:50 UTC
I can confirm this error with expand=no, but it does not occur with expand=yes.
When it occurs, changing expand to yes corrects it.
Comment 3 Gero 2005-02-06 02:28:02 UTC
Rod, could you be a bit more specific please, which expand option you refer to?
Where can it be activated? That would be great if the solution is this simple! :-)
Comment 4 Rod Butcher 2005-02-06 04:10:28 UTC
"Expand" is the first option on the "Panel Properties" tab , activated by
rightclicking on the panel.
However, it's not really a solution, as the panel should be correctly
repositioned if "expand" is not set also.
Seems like there's some necessary logic after a screen resolution change that
only gets executed if "expand" is set.
Comment 5 Gero 2005-02-06 12:54:03 UTC
Thanks. Actually, activating the "expand"-option does not solve the problem for
me--things are still shifted around. (Using "Screen Resolution Preferences" in
Gnome 2.9.90.)
Comment 6 Sebastien Bacher 2005-07-10 13:23:32 UTC
*** Bug 305629 has been marked as a duplicate of this bug. ***
Comment 7 Vincent Untz 2006-01-24 19:29:40 UTC
Mass changing: milestone 2.12.x => milestone 2.14.x
Comment 8 Sebastien Bacher 2006-04-01 10:21:04 UTC
Ubuntu bug about that: https://launchpad.net/distros/ubuntu/+source/gnome-panel/+bug/37546
Comment 9 Elijah Newren 2006-06-17 03:59:28 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 137473 ***
Comment 10 Sebastien Bacher 2006-06-17 17:09:21 UTC
Elijah, are you sure that's a duplicate? That bug is not specific to rightstick. Or maybe the title of the other bug need to be updated?
Comment 11 Elijah Newren 2006-06-17 20:14:39 UTC
Sebastien: Check out bug 152019, which Vincent marked as a duplicate.  I belive this bug is a duplicate of 152019 (feel free to point out if I'm wrong, though) and I would have marked as a duplicate of that bug, but since it was already marked as a dupe...