indicator-weather crashed with SIGSEGV in g_array_free()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
indicator-weather (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Using Pidgin, and decided switch the “show system tray icon” to “always” to see if an icon appears. (Currently, there's no icon alongside the Gwibber and the Thunderbird email icons in 12.10 Beta 2.)
What happened was no icon appeared for Pidgin, but the weather indicator apparently crashed and its icon disappeared.
ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: indicator-weather 12.07.30-0ubuntu1
ProcVersionSign
Uname: Linux 3.5.0-17-generic x86_64
ApportVersion: 2.6.1-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Tue Oct 9 23:04:39 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
InterpreterPath: /usr/bin/python2.7
PackageArchitec
ProcCmdline: /usr/bin/python /usr/bin/
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f7080b31465 <g_array_free+21>: lock cmpxchg %ecx,0x18(%rdi)
PC (0x7f7080b31465) ok
source "%ecx" ok
destination "0x18(%rdi)" (0x7f70752cfa68) in non-writable VMA region: 0x7f70752c3000-
SegvReason: writing VMA /usr/lib/
Signal: 11
SourcePackage: indicator-weather
StacktraceTop:
g_array_free () from /lib/x86_
?? () from /usr/lib/
?? () from /usr/lib/
g_main_
?? () from /lib/x86_
Title: indicator-weather crashed with SIGSEGV in g_array_free()
UpgradeStatus: Upgraded to quantal on 2012-09-30 (9 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1063643, 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.