Windows move on their own when i click on the desktop
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
compiz (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
I dont know where the problem is, but i see it often.
I am using dual monitors.
Using Gnome fallback (classical mode)
Compiz is enabled and the special effects like wobbly windows are enabled.
I notice the following problem in multiple programs, but most often in the two i use most: Totem Movie Player and Vuze.
I will be using a program and then click on the desktop or another program. the window of the first program will move on its own, somewhere else on the same screen. each time i click somewhere that is not inside the first program, the window will move. sometimes it will move to the top of the screen, sometimes to the bottom, usually it tries to travel to the right in addition to either up or down.after it gets to the right edge, it pops to the left side of the same monitor.
if i close Vuze (it hides to the tray) and reopen it, everything is fine again for a few hours. or if its another program, i close it and reopen it, it will be fine.
Sometimes the problem will go away if i continue to use the program for a bit longer and then click away.
Totem movie player has its own unique twist when i encounter the problem with it.
Say i just opened a video on my left monitor. i double click on the movie to make it full-screen, and then go back to my work on my right monitor (primary). i click on something. the fullscreen movie immediately pops over to my right screen! i double click it to go back to windows mode, and its on my left screen again. rinse & repeat.
This only stopped popping on my right screen when i told it to go to fullscreen using [F11] instead of double clicking. (i didnt need to close the program this time.)
i have also seen lifera move around in both ways. in a window it will move around the monitor it currently is on, or when maximized, it will pop between monitors.
really, the only program i use often that i haven't seen move is whatever program shows open folders (Nautilus? idk). but maybe it has, i'm not sure.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: xorg 1:7.6+12ubuntu1
ProcVersionSign
Uname: Linux 3.2.0-23-generic x86_64
NonfreeKernelMo
.proc.driver.
.proc.driver.
.proc.driver.
NVRM version: NVIDIA UNIX x86_64 Kernel Module 295.40 Thu Apr 5 21:37:00 PDT 2012
GCC version: gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu4)
.tmp.unity.
ApportVersion: 2.0.1-0ubuntu5
Architecture: amd64
CompizPlugins: [core,bailer,
CompositorRunning: compiz
Date: Fri Apr 20 01:19:26 2012
DistUpgraded: 2012-04-11 00:38:24,038 DEBUG enabling apt cron job
DistroCodename: precise
DistroVariant: ubuntu
ExtraDebuggingI
GraphicsCard:
NVIDIA Corporation G98 [GeForce 8400 GS] [10de:06e4] (rev a1) (prog-if 00 [VGA controller])
Subsystem: eVga.com. Corp. Device [3842:c738]
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
JockeyStatus:
xorg:nvidia_
xorg:nvidia_
MachineType: OEM OEM
ProcKernelCmdLine: BOOT_IMAGE=
SourcePackage: xorg
Symptom: display
UdevDb: Error: [Errno 2] No such file or directory
UpgradeStatus: Upgraded to precise on 2012-04-11 (9 days ago)
dmi.bios.date: 07/24/2008
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: Bearlake
dmi.board.vendor: Intel
dmi.board.version: Fab D
dmi.chassis.type: 3
dmi.chassis.vendor: OEM
dmi.chassis.
dmi.modalias: dmi:bvnPhoenixT
dmi.product.name: OEM
dmi.product.
dmi.sys.vendor: OEM
version.compiz: compiz 1:0.9.7.6-0ubuntu1
version.ia32-libs: ia32-libs 20090808ubuntu35
version.libdrm2: libdrm2 2.4.32-1ubuntu1
version.
version.
version.
version.
version.
version.
version.
version.
version.
affects: | ubuntu → xorg (Ubuntu) |
affects: | xorg (Ubuntu) → compiz (Ubuntu) |
Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 974242, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.