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.
** Changed in: indicator-session (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/839371
Title:
gtk-logout-helper crashed with signal 5 in consolekit_fallback()
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/839371/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
