Actually, let me change that request... it appears to me that these backtraces are suspect, because (1) they are showing very different crash locations, and (2) ThreadStacktrace.txt (retrace) says that we're crashing in GMemChunk calls inside of GKeyFile in glib 2.16.1, but I've been looking at the source and GKeyFile doesn't call GMemChunk.
So, the first thing to do IMO is to make sure that your libraries are in order. If you're positive that isn't the case, then run Transmission inside of valgrind to figure out where the memory corruption is coming from. If you download Transmission from svn, there's a bash script in the gtk/ directory for running Transmission under valgrind's microscope. -- transmission crashed with SIGSEGV https://bugs.launchpad.net/bugs/204677 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
