I've since upgraded to edgy and can't reproduce the bug anymore.
Gedit gets mightily slow when opening that file but it doesn't crash
anymore. (With slow I mean that it can take up to a minute to repaint
the screen after alt-tabbing away and back again).
But I guess that is a different issue and
You have been subscribed to a public bug:
Binary package hint: gedit
On a standard ubuntu 6.06 installation, gedit crashes after opening a
largish xml file (200kb). The crash usually causes X to restart,
sometimes the machine hangs and a hard boot is required
steps to reproduce:
from terminal,
This is similar to http://bugzilla.gnome.org/show_bug.cgi?id=144726
--
nautilus stops copying files if it encounters 2 files that differ only by case
and the target filesystem is case insensitive
https://launchpad.net/bugs/52348
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
I can confirm this bug with a floppy disk as copy target.
It's not always predictable which files get copied and which don't, but
the copy process is aborted halfway without warning to the user.
I think this bug can lead to data loss: e.g. you may be led to believe
you backed up a large number
I forgot to mention that I'm using Dapper
--
nautilus stops copying files if it encounters 2 files that differ only by case
and the target filesystem is case insensitive
https://launchpad.net/bugs/52348
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
Public bug reported:
Binary package hint: gedit
On a standard ubuntu 6.06 installation, gedit crashes after opening a
largish xml file (200kb). The crash usually causes X to restart,
sometimes the machine hangs and a hard boot is required
steps to reproduce:
from terminal, do
gedit
Dean, the page you linked explains how to get a debug deb, which I now
have, but it doesn't explain how to get a backtrace. Could you please
explain that part?
--
gedit crashes X on large xml file
https://launchpad.net/bugs/53337
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
