indicator-weather crashed with SIGSEGV in free()

Bug #778691 reported by Martin
74
This bug affects 17 people
Affects Status Importance Assigned to Milestone
DBus Menu
Invalid
Undecided
Unassigned
Weather Indicator
Invalid
Undecided
Unassigned
Ubuntu
Confirmed
Undecided
Unassigned

Bug Description

The indicator crash

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: indicator-weather 11.05.01~natty2
ProcVersionSignature: Ubuntu 2.6.38-9.43-generic 2.6.38.4
Uname: Linux 2.6.38-9-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
CrashCounter: 1
CrashDB: indicator_weather
Date: Fri May 6 11:47:47 2011
ExecutablePath: /usr/bin/indicator-weather
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110413)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/indicator-weather
ProcEnviron:
 LANGUAGE=es_AR:en
 LANG=es_AR.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f74735c088d <free+29>: mov -0x8(%rdi),%rsi
 PC (0x7f74735c088d) ok
 source "-0x8(%rdi)" (0x5441554156415739) not located in a known VMA region (needed readable region)!
 destination "%rsi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: indicator-weather
StacktraceTop:
 free () from /lib/x86_64-linux-gnu/libc.so.6
 g_array_free () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/libdbusmenu-glib.so.3
 ?? () from /usr/lib/libdbusmenu-glib.so.3
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
ThirdParty: True
Title: indicator-weather crashed with SIGSEGV in free()
UpgradeStatus: Upgraded to natty on 2011-04-21 (15 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Martin (mbattiti) wrote :
Changed in weather-indicator:
status: New → Invalid
Revision history for this message
Ted Gould (ted) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better.

However, processing it in order to get sufficient information for the developers failed (it does not generate an useful symbolic stack trace). This might be caused by some outdated packages which were installed on your system at the time of the report. Please upgrade your system to the latest package versions. If you still encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

Changed in dbusmenu:
status: New → Invalid
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ubuntu:
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.