DBus Menu

indicator-weather crashed with SIGSEGV in g_main_context_dispatch()

Bug #763284 reported by Def Sum on 2011-04-17

This bug report is a duplicate of: Bug #743541: indicator-weather crashed with SIGSEGV in dbusmenu_menuitem_build_variant(). Edit Remove

672

This bug affects 159 people

	Status	Importance	Assigned to
DBus Menu	Invalid	Undecided	Unassigned
Weather Indicator	Invalid	Undecided	Unassigned
indicator-weather (Ubuntu)	Confirmed	Undecided	Unassigned

Bug Description

Binary package hint: indicator-weather

$ lsb_release -rd
Description: Ubuntu Natty (development branch)
Release: 11.04

Weather indicator just crashes without any reason.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: indicator-weather 11.04.10+repack-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
NonfreeKernelModules: fglrx
Architecture: amd64
CrashCounter: 1
Date: Sun Apr 17 07:26:40 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=en_US:en
LANG=en_IE.UTF-8
LC_MESSAGES=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f09c9a1caee: cmp %r12d,0x8(%rax)
PC (0x7f09c9a1caee) ok
source "%r12d" ok
destination "0x8(%rax)" (0x00000039) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: indicator-weather
StacktraceTop:
?? () from /usr/lib/libdbusmenu-glib.so.3
g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
Title: indicator-weather crashed with SIGSEGV in g_main_context_dispatch()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Tags:

Revision history for this message

Def Sum (fashionised) wrote on 2011-04-17:

Dependencies.txt Edit (6.6 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (701 bytes, text/plain; charset="utf-8")
IndicatorLog.txt Edit (554.5 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (53.2 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (804 bytes, text/plain; charset="utf-8")
Registers.txt Edit (662 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (1.4 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (10.5 KiB, text/plain; charset="utf-8")

Vadim Rutkovsky (roignac) on 2011-05-11

Changed in weather-indicator:
status:	New → Invalid
Changed in indicator-weather (Ubuntu):
status:	New → Invalid

Revision history for this message

Ted Gould (ted) wrote on 2011-09-23:

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

dennygoot@gmail.com (dennygoot) wrote on 2012-04-02:

To Ted Gould, I have all the most updated packages installed here, I am even running 12.04 beta here. This bug is not only valid, but serious.

Revision history for this message

Mark Cariaga (mzc) wrote on 2012-04-03:

why is this bug invalid? it recurs at start-up

Revision history for this message

JP Vossen (jp-jpsdomain) wrote on 2012-04-03:

And as noted it is (still!) happening in the beta of 12.04 LTS! That's how I got here; mine crashed, I reported it, and all of the attachments and details disappeared when I said that my bug was the same as this one. If I see this again, how do I report it so that all the details do not disappear again? IOW, how do I append to this bug?

FWIW, when I skimmed my bug report bufor submitting, the sense I got was some kind of exception due to missing or invalid weather data at the source, which could explain why this is hard to track down. IIRC I saw this crash twice or so about a week ago, and it's been fine since.

Andrew Starr-Bochicchio (andrewsomething) on 2012-04-03

Changed in indicator-weather (Ubuntu):
status:	Invalid → New

Revision history for this message

Launchpad Janitor (janitor) wrote on 2012-04-03:

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

Changed in indicator-weather (Ubuntu):
status:	New → Confirmed

Revision history for this message

David Burrows (snadge) wrote on 2012-04-03:

I'm running precise also, with fglrx driver. Automated crash subject line matched this one.

Revision history for this message

dennygoot@gmail.com (dennygoot) wrote on 2012-04-07:

indicator-weather crashed with SIGSEGV in g_main_context_dispatch() again.

Revision history for this message

Lazy (ubuntu-bugs-oittaa) wrote on 2012-04-12:

Just happened to me. I'm also running Precise.

Revision history for this message

Joshua R. Poulson (jrp) wrote on 2012-04-13:

#10

This happened for me with Precise beta 2. I had simply left a desktop up overnight with no screen locking set.

Revision history for this message

Andy Braben (abraben) wrote on 2012-04-13: Re: [Bug 763284] Re: indicator-weather crashed with SIGSEGV in g_main_context_dispatch()

#11

It happens to me once or twice a day for no apparent reason. No problem
restarting it.

Andy.
On 13 Apr 2012 13:55, "Joshua R. Poulson" <email address hidden>
wrote:

> This happened for me with Precise beta 2. I had simply left a desktop up
> overnight with no screen locking set.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/763284
>
> Title:
> indicator-weather crashed with SIGSEGV in g_main_context_dispatch()
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/dbusmenu/+bug/763284/+subscriptions
>

Revision history for this message

Benjamin Schmid (benbuntu) wrote on 2012-04-14:

#12

Regression. Happens for me too on Precise without any user interaction on a regular basis. I refiled Bug #981391 hoping this does generate useful symbolic stack trace.

Benjamin Schmid (benbuntu) on 2012-04-14

tags:

added: precise

Revision history for this message

Mathieu Cossette (mcossette) wrote on 2012-04-17:

#13

While opening dash (with a query still active and searching) . . .

Revision history for this message

bwat47 (bwat47) wrote on 2012-07-24:

#14

Sane issue as benjamin here, randomly crashes while computer is idle.

Revision history for this message

Oscar Tiderman (oscar-tiderman) wrote on 2012-08-12:

#15

There's so many bug reports about indicator-weather crashing I can't keep track of which one I've reported to and which ones contains fixes and so on, anyway it's still crashing just by idling, hope someone will take care of it soon.

Revision history for this message

Simplehuman (simplehuman) wrote on 2012-09-01:

#16

Ubuntu 12.10 x64 it is still there

Revision history for this message

Tom Frost (tfrost) wrote on 2012-12-13:

#17

this happens every couple of days for no apparent reason...restarting indicator with no problems for a few days, then happens again.....using 12.04.1 LTS with AMD 64 X2 + Nvidia graphics