*
As I discussed on Launchpad, I think this backtrace is suspect because
it says that we're crashing inside GMemChunk, called by GKeyFile, in
glib 2.16.1. However I've just been looking at glib 2.16.1's source and
GMemChunk isn't used by GKeyFile (in fact, since it's deprecated it's
not called by any other glib or Transmission code).
So my first thought is that this is some kind of ABI library shear
problem, and I suggest you upgrade Transmission and/or build from source
to test that way. If a copy of Transmission built from source crashes,
I'm very much interested in that.
Also, it would be good if you could provide a valgrind log generated by
the bash script from transmission/gtk/my-valgrind.sh in svn.
Marking as invalid because there's nothing usable in the report to
date... but obviously if the problem persists in a fresh build I'm very
interested in hearing about it.
** Changed in: transmission (Ubuntu)
Status: New => Invalid
--
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
