gedit crashed with SIGSEGV in __memcpy_ssse3() (when using snippet)

Bug #863773 reported by John M
164
This bug affects 25 people
Affects Status Importance Assigned to Milestone
pygobject
Fix Released
Critical
gedit (Ubuntu)
Fix Released
High
Unassigned
Oneiric
Fix Released
High
Unassigned
pygobject (Ubuntu)
Fix Released
High
Unassigned
Oneiric
Won't Fix
High
Unassigned

Bug Description

A simple file drag and drop from Nautilus crashes gedit.

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
Date: Thu Sep 29 16:48:54 2011
ExecutablePath: /usr/bin/gedit
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110921.2)
ProcCmdline: gedit
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f7369006a10 <__memcpy_ssse3+6784>: mov -0x8(%rsi),%rdx
 PC (0x7f7369006a10) ok
 source "-0x8(%rsi)" (0x000000a9) not located in a known VMA region (needed readable region)!
 destination "%rdx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gedit
StacktraceTop:
 __memcpy_ssse3 () at ../sysdeps/x86_64/multiarch/memcpy-ssse3.S:1816
 ?? () 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 __memcpy_ssse3()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
John M (jwmwalrus) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __memcpy_ssse3 () at ../sysdeps/x86_64/multiarch/memcpy-ssse3.S:1816
 _pygi_marshal_from_py_array (state=0x7fff669c63d0, callable_cache=0x7f735dc9ecc0, arg_cache=0x7f735d87de60, py_arg=[<Atom at remote 0x5b05730>, <Atom at remote 0x5b05940>, <Atom at remote 0x5b05520>, <Atom at remote 0x5b05050>, <Atom at remote 0x5b05b50>, <Atom at remote 0x5b05ec0>, <Atom at remote 0x5b05310>, <Atom at remote 0x5b03310>], arg=0x7f7351a20e80) at /usr/include/x86_64-linux-gnu/bits/string3.h:52
 _invoke_marshal_in_args (cache=0x7f735dc9ecc0, state=0x7fff669c63d0) at /build/buildd/pygobject-3.0.0/gi/pygi-invoke.c:483
 _wrap_g_callable_info_invoke (self=0x669ae18, 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=0x7fff669c6560, func=<built-in method invoke of gi.FunctionInfo object at remote 0x669ae18>) at ../Python/ceval.c:4331

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gedit (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote : Re: gedit crashed with SIGSEGV in __memcpy_ssse3()

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gedit (Ubuntu):
status: New → Confirmed
Revision history for this message
Andreas Grois (soulsource) wrote :

Apport Retracing Service thinks, that my last report (#865214) is a duplicate of this bug. If this is true, then this bug has something to do with the snippets-plugin. In my case, the crashes on drag and drop only happen if the snippets plugin is on. If it's disabled, drag and drop works for me.

Revision history for this message
John M (jwmwalrus) wrote :

I confirm that disabling the snippets plugin is a workaround to the crash. So, this bug is related to Bug #865214.

Changed in gedit (Ubuntu):
importance: Medium → High
Changed in gedit (Ubuntu Oneiric):
assignee: nobody → Michael Terry (mterry)
importance: Undecided → High
status: New → Confirmed
summary: - gedit crashed with SIGSEGV in __memcpy_ssse3()
+ gedit crashed with SIGSEGV in __memcpy_ssse3() (when using snippet)
Revision history for this message
Michael Terry (mterry) wrote :

This is because of a Gtk.targets_include_uri(context.list_targets()) call in snippets plugin. I'm checking now if this is due to bad gtk bindings or not for drag contexts...

Revision history for this message
Michael Terry (mterry) wrote :

Reproducable with just:

from gi.repository import Gtk, Gdk
Gtk.targets_include_uri([Gdk.Atom.intern('text/plain', False)])

I think this is a failure of pygobject to notice the 'disguised' GIR property of Gdk.Atom. I've filed an upstream bug about it.

affects: gedit (Ubuntu) → pygobject (Ubuntu)
Changed in pygobject:
importance: Unknown → Medium
status: Unknown → New
Changed in pygobject:
importance: Medium → Critical
status: New → Confirmed
Martin Pitt (pitti)
Changed in pygobject (Ubuntu):
status: Confirmed → Triaged
Changed in pygobject (Ubuntu Oneiric):
status: Confirmed → Triaged
Revision history for this message
Michael (michaeljt) wrote :

This page [1] suggests that this is fixed upstream in gedit 3.2.3.

[1] http://askubuntu.com/questions/80992/cant-drag-and-drop-text-in-gedit

Revision history for this message
Sebastien Bacher (seb128) wrote :

The corresponding commit is:
http://git.gnome.org/browse/gedit/commit/?h=gnome-3-2&id=d9e37ea7aced28f6d30026e097039e9bfb5cd106

Mike, do you think you could SRU that (or the 3.2.3 update maybe, the git logs seem to indicate the changes there should be fine in a SRU)

Revision history for this message
Sebastien Bacher (seb128) wrote :

the new version fixes bug #840765 as well

Michael Terry (mterry)
Changed in gedit (Ubuntu):
status: New → Fix Released
Changed in gedit (Ubuntu Oneiric):
assignee: nobody → Michael Terry (mterry)
Changed in pygobject (Ubuntu Oneiric):
assignee: Michael Terry (mterry) → nobody
Changed in gedit (Ubuntu Oneiric):
status: New → Triaged
importance: Undecided → High
Changed in gedit (Ubuntu):
importance: Undecided → High
Revision history for this message
Michael Terry (mterry) wrote :

I've uploaded gedit 3.2.3 to oneiric-proposed. Will subscribe ubuntu-sru. This is a good SRU candidate because it will crash gedit, causing data loss if you haven't saved.

To reproduce, open gedit, enable the snippets plugin, and drag text from some other window into gedit.

Changed in gedit (Ubuntu Oneiric):
assignee: Michael Terry (mterry) → nobody
Revision history for this message
Martin Pitt (pitti) wrote : Please test proposed package

Hello John, or anyone else affected,

Accepted gedit into oneiric-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

Changed in gedit (Ubuntu Oneiric):
status: Triaged → Fix Committed
tags: added: verification-needed
Revision history for this message
John M (jwmwalrus) wrote :

I confirm that installing the package from oneiric-proposed (gedit version 3.2.3-0ubuntu0.1) solves the issue ---i.e., drag and drop from nautilus no longer crashes gedit when the snippets plugin is enabled.

Martin Pitt (pitti)
tags: added: verification-done
removed: verification-needed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gedit - 3.2.3-0ubuntu0.1

---------------
gedit (3.2.3-0ubuntu0.1) oneiric-proposed; urgency=low

  * New upstream release
    - Fixes crash when dragging text into gedit (LP: #863773)
    - Fixes "Edit->Insert Date" menu item (LP: #840765)
  * debian/patches/07_pyconsole_crash.patch:
    - Dropped, applied upstream
 -- Michael Terry <email address hidden> Fri, 02 Dec 2011 12:16:58 -0500

Changed in gedit (Ubuntu Oneiric):
status: Fix Committed → Fix Released
Changed in pygobject:
status: Confirmed → Fix Released
Revision history for this message
Martin Pitt (pitti) wrote :

This was fixed in April already.

Changed in pygobject (Ubuntu):
status: Triaged → Fix Released
Revision history for this message
Rolf Leggewie (r0lf) wrote :

oneiric has seen the end of its life and is no longer receiving any updates. Marking the oneiric task for this ticket as "Won't Fix".

Changed in pygobject (Ubuntu Oneiric):
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.