compiz crashed with SIGSEGV in g_utf8_validate()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Unity |
Fix Committed
|
Critical
|
Jason Smith | ||
unity (Ubuntu) |
Fix Committed
|
Critical
|
Jason Smith |
Bug Description
Occurred when attempting to remove an application from the Unity side bar. The application was successfully removed when compiz restarted.
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: libnux-0.9-0 0.9.38-0ubuntu1
ProcVersionSign
Uname: Linux 2.6.38-7-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Sat Apr 2 00:34:38 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/compiz
ProcCmdline: compiz
ProcEnviron:
LANGUAGE=en_US:en
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f74570fb150 <g_utf8_
PC (0x7f74570fb150) ok
source "$0x0" ok
destination "(%rdi)" (0x0000006b) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: nux
StacktraceTop:
g_utf8_validate () from /lib/x86_
g_variant_
g_variant_new_strv () from /lib/x86_
g_settings_
FavoriteStoreG
Title: compiz crashed with SIGSEGV in g_utf8_validate()
UpgradeStatus: Upgraded to natty on 2010-06-03 (302 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
affects: | nux (Ubuntu) → unity (Ubuntu) |
Changed in unity (Ubuntu): | |
assignee: | nobody → Jason Smith (jassmith) |
importance: | Undecided → Critical |
status: | New → Fix Committed |
Changed in unity: | |
assignee: | nobody → Jason Smith (jassmith) |
importance: | Undecided → Critical |
milestone: | none → 3.8.4 |
status: | New → Fix Committed |
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 #736792, 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.