Bug 433804 - Panel Position on MultiScreen setup not persistant
Summary: Panel Position on MultiScreen setup not persistant
Status: RESOLVED FIXED
: 465984 (view as bug list)
Alias: None
Product: openSUSE 11.1
Classification: openSUSE
Component: GNOME (show other bugs)
Version: Beta 2
Hardware: x86-64 Other
: P2 - High : Normal (vote)
Target Milestone: ---
Assignee: Federico Mena Quintero
QA Contact: E-mail List
URL:
Whiteboard: core-desktop, wrong-position
Keywords:
Depends on:
Blocks: randr-tracker
  Show dependency treegraph
 
Reported: 2008-10-09 10:21 UTC by Stephane Delcroix
Modified: 2009-09-18 22:28 UTC (History)
4 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stephane Delcroix 2008-10-09 10:21:49 UTC
the multi-display thing is finally working for me on this x61t out of the box.

Federico, I'll love you soooooo much (and I won't say more to avoid breaking any COBE rule)

But the GNOME panel always pop-up on the external display. I can move it to the main one, but this setting is not persistent across plugs/unplugs. it's a bit annoying...
Comment 1 Vincent Untz 2008-10-16 10:30:14 UTC
Stéphane: can you attach the content of /apps/panel/toplevels before and after you move your panel?
Comment 2 Stephane Delcroix 2008-10-16 10:52:52 UTC
with a single (laptop) screen:
gconftool-2 -R /apps/panel/toplevels
 /apps/panel/toplevels/bottom_panel_screen0:
  y = 0
  enable_animations = true
  enable_buttons = false
  disable_movement = true
  x_right = -1
  hide_delay = 500
  unhide_delay = 500
  size = 24
  y_bottom = 0
  expand = true
  name = 
  y_centered = false
  x_centered = false
  auto_hide_size = 6
  orientation = bottom
  screen = 0
  monitor = 0
  x = 0
  auto_hide = false
  enable_arrows = true
  /apps/panel/toplevels/bottom_panel_screen0/background:
   image = 
   type = color
   fit = false
   color = #ffffff
   opacity = 14207
   rotate = false
   stretch = false

plugging the external monitor, setting its resolution, moving it to the left of the laptop one, Apply'ing (the panel is on the exernal monitor):
gconftool-2 -R /apps/panel/toplevels
 /apps/panel/toplevels/bottom_panel_screen0:
  y = 0
  enable_animations = true
  enable_buttons = false
  disable_movement = true
  x_right = -1
  hide_delay = 500
  unhide_delay = 500
  size = 24
  y_bottom = 0
  expand = true
  name = 
  y_centered = false
  x_centered = false
  auto_hide_size = 6
  orientation = bottom
  screen = 0
  monitor = 0
  x = 0
  auto_hide = false
  enable_arrows = true
  /apps/panel/toplevels/bottom_panel_screen0/background:
   image = 
   type = color
   fit = false
   color = #ffffff
   opacity = 14207
   rotate = false
   stretch = false

Unlocking the panel, moving it, relocking:
gconftool-2 -R /apps/panel/toplevels
 /apps/panel/toplevels/bottom_panel_screen0:
  y = 0
  enable_animations = true
  enable_buttons = false
  disable_movement = true
  x_right = -1
  hide_delay = 500
  unhide_delay = 500
  size = 24
  y_bottom = 0
  expand = true
  name = 
  y_centered = false
  x_centered = false
  auto_hide_size = 6
  orientation = bottom
  screen = 0
  monitor = 1
  x = 0
  auto_hide = false
  enable_arrows = true
  /apps/panel/toplevels/bottom_panel_screen0/background:
   image = 
   type = color
   fit = false
   color = #ffffff
   opacity = 14207
   rotate = false
   stretch = false
Comment 3 Vincent Untz 2008-10-16 11:11:07 UTC
So, this is happening because the laptop screen is not monitor 0 but monitor 1 when you plug the external device. It should stay monitor 0, IMHO, and there's nothing the panel can do there, I'd guess.

Federico: this sounds like a bug for you ;-)
Comment 4 Stephane Delcroix 2008-11-03 10:58:34 UTC
not sure the priority is that high, but it's annoying. and still present in beta3
Comment 5 Federico Mena Quintero 2009-02-16 19:47:49 UTC
*** Bug 465984 has been marked as a duplicate of this bug. ***
Comment 6 Vincent Untz 2009-09-18 22:28:53 UTC
I fixed this upstream during 2.27.