← Back to team overview

dx-packages team mailing list archive

[Bug 852343] Re: gtk-logout-helper crashed with signal 5 in __libc_start_main()

 

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

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-session in Ubuntu.
Matching subscriptions: dx-packages
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:
  Fix Released
Status in “indicator-session” source package in Oneiric:
  Won't Fix

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