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

StacktraceTop: ?? ()

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...

Stacktrace done with dbgsym package installed, as same crash (without dbgsym) is reported by apport as :

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

so this related bug: 839325 declared invalid due to missing info.

Apport badly fails to report an existing Stacktrace, here is what i get when i try again to report this crash:

StacktraceTop:
consolekit_fallback (action=LOGOUT_DIALOG_TYPE_SHUTDOWN) at /build/buildd/indicator-session-0.3.4.1/./src/gtk-logout-helper.c:71

session_action (action=LOGOUT_DIALOG_SHUTDOWN) at /build/buildd/indicator-session-0.3.4.1/./src/gtk-logout-helper.c:100

main (argc=1, argv=0xbf8183d4) at /build/buildd/indicator-session-0.3.4.1/./src/gtk-logout-helper.c:213

Then post #5 above cant be understood: DebuggingProgramCrash wiki has been followed to get the dbgsym packages, so the system is fully updated , so dbgsym package have the same version (searching into nautilus for these "outdated" dbgsym fails of course)

So i declare this report as new again.

On Fri, 2011-09-02 at 09:12 +0000, dino99 wrote:
> consolekit_fallback (action=LOGOUT_DIALOG_TYPE_SHUTDOWN) at /build/buildd/indicator-session-0.3.4.1/./src/gtk-logout-helper.c:71

I don't disagree that this is the stack trace, unfortunately that line
is a simple print out:

  71 g_error("Unable to signal ConsoleKit");

That doesn't even take any parameters. So it's got to be something else
in another thread or a wild memory pointer. If you could check with
valgrind that might catch some invalid accesses that would show us where
the wild pointer could be, thanks!

  http://wiki.ubuntu.com/Valgrind

Thanks Ted for helping

apport information

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

fixed with Precise