Thank you for taking the time to report this bug and helping to make
Ubuntu better.
The rest of the backtrace tells a more interesting tale; it looks like maybe
gtk-logout-helper was smashing the stack in a loop. gtk-logout-helper.c was
removed in the 13.10 release, so 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.
#669 0x0000000000406da8 in consolekit_fallback
(action=action@entry=LOGOUT_DIALOG_TYPE_RESTART) at gtk-logout-helper.c:91
error = 0x2e7ba50
result = <optimized out>
#670 0x0000000000406da8 in consolekit_fallback
(action=action@entry=LOGOUT_DIALOG_TYPE_RESTART) at gtk-logout-helper.c:91
error = 0x2e7b8c0
result = <optimized out>
#671 0x0000000000406da8 in consolekit_fallback
(action=action@entry=LOGOUT_DIALOG_TYPE_RESTART) at gtk-logout-helper.c:91
error = 0x2e7bb00
result = <optimized out>
** Changed in: indicator-session (Ubuntu)
Status: New => Incomplete
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1156036
Title:
gtk-logout-helper crashed with SIGSEGV in __find_specmb()
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1156036/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
