Nautilus window jumping with dual monitors
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nautilus (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Not sure whether this is a Nautilus bug or window manager bug, but here goes ...
A bug report has already been filed at askubuntu : http://
I have a dual monitor setup (big desktop style where mouse goes from one screen to the other) in Precise 12.04.2 with my laptop on the left and external screen on the right. I have an ATI Radeon HD3635 card using fglrx drivers and I'm always using the Gnome Classic (No effects) environment.
What happens:
1. Open Nautilus program on ext screen and maximize it
2. Double click on a random folder
3. The Nautilus window jumps to the laptop screen
What should happen:
1. Open Nautilus program on ext screen and maximize it
2. Double click on a random folder
3. The Nautilus window should stay where it is. On the ext screen.
When it doesn't happen:
1. Open Nautilus program on ext screen and make sure it's not maximized
2. Double click on random folder
3. The Nautilus window stays on the ext screen
I also have a startup script doing this:
/usr/bin/xrandr --output CRT1 --right-of LVDS
/usr/bin/xrandr --output CRT1 --primary
Where CRT1 is the ext screen and LVDS is laptop screen.
Any help is appreciated, even more because Precise stays supported until 2017. And it's an annoying bug. ;)
---
ApportVersion: 2.0.1-0ubuntu17.3
Architecture: i386
DistroRelease: Ubuntu 12.04
GsettingsChanges:
org.gnome.
org.gnome.
org.gnome.
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
MarkForUpload: True
NonfreeKernelMo
Package: nautilus 1:3.4.2-0ubuntu8
PackageArchitec
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
Tags: precise
Uname: Linux 3.2.0-48-
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
description: | updated |
Thanks for your bug report. I'll confirm this, as from the ask ubuntu link there are two people experiencing this problem. Not sure how to fix it though, sorry!
Could you please run "apport-collect 1195725" in a terminal? That will attach some relevant debugging information to this report.