Looks like I hit something very much like this. In quick succession I had 3 other .crash files generated:
-rw-r----- 1 tt whoopsie 5218850 Aug 11 14:35 _usr_bin_python2.7.1000.crash -rw-r----- 1 tt whoopsie 63921832 Aug 11 14:37 _usr_bin_skype.1000.crash -rw-r----- 1 tt whoopsie 2291669 Aug 11 14:35 _usr_lib_unity-settings-daemon_unity-settings-daemon.1000.crash -rw-r----- 1 root whoopsie 125489 Aug 11 14:39 _usr_sbin_aptd.0.crash -rw-r--r-- 1 root whoopsie 0 Aug 11 14:39 _usr_sbin_aptd.0.upload -rw------- 1 whoopsie whoopsie 0 Aug 11 14:40 _usr_sbin_aptd.0.uploaded The aptd one was attributed to bug #1022993. The python one brought me here. I will see if the Skype one takes me to the item that doko mentions above. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/982816 Title: python2.7 crashed with SIGSEGV in __pthread_mutex_lock() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/982816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
