gedit crashes when opening an empty file
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gedit (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: gedit
gedit crashes when opening an empty file.
1. create an empty file by right-clicking on the file browser and choosing 'create document' then 'empty file'.
2. double-click on the file to open
3. gedit runs and crashes immediately (The gedit window disappears).
I tried in the terminal as well and got the following message.
$ gedit anEmptyFile
(gedit:14929): GLib-GIO-CRITICAL **: g_converter_
Segmentation fault
I'm using Ubuntu Linux 10.04 (Lucid Lynx) Desktop (64bit). It's upgraded from 9.10.
The version of gedit is 2.30.2.
$ lsb_release -rd
Description: Ubuntu 10.04 LTS
Release: 10.04
$ apt-cache policy gedit
gedit:
Installed: 2.30.2-0ubuntu1
Candidate: 2.30.2-0ubuntu1
Version table:
*** 2.30.2-0ubuntu1 0
500 http://
100 /var/lib/
2.
500 http://
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: gedit 2.30.2-0ubuntu1
ProcVersionSign
Uname: Linux 2.6.32-22-generic x86_64
Architecture: amd64
Date: Sun May 9 06:22:39 2010
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
ProcEnviron:
LANG=en_AU.utf8
SHELL=/bin/bash
SourcePackage: gedit
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.