gedit crashed with SIGSEGV in g_closure_invoke()

Bug #261534 reported by Nathan
This bug report is a duplicate of:  Bug #84306: Crash on closing active tabs. Edit Remove
32
This bug affects 4 people
Affects Status Importance Assigned to Milestone
gedit
Expired
Critical
gedit (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gedit

I just selected a sftp volume in the open file dialog (but I had done this before, so it maybe that is not the cause of the crash)

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/gedit
NonfreeKernelModules: ath_hal
Package: gedit 2.23.90-0ubuntu1
ProcAttrCurrent: unconfined
ProcCmdline: gedit
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=nl_BE.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: gedit
StacktraceTop:
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 g_closure_invoke ()
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_signal_emit_valist ()
 g_signal_emit () from /usr/lib/libgobject-2.0.so.0
Title: gedit crashed with SIGSEGV in g_closure_invoke()
Uname: Linux 2.6.26-5-generic x86_64
UserGroups: adm admin audio cdrom dialout dip floppy fuse kvm libvirtd lpadmin plugdev sambashare video

Tags: apport-crash
Revision history for this message
Nathan (nathansamson) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:IA__g_closure_invoke (closure=0x1ca4c60, return_value=0x0, n_param_values=2,
signal_emit_unlocked_R (node=0x1cb0a10, detail=0, instance=0x2690880,
IA__g_signal_emit_valist (instance=0x2690880, signal_id=<value optimized out>,
IA__g_signal_emit (instance=0x2, signal_id=1956542320, detail=0)
IA__gtk_widget_size_allocate (widget=0x2690880, allocation=<value optimized out>)

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
Pedro Villavicencio (pedro) wrote :

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

Changed in gedit:
assignee: nobody → desktop-bugs
status: New → Triaged
Changed in gedit:
status: Unknown → New
Changed in gedit:
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

could you ask the questions on the upstream report? otherwise this report is going to be also closed.

Changed in gedit (Ubuntu):
status: Triaged → Incomplete
Changed in gedit:
status: Incomplete → Invalid
Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don\'t hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.

Changed in gedit (Ubuntu):
status: Incomplete → Invalid
Changed in gedit:
importance: Unknown → Critical
status: Invalid → Expired
Revision history for this message
Sasa Paporovic (melchiaros) wrote :

I have mark this as duplicate of

https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/965543

,because the code base has properly changed in whole since this report arised.

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.