compiz crashed with SIGABRT in __kernel_vsyscall()

Bug #745627 reported by Conor Curran on 2011-03-30
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nux (Ubuntu)
Undecided
Unassigned

Bug Description

Did a fresh beta install (daily build from yesterday which apparently is the rc) and everything was fine until I tried to open any application at which point compiz kept crashing.
I was using a dual monitor setup.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: libnux-0.9-0 0.9.36-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38
Uname: Linux 2.6.38-7-generic i686
Architecture: i386
CrashCounter: 1
Date: Wed Mar 30 12:37:29 2011
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
ProcCmdline: compiz
ProcEnviron:
 LANGUAGE=en_GB:en
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: nux
StacktraceTop:
 __kernel_vsyscall ()
 raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
 abort () at abort.c:92
 g_assertion_message (domain=0x6896e6 "GLib", file=0x6d17f0 "/build/buildd/glib2.0-2.28.4/./glib/gvarianttypeinfo.c", line=186, func=0x6d1a70 "g_variant_type_info_check", message=<value optimised out>) at /build/buildd/glib2.0-2.28.4/./glib/gtestutils.c:1358
 g_assertion_message_expr (domain=0x6896e6 "GLib", file=0x6d17f0 "/build/buildd/glib2.0-2.28.4/./glib/gvarianttypeinfo.c", line=186, func=0x6d1a70 "g_variant_type_info_check", expr=0x6d17b9 "0 <= index && index < 24") at /build/buildd/glib2.0-2.28.4/./glib/gtestutils.c:1369
Title: compiz crashed with SIGABRT in __kernel_vsyscall()
UpgradeStatus: Upgraded to natty on 2011-01-04 (84 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Conor Curran (cjcurran) wrote :

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #743598, so 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. Please continue to report any other bugs you may find.

visibility: private → public
tags: removed: need-i386-retrace
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers