desktop-packages team mailing list archive

[Pedro Villavicencio <pedro@xxxxxxxxxx>]

We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on the current status, under the Status column, and change
the Status back to "New". Thanks again!


** Changed in: metacity (Ubuntu)
       Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to metacity in Ubuntu.
https://bugs.launchpad.net/bugs/655711

Title:
  new, maximized windows being moved to different monitor

Status in “metacity” package in Ubuntu:
  Expired

Bug description:
  Binary package hint: metacity

  Whenever a new, maximized window is opened on my main monitor,
  metacity (i assume) moves it to my left-most monitor. Most programs
  remember whether they were maximized the last time you shut them down,
  so next time you start them they open maximized. For instance Firefox
  does this. However, a fraction of a second after the window is
  displayed on the correct monitor, it jumps to my left-most monitor!

  This is extremely annoying. I'm forever dragging windows back to my
  middle monitor, which is the largest of the three and the one I use as
  my main monitor. I've read suggestions that it had something to do
  with what my "primary" monitor is, but I can't find any reference or
  configuration item for that. My middle monitor is screen 0 however
  (the left one being 1 and the right one 2), so that would not explain
  this behaviour.

  My exact configuration is as follows: I have two Geforce 8800 GTX's.
  My middle monitor is screen 0 and is attached to the first card, the
  left (screen 1) and right (screen 2) ones are attached to the second
  card. Because I have two cards I have to use Xinerama to be able to
  use them as one desktop, I can't use TwinView.

  This behaviour only started a few months ago (I don't remember exactly
  when, so unfortunately I can't pinpoint a particular update). Before
  that the behaviour was as you would expect: windows stayed on the
  monitor on which they were opened.

  There is another bug about a very similar problem (bug #224845), but
  it is listed as "fix released" since January 2009, so this problem
  must be a new one.

  Please let me know how I can help debug this problem!

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: metacity 1:2.30.1-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.32-25.44-generic 2.6.32.21+drm33.7
  Uname: Linux 2.6.32-25-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Wed Oct  6 14:12:18 2010
  ExecutablePath: /usr/bin/metacity
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  SourcePackage: metacity
  XsessionErrors:
   (polkit-gnome-authentication-agent-1:2319): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
   (gnome-panel:2314): GConf-WARNING **: Directory `/apps/panel/toplevels/bottom_panel_screen2/screen' was not being monitored by GConfClient 0x251a300
   (gnome-panel:2314): GConf-WARNING **: Directory `/apps/panel/toplevels/top_panel_screen2/screen' was not being monitored by GConfClient 0x251a300
   (gnome-panel:2314): GConf-WARNING **: Directory `/apps/panel/toplevels/bottom_panel_screen1/screen' was not being monitored by GConfClient 0x251a300
   (gnome-panel:2314): GConf-WARNING **: Directory `/apps/panel/toplevels/top_panel_screen1/screen' was not being monitored by GConfClient 0x251a300

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/655711/+subscriptions