compiz crashed with SIGSEGV in getCompPluginVTable20090315_unityshell()

Bug #1209442 reported by NoBugs! on 2013-08-08
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Unity
Triaged
High
Unassigned
compiz (Ubuntu)
Undecided
Unassigned
unity (Ubuntu)
Undecided
Unassigned

Bug Description

The unity panel is completely gone for me since the updates a few days ago.
I can't even report the bug from apport, so I'm attaching the .crash file here.

This is very disappointing, this is the first time an update that wasn't a distribution-update completely messed up my system. I can log in with fluxbox or another setup, but for most users unity "is" Ubuntu, so this is a very serious problem!

NoBugs! (luke32j) wrote :
Stephen M. Webb (bregma) wrote :

This looks like an ABI break between compiz and unityshell, except neither of those packages were updated in 13.04 recently (according to the attached crash log) and they're the same versions I have on my completely functional 13.04 system.

summary: - Unity no longer works, no panels after update.
+ compiz crashed with SIGSEGV in getCompPluginVTable20090315_unityshell()
Changed in unity:
importance: Undecided → High
status: New → Triaged
NoBugs! (luke32j) wrote :

I'm completely up-to-date on 13.04, and maybe my ancient graphics card is not supported anymore? lshw show it is Intel's " Mobile GM965/GL960 Integrated Graphics Controller". I was also affected by the fonts jittery bug, before Unity broke - maybe the fix for this broke in a worse way?

Just curious, would buying an Ubuntu certified pc model ensure that these types of random errors wouldn't happen?

NoBugs! (luke32j) wrote :

I tried reinstall, and it behaves the same, unfortunately.

dei (cephos) wrote :

Have the same problem with nvidia closed-source driver. Perhaps it comes from the new phased updgrade. One package gets phase-upgraded and one the first is dependent on not. Until now these missing dependencies weren't a problem, but now get more weight when independent packages can be updated without all other changes that were commited in the same time.

NoBugs! (luke32j) wrote :

Yeah, I was wondering about that, since I read phased updates were started around the same time this happened for me.

It seems ironic that I had been updating to Ubuntu-beta releases for awhile now, having less problems than this update in a "stable" release.

I'm guessing whatever method they use to downgrade a bad update, is not working - I have updated this system again and Unity is still broken. Gnome is having some graphical glitches too.

dei (cephos) wrote :

Sadly another two upgrades the next day didn't help either. :-( Anyone can give me hint how to debug that (I'm a Java-Dev, so shouldn't be hard if someone can give me a hint where to start)?

Sadly interface-problems happen more and more often since canonical has started implementing Mir on my computers too. Please let the old unity be the old and save the fancy new features for unity 8 on mir. Better forget about backports than possibly destabilize a stable-release that works for most people.

As far as I understood, a bad update will not be downgraded with phased updates but upgrades for further users will be blocked. Ubuntu's apt doesn't have any rollback-mechanics built-in as far as I know (would need btrfs to support snapshots and rollback before each update).

NoBugs! (luke32j) wrote :

It's been 2 weeks since I noticed, this problem, and hasn't been fixed - I wonder if there is any tool that lists which packages were bad updates, so I can manually set those back a version in Synaptic? Assuming that this was caused by a bad phased-update, that is.

Brian Murray (brian-murray) wrote :

Please add your /var/log/apt/term.log file and /var/log/apt/history.log file to this bug report so that we can examine which packages were installed when on your system.

Brian Murray (brian-murray) wrote :

Oh, it looks like you have some third party libunity packages installed which is likely the source of the problem.

 libunity-common 6.91.12ubuntu1daily13.05.01ubuntu.unity.experimental.certified-0ubuntu1 [origin: unknown]
 libunity-core-6.0-5 7.0.0daily13.06.19~13.04-0ubuntu1
 libunity-misc4 4.0.5daily13.02.26-0ubuntu1
 libunity-protocol-private0 6.91.12ubuntu1daily13.05.01ubuntu.unity.experimental.certified-0ubuntu1 [origin: unknown]
 libunity-webapps0 2.5.0~daily13.03.18-0ubuntu1
 libunity9 6.91.12ubuntu1daily13.05.01ubuntu.unity.experimental.certified-0ubuntu1 [origin: unknown]

Bug 1162093 is another example of this.

Brian Murray (brian-murray) wrote :

Its interesting to note that there are quite a few incidents of this on errors.

https://errors.ubuntu.com/problem/6fd787e3e07d9efbaeaa239c3e3b018b7959fea5

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Bug attachments