Ubuntu 16.04.1 unity disappears when set to autohide

Bug #1606358 reported by Walt Corey
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
unity (Ubuntu)
New
High
Unassigned

Bug Description

Initially I was going to report this against a completely working 16.04 VM using spice. In that case the system, once rebooted after the upgrade failed to show launcher at all and no desktop applications could be moved. This is new behavior in 16.04.1. All these things worked in 16.04.

To have a clean slate I created a brand new VM with the brand new 16.04.1 iso. It came up using spice just fine, as the default for the launcher is autohide off. As I prefer the full desktop I turned autohide to on and voilà.

Should you need further details, let me know. I use VMs to test new systems before I upgrade my production 14.04 system to 16.04. As it is an desktop existing system I am awaiting the software-updater prompt.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: unity 7.4.0+16.04.20160715-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
.tmp.unity_support_test.1:

ApportVersion: 2.20.1-0ubuntu2.1
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: Mon Jul 25 15:20:45 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 04) (prog-if 00 [VGA controller])
   Subsystem: Red Hat, Inc QEMU Virtual Machine [1af4:1100]
GsettingsChanges:
 b'org.compiz.core' b'outputs' b"['1440x900+0+0']"
 b'org.compiz.core' b'active-plugins' b"['core', 'composite', 'opengl', 'place', 'copytex', 'regex', 'move', 'session', 'mousepoll', 'imgpng', 'wall', 'fade', 'snap', 'vpswitch', 'compiztoolbox', 'workarounds', 'resize', 'grid', 'expo', 'scale', 'unitymtgrabhandles', 'ezoom', 'unityshell']"
 b'com.ubuntu.user-interface' b'scale-factor' b"{'VGA-1': 8, 'Virtual-0': 8}"
 b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
 b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1'
InstallationDate: Installed on 2016-07-25 (0 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic root=UUID=31a93994-4f44-4017-bbb5-be2d96dcf420 ro quiet splash vt.handoff=7
Renderer: Software
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/01/2011
dmi.bios.vendor: Bochs
dmi.bios.version: Bochs
dmi.chassis.type: 1
dmi.chassis.vendor: Bochs
dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2011:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-trusty:cvnBochs:ct1:cvr:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-trusty
dmi.sys.vendor: QEMU
version.compiz: compiz 1:0.9.12.2+16.04.20160714-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
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
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Mon Jul 25 15:18:58 2016
xserver.configfile: default
xserver.devices:
 input Power Button KEYBOARD, id 6
 input AT Translated Set 2 keyboard KEYBOARD, id 7
 input VirtualPS/2 VMware VMMouse MOUSE, id 8
 input VirtualPS/2 VMware VMMouse TOUCHSCREEN, id 9
xserver.errors: AIGLX: reverting to software rendering
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs: Output Virtual-0 Virtual-1 Virtual-2 Virtual-3
xserver.version: 2:1.18.3-1ubuntu2.2
xserver.video_driver: qxl

Revision history for this message
Walt Corey (commwrc) wrote :
Revision history for this message
temporaryname (f896421-deactivatedaccount) wrote :

See also http://askubuntu.com/questions/802468/menu-bar-and-launcher-missing-after-installing-updates-16-04-lts

This is what helped me:

[general_ubuntu-lowgfx]
profile = unity-lowgfx

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug report. It's not clear what you change and try exactly. Do you turn on the launcher setting and restart your session? Does unity fails to start or do you just fail to trigger the launcher by hitting the left border in a vm? (that doesn't seem to work for me but it's the same in stock 16.04 and with the update)s

Changed in unity (Ubuntu):
importance: Undecided → High
status: New → Incomplete
Revision history for this message
Walt Corey (commwrc) wrote :

I guess I don't understand your question concerning what I changed. My change was to upgrade a perfectly good 16.04 image that functioned perfectly and after the upgrade and subsequent reboot there was no louncher and if I started Netbeans 8.1 (a desktop icon) or started a terminal session, both would start, neither were draggable.

It's unclear to me why the importance went from undecided to High (which, yeah, I agree with as it's a major functionality regression, the status from new to incomplete. I gave perfectly reproduceable steps. As for what daemon or process is running I don't know. I am guessing it would take less than 30 mins to have an 'in the lab' reproduction' of the issue. In other words, this is not a wedge use case.

As for your question about turning on the autohide and restarting. I did that too but as soon as I set no to yes, the problem existed. Uppon reboot, it still existed. I hope that makes sense. What else would you like? Oh, apport started throwing exceptions when I used it to create this bug so perhaps everything it was supposed to provide was missing.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Sorry but things are not clear, your description sounds like unity stopped loading but those are contradictory statements

"My change was to upgrade a perfectly good 16.04 image that functioned perfectly and after the upgrade and subsequent reboot there was no louncher"

and "I turned autohide to on and voilà."

Does it happen if you install a stock 16.04.1 or or 16.04 and upgrade it without changing any setting? Or does it only do it if you change the launcher settings?

Do you get a .crash in /var/crash? If so could you report it with ubuntu-bug so informations can be collected, attaching it to a bug doesn't help us to get the needed details

Revision history for this message
Walt Corey (waltc) wrote :

OK, I did describe two steps to reproduce. In the original case, it was an existing 16.01 current with maintenance, that I in-place upgraded. As it was existing I had already switched the launcher from autohide=off to autohide=yes as well I already had a desktop icon. so there were two artefacts of the upgrade, 1) no access to launcher and 2) applications on the desktop were functional but there were not dragable by the window's title bar. In order to determine if that was an upgrade bug or a 16.04.1 bug I created a fresh vm of JUST 16.04.1 and could reproduce the initial symptom of the launcher being absent but the terminal window (context menu->new terminal) was drag-able.

There was a crash file in the first case of upgrading an existing current 16.04 vm. I can get it to submit.

Revision history for this message
Walt Corey (waltc) wrote :

Sorry, I can NOT get it to submit.

Revision history for this message
Sebastien Bacher (seb128) wrote :

hum, ok, I can't confirm here in a virtualbox image nor by forcing the lowgfx profile on a normal session

what error do you get if you try to submit the bug? can you clean the directory and try again to see if a new report is generated?

Changed in unity (Ubuntu):
status: Incomplete → New
Revision history for this message
Walt Corey (waltc) wrote :

There is this guy..
http://askubuntu.com/questions/802468/menu-bar-and-launcher-missing-after-installing-updates-16-04-lts

which addresses virtualbox specifically.

It wouldn't submit, literally nothing happened. Now that was under a 16.04 image that was upgraded to 16.04.1.

When I did a fresh 16.04.1 install into VirtManager, yes, it worked, right up until I set launcher to autohide, then it was good night Charlie Brown. . If you are not using an existing 16.04(.0) image then you can't reproduce the issue. But, as you can see from the above URL, someone else reported the very same upgrade problem as I did.

SOmething you should take a look at is 1001255, that is likely the culprit, with the exception of unable to move windows, as I reported as well as the above url.

Are there no launchpad bugs opened against 16.04.1 re: immovable desktop windows? Being a VM I am guessing the image's concept of its video device is done externally like spice/qxl. Remember, when you first boot a new image, the launcher is set to autohide=no. Turning autohide=yes will immediately create the issue. As I mentioned im my comment in the above askubuntu issue, renaming that subdir simply restores the laucher, it does not fix autohide=yes.

Ah, very interesting! I brought that image back and the suggested 'fix' of removing .config/compiz-1 restores the launcher but disables any effect of setting the autohide. I showed it as autohide on yet the launcher was visbile. I did restore setting, which turned autohide=off and then switched it to on and it is showing, regardless of what I do.

I thought I'd try it with a different browser. I see chrome is not an option so I tried the ubuntu brand browser...it won't let me choose the file to attach. This stuff, your bug-ubuntu needs some work. This is crazy. I just tried firefox again and it allows me to choose files but the Submit Bug Report button is inop.

It appears I can provide no further information. The other thing Sebastien, if you can not reproduce the bug, you can't verify the fix.

This is a critical bug for me. I can not upgrade existing 14.04 desktops if doing so breaks them.

Revision history for this message
Walt Corey (waltc) wrote :

Hooray Hooray.. problem # is 1607070. I hope that helps Sebastien.

The file did not allow read access, which caused the submit to fail.

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

Duplicates of this bug

Other bug subscribers

Remote bug watches

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