Re: SHR enlightenment crash
On Mon, 2 Nov 2009 06:21:22 -0500 Seth Rothenberg said: > Carsten, > > > gdb enlightenment PID > ... > ... > > we even have a whole wiki page on it: > > > > http://trac.enlightenment.org/e/wiki/Debugging > > > Thank you. That's a great lead. > The reason I looked at dmesg is in case it > is a systems issue as suggested by the message > >>>[21474576.125000] Unable to find swap-space signature > > Here's what I did next... > > opkg install gdb > gdb enlightenment 1542 > > I got a lot of reports of "no debugging symbols found" > (Perhaps I need to install a version compiled with -g or such?) > > and > > (gdb) bt > #0 0x409eae3c in poll () from /lib/libc.so.6 > #1 0x4085c7c8 in ?? () from /usr/lib/libX11.so.6 > Cannot access memory at address 0x0 > (gdb) > > All the output from gdb does not mention "sig" there should be -dbg (debug) packages of efl and e available in you repository. -- - Codito, ergo sum - "I code, therefore I am" -- The Rasterman (Carsten Haitzler)ras...@rasterman.com ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: SHR enlightenment crash
etect has no irq available > > [21474574.445000] mapped channel 0 to 0 > > [21474574.665000] s3c2440-sdi s3c2440-sdi: powered down. > > [21474574.665000] s3c2440-sdi s3c2440-sdi: initialisation done. > > [21474574.685000] s3c2440-sdi s3c2440-sdi: running at 0kHz (requested: > > 0kHz). [21474574.685000] s3c2440-sdi s3c2440-sdi: running at 196kHz > > (requested: 195kHz). > > [21474574.685000] s3c2440-sdi s3c2440-sdi: running at 196kHz > > (requested: 195kHz). > > [21474574.695000] s3c2440-sdi s3c2440-sdi: running at 196kHz > > (requested: 195kHz). > > [21474574.695000] s3c2440-sdi s3c2440-sdi: running at 196kHz > > (requested: 195kHz). > > [21474574.715000] s3c2440-sdi s3c2440-sdi: running at 196kHz > > (requested: 195kHz). > > [21474574.725000] mmc1: queuing CIS tuple 0x01 length 3 > > [21474574.745000] mmc1: queuing CIS tuple 0x1a length 5 > > [21474574.755000] mmc1: queuing CIS tuple 0x1b length 8 > > [21474574.755000] s3c2440-sdi s3c2440-sdi: running at 25000kHz > > (requested: 25000kHz). > > [21474574.755000] s3c2440-sdi s3c2440-sdi: running at 25000kHz > > (requested: 25000kHz). > > [21474574.76] mmc1: queuing CIS tuple 0x80 length 1 > > [21474574.76] mmc1: queuing CIS tuple 0x81 length 1 > > [21474574.76] mmc1: queuing CIS tuple 0x82 length 1 > > [21474574.765000] mmc1: new SDIO card at address 0001 > > [21474575.01] No device for DAI s3c24xx-i2s > > [21474575.22] No device for DAI Bluetooth > > [21474575.26] asoc: WM8753 HiFi <-> s3c24xx-i2s mapping ok > > [21474575.285000] asoc: WM8753 Voice <-> Bluetooth mapping ok > > [21474575.29] sound/soc/soc-dapm.c:349 mixer name 'Playback Mixer > > Voice Capture Switch' truncated to 31 characters. > > [21474575.29] sound/soc/soc-dapm.c:349 mixer name 'Playback Mixer > > Left Capture Switch' truncated to 31 characters. > > [21474575.29] sound/soc/soc-dapm.c:349 mixer name 'Playback Mixer > > Right Capture Switch' truncated to 31 characters. > > [21474575.29] sound/soc/soc-dapm.c:349 mixer name 'Mono Mixer > > Right Playback Switch' truncated to 31 characters. > > [21474575.29] sound/soc/soc-dapm.c:349 mixer name 'Mono Mixer > > Voice Playback Switch' truncated to 31 characters. > > [21474575.29] sound/soc/soc-dapm.c:349 mixer name 'Mono Mixer > > Sidetone Playback Switch' truncated to 31 characters. > > [21474575.29] sound/soc/soc-dapm.c:349 mixer name 'Mono Mixer > > Bypass Playback Switch' truncated to 31 characters. > > [21474575.29] sound/soc/soc-dapm.c:349 mixer name 'Right Mixer > > Voice Playback Switch' truncated to 31 characters. > > [21474575.29] sound/soc/soc-dapm.c:349 mixer name 'Right Mixer > > Sidetone Playback Switch' truncated to 31 characters. > > [21474575.29] sound/soc/soc-dapm.c:349 mixer name 'Right Mixer > > Right Playback Switch' truncated to 31 characters. > > [21474575.29] sound/soc/soc-dapm.c:349 mixer name 'Right Mixer > > Bypass Playback Switch' truncated to 31 characters. > > [21474575.29] sound/soc/soc-dapm.c:349 mixer name 'Left Mixer > > Voice Playback Switch' truncated to 31 characters. > > [21474575.29] sound/soc/soc-dapm.c:349 mixer name 'Left Mixer > > Sidetone Playback Switch' truncated to 31 characters. > > [21474575.29] sound/soc/soc-dapm.c:349 mixer name 'Left Mixer > > Bypass Playback Switch' truncated to 31 characters. > > [21474575.855000] HIFInit > > [21474576.125000] Unable to find swap-space signature > > [21474576.885000] BMI Get Target Info: Exit (ver: 0x2059 type: 0x1) > > [21474576.89] eth0 (sdio_ar6000): not using net_device_ops yet > > [21474576.96] AR6000 Reg Code = 0x4060 > > [21474588.78] eth0: no IPv6 routers present > > [21474589.26] usb0: no IPv6 routers present > > [21474595.76] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 > > [21474595.76] Bluetooth: BNEP filters: protocol multicast > > [21474597.065000] Bluetooth: SCO (Voice Link) ver 0.6 > > [21474597.065000] Bluetooth: SCO socket layer initialized > > [21474604.345000] mapped channel 10 to 2 > > [ 37.55] rxerr: port=1 ch=0x00, rxs=0x000d > > [ 37.585000] rxerr: port=1 ch=0x00, rxs=0x000c > > [ 42.405000] modem wakeup interrupt > > [ 43.985000] modem wakeup interrupt > > [ 47.055000] rxerr: port=0 ch=0x00, rxs=0x000c > > [ 47.055000] rxerr: port=0 ch=0x00, rxs=0x000c > > [ 3148.63] Adding 803240k swap on /dev/mmcblk0p4. Priority:-1 > > extents:1 across:803240k SS > > [ 3189.75] rxerr: port=1 ch=0x0f, rxs=0x0001 > > [ 3237.07] Adding 803240k swap on /dev/mmcblk0p4. Priority:-1 > > extents:1 across:803240k SS > > > > ___ > > support mailing list > > support@lists.openmoko.org > > https://lists.openmoko.org/mailman/listinfo/support > > > > > > > -- > Mit freundlichen Grüssen > Matthias Huber > Kohlstattstr. 14 > 86459 Wollishausen > Tel: 08238-7998 > LPI000181125 > > -- - Codito, ergo sum - "I code, therefore I am" -- The Rasterman (Carsten Haitzler)ras...@rasterman.com ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: illume-Keyboard lowercase?
On Mon, 12 Oct 2009 15:19:47 +0200 Nils Bokermann said: > Joachim Ott wrote: > > 2009/10/12 Nils Bokermann : > >> Al Johnson wrote: > >>> On Thursday 08 October 2009, Nils Bokermann wrote: > >>>> Hi! > >> Hi! > >> > >>>> I'm trying to get my Neo running with shr. Whenever I'm trying to type > >>>> in my password (consisting of upper and lowercase letters) I can use the > >>>> "shift" key on the "Terminal" keyboard, but a lowercase letter is sent. > >>>> > >>>> How do I get uppercase letters? > >>> Shift key gives upper case for me in shr unstable for every use I've > >>> tried. What exactly are you trying to do? > >> I'm trying to get my password typed in (which consists of lower-case and > >> upper case letters...) > >> > >> What I experience (even in the terminal-application) is: > >> I *can* use the shift-key and an uppercase-letter is shown as I type on the > >> keyboard, but on the terminal-screen, a lowercase letter is written. > > > > For the terminal: has someone (or something) changed the conversion > > handling for input? When you type "stty -a", do you see a "-iuclc" in > > the params or just a "iuclc"? For the latter case, you can fix that > > with "stty -iuclc". > > > > Hi Joachim, > > its not only the terminal. And for sake of completness: the terminal is > set -iuclc. calitals (shift) works in illume upstream, in xephyr and as people say - works on their gta02's with shr. i tested it and it works here. chances are u are missing keymaps for x that indicate "shift + a == A". literally these keymaps define such behavior and illume is just sending fake shifts+ a's to x via the x test extension. -- - Codito, ergo sum - "I code, therefore I am" -- The Rasterman (Carsten Haitzler)ras...@rasterman.com ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Illume Config Display
On Thu, 26 Mar 2009 15:17:50 + smchadw...@gmail.com said: > I'm fiddling around, for the first time, with Illume's config menu; some of > the items display well enough for me to use them, but others -- Wallpaper > Settings, for example -- display beyond the screen edges and there's no way > of scrolling around. I tried changing the screen orientation and the > resolution, but got the same results. Any ideas? Apologies if this has been > covered already. nothing new - known that they dont all fit on screen. :) -- - Codito, ergo sum - "I code, therefore I am" -- The Rasterman (Carsten Haitzler)ras...@rasterman.com ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: GTA02 is now an expensive brick
On Thu, 8 Jan 2009 05:49:39 -0800 (PST) Gothnet babbled: > > > > Carsten Haitzler (The Rasterman)-2 wrote: > > > > > > the real history is one of enigneers trying to push off the ever changing > > flavor of the month idea and trying to just get stuff to work. while > > kernel > > guys wrestled, userspace was being flung every which way... and not by me > > - not > > by harald. guess who was driving all the changes? you might want to dig up > > a > > bit more complete history before jumping to conclusions. :) > > > > > > Hey, no insult was implied and as a Software Engineer myself I know two > things - > > 1. Management are not only frequently wrong, but often difficult to persuade > otherwise > 2. If I'm given a free reign I'll go for stuff I'm interested in a find > stimulating > > My point is (and I hope I haven't missed the point of your comment when > stating this) that there doesn't seem to have been a consistent set of goals > or direction from the OM management or any particular focus (bar "Back to > Basics") to get the kernel and basic userspace functioning reliably, and > there does seem to have been a tendency to reinvent the wheel. And the > keyboard, the package manager yes - and these directives came from... management. engineering RESISTED or had the practical "lets use what we have and improve it as we go - some bits can be fixed/improved piecemeal, others need replacing in a bigger lump". but it means you can work on just getting something to work and then improve it as you go. i think that "given free reign" the enigneers would have done a much better job. much much much better. i tried my best to focus my efforts on doing things where my experience/knowledge would mean i can hit the ground running. fixing kernel suspend issues are not things i can hit the ground running on. but userspace suspend/resume infra i can - and i did (ompower). i spent a little while making a map navigation "widget" for diversity when that was all the rage. i worked on connman for wifi (the userspace bits for driving it) and finally got it to work - but was beginning to hit nasty wifi driver bugs. that was in addition to all the rest. i absolutely never spent 3 months on the keyboard - simply sean remembers a gap of 3 months and towards the end of those i did the keyboard - doing many other things prior to it. if management had actually given "free reign"they would have said: make the phone boot in a reasonable time make it last at least 48hrs without needing a recharge make it reliably make and receive phone calls and sms's make it sane/possible to enter text for sms's and contact information etc. make the other hardware function properly (wifi, gps, accelerometers) make some demo apps for the non-core hardware for a phone (gps, wifi, etc.) to show that it works and how to drive it. show us progress every 1 (or 2, 3 or 4) weeks with a new os image on a gta02. then sit back and let engineering do its job. the regular demos of "stuff moving along" (or a good explanation why you cant show anything currently) would be the oversight needed to make sure engineers didn't stray off-track. -- - Codito, ergo sum - "I code, therefore I am" -- The Rasterman (Carsten Haitzler)ras...@rasterman.com ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: GTA02 is now an expensive brick
On Thu, 8 Jan 2009 04:40:25 -0800 (PST) Gothnet babbled: > By the way, the Q and A email/looking forward to 2009 announcement from Sean > Moss-Pultz just confirmed a lot of what I'd thought about the OM management > situation. Where we have things like: > > "People, like Harald and Raster, are given immense freedom to work on what > they feel is most important." > > And then a story about how 3+ months were spent reimplementing a > keyboard > Perhaps people like Harald and Raster need their priorities given a nudge by > OM management once in a while? You know what, I don't give a about > which keyboard is best for terminal use, when I can't reliably make and > receive a phonecall/SMS. maybe you should have read my reply. it wasn't 3 months. also note that i am not a kernel coder so just jumping in and adding more cooks into what was already in the hands of kernel devs woukld be silly given that there was a mountain of userspace stuff to solve. nor did i have gsm firmware in hand at any time. there were people dedicated to just these. 3 guys worked pretty exclusively on the kernel. another guy was the gsm firmware guy - another team was doing gsmd. what you got from sean was a very surface-level answer. the truth was that it was the engineers saying "lets just stop changing direction and make the damn thing work". when sean and wolfgang and will went "oh lets use qtopia - cant we just port it?" i was going "how about we just use the 2007.x base and finish it to working? replace 1 bit at a time over time - eg replace the wm and launcher, improve keyboard, replace dialler etc. keep gsmd and just work on it to get it functional - make power management work". months were sunk into diversity which was pretty much meant to ignore gsm/gprs except for using it to break the telcos network - diversity was all about wifi, voip etc. - you have no idea how much time and how many engineers were sunk into that that went nowhere. then a retrophone idea (which was meant to be the phone bit and was basically an afterthought after diversity) - which had no tie-in technically or really to real work (eg use 2007.x). then there came "now qtopia!" then that had to be ported to x11 (holger time), then integration of qtopia and normal x11 and window manager stuff needed doing (as qtopia really had no concept of a wm and was assuming it was in qws and without one, owning the screen). then came all the new ui designs that had to be "pixel perfect" implementations of flash stuff for the launcher and the whole desktop (not done by me) - even the font was specified and font sizes and positioning of stuff - when i remember saying "how about we just work with what already works- in the way it works and improve it over time". i distinctly remember advising against qtopia as it'd be a time sink to get to work (if trying to mix with x11) considerign a team was dedicated to gsmd and so much work had gone into 2007.x. of course as a result 2008.x which was meant to make gta02 "workable" used none of 2007.x thus everything was lost. mind you qtopia brought holger on board and that was a huge asset. dropping x11 wasn't an option as we'd tie ourselves to a little-used windowing system (in open source circles) and a toolkit pretty much moving all development to c++ and qt as well as forcing the GPL license on all developers (no freedom to use other licenses like bsd, mit-x11, etc. etc.) unless they paid up to trolltech (who now are owned by a direct competitor too - nokia) further narrowing the potential user and developer base - so the x11 port was pretty much a "no choice" if qtopia was on the cards. the real history is one of enigneers trying to push off the ever changing flavor of the month idea and trying to just get stuff to work. while kernel guys wrestled, userspace was being flung every which way... and not by me - not by harald. guess who was driving all the changes? you might want to dig up a bit more complete history before jumping to conclusions. :) -- - Codito, ergo sum - "I code, therefore I am" -- The Rasterman (Carsten Haitzler)ras...@rasterman.com ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: SHR - Keyboard
e it may have some value. > > Agreed. With the corrective layout I can enter text reasonably reliably one > handed while walking. I wouldn't have a hope of doing this with the terminal > layout, or with the matchbox keyboard. > > > Compared with ordinary "tab completion" in linux commands it is not > > even a starter, and again is a distraction.. > > But for linux commands surely you would use the terminal layout, which > doesn't have the corrective feature enabled, and use tab completion. bingo. :) absolutely correct. > > clare (who really likes the matchbox keyboard - remember that?. It is > > used in the new "hackable"; > > and with apologies to Rasterman; but I do feel strongly on these points.) matchbox keyboard and illume temrinal layout are incredibly similar in their functionality. i don't see how there is a difference worth jumping around about beyond just the "i dont like e therefore do not want its keyboard". > Input method preferences are highly personal. Happily we have a choice of > input methods, and Rasterman included the facility to use them. If you > install the matchbox keyboard, or any other for that matter, it should appear > in the list of selectable keyboards in the illume config (spanner icon). yup. i even uses matchbox-keyboard as my initial tests for "other keyboards". i made it and multitap work. just add .desktop files so illume knows they exist and how to run them for you. matchboxkbd - i don't see the point of. multitap though - i do. :) > I suspect part of the reason people tend to dislike the qtopia and default > illume keyboards is that by default they don't do what we expect, and it > isn't obvious what they are doing. The matchbox keyboard is just an onscreen > representation of a familiar keyboard, and behaves as we expect. It doesn't > require any extra knowledge to get it to do what we want. The same could be > said of the illume terminal layout, but that isn't the default. also one could argue that the invers could be the case. i am trying to answer and sms and do nothing but yell at this tiny pokey keyboard i can barely hit with a finger - and the device has no place for a stylus (and the one that comes with it is so huge i wouldn't be seen dead carrying it). :) you can't win. you make lot A happy, then lot B unhappy. thats why there are multiple layouts to at least give the options to both. the default lean is towards using it as a PHONE - not as a terminal. i would assume the nerds have enough braincells to rub together to switch layout :) > The qtopia and illume keyboards try to be better, as does the iPhone > keyboard, but all require a bit of hidden knowledge to get them to work. Once > you know their secrets they are as good as or better than the matchbox > keyboard, but if you don't know the secrets then they are incredibly > frustrating. > > > ___ > support mailing list > support@lists.openmoko.org > https://lists.openmoko.org/mailman/listinfo/support > -- - Codito, ergo sum - "I code, therefore I am" -- The Rasterman (Carsten Haitzler)ras...@rasterman.com ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: SHR - Keyboard
On Tue, 16 Dec 2008 15:28:09 -0500 Paul babbled: > Is there a way to make the keyboard pop up on demand, say for the terminal? yes. the terminal can put a property on its window stating what the state of the keyboard for that window should be :) -- - Codito, ergo sum - "I code, therefore I am" ------ The Rasterman (Carsten Haitzler)ras...@rasterman.com ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Sad Story
On Tue, 16 Dec 2008 02:21:55 +0530 Karthik Kumar babbled: > Al Johnson wrote: > > Neither are representatives of Openmoko. They have bought phones just as > > you and I have. I suspect that they are frustrated by this long and > > unproductive thread, and by your perceived attitude. You don't appear to be > > interested in getting solutions to whatever problems you may be having. > > Suggesting someone is lying when they try to correct your misunderstanding > > is just plain offencive where I come from, as are your unsubstantiated > > accusations about Openmoko and their staff. This may simply be a cultural > > misunderstanding, as is often the case on international lists, in which > > case I suggest you correct it now. > > See, I do understand that they've got their own pressures. But by merely > trying to work on GTA03 (hardware or software), it's like they've thrown i think here you have the reality of producing a device wrong. let me put this straight. i used to work at openmoko. but i do not speak for them. openmoko employs a group of people. some of them do hardware, some software. the hardware goes do not know software or how to fix the higher level stuff - do you expect them to sit idle and do NOTHING (not work on gta03) and get paid for twiddling thumbs just because you are unhappy with the gta02? hell no. reality is that they march on to do gta03. some of software implicitly marches on too. openmoko is paying people to work on gta02 SOFTWARE and fix things. they spend their days doing it. they can do little to FIX hardware you have as it's in your hands. they CAN fix software as you can trivially download/flash updates. i am not addressing ANYTHING ELSE you have said - i'm leaving it well alone. i am ONLY addressing the work on GTA03 - they HAVE to do it. it's a reality of business because they have a hardware division that otherwise sits idle. -- - Codito, ergo sum - "I code, therefore I am" -- The Rasterman (Carsten Haitzler)ras...@rasterman.com ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Om2008.9 suspend? - OM2007.2 battery life > Om2008.9 battery life
On Wed, 01 Oct 2008 08:53:02 +0100 Andy Green <[EMAIL PROTECTED]> babbled: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Somebody in the thread at some point said: > > |> if it is - you are victim of the "qpe halted suspend before it ever > got to the > |> kernel" bug. ompower is stuck waiting for apm -s to return > (indicating resume) > |> at which time it will turn the light back on. > > I guess I should have said "if anything in userspace decides..." then, > but it is evidently the right idea. > > Just curious, what's qpe's POV about intercepting the suspend? I guess > there are plans to have it not do it without a better reason? it needs to to tell the gsm modem to go into "low power i'm suspended" mode - thus it needs to intercept the suspend action until it's managed to do this. i THINK that qpe simply manages to error here. either calypso does the right thing and replies and qpe doesnt know, or calypso just errors or refuses. but the problem is definitely in that space somewhere. :( (kill the apm process thats hung and presto - backlight will be back on! but you have a badly behaving calypso i think... so ymmv after that) -- - Codito, ergo sum - "I code, therefore I am" -- The Rasterman (Carsten Haitzler)[EMAIL PROTECTED] ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Om2008.9 suspend? - OM2007.2 battery life > Om2008.9 battery life
On Tue, 30 Sep 2008 22:57:44 +0100 Andy Green <[EMAIL PROTECTED]> babbled: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Somebody in the thread at some point said: > | I was thinking of switching to the latest Om2008.9 from OM2007.2 > | because Om2008.9 resumes a lot quicker from suspend. However, the > | battery life with Om2008.9 is greatly reduced. This leads me to > | believe that Om2008.9 either isn't truly suspending--more of a > | standby--or just isn't suspending everything that OM2007.2 does. > | Anyone else experiencing the same thing? > | > | The one difference is that Om2008.9 was running from the microsd card. > | Would that make a difference as far as power usage during suspend? > > There's this new userspace power daemon that makes decisions about > backlight and suspend now. If it decides to just keep backlight "off" > for long periods, there's a bug in recent kernels that actually leaves but it doesnt ever decide that :) the problem is qpe halting apm suspends. the backlight is turned off and ompower has issues an apm -s command. irf you find your system with light off and "seemingly dead" but possibly still powered on - connect to usb, ssh in and check ps - see if 'apm -s' is running: ps -ef | grep apm if it is - you are victim of the "qpe halted suspend before it ever got to the kernel" bug. ompower is stuck waiting for apm -s to return (indicating resume) at which time it will turn the light back on. > the backlight slightly on (trying to avoid another bug in the PMU). I > fixed this tonight on another tree and will update stable with it later > or tomorrow. > > It might not be the whole story but it should help. > > - -Andy > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.9 (GNU/Linux) > Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org > > iEYEARECAAYFAkjioNAACgkQOjLpvpq7dMpzdQCdH14VCgoAi0mwZdt3zNo/cXnd > A3gAoIMKQmiYrZKE2FiGbwBG77gyntDC > =DmKW > -END PGP SIGNATURE- > > ___ > support mailing list > support@lists.openmoko.org > https://lists.openmoko.org/mailman/listinfo/support > -- - Codito, ergo sum - "I code, therefore I am" -- The Rasterman (Carsten Haitzler)[EMAIL PROTECTED] ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: enlightenment crashes
On Fri, 26 Sep 2008 21:24:35 +1200 "Robin Paulson" <[EMAIL PROTECTED]> babbled: > 2008/9/26 The Rasterman Carsten Haitzler <[EMAIL PROTECTED]>: > > perhaps doing what it suggests might help? :) note - chances are whatever > > you have is likely behind the curve and possibly is segving as a result of > > inconsistent packages (eg svnrev of illume != svnrev of efl/e-wm). most > > likely. > > i flashed the new 2008.9 image a few days ago (i'd done an opkg > upgrade from 2008.8, but had been having the same problems, so went > from scratch and re-flashed), and have got the stock feeds - no extra > repos or anything, and i've done an opkg update && upgrade every day. > it's up to date now and still giving that message, so i doubt > anything's out of sync > > > so first check illume and evas, e-wm, edje, ecore, eet, embro, efreet, edbus > > are all the same svnrev. what svnrev is that? also installing -dbg (debug) > > ok, i did a check - all those packages (guess you mean embryo, not > embro?) are svnr 35818, with varying suffixes - r1/r2/r3/r4/r6/r12 illume as well? hmm. ok definitely behind the curve - i'm building 36262's currently. backtraces would be good! i dont use asu anymore. (fso stuff thouhg i've now been building stripped down images minus frameworkd and zhone etc. just to keep build sizes/times and flash times down). > > packages for these and gdb and gdb attaching and getting a backtrace will > > mean i can actually help you! :) > > right, installed the -dbg packages, and lots of dependencies too... > > i'm afraid the rest is beyond me - i read up a bit on gdb and > backtraces, but got lost around the use of file. any hints would be > great, or do you have a script ready-built that i could use? http://wiki.enlightenment.org/index.php/Debugging :) cunningly prepared i advance... :) > cheers for the help, appreciated > > ___ > support mailing list > support@lists.openmoko.org > https://lists.openmoko.org/mailman/listinfo/support > -- - Codito, ergo sum - "I code, therefore I am" -- The Rasterman (Carsten Haitzler)[EMAIL PROTECTED] ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: enlightenment crashes
On Fri, 26 Sep 2008 15:34:25 +1200 "Robin Paulson" <[EMAIL PROTECTED]> babbled: > and i just go it to print a different error message > "Enlightenment SIGABRT'd" > otherwise identical to the previous one with the SEGV'd perhaps doing what it suggests might help? :) note - chances are whatever you have is likely behind the curve and possibly is segving as a result of inconsistent packages (eg svnrev of illume != svnrev of efl/e-wm). most likely. so first check illume and evas, e-wm, edje, ecore, eet, embro, efreet, edbus are all the same svnrev. what svnrev is that? also installing -dbg (debug) packages for these and gdb and gdb attaching and getting a backtrace will mean i can actually help you! :) -- - Codito, ergo sum - "I code, therefore I am" -- The Rasterman (Carsten Haitzler)[EMAIL PROTECTED] ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: enlightenment crashes
On Fri, 26 Sep 2008 14:46:23 +1200 "Robin Paulson" <[EMAIL PROTECTED]> babbled: > is anyone else getting a lot of enlightenment crashes? my freerunner's > virtually unusable because of them - it usually recovers after the > crash, though not always, but it takes over a minute to sort itself > out. they usually happen whenever i use a qtopia app - messages is the > worst, but also contacts and dialler cause problems. i'm running the > stable branch, with most recent updates are you sure it's enlightenment and not qpe? zecke used the same "white box of death" code i have for e for catching qpe crashes and restarting it. carefully read the dialog. (i already had one person complain about e crashes when it actually was qpe. e also doesn't take a minute or so - e takes in the range of < 10 seconds (more like 5) to completely restart itself, which is why i wonder if you read the dialog. :) -- --------- Codito, ergo sum - "I code, therefore I am" -- The Rasterman (Carsten Haitzler)[EMAIL PROTECTED] ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [2008.8 updated] Illume keyboard, Where is Enter?
On Sun, 14 Sep 2008 01:27:58 +0200 yves mahe <[EMAIL PROTECTED]> babbled: > Carsten Haitzler (The Rasterman) wrote: > > On Fri, 12 Sep 2008 18:30:05 +0200 jollyr0ger <[EMAIL PROTECTED]> > > babbled: > > > >> Like the subject into the Raster's illume keyboard, where is the enter > >> button? > > the terminal layout has one (full qwerty kbd - minus function keys), or.. > > just slide your finger down. :) (any layout) > > > > > I discovered that and also that sliding up changes the keyboard. :) > > I have added this and all I have read on this keyboard in the wiki: > > http://wiki.openmoko.org/wiki/Illume#How_to_use_.28Raster.27s.29_keyboard_.3F > > Please, Rasterman, could you check if I have not forget something else. > > Yves MAHE i will be doing a full rundown on how all of it works.. just as soon as i clean up a bunch of loose ends. and right now i have a totally bizarre scrollframe bug i'm ploughing through... -- - Codito, ergo sum - "I code, therefore I am" -- The Rasterman (Carsten Haitzler)[EMAIL PROTECTED] ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [2008.8 updated] Illume keyboard, Where is Enter?
On Fri, 12 Sep 2008 18:30:05 +0200 jollyr0ger <[EMAIL PROTECTED]> babbled: > Like the subject into the Raster's illume keyboard, where is the enter > button? the terminal layout has one (full qwerty kbd - minus function keys), or.. just slide your finger down. :) (any layout) -- - Codito, ergo sum - "I code, therefore I am" -- The Rasterman (Carsten Haitzler)[EMAIL PROTECTED] ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Illume keyboard Disappeared
On Tue, 26 Aug 2008 16:00:08 -0400 Alex Fitzpatrick <[EMAIL PROTECTED]> babbled: > VictorSigma wrote: > > Armin ranjbar wrote: > > > > after running a few while , maybe after suspends , Illume keyboard does > > > not appear and standard om2008 keyboard appear , any one has any idea ? > > > > > > I myself asked this question recently.(Please search the mailing list before > > posting) > > http://n2.nabble.com/preserving-illume-keyboard-on-update-tp778734p778734.html > > > > link > > > > > > > But that thread has no answer either... Anyone know how to enable a full > keyboard with the new update? as best i know there is no way to turn qpe's keyboard off. until that happens there will always be fighting between illume's own keyboard and qpe's (As the vkbd system is generic allowing for any keyboard window - and illume just creates one of its own that gets picked up by the generic system). -- Carsten Haitzler (The Rasterman) <[EMAIL PROTECTED]> ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Illume config?
On Tue, 26 Aug 2008 21:12:50 +0430 Armin ranjbar <[EMAIL PROTECTED]> babbled: yes - because that "spanner" was never meant to be accessible or exist. it is sheer bi-product of the way asu was released that you could get it back through a theme change. so as such that illume-config theme is really a bug - or exposes a bug that was hidden. you can argue that "but that config gives me all sorts of useful stuff" etc. but that is not what om wanted - they explicitly did NOT want that config tool. (it's actually just part of e/illume - an internal dialog window). you can switch to the illume profile (the default profile changed to asu - see /etc/enlightenment/default_profile) and you'll get it back. > This this Really INVALID ? > > > On Tue, Aug 26, 2008 at 4:55 PM, Armin ranjbar <[EMAIL PROTECTED]> wrote: > > > Dear all , > > > > > > there was an application which configures menus , 'gadgets' , icon size > > > and ... of om2008 , i found that in the menu ( left up size , tool > > > shaped icon ) , i wonder which application does provide that since it > > > does appear that illume-config isn't it , any idea ? > > > > > > -- > > > Armin ranjbar , System Administrator > > > > > > ___ > > > support mailing list > > > support@lists.openmoko.org > > > https://lists.openmoko.org/mailman/listinfo/support > > > > > > > I filed a bug report on that one: > > https://docs.openmoko.org/trac/ticket/1863 it's closed... > > > > ___ > > support mailing list > > support@lists.openmoko.org > > https://lists.openmoko.org/mailman/listinfo/support > > > -- > Armin ranjbar , System Administrator > > ___ > support mailing list > support@lists.openmoko.org > https://lists.openmoko.org/mailman/listinfo/support -- Carsten Haitzler (The Rasterman) <[EMAIL PROTECTED]> ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: preserving illume keyboard on update
On Mon, 25 Aug 2008 15:36:12 +0200 Jelle De Loecker <[EMAIL PROTECTED]> babbled: > Interesting! > But "who" is openmoko? What group of persons decide this? And surely > they must know about this? this has been beaten to death on the community list already :) i am just trying to give people what they are saying they want - as best i can. > If not, and you want me to vent my frustration with the qpe keyboard > somewhere else, just give me an address! > I've made a list! :) hahahahaha! :) seriously - right now asu is still young. it wont be perfect. it's missing a lot. i have actually now got FSO building myself and am already sending patches to mickey for the FSO build that does use the illume keyboard. i intend to continue to support FSO over the long term and have a reasonable go at the gui end of things there while mickey & gang really hammer at the back end. > I just hope this doesn't turn into something like the > "gimp-in-one-window" struggle... > > Here's hoping for a good solution! if you ask me... try FSO. the phone bits are not that mature - but it's definitely got a future going for it. :) > Carsten Haitzler (The Rasterman) schreef: > > On Sun, 24 Aug 2008 01:53:47 +0200 Jelle De Loecker <[EMAIL PROTECTED]> > > babbled: > > > > the whole keyboard thing is a mess right now. illume has one - that > > seemingly people want. qpe has one that om wants. illume provides a gui > > config to turn it's keyboard on and off or launch a 3rd party vkbd app and > > use that. this gui is turned off by om and pretty much permanently > > inaccessible. qpe doesn't provide any way to say "yes" or "no" to getting > > its keyboard up. so basically qpe is playing the game of "take my keyboard > > or dont use qpe" right now, and illume is playing the game of "do what you > > want - i have config for that", but that game is pretty much inaccessible. > > > > there is a dbus call you can use to fiddle with some config but that > > incantation needs a dbus session key (so you'll need to steal it from a > > running session or do this with a terminal on the FR itself), but this > > still will only affect illume and do nothing about qpe. > > > > this all needs to be resolved and so it'll be a mess until it's cleared up. > > the wiki is not really correct - it's well behind any development and it's > > not really understanding how the keyboard works, but that has been changing > > rapidly > > ___ > support mailing list > support@lists.openmoko.org > https://lists.openmoko.org/mailman/listinfo/support -- Carsten Haitzler (The Rasterman) <[EMAIL PROTECTED]> ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: preserving illume keyboard on update
On Sun, 24 Aug 2008 01:53:47 +0200 Jelle De Loecker <[EMAIL PROTECTED]> babbled: the whole keyboard thing is a mess right now. illume has one - that seemingly people want. qpe has one that om wants. illume provides a gui config to turn it's keyboard on and off or launch a 3rd party vkbd app and use that. this gui is turned off by om and pretty much permanently inaccessible. qpe doesn't provide any way to say "yes" or "no" to getting its keyboard up. so basically qpe is playing the game of "take my keyboard or dont use qpe" right now, and illume is playing the game of "do what you want - i have config for that", but that game is pretty much inaccessible. there is a dbus call you can use to fiddle with some config but that incantation needs a dbus session key (so you'll need to steal it from a running session or do this with a terminal on the FR itself), but this still will only affect illume and do nothing about qpe. this all needs to be resolved and so it'll be a mess until it's cleared up. the wiki is not really correct - it's well behind any development and it's not really understanding how the keyboard works, but that has been changing rapidly. > There is a script on the wiki which enables you to install the full > qwerty keyboard, unfortunately the last file gives a 404, which makes it > rather useless. > > Is there a way, other then recompiling it, to get the good keyboard back? > > How does one get a dictionary for their own language, anyway? Or how do > you get an Azerty keyboard? > > /Met vriendelijke groeten,/ > > *Jelle De Loecker* > Kipdola Studios - Tomberg > > > > Russell Sears schreef: > > VictorSigma wrote: > > > >> I currently have the 20080823 openmoko-qtopia-x11-image-om-gta02.jffs2 > >> image flashed on my freerunner and it is working great. The problem is > >> that it originally comes with the illume keyboard pre-installed but > >> whenever I 'opkg update' the keyboard is changed to the qtopia version. Is > >> there anyway to preserve the illume keyboard or reinstall it after the > >> update? > >> > >> thanks > >> > > > > rasterman explained this already. qpe (the monolithic binary blob that > > makes phone calls) is hardcoded to start up its own keyboard. If qpe > > registers its keyboard first, then you don't get the illume one anymore. > > > > I think the fix is to break disable the qpe keyboard somehow. I've > > tried breaking it's config file, but that crashes qpe, breaking phone > > calls... I got a bit further than that, and think I found the code (51% > > sure...) that turns the qpe keyboard on, but now I don't have time to > > deal with it anymore. > > > > If you time to mess with it, consider rebuilding qpe with this patch > > removed: > > > > http://git.openmoko.org/?p=qtopia.git;a=commit;h=5a1a5204e9a4ace32dca98fdfd3b52b75592ee04 > > > > the diff: > > > > http://git.openmoko.org/?p=qtopia.git;a=blobdiff;f=src/server/phone/serverinterface/phonelauncher/phonelauncher_illume.cpp;h=405a0b654e9c34a390d18e3466242de5de1cc53d;hp=623258b15a27a969dd8a0926884792936f41103b;hb=5a1a5204e9a4ace32dca98fdfd3b52b75592ee04;hpb=38d2a3923ef46b12279901e5a5dc4c84aeae5d6e > > > > A better approach would add a config option to turn qpe's keyboard off. > > The long-term goal is to replace it with the illume one, but OM will be > > supporting the qpe keyboard in the near-term... > > > > -Rusty > > > > ___ > > support mailing list > > support@lists.openmoko.org > > https://lists.openmoko.org/mailman/listinfo/support > > > -- Carsten Haitzler (The Rasterman) <[EMAIL PROTECTED]> ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: 2007.02 ECORE ERROR: Ecore Magic Check Failed! Tut tut tut
On Tue, 19 Aug 2008 17:32:44 +0200 "arne anka" <[EMAIL PROTECTED]> babbled: > > Ok, it's from the /etc/rcS.d/S01exquisite. Both S01exquisite and > > S01psplash > > search for splash=false resp. psplash=false in /proc/cmdline and as none > > which one is responsible for the ugly boots? exquisite does the first boots (with the 0->100% progress). it's a theme file (.edj) so can be re-themed to be anything you like. the 2nd is enlightenment's splash screen - same image just the green bar bouncing (and e doesn't track any percentage complete. it just knows its buys and does have status messages that the init splash doesn't show though). again. edj (edje) file. themable. :) -- Carsten Haitzler (The Rasterman) <[EMAIL PROTECTED]> ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Closing applications in ASU
On Sun, 27 Jul 2008 21:32:52 +0200 Sven Klomp <[EMAIL PROTECTED]> babbled: > On Sunday 27 July 2008 16:29:33 Carsten Haitzler wrote: > > On Sat, 26 Jul 2008 20:52:11 +0530 "rakshat hooja" <[EMAIL PROTECTED]> > babbled: > > > Pressing the power button for a split second should close the > > > application. Am not running ASU at the monment but it does so in 2007.2 > > > and qtopia so its likely it does that in ASU too. > > > > no. in asu press power button suspends immediately. press and hold power > > button shuts system down. > > Does it suspend or only dim LCD? It looks different than apm -s to me. suspend = (well dim then about 1 second later suspend). it REQUESTS a suspend tho - this can be blocked by qpe for one reason or another. if the suspend it blocked all you get is a screenblank. if it isnt - its blank then suspend almost instantly. -- Carsten Haitzler (The Rasterman) <[EMAIL PROTECTED]> ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Closing applications in ASU
On Sat, 26 Jul 2008 21:20:12 +0530 "sparky mat" <[EMAIL PROTECTED]> babbled: remove does close it - *IF* the application responds to delete requests - if it decides not to close itself (if it advertises talking the WM_DELTETE protocol). if it doesn't say it speaks this protocol - the client connection is terminated. i'd be majorly surprised that this doesn't work. this is the same code that closes windows in e on the desktop - and it has over many years... never failed. it works for me right now in ASU. all i can imagine is that your ASU is some broken build with broken lib versions etc, or the application is just refusing to close. > I don't think remove closes it. I keep doing that, but it just takes me to > Home. If i check the dropdown, the app's still there. > > On Sat, Jul 26, 2008 at 8:59 PM, Yorick Moko <[EMAIL PROTECTED]> wrote: > > > On Sat, Jul 26, 2008 at 5:16 PM, sparky mat <[EMAIL PROTECTED]> wrote: > > > How do I close applications in ASU? > > > > > > For example, I am in Assassin and the only way to go to Home is by > > selecting > > > it from the drop-down on top (??) . How do I close it? I noticed that > > some > > > apps have an 'x' for closing them. Is there a uniform way of closing > > them? > > > > > > ___ > > > support mailing list > > > support@lists.openmoko.org > > > https://lists.openmoko.org/mailman/listinfo/support > > > > > > > > > > in the left buttom of the dropdown there is a "remove" button > > this will close the application > > > > ___ > > support mailing list > > support@lists.openmoko.org > > https://lists.openmoko.org/mailman/listinfo/support > > > -- Carsten Haitzler (The Rasterman) <[EMAIL PROTECTED]> ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Closing applications in ASU
On Sat, 26 Jul 2008 20:52:11 +0530 "rakshat hooja" <[EMAIL PROTECTED]> babbled: > On Sat, Jul 26, 2008 at 8:46 PM, sparky mat <[EMAIL PROTECTED]> wrote: > > > How do I close applications in ASU? > > > > For example, I am in Assassin and the only way to go to Home is by > > selecting it from the drop-down on top (??) . How do I close it? I noticed > > that some apps have an 'x' for closing them. Is there a uniform way of > > closing them? > > > > > Pressing the power button for a split second should close the application. > Am not running ASU at the monment but it does so in 2007.2 and qtopia so > its likely it does that in ASU too. no. in asu press power button suspends immediately. press and hold power button shuts system down. -- Carsten Haitzler (The Rasterman) <[EMAIL PROTECTED]> ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: events/0 uses 25% of CPU, avahi-daemon uses 9% (bluetooth problem?)
On Sun, 27 Jul 2008 10:25:02 +0200 Mikael Berthe <[EMAIL PROTECTED]> babbled: > * Russell Sears <[EMAIL PROTECTED]> [2008-07-19 03:21 +0200]: > > Today events/0 was using 25% of CPU, avahi-daemon, 9% > > > > From what I can tell, there's nothing interesting in dmesg or logread. > > This is on a factory image + opkg upgrade as of last night. > > Same here, > PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND > 5 root 15 -5 000 R 31.0 0.0 67:27.00 events/0 > > Just wondering if there's a way to fix that without rebooting... > Any idea? i have found that it can go away if u suspend and resume again... so it's some wakeup issue from suspend... i suspect. -- Carsten Haitzler (The Rasterman) <[EMAIL PROTECTED]> ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: REMOVE
On Fri, 25 Jul 2008 15:05:19 +0100 "Robin Paulson" <[EMAIL PROTECTED]> babbled: > 2008/7/24 Steven ** <[EMAIL PROTECTED]>: > > If you figured out how to subscribe to the list, you should have no > > problem unsubscribing. > > https://lists.openmoko.org/mailman/listinfo/support > > the problem is, no matter how many times people quote that wonderful > link, it still doesn't work. > have you tried clicking on it yourself? yes. after i agree to the security exception i get the mailman unsubscribe page with forms. and down the bottom is the unsusbscribe stuff... of course i'm not going to do it. i want to remain subscribed :) -- Carsten Haitzler (The Rasterman) <[EMAIL PROTECTED]> ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Does it make sense to have the kernel use a swap partition?
gt; Htop is quite good at showing all three uses of memory, well worth a look. > > > > Don't know how accurate it is though. Any thoughts on that? > > > > Nils > > > > ___ > > support mailing list > > support@lists.openmoko.org > > https://lists.openmoko.org/mailman/listinfo/support > > > -- Carsten Haitzler (The Rasterman) <[EMAIL PROTECTED]> ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Keyboard not working on latest ASU
On Wed, 23 Jul 2008 15:50:44 +0200 "Torfinn Ingolfsen" <[EMAIL PROTECTED]> babbled: > Hi, > > On Wed, Jul 23, 2008 at 2:28 PM, The Rasterman Carsten Haitzler > <[EMAIL PROTECTED]> wrote: > > and it will continue to be there/not there between svn versions. qtopia has > > its own vkbd and illume has one - they conflict and right now i can only > > turn off the illume one in code. so depending what svnrev u get it may or > > may not be enabled or conflict etc. etc. - u'll have to wait for dust to > > settle. > > In the future, could it be possible to have a configurable keyboard? > - I install three keyboards I like (or all available keyboards) > - I configure somewhere (a .conf file in /etc maybe?) which keyboard I > prefer, this is the keyboard that appears whenever a keyboard i needed > Additionally, all keyboards have a way to switch to another keyboard > (menu?, extra key?) so that I can switch whenever I want, even in mid > sentence. yes. configuring which keyboard comes up is on my todo list. it's almost there - i am adding in config fields and then e will handle executing the keyboard 0 if it needs executing, or be able to use its internal one (its not a separate process, so it comes with less overhead), or have no keyboard at all... thats my plan anyway... -- Carsten Haitzler (The Rasterman) <[EMAIL PROTECTED]> ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Keyboard not working on latest ASU
On Wed, 23 Jul 2008 13:07:22 +0200 "Torfinn Ingolfsen" <[EMAIL PROTECTED]> babbled: > Hello, > > On Wed, Jul 23, 2008 at 2:13 PM, Ole Kliemann > <[EMAIL PROTECTED]> wrote: > > But right now[1], I don't get a keyboard at all. > > > > [1] > > http://buildhost.openmoko.org/daily/freerunner/200807/20080722/openmoko-qtopia-x11-image-om-gta02.jffs2 > > illume is rev152 in this image. > > I can confirm this - I just did an 'opkg upgrade -force-overwrite' > even after I was warned. And no the keyboard never shows up (test with > PIN code dialog, contacts application). > Is there a way to "roll back" to a known working version? and it will continue to be there/not there between svn versions. qtopia has its own vkbd and illume has one - they conflict and right now i can only turn off the illume one in code. so depending what svnrev u get it may or may not be enabled or conflict etc. etc. - u'll have to wait for dust to settle. -- Carsten Haitzler (The Rasterman) <[EMAIL PROTECTED]> ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Keyboard not working on latest ASU
On Sat, 19 Jul 2008 13:43:54 + Ole Kliemann <[EMAIL PROTECTED]> babbled: > After `opkg update ; opkg upgrade' on my FR using ASU this morning, the > onscreen keyboard is broken. It is still displayed and when striking a > key the letter is raised but nothing more; the input is not working. > Also the `drag-up-gesture' for switching the layout to numbers is not > working. > > Problem resides when reflashing with: > > http://buildhost.openmoko.org/daily/freerunner/200807/20080718/uImage-om-gta02-latest.bin > http://buildhost.openmoko.org/daily/freerunner/200807/20080718/openmoko-qtopia-x11-image-om-gta02.jffs2 i'm in the middle of a full kbd rewrite... it's all functional now... with latest svn (rev151) for sure, but dictionary lookup is not working (havent done that yet). -- Carsten Haitzler (The Rasterman) <[EMAIL PROTECTED]> ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
