[ Oneiric i386 b1 ] gtk-logout-helper crashed with signal 5 in __libc_start_main()

Bug #839325 reported by dino99
836
This bug affects 191 people
Affects Status Importance Assigned to Milestone
indicator-session (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

After a 2 steps shutdown: first, logout, then shutdown, i find this crash at next cold boot time, all latest updates done.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: indicator-session 0.3.4.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-9.15-generic-pae 3.0.3
Uname: Linux 3.0.0-9-generic-pae i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Fri Sep 2 08:36:49 2011
ExecutablePath: /usr/lib/indicator-session/gtk-logout-helper
ProcCmdline: /usr/lib/indicator-session/gtk-logout-helper --shutdown
ProcEnviron:
 SHELL=/bin/false
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
Signal: 5
SourcePackage: indicator-session
StacktraceTop:
 ?? ()
 __libc_start_main (main=0x80492d0, argc=2, ubp_av=0xbf8342a4, init=0x804a520, fini=0x804a590, rtld_fini=0xb77d2bc0, stack_end=0xbf83429c) at libc-start.c:226
 ?? ()
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
dino99 (9d9) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop: ?? ()

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):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed
Download full text (3.2 KiB)

Thank you for your report!

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:

outdated debug symbol package for libavahi-common3: package version 0.6.30-4ubuntu1 dbgsym version 0.6.30-0ubuntu2
outdated debug symbol package for libslang2: package version 2.2.4-2ubuntu1 dbgsym version 2.2.2-4ubuntu2
outdated debug symbol package for libtiff4: package version 3.9.5-1ubuntu1 dbgsym version 3.9.4-5ubuntu6
outdated debug symbol package for libnih1: package version 1.0.3-4ubuntu2 dbgsym version 1.0.3-1ubuntu1
outdated debug symbol package for libgpg-error0: package version 1.10-0.3ubuntu1 dbgsym version 1.10-0.2ubuntu1
outdated debug symbol package for dbus: package version 1.4.12-4ubuntu2 dbgsym version 1.4.6-1ubuntu6.1
libpango1.0-0 version 1.29.3+git20110809.b74e01cc-0ubuntu1~11.10~ricotz0 required, but 1.29.3-0ubuntu3 is available
outdated debug symbol package for libk5crypto3: package version 1.9.1+dfsg-1ubuntu1 dbgsym version 1.8.3+dfsg-5ubuntu2.1
outdated debug symbol package for libavahi-client3: package version 0.6.30-4ubuntu1 dbgsym version 0.6.30-0ubuntu2
outdated debug symbol package for x11-xkb-utils: package version 7.6+4 dbgsym version 7.6+2
outdated debug symbol package for passwd: package version 1:4.1.4.2+svn3283-3ubuntu2 dbgsym version 1:4.1.4.2+svn3283-3ubuntu1
outdated debug symbol package for libkrb5-3: package version 1.9.1+dfsg-1ubuntu1 dbgsym version 1.8.3+dfsg-5ubuntu2.1
outdated debug symbol package for libxklavier16: package version 5.1-1ubuntu1 dbgsym version 5.0-2ubuntu1
outdated debug symbol package for libdatrie1: package version 0.2.4-3 dbgsym version 0.2.4-1
libglib2.0-0 version 2.29.18~git20110829.d156492c-0ubuntu1~11.10~ricotz0 required, but 2.29.16-0ubuntu3 is available
outdated debug symbol package for libdbus-1-3: package version 1.4.12-4ubuntu2 dbgsym version 1.4.6-1ubuntu6.1
outdated debug symbol package for libgssapi-krb5-2: package version 1.9.1+dfsg-1ubuntu1 dbgsym version 1.8.3+dfsg-5ubuntu2.1
outdated debug symbol package for upower: package version 0.9.12-1 dbgsym version 0.9.9-4
outdated debug symbol package for procps: package version 1:3.2.8-10ubuntu5 dbgsym version 1:3.2.8-10ubuntu3
outdated debug symbol package for libltdl7: package version 2.4-2ubuntu1 dbgsym version 2.2.6b-2ubuntu3
outdated debug symbol package for libupower-glib1: package version 0.9.12-1 dbgsym version 0.9.9-4
outdated debug symbol package for libkrb5support0: package version 1.9.1+dfsg-1ubuntu1 dbgsym version 1.8.3+dfsg-5ubuntu2.1
outdated debug symbol package for dpkg: package version 1.16.0.3ubuntu3 dbgsym version 1.16.0~ubuntu7.1
outdated debug symbol package for libnih-dbus1: package version 1.0.3-4ubuntu2 dbgsym version 1.0.3-1ubuntu1
outdated debug symbol package for module-init-tools: package version 3.16-1ubuntu1 dbgsym version 3.12-1ubuntu6
outdated debug symbol package for libthai0: package version 0.1.15-2 dbgsym version 0.1.14-2ubuntu1

Please upgrade your system to the latest package versions. If you still
encou...

Read more...

tags: removed: need-i386-retrace
dino99 (9d9)
description: updated
Revision history for this message
Ted Gould (ted) wrote : Re: [Bug 839325] Re: [ Oneiric i386 b1 ] gtk-logout-helper crashed with signal 5 in __libc_start_main()

On Fri, 2011-09-02 at 07:16 +0000, dino99 wrote:
> + After a 2 steps shutdown: first, logout, then shutdown, i find this
> + crash at next cold boot time, all latest updates done.

So to be clear, the machine shuts down, you just get the crash dialog
when you log in the next time?

Revision history for this message
Evan Huus (eapache) wrote :

I just experienced this bug with a fully up-to-date Oneiric. Marking as confirmed.

Changed in indicator-session (Ubuntu):
status: Invalid → Confirmed
Revision history for this message
dino99 (9d9) wrote :

@Ted
yes for #6 above

to reproduce:
- logout
- shutdown

and find the crash on next boot. I get it when i'm logged as gnome-classic (not tested with Ubuntu/Unity as i dont use them)

Revision history for this message
dino99 (9d9) wrote :

Please look at the same similar crash produced with dbgsym to get more info:

bug #839371 : crash with dbgsym & valgrind

Using dbgsym have changed the title bug report, but its the same crash.

Revision history for this message
Efrain Valles (effie-jayx) wrote :

I can confirm, after restarting and starting a session.

Revision history for this message
tfmoraes (tfmoraes) wrote :

I'm having this bug too, but I'm running a 64 bits Ubuntu 11.10 b1.

Revision history for this message
icarrero (icarrero) wrote :

same as tfmoraes, and mine crash when rebooting too, not only when logout+halt

Revision history for this message
Jared (jared-vanvolkenburg) wrote :

I haven't been able to successfully load the unity desktop since this crash. All I get is the desktop with the file menu in the top left corner. I am not able to view or access any indicators or the unity bar. I have logged off, rebooted, and manually shutdown without successfully fixing the problem. I logged on as a guest user and unity started up successfully.

Revision history for this message
Brandon Bolton (brandon-bolton-224) wrote :

I just got this when I logged in. I have 11.10 32-bit and I run updates all of the time.

Revision history for this message
philinux (philcb) wrote :

Same on 64 bit.

Revision history for this message
JoshuaPurcell (joshua-purcell) wrote :

Although the original report for this bug only mentions 32-bit, this bug also affects 64-bit install as is mentioned in post #15.

Revision history for this message
Brad Needham (fishrcynic) wrote :

Ditto 64 bit here

Revision history for this message
hcmeyer (hcmeyer) wrote :

2 comments:

1) I seem to have experienced this bug after installing gnome3 desktop, it did not occur before

2) i have been unable to shutdown from the desktop or the login screen, either sudo poweroff or the big red switch is needed.

Revision history for this message
Anthony Harrington (linuxchemist) wrote :

Further to comment 18, when the shutdown option is selected from the "power cog" (shutdown -> shutdown), it instead logs me out and the shutdown option at the lightdm screen does nothing. What i have to do as a quick workaround is to use sudo halt, after logging into tty1 - but pc refuses to poweroff of its own accord anymore.

Revision history for this message
Eduard Hasenleithner (eduard-hasenleithner) wrote :

IMHO the gtk-logout-helper crash must not be mixed up with the other symptom described in comment 18 and 19. I've also experienced failing to shutdown, and think it is probably already documented in Bug #838792 and Bug #660120.

(N.B: I have the feeling that neither indicator-session nor gnome-session are responsible for the bug, and there is a different common root cause.)

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.