compiz crashed when i removed program icon from launch bar
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nux (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
ubuntu 11.04
0.9.38-0ubuntu1 (nux-tools)
thought it would remove the icon fron the launch bar but instead froze took a couple of seconds then got rid of it and gave me a bug message
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
NonfreeKernelMo
Architecture: amd64
Date: Tue Apr 5 00:54:37 2011
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcCmdline: compiz
ProcEnviron:
LANGUAGE=en_CA:en
LANG=en_CA.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f20c14030f3 <g_atomic_
PC (0x7f20c14030f3) ok
source "(%rdi)" (0x00000020) not located in a known VMA region (needed readable region)!
destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nux
StacktraceTop:
g_atomic_int_get () from /lib/x86_
g_bit_lock () from /lib/x86_
g_variant_ref_sink () from /lib/x86_
g_variant_new_strv () from /lib/x86_
g_settings_
Title: compiz crashed with SIGSEGV in g_atomic_int_get()
UpgradeStatus: Upgraded to natty on 2011-04-04 (0 days ago)
UserGroups: adm admin audio avahi avahi-autoipd backup bin cdrom couchdb crontab daemon dialout dip disk fax floppy fuse games gdm gnats haldaemon irc kmem libuuid list lp lpadmin mail man mediatomb messagebus mlocate netdev news nopasswdlogin operator plugdev proxy pulse pulse-access root rtkit sambashare saned sasl shadow src ssh ssl-cert staff sudo sys syslog tape tty users utempter utmp uucp video voice www-data
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 #748841, 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.