Clicking on an app icon doesn't work if it's opened in another workspace

Bug #1883390 reported by Tiger
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
unity (Ubuntu)
New
Undecided
Unassigned

Bug Description

My Ubuntu version is a 16.04 LTS.
I make regularly updates using the console commands.
sudo apt-get update upgrade dist-upgrade autoremove

Steps to reproduce the bug

1- open an app, for example the terminal in workspace 1

2- go to workspace 2 and click in the left bar on the terminal icon

Results: the process is not switching to workspace 1 where the terminal is already opened.

It was working perfectly before and I made no changes to my system except the updates.

I discover this issue with another one.

Some applications, it's the case for terminal, when being opened are placed too high and their handle title bar are behind Ubuntu top bar.
---
.tmp.unity_support_test.0:

ApportVersion: 2.20.1-0ubuntu2.23
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
DistUpgraded: 2018-06-03 22:20:12,658 DEBUG /openCache(), new cache size 87127
DistroCodename: xenial
DistroRelease: Ubuntu 16.04
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company 4th Gen Core Processor Integrated Graphics Controller [103c:2101]
InstallationDate: Installed on 2018-01-12 (906 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
MachineType: Hewlett-Packard HP ProBook 650 G1
Package: unity 7.4.5+16.04.20190312-0ubuntu1
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-184-generic root=UUID=4fd5248b-09d7-44d4-b495-41e00741bb9e ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.4.0-184.214-generic 4.4.223
Tags: xenial xenial xenial ubuntu compiz-0.9
Uname: Linux 4.4.0-184-generic x86_64
UpgradeStatus: Upgraded to xenial on 2018-06-03 (764 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 04/29/2014
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: L78 Ver. 01.05
dmi.board.name: 2101
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 16.38
dmi.chassis.asset.tag: CNU420C9KF
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvrL78Ver.01.05:bd04/29/2014:svnHewlett-Packard:pnHPProBook650G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.38:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP ProBook 650 G1
dmi.product.version: A3009DD10303
dmi.sys.vendor: Hewlett-Packard
upstart.unity-panel-service.log:
 (unity-panel-service:4179): Indicator-Appmenu-WARNING **: Already have a menu for window ID 65011715 with path /com/canonical/menu/3E00003 from :1.79, unregistering that one

 (unity-panel-service:4179): Indicator-Appmenu-WARNING **: Already have a menu for window ID 65011715 with path /com/canonical/menu/3E00003 from :1.79, unregistering that one
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.91-2~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2

Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1883390/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
Revision history for this message
Paul White (paulw2u) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers.

I have classified this bug as being an issue in the 'unity' package as that is the default desktop environment in Ubuntu 16.04. If you are not using Unity then you will need to reassign this bug report to the package which is related to the desktop environment that you are currently using.

Please execute the following command as it will automatically gather debugging information, in a terminal:

   apport-collect 1883390

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

affects: ubuntu → unity (Ubuntu)
Revision history for this message
Tiger (tiger34) wrote : BootLog.txt

apport information

tags: added: apport-collected compiz-0.9 ubuntu xenial
description: updated
Revision history for this message
Tiger (tiger34) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Tiger (tiger34) wrote : Dependencies.txt

apport information

Revision history for this message
Tiger (tiger34) wrote : DpkgLog.txt

apport information

Revision history for this message
Tiger (tiger34) wrote : GsettingsChanges.txt

apport information

Revision history for this message
Tiger (tiger34) wrote : Lspci.txt

apport information

Revision history for this message
Tiger (tiger34) wrote : Lsusb.txt

apport information

Revision history for this message
Tiger (tiger34) wrote : MonitorsUser.xml.txt

apport information

Revision history for this message
Tiger (tiger34) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Tiger (tiger34) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Tiger (tiger34) wrote : ProcEnviron.txt

apport information

Revision history for this message
Tiger (tiger34) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Tiger (tiger34) wrote : ProcModules.txt

apport information

Revision history for this message
Tiger (tiger34) wrote : UdevDb.txt

apport information

Revision history for this message
Tiger (tiger34) wrote : UnitySupportTest.txt

apport information

Revision history for this message
Tiger (tiger34) wrote : XorgLog.txt

apport information

Revision history for this message
Tiger (tiger34) wrote : XorgLogOld.txt

apport information

Revision history for this message
Tiger (tiger34) wrote : Xrandr.txt

apport information

Revision history for this message
Tiger (tiger34) wrote : xdpyinfo.txt

apport information

Revision history for this message
Tiger (tiger34) wrote :

About compiz which is listed in apport-collect information.
This is something I found while trying to find information about the bug.
Someone was speaking about it, I installed it with:

sudo apt-get install compizconfig-settings-manager

But I never used it.

Revision history for this message
Tiger (tiger34) wrote :

I've some news about this bug.

I've another PC with Ubuntu 16.04 installed. The updates had not been made since some time.
I checked that the bug was not existing at that moment.

Then I did the system upgrade with sudo apt-get update, upgrade and dist-upgrade, autoremove.

And the bug did not occurred...

I know that if the developers are not able to reproduce, they'll not be able to fix that bug for my laptop.

I'm going to try to find the differences between the two laptops to give you information, but I know that maybe I'll never find it.

The most annoying is the fact that the handle of title bars of some windows are behind the Ubuntu top bar, but I can manage it with alt + mouse right click to move windows.

Maybe some Ubuntu devs will have the bug.

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.