it will not duplicate, it will open a new bug with extra details
--
gEdit segfaults on x86_64
https://bugs.launchpad.net/bugs/353793
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
This bug affect lucid too..
How to duplicate:
- Create a new empty file on the desktop (right click - create empty document)
exemple - test.txt
- Double click on the file - gedit crash / same thing happen if you open this
file from gedit
I got this line in /var/log/messages:
May 6 08:49:39
I submit my .crash file
** Attachment added: _usr_bin_gedit.1000.crash
http://launchpadlibrarian.net/47916136/_usr_bin_gedit.1000.crash
** Changed in: gedit (Ubuntu)
Status: Invalid = New
--
gEdit segfaults on x86_64
https://bugs.launchpad.net/bugs/353793
You received this bug
don't add .crash to the bugs this way they can contain informations you
don't want to add there and are meant to be sent by ubuntu-bug not to be
added manually this way
** Changed in: gedit (Ubuntu)
Status: New = Invalid
** Changed in: gedit (Ubuntu)
Assignee: Ubuntu Desktop Bugs
Ok sorry i didn't knew... Do you need that i fill a new bug gedit
crashed with SIGSEGV in g_utf8_validate() with ubuntu-bug tool (double
click to my .crash file) ? because will be a duplicate with this one..
--
gEdit segfaults on x86_64
https://bugs.launchpad.net/bugs/353793
You received this
** Summary changed:
- Segfault
+ gEdit segfaults on x86_64
--
gEdit segfaults on x86_64
https://bugs.launchpad.net/bugs/353793
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
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
