Attached are the debug files. I first did the gdb run, and seahorse faulted as expected after entering the pass phrase. (logs attached)
However when running under valgrind, a segment fault DID NOT occur after entering the passphrase, and it then prompted for a server name and user to connect to. Therefore it got further than before. I am currently at work and don't have access to that server, so a correct error was displayed saying the server could not be found at that point. (I am assuming it would have then worked if the server was available). If the attached logs do not provide you with enough information, please let me know and I will re-run the valgrind at home where the server is available. However as I never got to this point before, I am guessing you should have the appropriate debug info. regards, Matt Andreas Moog wrote: > Thanks for the update. Please try to obtain a backtrace following the > instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload > the backtrace (as an attachment) to the bug report. This will greatly > help us in tracking down your problem. > > ** Attachment added: "valgrind-seahorse.log.tar.gz" http://launchpadlibrarian.net/17283967/valgrind-seahorse.log.tar.gz ** Attachment added: "gdb-seahorse.txt" http://launchpadlibrarian.net/17283968/gdb-seahorse.txt -- seahorse crashed with SIGSEGV in glade_xml_get_widget() https://bugs.launchpad.net/bugs/183509 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to seahorse in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
