Public bug reported:
Binary package hint: gedit
When opening a file that gives a 'read error' gedit hangs. The window is
non-responsive, but can be closed (force close), but the gedit process
remains. It will use 100% CPU, and, worse, cannot be TERM'ed, KILL'ed or
STOP'ped.
This happened to me twice when opening a text file on a (faulty) CD (two
different CD's). The only solution I have found is a re-boot. The fact
that gedit is the default for opening text files in Ubuntu does not help
here (this is why it happened twice to me), although normally I have no
quarrels with gedit at all.
IMHO, this situation should *NEVER* occur. Read errors, although not
frequent nowadays, do happen and are no reason for your program (or
system) to go insane. (I am working now with my laptop fan blaring
loudly due to the CPU load. The thing is getting hot on my lap too...)
I would *expect* any process that gets read errors on a file, to catch
them and give a nice, short, apologetic message to the user about not
being able to read the file. Perhaps a choice like 'Ignore', or 'Abort'
would be useful.
Here are the info thingies:
Description: Ubuntu 8.04.1
gedit:
Installed: 2.22.3-0ubuntu1
My system was upgraded from Feisty (and from Gutsy, IIRC).
(I'm off for a reboot now...)
** Affects: gedit (Ubuntu)
Importance: Undecided
Status: New
--
gedit hangs (hogs CPU) on read error
https://bugs.launchpad.net/bugs/280947
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
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
