[00:34] phew ... 30min before freeze i'm done [00:36] Woot [00:57] heh, and i'm on the frontpage of http://www.umpcportal.com/ :) [00:58] so we got proper touchscreen calibration ... not 100% where i wanted to be, but it will do for this release (i'll write a tool that supports more options for jaunty) and its fully hal capable [01:30] ogra: nice [01:34] shame they got your name wrong i think on report [01:36] ogra: That's a great review. Nice work on -mobile! [01:36] yeah, and i didnt even do much [01:37] sadly his theme is totally broken, my image here looks way nicer :/ [01:37] not sure why ... its the same image [01:37] No, you just made it work. Having something that works well on that variety of hardware, and gets "...the best [Linux build] I've seen on a UMPC..." [01:38] yeah, i was a bit shocked by his next sentence ... "unlike the ubuntu mobile i tried before" [01:38] he did not review the last release as he thought it was just a developers release apparently [01:39] ah [01:39] I suspect it's a combination of hardware issues (the Ubuntu MID release really only works on a couple specific pieces of hardware), and had some of the issues we've been chasing for this release. [01:39] i know him quite well, he's an ex colleague :) i guess i need to drive to cologne one day and take him out for a beer to teach him abotu linux [01:41] Unfortunate that he claims it's designed for "MIDs", as it's really for the larger segment, but that ought go away over time. [01:41] yeah [01:42] ogra: it seems to me you have a fan without even needing to shell out for the beer..so well done ;) [01:42] :D [01:42] i hope teh publicity gets me these lshal outputs i need so urgently ... :) [01:43] i dont really want to release with a touchscreen driver that only supports two devices [01:43] I'm also reminded, where are we on the psb driver? Does 2D work? [01:44] bah, just got a mail ... [01:44] * persia tries ogra's image on the SR to see how the touchscreen works [01:44] he complains about the install [01:44] Does the installer not work? [01:45] it does, but seems grub did break ... "file not found" [01:45] i'll try an install myself tomorrow [01:45] way to tired for today ... eh touchscreen calibration was a hard bone to chew ... [01:45] This is for i386! I thought that problem was lpia-specific [01:46] * persia digs into the ubuntu-mobile image to find out why [01:46] * persia is excited that the lack of the lpia kernel may not be the reason grub doesn't install [02:00] heh, he wants me for a live interview and question/answer session on friday :) [02:11] that sounds like fun..post the time of of it to the list [02:11] i will :) [02:12] but i'm to tired to negotiate that now ... will do tomorrow [02:14] * ogra just finishes his goodnight beer ... [08:10] Morning [10:01] StevenK: FYI there's a 48x48 icon in upstream's icons; and it's in .xcf so you could create a png if xpms lack colors === davmor3 is now known as davmor2 [10:58] hey, is there any official/non-official support for Amtek U560? [11:01] josephus: What proc? How much ram? what screen size? What resolution? [11:08] A110, 1024x600, etc.. What I'm concerned about is the wifi/bt support as I have no idea what chipset it has [11:14] specs: http://www.umpcportal.com/products/product.php?id=116 [11:18] Should work fine. It looks a lot like my kohjinsha, except smaller. [11:19] Do you have a unit, or would you be getting it in hopes that it worked? [11:22] josephus: http://www.mahalo.com/Amtek_U560 claims it can be purchased pre-installed with Ubuntu. I can't find any confirmation at the manufacturer's website, but that's typically a strong argument for HW support :) [11:27] ogra: About the -mobile image: it doesn't boot in KVM. Any ideas? [11:27] not really [11:28] OK. I just get a "Cannot Boot" message. Works beautifully on real HW. I'm excited about trying your new calibration tool, to see if I can get the touchscreen to reach the last 5% of the screen. [11:29] Yeah I've found that page too. Actually I plan to get any UMPC with QWERTY that has Linux support, unfortunately Amtek is the only one I can get in a short time. [11:30] josephus: I can say with some certainty that the Kojinsha SR series, the Samsung Q1 series, the Aigo MID, and the Sharp D4 are the most likely to be supported for -mid for intrepid (note that neither the Q1 nor the SR are really MIDs). [11:31] josephus: It's safest if you get one of those, because there's someone in this channel that has one, and with whom you can discuss any adjustments. On the other hand, if you don't mind getting your hands dirty a bit, just about anything with Linux support ought to work, and can certainly be made to work for the next release (assuming it meets minimum specs, etc.) [11:36] persia, i have to find a working basic config, currentl the devices are totally unconfigured until you run the tool first [11:36] persia: I will have to get my hands dirty either way but I would be stuck if there were no support for the wifi. [11:37] but at least the tool runs in X and has a .desktop entry in the control center [11:37] ogra: Right. I want to run the tool, and get it configured, and pass you the data :) [11:37] Oh it does? [11:37] * persia looks [11:37] oh, lshal should suffice [11:37] (at least if you know it works with evtouch normally) [11:37] ogra: Oh. That's easy. I thought you also needed some other information from a working calibrated xorg.conf [11:38] not anymore, thats up to you now ... i gave you a clibration tool :P [11:38] OK. I'm looking for it :) [11:39] What is it called? [11:39] * persia updates in case it requires something newer [11:39] i did hide it under "Touchscreen Calibration" :) [11:40] should be in system->Settings [11:40] or however thats called in english [11:40] in the menu where you find synaptics and friends [11:43] I have System/Preferences and System/Administration. Neither has Touchscreen Calibration. Which package do I need to have installed? [11:44] xserver-xorg-input-evtouch [11:45] I have 0.8.7-3ubuntu6 installed. [11:45] * persia upgrades [11:46] yeah, you nee 8 [11:46] *need [11:46] 7 makes it work from commandline, 8 gives you the X goodness [11:46] Err. I did that wrong. upgrading the kernel and firefox in a live session is *not* recommended. [11:47] heh [11:47] you should be able to re-login [11:47] at least for FF [11:48] I won't even bother. I'm just going to run the calibration tool. I finished testing the stuff I booted this for, and need to boot back into -desktop to test a couple other things and recover some data before I do a reinstall. [11:48] thats mobile or mid ? [11:48] -mobile [11:48] do you have a proper dark theme ? [11:49] Everything looks good except the default background for the browser, terminal, text-editor, etc. [11:49] * ogra is curious why it didnt work in the video [11:49] For the terminal, I set to 100% transparency and white text, which is very nice with which to work. [11:49] whats wrong with the default background ? wasnt it white ? [11:49] (i didnt modify it) [11:50] Right. Can't upgrade: not enough space. I'll do the calibration in -desktop. [11:50] Yes, it was white, which didn't look good with the dark theme and pretty left and top bars. [11:50] yeah, or reboot and only upgrade the evtouch package [11:50] ok [11:50] yeah, i can change the terminal defaults ... and set a browser homepage [11:50] Well, since I have to reboot into desktop anyway for other reasons, I'll do it that way. [11:51] the calibration requires a reboot btw [11:51] It looks *great* though. I'll definitely be running -mobile on the Kohjinsha at UDS. [11:51] i didnt manage to make it work without restarting hal [11:51] All the more reason to do it in -desktop: that's actually resident on the hard drive. [12:00] meh, it has a typo [12:00] (says restart your session instead of system) [12:00] oh !!! [12:00] * ogra has an idea [12:02] oh, and i called it "Calibrate Touchacreen" not "Touchscreen Calibration" :) [12:04] yipppie ... i have the proper solution [12:04] Earlier in the alphabet is *always* better. [12:04] no need for a reboot [12:04] Hrm? [12:04] * ogra slaps forehead why he didnt get that idea yesterday already [12:05] well, i wanted to run the config commit from a Xsession.d script ... didnt manage to make that work, so you needed to restart the system ... instead of simply doing a relogin [12:05] and i had to put the commit stuff into an initscript [12:06] simply running the initscript at the end of calibration sets the new values :P [12:06] and you just need to relogin instead of rebooting [12:07] ogra: Nothing turns red for me. [12:07] takes a moment [12:07] (you did hit enter, right ? ) [12:08] * persia tries again. [12:08] i just tried it the first time on the Q! [12:08] Q1 [12:08] worked fine [12:08] OK. First step, touch the pen to the screen, and move around all the edges. [12:08] Second step, press Enter [12:08] right [12:08] Third step, wait. [12:08] third, wait until top left cross turns red [12:09] you sure your enter key works ? [12:10] Yes. If I now tap the screen 9 times, the tool exits. Just nothing ever turns red. [12:10] i'll rework the cursors and font for that screen in jaunty ... it really needs a better visual handling ... [12:11] it's left-to-right, top-to-bottom? [12:11] right [12:11] starts top left, goes to top right ... then middle row [12:11] same there [12:11] * persia ignores the lack of visual response, and calibrates the touchscreen. [12:11] then bottom row [12:12] you had the values showing up on the screen while moving to the edges ? [12:13] No. The values on the screen never changed whilst I was moving to the edges. [12:14] so in case you are done, just run sudo /etc/init.d/xserver-xorg-input-evtouch start from a terminal and relogin [12:14] oh [12:14] It also failed to calibrate my touchscreen. [12:14] are you sure that touchscreen is evtouch ? [12:14] Does logging out and in again not reload? Do I need to also restart the init script? [12:14] well, currently you actually need to reboot [12:15] but wait [12:15] you dont have a .fdi file :P [12:15] so the driver isnt loaded at all [12:16] RIght. What do I need to do to get an .fdi file? [12:16] easiest is to copy the 10-eGalax.fdi in /usr/share/hal/fdi/policy/10osverndor [12:16] copy it to? [12:16] look at the two "" lines [12:16] to something... pick a significant name for your touchscreen device [12:17] like "PenMount USB" ? [12:17] change the match lines to match your touchscreen with lshal values (easiest is to install gnome-devcie-manager) [12:17] yeah, something like that [12:18] hal needs one or two values to match against to know it should not load evdev but evtouch for this device ... else its silly and says its a mouse or kbd and uses evdev [12:18] Yeah. That's what is happening now. === amitk_ is now known as amitk [12:19] should also show up like that in Xorg.0.log [12:19] So you recommend matching against info.product and info.capabiliites? [12:20] yeah, or whatever unique parameters can identify your device [12:20] you will need to reboot then [12:20] hal wont just pick it up [12:21] (unless you can unplug it, which i doubt) [12:21] rebooting is no issue. Let's see what happens. [12:22] I suspect the reason I appeared to be able to calibrate was that I was using the left-click-to-advance function. [12:24] yeah [12:29] if you have a working .fdi, paste it for me, i have a package update pending [12:35] ogra: I note the touchscreen doesn't work for my Q1 [12:35] StevenK, do you have the latest evtouch update ? [12:35] it doesnt pre-calibrte anymore, it will only work after a first calibration run [12:36] ogra: I have 0.8.7-3ubuntu8 xserver-xorg-input-evtouch [12:36] ogra: Ah. How do I calibrate it? [12:36] good, look for "claibrate touchscreen" [12:36] it has a menu entry [12:37] in System->Administartion [12:37] Ah. Currently we don't parse system [12:37] aha [12:37] well, run sudo calibrate_touchscreen then from a terminal [12:39] i would have put it in Preferences, but that didnt seem appropriate for a sudo'ed tool [12:42] StevenK: Do you want an applications-merged/ entry to grab Settings and call it "Preferences"? [12:43] persia: Nope, since the top level of the System menu is Preferences and it grabs the stuff [12:43] * ogra lols about the "rename it" mail thread in -mobile [12:43] geez [12:43] StevenK: OK. You've a working local applications-merged/ entry? [12:44] I had. [12:44] Well then, I won't create one :) [12:44] I've since hacked code to also parse settings.menu [12:44] Unless you think that will pull in too much [12:45] Hm. It really does. [12:48] Hrm? kourou reads settings.menu directly? I like merging better, unless we want to do something funny. [12:52] ogra: Adding the .fdi file made things turn red, but it's not a very visible red. Could it change value more, as well as hue? [12:52] i'll try that, so paste me the .fdi :) [12:52] persia: It was going to, and now it isn't. [12:52] :) [12:53] ogra: I'm still rebooting to make sure the calibration worked. I'll paste you the .fdi soonish now... [12:53] it worked :) [12:53] (and then I have a good excuse to unbox the new device and calibrate that too) [12:53] and get me another .fdi :) [12:54] hmm, i should merge all of them into a evtouch.fdi [12:55] Probably. Ends up with more matches, but avoids namespace issues. [12:55] Hrm. Now it won't boot :/ [12:55] :( [12:57] Almost time for the meeting [13:01] Starting the meeting [13:02] ogra: Not calibrated :( [13:03] lool, you about in the meeting? [13:03] I am [13:03] persia, does /etc/evtouch/config contain values ? [13:04] should have 22 lines [13:05] and does hal see it as evtouch device now ? [13:05] lsha|less [13:05] and then search for evtouch [13:05] *lshal indeed [13:09] lots of stuff there. [13:09] in lshal ? [13:09] do you see things like maxx and maxy ? [13:10] I see all of that in /etc/evtouch/config, but it's dark, I'm distracted, and there are too many keyboards, so I haven't gotten the lshal stuff yet :) [13:11] well, you should see all the values in lshal as well and you should see evtouch somewhere in there as well [13:12] your .fdi probably defines the wrong device ... usually a touchscreen has two or three of them [13:16] ogra: gnome-device-manager shows it to be evtouch, and has all the hint values: it's just not calibrated correctly. [13:16] hum [13:17] what mainly counts is the maxx, maxy, minx and miny [13:17] ogra: So, in about 43 minutes, I'll ask you to lead me *very* slowly through the steps, checking each step, and we can sort it. [13:17] the min values usually are between 100 and 300 [13:18] max should be between 6000 and 8000 somewhere [13:19] I'm getting stuff like -1019 through to about -5 [13:19] for the min/max values ? [13:19] thats definately wrong [13:20] the Xn/Yn values are fine to be negative, but min/max should be positive [13:20] Xn/Yn are the fine tuning values for the crosshairs ... min/max are the edges [13:22] Oh. I get 0 and 20000 then. [13:40] should intrepid images boot in vmware? [13:42] josephus: I don't know that anyone has tried. -mid is known to boot in virtualbox and KVM. -mobile didn't boot for me on kvm, but I've heard no confirmation, or information about testing in other environments. [13:59] Burgundavia: You had a question about form factors? [14:00] yah, still wrapping my head around the dividing line between mid and netbook, from the package selection sense [14:01] mid is for 4-7" devices [14:01] Burgundavia: OK. Firstly, let's ignore the word "netbook". [14:01] netbook is for netbooks [14:01] So, there's two flavours that we tend to work on here: ubuntu-mid and ubuntu-mobile. [14:01] Burgundavia, you mix up -mobile with -mid :) [14:01] No ubuntu-netbook? :) [14:01] yes, I do [14:02] ubuntu-mid is a hildon-based environment: loosely related to Maemo. [14:02] lool: Nope. There is no ubuntu-netbook. [14:02] right, got that, mobile is not-netbook? [14:02] persia: Is it maemo or is it moblin? [14:02] ubuntu-mobile is a gnome-based environment designed for small screens. [14:02] Ah sorry, no fair making fun of the mess I'm in as well :-) [14:02] but ubuntu-mobile lacks nice things like the ume-launcher [14:02] Burgundavia, -mobile is for touchscreens, the netbook remix is a commercial product for netbooks ... largely without touchscreens using 4 specailly written apps [14:02] lool: Yes. [14:02] * lool has some odd type of humor today it seems [14:03] Burgundavia: ume-launcher isn't in Ubuntu :) [14:03] netbook-launcher is [14:03] We should start a nettop image for crazyness [14:03] but, yes I see your point [14:03] Burgundavia, netbook-launcher (how its called in intrepid) is only usable on a vers specual setup, i.e. all size values are hardcoded [14:04] Burgundavia: So, clearly, anyone can use any software on any device, but the idea of -mobile is to target things with touchscreens and limited screen real-estate, but still large enough to fit in a bag. [14:04] seems to work just fine scaling up on my 1280x768 laptop [14:04] you need to compile a special version with different values for different screens, thats currently not doable with our manpower [14:04] The idea of -mid is to have something significantly more pocketable. [14:04] n810-sized (but atom based)? [14:04] Burgundavia, it is hardcoded to 24px panels and to 5px off the edge of the screen ... you cant use a sidepanel for xample [14:04] its not built for touchscreens [14:04] right, I saw that [14:05] ouch [14:05] beyond that it doesnt work in intrepuid [14:05] its also closely bound to clutter 0.6 [14:05] with clutter 0.8 which is the current version fonts are not displayed etc [14:05] clutter doesnt work with compiz either [14:06] the first few unreleased ubuntu-mobile builds used netbook-launcher [14:06] Burgundavia: Precisely. [14:06] yay for my bling doesn't work with your bling [14:06] after using it for two weeks i really didnt find it suitable for a release [14:06] it will rock in jaunty but for intrepid it simply isnt ready [14:07] needs to much of a rewrite which wont happen before beta i think [14:08] you need a followup faq post, clearly [14:08] Burgundavia: First we need a common set of questions. [14:08] Currently, most questions are being asked for the first time. [14:09] The only one that seems common is confusion about netbook, but that's been pervasive since the netbook remix was announced. [14:09] Burgundavia, i took the blame to take maintenance for the netbook apps, they surely fall into the mobile area and i know there are plans to make netbook-launcher work on touchscreens, but as long as its not there i cant do much about it [14:09] well, the netbook and mid stuff don't fit into neat existing categories like laptop, desktop and phone [14:09] so -mobile is what it is and wont change much [14:10] Burgundavia: Well, someone didn't want us to call a MID a PDA. I don't personally understand why, but... [14:10] and the community feedback on http://www.umpcportal.com/2008/09/ubuntu-mobile-edition-news-and-first-boot-video/ and the ubuntu-mobile and gnome-mobile lists somewhat prove i'm doing it right ;) [14:10] yes, some marketing wonks in Intel [14:10] because PDA == Palm == 90s == boring [14:10] Burgundavia, btw, what was your KDE complaint about yesterday ? [14:10] -mobile is new, but the desktop environment doesn't work so well on a 7" screen (it's sitting next to me now: I *know* it's not as pretty as -mobile), but -mobile is too small for a 14" screen. [14:11] Burgundavia: I guess. My PDAs haven't been boring for years, but they've all been what are now called MIDs. [14:11] ogra: evtouch and zenity [14:11] it will work, just not display the help [14:12] i'm fine f soemone sends me a kdialog patch [14:12] it would also need a special .desktop file using kdesu [14:13] but after all you can call sudo calibrate_touchscreen in any environment [14:14] i'll write a wikipage for it once i have enough .fdi files that it actually supports more than 2 device categories ... [14:15] currently i can only suport the two touchscreen categories i can test on and despite several calls on planet and mailing lists i didnt recieve more lshal output from other people yet [14:17] ogra: So, lead me through a process that gets me a working calibration. [14:17] (and I'll give you a .fdi file) [14:18] well, i wonder why you get the 20000 there [14:18] might corellare with the DPI [14:18] *corelate [14:25] ogra: This is only ~170 DPI. Should be about the same as the Q1U [14:26] well, if you run the calibration now, do you see the numbers moving ? [14:26] No. [14:26] else i suspect either its not an evtouch device or the fdi points to the wrong device [14:26] * persia tries some other things [14:27] Do I need to delete some file? It won't run now. [14:30] not at all ? [14:30] it should run in any case (even if you dont have a touchscreen) [14:31] Well, it shows the splash, and then tells me the calibration is complete. No calibration screen. [14:31] hal-find-by-property --key input.x11_driver --string evtouch [14:31] does that return a UDI ? [14:31] should have something like logicaldev_input at the end [14:35] That didn't return anything. I suppose that means my .fdi file is wrong. I wonder why it said evtouch in gnome-device-manager [14:39] what device did it apply to ß [14:39] ? [14:39] ogra: Hrm? The touchscreen, according to g-d-m. [14:39] usually you have a HID->USB Interface->Touchpad/screen chain [14:39] it has to apply to the lowest in the chain [14:41] Computer -> USB UHCI Controller -> Hub -> USB Device -> Mouse HID Device Interface (Boot) Interface -> Pointing Device [14:42] no touchpad there ? [14:43] touchpad is Computer -> Platform Device -> i8042 AUX2 port -> Touch Pad [14:43] thats likely the synaptics touchpad [14:43] there should be a second one for the touchscreen [14:43] attached to usb [14:44] Nope. The only listed touchpad is the actual touchpad. The touchscreen is a "Pointing Device". [14:44] else you even miss kernel support for it i think [14:44] * persia fiddles with the .fdi file, and tries to fix that first [14:44] yeah, but thats only half of the device [14:44] Well, it works, it's just not calibrated. [14:44] it works with evtouch loaded ? [14:45] did it work before ? without loading it ? [14:46] [ 15.737517] input: IDEACO^D IDC 6680 as /class/input/input2 [14:46] [ 15.741238] input,hiddev96,hidraw0: USB HID v1.10 Mouse [IDEACO^D IDC 6680] on usb-0000:00:1d.2-1 [14:46] [ 15.785496] input: IDEACO^D IDC 6680 as /class/input/input3 [14:46] [ 15.788536] input,hidraw1: USB HID v1.10 Mouse [IDEACO^D IDC 6680] on usb-0000:00:1d.2-1 [14:46] [ 15.788555] usbcore: registered new interface driver usbhid [14:46] Yeah. It works either way, it just isn't calibrated. Anyway, it's the same screen as used in the Flybook: I think I'll go hunt to see how they do it. [14:46] thats my dmesg output for my touchscreen [14:46] do you see yours in dmesg ? [14:46] /class/input/input2 is the actual touchscreen [14:47] input3 is a strange mouse emulation device [14:47] No, I only have one device showing. [14:47] i know evtouch work for lifebook ... not sure about flybook [14:48] whats the actual device name/manufacturer ? [14:48] i have a list here for evtouch [14:49] AHA ! [14:49] flybook is plpevtch [14:49] DIALOGUE [14:50] and plpevtch isnt packaged :( [14:50] http://download.plop.at/files/plpevtch/xf86-input-plpevtch-0.0.3.tar.gz [14:51] i wonder if thats mergeable into evtouch [14:51] My event devices are "Macintosh mouse button emulation", "AT Translated Set 2 keyboard", "DIALOGUE INC PenMount USB", "Power Button (FF)", "Lid Switch", "Power Button (CM)", "Video Bus", "F013FF-68 PC-CAM", "SynPS/2 Synaptics TouchPad", and "PS/2 Generic Mouse". [14:52] DIALOGUE INC PenMount USB sounds about right [14:52] I think the extra function keys come through the camera (as it supports EV_KEY) [14:52] i was just about to buy a dell mini inspiron 9 .. but then discovered they do not ship it with ubuntu in australia [14:53] Yes, that's the one I can't calibrate. Intrepid is *much* better than hardy for this device, but it's still off by a bit. [14:53] i want to buy something cute and small that has ubuntu on it.. are there other options available or coming soon? [14:53] apt-get install xserver-xorg-input-penmount [14:54] that should make use of it [14:54] it emulates wacom [14:55] so you need to use wacom calibration tools [14:55] sigh ... and it even emulates it throuh the serial port [14:55] Ahh. That explains it. I've been fiddling on and off with evtouch since May, and all along it's been the wrong driver :) [14:56] http://paste.ubuntu.com/50489/ [14:56] ogra: Thanks. Despite my shame, it will be nice to have this working :) [14:56] rework that to a .fdi file [14:56] (probably adjust min/max values) [14:57] Are those sensible defaults with which to start? [14:57] no idea [14:57] bug 261873 has example .fdi files [14:57] Launchpad bug 261873 in xf86-input-evtouch "make evtouch devices work with hal-input in intrepid" [High,Fix released] https://launchpad.net/bugs/261873 [14:57] Oh, right. I have some installed :) [14:58] just make all the options string and make the option names lowercase [15:00] if you get me your lshal i can create an fdi file to start from ... i bet you need to adjust the values though [15:02] I'll fiddle with it a bit tonight or tomorrow. If I get lost, I'll give you lshal, but it's worth learning. [15:02] its worth having the .fdi in the package i guess [15:02] even if people have to modify it manually its helpful [15:03] we need s generalized calibration tool in jaunty [15:03] persia: linux-lpia-meta binary NEWed [15:03] i'll propose a spec for that [15:03] \0/ [15:03] StevenK, did you get your calibration working btw ? [15:03] * persia will be very excited to see if the "No kernel found" error goes away as expected. [15:04] ogra: No [15:04] StevenK, no in you didnt try ? or no in something was broken [15:04] ogra: The latter [15:04] if so, what (i want to have that done before beta) [15:05] ogra: No instructions, so I had no clue what to do [15:05] apt-get install zenity :) [15:05] It also requires zenity? [15:05] it doesnt ... but it shows instructions if zenity is there [15:06] less /usr/bin/calibrate_touchscreen otherwise :) [15:06] it has the instructions inline for now [15:06] ogra: It should Recommends zenity [15:06] for jaunty i want a full pygtk tool that can also modify the tap values etc [15:07] persia, that would pull in zenity into -mid i wasnt sure thats desired [15:07] ogra: Hrm. Good point. [15:07] not sure how much gnome that pulls in [15:07] I'll check that tomorrow [15:08] basically ... move your pen to all edges, hit enter, wait until top left cross turns red, tap each red cross once [15:08] So tap all four corners? [15:08] all 9 crosses [15:09] did you get the claibration screen ? [15:09] I wasn't getting any indications I should be using my finger, or the mouse, or what [15:09] (white screen with a bunch of crosses) [15:09] Yes, I got that screen [15:09] good [15:09] so it basically works at least [15:09] best is to use a pen [15:11] if you did like i sadi above, run sudo invoke-rc.d xserver-xorg-input-evtouch start and restart your X session ... it should eb calibrated then [15:11] *be [15:12] * ogra wonders if he should fall bac to xdialog [15:12] hmm, thats not installed by default either anywhere [15:13] but would probbly be the better choice for hildon [15:14] * ogra checks whats required for that [15:14] hmm, no deps at all apart from Xlibs :) [15:21] Falling back to that makes sense then. We can hint the alternate in the seeds. [15:21]