Switching between windows of the same program is broken

Bug #1485330 reported by teo1978
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
compiz (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

This is not systematically reproducible, but it happens very often.

Here's the sequence of actions and what happens (again, don't expect to be able to reproduce at the first try, this happens RANDOMLY):

1 - I have several windows of the same program open. E.g. several terminal windows or several Gedit windows, let's call it program X.
2 - None of them is currently focused. Focus is on some other window of some other program
3 - I click on the icon of program X in the launcher
=> one of the windows get focused, but let's assume it's not the one I want
4 - so I click again on program X's icon in Launcher
=> all the existing open windows of program X become visible on the screen, resized and layed out one next to the other allowing you to choose which one you want to focus
5 - I click on one of them
=> ANOTHER ONE gets focus instead
6 - so I repeat steps 4 and 5
=> this time the one I ckicked comes to the foreground (this always works the second time), BUT it doesn't have the title bar and borders (and I'm not sure if it gets focused and usable, because I am always so annoyed by not being able to move the window, that I cannot continue working until I do the workaround and get the complete window)

You can repeat steps 4-5 as many times as you want but it will never work as long as you keep selecting the desired window

My workaround is to repeat steps 4-5 again, and select another window of the same program, other than the one I want. Then, all the windows of program X (including the one I want) are visible and have the title bars and borders, so I can switch to the one I want by clicking directly on it (in real size, without clicking the Launcher icon again). But in order to do so, depending on how the windows were laid out, I may need to move them, or unfullscreen one if it was fullscreened.

This bug is unhumanly annoying and has been around at least since 14.04, and I'm frustrated to see it's not fixed in 15.04

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2
Uname: Linux 3.19.0-25-generic x86_64
.tmp.unity.support.test.0:

ApportVersion: 2.17.2-0ubuntu1.2
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Sun Aug 16 16:44:41 2015
DistUpgraded: 2015-08-15 21:46:56,607 DEBUG enabling apt cron job
DistroCodename: vivid
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.7, 3.19.0-25-generic, x86_64: installed
 vboxhost, 4.3.14, 3.13.0-61-generic, x86_64: installed
 vboxhost, 4.3.14, 3.16.0-44-generic, x86_64: installed
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] Device [1025:0647]
 NVIDIA Corporation GF117M [GeForce 610M/710M/820M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691]
InstallationDate: Installed on 2013-10-11 (673 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MachineType: Acer Aspire V3-571G
PackageArchitecture: all
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic.efi.signed root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7
SourcePackage: compiz
UpgradeStatus: Upgraded to vivid on 2015-08-15 (0 days ago)
dmi.bios.date: 10/15/2012
dmi.bios.vendor: Acer
dmi.bios.version: V2.07
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: VA50_HC_CR
dmi.board.vendor: Acer
dmi.board.version: Type2 - Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V2.07
dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07:
dmi.product.name: Aspire V3-571G
dmi.product.version: V2.07
dmi.sys.vendor: Acer
version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.60-2
version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1
xserver.bootTime: Sat Aug 15 23:24:41 2015
xserver.configfile: default
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
 NOUVEAU(G0): [XvMC] Failed to initialize extension.
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 8940
 vendor AUO
xserver.version: 2:1.17.1-0ubuntu3

Revision history for this message
teo1978 (teo8976) wrote :
Changed in compiz (Ubuntu):
status: New → Confirmed
Revision history for this message
teo1978 (teo8976) wrote :

Sorry but I am confirming my own bug because it's been around for years and it's still here after two major releases and there's no point in waiting for some other random user to stumble upon the report and confirm it. The bug is there.

Revision history for this message
teo1978 (teo8976) wrote :

Quite possibly related: #1485333

Though the first part of #1485333 is new, there you'll find 100% reproducible steps which will also reproduce this issue.

Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

I confirm the bug is true ;)

Changed in compiz (Ubuntu):
importance: Undecided → Medium
Revision history for this message
teo1978 (teo8976) wrote :

The importance of this bug is clearly "high", not medium. It meets at least two of the criteria:

- Has a moderate impact on a large portion of Ubuntu users (estimated)
- Impacts accessibility of a core application

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.