**** BEGIN LOGGING AT Wed Jan 08 02:59:59 2014
Jan 08 03:02:35 <Sysaxed> robink: so is there any way to convert it?
Jan 08 03:02:38 <robbiethe1st> also, mic button?
Jan 08 03:03:42 <Sysaxed> yeah, that small button that is usually used for answering the call
Jan 08 03:04:03 <Sysaxed> why did I call it mic button :D
Jan 08 03:07:50 <robbiethe1st> wait... what button?
Jan 08 03:08:14 <robbiethe1st> Where is it?
Jan 08 03:10:21 <Sysaxed> on the cord of the headphones
Jan 08 03:17:28 <robbiethe1st> Oh
Jan 08 03:17:46 <robbiethe1st> um... I got one of those a while back. Never could get it to work
Jan 08 03:20:28 <DocScrutinizer05> FIQ: probably the maemo-launcher
Jan 08 03:23:19 <Sysaxed> robbiethe1st: yep, it does not work with n900
Jan 08 03:23:36 <Sysaxed> robbiethe1st: I remember somebody was trying to make it work... not sure if he succeeded
Jan 08 03:23:41 <robbiethe1st> If you're handy with a soldering iron, you could probably bypass all the electronics
Jan 08 03:23:45 <Sysaxed> robbiethe1st: but I don't care about it, I want my mic to work
Jan 08 03:24:15 <DocScrutinizer05> FIQ: where do you see 2 processes? are you sure that's not 2 threads?
Jan 08 03:27:14 <FIQ> unless I'm mistaken (I've never done any multithreaded developing), seperate threads don't get their own PID
Jan 08 03:27:23 <FIQ> but I might just be wrong
Jan 08 03:28:37 <FIQ> robbiethe1st: 
Jan 08 03:28:43 <robbiethe1st> ?
Jan 08 03:29:01 <FIQ> top right of backupmenu's UI has a "-" rather than a "|"
Jan 08 03:29:14 <FIQ> kinda nitpicking but still :p
Jan 08 03:29:24 <DocScrutinizer05> sorry, I lookd for the wrong thing
Jan 08 03:29:28 <DocScrutinizer05> you're right
Jan 08 03:29:47 <robbiethe1st> Huh
Jan 08 03:29:52 <robbiethe1st> Never noticed it
Jan 08 03:30:04 <FIQ> I can't take my eyes from that "error" when I have it running D:
Jan 08 03:30:11 <DocScrutinizer05> well, you're right it's 2 hildon-home processes for example. Threads indeed get their own PID
Jan 08 03:30:25 <robbiethe1st> So edit the shell-script file?
Jan 08 03:30:31 <FIQ> DocScrutinizer05: mkay.. so why does it do that?
Jan 08 03:30:34 <robbiethe1st> It's not like it's encrypted or compiled or anything
Jan 08 03:30:45 <FIQ> robbiethe1st: where is it located?
Jan 08 03:30:57 <DocScrutinizer05> as I guessed: maemo-launcher?
Jan 08 03:30:58 <FIQ> nvm I guess I can just check with dpkg
Jan 08 03:30:59 <robbiethe1st> Um, /usr/share/backupmenu/BackupMenu.item
Jan 08 03:31:08 <FIQ> ty
Jan 08 03:31:08 <robbiethe1st> you want the non-launcher one
Jan 08 03:31:32 <DocScrutinizer05> err invoker
Jan 08 03:31:35 <DocScrutinizer05> IroN900:~# ll `which hildon-home`
Jan 08 03:31:36 <robbiethe1st> should be just a string, which is passed to text2screen/t2s
Jan 08 03:31:37 <DocScrutinizer05> lrwxrwxrwx 1 root root 22 2012-07-18 23:07 /usr/bin/hildon-home -> /usr/bin/maemo-invoker
Jan 08 03:31:51 <FIQ> DocScrutinizer05: ah ok
Jan 08 03:32:37 <DocScrutinizer05> maemo-invoker impersonates a lot of stuff, and calls hildon-home-real or whatever the name
Jan 08 03:33:34 <DocScrutinizer05> so in the end you will have one process maemo-invoker and one processs hildon-home-real and both did a self-rename to hildon-home
Jan 08 03:33:49 <DocScrutinizer05> that's my wild guessing
Jan 08 03:34:21 <FIQ> hm this is kinda weird
Jan 08 03:34:32 <FIQ> this script seem to have got it right
Jan 08 03:35:27 <DocScrutinizer05> lrwxrwxrwx 1 root root 22 2012-12-26 15:55 /usr/bin/hildon-desktop -> /usr/bin/maemo-invoker
Jan 08 03:35:46 <DocScrutinizer05> lrwxrwxrwx 1 root root 22 2012-03-26 01:16 /usr/bin/hildon-status-menu -> /usr/bin/maemo-invoker
Jan 08 03:36:11 <FIQ> oh I see the issue
Jan 08 03:36:23 <FIQ> one string is noticeable bigger than the other
Jan 08 03:37:20 <DocScrutinizer05> -rwxr-xr-x 1 root root 486276 2012-12-23 17:04 /usr/bin/hildon-desktop.launch
Jan 08 03:37:24 <FIQ> but the typo makes sense
Jan 08 03:37:33 <FIQ> oh well, let's see if this fix works
Jan 08 03:39:30 <DocScrutinizer05> I actually think it's maemo-launcher, while maemo-invoker only sends a dbus ,sg to launcher
Jan 08 03:39:44 <DocScrutinizer05> msg
Jan 08 03:44:40 <DocScrutinizer05> FIQ: btw that's why it's sometimes not exactly simple to strace something like hildon-status-menu
Jan 08 03:45:02 <FIQ> there we go
Jan 08 03:45:22 <FIQ> just had to remove an extra dash at the top
Jan 08 03:45:24 <FIQ> nice
Jan 08 03:45:35 <FIQ> ty for the hint, robbiethe1st
Jan 08 08:58:01 <Apic> A wonderful splendid good Pungenday Morning (UGT), the 8th Day of Chaos in the YOLD 3180 to You all.
Jan 08 09:50:25 <dhbiker> hi tehre
Jan 08 09:50:28 <dhbiker> there*
Jan 08 09:50:46 <dhbiker> why am i getting maemo update to stable #6.1
Jan 08 09:50:55 <dhbiker> and then it says i need to use pc suite
Jan 08 09:51:00 <dhbiker> to backup
Jan 08 09:51:04 <dhbiker> ?!?!
Jan 08 11:31:18 <int_ua> Am I the only one who gets XML parsing error in MicroB in 100% of cases after searching "arch abrt"?
Jan 08 11:32:04 <int_ua> http://www.google.com/search?hl=uk&ie=UTF-8&q=arch+abrt
Jan 08 11:35:33 <hardy_magnus> hey friends i recently installed  9.1 update on my n900. what is new in that update?
Jan 08 11:48:00 <anYc> there's a changelog in the wiki
Jan 08 11:48:35 <anYc> afair, qt libs and fmtx downgrade
Jan 08 12:47:12 <sixwheeledbeast> MrPingu: thanks for looking at the DARP wiki page I have updated it too. Feel free to test as many packages as you can ;)
Jan 08 12:48:25 <MrPingu> sixwheeledbeast: Good work ;) Actually with exams coming up I won't be that busy with that but I'll keep it in mind ;)
Jan 08 12:52:48 <sixwheeledbeast> MrPingu: no problems
Jan 08 12:53:20 <sixwheeledbeast> I suppose I "could" plug my packages in testing like http://talk.maemo.org/showthread.php?t=92014 :D
Jan 08 12:58:41 <MrPingu> sixwheeledbeast, I'm not sure about flopswap? It requires additional setup
Jan 08 13:13:58 <DocScrutinizer05> sixwheeledbeast: you'll need a preinstall script in your .deb that checks if the system is correctly tweaked/configured and if not then the script shalll either spit out a help text explaining what user is supposed to do, or rather even open microB on a help wbepage that serves same purpose
Jan 08 13:14:25 <DocScrutinizer05> (re flopswap)
Jan 08 13:15:11 <DocScrutinizer05> make sure you quit install with a failure so dpkg/apt database doesn't count the package as installed when actually it's not
Jan 08 13:17:15 <DocScrutinizer05> thw helptext/webpage ideally goes "Dear user! this package is doing $lengthy-description. For this you need to prepare your system manually: do a)... b)... c)...  **THEN TRY AGAIN TO INSTALL THIS PACKAGE!"
Jan 08 13:18:16 <DocScrutinizer05> keep in mind you will want to also have a proper working way to UNinstall!
Jan 08 15:26:19 <Apic> I lost the Game yet _again_. B-(
Jan 08 15:47:03 <DocScrutinizer05> hm?
Jan 08 15:49:05 <sixwheeledbeast> Hello, just got back reading backscroll
Jan 08 15:53:02 <sixwheeledbeast> MrPingu: FlopSwap is still a work in progress TBH. It requires two swap partitions on the uSD card and that in thoery should be it.
Jan 08 15:53:12 <Apic> ♫▶ Josh Wink - Lil Louis - French Kiss - Original Version
Jan 08 15:53:13 <Apic> ww
Jan 08 15:53:25 <sixwheeledbeast> Apic: oops?
Jan 08 15:53:33 <Apic> sry
Jan 08 15:59:34 <sixwheeledbeast> other than the two linux-swap partitions on the uSD card FlopSwap takes care of everything else with postinst postrm scripts. FlopSwap will not cause system issues if any swaps are missing. This information is currently contained in the package description.
Jan 08 16:00:45 <sixwheeledbeast> MrPingu: I guess from "additional setup" you mean the two linux-swap partitions?
Jan 08 16:01:07 <MrPingu> sixwheeledbeast: yes
Jan 08 16:01:18 <sixwheeledbeast> Without them flopswap would be pointless
Jan 08 16:03:58 <sixwheeledbeast> I am open to any ideas to improve it.
Jan 08 16:13:51 <MrPingu> exactly, that's my concern why it maybe shouldn't go in extras. 
Jan 08 16:15:22 <sixwheeledbeast> Oh...well TBH it's not ready for extras yet.
Jan 08 16:15:22 <FIQ> huh
Jan 08 16:15:29 <FIQ> er wrong channel sorry
Jan 08 16:17:55 <sixwheeledbeast> The version in testing is from a good while ago.
Jan 08 18:51:59 <SAiF> what is the encryption used in /etc/passwd for storing passwd? just to know.
Jan 08 19:08:38 <sixwheeledbeast> i'd guess MD5
Jan 08 19:09:10 <sixwheeledbeast> https://en.wikipedia.org/wiki/Passwd_%28file%29#Password_file
Jan 08 19:55:35 <DocScrutinizer05> SAiF: you can tell from header of each hash
Jan 08 19:56:49 <DocScrutinizer05> https://en.wikipedia.org/wiki/Passwd_(file)#Shadow_file   $id
Jan 08 19:57:22 <DocScrutinizer05> (On GNU/Linux, "$1$" stands for MD5, "$2a$" is Blowfish, "$2y$" is Blowfish (correct handling of 8-bit chars), "$5$" is SHA-256 and "$6$" is SHA-512,
Jan 08 20:00:05 <DocScrutinizer05> HMMMPFFF sorry, messy maemo messybox decides to not adhere, as usual
Jan 08 20:22:31 <DocScrutinizer05> anyway see https://mg.pov.lt/maemo-irclog/search?q=etc%2Fshadow, we had that topic several times before, should show up in on of those hits
Jan 08 20:22:57 <DocScrutinizer05> or "simply" check messybox sources
Jan 08 20:25:47 <DocScrutinizer05> and suuuure, maemo doesn't have encrypt(1)
Jan 08 20:25:58 <DocScrutinizer05> and passwd is fubar
Jan 08 20:27:42 <DocScrutinizer05> actually you need to check sources of passwd and/or sudo
Jan 08 20:27:45 <DocScrutinizer05> it seems
Jan 08 21:13:44 <t3st3r> Interesting question: my N900 started to think it's USA and so applies USA regulatory rules to wi-fi. Except all things around it means inability to connect to some access points as in Russia channelsd 12/13 are allowed. 
Jan 08 21:14:19 <freemangordon> CAL broken?
Jan 08 21:14:26 <t3st3r> where the heck N900 gets idea about US and how do I make it to reconsider it back to RU?
Jan 08 21:14:42 <t3st3r> [01:14:25] <freemangordon> CAL broken? <- hmm, not sure. How to check?
Jan 08 21:14:54 <freemangordon> syslog
Jan 08 21:14:59 <t3st3r> at least MACs/IMEI/.... looks sane.
Jan 08 21:15:15 <freemangordon> look for libcal errors
Jan 08 21:15:22 <freemangordon> in syslog that is
Jan 08 21:15:23 <t3st3r> one moment...
Jan 08 21:15:47 <freemangordon> or something in dmesg, dunno, never heard of such aproblem before
Jan 08 21:16:28 <t3st3r> what more interesing, trying iw reg set causes  some OOPS in kernel oO
Jan 08 21:16:59 <t3st3r> I'm using stable community SSU, if this matters
Jan 08 21:17:06 <freemangordon> should not
Jan 08 21:18:40 <t3st3r> dmesg seems to be clear, though some part has been lost due to small buffer...
Jan 08 21:19:23 <freemangordon> boot part is in syslog
Jan 08 21:20:37 <t3st3r> and where does N900 getting regulatory domain from? I guess it should change rules if I go to other country?
Jan 08 21:20:57 <freemangordon> hmm, no idea TBH
Jan 08 21:21:20 <freemangordon> or rather - I think it is from CAL
Jan 08 21:21:54 <freemangordon> but what happens if you go abroad...
Jan 08 21:22:30 <t3st3r> well, from logical standpoint if I go from RU to US, I should have option to comply with local regulations, shutting down use of channels 12/13. But when I go back I should be able to use 12/13 again.
Jan 08 21:22:52 <freemangordon> t3st3r: did that happens to all routers you connect to?
Jan 08 21:22:57 <freemangordon> *do
Jan 08 21:23:04 <freemangordon> shit, does :D
Jan 08 21:23:12 * freemangordon needs some rest
Jan 08 21:23:31 <t3st3r> freemangordon> hmm, well, I had some dumb issue with router reflashed to openwrt which was not willing to use chan 12/13 as well. 
Jan 08 21:24:26 <t3st3r> this has been upcoming to strange interpretation of "world" configuration being "US". I've fixed that and now device can use chan 12/13 again.
Jan 08 21:25:02 <freemangordon> t3st3r: hmm, I am afraid I can't be of much help, seems you know how the stuff works more than I do
Jan 08 21:25:10 <t3st3r> Ironically, this caused extra testing of high channels and I detected regulatory plague affected N900 at that point, as it utterly fails to see all channel 12/13 APs.
Jan 08 21:25:58 <freemangordon> t3st3r: hmm, thinking of that...
Jan 08 21:26:03 <t3st3r> at boot it just sets up US regdomain. No idea why it sticks to it and where it getting such idea Oo
Jan 08 21:26:46 <freemangordon> "Jan  8 13:14:59 Nokia-N900 kernel: [48243.015899] cfg80211: Regulatory domain: US"
Jan 08 21:27:13 <freemangordon> yep, you guess it right - I am not in US
Jan 08 21:27:32 <t3st3r> So you have it too? oO
Jan 08 21:27:45 <freemangordon> it's always been like that
Jan 08 21:28:13 <t3st3r> what iw list tells you? Can you use chan 12/13? (if your regulatory allows that of course)
Jan 08 21:28:36 <Ashley`> how to check regulatory domain?
Jan 08 21:29:17 <freemangordon> t3st3r:                         * 2467 MHz [12]
Jan 08 21:29:17 <freemangordon> * 2472 MHz [13]
Jan 08 21:29:38 <Ashley`> [ 1309.645477] cfg80211: Regulatory domain changed to country: EU
Jan 08 21:29:43 <t3st3r> iw list from root... 
Jan 08 21:29:57 <t3st3r> it then lists chan 12/13 as "disabled".
Jan 08 21:30:12 <t3st3r> [01:29:52] <Ashley`> [ 1309.645477] cfg80211: Regulatory domain changed to country: EU <- I lack that part :(
Jan 08 21:30:27 <Ashley`> (it's from dmesg)
Jan 08 21:30:45 <t3st3r> ashley> I know. For me it tells it changed to US and no more records about that.
Jan 08 21:30:47 <freemangordon> t3st3r: I bet your CAL data is broken. or something else
Jan 08 21:30:56 <Ashley`> cssu testing here
Jan 08 21:31:04 <freemangordon> t3st3r: I have that "changed to EU" too
Jan 08 21:31:11 <t3st3r> freemangordon> haven't found any records about CAL issues.
Jan 08 21:31:18 <Ashley`> (not the newest one though...)
Jan 08 21:31:35 <freemangordon> t3st3r: and it is right after icd2 started
Jan 08 21:32:03 <t3st3r> not sure if RU variant of N900 is EU but overall wi-fi settings should be rather similar.
Jan 08 21:32:46 <freemangordon> t3st3r: could be either CAL or something in sysconf config(or whatever that lib was called)
Jan 08 21:33:00 <t3st3r> interesing... iw reg set to EU seems to work... checking... 
Jan 08 21:33:18 <t3st3r> it also re-enabled channels.
Jan 08 21:33:28 <freemangordon> t3st3r: maybe you should strace icd2
Jan 08 21:33:30 <t3st3r> But why the heck I miss this part automatically?
Jan 08 21:35:03 <freemangordon> t3st3r: what is ther result of "osso-product-info -q OSSO_PRODUCT_WLAN_CHANNEL"
Jan 08 21:35:19 <freemangordon> here is fcc/us
Jan 08 21:35:52 * freemangordon is not sure which exactly setting is icd2 uses
Jan 08 21:36:22 <t3st3r> hmm, it tells fcc/us oO
Jan 08 21:36:47 <t3st3r> which is not a case obvuiusly...
Jan 08 21:36:53 <freemangordon> t3st3r: ok, but I don't know where icd2 gets it from
Jan 08 21:37:10 <freemangordon> could be CAL, gconf, sysconf, what else?
Jan 08 21:37:24 <t3st3r> the most strange thing is that I haven't changed any settings at all. 
Jan 08 21:37:36 <freemangordon> t3st3r: fs corruption?
Jan 08 21:38:00 <t3st3r> theoretically it could happen, sure, but I don't see other issues.
Jan 08 21:38:08 <freemangordon> t3st3r: maybe a reflash will be the easier way to solve that. who knows
Jan 08 21:38:18 <freemangordon> easiest*
Jan 08 21:38:28 * freemangordon deffinitely needs sleep
Jan 08 21:39:34 <freemangordon> t3st3r: maybe wait for DocScrutinizer05 and/or Pali to appear, they know a bit how icd2 works iirc
Jan 08 21:39:40 <t3st3r> well, now I can see my test channel13 AP... but setting it manually is no fun and error prone if I go to other country...
Jan 08 21:41:01 <freemangordon> t3st3r: so you are sure that regulatory domain should automatically change?
Jan 08 21:41:33 <freemangordon> going to as google
Jan 08 21:41:37 <freemangordon> ask even
Jan 08 21:42:22 <t3st3r> freemangordon> well, not sure but it would be logical, based on timezone or GPS. 
Jan 08 21:42:54 <t3st3r> or else there is risk to violate regulations my going to other country with mobile device with wrong settings.
Jan 08 21:43:21 <t3st3r> and at least "out of the box" it can see channel 12/13 APs.
Jan 08 21:43:45 <t3st3r> so I really wonder what has changed/borked oO
Jan 08 21:44:33 <freemangordon> well, if your hypthezis that RD should autochange, then it could be your router that told n900 wrong RD
Jan 08 21:44:48 <freemangordon> somehow
Jan 08 21:45:05 <freemangordon> I am not really in wifi stuff
Jan 08 21:45:53 <freemangordon> ooh
Jan 08 21:46:01 <freemangordon> bug 5699
Jan 08 21:46:04 <povbot> 04Bug https://bugs.maemo.org/5699 WLAN regulatory domain changes to US when no position data available
Jan 08 21:46:36 <freemangordon> "If we cannot determine the location we must default to US since all devices
Jan 08 21:46:36 <freemangordon> must conform to FCC requirements.
Jan 08 21:46:53 <freemangordon> t3st3r: ^^^
Jan 08 21:47:21 <t3st3r> freemangordon> and how do they detect location?
Jan 08 21:47:32 <freemangordon> read the bug report
Jan 08 21:47:44 <t3st3r> url?
Jan 08 21:47:53 <freemangordon> ^^^
Jan 08 21:47:57 <freemangordon> bug 5699
Jan 08 21:47:58 <t3st3r> ah, bot :)
Jan 08 21:51:04 <Apic> B-)
Jan 08 21:51:17 <DocScrutinizer05> RD gets set by AP
Jan 08 21:51:20 <DocScrutinizer05> ;-P
Jan 08 21:51:27 <t3st3r> thanks, I think this stuff explains a lot. But I done GPS fix recently in hope it would get idea. 
Jan 08 21:51:43 <t3st3r> [01:51:23] <DocScrutinizer05> RD gets set by AP <- ???
Jan 08 21:51:51 <t3st3r> AP can set RD flags?
Jan 08 21:52:02 <DocScrutinizer05> afaik yes
Jan 08 21:52:18 <t3st3r> Interesting. What next? AP can reflash boot loader? oO
Jan 08 21:52:28 <DocScrutinizer05> there's something in RFCs to tell clients which RD they are in
Jan 08 21:52:46 <DocScrutinizer05> at least iirc
Jan 08 21:52:59 <t3st3r> DocScrutinizer05> some APs can sent "country" information element.
Jan 08 21:53:09 <DocScrutinizer05> yes, sth like that
Jan 08 21:53:10 <t3st3r> to give hint about location
Jan 08 21:53:25 <t3st3r> and some APs around are sending it... and its correct - RU.
Jan 08 21:54:13 <DocScrutinizer05> well, it seems maemo is setting RD according to CAL and maybe LOCALE
Jan 08 21:54:36 <t3st3r> scanning with iw (not on n900!) would show a lot of info about APs around, incl all (?) IEs.
Jan 08 21:55:08 <t3st3r> strange, I've attempted to change locale and so on and it had zero effect.
Jan 08 21:55:39 <t3st3r> I attempted to change timezones, set up russian settings (even if I prefer English UI) and so on.
Jan 08 21:55:59 <t3st3r> still it has been sticking to US :)
Jan 08 21:56:13 <freemangordon> DocScrutinizer05: look at bug 5699
Jan 08 21:56:17 <povbot> 04Bug https://bugs.maemo.org/5699 WLAN regulatory domain changes to US when no position data available
Jan 08 21:56:25 <freemangordon> it gets it from the MNO
Jan 08 21:57:29 <DocScrutinizer05> wtf is MNO?
Jan 08 21:57:38 <Ashley`> how can I install the new apt-worker?
Jan 08 21:57:43 <freemangordon> Mobile Network Operator
Jan 08 21:57:50 <DocScrutinizer05> makes sense
Jan 08 21:58:20 <freemangordon> Ashley`: what is that new apt-worker? you mean hildon-application-manager?
Jan 08 21:58:39 <freemangordon> (apt-worker is part of HAM package)
Jan 08 21:59:15 <freemangordon> DocScrutinizer05: I suspect it falls back to CAL when no positioning available
Jan 08 21:59:23 <DocScrutinizer05> yes
Jan 08 21:59:25 <t3st3r> Hmm, well, I haven't used cell net for some time but I did GPS fix and some APs are surely emitting RU in their beacon IEs.
Jan 08 21:59:26 <DocScrutinizer05> it does
Jan 08 21:59:46 <freemangordon> because there is OSSO_PRODUCT_WLAN_CHANNEL='fcc/us'
Jan 08 21:59:51 <freemangordon> on my devide
Jan 08 21:59:55 <freemangordon> *device
Jan 08 21:59:58 <DocScrutinizer05> GPS is mostly ignored in maemo
Jan 08 22:00:09 <DocScrutinizer05> for time as well as roaming and other stuff
Jan 08 22:00:36 <freemangordon> so, if someone writes what? fcc/ru? then it should fallback to RU when no info available
Jan 08 22:00:43 <t3st3r> okay, but then there is  bunch of APs sending RU in beacons.
Jan 08 22:00:45 <freemangordon> but I am not bold enough to test that
Jan 08 22:01:11 <DocScrutinizer05> definitely not fcc/ru, no such thing
Jan 08 22:01:11 <freemangordon> t3st3r: did you read the bug report?
Jan 08 22:01:21 <DocScrutinizer05> see your own code ;-)
Jan 08 22:01:25 <freemangordon> well, etsi?
Jan 08 22:01:29 <t3st3r> freemangordon> I'm did and now I'm reading comments...
Jan 08 22:01:35 <DocScrutinizer05> etsi, yep, guess so
Jan 08 22:01:38 <freemangordon> yeah, the comments
Jan 08 22:01:50 <DocScrutinizer05> OSSO_PRODUCT_WLAN_CHANNEL is an env?
Jan 08 22:01:54 <freemangordon> no
Jan 08 22:02:03 <freemangordon> osso-product-info
Jan 08 22:02:38 <DocScrutinizer05> OSSO_PRODUCT_WLAN_CHANNEL='fcc/us'  grrr
Jan 08 22:03:15 <freemangordon> thanks to almighty fmg we have it REed :P
Jan 08 22:03:18 <freemangordon> https://gitorious.org/community-ssu/osso-product-info/source/bd52864557b076d5918f8e1bf2e494d4f331bf96:libossoproductinfo.c
Jan 08 22:03:38 <DocScrutinizer05> OSSO_PRODUCT_KEYBOARD='German' double-bold-GRRRR
Jan 08 22:04:07 <DocScrutinizer05> OSSO_PRODUCT_REGION='Germany'
Jan 08 22:05:23 <DocScrutinizer05> sorry, I start to get a nervous breakdown, primarily thanks to openmoko.org MX SMTP/TLS broken
Jan 08 22:05:43 <DocScrutinizer05> or not
Jan 08 22:06:04 <freemangordon> ok, it checks if we are in SB first, if not, it asks com.nokia.SystemInfo, if that fails it looks in CAL
Jan 08 22:06:05 <DocScrutinizer05> or no more compatible to my system, both kmail and thunderbird
Jan 08 22:08:40 <DocScrutinizer05> t900:~# sysinfo-tool -g /certs/ccc/pp/wlan-channel    
Jan 08 22:08:42 <DocScrutinizer05> fcc/us
Jan 08 22:12:46 <freemangordon> yep, it is not in CAL
Jan 08 22:13:41 <DocScrutinizer05> sw-release-ver
Jan 08 22:13:43 <DocScrutinizer05> RX-51_2009SE_2.2009.ENOS-NO-CELMO
Jan 08 22:13:45 <DocScrutinizer05> ;-P
Jan 08 22:13:48 <DocScrutinizer05> CAL
Jan 08 22:14:29 <DocScrutinizer05> kernel-ver
Jan 08 22:14:30 <DocScrutinizer05> MD2.6.28-20093204eno3+0m5
Jan 08 22:14:34 <freemangordon> where did you get that device from?
Jan 08 22:14:41 <DocScrutinizer05> sw-release-ver
Jan 08 22:14:42 <DocScrutinizer05> RX-51_2009SE_1.2009.37-7_ENOS_MR0
Jan 08 22:14:45 <DocScrutinizer05> devel device
Jan 08 22:14:49 <freemangordon> yeah
Jan 08 22:15:08 <FIQ> hi
Jan 08 22:15:26 <freemangordon> anyway, I am off, night
Jan 08 22:15:36 <DocScrutinizer05> o/
Jan 08 22:16:08 <FIQ> how come when I try to make sensible error messages (i.e. not swedish error output) by using LANG=C (insertstuffhere), N900 responds with not changing the locale at all, *but* happily screwing up åäö (probably because of utf8 fail)
Jan 08 22:16:49 <FIQ> is there a "right" way to do this on the N900?
Jan 08 22:17:18 <FIQ> i.e. run a command in another language without changing the entire OS' lang
Jan 08 22:18:34 <wnd> you may want to try setting LC_CTYPE
Jan 08 22:19:26 <wnd> I usually set LC_ALL, LANG and LANGUAGE when I need to temporarily use locale other than the default
Jan 08 22:20:12 <wnd> of course, that's on desktop
Jan 08 22:32:56 <FIQ> on desktop, all I do is type LANG=C (whatever)
Jan 08 22:33:01 <FIQ> which works flawlessy
Jan 08 22:44:18 <amospalla> is thumb 9.1 released?, I think it is, but it does not appear as an update on my n900.
Jan 08 23:11:52 <sixwheeledbeast> amospalla: yes
Jan 08 23:14:45 <MrPingu> but without meta-package it seems?
Jan 08 23:20:09 <sixwheeledbeast> I installed it no problem IIRC released 20140101
Jan 08 23:20:25 <MrPingu> hmmm?
Jan 08 23:20:33 <MrPingu> I doesn't show up here
Jan 08 23:20:46 <MrPingu> but slow HAM is still doing its thing
Jan 08 23:20:58 <sixwheeledbeast> have you installed it?
Jan 08 23:21:32 <MrPingu> No, I have testing 9.1 because fmtx problems
Jan 08 23:22:30 <sixwheeledbeast> oh sorry
Jan 08 23:22:41 <MrPingu> but I don't get the meta-package update but all separate updates show for thumb
Jan 08 23:23:34 <sixwheeledbeast> oh ... my bad thumb hasn't been released yet, miss read "testing/thumb" 
Jan 08 23:24:46 <sixwheeledbeast> I doubt there is much need it's only rolling back the fmtx package AFAIK
Jan 08 23:28:16 <MrPingu> Yes, and it still sucks that US devices have borked fmtx
Jan 08 23:31:55 <MrPingu> Oh and if you need a nice font for xterm, I think anonymous is really awesome 
Jan 08 23:33:03 <MrPingu> And I am going for some sleep, night
Jan 08 23:33:12 <sixwheeledbeast> me to night o/
Jan 08 23:48:08 <amospalla> thank you  guys
Jan 09 01:06:08 * FIQ uses dejavu sans mono in the terminal and xchat
Jan 09 01:06:16 <FIQ> always liked that font
Jan 09 01:07:34 <FIQ> used to use MHei(whatever)
Jan 09 01:07:48 <FIQ> and droid sans mono
Jan 09 01:07:54 <FIQ> at some different points
**** ENDING LOGGING AT Thu Jan 09 02:59:58 2014