After removing and restarting: low graphics mode and blank screen

Bug #1281192 reported by Edwin Pujols on 2014-02-17
This bug affects 2 people
Affects Status Importance Assigned to Milestone
One Hundred Papercuts
Unity System Compositor
unity-system-compositor (Ubuntu)

Bug Description

When I remove u-s-c and ubuntu-desktop-mir with `remove --auto-remove`, I get greeted with the "Low graphics" dialog and lightdm won't start. I can get back to the desktop if I reinstall both packages (and run `sudo restart lightdm`).

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: ubuntu-desktop-mir 0.0.2+14.04.20140212.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
Uname: Linux 3.13.0-8-generic i686
ApportVersion: 2.13.2-0ubuntu4
Architecture: i386
CurrentDesktop: Unity
Date: Mon Feb 17 13:07:13 2014
 Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Device [103c:30a2]
   Subsystem: Hewlett-Packard Company Device [103c:30a2]
InstallationDate: Installed on 2014-01-14 (34 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20140113)
PackageArchitecture: all
SourcePackage: unity-system-compositor
 ERROR: /build/buildd/mir-0.1.5+14.04.20140212/src/platform/graphics/mesa/linux_virtual_terminal.cpp(125): Throw in function virtual void mir::graphics::mesa::LinuxVirtualTerminal::set_graphics_mode()
 Dynamic exception type: boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<std::runtime_error> >
 std::exception::what: Failed to set VT to graphics mode
 5, "Input/output error"
UpgradeStatus: No upgrade log present (probably fresh install)
version.libdrm: libdrm2 2.4.52-1
version.lightdm: lightdm 1.9.7-0ubuntu2
version.mesa: libegl1-mesa-dev N/A

Edwin Pujols (edwinpm5) wrote :
description: updated
Edwin Pujols (edwinpm5) wrote :

Just in case the last dist-upgrade is related (and this bug is Invalid), I've just upgraded to libunity-core-6.0-9.

Daniel van Vugt (vanvugt) wrote :

I experienced the same yesterday. It's a combination of:
  1. Stale ~/.Xauthority file
  2. Removing ubuntu-desktop-mir doesn't seem to remove the config and it keeps using USC.

  1. rm ~/.Xauthority
  2. sudo apt-get remove unity-system-compositor

The first issue is an old X bug. The second I think is a packaging bug of ubuntu-desktop-mir.

Edwin Pujols (edwinpm5) wrote :

Thanks, that did it.

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in unity-system-compositor (Ubuntu):
status: New → Confirmed

It renders essential functionality of the package (or a dependent one) broken.

Changed in unity-system-compositor (Ubuntu):
importance: Undecided → High
Changed in unity-system-compositor:
status: New → Confirmed
Changed in hundredpapercuts:
status: New → Triaged
Changed in unity-system-compositor (Ubuntu):
status: Confirmed → Triaged
Changed in hundredpapercuts:
importance: Undecided → High
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers