gedit regularly crash up on save

[Slavutinskiy Victor]

Binary package hint: gedit

On save gedit crash up and break down, without saving really.

ProblemType: Bug
Architecture: amd64
Date: Wed Mar 24 10:52:07 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/gedit
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
NonfreeKernelModules: nvidia
Package: gedit 2.29.9-0ubuntu2
ProcEnviron:
 LANGUAGE=ru_RU:ru:en_GB:en
 PATH=(custom, no user)
 LANG=ru_RU.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-9.152-rt
SourcePackage: gedit
Uname: Linux 2.6.31-9-rt x86_64
XsessionErrors: (polkit-gnome-authentication-agent-1:4475): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a '.crash' file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

 If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

 If you are using Ubuntu with the Gnome desktop environment - launch nautilus and navigate to your /var/crash directory and double click on the crash report you wish to submit.

 If you are using Kubuntu or Xubuntu you can file the crash using /usr/share/apport/apport-qt --crash-file=/var/crash/_my_crash_report.crash in a terminal - where _my_crash_report.crash is the crash you would like to report.
 I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.

[Slavutinskiy Victor (vitosnet)]

It impossible to do the thing You ask. After all updates it still says that bug report could not be send because packages

initscripts, klibc-utils, libblkid1, libc-bin, libc6, libcomerr2, libglib2.0-0, libgssapi-krb5-2, libgtk2.0-0, libgtk2.0-common, libk5crypto3, libklibc, libkrb5-3, libkrb5support0, libuuid1, libxi6, libxrandr2, mount, sysv-rc, sysvinit-utils, util-linux

has old versions.

All I can say that it happened only with files with WINDOWS-1251 encoding and there is new files with names like

.goutputstream-1BIX9U or .goutputstream-CZLR9U in file directoty. Some of them include parts of original files, some empty.

[Sebastien Bacher (seb128)]

Could yoy try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem?

Having an example of file triggering the crash would be useful too

[Slavutinskiy Victor (vitosnet)]

Yes, it partially possible.

[Slavutinskiy Victor (vitosnet)]

This is source file.

[Sebastien Bacher (seb128)]

do you still get the issue? the gdb log has neither debug symbols not a stacktrace, you need to type "backtrace" to get one

[Slavutinskiy Victor (vitosnet)]

No, after updates and reinstallations bug is gone. Thank You.

[Launchpad Janitor (janitor)]

[Expired for gedit (Ubuntu) because there has been no activity for 60 days.]