We are closing this bug report as it lacks the information, described in
the previous comments, we need to investigate the problem further.
However, please reopen it if you can give us the missing information and
don't hesitate to submit bug reports in the future.
** Changed in: gedit (Ubuntu)
You didn't have it turned on at the crash time since it has no info on
the crash, see http://wiki.ubuntu.com/DebuggingProgramCrash then if you
want to get a stracktrace by hand
** Changed in: gedit (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a
Yeah, I DID use apport and submitted this all automatically. What else
do you want me to do?
** Changed in: gedit (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/7
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 automat
** Tags added: apport-collected
** Description changed:
Binary package hint: gedit
about 12 files open, all with changes unsaved, opened a new file, then all
the unsaved files were gone.
from error log:
Mar 31 15:52:39 4720z kernel: [68293.043574] gedit[20745]: segfault at 8ca ip
005
