[08:53] ogra: I think I found a hint as to why your image won't load in KVM: when booting it shows as both a DVD drive and a regular drive. Is the image perhaps partitioned somehow? === asac_ is now known as asac [11:17] hello [11:17] persia: hello [11:18] persia, Err http://archieve.ubuntu.com intrepid/main linux-image-2.6.27-4-generic 2.6.27-4.5 [11:18] 404 Not Found [IP: 91.189.88.46.80] [11:18] " [11:19] i just got that from a user trying the workaround ... do you notice something ? [11:24] hmm, no, its all correct, he must have fiddled with the sources.list himself to get that typo in [12:46] persia, my image isnt partitioned btw, i use the script build-mobile-img StevenK uses on cdimage [12:46] so i dont see wha mine wouldnt boot but his does [12:47] *why [13:00] hmm [13:00] might be that cdimage builds in a hardy envionemnt [13:00] Ah too bad amitk isn't around [13:00] http://article.gmane.org/gmane.linux.kernel.wireless.general/21379 [13:00] * ogra tries running syslinux for his image in a hardy chroot [13:01] lool, did you try it ? [13:02] Nope, but at least it feel like we could use madwifi + new hal in linux-lpia rather than building a lrm [13:02] neh, would have been helpful if they had put a changelog in the tar.bz2 [13:18] crevette: Hi. superm1 and I tested your 0.28 preparation in a variety of environments. It works great, unless we use the 2.6.27 kernel. [13:18] superm1 is working on packaging 1.5: if this tests cleanly, we may use that. [13:19] lool: Would you mind taking a look at http://paste.ubuntu.com/51200/ ? It is supposed "hildonisation" for the bluez-gnome preferences applet. Personally, I think it's probably an improvement generally rather than only in hildon, but I'd like your opinion as someone more familiar with GTK+. [13:20] ogra: If you're using the same script then I'm also confused. Do you see any difference building under hardy? Also, you probably want to grab the new version of the script, that fixes the no-kernel-is-being-installed issue. [13:21] ogra: Additionally, the reason people are seeing that 404 error is that their apt-cache is out of date. They need to run apt-get update. [13:21] persia: Did you see the URL? http://archieve.ubuntu.com intrepid/main [13:22] well, since they are downloading and install manually i just put a direct url in a blog comment now [13:22] StevenK, must be a typo in the copy/paste though, the sources.list in the image and the preseed are both fine [13:22] Ooh. I didn't see that. Maybe a preseeding issue? [13:22] i checked that [13:23] Ah. RIght. Let's call that a reporter typo then. [13:23] persia, and hardy doesnt help it seems [13:23] ogra: Hrm. I dunno. The images I get from StevenK work everywhere. Your image gives strange results in KVM, and won't boot on the D4. It works fine on the SR. [13:24] yeah, i see the qemu issue here as well [13:24] but using the hardy syslinux definately doesnt change a thing [13:24] ogra: Also, if you haven't seen already, I updated the -mobile preseeding bug with all the useful details, after some discussion in ubuntu-installer. You probably need to fiddle ubuntu-mobile-default-settings though. [13:25] yeah, gdm-cdd.conf currentl relies on ubuntu as username and no password [13:29] ogra: What else do you have customised? d-i passwd/auto-login will sedify gdm.conf to do the right thing. [13:30] right [13:31] gdm-cdd.conf uses the theme i use in the desktop and the face browser [13:31] Ah. I wonder if user-setup apply can handle gdm-cdd.conf. [13:32] Anyway, you can't effectively force the username except in --automatic mode, which you don't really want, as there's no reason -mobile should br crippled like that. [13:32] i dont really like to force any kind of typing in gdm though [13:32] unless i have any kind of onscreen kbd [13:33] Right. That's why I'm suggesting d-i passwd/auto-login : it will automatically log in *whichever* username the user selects in the installer. [13:33] but you wont get back in if you log out [13:33] it doesnt set timed login and doesnt set userlist [13:34] both is needed [13:34] Hmm... [13:34] autologin only works on first login, for the second timed login is required as well [13:34] What's the use case for logging out? [13:34] touchscreen recalibration [13:35] heh, fun there is denemo for maemo :) [13:35] Maybe that doesn't have quite so many bugs. [13:36] it seems to use timidity [13:36] ogra: Also, with the announcement of GNOME Mobile, what do you think about aligning Ubuntu Mobile with that base? [13:36] i guess its an older version [13:36] ?? [13:36] mid is aliged with that [13:36] Hrm? [13:36] -mid is hildon. [13:36] i dont want hildon in -mobile [13:36] Neither do I. [13:36] Gnome Mobile isn't Hildon [13:36] gnome-mobile *is* hildon [13:36] No. [13:37] Maemo is hildon. GNOME Mobile is different. [13:37] well, matchbox and friends at least [13:38] The block diagram I see is BlueZ, e-d-s, Telepathy, Avahi, GStreamer, Matchbox, GCon, SQLite, GCVF, GIO, Pango, Cairo, ATK, GTK*, GLib, and DBus. [13:39] I *don't* see hildon-desktop, or any of that sort of thing. [13:39] well, apart from matchbox and telepathy ubuntu-mobile has exactly all components [13:40] From that set, Ubuntu Mobile uses almost all of it: the only pieces absent are that Telepathy wasn't selected for intrepid, and you're hinting compiz/metacity, rather than using matchbox. [13:40] Am I missing something important? [13:40] nope [13:40] well, gvfs instead of gnome-vfs (which is dead) [13:41] Yeah. Where I wrote "GCVF" I meant to write "GVFS" [13:41] i was commenting the diagram :) [13:41] Oh :) [13:41] So I was thinking it might be handy to claim "Ubuntu Mobile is based on GNOME Mobile". [13:42] But that requires consensus that it actually is :) [13:42] * ogra wonders when he manages to have hiw 2G SD card filled with crap in the n800 ... i'm installing apps since yesterday :P [13:42] 2G is insufficient space. [13:42] well, i'D like to go on claiming that it is based on gnome desktop but it incorporates gnome mobile technology [13:43] it uses nearly the complete set of gnome desktop apps [13:46] OK. That makes sense. GNOME Mobile claims it is the basis of Ubuntu Mobile, and I like to reciprocate, but I can see the value in claiming GNOME Desktop as well. [13:46] For -mid, I think Maemo is the sensible upstream, so perhaps it's GNOME Mobile -> Maemo -> Ubuntu MID. [13:46] thats the important part to me ... i want the apps to work on 600 vertical pixels (minus 48px panel) [13:47] Right, and that is a long-standing GNOME Desktop requirement: holding them to it makes sense. [13:47] xactly [13:51] persia: Hmm the patch changed slightly since last time I saw it; I'm pretty sure it's not hildon dependent, but UI reorg [13:51] I know the OEM people had trouble packing everything on screen in bluetooth dialogs [13:51] lool: It's entirely UI reorg. If the GTK+ looks clean to you, I'm thinking of pressing for it to be the default, rather than "hildon". [13:52] Yeah, 1.5 has a *much* cleaner interface, and is compatible with our kernels. Needs a heap of testing to be included though. [13:52] perhaps this patch can now be made upstream then [13:53] It was longer in the past, had more dialogs and all [13:53] * lool needs to go afk [13:53] That's what I'm thinking, but since it's the first time I've every written in GTK, I want someone else's opinion :) [13:55] I remember reviewing the changes in depth, but it's hard to comment on them as a patch as it depends on the affected widgets/code [13:55] ogra-maemo: Like your N800? :) [13:55] yeah, love it [13:56] lool: OK. Is this something you can do later, or shall I hunt another GTK master? [13:56] the font is quite small in xchat [13:58] persia: I think you're trying our the bluez packages regularly? would be nice to apply the patch and see if it still improves the UI and send it upstream [13:58] How stupid, my screen speakers are now shut off when the screen goes in power suspend mode [13:58] lool: OK. I'll find another GTK Master. Thanks as always. [13:59] * lool goes back to cleaning [14:00] ogra-maemo, meep [14:00] hmm, no sounds [14:00] ogra-maemo, meep [14:00] ogra-maemo, again [14:01] ogra-maemo, pfft [14:01] ogra-maemo: Does it help if someone else does it, or is it just broken? [14:01] ah, no libnotify [14:01] i guess i have to configure a wav file for sounds and the ballon thngie only wiorks with libnotify installed [14:02] * ogra-maemo goes looking for the pkg [14:10] Hmm. In today's MID image, midbrowser doesn't launch. [14:48] Hmm NM seems to think the ath5k wifi on the Q1U is a wired network interface [14:50] did you try dis/enable wireless from the context menu ? [14:51] ogra-maemo: There's no such thing, because it doesn't recognize it as a network interface [14:51] ogra-maemo: What was last time you checked ath5k on Q1U? 2.6.26? [14:52] It might work if we fix hal [14:52] I could tell if I'd plug a kbd [14:53] i tried with .27 [14:53] it recognized it corrently but all connect attempts failed [14:53] *correctly [14:54] i think the last time was with .27-2 [14:54] * ogra needs to go to mow the lawn ... semms its the last sunny day for quite some time ... back later [14:59] lool: Do you think bug #275158 needs to be on the release list? [14:59] Launchpad bug 275158 in xfree86-driver-synaptics "Please enable a build for lpia" [Undecided,New] https://launchpad.net/bugs/275158 [15:02] Hi all. A question on the necessary hardware to run the mid image on. I am currently running ubuntu 7.10 on a Fuyitsu Siemens Stylus 3400 (Pentium III). Since it is a tablet-pc, I am wondering whether I could run the mid version of ubuntu on it as well. [15:02] Btw. it has only 4MB graphics memory, no 3D accel. [15:02] rhp: How much RAM? [15:02] 192MB [15:03] It'd be tight. You could try. I think you'd do best to use the mccaslin image, and make sure that the -lpiacompat kernel is installed. [15:04] Mind you, ubuntu-mid is really designed for > 200DPI, so things will look a bit chunky. [15:04] ogra-maemo: It fails to connect here as well; ISTR the driver only supports WEP at this time though [15:04] And I'm using WPA [15:05] I should check with some other AP and open access [15:05] cant be, i'm using WEP all over my house [15:05] persia: It shouldn't be a release blocker [15:05] ogra: Do you get any packets in monitor mode? [15:06] lool: Oh well. It's trivial to fix, but I'm not sure if tjaalton or bryce will want to fix it if it's not a release blocker. [15:06] well, would be good to have synaptics (touchpads wont work without it, hal-input defaults to it for all touchpads) actually and its a trivial change [15:06] lool, i didnt try [15:06] i will if i'm back ... really out now ... [15:06] And my D4 (form factor device) has a synaptics touchpad. [15:07] persia: I could fix it as well I guess? [15:08] lool: If you have the git-fu, indeed. [15:08] I do [15:09] lool: Well then, thanks :) [15:09] ogra: I don't see any packets [15:10] persia: what does McCaslin indicate? Is that a code name for versions of ubuntu-mid? [15:11] How reliable are the intrepid test versions? Reliable enough, or should I really stick with the released hardy version? [15:11] rhp: For the Ubuntu MID hardy release, there were four things released. One was called "mccaslin" and was optimised for the Samsung Q1U. It most likely to be compatible with most hardware. The others were "menlow", optimised for some development boards, a KVM image, and a Moblin-Image-Creator project tarball. [15:12] rhp: If you want to play with the development snapshots, you can grab a daily from http://cdimage.ubuntu.com/ubuntu-mid/intrepid/current/ [15:13] I read on the web-site there is also a 'regular' i386 version. [15:13] But I don't see images for that. [15:13] That should work, and if it doesn't, try installing the -lpiacompat kernel in a chroot, and try that. [15:14] Ok, I'll try. [15:14] There's no images available for the i386 version of ubuntu-mid, and there's *heaps* of bugs because some changes were made architecture-specific that weren't. [15:14] There's a preview image of ubuntu-mobile available for i386, but I'm not sure how well it works with 192MB RAM. [15:14] ok then, the mccaslin image it is. Thanks. [15:15] What are the development snapshots targetted at? [15:15] You mean, what sort of devices? [15:16] Yes [15:17] There seems to be only one version, so no destinction between mccaslin and menlow. [15:17] Well, I know it's been tested in KVM, on the Aigo MID, on the Samsung Q1U, on the Kohjinsha SR, and on the Sharp D4. [15:17] persia: fixed [15:17] persia: You might need Pas support though [15:17] lool: Excellent. Yeah, I'll send that as soon as I notice the upload is accepted. [15:17] No it's fine [15:17] %xfree86-driver-synaptics: !s390>------->------->------->------- # Needs xserver-xfree86 [15:18] persia: I built the source from a debian box, so didn't close the lp bug in the changes, but I closed the bug by hand [15:18] Oh good. StevenK said it was in P-a-s, but didn't say it didn't need support. I'll just expect the D4 sidebar to work for tomorrow's image then. [15:18] lool: No problem. I don't really care about changelog-closes-bug for this last-minute architecture-enablement stuff. [15:20] rhp: There shouldn't be anything device-specific in the development snapshot images (if there is, it's a bug). Whether all the features are working properly or not is a different issue. [15:25] persia: ok, clear enough. I'll give it a spin and find out for myself. [15:27] rhp: Please let us know how it works. [15:27] Sure [16:41] hello persia [16:42] hey crevette. Have you tried superm1's test packages? [16:42] yep [16:42] not entirely [16:42] but there is no bluez-utils 4.x ? [16:45] Just install bluetooth, bluez, and bluez-gnome: it should take care of everything else. [16:46] weird that bluez 4.7 is not installed [16:46] crevette: You've added the bluetooth PPA to your sources.list ? [16:46] yep [16:46] okay, installing bluetooth solvd the problem [16:47] OK. Good :) [16:47] nice if we can have bluez 4 for intrepid [16:47] I have an error install bluez [16:48] Des erreurs ont été rencontrées pendant l'exécution : [16:48] /var/cache/apt/archives/bluez_4.7-0ubuntu1~ppa2_i386.deb [16:48] E: Sub-process /usr/bin/dpkg returned an error code (1) [16:48] sorry for the french [16:48] I thought superm1 fixed that. [16:48] purge bluez-input, bluez-audio, bluez-serial, and bluez-network [16:51] I had a shitful of errors also about makedev === asac_ is now known as asac [16:57] Yeah. Ignore those. They need to be sorted, but they don't break anything. [16:57] Also. [16:57] !ohmy [16:57] Please watch your language and topic to help keep this channel family friendly. [17:00] ah [17:00] :) [17:00] sorry [17:01] bluetooth-wizard is nice [17:03] Yeah. It actually works too :) [17:04] bluetooth-sendto doesn't work for me [17:04] it keeps stalled with an error of obex-data-server [17:04] Oh, right. superm1 was going to look at that today: I think he said it might need obexd. [17:06] obex-data-server doesn't work no more with bluez 4 ? [17:06] Dunno. You might ask superm1 for more explanation in #ubuntu-motu [17:07] I did a little keyboard testing, and am hacking the UI patch for the preferences dialog to not look so bad at 600 vertical pixels. [17:26] persia: I didn't get the comment https://mail.google.com/mail/#inbox/11ca06991d3a9b81 [17:26] oups [17:26] not this one [17:27] Yeah. I can't read that :) [17:27] https://bugs.launchpad.net/ubuntu/+source/bluez-utils/+bug/274950/comments/9 [17:27] Launchpad bug 274950 in obex-data-server "Look into switching to bluez 4.x" [Undecided,In progress] [17:27] he wants to build the package with the patch ? [17:28] Yep, and push to the PPA for people to test. [17:28] More specifically, he's asking if you have time to build a package with the patch for testing. [17:28] okay [17:28] I'll try [17:29] crevette: Good luck. [17:29] If you run into issues, just ask for superm1 on #ubuntu-motu, and he'll probably be able to help. I'm likely to be away soon, and for a while :) [17:29] okayish [20:37] ok. this is probably to stupid to ask, but I could not find an anwser on the wiki. Here goes: how should I put the image on a usb stick to make it boot ubuntu-mid? cat xxx.img > /dev/sdb? [21:17] Is it true that booting the usb.img will overwrite my disk on the target system? [21:17] If so, I surely missed that big fat red warning sign that indicated as much...