Okay, now for a patched gnome-panel. For this one, you'll need to install the gnome-panel and libpanel .debs. To get the old ones, recompile without the patch and reinstall the .debs. There also may be a way to force synaptic/apt-get to reinstall over the current ones, but I'm not sure what it is.
This test again puts data in ~/foo. It outputs some information on startup, and other information when the application is launched. This should tell us whether the bug is in gnome-panel or in the underlying gnome/GTK libraries. Right now I'm about 50/50 as to which I suspect. Install the debs listed above and then log out and log back in. (I've tested on my single display machine, so you should be okay as far as hosing your system, though this may leak memory.) Then run an application on screen 1 that shows up on the wrong screen (screen 0), and send the output. Thanks! ** Attachment added: "Debug patch to gnome-panel." http://launchpadlibrarian.net/27221254/C%3A%5Ccygwin%5Chome%5Cgwa%5Cgnome-panel-fdfoo.patch -- menu items selected from screen 1 open on screen 0 https://bugs.launchpad.net/bugs/346964 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
