gtk-logout-helper crashed with signal 5 in __libc_start_main()

Bug #852343 reported by Chris Johnston
This bug affects 273 people
Affects Status Importance Assigned to Milestone
indicator-session (Ubuntu)
Fix Released
Low
Unassigned
Oneiric
Won't Fix
Low
Unassigned

Bug Description

Got this after login

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: indicator-session 0.3.5.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
Uname: Linux 3.0.0-10-generic x86_64
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
Date: Sat Sep 17 00:08:25 2011
ExecutablePath: /usr/lib/indicator-session/gtk-logout-helper
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110715)
ProcCmdline: /usr/lib/indicator-session/gtk-logout-helper --shutdown
ProcEnviron:
 SHELL=/bin/false
 PATH=(custom, no user)
 LANG=en_US.UTF-8
Signal: 5
SourcePackage: indicator-session
StacktraceTop:
 ?? ()
 ?? ()
 __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6
 ?? ()
 ?? ()
Title: gtk-logout-helper crashed with signal 5 in __libc_start_main()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
Chris Johnston (cjohnston) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 consolekit_fallback (action=LOGOUT_DIALOG_TYPE_RESTART) at /build/buildd/indicator-session-0.3.5.1/./src/gtk-logout-helper.c:75
 session_action (action=LOGOUT_DIALOG_TYPE_RESTART) at /build/buildd/indicator-session-0.3.5.1/./src/gtk-logout-helper.c:104
 main (argc=1, argv=0x7fff8a0a0d38) at /build/buildd/indicator-session-0.3.5.1/./src/gtk-logout-helper.c:235

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in indicator-session (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in indicator-session (Ubuntu):
status: New → Confirmed
tags: added: bugpattern-needed
visibility: private → public
Revision history for this message
msutkowski (michal-sutkowski) wrote :

I was playing with bluetooth connection and suddenly it happened.

Revision history for this message
quickstar (iceempror) wrote :

During an apt-get upgrade, suddenly happened

Revision history for this message
crtm (carlosrtm) wrote :

Crash after login

Revision history for this message
Andrea Caminiti (nrayever) wrote :

Crashed after login!

Revision history for this message
andy62mcc (andy62mcc) wrote :

Crashed after login

Revision history for this message
John Read (john-j4u) wrote :

crash after login

Revision history for this message
didi (lembke) wrote :

crash after login

Revision history for this message
xe2xpk (skorlowsky) wrote :

same as above (crash after login)

Revision history for this message
Camille Appert (bibinou) wrote :

Thank you for taking the time to make Ubuntu better.
Please use the "Do this affect you to ?" button below the bug title and only post a comment if you have significant information to add that has not already been posted.

Revision history for this message
Justin (justin-wzy) wrote :

Crashed after login

Revision history for this message
Joshua (x-memoriter) wrote :

Crashed after login, too.

Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

bumping importance due to the number of duplicates.

Changed in indicator-session (Ubuntu Oneiric):
importance: Medium → High
milestone: none → ubuntu-11.10
assignee: nobody → Canonical Desktop Team (canonical-desktop-team)
Revision history for this message
stefano fanucchi (slackpinguino) wrote :

Crashed after login

Revision history for this message
Alberto (alberto-torricelli) wrote :

During an apt-get upgrade, suddenly happened

Revision history for this message
danghaag (danghaag) wrote :

This crashes shortly after every login.

Revision history for this message
Kostya Pakhomov (naluster) wrote :

Crashed shortly after login

Revision history for this message
Devon Private (dawiz-99) wrote :

Crashed after login, on i386 upgrade from 11.04 Natty

tags: added: rls-mgr-o-tracking
Revision history for this message
Martin Pitt (pitti) wrote :

This crash happens on logout, which is fairly uninteresting. You just see the apport report at login, because at that point it picks up crash reports which haven't been presented yet.

Changed in indicator-session (Ubuntu Oneiric):
importance: High → Low
milestone: ubuntu-11.10 → none
Martin Pitt (pitti)
tags: added: bugpattern-written
removed: bugpattern-needed
Revision history for this message
Ricardo Paulino (paulinocorp) wrote : Re: [Bug 852343] Re: gtk-logout-helper crashed with signal 5 in __libc_start_main()

But then, is there anything to do?

Thanks.

paulinocorp

Em sexta-feira, 30 de setembro de 2011, Martin Pitt escreveu:

> This crash happens on logout, which is fairly uninteresting. You just
> see the apport report at login, because at that point it picks up crash
> reports which haven't been presented yet.
>
> ** Changed in: indicator-session (Ubuntu Oneiric)
> Importance: High => Low
>
> ** Changed in: indicator-session (Ubuntu Oneiric)
> Milestone: ubuntu-11.10 => None
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (853385).
> https://bugs.launchpad.net/bugs/852343
>
> Title:
> gtk-logout-helper crashed with signal 5 in __libc_start_main()
>
> Status in “indicator-session” package in Ubuntu:
> Confirmed
> Status in “indicator-session” source package in Oneiric:
> Confirmed
>
> Bug description:
> Got this after login
>
> ProblemType: Crash
> DistroRelease: Ubuntu 11.10
> Package: indicator-session 0.3.5.1-0ubuntu1
> ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
> Uname: Linux 3.0.0-10-generic x86_64
> ApportVersion: 1.23-0ubuntu1
> Architecture: amd64
> Date: Sat Sep 17 00:08:25 2011
> ExecutablePath: /usr/lib/indicator-session/gtk-logout-helper
> InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110715)
> ProcCmdline: /usr/lib/indicator-session/gtk-logout-helper --shutdown
> ProcEnviron:
> SHELL=/bin/false
> PATH=(custom, no user)
> LANG=en_US.UTF-8
> Signal: 5
> SourcePackage: indicator-session
> StacktraceTop:
> ?? ()
> ?? ()
> __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6
> ?? ()
> ?? ()
> Title: gtk-logout-helper crashed with signal 5 in __libc_start_main()
> UpgradeStatus: No upgrade log present (probably fresh install)
> UserGroups:
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/852343/+subscriptions
>

--
Ricardo Filipe Guimarães Gonçalves Paulino
*<email address hidden>*
<email address hidden>
www.twetter.com/paulinocorp <http://www.tweter.com/paulinocorp>
Programador

Revision history for this message
Dave Gilbert (ubuntu-treblig) wrote :

Should this be duped with bug 543609?
(I'm tempted but given the number of dupes in both I'm a bit cautious).

Martin Pitt (pitti)
Changed in indicator-session (Ubuntu):
assignee: Canonical Desktop Team (canonical-desktop-team) → nobody
Changed in indicator-session (Ubuntu Oneiric):
assignee: Canonical Desktop Team (canonical-desktop-team) → nobody
Revision history for this message
Charles Kerr (charlesk) wrote :

gtk-logout-helper -- which is where this crash occurred -- no longer exists in indicator-session, so I believe this crash has been fixed.

It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running apport-collect <bug #> and any other logs that are relevant for this particular issue.

Changed in indicator-session (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
Charles Kerr (charlesk) wrote :

Marking this as Wontfix for Oneiric, which was end-of-lifed in May 2013.

Changed in indicator-session (Ubuntu Oneiric):
status: Confirmed → Won't Fix
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.