It seems to be possible to bring down the system without a reset, switch to a virtual terminal and press Ctrl+Alt+Del, the machine gets down to a blinking line in the top left corner, press Ctrl+Alt+Del again to sync the disks and reboot the system. Apparently, the file systems are not messed up this way.
During reboot, when killing NetworkManager (has to be terminated, it refuses to exit during regular shutdown procedures), it prints the following message: NetworkManager: <WARN> nm_hal_deinit(): libhal shutdown failed - Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Still "works" with: linux-restricted-modules 2.6.24.17.19 gnome-system-monitor 2.22.1-0ubuntu2 although now you have to look at the "Resources" tab in the monitor to crash the system. -- gnome-system-monitor crashes when wifi (fwlanusb) statistics are queried https://bugs.launchpad.net/bugs/222213 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
