gedit crashed with SIGSEGV in g_type_check_instance()

Bug #256108 reported by Vicente Ruiz
8
Affects Status Importance Assigned to Milestone
gedit (Ubuntu)
Incomplete
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gedit

When I clicked two times over a python file on nautilus, gedit crashed it. Immediately, I tried again and gedit worked fine.

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/gedit
NonfreeKernelModules: nvidia
Package: gedit 2.23.1-0ubuntu2
ProcAttrCurrent: unconfined
ProcCmdline: gedit file:///home/username/gsyvo/gsyvo.py
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: gedit
StacktraceTop:
 g_type_check_instance ()
 g_signal_emit_valist ()
 g_signal_emit () from /usr/lib/libgobject-2.0.so.0
 ?? ()
 ?? () from /usr/lib/libgio-2.0.so.0
Title: gedit crashed with SIGSEGV in g_type_check_instance()
Uname: Linux 2.6.26-5-generic x86_64
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev sambashare video

Tags: apport-crash
Revision history for this message
Vicente Ruiz (uve) wrote :
Revision history for this message
Vicente Ruiz (uve) wrote :

I don't know if this bug is the same that #244292.

Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:IA__g_signal_emit_valist (instance=0x207d20, signal_id=257, detail=0,
IA__g_signal_emit (instance=0x207d20, signal_id=257, detail=0)
model_iterate_children_cb (file=<value optimized out>,
complete_in_idle_cb (data=0x1fef8c0)
IA__g_main_context_dispatch (context=0x1b04d70)

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in gedit:
importance: Undecided → Medium
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for your bug report. A new version of the package has been uploaded, could you try if you still get the issue and attach a new crash file if that's the case?

Changed in gedit:
assignee: nobody → desktop-bugs
status: New → Incomplete
Revision history for this message
Juan Pablo Salazar Bertín (snifer) wrote :

I found a way to reproduce this bug, I'll try to reproduce it with the new version.

snifer@snifer-laptop:~$ dmesg > dmesg.txt
snifer@snifer-laptop:~$ mkdir somedir
snifer@snifer-laptop:~$ cp dmesg.txt somedir/
snifer@snifer-laptop:~$ gedit somedir/dmesg.txt
snifer@snifer-laptop:~$ rm -r somedir/
snifer@snifer-laptop:~$ gedit dmesg.txt

** (gedit:7690): WARNING **: Could not get info for file:///home/snifer/somedir: Error stating file '/home/snifer/somedir': No such file or directory

(gedit:7690): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(gedit:7690): GLib-GObject-CRITICAL **: g_signal_emit_valist: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed

Revision history for this message
Juan Pablo Salazar Bertín (snifer) wrote :

Unfortunately it's still present in version 2.23.3-0ubuntu1. Reported as bug #257803.

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.