[03:35] highvoltage, got my first Qimo 2.0 packages built! [14:01] so Scratch doesn't look to be in the repos, anybody have suggestions on something I can use in place of eToys? [14:38] highvoltage, ping === joerg__ is now known as joerg [22:50] I am playing with wiimote whiteboard stuff at the moment [22:50] it would be rather good to get it packaged for Ubuntu [22:52] it is a python app, with a few dependencies, all in the repos [22:53] http://github.com/pnegre/python-whiteboard [22:54] there is also this one http://www.stepd.ca/gtkwhiteboard/ [22:55] I will have a go at packaging it at some point in the next few weeks [22:55] but I am a bit of a newbie to the whole packaging thing. If anyone wants to help that would be great. [22:57] I think it would be amazing if someone could install Ubuntu, install the whiteboard app and then with a wiimote and a projector and a £10 IR pen have an interactive whiteboard [22:59] As been a while I wanted to test that though haven't had the chance yet [22:59] at this point, it's extremely unlikely something new enters Lucid as we have our Feature Freeze on Thursday but it's clearly something we should look at, east least for Lucid+1 [23:01] AlanBell: did those apps work for you? [23:13] alkisg: I just did a test with VBox, it booted just fine ... [23:14] stgraber: hmm... except for that vbox problem, I also have a problem with tftpd-hpa not starting at boot. [23:14] stgraber: what settings do you use in vbox? [23:14] networking / pae etc? [23:15] alkisg: I used the usual one, bridged using the VT extension of my CPU, PAE enabled + 3D graphic [23:15] alkisg: http://pastebin.com/f69a74c92 [23:15] * alkisg shrugs... I can reproduce the problem here 100% - removing nbd-proxy make it work, reinstalling it make it halt [23:16] alkisg: can you try: ltsp-update-image --arch i386 -n [23:16] I'm wondering if that's my use of -n that solves the issue ;) [23:16] (as it had fixed quite a lot of stability issue for me in the past) [23:17] trying... [23:17] (btw do you see any speed difference with -n? ) [23:18] not really no, it's using slightly more bandwidth and less CPU but that's about it [23:18] though most squashfs issues I had sometime, completely vanished once I started using -n [23:18] hi, for the wii whiteboard i found some packages which did not work. they claim to have a problem with the bluetooth stack of bluez [23:19] following seems to work (last post with download) http://code.google.com/p/linux-whiteboard/issues/detail?id=22 [23:23] stgraber: nah, the same [23:23] bs=1024, sz=537016, and then hangs [23:25] alkisg: can you boot without nbd-proxy, then do: [23:25] - nbd-proxy 2000 2000 [23:25] - nbd-client /dev/nbd1 127.0.0.1 2001 [23:25] - mkdir -p /mnt/test [23:25] - mount /dev/nbd1 /mnt/test [23:25] With break=mount ? [23:25] something should fail at some point doing that [23:26] alkisg: nope, just boot the thin client as usual and do that from the shell [23:26] ok [23:26] it won't disconnect the existing nbd connection so it shouldn't be a problem [23:26] btw I also tried with your client (.xml), no difference [23:28] * alkisg also notes that he's using the default generic-pae kernel... (i386) [23:29] I'm on Lucid amd64 on my laptop (where the VM was running), actual thin client is an Intel Atom one with 512MB of RAM and gigabit network to the server [23:29] I have 10 or so of them at the office running on Lucid, some as thin client, some as fat. All with the latest packages from my PPA [23:31] nbd-proxy 10.160.31.10 2000 2000 [23:31] Hangup [23:32] From syslog: Feb 14 01:32:29 alkis nbd_server[11106]: Read failed: Inappropriate ioctl for device [23:33] alkisg: interesting, that's lucid 32bit right ? [23:33] Yup [23:33] I'll get you a debug version then, hang on a sec [23:35] alkisg: http://www.stgraber.org/download/nbd-proxy [23:35] alkisg: make it executable and run it with: ./nbd-proxy 10.160.31.10 2000 2000 2> debug.log [23:36] you should then have a full debug log in debug.log [23:36] stgraber: I tried again the same line (with the original nbd-proxy) and it worked! [23:36] hmm, something is really wrong then ... [23:36] so running the same thing two times failed the first time and worked the second ? [23:36] Yes [23:37] Let me reboot and test it again... [23:38] Yes, again the same thing [23:38] (so a quick fix would be to run it twice :P) [23:38] ok, putting the debug version... [23:38] does it die the first time ? [23:38] it's supposed to fork into background [23:38] so you would have to check with "ps aux" [23:39] It just says "Hangup" - I didn't look at ps [23:39] The second time, it doesn't fork to the background [23:39] It just waits - I thought it woulnd't fork.. [23:39] hmm, ok, so it's actually behaving as it should ... [23:40] it's supposed to fork and say "hangup" (I don't remember why the "hangup") [23:40] and if it's already running, then it'll hang until the previous instance is killed [23:40] (as it can't listen twice on the same port) [23:40] Ah [23:40] Yeah, I see it on the processes list [23:40] what's happening if you do that nbd-client ? [23:41] Error: cannot open NBD: No such file or directory [23:41] Please ensure the 'nbd' module is loaded. [23:41] with: nbd-client /dev/nbd1 127.0.0.1 2001 [23:42] my bad [23:42] nbd-client 127.0.0.1 2001 /dev/nbd1 [23:42] that should work better [23:42] Error: Connect: Connection refused [23:42] should that be 2001 or 2000? [23:43] yeah ... seems like I'm half-asleep and it's not even late here ... :) [23:43] with 2000 it connects but I get a whole lot of errors [23:43] what kind of error ? [23:43] Buffer I/O error on device nbd1, logical block 1 [23:44] nbd1: Attempted send on closed socket [23:44] oh, interesting [23:44] is nbd-proxy still running ? [23:44] Uh, ok, pressing ctrl+z / bg to check... [23:45] Yes, it is [23:45] ok, then I'm going to need some debug info I guess ;) [23:45] nbd-client died though. I rerun it and now it hanged on "Negotiation:" [23:45] restart the VM to get the kernel in a sane state [23:45] stgraber: I can also give you vnc access if you want... [23:46] alkisg: that'd be great [23:46] I usually do it with x11vnc -connect, but you'd need vncviewer -listen and a port forwarding for that, any other ideas? [23:47] Ah, silly me [23:47] Sorry, I'll just port forward 5900