This bug is easy to reproduce (hopefully not only on my machine): Enable the snippets plugin in the preferences of gedit and then try to drag and drop some text within the gedit window. Gedit will crash. Everything works fine, if the snippets plugin is turned off.
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gedit 3.2.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Mon Oct 3 11:14:23 2011
ExecutablePath: /usr/bin/gedit
ProcCmdline: gedit
SegvAnalysis:
Segfault happened at: 0x7fac79b37a10: mov -0x8(%rsi),%rdx
PC (0x7fac79b37a10) ok
source "-0x8(%rsi)" (0x0000007c) not located in a known VMA region (needed readable region)!
destination "%rdx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gedit
StacktraceTop:
?? () from /lib/x86_64-linux-gnu/libc.so.6
?? () from /usr/lib/python2.7/dist-packages/gi/_gi.so
?? () from /usr/lib/python2.7/dist-packages/gi/_gi.so
PyEval_EvalFrameEx () from /usr/lib/libpython2.7.so.1.0
PyEval_EvalCodeEx () from /usr/lib/libpython2.7.so.1.0
Title: gedit crashed with SIGSEGV in PyEval_EvalFrameEx()
UpgradeStatus: Upgraded to oneiric on 2011-09-27 (6 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #863773, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.