← Back to team overview

desktop-packages team mailing list archive

[Bug 829044] Re: gedit crashed with SIGSEGV

 

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

** Changed in: gedit (Ubuntu)
   Importance: Undecided => High

** Changed in: gedit (Ubuntu)
   Importance: High => Low

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/829044

Title:
  gedit crashed with SIGSEGV

Status in Light-Weight Text Editor for Gnome:
  Fix Released
Status in “gedit” package in Ubuntu:
  Fix Committed

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/gedit/+bug/829044/+subscriptions