indicator-weather crashed with SIGSEGV in g_str_equal()

Bug #1044065 reported by Daniel Cvelbar
54
This bug affects 12 people
Affects Status Importance Assigned to Milestone
Weather Indicator
New
Undecided
Unassigned

Bug Description

indicator-weather is a reinstall after a purge (sudo apt-get remove --purge indicator-weather) followed by an auto remove to remove python. No proposed version avalible

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: indicator-weather 12.07.30~precise1 [origin: LP-PPA-weather-indicator-team]
ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
Uname: Linux 3.2.0-29-generic i686
ApportVersion: 2.0.1-0ubuntu12
Architecture: i386
CrashDB: indicator_weather
Date: Thu Aug 30 16:41:08 2012
ExecutablePath: /usr/bin/indicator-weather
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/indicator-weather
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x4d0678: mov (%ecx),%al
 PC (0x004d0678) ok
 source "(%ecx)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%al" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: indicator-weather
StacktraceTop:
 ?? () from /lib/i386-linux-gnu/libc.so.6
 g_str_equal () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_hash_table_lookup () from /lib/i386-linux-gnu/libglib-2.0.so.0
 dbusmenu_menuitem_property_get_variant () from /usr/lib/i386-linux-gnu/libdbusmenu-glib.so.4
 dbusmenu_menuitem_properties_variant () from /usr/lib/i386-linux-gnu/libdbusmenu-glib.so.4
ThirdParty: True
Title: indicator-weather crashed with SIGSEGV in g_str_equal()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: audio avahi avahi-autoipd cdrom dialout dip fax floppy fuse netdev plugdev sambashare scanner sudo tape users video

Revision history for this message
Daniel Cvelbar (dcvelbar) wrote :
visibility: private → public
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.