=== asac_ is now known as asac [01:01] so anyone know how to enable card reader on acer aspire one ? [01:18] pururu: the right hand side does not work..the left works [01:18] at least for me [01:18] no..i don't know why [01:19] are you seeing the same thing? [01:24] dunno... i think they both dosnt work... and i dont need left one [01:25] i want to backup something and make fresh install from release image [01:28] back up to a pen drine? [01:29] s/drine/drive [01:30] * pururu goes to shop to buy one more usb stick. why i got this SD card lol. i cant boot from it, and cant write to it... [01:40] ha ha [01:40] pururu: what happens when you put the caard in ..nothing? [01:41] exactly [01:41] maybe you need to mount it? [01:42] it dosnt show in fdisk -l too [01:44] [ 5249.232063] mmc0: new SD card at address 1234 [01:44] [ 5249.234652] mmcblk0: mmc0:1234 SA01G 995328KiB [01:44] but i see this in dmesg [01:45] mmm [01:45] this is for right side slot [01:50] mmm [01:50] * pururu calling for linux hackers to save a world [01:53] pururu, nice! your sd card is working [01:53] woohoo [01:53] pururu, sudo fdisk -l /dev/mmcblk0 [01:53] yeah it show something [01:55] pururu, paste the output to http://paste.ubuntu.com/ [01:58] ok i created partition with gparted and mounted it, it work [01:58] still need to paste this? [01:58] cool! [01:58] nope [01:58] thanks for your help [01:59] you're welcome ;-) [01:59] ;-) [02:01] but i'm not sure this will work on fresh ubuntu... cuz i made few changes to enable card reader... as described on ubuntu aspire one site [02:01] like setpci one time yesterday... and writing something to fstab [02:02] i just not seen any result [02:03] pururu, i guess you will not need to make these changes [02:03] it seems so [03:03] how can i add a password protected bluetooth device with the new bluetooth manager [03:37] putz...https://bugs.edge.launchpad.net/ubuntu/+source/bluez-gnome/+bug/284994 [03:37] Launchpad bug 284994 in bluez-gnome "bluetooth-wizard unable to pair headset" [Undecided,New] [03:39] * ian_brasil clicks the nice new affects me button [10:19] hello there [10:33] Good morning crevette [10:38] hello persia [10:39] good evening (?) persia [10:39] Yeah, it's evening here :) [10:59] * ogra yawns [11:11] * ogra wonders why -mid changes tty's on each restart of X [11:11] * persia suspects an openvt race [11:12] its weird [11:12] initially its on tty1 [11:12] after the first restart its on 7 [11:12] after the second its on 9 [11:12] and then it jumps between 7 and 9 with each restart [11:13] It takes the first available VT. [11:14] It starts before getty, so gets tty1 when it starts. [11:14] Then, when restarting, it starts before it finishes, so takes tty7. [11:14] hmm, no gconf dbon mid ? [11:14] * ogra thought he could pull the icon theme name from some gconf key [11:15] When it really finishes, getty takes over tty1, so the next time, it needs a different one. [11:15] tty8 is taken by usplash, so it gets 9. [11:15] then back to 7 because 7 is free from the previous X death, etc. [11:15] There should be a gconf db [11:15] usplas shuld have called /etc/init.d/usplash start to free it up at the end of booting [11:16] tty8? [11:17] That's where the console log goes. Unredirecting that means either not showing it, or redirecting somewhere else. [11:17] # Clear VT 8 of any console messages [11:17] clear >/dev/tty8 [11:17] # ask usplash to go away [11:17] usplash_write QUIT [11:17] thats from the usplash_quit function [11:17] which is called by /etc/init.d/usplash start [11:18] it does more stuff like actually killing leftover usplash processes and switch to vt1 [11:18] hunh. Where does /dev/console point after that? [11:18] tty1 i think [11:19] Maybe that doesn't work because X has tty1? [11:19] yeah [11:19] which is not usual [11:19] anyway, the missing gconf db is more weird than the tty jumping [11:20] i ony have toplevel dirs in gconf editor [11:20] but not a singe key [11:20] *single [11:21] That's very odd, because kourou uses gconf to determine the current category. [11:21] gconf ? [11:21] no [11:22] it uses xdg [11:22] and the theme is hardcoded [11:23] so there is no dependency at all on gconf ... i was about to add one :) [11:23] thats why i looked in gconf-editor [11:23] err [11:23] ignore me [11:24] the theme in gconf-editor is weird ... it doesnt show the little expander arrows and my doublecliks on the folders were not strong enough [11:25] there we go ... /desktop/gnome/interface/icon_theme [11:26] that should be the last bit of icon theme things we need ... [11:27] * ogra fixed rendering completely already and we have a fallback to the gtk-missing icon if no icon is found now [11:28] switching from gtk.Iconview to gtk.Table might be harder though [11:29] does it make sense to have a context menu in kourou ? [11:31] i.e. do many target devices of -mid ave the ability to right click ? [11:45] My tablet has right click. Also, most touch devices support right-click by long-touch. The Zaurus uses that for context. [11:45] Personally, I think it'd be cool if the context menu could include a means of adjusting Home, either by adding or removing icons. [11:46] yeah [11:46] i thought of adjusting home, changing background and opening the theme capplet [11:46] later probably a "create launcher" [11:56] great, icon theme from gconf works [12:00] * ogra pushes to his dev branch [12:01] * ogra scratches head about a redraw function ... i'm getting tired of restarting X somehow [12:07] Perhaps a reload function? [12:08] yeah, thats what i meant [12:08] Just implement it as a quit function for the plugin, and make sure hildon-desktop can be given a restart hint in the .desktop file. [12:08] but externally triggerable [12:09] Why would you want it externally triggerable? [12:11] because i could write external tools like a kourou-icon-theme-selector ... that wouldnt have to sit in the app itself (but be called from context menu) and after an icon change it can trigger a reload [12:11] same for a wallpaper selector [12:11] Don't do that in kourou [12:11] both are things you dont need permanently in ram [12:11] Get hildon-desktop to accept external triggers that restart a given plugin. [12:12] That's generally resuable for everything. [12:12] might exist already [12:13] hmm, apparently not [12:14] all references google knows point to restart hildon-desktop completely [12:14] "or restart your device" [12:14] woah [12:15] Right : implementing something like that in hildon-desktop would be a big help generally. [12:15] It's not just for reload, but having a way to be able to kill a stuck app. [12:15] but i'm currently not in C mood [12:16] so i'll look at other kourou stuff first [12:17] switching iconview to table will be big :/ [12:17] but i'D love to play with wallpaper things :( [12:33] gah [12:33] gdk_pixbuf_new_from_file_at_scale() isnt ported to pygtk [12:33] grmbl [12:44] ogra: you just need to port it :) [12:44] crevette, as i said above, not in C mood today :) [12:45] * crevette doesn't understand c :) [12:46] * ogra does but wants to play python ... its weekend, so what i do is for having fun ;) [12:49] actually I'm fighting with a patch I want to achieve, and which me make crazy because of warning during compilation :) [12:49] I wonder why the project I'm interested with are in C [12:49] projects [14:08] hello guys === root is now known as Guest95875 === Guest95875 is now known as ido- [14:10] was wondering whats the difference between MID and mobile versions [14:14] which should i choose for my samsung Q1 [14:31] ido-, I'd recommend the UMPC image for your samsung Q1 : it's had a fair bit of testing on that platform, and works fairly well. [14:31] MID is for smaller things, like the Aigo MID, Sharp D4, etc. [15:57] thanks [15:57] downloaded it [15:58] tryin to getit to boot [16:37] downloaded the latest build of umpc from yesterday [16:37] tried to boot it on my Q1 [16:37] and it stops at initramfs [16:37] no error [16:50] hrm. [16:54] Q1 or Q1U? [16:58] Q1U [16:58] should i use an older build [16:59] or is it not supposedto wokr [17:01] persia ? [17:02] No, it's supposed to work. I've heard from a couple Q1U owners that it worked. [17:02] hrm. [17:02] so i'll download an older build [17:02] Where does it get stuck? [17:02] which do you recommend ? [17:02] No, you want the released build. [17:02] well, it starts showing the ubuntu loading bar thingy [17:03] Does it get about 15-20% along? [17:03] and then stops, and goes into busybox/initramfs prompt [17:03] That's rather unexpected. [17:03] Anyone else around have a Q1U? [17:05] seems no one is here [17:06] Or at least nobody paying attention right now. [17:06] THis is repeatable? [17:06] or that. [17:06] every time I try to boot..? [17:06] That sounds repeatable. [17:07] Which image did you download? [17:07] sec [17:08] ubuntu-umpc.img [17:09] cant find the exact link since ubuntu is down [17:09] http://cdimage.ubuntu.com/ubuntu-umpc/intrepid/current/ubuntu-umpc.img ? [17:09] well, at least the cd-download server [17:09] yes [17:09] actually, the build from the 10/30 [17:09] Hrm. That's the recommended image : I wouldn't expect any other to work better. [17:10] i used dd for windows [17:10] to put it on the a usb stick [17:10] That should work. [17:10] with bs=1024 [17:11] it did boot anyhow. [17:11] i'll boot it in a minute [17:11] and i'll dmesg [17:11] see what errors it shows [17:11] Sounds like a good plan. [17:18] question [17:18] can i make it boot without the ubuntu bar ? [17:18] so i could see progress on the console [17:19] hrm [17:19] weird [17:19] re-written the image with bs=512 [17:19] and now it loaded... [17:23] 1024 is the usually recommendation, but I'm glad to hear 512 worked for you. [17:24] To boot without splash, use "nosplash" as a boot argument, but if it boots perhaps you don't need that. [17:24] yes [17:24] indeed [17:24] how do i calibrate the screen [17:25] I think it's system...Administration...Calibrate Screen [17:26] doesnt work [17:26] ogra, Any advice? [17:26] says "no evtouch capablee device found" [17:27] That's very confusing for the Q1U, because the guy who put together the calibration tool has one. [17:28] hrm. who is he ? [17:55] persia ? [18:40] persia, the recommended image isnt a daily build but the released one :P [18:41] ogra, Isn't that the release build for umpc? [18:41] see topic ;) [18:41] i think there was a 30.1 or .2 build [18:41] It went to releases! I thought it was only going to cdimage. [18:41] because the livefs was borked in the pre last one [18:42] * ogra hands persia a pair of glasses :) [18:42] Which might explain ido- 's calibration issues. [18:43] -mid is on releases, -umpc is on cdimage [18:43] but nontheless both had released images with proper naming etc [18:43] * persia confusedly re-reads the URL, and is again confused, but will learn [18:44] yeah i'm not happy either [18:45] I'm not unhappy, just confused. [18:45] 30.1 was the last daily build ... terranova had a hiccup on the 30 image [18:46] well, i would have liked both in the same place [18:47] Oh, yeah, it would be nice if the ultimate intrepid daily build was also the release build, but that's just an implementation detail. [18:47] My fault mostly, for not raising it to the release team early enough. [18:47] ?? [18:47] the ultimate one is the released one [18:48] for upc that was 30.1, for mid that was 29 [18:48] So http://cdimage.ubuntu.com/ubuntu-umpc/intrepid/current/ubuntu-umpc.img == http://cdimage.ubuntu.com/releases/intrepid/release/ubuntu-8.10-umpc-i386.img ? [18:49] right, current was copied over to ubuntu-8.10-umpc-i386.img [18:49] but not 20081030 [18:49] Then what do you mean " i would have liked both in the same place" ? [18:49] MID + UMPC? [18:49] yes [18:49] RIght. My fault. [18:49] its tricky to get that across [18:49] nope [18:50] thats been part of the renaming [18:50] not yours [18:50] Yeah, but I'm the person who integrated the images with the milestone series and missed a step in doing so, which is why the rename came so late. [18:50] mid is "official", umpc isnt [18:51] Yep. [18:51] umpc will be official next time : all the prerequisites are in place. [18:52] right, i'll write a spec for presseding umpc to be netbook tomorrow ... lets see if we get gfxboot working with syslinux ;) [18:52] huh? [18:53] that way it would be possible to have all three flavours in a single image, build lpia and generic and have a selection menu like the cd [18:53] Why would you want to do that? [18:53] Ah. Interesting. Is the netbook team planning to go for flavour status then? [18:54] no, but i'm supposed to do something with the four apps [18:54] so ubuntu-umpc-default-settings will get a preseed value to switch flavours [19:10] hrm [19:10] back [19:10] orga/persia [19:10] another problem, non-related [19:10] i can't seem to get the install to work correctly [19:11] first, it doesnt always run (runs only after trying to run it multiple times) [19:11] and even when it does, it fails somewhere at the stage when its trying to repartition my HD [19:12] weird [19:12] it definately installs fine here [19:12] could i make it persistant storage without the need to install it somewhere ? [19:13] on identical HW (unless theere are different Q1U configurations, which i dont belive) [19:13] ido-, You could, but performance suffers : better to chase the install. [19:13] i think casper in intrepid had no proper support for persistance [19:13] unless that was fixed last minute [19:13] I thought that was fixed at the end, although I could be mistaken. [19:14] but afak the patch was considered o big for the late release state [19:14] so how do i make it persistant directly ? [19:15] * ogra repeats ... "i think casper in intrepid had no proper support for persistance" [19:15] whats casper? [19:16] the tool providing persistance ... and the liveCD bootmechanism used on the image [19:16] oh [19:19] orga [19:19] did you resize the partition using the installer ? [19:19] no [19:19] hrm that could be the thing causing it to fail [19:20] what kind of partition is that ? [19:20] ntfs ? [19:20] the one that comeswith the device. [19:20] might need something like a defrag run before and removal of the windows swapfile before you can even resize it [19:20] hrm. getting the error: An error occurred while writing the changes to storage device" [19:21] does gpart do that ? [19:21] gparted [19:21] windows usues to put the swapfile at the end of a partition which might cause resizing to fail [19:21] no idea what gparted does, we dont sue it since years in ubuntu, partman (teh tool the installer backend uses) doesn usually a safer and more effective job [19:22] *use [19:27] seems the ntfs partition was unclean [19:27] so it couldnt shrink it [19:28] right [19:28] clean it under windows first [19:28] thats what i'm doing [19:28] do a defrag and disable the swapfile ... [19:28] you can re-enable it after the shrinking [19:29] how did you calibrate your screen orga? [19:29] using te calibration tool [19:30] which one ? [19:30] thats why i wrote it :) [19:30] the one from the system menu [19:30] oh. [19:30] it didnt detect a touchscreen device on mine.. [19:30] (although the touchscreen worked ok..) [19:30] and Xorg.log showed evtouch loaded [19:31] works fine here ... just tested it this second [19:32] and if you have the same device i dont see a reason why it shouldnt work [19:32] hrm. [19:32] lshal|grep eGalax [19:32] does that return anything ? [19:32] lspci shows eGalax [19:32] i think lshal does so to.. [19:33] hal cares for the device nowadays [19:33] check it, it should return two lines [19:33] sec, rebooting into ubuntu after disk cleanup.. [19:33] how much space should i allocate for ubuntu ? [19:33] would 3gb be fine for starters ? [19:34] its just for testing.. [19:34] to set how well it works on the umpc [19:34] the current install uses about 2.5G [19:34] so for testing 3G plus swap [19:34] really ? [19:34] oh. o [19:34] ok [19:35] that leaves you 500M for user data [19:35] thats not much. [19:35] well, give it more then :) [19:35] just got it booted [19:35] takes a while to boot.. [19:35] sure, its a live session [19:35] running calibration [19:36] nope, says no evtouch capable device found [19:36] but your touchsceen works ? [19:36] yes [19:36] what does the lshal command give you ? [19:36] lshal has eGalax [19:36] two times ? [19:36] yhep, info.product [19:36] and usb_device.product [19:36] i wonder if they have eGalax that are named differently somehow [19:37] eGalax "TouchScreen" [19:37] "eGalax ouchScreen" [19:37] [19:37] [19:38] thats what hal looks for in the device entry in lshal [19:38] and it works fine here in live mode as well as in installed mode [19:38] just tested both again [19:38] whats info.capabilities ? [19:39] a hal key [19:39] i dont see it under the touchscreen udi [19:39] lshal|less [19:39] did that [19:40] and ? [19:40] err, wait [19:40] hrm ok. [19:40] the Q1U has a Touchkit [19:41] yes [19:41] look for: lshal|grep Touchkit [19:41] Touchkit HID-USB Touchscreen [19:41] [19:41] [19:42] same thing [19:42] where do you se that config thingy ? [19:42] is it part of the calibration util ? [19:42] info.capabilities = {'input', 'input.mouse'} (string list) [19:42] info.category = 'input' (string) [19:42] info.parent = '/org/freedesktop/Hal/devices/usb_device_eef_1_noserial_if0' (string) [19:42] info.product = 'Touchkit Touch' (string) [19:42] in lshal [19:43] lshal|less [19:43] you should actually have it identical [19:43] well, almost [19:43] the info.product is different [19:43] oh [19:43] its "Touchkit HID-USB Touchscreen" [19:44] thats the prob then [19:44] not contains "touchkit touch" [19:44] you can edit /usr/share/hal/fdi/policy/10osvendor/50-touchkit.fdi [19:44] where did you see '" [19:44] after install though [19:44] sure i can [19:44] and i'll see if i can shove that in as bugfix [19:45] the match is in the .fdi file above [19:45] edited it [19:45] left only "Touchkit" [19:45] what now ? [19:45] just make it match Touchkit without Touch [19:45] well, it wont work easily on the livesystem [19:45] can i restart the hal thingy ? [19:45] oh, only after reboot.. [19:45] you essentially need to stop X, restart hal and start X again [19:46] how do i restart hal ? [19:46] sudo /etc/init.d/hal restart [19:47] hrm.is the calibration util source public ? [19:47] apt-get source xserver-xorg-input-evtouch [19:47] but it will go away in jaunty [19:48] go away ? [19:48] upstream xorg is working on making all touchscreen devies use the evdev driver and we'll have a generic calibration tool that should match more than evtouch [19:48] oh [19:48] ok [19:48] so the current tol is only an interim solution [19:49] *tool [19:49] i just wrote it to have anything at all [19:49] hrm [19:49] restarted hal [19:49] and X [19:49] since evtouch is abandoned by its dev since years and the calibration tool never worked [19:49] and it still didnt work [19:50] hal-find-by-property --key input.x11_driver --string evtouch [19:50] does that return anything ? [19:50]