crashes when closing file too soon after save (gedit crashed with signal 7 in g_main_context_dispatch())

Bug #522100 reported by Delan Azabani
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gedit
Fix Released
Medium
gedit (Ubuntu)
Fix Released
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gedit

When saving a file in gedit, I often press ^S, then ^W or ^Q quite quickly, so much in fact that I don't even release the control key. If I close or quit too soon after saving a file, gedit saves successfully, then hangs for about five seconds and crashes. Apport soon informs me of the crash.

gedit 2.29.6
Lucid

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Mon Feb 15 19:42:56 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/gedit
NonfreeKernelModules: nvidia
Package: gedit 2.29.6-0ubuntu1
ProcCmdline: gedit /home/username/www/busbook/index.php
ProcEnviron:
 LANG=en_AU.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-13.18-generic
Signal: 7
SourcePackage: gedit
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/libgio-2.0.so.0
 g_main_context_dispatch ()
 ?? () from /lib/libglib-2.0.so.0
 g_main_loop_run () from /lib/libglib-2.0.so.0
Title: gedit crashed with signal 7 in g_main_context_dispatch()
Uname: Linux 2.6.32-13-generic x86_64
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare tape video

Revision history for this message
Delan Azabani (azabani) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 query_info_cb (source=<value optimized out>, res=<value optimized out>,
 ?? () from /usr/lib/libgio-2.0.so.0
 g_main_context_dispatch ()
 ?? () from /lib/libglib-2.0.so.0
 g_main_loop_run () from /lib/libglib-2.0.so.0

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
Delan Azabani (azabani)
visibility: private → public
Changed in gedit (Ubuntu):
status: New → Confirmed
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for your bug report. This bug has been reported to the developers of the software. You can track it and make comments here: https://bugzilla.gnome.org/show_bug.cgi?id=611013

summary: - gedit in Lucid crashes when closing file too soon after save (gedit
- crashed with signal 7 in g_main_context_dispatch())
+ crashes when closing file too soon after save (gedit crashed with signal
+ 7 in g_main_context_dispatch())
Changed in gedit (Ubuntu):
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
status: Confirmed → Triaged
Revision history for this message
Ignacio Casal Quinteiro (nacho-resa) wrote :

It seems that some dbg packages are missing for the stacktrace. i.e glib.

Revision history for this message
Sartor (sartorua) wrote :

I have same problem. It appears after update to 2.29.9-0ubuntu2.

Changed in gedit:
importance: Unknown → Medium
status: Unknown → Fix Released
Revision history for this message
Victor Vargas (kamus) wrote :

According to upstream tracker this issue was solved in development branch a long time ago, so marked as fixed.

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