** Changed in: gedit
Status: New => Fix Released
** Changed in: gedit
Importance: Unknown => Critical
--
gedit crashed with SIGSEGV in IA__g_list_last()
https://bugs.launchpad.net/bugs/401934
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a
** Branch linked: lp:ubuntu/gtk+2.0
--
gedit crashed with SIGSEGV in IA__g_list_last()
https://bugs.launchpad.net/bugs/401934
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
h
The entry for gedit is not actually the gedit package in Ubuntu, but
rather the upstream entry for this issue in gedit. We don't have control
about that status.
Upstream, however, did mark this bug as fixed. Unfortunately there seems
to be a problem with Launchpad, making it unable to read the ups
I'm not familiar enough with the way the bugs are closed in launcpad,
but if the fix was released in the gtk source, shouldn't it be also
changed in the gedit status as well?
--
gedit crashed with SIGSEGV in IA__g_list_last()
https://bugs.launchpad.net/bugs/401934
You received this bug notificati
The issue is fixed in karmic now
** Changed in: gtk+2.0 (Ubuntu)
Status: Triaged => Fix Released
--
gedit crashed with SIGSEGV in IA__g_list_last()
https://bugs.launchpad.net/bugs/401934
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug ass
I found Scribes as a good alternative editor, until gedit works again.
--
gedit crashed with SIGSEGV in IA__g_list_last()
https://bugs.launchpad.net/bugs/401934
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing l
I've launched gedit to modify some configuration files.
It start, open the file and then crash immediatly.
In the shell the output is: Segmentation fault (core dumped)
karmic koala alpha 4
--
gedit crashed with SIGSEGV in IA__g_list_last()
https://bugs.launchpad.net/bugs/401934
You received this
Not necessarily the first line , but i'v tried several times for
different file sizes , its when the cursor is in any line >15th line.
[this is not even constant , when a file is larger , then the acceptable
line changes! for some files it crashes for >24 lines!]
To play it safe i mention first li
** Description changed:
Binary package hint: gedit
Trying to open a python script. It worked one time but crashes on any
subsequent attempt.
+
+ The crash happens *consistently , mainly* for files which are several lines
of text and have been edited previously by the user profile.
+ The
On 08/26/2009 05:04 PM, -RAX- wrote:
> It only crush if the file is longer/bigger than a certain file and there
> is no window open.
>
> To skip the crush, u can open an empty file or a small file then open
> the large one. This make me think the problem is somehow related to the
> file size while
It only crush if the file is longer/bigger than a certain file and there
is no window open.
To skip the crush, u can open an empty file or a small file then open
the large one. This make me think the problem is somehow related to the
file size while creating the GUI.
--
gedit crashed with SIGSEG
It's become so frequent I've installed and begun using leafpad as a
simpler alternative to nano.
--
gedit crashed with SIGSEGV in IA__g_list_last()
https://bugs.launchpad.net/bugs/401934
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
same here when opening .rc files
--
gedit crashed with SIGSEGV in IA__g_list_last()
https://bugs.launchpad.net/bugs/401934
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
http
it seems to affect me too. i created a text document on the desktop,
then every time i tried to open it by double clicking it, gedit crashed.
when i opened gedit using the terminal an THEN clicked it, it opened
alright. when i closed gedit and double-clicked the file again, it still
works.
--
ged
** Changed in: gtk+2.0 (Ubuntu)
Importance: Medium => High
--
gedit crashed with SIGSEGV in IA__g_list_last()
https://bugs.launchpad.net/bugs/401934
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
deskt
hmm
'sudo gedit /etc/apt/sources.list' crashes
but I was able to sudo gedit the valgrind log
heres my logfile
** Attachment added: "valgrind.log"
http://launchpadlibrarian.net/30476368/valgrind.log
--
gedit crashed with SIGSEGV in IA__g_list_last()
https://bugs.launchpad.net/bugs/401934
You
Here is my valgrind log. as mentioned early in comment 13, running with
G_DEBUG=gc-friendly does not crash the gedit, so I had to run it without
it.
the steps I did are:
$ sudo -i
# G_SLICE=always-malloc valgrind -v --tool=memcheck --leak-check=full
--num-callers=40 --log-file=valgrind.log gedit
the upstream developers need a valgrind log of the new crashes, may
someone still having the issue provide one? the instructions on how to
get one are available here: https://wiki.ubuntu.com/Valgrind ; Please
attach that resulting file to the report later, if you have any
questions regarding that
bug 413710 and 413690 are duplicates of the same crash with libgtk2.0-0
2.17.7-0ubuntu3; reopening.
** Changed in: gtk+2.0 (Ubuntu)
Status: Fix Released => Triaged
--
gedit crashed with SIGSEGV in IA__g_list_last()
https://bugs.launchpad.net/bugs/401934
You received this bug notification
> gedit will still crash whenever I run
could you open a new bug using apport and the new gtk?
--
gedit crashed with SIGSEGV in IA__g_list_last()
https://bugs.launchpad.net/bugs/401934
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
-
after updating, gedit will still crash whenever I run:
gksudo /etc/hosts
for example. It never loads the file. It will load files that I don't
need to be root to access. I didn't get an Apport bug report window so
I am reporting it here.
--
gedit crashed with SIGSEGV in IA__g_list_last()
htt
This bug was fixed in the package gtk+2.0 - 2.17.7-0ubuntu3
---
gtk+2.0 (2.17.7-0ubuntu3) karmic; urgency=low
* debian/patches/090_git_change_fix_gdk_crash.patch:
- git change to fix a lot of gdk crashes in firefox and gedit for example
(lp: #404423, #401934)
-- Sebastie
this has been fixed upstream with the following commit:
http://git.gnome.org/cgit/gtk+/commit/?id=9f822431970b9744f0184ae2d9e9977f607ffe4e
** Changed in: gtk+2.0 (Ubuntu)
Status: Triaged => Fix Committed
--
gedit crashed with SIGSEGV in IA__g_list_last()
https://bugs.launchpad.net/bugs/40
The problem is that gedit remembers the cursor position for each file
*by name*. If you rename the file to something else then gedit treats it
as a new file and sets the cursor position to a "safe position", If you
rename it back and try to load it, gedit tries to use the cursor
position saved for
gedit opening a text file named "Linux Notes". Oddly enough, if I rename
it to any else - "Windows Notes", "sams Notes", it opens ok. If then I
rename it once again to "Linux Notes" it fails?!
--
gedit crashed with SIGSEGV in IA__g_list_last()
https://bugs.launchpad.net/bugs/401934
You received t
a workaround for this is:
-First , open a file which has *not* been edited.
-now open the file which causes the crash.[opens in a new tab] no crashes now.
--
gedit crashed with SIGSEGV in IA__g_list_last()
https://bugs.launchpad.net/bugs/401934
You received this bug notification because you are a
kaervos is right, this doesn not happen with files which have not been
edited , crash happens only with files that have been edited.
--
gedit crashed with SIGSEGV in IA__g_list_last()
https://bugs.launchpad.net/bugs/401934
You received this bug notification because you are a member of Ubuntu
Desk
A little further information:
It seems this has something to do with restoring the state of the
document, and scrolling the document to the last location.
This should be able to be reproduced by anyone by disabling line
wrapping in gedit, entering a few very long lines, then exiting/saving
while
Thanks you kaervos, I've added a comment upstream with the information.
--
gedit crashed with SIGSEGV in IA__g_list_last()
https://bugs.launchpad.net/bugs/401934
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing
Installed debug gtk libraries and ran again
** Attachment added: "valgrind-logs-gedit_gtk-dbg.tar.gz"
http://launchpadlibrarian.net/29673804/valgrind-logs-gedit_gtk-dbg.tar.gz
--
gedit crashed with SIGSEGV in IA__g_list_last()
https://bugs.launchpad.net/bugs/401934
You received this bug notif
** Changed in: gtk+2.0 (Ubuntu)
Milestone: None => ubuntu-9.10-beta
--
gedit crashed with SIGSEGV in IA__g_list_last()
https://bugs.launchpad.net/bugs/401934
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing
Could you get a valgrind log with libgtk2.0-0-dbg installed?
--
gedit crashed with SIGSEGV in IA__g_list_last()
https://bugs.launchpad.net/bugs/401934
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
deskto
To further back borrell's case, running gedit under valgrind using the
instructions at https://wiki.ubuntu.com/Valgrind for some reason allows
gedit to run normally.
If I launch gedit directly I can get it to crash every time, but the
"G_DEBUG=gc-friendly" stops gedit from crashing for some reason
I ran Valgrind quite a few times, but try as I might I couldn't get
gedit to crash :/
Here's the log anyway. Maybe someone else can get ti to crash
** Attachment added: "valgrind.log"
http://launchpadlibrarian.net/29647438/valgrind.log
--
gedit crashed with SIGSEGV in IA__g_list_last()
https
Could somebody having the issue run gedit under valgrind with the
instructions: https://wiki.ubuntu.com/Valgrind and attach that resulting
file to the report? Thanks in advance.
** Package changed: gedit (Ubuntu) => gtk+2.0 (Ubuntu)
--
gedit crashed with SIGSEGV in IA__g_list_last()
https://bug
Same as TechDude3177, crashing when opening plaintext files
--
gedit crashed with SIGSEGV in IA__g_list_last()
https://bugs.launchpad.net/bugs/401934
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop
I have the same thing but gedit crashs and the file is just a plain text
file
--
gedit crashed with SIGSEGV in IA__g_list_last()
https://bugs.launchpad.net/bugs/401934
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs ma
** Changed in: gedit
Status: Unknown => New
--
gedit crashed with SIGSEGV in IA__g_list_last()
https://bugs.launchpad.net/bugs/401934
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lis
Thanks for the backtrace Andreas, the other one was missing afunction
that might be important to figure out how to fix the crash, I've sent
this upstream at: http://bugzilla.gnome.org/show_bug.cgi?id=589367
** Bug watch added: GNOME Bug Tracker #589367
http://bugzilla.gnome.org/show_bug.cgi?id=
** Tags removed: need-i386-retrace
--
gedit crashed with SIGSEGV in IA__g_list_last()
https://bugs.launchpad.net/bugs/401934
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
ht
** Tags added: need-i386-retrace
--
gedit crashed with SIGSEGV in IA__g_list_last()
https://bugs.launchpad.net/bugs/401934
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
http
Same here. I attempted to run after a fresh boot with the same crash.
code:
quagm...@quagmire-desktop:~$ sudo gedit /etc/pulse/default.pa
[sudo] password for quagmire:
Segmentation fault (core dumped)
quagm...@quagmire-desktop:~$
/code
However, it doesn't crash all the time.
If I open Text Edi
** Changed in: gedit (Ubuntu)
Status: Incomplete => New
--
gedit crashed with SIGSEGV in IA__g_list_last()
https://bugs.launchpad.net/bugs/401934
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desk
** Attachment added: "movemembers.py"
http://launchpadlibrarian.net/29356949/movemembers.py
--
gedit crashed with SIGSEGV in IA__g_list_last()
https://bugs.launchpad.net/bugs/401934
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
-
Pedro, what Is wrong with the Traces that apport attached automatically?
They include debugging symbols and should be enough for a quick glance.
(Not the retracer ones, they are obviously broken)
Anyway, attaching new backtrace.
It happens only with this one script, attaching it to this report. I
Thanks for your bug report. Please try to obtain a backtrace
http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the
bug report. Are you using a plugin could you test to disable it and try
to reproduce the bug again? May you tell us a few easy steps in order to
reproduce it or it ju
46 matches
Mail list logo
