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 169697 - Corner panel wanders away
Corner panel wanders away
Status: RESOLVED DUPLICATE of bug 160765
Product: gnome-panel
Classification: Other
Component: panel
2.9.x
Other Linux
: Normal normal
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-03-09 14:17 UTC by Reinout van Schouwen
Modified: 2005-03-30 06:50 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10

Attachments
panel configuration dump (167.34 KB, text/plain)
2005-03-29 14:40 UTC, Reinout van Schouwen 		Details

Description Reinout van Schouwen 2005-03-09 14:17:51 UTC 
Distribution/Version: MandrakeCooker

This bug was introduced somewhere in the 2.9 series.

I have an autohiding corner panel with just a workspace switcher in the lower
right corner of the screen. Each time I login, it has 'wandered' to the left and
I need to drag it back to the corner.

Instead, it should stay wherever I placed it, at the next login.
Comment 1 Vincent Untz 2005-03-09 14:29:08 UTC 
Weird. I never saw this. I suppose you can always reproduce...
I'll try to look at it, but it's definitely weird.
Comment 2 Reinout van Schouwen 2005-03-09 14:30:09 UTC 
Reproducable on two distinct installations, indeed.
Comment 3 Vincent Untz 2005-03-29 14:26:47 UTC 
Reinout: I tried and could not reproduce. Could you attach your panel config
(gconftool-2 --dump /apps/panel > panelconf.txt)?
Comment 4 Reinout van Schouwen 2005-03-29 14:40:51 UTC 
Created attachment 39384 [details]
panel configuration dump

Sure, here it is.
Comment 5 Vincent Untz 2005-03-30 06:50:47 UTC 
Ok. I get it.
In fact, the main problem is bug #107622. Another problem is bug #160765.
Combination of both bugs causes your bug.

I'm closing as duplicate of bug #160765.

*** This bug has been marked as a duplicate of 160765 ***