gedit crashed with SIGSEGV

Bug #829044 reported by Curtis Hovey
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gedit
Fix Released
Medium
gedit (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

I was using the snippet completion plugin. After using control+space to open the completion list. pressed the details button to see more about the selection. gedit went belly up:

Traceback (most recent call last):
  File "/usr/lib/gedit/plugins/snippets/completion.py", line 126, in do_get_info_widget
    view = Gedit.View(Gedit.Document())
TypeError: GObject.__init__() takes exactly 0 arguments (1 given)

^ This looks like a python gi error. Classes that descend from gobject must be initialised using keyword arguments. I expect the problem line to be written as
    view = Gedit.View(doc=Gedit.Document())
per http://developer.gnome.org/gedit/stable/gedit-gedit-view.html#gedit-view-new

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gedit 3.1.3-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-8.11-generic-pae 3.0.1
Uname: Linux 3.0.0-8-generic-pae i686
NonfreeKernelModules: nvidia wl
Architecture: i386
CrashCounter: 1
Date: Thu Aug 18 17:08:48 2011
Disassembly: => 0xb77e79f7: Cannot access memory at address 0xb77e79f7
ExecutablePath: /usr/bin/gedit
ProcCmdline: gedit
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0xb77e79f7: Cannot access memory at address 0xb77e79f7
 PC (0xb77e79f7) ok
 SP (0xbfa5b7a0) ok
 Reason could not be automatically determined.
Signal: 11
SourcePackage: gedit
Stacktrace:
 #0 0xb77e79f7 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0xbfa5b7a0
StacktraceTop: ?? ()
Title: gedit crashed with SIGSEGV
UpgradeStatus: Upgraded to oneiric on 2011-07-30 (19 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Curtis Hovey (sinzui) wrote :
visibility: private → public
Changed in gedit:
importance: Unknown → Medium
status: Unknown → New
Revision history for this message
Apport retracing service (apport) wrote :

Stacktrace:
 #0 0xb77e79f7 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0xbfa5b7a0
StacktraceTop: ?? ()

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gedit (Ubuntu):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed
Download full text (3.8 KiB)

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate an useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

libgcc1 version 1:4.6.1-7ubuntu1 required, but 1:4.6.1-7ubuntu2 is available
outdated debug symbol package for libavahi-common3: package version 0.6.30-4ubuntu1 dbgsym version 0.6.30-0ubuntu2
outdated debug symbol package for libtiff4: package version 3.9.5-1ubuntu1 dbgsym version 3.9.4-5ubuntu6
gir1.2-peas-1.0 version 1.1.1-0ubuntu2 required, but 1.1.1-0ubuntu3 is available
outdated debug symbol package for dpkg: package version 1.16.0.3ubuntu3 dbgsym version 1.16.0~ubuntu7.1
libpam-modules version 1.1.3-1ubuntu3 required, but 1.1.3-2ubuntu1 is available
outdated debug symbol package for libgpg-error0: package version 1.10-0.3ubuntu1 dbgsym version 1.10-0.2ubuntu1
libpam0g version 1.1.3-1ubuntu3 required, but 1.1.3-2ubuntu1 is available
libpam-modules-bin version 1.1.3-1ubuntu3 required, but 1.1.3-2ubuntu1 is available
libfontconfig1 version 2.8.0-3ubuntu1 required, but 2.8.0-3ubuntu2 is available
outdated debug symbol package for libk5crypto3: package version 1.9.1+dfsg-1ubuntu1 dbgsym version 1.8.3+dfsg-5ubuntu2.1
outdated debug symbol package for libavahi-client3: package version 0.6.30-4ubuntu1 dbgsym version 0.6.30-0ubuntu2
outdated debug symbol package for passwd: package version 1:4.1.4.2+svn3283-3ubuntu2 dbgsym version 1:4.1.4.2+svn3283-3ubuntu1
outdated debug symbol package for libkrb5-3: package version 1.9.1+dfsg-1ubuntu1 dbgsym version 1.8.3+dfsg-5ubuntu2.1
outdated debug symbol package for libdatrie1: package version 0.2.4-3 dbgsym version 0.2.4-1
libpeas-common version 1.1.1-0ubuntu2 required, but 1.1.1-0ubuntu3 is available
libenchant1c2a version 1.6.0-2 required, but 1.6.0-3 is available
fontconfig-config version 2.8.0-3ubuntu1 required, but 2.8.0-3ubuntu2 is available
outdated debug symbol package for libdbus-1-3: package version 1.4.12-4ubuntu2 dbgsym version 1.4.6-1ubuntu6.1
libcups2 version 1.5.0-2 required, but 1.5.0-5 is available
fontconfig version 2.8.0-3ubuntu1 required, but 2.8.0-3ubuntu2 is available
libc-bin version 2.13-16ubuntu4 required, but 2.13-17ubuntu2 is available
libffi6 version 3.0.10~rc8-6 required, but 3.0.11~rc1-1 is available
gcc-4.6-base version 4.6.1-7ubuntu1 required, but 4.6.1-7ubuntu2 is available
outdated debug symbol package for libgtksourceview-3.0-0: package version 3.1.2-0ubuntu1 dbgsym version 3.0.0-0ubuntu1
outdated debug symbol package for libgssapi-krb5-2: package version 1.9.1+dfsg-1ubuntu1 dbgsym version 1.8.3+dfsg-5ubuntu2.1
gedit-common version 3.1.3-0ubuntu1 required, but 3.1.4-0ubuntu1 is available
outdated debug symbol package for liblaunchpad-integration-3.0-1: package version 0.1.54 dbgsym version 0.1.51
gedit version 3.1.3-0ubuntu1 required, but 3.1.4-0ubuntu1 is available
outdated debug symbol package for libkrb5support0: package version 1.9.1+dfsg-1ubuntu1 dbgsym version 1.8.3+dfsg-5ubuntu2.1
outdated debug symbol package for libthai0: package version 0.1.15-2 dbgsym version 0.1.14-2ubuntu1
libstd...

Read more...

tags: removed: need-i386-retrace
Revision history for this message
Curtis Hovey (sinzui) wrote :

I submitted a patch upstream.

Changed in gedit (Ubuntu):
status: Invalid → Triaged
Changed in gedit:
status: New → Fix Released
Revision history for this message
Sebastien Bacher (seb128) wrote :

the issue has been fixed in git and will be in Oneiric with the next GNOME update

Changed in gedit (Ubuntu):
status: Triaged → Fix Committed
importance: Undecided → High
importance: High → Low
Revision history for this message
Vadim Rutkovsky (roignac) wrote :

Can't reproduce in Gedit 3.3.2

Changed in gedit (Ubuntu):
status: Fix Committed → Fix Released
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.