Ubuntu
protobuf package

Xserver removed after upgrade (2014-02-04)

Bug #1276562 reported by Edwin Pujols on 2014-02-05

8

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	protobuf (Ubuntu)	Fix Released	Undecided	Unassigned

Bug Description

I am on trusty-proposed.

After last of upgrade of date (2014-02-04 01:47 UTC) the Xserver/Xorg/X11 package was removed automatically. I did a `dist-upgrade` (without autoremove). I noticed this when lightdm didn't start.

I then installed `ubuntu-deskop` in order to pull the Xserver (I had removed libreoffice previously). LightDM was able to start and log me into the graphical shell, but compiz failed with this message

compiz --replace
compiz (core) - Info: Loading plugin: core
compiz (core) - Info: Starting plugin: core
compiz (core) - Info: Loading plugin: ccp
compiz (core) - Error: Failed to load plugin: ccp

I'll try to restarting, for now.

I attach my apt history and dpkg log. (Notice that the times are localized to Santo Domingo, Dominican Republic, about 4 hours _less_ than UTC.)

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: ubuntu-desktop 1.315
ProcVersionSignature: Ubuntu 3.13.0-7.25-generic 3.13.1
Uname: Linux 3.13.0-7-generic i686
ApportVersion: 2.13.2-0ubuntu2
Architecture: i386
CurrentDesktop: Unity
Date: Wed Feb 5 08:19:31 2014
InstallationDate: Installed on 2014-01-14 (21 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20140113)
SourcePackage: ubuntu-meta
UpgradeStatus: No upgrade log present (probably fresh install)

Tags:

Revision history for this message

Edwin Pujols (edwinpm5) wrote on 2014-02-05:

#1

dpkg.log Edit (241.9 KiB, text/plain)
Dependencies.txt Edit (48.2 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (316 bytes, text/plain; charset="utf-8")

Revision history for this message

Edwin Pujols (edwinpm5) wrote on 2014-02-05:

#2

apt history Edit (16.6 KiB, text/plain)

Revision history for this message

Edwin Pujols (edwinpm5) wrote on 2014-02-05:

#3

apt history, where the problem started Edit (6.2 KiB, text/plain)

Revision history for this message

Edwin Pujols (edwinpm5) wrote on 2014-02-05:

#4

what I did after to get lightdm working Edit (4.3 KiB, text/plain)

Revision history for this message

Edwin Pujols (edwinpm5) wrote on 2014-02-05:

#5

After restarting:

1. plymouthd reported a crash via apport. apport told me that the bug has already been reported, never happened to me before. (Anyways, I don't have permissions to see the bug reported.)

2. LigthDM failed to start on its own, had to `sudo restart lightdm`. I attach its log file.

I'll restart with the previous kernel...

Revision history for this message

Edwin Pujols (edwinpm5) wrote on 2014-02-05:

#6

lightdm.log after restart (and `sudo restart lightdm`) Edit (4.4 KiB, text/plain)

Revision history for this message

Edwin Pujols (edwinpm5) wrote on 2014-02-05:

#7

Greeter, after restart Edit (6.2 KiB, text/plain)

Revision history for this message

Edwin Pujols (edwinpm5) wrote on 2014-02-05:

#8

BTW, the bug I am not authorized to see is #1216022, but not sure if that page even exists (the title says "Page not found").

Revision history for this message

Iain Lane (laney) wrote on 2014-02-05:

#9

I think you're confused - there was a bug in 'protobuf' this morning which made compiz fail to start, and an unrelated xorg upload at the same time. I don't see a removal in your logs , just an upgrade.

If you dist-upgrade now then compiz ought to be fixed.

Also, I recommend that you don't use trusty-proposed as it is for machine use only.

affects:	ubuntu-meta (Ubuntu) → protobuf (Ubuntu)
Changed in protobuf (Ubuntu):
status:	New → Fix Released

Revision history for this message

Edwin Pujols (edwinpm5) wrote on 2014-02-05:

#10

Yes, on reading further I noticed that Xorg was simply being upgraded. Thanks.

Revision history for this message

drs305 (drs305) wrote on 2014-02-05:

#11

I had the same experience today after updating the system. I suspected it was Xorg or compiz but didn't have the time to troubleshoot other than restore an old image and repeat the upgrade to the same failure a few hours ago.

Will the revised problem package still have the 0ubuntu4 designation? Most of what I suspected might be the cause were designated as such and I thought I'd just wait until the next updates.

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

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