indicator-weather crashed with SIGSEGV in g_main_context_dispatch()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
indicator-weather (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu oneiric (development branch)
Release: 11.10
Codename: oneiric
$ LANG=C apt-cache policy indicator-weather
indicator-weather:
Installed: 11.05.31-0ubuntu2
Candidate: 11.05.31-0ubuntu2
Version table:
*** 11.05.31-0ubuntu2 0
500 http://
100 /var/lib/
I installed the package on the default unity mode, and it worked fine.
But, it won't appear on the upper menu bar when I login by the ubuntu
classic mode and the crash happens suddenly.
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: indicator-weather 11.05.31-0ubuntu2
ProcVersionSign
Uname: Linux 3.0.0-10-generic x86_64
NonfreeKernelMo
Architecture: amd64
Date: Wed Sep 7 03:54:20 2011
ExecutablePath: /usr/bin/
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901)
InterpreterPath: /usr/bin/python2.7
PackageArchitec
ProcCmdline: /usr/bin/python /usr/bin/
ProcEnviron:
PATH=(custom, no user)
LANG=ja_JP.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f79cb91b216: mov (%rax),%rdi
PC (0x7f79cb91b216) ok
source "(%rax)" (0x544155415641
destination "%rdi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: indicator-weather
StacktraceTop:
?? () from /usr/lib/
?? () from /usr/lib/
g_main_
?? () from /lib/x86_
g_main_loop_run () from /lib/x86_
Title: indicator-weather crashed with SIGSEGV in g_main_
UpgradeStatus: No upgrade log present (probably fresh install)
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 #832361, 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.