indicator-weather crashed with SIGSEGV in g_array_free()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
indicator-weather (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
indicator-weather has never worked right on my raring desktop. It is stuck on showing 15'C despite changing locations and the fact that it should be showing frickin' -2'C. It generally crashes within a couple of hours of restarting my computer.
ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: indicator-weather 12.07.30-0ubuntu5
ProcVersionSign
Uname: Linux 3.8.0-14-generic x86_64
NonfreeKernelMo
ApportVersion: 2.9.2-0ubuntu3
Architecture: amd64
CrashCounter: 1
Date: Mon Mar 25 11:17:21 2013
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2012-06-03 (295 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
InterpreterPath: /usr/bin/python2.7
MarkForUpload: True
PackageArchitec
ProcCmdline: /usr/bin/python /usr/bin/
ProcEnviron:
PATH=(custom, user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7feb660ca8b5 <g_array_free+21>: lock cmpxchg %ecx,0x18(%rdi)
PC (0x7feb660ca8b5) ok
source "%ecx" ok
destination "0x18(%rdi)" (0x7feb58ea9b48) in non-writable VMA region: 0x7feb58e9d000-
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 raring on 2013-01-11 (72 days ago)
UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sbuild sudo vboxusers
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.