we don't try to avoid the bug report but only apport bugs are registred
in the crash database used for autoduplication and debug retracing so
it's better if crashes are reported this way
--
gedit unable to open a file in which the filename includes apostrophe
https://bugs.launchpad.net/bugs/21612
And could you rather not to try to find excuses to avoid the bug report?
The bug can be easily reproduced by just following the bug description I
gave initially... And as far as I know, the *.crash file is just plain
text.
Anyway, can you check Bug #220693?
--
gedit unable to open a file in whic
Could you rather use apport to send the crash?
** Attachment removed: "_usr_bin_gedit.1000.crash"
http://launchpadlibrarian.net/13385860/_usr_bin_gedit.1000.crash
** Attachment removed: "_usr_bin_gedit.1000.crash"
http://launchpadlibrarian.net/13386014/_usr_bin_gedit.1000.crash
** Change
** Attachment added: "_usr_bin_gedit.1000.crash"
http://launchpadlibrarian.net/13386014/_usr_bin_gedit.1000.crash
--
gedit unable to open a file in which the filename includes apostrophe
https://bugs.launchpad.net/bugs/216129
You received this bug notification because you are a member of Ubun
This is what I get when I run it from the command line:
** (gedit:6176): CRITICAL **: Could not execute ctags: Text ended before
matching quote was found for '. (The text was 'ctags -n
--fields=-k-f-s-t+K+l+n -f - /home/jwm/it's a shame.txt')
sys:1: Warning: g_path_get_basename: assertion `file_n
