the way those informations are added usually is to open a new bug and to
close it as duplicate after it has been processed by the retracing tools
--
gedit crashes while editing. Gives Segmentation fault
https://bugs.launchpad.net/bugs/419683
You received this bug notification because you are a me
@Sebastien Bacher: "the process outlined above will automatically open a
new bug report"
That is not true. After apport uploaded my crash file, I was asked to
check if my issue was not already reported. And it was. Are you
suggesting I should have opened a duplicated bug? That doesn't sound
right
don't attach crash files to bug they are made to be sent using apport so
they can be retraced correctly
** Attachment removed: "_usr_bin_gedit.1000.crash"
http://launchpadlibrarian.net/34969012/_usr_bin_gedit.1000.crash
--
gedit crashes while editing. Gives Segmentation fault
https://bugs.lau
Guys, it would be nice to automatically attach the .crash file to the
exiting issue when I run ubuntu-bug some.crash so that we don't have to
wait for the crash file to be uploaded twice.
** Attachment added: "_usr_bin_gedit.1000.crash"
http://launchpadlibrarian.net/34969012/_usr_bin_gedit.1000
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
Reinstalling gtklib2.0 seems to have resolved this issue.
--
gedit crashes while editing. Gives Segmentation fault
https://bugs.launchpad.net/bugs/419683
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu
