This is an amazing bug trail! A lot has been done and @Timo, thanks for the work so far. I have an update that might help.
I have 2 laptops, a ASUS and a Lenovo. They both had the issue. I did a reinstall of Ubuntu 16.04 on the Lenovo keeping the home folder. First I had the "no launcher problem" again but after update and reboot it suddenly worked. The the ASUS laptop got the same issue. I have now 2 laptops one working and one not, with the same software but apparently different settings. I saw the status being set to "Fix released" and assumed that just update+upgrade would bring in the fix. My versions are on both computers: $uname -a 4.4.0-116-generic $apt policy libgl1-mesa-dri libgl1-mesa-dri: Installed: 17.2.8-0ubuntu0~16.04.1 Candidate: 17.2.8-0ubuntu0~16.04.1 $apt policy xserver-xorg-core xserver-xorg-core: Installed: 2:1.18.4-0ubuntu0.7 Candidate: 2:1.18.4-0ubuntu0.7 The not working laptop (ASUS) was switched from the NVIDIA driver to the X.org X server just before the trouble started. There is an odd way of bypassing this bug: Go to the background image and right click and select: "Change Desktop image" You don't want to do this but select: "All Settings". Select: "User accounts". Create a new user. In my case the guest user. (standard, non admin) At least in my case I can use the newly created user WITHOUT ANY PROBLEMS. The newly created user can see and use the launcher. In this way I can at least use the computer. At least it is a temporary fix. The I started looking for differences between my normal user and the new guest user. It is possible to ctrl-alt to a different tty and log in as a different user. Some config must different and make sense but hard to compare and I do not know where to look. So far I only found that the .Xauthority file of both is different. The have the MIT-MAGIC-COOKIE setting with different settings. Removing the .Xauthority file will have the file recreated but does not help in fixing the problem. Please let me know how I can compare both users and where to look. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1735594 Title: [regression] compiz crashes after Mesa upgrade Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Xenial: Fix Released Status in mesa source package in Artful: Fix Released Bug description: [Impact] When I use the Unity session I automatically get logged out under these conditions: When I hover with my mouse over any icon of the sidebar. When I press the alt key. When I press the super key. running dmesg after this unwanted logout happens I get following information: compiz[10616]: segfault at 0 ip 00007fbca309feeb sp 00007fff5f59a4d0 error 4 in i965_dri.so[7fbca2af6000+7e4000] This is caused by a mesa upgrade, which added a patch for bug #1727401. The crasher is reproduced on: - gen4 / gen5 Intel - if using modesetting X driver, like when xserver-xorg-video-intel is not installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults to modesetting) [Test case] Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash. [Regression potential] The backported patches need to be tested, here for regressions and on 1727401 that they fix the original bug (again). Best to test on a wide array of Intel HW: gen4 (965GM/GM45/G45) gen5 (Ironlake) gen6 (Sandy Bridge) gen7 (Bay Trail, Ivy Bridge, Haswell) gen8 (Braswell, Broadwell) gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1735594/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
