I've been unable to determine if this is really fixed or not as there's
no changelog evidence, regardless, I cannot repro it and jaunty is no
longer supported, so I'm invalidating.
** Changed in: gnome-terminal (Ubuntu)
Status: Fix Committed => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/309884
Title:
deleting a module that is in use locks up terminal
Status in “gnome-terminal” package in Ubuntu:
Invalid
Bug description:
Binary package hint: gnome-terminal
I tried to delete a module but forgot to rmmod it first. The instance
of gnome-terminal I was using became unresponsive. I opened up
another terminal and tried to kill -9 the frozen bash process; this
caused the second terminal to freeze as well. Then I used xkill to
kill both terminals--it seemed to work, but I could not open a new
terminal after that. Also, I could no longer switch to a tty shell
using Ctrl-Alt-Fkey. I tried to reboot at this point, and it reported
that "Terminal" was not responding. The reboot process froze before X
could be shut down.
Now, I know what you're thinking; I shouldn't try to delete a module
that's in use. It was an accident, but it should have resulted in an
error message rather than rendering bash useless and requiring a hard
reboot.
Ubuntu 8.10
gnome-terminal 2.24.1.1-0ubuntu1
The module I tried to delete was gspca_ov511.ko.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/309884/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
