gedit crashed with SIGSEGV in IA__g_slist_remove()

[Marco Rodrigues]

Binary package hint: gedit

Just opened an php file in command-line.

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/gedit
NonfreeKernelModules: nvidia
Package: gedit 2.25.7-0ubuntu1
ProcCmdline: gedit index.php
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_US.UTF-8
Signal: 11
SourcePackage: gedit
StacktraceTop:
 IA__g_slist_remove (list=0x93286b0, data=0x93286a8)
 ?? ()
 IA__g_datalist_clear (datalist=0x9563060)
 g_object_finalize (object=0x9563058)
 gtk_text_buffer_finalize (object=0x9563058)
Title: gedit crashed with SIGSEGV in IA__g_slist_remove()
Uname: Linux 2.6.28-8-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin plugdev sambashare scanner video

[Apport retracing service (apport)]

StacktraceTop:IA__g_slist_remove (list=0x93286b0, data=0x93286a8)
g_proxy_drive_update (drive=0x93286a8, iter=0x9738480)
IA__g_datalist_clear (datalist=0x9563060)
g_object_finalize (object=0x9563058)
gtk_text_buffer_finalize (object=0x9563058)

[Sebastien Bacher (seb128)]

Thanks 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=573771

[Sebastien Bacher (seb128)]

upstream bug question

"Is i reproduceable? Can you ask for a valgrind log? Does it happens if all
plugins are disabled? If it doesn't happen, can you pinpoint the problematic
plugin?"

could you reply to those questions?

[Marco Rodrigues (gothicx)]

I can't reproduce it.. it happened one time or two, it didn't reproduced always, so if It happen again, I could report it.

My active plugins are only two: Modelines and Save without trailing space.

[Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount)]

We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

[Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount)]

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!