gedit crashed with SIGSEGV in PyEval_EvalFrameEx()

[Christian González]

I upgraded Ubuntu from natty to oneiric and with it Gedit from 2 to 3.
When I just write some text, select a few letters with the mouse and drag these letters to another place, gedit3 crashes reproducible.

What I tested until now is that if I use a fresh user account, the problem does not exist. So IMHO it is something that has to do with the transition from the gedit2 config files to gedit3 which maybe are not read correctly?
I didn't find out where I can compare the two users' gedit configs - where can I look?

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gedit 3.2.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 1.23-0ubuntu3
Architecture: amd64
CrashCounter: 1
Date: Tue Oct 11 10:20:11 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gedit
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
ProcCmdline: gedit /home/username/Projekte/Critecia/critecia/src/app/views/slots/add_month_schedule.ctp
SegvAnalysis:
 Segfault happened at: 0x7fe9c9ce5ef0: mov -0x8(%rsi),%rdx
 PC (0x7fe9c9ce5ef0) 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-10-07 (3 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:
 __memcpy_ssse3_back () at ../sysdeps/x86_64/multiarch/memcpy-ssse3-back.S:2001
 _pygi_marshal_from_py_array (state=0x7fffeda61860, callable_cache=0x2ee4980, arg_cache=0x254c200, py_arg=[<Atom at remote 0x2501f18>, <Atom at remote 0x2501f70>, <Atom at remote 0x2501fc8>, <Atom at remote 0x2527050>, <Atom at remote 0x25270a8>, <Atom at remote 0x2527100>, <Atom at remote 0x2527158>, <Atom at remote 0x25271b0>], arg=0x2e8e6b0) at /usr/include/x86_64-linux-gnu/bits/string3.h:52
 _invoke_marshal_in_args (cache=0x2ee4980, state=0x7fffeda61860) at /build/buildd/pygobject-3.0.0/gi/pygi-invoke.c:483
 _wrap_g_callable_info_invoke (self=0x2525d88, py_args=<optimized out>, kwargs=<optimized out>) at /build/buildd/pygobject-3.0.0/gi/pygi-invoke.c:620
 ext_do_call (nk=0, na=<optimized out>, flags=<optimized out>, pp_stack=0x7fffeda619f0, func=<built-in method invoke of gi.FunctionInfo object at remote 0x2525d88>) at ../Python/ceval.c:4331

[Sebastien Bacher (seb128)]

The issue is in some python code, try to see what extra option you enabled using python there?

[Sebastien Bacher (seb128)]

likely bug #863773