Red Hat Bugzilla – Bug 5565
gedit crashed when started with an argument
Last modified: 2013-04-02 00:13:34 EDT
If gedit is started with a file as an argument (eg. "gedit
/etc/sendmail.cf"), it exits immediately with a core dump
(after the gnome application crash dialog)
*** Bug 5587 has been marked as a duplicate of this bug. ***
When opening a text file from gmc (in this case fstab)
right-clicking on it & choosing open with gedit the app
(gedit) crashes with a segmentation fault. It does not crash
if you open gedit first then load the text file into it.
0x403da4e1 in __kill () from /lib/libc.so.6
this is an annoying but minor bug
*** Bug 5856 has been marked as a duplicate of this bug. ***
gEdit crashes everytime you try to start it
*** Bug 6102 has been marked as a duplicate of this bug. ***
Giving gedit a file name on the command line causes gedit to
crash. Invoking gedit, then opening the file works.
I've reproduced this both on a machine upgraded from 6.0 and
a machine freshly installed.
*** Bug 6333 has been marked as a duplicate of this bug. ***
when the default editor is gedit the edit voice of the
right click menu of gmc causes a segmentation fault of gedit
------- Additional Comments From email@example.com 10/25/99 14:46 -------
This sounds very much like the bug I submitted, #5565
*** Bug 6525 has been marked as a duplicate of this bug. ***
I have been able to make GEdit crash on my fresh RH 6.1
install by doing various things. I had no problems under RH
6.0. All crashes are Seg Faults and core is dumped.
1) Opened a file, copied some text, pasted the text, opened
the search dialog, canceled the search operation, hit the
print button, hit OK and it crashes.
2) Checking some options in the settings menu causes GEdit
3) Opening the Settings->Preferences dialog and making any
change followed by either Apply or OK will cause GEdit to
Dell Dimension XPS R400
Intel PII 400Mhz
Both starting gedit with an initial argument and opening a file with gedit from
within gmc seems to work with gedit 0.6.0
*** Bug 8387 has been marked as a duplicate of this bug. ***
This has been fixed in October GNOME.