unity does not start when booting with 4.11.3 kernel

Bug #1694167 reported by Christoph Grimmer-Dietrich
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

I installed the recent 4.11.3 kernel from the packages downloaded from kernel.ubuntu.org

After rebooting unity did not start properly. I had no dash, no decorations and no dock. After starting unity manually from the command line I got window decorations for a program that is run after login but nothing else.

After switching back to 4.11.2 the system is working fine again.

> lsb_release -rd
Description: Ubuntu 17.04
Release: 17.04

If you need further information please let me know!
---
ApportVersion: 2.20.4-0ubuntu4.4
Architecture: amd64
CurrentDesktop: Unity:Unity7
DistroRelease: Ubuntu 17.04
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-08-01 (347 days ago)
InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
Package: linux (not installed)
Tags: zesty
Uname: Linux 4.11.8-041108-generic x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: Upgraded to zesty on 2017-04-26 (79 days ago)
UserGroups: adm cdrom dip docker kvm lpadmin plugdev sambashare sudo
_MarkForUpload: True

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/1694167/+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
Paul White (paulw2u)
affects: ubuntu → linux (Ubuntu)
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1694167

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
tags: added: zesty
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

4.11.3 sounds like an upstream kernel. Does this bug also happen with the stock Ubuntu kernel?

tags: added: kernel-da-key
Changed in linux (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Christoph Grimmer-Dietrich (christoph-grimmer) wrote : JournalErrors.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
Christoph Grimmer-Dietrich (christoph-grimmer) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Christoph Grimmer-Dietrich (christoph-grimmer) wrote : ProcEnviron.txt

apport information

Revision history for this message
Christoph Grimmer-Dietrich (christoph-grimmer) wrote : Re: [Bug 1694167] Re: unity does not start when booting with 4.11.3 kernel

Hallo Joseph,

The bug did only occur when using 4.11.3 from kernel.ubuntu.com. 4.11.2 was
running fine as well as my currently used 4.11.8. I switched to the
upstream kernel due to severe problems with my bluetooth headset as well as
the lacking DP support.

2017-07-14 15:32 GMT+02:00 Joseph Salisbury <email address hidden>
:

> 4.11.3 sounds like an upstream kernel. Does this bug also happen with
> the stock Ubuntu kernel?
>
> ** Tags added: kernel-da-key
>
> ** Changed in: linux (Ubuntu)
> Importance: Undecided => Medium
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1694167
>
> Title:
> unity does not start when booting with 4.11.3 kernel
>
> Status in linux package in Ubuntu:
> Incomplete
>
> Bug description:
> I installed the recent 4.11.3 kernel from the packages downloaded from
> kernel.ubuntu.org
>
> After rebooting unity did not start properly. I had no dash, no
> decorations and no dock. After starting unity manually from the
> command line I got window decorations for a program that is run after
> login but nothing else.
>
> After switching back to 4.11.2 the system is working fine again.
>
> > lsb_release -rd
> Description: Ubuntu 17.04
> Release: 17.04
>
>
> If you need further information please let me know!
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
> 1694167/+subscriptions
>

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Can you see if this bug also occurs with the latest mainline kernel:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13-rc1/

Revision history for this message
Christoph Grimmer-Dietrich (christoph-grimmer) wrote :

I recently tried going up to 4.12. Unity did start but the firmware for the Intel wireless device did not load. So I'm running a recent 4.11 right now. Since I use the laptop for work I'm reluctant to install a RC. The 4.12 did mess up enough ☺️

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
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.