It should be fixed in gedit 3.10, see
https://bugzilla.gnome.org/show_bug.cgi?id=584803#c7
This version is a part of Ubuntu 14.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/360591
Title:
Crash
** Changed in: gedit
Status: New = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/360591
Title:
Crash when doing a replace all: gedit crashed with SIGSEGV in
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
Is this bug still affecting people with Gedit 3.3.x?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/360591
Title:
Crash when doing a replace all: gedit crashed with SIGSEGV in
** Changed in: gedit
Importance: Unknown = Critical
--
Crash when doing a replace all: gedit crashed with SIGSEGV in
gtk_text_iter_set_offset()
https://bugs.launchpad.net/bugs/360591
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Just got the same crash. In my case, I was opening two huge (~7MB each)
SQL dumps simultaneously (I wanted to perform a diff). I didn't interact
at all with gedit, as far as I can tell, the SQL dumps where being
opened/parsed by gedit when the crash occurred.
--
Crash when doing a replace all:
Just for information, here is my last comment on the bugzilla tracker:
I have perform the test with the same data on 3 other platforms since the bug
report:
1. - latest Ubuntu Karmic Koala (future 9.10) 32bit
2. - latest Ubuntu 9.04 32bit
3. - latest Ubuntu 8.04.2 LTS 32bit
The crash has
I have the same issue, also with a WordPress database dump trying to do
the same type of prefix replacement.
--
Crash when doing a replace all: gedit crashed with SIGSEGV in
gtk_text_iter_set_offset()
https://bugs.launchpad.net/bugs/360591
You received this bug notification because you are a
Thank you for sending the bug to GNOME
** Changed in: gedit (Ubuntu)
Status: New = Triaged
--
Crash when doing a replace all: gedit crashed with SIGSEGV in
gtk_text_iter_set_offset()
https://bugs.launchpad.net/bugs/360591
You received this bug notification because you are a member of
Adding a reference to the upstream bug in Gnome Bugzilla system
** Bug watch added: GNOME Bug Tracker #584803
http://bugzilla.gnome.org/show_bug.cgi?id=584803
** Changed in: gedit
Importance: Undecided = Unknown
** Changed in: gedit
Status: New = Unknown
** Changed in: gedit
** Changed in: gedit
Status: Unknown = New
--
Crash when doing a replace all: gedit crashed with SIGSEGV in
gtk_text_iter_set_offset()
https://bugs.launchpad.net/bugs/360591
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Could somebody having the issue send the bug the to the people writting
the software (https://wiki.ubuntu.com/Bugs/Upstream/GNOME)?
** Also affects: gedit
Importance: Undecided
Status: New
--
Crash when doing a replace all: gedit crashed with SIGSEGV in
gtk_text_iter_set_offset()
Hello Sebastien,
I have installed the following package:
sudo apt-get install libgtk2.0-0-dbgsym=2.16.1-0ubuntu2
sudo apt-get install libgtksourceview2.0-0-dbgsym=2.6.1-0ubuntu1
Then I have run once more the test, you can find attached the stacktrace.
NB: gedit crashed once more, I have the final
** Changed in: gedit (Ubuntu)
Status: Incomplete = New
--
Crash when doing a replace all: gedit crashed with SIGSEGV in
gtk_text_iter_set_offset()
https://bugs.launchpad.net/bugs/360591
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
could you install the gtk and gtksourceview debug packages and get a new
stacktrace?
--
Crash when doing a replace all: gedit crashed with SIGSEGV in
gtk_text_iter_set_offset()
https://bugs.launchpad.net/bugs/360591
You received this bug notification because you are a member of Ubuntu
Bugs,
do you mean that it is a launchpad feature that will analyse the
coredumped, create a backtrace from it, delete the coredumped and then
will make public the bug report? That's a great feature!
right, the making public part is not automatic though, somebody has to
check that the stacktrace has no
Hello Sebastien,
You can find attached here the backtrace of gedit during the crash.
About the retracer, do you mean that it is a launchpad feature that will
analyse the coredumped, create a backtrace from it, delete the coredumped and
then will make public the bug report? That's a great
I forgot to mention that gedit has been updated but I still have the
bug, here is my current version of gedit: 2.26.1-0ubuntu1
--
Crash when doing a replace all: gedit crashed with SIGSEGV in
gtk_text_iter_set_offset()
https://bugs.launchpad.net/bugs/360591
You received this bug notification
The next time I'm home and using my computer, I will try to reproduce the bug
and generate a stack trace that is usable for you and that does not contain
sensitive information.
One note though, if you have a wordpress blog, try to export the entire
wordpress database (only the wordpress related
Sorry, I had to remove the core dump as it contains information from the file I
opened. And there are e-mails and other stuff that I do not want to publish.
In case you want the core dump, you will have to request it directly to me, and
I will try to clean it before sending it.
** Visibility
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please try to obtain a backtrace following the
instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload
the backtrace (as an attachment) to the bug report. This will greatly
help us in tracking down
the apport bugs are private by default and nobody has access to the
coredump until retracing, the retracer provides a debug stacktrace and
clean the coredump while doing so, you broke the retracing by cleaning
the bug yourself though so it would be nice if you could get a
stacktrace and add it
22 matches
Mail list logo