compiz crashed with SIGSEGV

Bug #980672 reported by kc1di-qrp@roadrunner.com
62
This bug affects 12 people
Affects Status Importance Assigned to Milestone
unity (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

not pannel or top bar present, 3d problem I think it crashes immediately upon log in.
2d works ok.
hope this one fixed quickly.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: unity 5.8.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
Uname: Linux 3.2.0-23-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu2
Architecture: amd64
Date: Fri Apr 13 06:11:19 2012
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328)
ProcCmdline: compiz --replace
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fefabb6c7f4: mov (%rsi),%rcx
 PC (0x7fefabb6c7f4) ok
 source "(%rsi)" (0x7fef80dcfc00) not located in a known VMA region (needed readable region)!
 destination "%rcx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /usr/lib/nvidia-current/libnvidia-glcore.so.295.40
 ?? () from /usr/lib/nvidia-current/libnvidia-glcore.so.295.40
 ?? () from /usr/lib/nvidia-current/libnvidia-glcore.so.295.40
Title: compiz crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
kc1di-qrp@roadrunner.com (kc1di-qrp) wrote :
Revision history for this message
kc1di-qrp@roadrunner.com (kc1di-qrp) wrote :

This happened after update today (04-13)

Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 _wordcopy_fwd_aligned (dstp=46664240, srcp=140666635877376, len=369) at wordcopy.c:85
 ?? ()
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in unity (Ubuntu):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

libnux-2.0-common version 2.8.0-0ubuntu2 required, but 2.10.0-0ubuntu1 is available
unity-common version 5.8.0-0ubuntu2 required, but 5.10.0-0ubuntu2 is available
nux-tools version 2.8.0-0ubuntu2 required, but 2.10.0-0ubuntu1 is available
outdated debug symbol package for nux-tools: package version 2.10.0-0ubuntu1 dbgsym version 2.8.0-0ubuntu2
unity-services version 5.8.0-0ubuntu2 required, but 5.10.0-0ubuntu2 is available
outdated debug symbol package for unity-services: package version 5.10.0-0ubuntu2 dbgsym version 5.8.0-0ubuntu2
libunity-core-5.0-5 version 5.8.0-0ubuntu2 required, but 5.10.0-0ubuntu2 is available
outdated debug symbol package for libunity-core-5.0-5: package version 5.10.0-0ubuntu2 dbgsym version 5.8.0-0ubuntu2
unity version 5.8.0-0ubuntu2 required, but 5.10.0-0ubuntu2 is available
outdated debug symbol package for unity: package version 5.10.0-0ubuntu2 dbgsym version 5.8.0-0ubuntu2
libnux-2.0-0 version 2.8.0-0ubuntu2 required, but 2.10.0-0ubuntu1 is available
outdated debug symbol package for libnux-2.0-0: package version 2.10.0-0ubuntu1 dbgsym version 2.8.0-0ubuntu2
outdated debug symbol package for libgconf2-4: package version 3.2.5-0ubuntu2 dbgsym version 3.2.3-0ubuntu0.1

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

tags: removed: need-amd64-retrace
Revision history for this message
kc1di-qrp@roadrunner.com (kc1di-qrp) wrote :

system was fully updated this morning (4-13)

Changed in unity (Ubuntu):
status: Invalid → Confirmed
visibility: private → public
dino99 (9d9)
Changed in unity (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Uxío Fernández (uxiofp) wrote :

Same problem:

https://bugs.launchpad.net/ubuntu/+source/unity/+bug/980879

I uninstall nvidia-current-updates and compiz works now.

Revision history for this message
Uxío Fernández (uxiofp) wrote :

Start-Date: 2012-04-13 17:07:16
Commandline: apt-get purge nvidia-current-updates
Purge: nvidia-current-updates:amd64 (295.40-0ubuntu1)
End-Date: 2012-04-13 17:08:12

Revision history for this message
Uxío Fernández (uxiofp) wrote :
Download full text (5.5 KiB)

This update cuased the problem:

Start-Date: 2012-04-13 16:33:06
Commandline: aptdaemon role='role-commit-packages' sender=':1.59'
Upgrade: libsmbclient:amd64 (3.6.3-2ubuntu1, 3.6.3-2ubuntu2), apt-transport-https:amd64 (0.8.16~exp12ubuntu7, 0.8.16~exp12ubuntu8), ubuntu-desktop:amd64 (1.265, 1.266), libical0:amd64 (0.48-1ubuntu2, 0.48-1ubuntu3), gir1.2-dbusmenu-gtk-0.4:amd64 (0.6.1-0ubuntu1, 0.6.1-0ubuntu2), ubuntu-standard:amd64 (1.265, 1.266), libc-bin:amd64 (2.15-0ubuntu6, 2.15-0ubuntu7), gir1.2-gstreamer-0.10:amd64 (0.10.36-1, 0.10.36-1ubuntu1), metacity:amd64 (2.34.1-1ubuntu10, 2.34.1-1ubuntu11), libunity9:amd64 (5.8.0-0ubuntu1, 5.10.0-0ubuntu1), compiz-plugins-default:amd64 (0.9.7.4-0ubuntu3, 0.9.7.6-0ubuntu1), bind9-host:amd64 (9.8.1.dfsg.P1-2, 9.8.1.dfsg.P1-3), gvfs-fuse:amd64 (1.12.0-0ubuntu5, 1.12.0-0ubuntu6), libgnome-desktop-3-2:amd64 (3.4.0-0ubuntu3, 3.4.0-0ubuntu4), gnome-session-bin:amd64 (3.2.1-0ubuntu6, 3.2.1-0ubuntu7), python-minimal:amd64 (2.7.2-9ubuntu6, 2.7.3-0ubuntu1), gwibber-service-identica:amd64 (3.4.0-0ubuntu3, 3.4.0-0ubuntu4), smbclient:amd64 (3.6.3-2ubuntu1, 3.6.3-2ubuntu2), liblaunchpad-integration-common:amd64 (0.1.54build1, 0.1.56), libgck-1-0:amd64 (3.2.2-2ubuntu3, 3.2.2-2ubuntu4), dnsutils:amd64 (9.8.1.dfsg.P1-2, 9.8.1.dfsg.P1-3), gvfs-backends:amd64 (1.12.0-0ubuntu5, 1.12.0-0ubuntu6), liblaunchpad-integration-3.0-1:amd64 (0.1.54build1, 0.1.56), udisks:amd64 (1.0.4-5ubuntu1, 1.0.4-5ubuntu2), gnome-settings-daemon:amd64 (3.4.0-0ubuntu6, 3.4.0-0ubuntu7), gir1.2-dbusmenu-glib-0.4:amd64 (0.6.1-0ubuntu1, 0.6.1-0ubuntu2), unity-scope-musicstores:amd64 (5.8.0-0ubuntu1, 5.10.0-0ubuntu1), libnm-util2:amd64 (0.9.4.0-0ubuntu2, 0.9.4.0-0ubuntu3), libdee-1.0-4:amd64 (1.0.8-0ubuntu2, 1.0.10-0ubuntu1), gnome-session:amd64 (3.2.1-0ubuntu6, 3.2.1-0ubuntu7), gnome-session-common:amd64 (3.2.1-0ubuntu6, 3.2.1-0ubuntu7), libutouch-geis1:amd64 (2.2.8-0ubuntu1, 2.2.9-0ubuntu1), gvfs-libs:amd64 (1.12.0-0ubuntu5, 1.12.0-0ubuntu6), libgcr-3-1:amd64 (3.2.2-2ubuntu3, 3.2.2-2ubuntu4), libdns81:amd64 (9.8.1.dfsg.P1-2, 9.8.1.dfsg.P1-3), gwibber-service-twitter:amd64 (3.4.0-0ubuntu3, 3.4.0-0ubuntu4), gwibber-service-facebook:amd64 (3.4.0-0ubuntu3, 3.4.0-0ubuntu4), libwbclient0:amd64 (3.6.3-2ubuntu1, 3.6.3-2ubuntu2), xdg-user-dirs:amd64 (0.14-0ubuntu1, 0.14-0ubuntu2), checkbox:amd64 (0.13.6, 0.13.7), gvfs-bin:amd64 (1.12.0-0ubuntu5, 1.12.0-0ubuntu6), gnome-keyring:amd64 (3.2.2-2ubuntu3, 3.2.2-2ubuntu4), gvfs-common:amd64 (1.12.0-0ubuntu5, 1.12.0-0ubuntu6), libapt-inst1.4:amd64 (0.8.16~exp12ubuntu7, 0.8.16~exp12ubuntu8), ubuntu-minimal:amd64 (1.265, 1.266), nvidia-current-updates:amd64 (295.33-0ubuntu1, 295.40-0ubuntu1), shared-mime-info:amd64 (1.0-0ubuntu3, 1.0-0ubuntu4), gnome-desktop3-data:amd64 (3.4.0-0ubuntu3, 3.4.0-0ubuntu4), unity-lens-music:amd64 (5.8.0-0ubuntu1, 5.10.0-0ubuntu1), metacity-common:amd64 (2.34.1-1ubuntu10, 2.34.1-1ubuntu11), libisccc80:amd64 (9.8.1.dfsg.P1-2, 9.8.1.dfsg.P1-3), apt-utils:amd64 (0.8.16~exp12ubuntu7, 0.8.16~exp12ubuntu8), update-manager:amd64 (0.156.10, 0.156.11), update-manager-core:amd64 (0.156.10, 0.156.11), linux-firmware:amd64 (1.78, 1.79), samba-common:amd64 (3.6.3-2ubuntu1, 3.6.3-2ubuntu2), apt:amd6...

Read more...

Revision history for this message
Uxío Fernández (uxiofp) wrote :

The same happens with nvidia-current , compiz crash.

Now i run Ubuntu-2D and unity works ok.

Revision history for this message
roothorick (8-roothorick-gmail-com) wrote :

Having the same problem on my HP tx2000.

It's not Compiz. There's something seriously screwed with the nvidia driver itself. glxgears gives a measly 5fps, and anything else 3D that I've tried won't run at all -- it'll hang, if it doesn't simply crash outright.

I'm rolling back to nvidia-current 295.33 for regression testing right now.

glxinfo doesn't report anything out of the ordinary. Direct rendering still says "yes" and the renderer string is the same as it always was.

Revision history for this message
roothorick (8-roothorick-gmail-com) wrote :

Yep, it's a regression! Rolled nvidia-current back to 295.33 and I have full 3D unity back and can play Minecraft again.

Revision history for this message
Paul (p37307) wrote :

I had the same issue and disabled nvidia all together for the time being. I went ahead and marked my bug a duplicate of yours. Mine is located at https://bugs.launchpad.net/compiz-core/+bug/980521.

Revision history for this message
kc1di-qrp@roadrunner.com (kc1di-qrp) wrote :

I Can Confirm that disabling Nvidia Current driver restores Compiz to action. So it's something to do with compiz and Nvidia Drivers.

Revision history for this message
Andrew Heil (heilandrew) wrote :

I can confirm that the last dist-upgrade made compiz not work in a "GNOME Classic" session.

The desktop takes a long time to load, and one mouse click on the desktop makes the panels disappear (even though the process is still running) and makes the window decorations disappear.

Purging the "nvidia-current" and "nvidia-current-updates" packages (which puts me back to using nouveau) fixes the problem.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 980298, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

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.