indicator-applet crashed with SIGSEGV in cairo_rectangle()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
indicator-application (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: indicator-
1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu.
Description: Ubuntu maverick (development branch)
Release: 10.10
2) The version of the package you are using, via 'apt-cache policy packagename' or by checking in Synaptic.
indicator-
Installed: 0.2.3-0ubuntu1
Candidate: 0.2.3-0ubuntu1
Version table:
*** 0.2.3-0ubuntu1 0
500 http://
100 /var/lib/
3) What you expected to happen
Not crash.
4) What happened instead
While listening to Last.fm Personal Radio via Rhythmbox 0.13.0 with cross-fading enabled (so songs are properly scrobbled) the idicator-applet crashes and prompts me to reload or cancel.
ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: indicator-
ProcVersionSign
Uname: Linux 2.6.35-12-generic x86_64
NonfreeKernelMo
Architecture: amd64
Date: Fri Jul 30 07:49:19 2010
ExecutablePath: /usr/lib/
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100602.2)
ProcCmdline: /usr/lib/
ProcEnviron:
LANG=en_US.utf8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f109f940e98 <cairo_
PC (0x7f109f940e98) ok
source "0x4(%rdi)" (0x00000004) not located in a known VMA region (needed readable region)!
destination "%ecx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: indicator-
StacktraceTop:
cairo_rectangle () from /usr/lib/
play_button_
g_closure_invoke ()
?? () from /usr/lib/
g_signal_
Title: indicator-applet crashed with SIGSEGV in cairo_rectangle()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
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 #612357, 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.