Hi Lockal, from the stacktrace it looks like a null pointer's being dereferenced in tr_sessionLock()'s call to "tr_lockLock (session->lock);" ... however, session->lock is initialized on startup and then never changed until shutdown. So maybe the crash reporter tool got confused with which report it sent with your summary, or maybe there's some memory corruption going on that NULLed that pointer out.
Lockal, are you able to reproduce this bug? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1199082 Title: transmission-gtk crashed with SIGSEGV in __GI___pthread_mutex_lock() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1199082/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
