Unity doesn't start in focal

Bug #1863422 reported by Rod Smith
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
unity (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

My system has been upgraded through several Ubuntu versions, and I'm now (15 Feb 2020) on a pre-release version of Ubuntu 20.04 (Focal Fossa). I've been using Unity on this system since Ubuntu's installation years ago, and it's worked fine, including when I first installed the pre-release Ubuntu 20.04 a week or two ago. I updated packages on 13 Feb or 14 Feb, however. Now, when I log in, I get nothing but a blank screen -- no window manager or desktop environment appears to be running. I'm able to open a Terminal by right-clicking on the (black) desktop and selecting "run from Terminal" from the list of options, and I can then start icewm -- but I need to use the "--replace" option because icewm thinks a window manager IS running, even though the windows have no widgets or other ways to control them. (I've been using X since pre-Linux days, so I know what X without a window manager looks like, and to all appearances, this is it.)

$ lsb_release -rd
Description: Ubuntu Focal Fossa (development branch)
Release: 20.04

$ apt-cache show ubuntu-unity-desktop | grep Version
Version: 0.2

$ apt-cache show unity | grep Version
Version: 7.5.0+20.04.20200211-0ubuntu1
---
ProblemType: Bug
.tmp.unity_support_test.0:

ApportVersion: 2.20.11-0ubuntu16
Architecture: amd64
CompositorRunning: None
CurrentDesktop: XFCE
DistUpgraded: Fresh install
DistroCodename: focal
DistroRelease: Ubuntu 20.04
DistroVariant: ubuntu
DkmsStatus:
 fwts-efi-runtime-dkms, 20.01.00, 5.4.0-12-generic, x86_64: installed (WARNING! Diff between built and installed module!)
 fwts-efi-runtime-dkms, 20.01.00, 5.4.0-14-generic, x86_64: installed (WARNING! Diff between built and installed module!)
 virtualbox, 6.1.2, 5.4.0-14-generic, x86_64: installed
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:3978]
GsettingsChanges:
 b'org.compiz.core' b'active-plugins' b"['core', 'composite', 'opengl', 'place', 'regex', 'resize', 'session', 'snap', 'vpswitch', 'wall', 'animation', 'compiztoolbox', 'fade', 'grid', 'imgpng', 'mousepoll', 'move', 'scale', 'workarounds', 'expo', 'ezoom', 'switcher', 'unityshell']"
 b'com.canonical.Unity' b'minimize-count' b'37'
 b'com.ubuntu.user-interface' b'scale-factor' b"{'HDMI-1': 8, 'eDP1': 8, 'HDMI1': 8, 'eDP-1': 8}"
 b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
InstallationDate: Installed on 2017-10-23 (845 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: LENOVO 20289
MonitorsUser.xml:
 <monitors version="2">
 </monitors>
Package: unity 7.5.0+20.04.20200211-0ubuntu1
PackageArchitecture: amd64
ProcKernelCmdLine: \\vmlinuz-5.4.0-14-generic ro root=/dev/hostname/zesty initrd=\initrd.img-5.4.0-14-generic
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
Tags: third-party-packages focal third-party-packages third-party-packages ubuntu
Uname: Linux 5.4.0-14-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin mythtv plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 09/04/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: 7CCN32WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Plum 5A
dmi.board.vendor: LENOVO
dmi.board.version: 31900058STD
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo IdeaPad U530 Touch
dmi.modalias: dmi:bvnLENOVO:bvr7CCN32WW:bd09/04/2013:svnLENOVO:pn20289:pvrLenovoIdeaPadU530Touch:rvnLENOVO:rnPlum5A:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadU530Touch:
dmi.product.family: IDEAPAD
dmi.product.name: 20289
dmi.product.sku: LENOVO_MT_20289
dmi.product.version: Lenovo IdeaPad U530 Touch
dmi.sys.vendor: LENOVO
upstart.unity7.log: WARN 2018-03-10 16:53:55 unity <unknown>:0 compiz: Fatal IO error 4 (Interrupted system call) on X server :0.
version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
version.libdrm2: libdrm2 2.4.100-4
version.libgl1-mesa-dri: libgl1-mesa-dri 19.3.3-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.3.3-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
xserver.bootTime: Sat Feb 15 14:00:36 2020
xserver.configfile: default
xserver.errors:

xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.20.7-2ubuntu1
xserver.video_driver: modeset

Revision history for this message
lotuspsychje (lotuspsychje) wrote :

Thank you for reporting this bug and make ubuntu better!

When filing bugs to ubuntu, please use ubuntu-bug packagename
so relevant system info gets pulled into the bug.

You can still pull the needed info with: apport-collect 1863422
at this stage

As side note, ubuntu 20.04 is currently still in development
its highly reccomended to help testing bugs based on the daily iso's
instead of upgrading, this will make the work for the developers
more easy to find out the root of the problem.

Revision history for this message
Rod Smith (rodsmith) wrote : CurrentDmesg.txt

apport information

tags: added: apport-collected focal third-party-packages ubuntu
description: updated
Revision history for this message
Rod Smith (rodsmith) wrote : Dependencies.txt

apport information

Revision history for this message
Rod Smith (rodsmith) wrote : DpkgLog.txt

apport information

Revision history for this message
Rod Smith (rodsmith) wrote : LightdmDisplayLog.txt

apport information

Revision history for this message
Rod Smith (rodsmith) wrote : LightdmLog.txt

apport information

Revision history for this message
Rod Smith (rodsmith) wrote : Lspci.txt

apport information

Revision history for this message
Rod Smith (rodsmith) wrote : Lsusb.txt

apport information

Revision history for this message
Rod Smith (rodsmith) wrote : Lsusb-t.txt

apport information

Revision history for this message
Rod Smith (rodsmith) wrote : Lsusb-v.txt

apport information

Revision history for this message
Rod Smith (rodsmith) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Rod Smith (rodsmith) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Rod Smith (rodsmith) wrote : ProcEnviron.txt

apport information

Revision history for this message
Rod Smith (rodsmith) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Rod Smith (rodsmith) wrote : ProcModules.txt

apport information

Revision history for this message
Rod Smith (rodsmith) wrote : UdevDb.txt

apport information

Revision history for this message
Rod Smith (rodsmith) wrote : UnitySupportTest.txt

apport information

Revision history for this message
Rod Smith (rodsmith) wrote : XorgLog.txt

apport information

Revision history for this message
Rod Smith (rodsmith) wrote : XorgLogOld.txt

apport information

Revision history for this message
Rod Smith (rodsmith) wrote : Xrandr.txt

apport information

Revision history for this message
Rod Smith (rodsmith) wrote : upstart.unity-panel-service.log.txt

apport information

Revision history for this message
Rod Smith (rodsmith) wrote : xdpyinfo.txt

apport information

Revision history for this message
Rod Smith (rodsmith) wrote : xserver.devices.txt

apport information

Revision history for this message
Rod Smith (rodsmith) wrote : xserver.outputs.txt

apport information

Revision history for this message
Khurshid Alam (khurshid-alam) wrote :

Unity needs to be recompiled against newer unity-settings-daemon-dev. When that happens it will automatically get fixed. Meanwhile you can you can use maintainers ppa.

Also it is not a good idea to upgrade. Instead use fresh install for testing.

Revision history for this message
Balint Reczey (rbalint) wrote :

I think the recompilation did happen:

unity-settings-daemon (15.04.1+20.04.20200311-0ubuntu1) focal; urgency=medium

  [ Khurshid Alam ]
  * Port rest of the schemas gnome-settings-daemon-common to
    com.canonical.unity.settings-daemon. LP: #1842324 (LP: #1842324)

 -- Sebastien Bacher <email address hidden> Wed, 11 Mar 2020 16:32:29 +0000

unity (7.5.0+20.04.20200312-0ubuntu1) focal; urgency=medium

  [ Khurshid Alam ]
  * Bump dependency of unity-settings-daemon & unity-settings-daemon-
    schemas

 -- Sebastien Bacher <email address hidden> Thu, 12 Mar 2020 10:58:27 +0000

I can also log in to the Unity session thus I belive this bug is fixed.

Changed in unity (Ubuntu):
status: New → Fix Released
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.