Sorry to bother You again ... Even if the execution of gnome-help inside valgrind doesn't generate any crash, I saw that the log output of valgrind is not "empty". Maybe the new attached TXT file could display some info about the bug.
I'm not able to understand, but it seems that valgrind detected some errors and prevented the SIGSEGV to happen. Ciao CM ** Attachment added: "TXT file generated by valgrind (no crash - many errors)" http://launchpadlibrarian.net/50910245/valgrind-log.txt -- gnome-help crashed (segmentation fault) while printing https://bugs.launchpad.net/bugs/580206 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to yelp in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
