Ubuntu
indicator-session package

indicator-session-service crashed with SIGABRT in raise()

Bug #839920 reported by Thierry Mallard on 2011-09-02

This bug report is a duplicate of: Bug #835885: indicator-session-service crashed with SIGABRT in raise(). Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	indicator-session (Ubuntu)	New	Undecided	Unassigned

Bug Description

It happened when launching for the first time the Software Center

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: indicator-session 0.3.4.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-9.15-generic 3.0.3
Uname: Linux 3.0.0-9-generic x86_64
Architecture: amd64
Date: Fri Sep 2 23:50:42 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/indicator-session/indicator-session-service
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcCmdline: /usr/lib/indicator-session/indicator-session-service
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, no user)
LANG=fr_FR.UTF-8
Signal: 6
SourcePackage: indicator-session
StacktraceTop:
raise () from /lib/x86_64-linux-gnu/libc.so.6
abort () from /lib/x86_64-linux-gnu/libc.so.6
g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: indicator-session-service crashed with SIGABRT in raise()
UpgradeStatus: Upgraded to oneiric on 2011-09-02 (0 days ago)
UserGroups: adm cdrom dialout dip fax floppy fuse plugdev tape video

Tags:

Revision history for this message

Thierry Mallard (thierrymallard) wrote on 2011-09-02:

XsessionErrors.txt Edit (3.5 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2011-09-02: This bug is a duplicate

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 #835885, 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.