On Wednesday 27 October 2004 03:45, Anders Johansson wrote:
On Wednesday, 27 October 2004 02.07, Phil Burness wrote:
pburness Oct 27 01:00:34 desktop k3b: resmgr: server response code 500 then more of above followed by Oct 27 01:00:34 desktop k3b: resmgr: server response code 502 Oct 27 01:00:34 desktop resmgr[1307]: disconnect from pburness Oct 27 01:00:34 desktop resmgr[1307]: accepted connection from user pburness Oct 27 01:00:34 desktop resmgr[1307]: disconnect from pburness Oct 27 01:00:34 desktop kernel: Device not ready. Make sure there is a disc in the drive. then more of the accept - disconnect stuff with server response code 502 & 501 and more of the Device not ready messages
This all looks perfect to me, just as it should be (I'm assuming there really isn't a disc in the drive). But you still can't see the device as a writer in k3b? That is weird. Are you sure you haven't changed anything else about the system? I only use apt to upgrade / update and here are the last entries from the apt.log
Sat 23 Oct 2004 16:33:56 BST;upgrade;xpdf;2.02pl1-89 => 2.02pl1-141 Sat 23 Oct 2004 16:33:56 BST;upgrade;libtiff;3.5.7-307 => 3.5.7-376 Sun 24 Oct 2004 09:06:12 BST;install;xcdroast;0.98alpha14-44 Tue 26 Oct 2004 12:36:42 BST;upgrade;tetex;2.0.2-76 => 2.0.2-199 Tue 26 Oct 2004 12:36:42 BST;upgrade;aaa_base;9.0-7 => 9.0-10 As can be seen the only packages loaded since 25th when things where working are aaa_base and tetex. The only other thing that happened is that I rebooted into vmlinux-2.4.21-243 but that breaks my wireless connection so I rebooted back into vmlinux-2.4.21-99 could this have an effect? Phil