**** BEGIN LOGGING AT Sat Sep 14 02:59:59 2013
Sep 14 05:07:03 <alabd> Good day all , does SHR have security lock(with password) for idle times ? if yes where to get latest stable shr and if no which os on FR do that ?
Sep 14 05:37:58 <lindi-> alabd: what do you want the security lock to prevent?
Sep 14 06:02:17 <alabd> lindi-: hi , to prevent someone reads sms and contacts
Sep 14 06:03:31 <alabd> lindi-: u there ? 
Sep 14 09:01:29 <txasatonga> sdl 2.0 vala vapi-bindings in gitorious, someone wont help for finnish them
Sep 14 09:21:31 <txasatonga> they are at : https://gitorious.org/sdl-2-0-vala-vapi
Sep 14 09:21:43 <txasatonga> someone interested?
Sep 14 09:22:02 <txasatonga> quit
Sep 14 10:47:44 <alabd> lindi-: ping
Sep 14 10:58:27 <lindi-> alabd: ?
Sep 14 10:59:35 <alabd> i have bought a new micro sd card , but how to create a ext3 partition on it with fdisk (gparted returns error )
Sep 14 11:05:24 <lindi-> alabd: there are at least two different fdisk programs
Sep 14 11:05:31 <lindi-> alabd: both are called 'fdisk'
Sep 14 11:05:44 <alabd> anyone you know
Sep 14 11:05:53 <alabd> i have fdisk cfdisk 
Sep 14 11:06:25 <lindi-> cfdisk is third program
Sep 14 11:07:07 <alabd> fdisk -l shows 
Sep 14 11:07:08 <alabd>    Device Boot      Start         End      Blocks   Id  System
Sep 14 11:07:09 <alabd> /dev/sdc1              13        9415     3835904   83  Linux
Sep 14 11:07:25 <alabd> but how to format it in ext3
Sep 14 11:07:41 <alabd> i wana install shr oon it
Sep 14 11:08:04 <lindi-> alabd: format = create filesystem, you do that with mkfs
Sep 14 11:08:36 <lindi-> alabd: mkfs -t ext3 ...
Sep 14 11:08:51 <alabd> yes
Sep 14 11:09:26 <lindi-> alabd: if you want something easy to use you could use disk utility from gnome
Sep 14 11:09:37 <alabd> i used gparted
Sep 14 11:09:39 <alabd>  but error
Sep 14 11:10:35 <alabd> sudo mkfs -t ext3 /dev/sdc1
Sep 14 11:10:35 <alabd> seems good
Sep 14 11:12:54 <alabd> lindi-: solved , now after mounting sd1 i shoud unzip shr.tar.gz on it yes?
Sep 14 11:13:38 <lindi-> alabd: I have no idea on installing shr like that sorry
Sep 14 11:14:39 <JaMa> alabd: yes you just unpack the image, but don't forget to use --numeric-owner parameter for tar
Sep 14 11:14:52 <alabd> JaMa: yes sure thanks
Sep 14 11:26:26 <alabd> JaMa: ok i have unzipped it
Sep 14 11:27:31 <alabd> and i have put it in fr 
Sep 14 11:27:36 <alabd> but it does not boot 
Sep 14 11:27:40 <alabd> why ?
Sep 14 11:28:06 <JaMa> -ENOTENOUGHINFORMATION
Sep 14 11:29:48 <alabd> ?
Sep 14 11:30:12 <lindi-> JaMa: he wants to know what boot loader you are using, where it is installed and how it is configured
Sep 14 11:31:55 <alabd> lindi-: how to say it 
Sep 14 11:37:44 <lindi-> alabd: I guess that means you don't know :/
Sep 14 11:37:54 <alabd> :P yes
Sep 14 11:37:58 <alabd> how to guess it
Sep 14 11:38:21 <lindi-> sudo strings /dev/mtd1 | grep Bootloader
Sep 14 11:38:38 <lindi-> alabd: better try to follow some shr instructions
Sep 14 11:38:45 <lindi-> if you can find them
Sep 14 11:41:05 <alabd> where to get a proper bootloader ?
Sep 14 11:46:52 <lindi-> alabd: I have no idea what SHR people consider to be proper bootloader
Sep 14 11:47:24 <R-Day> lindi-: and whay ppl are u then?
Sep 14 11:47:32 <R-Day> *what
Sep 14 11:49:53 <alabd> lindi-: JaMa i have boot qi image on NAND but shr does not boot yet
Sep 14 11:50:11 <lindi-> R-Day: http://wiki.openmoko.org/wiki/User:Lindi documents my setup
Sep 14 11:51:10 <alabd> JaMa: i've done it sudo dfu-util -a u-boot -R -D qi.udfu
Sep 14 11:58:36 <R-Day> lindi-: thx, I see you're using qi; if I want to install qi then I have to flash both qi+kernel image?
Sep 14 12:00:26 <lindi-> R-Day: I haven't flashed any kernels to NAND, it's in SD card
Sep 14 12:00:32 <alabd> any opinion ?
Sep 14 12:03:49 <alabd> JaMa: my boot loader is qi and it boots shr on sd card ...but boot stops at login: ....
Sep 14 12:06:28 <R-Day> lindi-: was just asking since, qi's official page states this: "After downloading the kernel and bootloader they can be flashed to your device..." and in the download section u have qi-s3c2442-bootmenu-0.1.udfu & uImage-GTA02-bootmenu-0.2.bin, so I didn't know if this kernel is required specifically for proper qi operation
Sep 14 12:07:25 <R-Day> alabd: you're trying to run shr from sd card?
Sep 14 12:07:46 <alabd> yes 
Sep 14 12:08:11 <R-Day> and what u have flashed on the phone?
Sep 14 12:09:25 <alabd> R-Day: qtmoko or android i don;t remember exactly , that also does not boot
Sep 14 12:09:57 <R-Day> then why i don't flash shr to the phone?
Sep 14 12:10:02 <R-Day> *u
Sep 14 12:10:36 <alabd> why not on sd card ?
Sep 14 12:11:09 <R-Day> I think it's loading faster, but I might be wrong
Sep 14 12:11:24 <lindi-> R-Day: "qi's official page" is quite interesting concept :)
Sep 14 12:12:08 <lindi-> R-Day: it might refer to some kexec boot menu kernel which I don't think caught on
Sep 14 12:12:38 <alabd> R-Day: which one is more stable ?> shr-2012.07 ...shr-core ...shr-core-staging..shr-unstable ...
Sep 14 12:13:03 <R-Day> alabd: use the core version
Sep 14 12:14:27 <R-Day> lindi-: ok then, if I like to install qi then from where and which version should I grab it? :)
Sep 14 12:14:30 <alabd> R-Day: which one ubifs or jffs2 ?
Sep 14 12:14:47 <R-Day> jffs2
Sep 14 12:16:48 <alabd> R-Day: didn't you understand why it does not boot from sd card ?
Sep 14 12:18:14 <lindi-> R-Day: that depends on the distro
Sep 14 12:19:22 <R-Day> nope, sry, I don't know what u meant by this "but boot stops at login: ....", shr doesn't has a login
Sep 14 12:20:43 <R-Day> if u can describe the screen, mention some message on the screen, where the boot process stops then maybe I can help u
Sep 14 12:25:40 <alabd> R-Day: when shr is going to boot , it stops at line debugfs dir creatiom failed -19 shr ..om-gta02 tty1 ...
Sep 14 12:25:52 <alabd> om-gta02 login :
Sep 14 12:26:21 <R-Day> oh i see
Sep 14 12:30:23 <R-Day> unfortunately I don't know why that dir creation fails
Sep 14 12:37:48 <R-Day> alabd: are u still here?
Sep 14 12:37:57 <alabd> sure
Sep 14 12:48:09 <alabd> R-Day: ping
Sep 14 12:50:46 <JaMa> which image you were trying to install and failed to boot to gui?
Sep 14 12:51:29 <R-Day> alabd: I think it's better to start it over, format the sd card to ext2
Sep 14 12:51:36 <alabd> JaMa: http://build.shr-project.org/shr-2012.07/images/om-gta02/shr-image-om-gta02.tar.gz
Sep 14 12:51:47 <alabd> R-Day: it is ext3
Sep 14 12:52:24 <JaMa> that one should work as it's stable image
Sep 14 12:55:39 <R-Day> my advice is to re-format the sd card and uncompress this release to the card
Sep 14 12:55:43 <R-Day> http://build.shr-project.org/shr-core/images/om-gta02/shr-image-om-gta02.tar.gz
Sep 14 12:57:28 <alabd> i try it with ext2
Sep 14 12:57:50 <R-Day> it should work with both actually
Sep 14 13:00:32 <R-Day> JaMa: any chance that u use qi bootloader?
Sep 14 13:10:44 <JaMa> R-Day: yes I'm using qi
Sep 14 13:12:24 <R-Day> JaMa: I'm still using u-boot, which version of qi u recommend and from where I should get it?
Sep 14 13:20:53 <alabd> which one is older? http://build.shr-project.org/shr-core/images/om-gta02/shr-image-om-gta02.tar.gz  or  http://build.shr-project.org/shr-2012.07/images/om-gta02/shr-image-om-gta02.tar.gz
Sep 14 13:25:10 <R-Day> it seems that both addresses link to the same dir on the server, so it doesn't matter which u gonna download :)
Sep 14 13:31:07 <alabd> R-Day: no they are not the same one is 2012 and one is shr-core
Sep 14 13:31:09 <alabd> anyway
Sep 14 13:31:25 <alabd> R-Day: why there is no sms app in apps ?
Sep 14 13:32:39 <R-Day> but that's only in the url, trust me, I checked the md5 sum
Sep 14 13:33:21 <R-Day> so did u managed to to install?
Sep 14 13:33:33 <alabd> no i have booted from sd card
Sep 14 13:34:52 <R-Day> I meant install to sd, more exactly uncompress it and boot it, my mistake, wansn't precise
Sep 14 13:35:29 <alabd> yes it is booted now
Sep 14 13:35:30 <alabd> i went to apps
Sep 14 13:35:36 <alabd> but there is no sms manager app there
Sep 14 13:36:04 <R-Day> I do have an app named Messages for sms
Sep 14 13:36:17 <R-Day> it's there by default
Sep 14 13:36:45 <alabd> R-Day: would you check your shr built date ?
Sep 14 13:37:08 <alabd> in setting > others
Sep 14 13:38:08 <R-Day> 20130426, branch:danny
Sep 14 13:39:33 <alabd> the same
Sep 14 13:40:07 <R-Day> what's the last app name u see
Sep 14 13:40:28 <alabd> htop
Sep 14 13:41:36 <R-Day> above htop is Dialer and beside that is Messages
Sep 14 13:51:08 <alabd> i can't se it ,
Sep 14 13:51:10 <alabd> anyway
Sep 14 13:51:14 <alabd> thanks R-Day
Sep 14 13:51:18 <alabd> i should go
Sep 14 13:51:26 <alabd> bye
Sep 14 13:51:46 <R-Day> bye
Sep 14 21:10:45 <Thamos> i am just now installing the new shr-core-latest-124.
Sep 14 21:15:59 <JaMa> good
Sep 14 21:16:06 * JaMa hopes it works
Sep 14 21:35:24 <jake42> englightenment segfaults on first boot after/while doing ts-calibration on GTA04
Sep 14 22:08:49 <Thamos> damn it, i have to solve some trouble at my hostmachine first....
Sep 14 22:49:23 <Thamos> ok, wifi is working, have updated without my hostmachine :)
Sep 14 23:00:05 <Thamos> for gta02 there is bug 2095 still annoying. Maybe somebody should look over the supplied patch? http://www.shr-project.org/trac/attachment/ticket/2095/phonefsod.patch
Sep 14 23:00:18 <dos1> Thamos: wifi on gta02?
Sep 14 23:00:26 <Thamos> yeah
Sep 14 23:00:51 <Thamos> gta04 would be nice ^^
Sep 14 23:01:13 <dos1> wifi doesn't work on my gta02 since ages
Sep 14 23:01:22 <dos1> (but well, never really tried to resurrect it)
Sep 14 23:01:31 <Thamos> it very unstbable
Sep 14 23:01:50 <Thamos> i had tried several times
Sep 14 23:02:02 <dos1> few years ago i've been using it daily without issues
Sep 14 23:02:22 <dos1> sometimes wmiconfig --power maxperf was needed, but other than that it was ok
Sep 14 23:02:51 <dos1> now it shows garbage in iwconfig after trying to connect...
Sep 14 23:02:54 <Thamos> to me it seems like an kernel issue... Sometimes the dhcpc simpliy can't reach the  router
Sep 14 23:03:11 <Thamos> maybe wpa_supplicant
Sep 14 23:03:42 <Thamos> this time i had to first power it on manually
Sep 14 23:03:52 <dos1> I guess no one is really interested in fiddling with gta02 kernel nowadays
Sep 14 23:04:27 <Thamos> yeah, but there seem to be quite some bugs in 2.6.39.4
Sep 14 23:05:37 <Thamos> but maybe i am wrong.
Sep 14 23:05:48 <Thamos> i am not that deep in this stuff.
Sep 14 23:06:21 <Thamos> dos1: may you have a look about bug 2095 _
Sep 14 23:06:22 <Thamos> ?
Sep 14 23:06:53 <dos1> this bug doesn't happen here
Sep 14 23:07:05 <dos1> but if that patch fixes it for you, i guess i can commit it
Sep 14 23:08:08 <Thamos> doesn't happen by you?
Sep 14 23:08:17 <dos1> hmm
Sep 14 23:08:25 <dos1> I don't really understand that patch
Sep 14 23:08:35 <Thamos> i have a big contacts and sms-list, maybe this is cause
Sep 14 23:08:58 <dos1> on sim?
Sep 14 23:09:12 <Thamos> no, in opim
Sep 14 23:09:19 <dos1> that shouldn't matter
Sep 14 23:09:44 <Thamos> line 177 in orig. file got called to late
Sep 14 23:10:11 <dos1> i've seen it few times (repeating pin dialog), but loooong time ago
Sep 14 23:10:34 <Thamos> at my place its happening now...
Sep 14 23:11:33 <Thamos> problem is, that in line 178 it doesn't check, if the dialog is already displayed
Sep 14 23:11:47 <Thamos> only one time in 177.
Sep 14 23:12:02 <Thamos> so it got repeated indifinitly
Sep 14 23:12:51 <Thamos> i have created some extra function, which got called, that checks first.
Sep 14 23:12:58 <dos1> yeah, i see
Sep 14 23:13:18 <Thamos> but i got no clue of this stuff bevor i begun.
Sep 14 23:13:25 <dos1> i guess you don't need sim_auth_needed in that if in 188?
Sep 14 23:13:33 <Thamos> so my idea might be unecessary complicated.
Sep 14 23:13:45 <dos1> as it's checked one if above
Sep 14 23:14:30 <Thamos> yeah, this could be an elif
Sep 14 23:14:45 <Thamos>  with phoneui.notification only
Sep 14 23:14:51 <dos1> why do we need that timeout there at the first place?
Sep 14 23:15:20 <dos1> i know you're not the best person to ask that, but any idea? :D
Sep 14 23:15:51 <Thamos> yeah, i though about that, too.
Sep 14 23:16:10 <Thamos> but already some weeks ago... 
Sep 14 23:16:32 <Thamos> i think phonefsod could be started faster/earlier than phoneui
Sep 14 23:16:47 <dos1> this is _on_phoneuid_appeared
Sep 14 23:17:20 <Thamos> in prinziple....
Sep 14 23:18:10 <Thamos> i don't know exaclty, but i think phouneuid was not really ready, when it appeared on bus.
Sep 14 23:18:11 <dos1> maybe it was supposed to just run once, after 2 seconds delay?
Sep 14 23:18:21 <dos1> but heck, why doesn't it happen here?
Sep 14 23:18:23 <dos1> oh
Sep 14 23:18:25 <dos1> i know
Sep 14 23:18:35 <dos1> stupid me :)
Sep 14 23:18:51 <dos1> i have automatic pin unlock :D
Sep 14 23:19:19 <dos1> it doesn't show for me at all, so obviously i couldn't notice this problem :D
Sep 14 23:19:40 <Thamos> ^^
Sep 14 23:19:43 <dos1> lemme disable it and check...
Sep 14 23:20:02 <Thamos> i have to check full source, to counter your argument...
Sep 14 23:24:41 <dos1> well, it didn't happen to me anyway
Sep 14 23:24:46 <Thamos> hm, ok, i don't know why, but showing sim might fail because phoneuid is not on the bus despite of _on_phoneuid_appeared
Sep 14 23:25:14 <dos1> so time for some phoneuid killing? ;)
Sep 14 23:25:29 <Thamos> maybe this should be investigated further and my patch only some workaround.
Sep 14 23:25:43 <Thamos> ^^
Sep 14 23:26:06 <Thamos> hm. i wanted to go to bed next time...
Sep 14 23:27:20 <dos1> right
Sep 14 23:27:45 <Thamos> can you reproduce it now?
Sep 14 23:27:45 <dos1> when phoneuid launched after pin dialog should be displayed, it happens
Sep 14 23:28:41 <dos1> let's see the code...
Sep 14 23:28:57 <dos1> my first guess how to fix it would be to just remove timeout and call _show_sim_auth directly
Sep 14 23:30:55 <Thamos> i have thought about that, too. But I came up with some scenaria against it.
Sep 14 23:31:06 <Thamos> But i don't know it anymore :(
Sep 14 23:31:46 <Thamos> i guess, than no pin would be showed, if phoneuid is loaded later
Sep 14 23:31:55 <dos1> nope
Sep 14 23:32:09 <dos1> in that case,  	_gsm_device_status_handler shows it
Sep 14 23:32:31 <dos1> and there is no timeout
Sep 14 23:33:03 <Thamos> yeah, because of that i got bug 2094...
Sep 14 23:33:18 <Thamos> some times.
Sep 14 23:33:22 <dos1> it was introduced in commit 4aef4d6932470af32037d0645839e9c4a5057b2e by mrmoku
Sep 14 23:33:47 <dos1> from commit message it seems that what he meant was to just delay that call
Sep 14 23:33:53 <dos1> not repeat it over and over :)
Sep 14 23:34:16 <dos1> it was meant to fix #1478
Sep 14 23:35:02 <Thamos> hm, ok.
Sep 14 23:35:31 <dos1> ok, so I suppose return TRUE; in _show_sim_auth should be enough to fix it
Sep 14 23:35:56 <Thamos> but i have seen the need in my logs
Sep 14 23:35:57 <dos1> s/TRUE/FALSE/
Sep 14 23:35:58 <apt> dos1 meant: ok, so I suppose return FALSE; in _show_sim_auth should be enough to fix it
Sep 14 23:36:11 <Thamos> see line 63 of http://www.shr-project.org/trac/attachment/ticket/2095/phonefsod.log
Sep 14 23:36:57 <dos1> Thamos: that's the line from  _gsm_device_status_handler
Sep 14 23:36:59 <Thamos> ok, but this one is from the  _gsm_device_status_handler
Sep 14 23:37:12 <Thamos> yeah, just seen ^^
Sep 14 23:37:29 <Thamos> so _gsm_device_status_handler needs a bigger timeout
Sep 14 23:37:30 <dos1> Thamos: then there's 66, which comes from _on_phoneuid_appeared
Sep 14 23:37:59 <Thamos> yes
Sep 14 23:37:59 <dos1> so everything's fine, just "return FALSE;"
Sep 14 23:38:26 <dos1> naugthy mrmoku! :)
Sep 14 23:38:28 <dos1> ~seen mrmoku
Sep 14 23:38:29 <apt> mrmoku <~mrmoku@ppp-188-174-133-85.dynamic.mnet-online.de> was last seen on IRC in channel #openmoko-cdevel, 256d 21h 55m 23s ago, saying: ':)'.
Sep 14 23:38:37 <dos1> hmm, pretty long
Sep 14 23:39:32 <Thamos> hm, not good.
Sep 14 23:40:17 <Thamos> i would increase the timeout to 5 seconds and then return false.
Sep 14 23:40:41 <dos1> it's not clear why this timeout is needed at all
Sep 14 23:40:43 <Thamos> an gsm_handler should get a timeout, too?
Sep 14 23:41:00 <dos1> no, it was introduced just to workaround some dbus activation issue
Sep 14 23:41:14 <Thamos> true. Shouldn't be needed.
Sep 14 23:41:29 <dos1> for some reason call to phoneuid on faster machines was failing right after it appeared on bus
Sep 14 23:42:17 <Thamos> and now seems to be on freerunner as well.
Sep 14 23:44:04 <Thamos> Will you prepare a new workaround-patch for 2094/2095 as said?
Sep 14 23:44:29 <dos1> Thamos: http://git.shr-project.org/git/?p=phonefsod.git;a=commit;h=c9f45e299562a28f496786b8e3902d6106cef145 :)
Sep 14 23:44:34 <Thamos> i want to go to bed now, and i think i got no time for at least 5 days...
Sep 14 23:44:59 <Thamos> k
Sep 14 23:45:20 <Thamos> what abaout 2094? I think gsm_handler needs a timeout, too...
Sep 14 23:45:58 <Thamos> don't you?
Sep 14 23:46:39 <dos1> hm
Sep 14 23:46:50 <dos1> right, from this log it seems so
Sep 14 23:53:59 <dos1> i wonder if that's not some phoneuid bug
Sep 14 23:54:29 <Thamos> that it's not really ready?
Sep 14 23:54:39 <dos1> yup
Sep 14 23:54:53 <dos1> maybe it registers on dbus too early, or something like that
Sep 14 23:55:02 <Thamos> may be.
Sep 14 23:55:10 <Thamos> i got no clue
Sep 14 23:55:52 <Thamos> hey dos, when i want to get newest fsogsmd, how is the fastest way to compile it?
Sep 14 23:56:08 <dos1> shr-chroot and bitbake
Sep 14 23:56:22 <Thamos> is it enough to insert the commit number in some file?
Sep 14 23:56:32 <dos1> yup, cornucopia.inc IIRC
Sep 14 23:57:01 <dos1> or you can ask me to send you my ipks, if you trust binaries from me ;)
Sep 14 23:57:02 <Thamos> ok, i am really annoyed by the bugs that are solved already...
Sep 14 23:57:31 <Thamos> would be nice
Sep 15 00:07:43 <Thamos> ok, time is out, i am off then.
Sep 15 00:07:58 <Thamos> dos1
Sep 15 00:08:02 <Thamos> goodbye.
Sep 15 00:08:09 <dos1> cya
Sep 15 00:08:12 <Thamos> ahm, and thanks a lot
Sep 15 00:08:26 <Thamos> for your help. i nearly forgot ^^
Sep 15 00:08:35 <dos1> yw
Sep 15 00:33:47 <dos1> JaMa: bumped SRCREV of phonefsod in shr branch
Sep 15 00:34:16 <dos1> JaMa: I think we should also consider using cornucopia from latest git rev
Sep 15 00:36:21 <dos1> I'm voting for (it works well on my device and it fixes some really annoying problems), but I'll leave final decision to you
**** ENDING LOGGING AT Sun Sep 15 02:59:59 2013