[Bug 62446] Re: at-spi-registryd crash (please attach backtraces, check crash reports before)
Your bug lacks information we would need to investigate further. We are now going to close the bug - please reopen if you have more information at hand. ** Changed in: at-spi (Ubuntu) Status: Needs Info = Rejected -- at-spi-registryd crash (please attach backtraces, check crash reports before) https://launchpad.net/bugs/62446 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 62446] Re: at-spi-registryd crash (please attach backtraces, check crash reports before)
Does anybody have news on this one? ** Changed in: at-spi (Ubuntu) Importance: Undecided = Medium -- at-spi-registryd crash (please attach backtraces, check crash reports before) https://launchpad.net/bugs/62446 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 62446] Re: at-spi-registryd crash (please attach backtraces, check crash reports before)
** Bug 64341 has been marked a duplicate of this bug -- at-spi-registryd crash (please attach backtraces, check crash reports before) https://launchpad.net/bugs/62446 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 62446] Re: at-spi-registryd crash (please attach backtraces, check crash reports before)
I have seen this as well. However, it is problematic to generate a backtrace from at-spi-registryd, as it drops to T state (in ps aux) whenever you attach to it using either gdb or strace, and kill -CONT'ing it does not help, and it actually makes Gnome in general not respond. I am more than willing to help debug this problem, but not while it can't be debugged by the means pointed out in the wiki page you linked to. -- at-spi-registryd crash (please attach backtraces, check crash reports before) https://launchpad.net/bugs/62446 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 62446] Re: at-spi-registryd crash (please attach backtraces, check crash reports before)
I've not had any crashes after today's update. Anyone else? I've tried to stress it a bit by killing and restarting it as well. -- at-spi-registryd crash (please attach backtraces, check crash reports before) https://launchpad.net/bugs/62446 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 62446] Re: at-spi-registryd crash (please attach backtraces, check crash reports before)
Meh, spoke too soon. I just got the crash again :( However, some observations: First there are two copies of at-spi- registryd running in gnome, one as user and one as root. When I try tol attach gdb to the user version PID I get a general Gnome freeze as Steve says. If I start KDE from GDM instead of Gnome I get zero copies of at-spi- registryd running (no surprise there). When I then start orca from KDE I get ONE copy of at-spi-registryd and that one accepts a gdb attach. So my plan now is to run that and start lots of gnome apps in Gnome and see if I can provoke a crash. -- at-spi-registryd crash (please attach backtraces, check crash reports before) https://launchpad.net/bugs/62446 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 62446] Re: at-spi-registryd crash (please attach backtraces, check crash reports before)
I have similar error ** Attachment added: auto report http://librarian.launchpad.net/4607343/_usr_lib_at-spi_at-spi-registryd.1000.crash -- at-spi-registryd crash (please attach backtraces, check crash reports before) https://launchpad.net/bugs/62446 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 62446] Re: at-spi-registryd crash (please attach backtraces, check crash reports before)
tasadar_f: your report does not contain a backtrace either. -- at-spi-registryd crash (please attach backtraces, check crash reports before) https://launchpad.net/bugs/62446 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 62446] Re: at-spi-registryd crash (please attach backtraces, check crash reports before)
I have a similar bug ** Attachment added: ouput http://librarian.launchpad.net/4619523/_usr_lib_at-spi_at-spi-registryd.1000.crash -- at-spi-registryd crash (please attach backtraces, check crash reports before) https://launchpad.net/bugs/62446 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 62446] Re: at-spi-registryd crash (please attach backtraces, check crash reports before)
+1, details attached. ** Attachment added: Autogenerated crash report http://librarian.launchpad.net/4566868/_usr_lib_at-spi_at-spi-registryd.1000.crash -- at-spi-registryd crash (please attach backtraces, check crash reports before) https://launchpad.net/bugs/62446 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 62446] Re: at-spi-registryd crash (please attach backtraces, check crash reports before)
** Description changed: - the problem report just pops up + I have the same bug! + at-spi-registrydclosed unexpectedly -- at-spi-registryd crash (please attach backtraces, check crash reports before) https://launchpad.net/bugs/62446 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 62446] Re: at-spi-registryd crash (please attach backtraces, check crash reports before)
The crash report does not contain a backtrace. -- at-spi-registryd crash (please attach backtraces, check crash reports before) https://launchpad.net/bugs/62446 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
