indicator-application-service crashed with SIGSEGV in g_closure_invoke()

[Scott Kamp]

Binary package hint: indicator-application

 lsb_release -rd
Description: Ubuntu maverick (development branch)
Release: 10.10

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: indicator-application 0.2.2-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-8.13-generic 2.6.35-rc5
Uname: Linux 2.6.35-8-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Thu Jul 15 09:30:13 2010
ExecutablePath: /usr/lib/indicator-application/indicator-application-service
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100602.2)
ProcCmdline: /usr/lib/indicator-application/indicator-application-service
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.utf8
SegvAnalysis:
 Segfault happened at: 0x403add: cmpb $0x0,0x0(%r13)
 PC (0x00403add) ok
 source "$0x0" ok
 destination "0x0(%r13)" (0x00000021) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: indicator-application
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/libdbus-glib-1.so.2
 g_closure_invoke ()
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_signal_emit_valist ()
Title: indicator-application-service crashed with SIGSEGV in g_closure_invoke()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:
 apply_status (app=0x1287240,
 ?? () from /usr/lib/libdbus-glib-1.so.2
 g_closure_invoke (closure=0x128a630,
 signal_emit_unlocked_R (node=0x127fa90,
 g_signal_emit_valist (instance=0x1279ac0,

[David Barth (dbarth)]

Karl, can you investigate this one? Have you seen such issues while working on indicators recently?

[Karl Lattimer (karl-qdh)]

Personally I haven't seen anything of the kind.

Do you want me to prioritise this above my other bugs?

[Karl Lattimer (karl-qdh)]

@OutBackDingo could you tell me what indicators you have running when this bug manifests itself?

[Scott Kamp (scottkamp)]

that would have been wireless battery bluetooth im sound, though since
encountering this issue ive stopped running gnome
kde appears to be fine.... i can reload gnome tonight see if the issues
still exists, since ive gotten some updates since this bug post

On Tue, Aug 31, 2010 at 7:38 AM, Karl Lattimer <email address hidden> wrote:

> @OutBackDingo could you tell me what indicators you have running when
> this bug manifests itself?
>
> --
> indicator-application-service crashed with SIGSEGV in g_closure_invoke()
> https://bugs.launchpad.net/bugs/606052
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Karl Lattimer (karl-qdh)]

Please do, I hope it's gone and assume it is as there would probably be a lot more reports.