I tried upgrading to Hardy, and only partially succeeded -- the system is the notorious Dell Optiplex 320, and I couldn't get Hardy's 2.6.24 kernel to boot on it; consequently, I'm now using a mostly-Hardy system with Gutsy's 2.6.22 kernel. This affects VirtualBox too, because it needs kernel modules; I couldn't find or compile kernel modules for the new VBox with the old kernel, so I'm using VBox from Gutsy too.
I'm telling you this sordid story, because testing the network-bridge set-up is an effort; given the peculiar state of the system, is it worth it (just to make sure -- this is not a rhetorical question)? I'm hoping, based on https://bugs.launchpad.net/ubuntu/+source/linux/+bug/138305, that Intrepid's 2.6.27 kernel will be able to boot here, and then I'll be able to try again. Oh, and as mentioned above, the host is Kubuntu, the guest is (always) Windows XP. Obviously, the kioslaves problem is only in the host. Thanks for your attention, Shai. -- Installing a network bridge broke kioslaves https://bugs.launchpad.net/bugs/198458 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdepim in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
