IRC log for #maemo-ssu on 20121116

00:00.04DocScrutinizer05HAM?
00:00.06FIQyes
00:00.16DocScrutinizer05depends on how many repos you got enabled, I guess
00:00.31FIQwoo
00:00.32DocScrutinizer05with extras-devel it usually takes 7 min here
00:00.38FIQit asked if I wanted to install enabler
00:01.02FIQit took precisely 7min :p
00:01.24FIQseemed to work
00:01.49DocScrutinizer05lesson learnt: don't make bash your default shell
00:02.17FIQI don't like busybox though
00:02.25DocScrutinizer05neither
00:02.28DocScrutinizer05~jrtools
00:02.29infobotjrtools is, like, http://wiki.maemo.org/User:Joerg_rw/tools
00:03.01DocScrutinizer05ok, I have to start it by typing `bash` as first command to xterm
00:03.13FIQmaybe I should try to edit .shrc or whatever the equavilence to .bashrc is, and check for PS1 in order to spawn bash on top of it
00:03.22FIQit's hackish, but i'm lazy
00:03.29DocScrutinizer05~jrtools
00:03.30infobotwell, jrtools is http://wiki.maemo.org/User:Joerg_rw/tools
00:03.43DocScrutinizer05messybox is sourcing bashrc
00:04.10FIQso messybox thinks it's bash?
00:04.22DocScrutinizer05you *might* check if you got an interactive shell or not. But probably that doesn't pan out either, in the end
00:04.45FIQfair enough, i'll type bash manually
00:04.52DocScrutinizer05some retard maintained thought messybox == bash, yes
00:05.37DocScrutinizer05FIQ: check my nifty PATH joggling
00:05.38FIQi'd rather not touch busybox, but i guess i'm forced as maemo depend on it
00:05.45FIQhmm
00:06.07*** join/#maemo-ssu dhbiker (~dhbiker@95.87.145.172)
00:06.17FIQyou mean placing /usr/bin/gnu first?
00:06.18DocScrutinizer05juggling even
00:06.24DocScrutinizer05yep
00:06.31FIQI already do that :P
00:06.50FIQto not have to bother with busybox binary
00:07.23DocScrutinizer05hmm, actually my recent files look different
00:08.58FIQexport PATH="/usr/bin/gnu:"$PATH":$HOME/bin is my path atm
00:09.21FIQ("bin" actually contains shellscripts but whatever)
00:14.18DocScrutinizer05I once got a nifty sed cmdline, but I seem too ill and dizzy to locate it
00:14.49DocScrutinizer05sorry
00:14.59FIQalso
00:15.36FIQwhy does HAM (not only for cssu, but that's one of the things) show "(null) Install anyway?" when installing?
00:15.53DocScrutinizer05dafaq ~user/.bashrc vanished
00:16.08FIQevil maemo
00:16.11DocScrutinizer05or I'm starting to lose my mind
00:16.15MrPinguHmm, what I don't like or liked about the bash thingy; as soon you ran sudo gainroot from bash, it returns you to busybox
00:16.40FIQMrPingu: I just made sudo usable as on linux desktop
00:16.50FIQby making an own file in sudoers.d
00:16.51DocScrutinizer05well, that's 'normal' since you open a new default shell
00:17.07FIQ"Upgrade for Maemo" guess I'll be afk shortly
00:17.26MrPinguYes, I know but I don't like it
00:17.53MrPinguI always close xterm by issuing exit
00:18.07DocScrutinizer05if you don't like what the command you invoked is doing, find a better command
00:18.16FIQ.................
00:18.24FIQThat was stupid
00:18.47FIQHAM closed everything, *then* proceed to tell me that there wasn't enough battery
00:18.59MrPinguIt would mean in the worst case I would have to issue it 4 times :P
00:19.23MrPinguDocScrutinizer05: You got a point there!
00:19.25DocScrutinizer05MrPingu: btw bash for root seems semi-safe
00:19.45DocScrutinizer05while bash for user definitely never been
00:20.03FIQis there a reason that you shouldn't use "proper sudo"?
00:20.04DocScrutinizer05paradox but true
00:20.39DocScrutinizer05nah, sudo is used all the time, but sudo isn't `root` aka sudo gainroot
00:20.45FIQi.e. enable yourself to do "sudo (whatever)" instead of logging in as root and do "(whatever)"
00:21.14DocScrutinizer05if you log in via `root` you get root's environment ($HOME etc)
00:21.24FIQwell.. yeah
00:21.54MrPingusemi-safe still don't like that :P For now I stick to busybox, till I hate it so much and can't bear it anymore
00:22.02DocScrutinizer05if you log in via `sudo gainroot` you're still in user's environment
00:22.27FIQI use sudo as on a desktop, basically
00:22.34MrPinguDocScrutinizer05: Thanks for the passwd for root, love it :)
00:22.36FIQi.e. no "root" or "sudo gainroot"
00:22.54DocScrutinizer05if you do sudo $somecmd, then you're quite obviously in user's environment still
00:23.03FIQyes I know
00:23.13MrPinguBut sudser fvcks it up
00:23.23DocScrutinizer05sudser is brainfsck
00:23.27FIQMrPingu: I did it manually
00:23.51MrPinguFIQ: would love to hear how, but I really need to get some sleep now
00:24.11MrPinguGood night!
00:24.46DocScrutinizer05MrPingu: I thought a lot how to make root password more safe. First step: make HAM ask for root password, so nobody can install crap to nuke passwords
00:25.30FIQmade a file in sudoers.d, typed "user ALL = (ALL) ALL" and ran update-sudoers
00:25.40DocScrutinizer05I discussed it with kerio a whole night long
00:25.52FIQ/etc/sudoers.d, that is
00:26.15DocScrutinizer05FIQ: definitely a poor idea
00:26.18DocScrutinizer05in my book
00:26.26FIQhmmmm
00:26.31FIQhow so?
00:26.47DocScrutinizer05it defeats the whole idea of root permissions
00:27.16FIQDocScrutinizer05: maemo is a single user environment
00:27.25DocScrutinizer05you as well could set UID for user to 0
00:27.35DocScrutinizer05FIQ: definitely not
00:28.26DocScrutinizer05there's users "root", "user", "apt", "ntpd", "dahellknows"....
00:28.49FIQfair enough, but I don't see the problem
00:28.52DocScrutinizer05not exactly a singleuser system
00:29.03FIQsudo gainroot gives you root access in user environment
00:29.19DocScrutinizer05so what?
00:29.42DocScrutinizer05sudo gainroot asks for root password on my machine
00:29.49FIQthe above gives you the same, just with letting you to not have to do sudo gainroot before
00:30.36FIQsudo gainroot also does it w/o password by default, while the above *do* ask the password, for user
00:30.39DocScrutinizer05FIQ: chmod -R a+rwx /
00:31.21FIQwhy would you do that?
00:31.34DocScrutinizer05FIQ: I'm not going to debate with you how to fuck up a fubar concept even more
00:31.55*** join/#maemo-ssu FireFly (~firefly@oftn/member/FireFly)
00:32.04DocScrutinizer05FIQ: same question to your "user ALL = (ALL) ALL"
00:32.20DocScrutinizer05why would you do that?
00:33.08DocScrutinizer05since chmod -R a+rwx / work much better, by not even requiring a sudo in front of any braindamaged command user may want to nuke system with
00:33.55FIQDocScrutinizer05: it also gives all other users root
00:34.13DocScrutinizer05either use permissions, the put it to purpose properly, or not use them at all, no?
00:35.20DocScrutinizer05<FIQ> DocScrutinizer05: maemo is a single user environment
00:36.19DocScrutinizer05((<FIQ> DocScrutinizer05: it also gives all other users root)) so what?
00:36.43DocScrutinizer05either you bother about security, or not
00:37.02DocScrutinizer05the most dangerous processes run under user anyway
00:38.12DocScrutinizer05multiuser setup and user separation is for security purposes. Not much sense in neutering it for user
00:38.39DocScrutinizer05even less sense in improving that neutering
00:39.36DocScrutinizer05Nokia fsckd it up by running stuff like HAM under user and not daring to ask for a password when it invokes apt-worker under root
00:39.55FIQDocScrutinizer05: I'm "user", and last time I checked, I'm the owner of the n900. sudo gainroot gives user full root (without even a password by default), my proposal does it too. The difference is that in one way needs me to first type a command to allow root commands, then a second do what I want, then exit when done with a third command while my line lets you do it with one command
00:40.26FIQAlso, my thing ask for a password. sudo gainroot doesn't
00:40.39DocScrutinizer05meh
00:41.30FIQDo you disallow root for yourself on your desktop machines too?
00:41.54DocScrutinizer05who the fuck disallows anything?
00:42.32DocScrutinizer05sorry, this exhausts me too much. should stay in bed curing my flu
00:43.20FIQI don't see the problem here, but I might miss something here, I don't deny it
00:43.47DocScrutinizer05~jrtools
00:43.47infobotsomebody said jrtools was http://wiki.maemo.org/User:Joerg_rw/tools
00:44.11FIQ(Also chmod 777 is a bad idea for other reasons too, as it screws things up in other ways, but that's irrelevant)
00:47.21DocScrutinizer05FIQ: I missed sth: your setup asks for password - user password though, which is kinda silly ubuntu bullshit, but kinda works for maemo since you can't change your own user password on maemo
00:47.26FIQ[01:41:30] <FIQ> Do you disallow root for yourself on your desktop machines too? -- i.e. you don't give your normal user account full sudo as you think it's bad security principe
00:47.48FIQoh you thought i had nopasswd?
00:48.02DocScrutinizer05yes, my users never have root access by using their *own* password
00:48.21FIQhmm
00:48.29DocScrutinizer05root access should need root password, not user's password
00:48.36FIQlet me think now
00:48.53FIQchanging password can be done on the user's account
00:48.57DocScrutinizer05n8 again
00:49.08FIQ(normally)
00:49.28FIQso basically asking for user password is like asking for no password at all
00:49.28DocScrutinizer05not as user, under maemo (thanks busybox passwd)
00:49.42FIQyeah, i said "(normally)"
00:49.48DocScrutinizer05only root can change user's password on maemo
00:49.51FIQI think I get your point now
00:52.11FIQthough in practice maemo is a joke to get root on due to HAM
00:52.26FIQbut still
00:52.32DocScrutinizer05see my comment several lines above
00:52.47FIQyeah I saw it
00:52.55DocScrutinizer05actually my comments (plural)
00:53.08FIQno need to break it more
00:53.37DocScrutinizer05[2012-11-16 01:24:46] <DocScrutinizer05> MrPingu: I thought a lot how to make root password more safe. First step: make HAM ask for root password, so nobody can install crap to nuke passwords
00:53.48FIQyeah
00:53.52FIQsaw the line
00:54.30FIQwell you've modified HAM in cssu, making that shouldn't be too hard :p
00:54.39DocScrutinizer05if we had a better sudo executable (more recent) we could solve this pretty nicely
00:55.03FIQalso what about the autologin?
00:55.11DocScrutinizer05but yeah, we might fix HAM as well
00:55.14FIQ(on boot, that is)
00:55.26DocScrutinizer05another PITA
00:55.32FIQit's just "user" but still
00:55.55DocScrutinizer05it should attach PAM to device lockcode and PIN query
00:56.35DocScrutinizer05actually lockcode should be a PAM module
00:56.41FIQPIN is easy to dodge if you just want to access the system
00:57.00DocScrutinizer05and H-D startup get done by sth like XDM
00:57.02FIQlockcode or asking for user's password, it is
00:58.04FIQMy previous device asked for lockcode on startup :p
00:59.43DocScrutinizer05honestly they ought have implemented lockcode query into NOLO
01:00.06DocScrutinizer05as well as charging ;-P
01:00.30FIQshouldn't it be possible to query on boot?
01:01.03FIQi mean, there's bootmenu, shouldn't be too hard to make a "bootloader" that asks for password before proceeding
01:01.08DocScrutinizer05nah, it will still aloow resueOS and flashing
01:01.42DocScrutinizer05both done by NOLO
01:01.42FIQwell flashing nukes system
01:02.00FIQlike reinstalling the OS on a desktop :p
01:02.19DocScrutinizer05yep, but on desktop you got device password on BIOS level
01:02.23DocScrutinizer05if you want
01:02.35DocScrutinizer05rendering device basically useless for thieves
01:03.19DocScrutinizer05no such thing on N900
01:03.33DocScrutinizer05thanks NOLO (our 'BIOS')
01:03.58FIQTrue
01:04.13DocScrutinizer05o/
01:04.20FIQwell as long as the OS isn't open doors, I'm happy, if people really want to get my data, go on and steal my HDD, I'm not *that* paranoid :3
01:04.24FIQbye
01:06.40FIQ(also isn't uboot lowlevel enough?)
01:09.35*** join/#maemo-ssu Jade (~jade@modemcable190.180-203-24.mc.videotron.ca)
01:09.35*** join/#maemo-ssu Jade (~jade@unaffiliated/jade)
01:26.18*** join/#maemo-ssu Jade (~jade@modemcable190.180-203-24.mc.videotron.ca)
01:26.18*** join/#maemo-ssu Jade (~jade@unaffiliated/jade)
01:35.58DocScrutinizer05uboot comes after NOLO, flashing / rescueOS booting is done *in* NOLO
01:36.41DocScrutinizer05actually even NOLO can get coldflashed by a new one that wouldn't ask for password
01:36.59DocScrutinizer05since ROMBOOT allows coldflashing
01:37.48FIQthere we go, CSSU installed
01:37.53DocScrutinizer05but afaik NOLO resp the XLoader header at least needs a signature to get executed by ROMBOOT, so nobody could tamper XLoader
01:38.14FIQHAM took literally 15min to show update...
01:38.22DocScrutinizer05hmm,
01:38.25DocScrutinizer05terrible
01:38.26FIQonce I booted from new battery
01:38.47FIQthe update itself took 8min
01:38.52DocScrutinizer05but don't worry, updates are less painful
01:39.53FIQso HAM took less time to do what I actually wanted than it took to show me it, even though it showed me previously
01:39.54FIQyaay!
01:39.57DocScrutinizer05once the automatic check for updates shows "maemo 5 CSSU update available" it doesn't take forever to show that update in HAM. Then you fire "update that" and forget
01:40.21FIQi "disabled" the check
01:40.38FIQso I went manually opening HAM and press update button
01:40.46FIQthat task took 15min
01:41.29DocScrutinizer05yeah, that's when it downloads *all* repo 'indexes' and builds databese with dependencies
01:41.47FIQhmmm
01:42.11FIQcan I uninstall these stuff taking up place on my appmenu w/o problems?
01:42.35DocScrutinizer05on my 300MHz 150MB RAM laptop the same procedure in Yast took a day, literally
01:42.41FIQamazon, ap news, documents to do, facebook, foreca, that is
01:42.57DocScrutinizer05"these stuff"?
01:43.00FIQsounds.. "fun"
01:43.12FIQi mentioned which i meant :p
01:43.15DocScrutinizer05yeah sure, apt-get purge
01:43.34FIQwonder what they're called.. hm
01:43.45DocScrutinizer05apt-cache search
01:44.04FIQyeah
01:44.59FIQalso your HAM doesn't kill apt-worker on exit
01:44.59DocScrutinizer05first remove the friggin desktop widget though, in desktop edit mode
01:45.17FIQi don't use the desktop
01:45.22FIQremoved everything etc
01:45.24FIQblank bg
01:45.25FIQ:p
01:45.38DocScrutinizer05then it's safe to apt-get purge that crap
01:46.25DocScrutinizer05(though foreca isn't that bad, I actually use it)
01:48.51FIQargh didn't found the name for documents to go stuff
01:49.30DocScrutinizer05hmm, sorry can't look it up here anymore ;-)
01:49.38DocScrutinizer05or maybe I can?
01:50.04FIQfound it
01:50.08FIQ"dtg-installer"
01:50.10DocScrutinizer05dtg-installer
01:50.16DocScrutinizer05:-D
01:51.04FIQwhat about the er
01:52.04FIQ"Handbook" and the "how to start" entries? :3
01:52.41FIQor that mahjong game for that matter
02:42.12*** join/#maemo-ssu Jade (~jade@modemcable190.180-203-24.mc.videotron.ca)
02:42.12*** join/#maemo-ssu Jade (~jade@unaffiliated/jade)
02:45.04*** join/#maemo-ssu luf (~luf@ip-89-103-223-164.net.upcbroadband.cz)
03:28.50*** join/#maemo-ssu amiconn_ (amiconn@rockbox/developer/amiconn)
03:51.21*** join/#maemo-ssu luf (~luf@ip-89-103-223-164.net.upcbroadband.cz)
04:03.52*** join/#maemo-ssu DocScrutinizer05 (~HaleBopp@openmoko/engineers/joerg)
06:03.19*** join/#maemo-ssu Jade (~jade@Jade.broker.freenet6.net)
06:03.19*** join/#maemo-ssu Jade (~jade@unaffiliated/jade)
06:10.25kerioDocScrutinizer05: CSSU replacement for foreca-widget!
06:28.44*** join/#maemo-ssu chainsawbike (~chainsawb@unaffiliated/chainsawbike)
07:07.47tadzikDocScrutinizer05: (mime types), no, I mean the code that's responsible for reacting to longpress, drawing the context menu, making it disappear etc
07:16.17keriogtk, maybe?
07:29.09*** join/#maemo-ssu X-Fade (~xfade@d5152FFD8.static.telenet.be)
08:03.25tadzikno, it's somewhere above Gtk, I think
08:03.48tadzikWhat I want to do is to make the context menu not disappear when you stop pressing the screen
08:03.55tadzikso you can actually see what popped out
08:04.27tadzikin Gtk the context menu does not disappear when you cease pressing right mouse button, so I guess that's have to be some hildon shamanism
08:49.07*** join/#maemo-ssu BCMM (~BCMM@unaffiliated/bcmm)
09:04.13*** join/#maemo-ssu luf (~luf@ip-89-103-223-164.net.upcbroadband.cz)
10:05.32*** join/#maemo-ssu kolp (~quassel@212.255.16.50)
10:21.58*** join/#maemo-ssu dhbiker (~dhbiker@95.87.145.172)
10:33.24DocScrutinizer05tadzik: for some reason I sometimes achieve to not close context menu when lifting stylus. I guess it's rather a bug that hits when touchpoint coords move minimally on lifting stylus, rather than an option designed in on purpose
10:37.17vi__It happens when you lift off the very edge of the menu perimeter.
10:37.28vi__I believe the relevent code is in hildon-home.
10:37.56tadzikDocScrutinizer05: indeed, it is possible
10:38.08tadzikthen that's a bug worth fixing, imho
10:42.35tadzik(and will probably turn out to be a PITA)
11:01.44DocScrutinizer05nah, the fix should be 'easy': just don't close the menu when pen-up event happens outside of menu area, no matter if coords moved away from pen-down coords or not
11:02.51DocScrutinizer05actually it seems to me this is indeed a function that has to be coded in on purpose. Probably just needs commenting out
11:04.03DocScrutinizer05if you wanna do a real fix, then check for distance between pen-down and pen-up event and close menu only when distance is >threshold
11:05.13DocScrutinizer05maybe, just *maybe*, there's already such check for distance, and somebody simply set a fsckng low threshold
11:05.38tadzikpossibly
11:05.49keriothe context menu does indeed disappear if you right-click-and-hold and then release the right mouse button
11:05.53tadzikI'll have to locate the code first; will look more after $dayjob
11:06.00kerioiirc
11:07.02tadziknot unles you move it over some menu item
11:07.15tadzikif you click, hold, drag away it stays
11:14.22*** join/#maemo-ssu Pali (~pali@unaffiliated/pali)
11:21.51*** join/#maemo-ssu arcean (~arcean@aaeo131.neoplus.adsl.tpnet.pl)
11:31.41vi__kerio: That implies it is a bug that is a result of the emulated push+hold right click.
11:39.36*** join/#maemo-ssu kolp_ (~quassel@212.255.20.215)
12:11.45*** join/#maemo-ssu NIN101 (~NIN@p5DD28D91.dip0.t-ipconnect.de)
12:32.39DocScrutinizer05tadzik: ((if you click, hold, drag away it stays)) unlike on touchscreen where it vanishes if you dare to drag
12:32.56DocScrutinizer05tadzik: which is a bit strange
12:33.06tadzikDocScrutinizer05: yeah. I was talking about desktop gtk
12:33.21tadzikin hildon that's strange and annoying imho
12:33.30tadzikbut for example Opera got it right on maemo
12:33.48DocScrutinizer05(the absolute contrary behavior between mouse RMB and stylus longtouch)
12:35.32DocScrutinizer05also I find anchor of context menu got chosen rather unfortunate (menu appears to right of touchpoint, so you basically *always* cover it with stylus/finger)
12:35.54tadziktrue
12:36.01tadzikroom for improvement! \o/
12:36.23DocScrutinizer05what a fool chosen those parameters?
12:36.40DocScrutinizer05obviously somebody who tested on PC screen in emulator
12:36.48DocScrutinizer05with mouse
12:36.57tadzikentire maemo feels this way for me
12:37.04tadzikwell, almost
12:37.15tadzikit's not quite utilizing the potential in a touchscreen interface
12:37.17kerionah
12:37.54tadziklike the status area. Clicking small stuff with mouse is fine. Clicking small stuff with big finger is tricky
12:38.11tadzikcall me blasphemer, but I think android does it right :)
12:38.16tadzikthis particular thing
12:38.57tadzikalthough n900 does not have much space above screen, so it may not be such a good idea
12:39.01vi__DocScrutinizer05: obviously someone who was left handed...
12:39.04vi__A WITCH!
12:39.05DocScrutinizer05I'm using fingernail. I actually love the smaller touchareas in fremantle, compared to finger-only GUI design of e.g. harmattan
12:40.24DocScrutinizer05vi__: yep, or lefthanded
12:41.00DocScrutinizer05but then that guy ought have *forced* a "lefthand/righthand" user setting option into fremantle screen settings
12:42.01DocScrutinizer05after all at least that guy *should* be aware of the problems of the other part of mankind that doesn't use same hand as the rest
12:42.22kerioDocScrutinizer05: he did that on purpose
12:42.28DocScrutinizer05revenge
12:42.37kerioto inflict vengeance to every right-handed person on the planet!
12:42.54kerios/on the planet/that happened to be using a n900, so very few people/
12:43.50DocScrutinizer05actually this is a pretty good filed and opportunity for a mad useful improvement in CSSU
12:43.57DocScrutinizer05field*
12:44.15DocScrutinizer05arcean: ^^^
12:44.31DocScrutinizer05arcean: last ~150 lines
12:46.37DocScrutinizer05arcean: in short: implement (or check if already there) a threshold for drag after stylus-down, to make context menu close. Do not close when threshold distance isn't exceeded. and create a config option to change anchor point of context menu to arbitrary of 4 corners
13:16.12*** join/#maemo-ssu Timo (~timo@unaffiliated/tiempjuuh)
14:07.38*** join/#maemo-ssu M4rtinK (~M4rtinK@mail.melf.eu)
14:17.22*** join/#maemo-ssu M4rtinK (~M4rtinK@109.107.211.150)
14:44.01*** join/#maemo-ssu M4rtinK (~M4rtinK@109.107.211.150)
15:58.34*** join/#maemo-ssu Timo (~timo@unaffiliated/tiempjuuh)
16:01.58*** join/#maemo-ssu arcean (~arcean@aaeo131.neoplus.adsl.tpnet.pl)
16:17.50*** join/#maemo-ssu toxaris (~toxaris@s83-180-246-172.cust.tele2.se)
17:17.06*** join/#maemo-ssu Linger (~Linger@CPE-121-218-40-55.lnse4.ken.bigpond.net.au)
17:17.15LingerGood morning
17:19.04LingerI'm a fellow with some fairly easy technical questions.
17:19.53LingerQuestions regarding IRC.
17:20.05wmaroneask, don't wait
17:20.57LingerOk, thank you. I'm an Aussie. I have not been on IRC for 10 years. Where would I go do talk to Aussies?
17:21.48DocScrutinizer05not on freenode. channels on freenode are technical topics, not geographical
17:21.49LingerI'm 26. Used to me on IRC a lot when I was a teen. But I lost interest for a while.
17:21.51wmaronewell that's not a technical question
17:22.21LingerFair point
17:22.50DocScrutinizer05we got some aussies in every maemo related channel
17:22.53LingerWell I would be happy to ask a technical question, as I have an InfoSec background
17:23.11*** join/#maemo-ssu M4rtinK (~M4rtinK@mail.melf.eu)
17:23.26kerioLinger: did you just stumble upon #maemo-ssu?
17:23.46LingerTruth is, it's Friday night here in Aus. I've had a few beers. I'm looking for some interesting discussion before I crash.
17:23.53LingerYes I did
17:24.51keriothis is a channel dedicated to a community project for a niche OS for niche smartphones
17:25.25LingerHowever I'd be more than happy to leave you gents alone. I just don't know where the Aussies go on IRC anymore. I've been out of it for a long time.
17:25.36LingerI apologise.
17:26.04LingerI have no intention to take the discussion off topic
17:26.15kerioperhaps you might want to connect to a less-specific irc network?
17:26.36LingerI'm open to suggestions
17:27.11LingerLike I said, I have no idea where to go.
17:27.27kerio\_o_/
17:27.41kerioi have no idea, sorry
17:27.43LingerI'm a somewhat drunk InfoSec fag. Aussie.
17:28.10LingerNo problem mate.
17:28.23*** join/#maemo-ssu _rd (~rd@p57B491F4.dip0.t-ipconnect.de)
17:28.54LingerWould it be a problem to entertain my somewhat drunken self on this channel for a while?
17:29.18LingerGiven that there does not seem to be much else going on.
17:30.45kerioare you kidding me
17:30.46LingerI can ensure my questions are technology based.
17:30.53kerioquestions about what
17:31.01keriothere's 53 people here
17:31.09keriothere's probably about 20 times in #linux or whatever
17:31.18LingerAnd none of them seem to be active.
17:31.58DocScrutinizer05so you're interested in monologues?
17:32.06LingerI've worked as an InfoSec analyst for a while.
17:32.21DocScrutinizer05tease us
17:32.24LingerSurely theres some middle ground
17:33.53LingerMonologues to me relates to the English literature definition.
17:34.24kerioDocScrutinizer05: he's annoying and off-topic - but then again, there's not really anything else going on, here
17:34.48DocScrutinizer05I'm not yet ready to kick him
17:34.58LingerFair call.
17:35.05DocScrutinizer05off topic isn't a problem as long as nobody complains
17:35.31LingerIs InfoSec off topic?
17:35.35DocScrutinizer05chances for somebody complaining increase the more the talk is OT though
17:35.42DocScrutinizer05not per se
17:35.54keriowtf is infosec anyway?
17:36.10LingerInformation Security
17:37.15LingerI did InfoSec for a very large company, that you would all know.
17:37.48LingerYou cunts are interested in tech issues. I imagine you may have questions
17:38.06kerioDocScrutinizer05: we could make him audit maemo :D
17:38.23LingerThis is on topic no?
17:38.53DocScrutinizer051. warning: speech
17:40.06*** mode/#maemo-ssu [+o kerio] by ChanServ
17:40.15DocScrutinizer05just in case
17:41.15LingerAsk a cunt who was considered one of the three people within the organisation who was considered knowledgeable enough to make judgements on InfoSec issues.
17:41.21Lingerask anything
17:42.18LingerA global organisation. 70,000+ users
17:43.48LingerIs this not intersting?
17:48.52LingerNo? I do remember how IRC works. You can reply to me if you like.
17:50.08LingerI have a good job. I have made the most of my IT experience.
17:50.41LingerSo what?
17:50.59LingerKick/Ban me.
17:52.08DocScrutinizer05how to get the root certificate of any security infra (here: the one Nokia implemented with aegis)
17:52.45DocScrutinizer05(you know, for the simple questions we got google and wikipedia nowadays)
17:53.19Lava_Croftstrokes his beard
17:55.02*** join/#maemo-ssu _rd (~rd@p57B491F4.dip0.t-ipconnect.de)
17:56.53LingerOk. So I'm a guy who works on security on Pc's. I recently got a new phone. A Samsung S3 $g.
17:57.25LingerPlease tell me what issues I way have with this phone.
17:57.49Linger4g
17:57.54Lingerrather
18:00.42LingerNo?
18:01.50LingerIt seems as though IRC is as I remember it.
18:03.03LingerSo how long are you neck beards?
18:04.30LingerIRC is where you feel like you have some power
18:05.05kerioDocScrutinizer05: hold on, why am i opped?
18:05.24DocScrutinizer05just in case, since I'm busy
18:08.32LingerSd.
18:08.40LingerSad
18:09.36LingerAnd then what?
18:11.12LingerCook some bacon and eggs
18:11.25kerioLinger: you're being annoying
18:11.30keriostop or leave
18:13.58keriohm
18:14.09*** mode/#maemo-ssu [-o kerio] by kerio
18:14.22*** join/#maemo-ssu _rd (~rd@p57B491F4.dip0.t-ipconnect.de)
18:35.38*** join/#maemo-ssu NIN102 (~NIN@p5DD28E2D.dip0.t-ipconnect.de)
18:59.23*** join/#maemo-ssu _xnt14 (~xnt14@xceleo.us)
19:16.01freemangordonmerlin1991: ping
19:33.31merlin1991freemangordon: pong
19:41.01*** join/#maemo-ssu Woody14619 (~Woody@Maemo/Community/council/Woody14619)
19:59.34*** join/#maemo-ssu arcean (~Arcean@aaeo131.neoplus.adsl.tpnet.pl)
20:13.52freemangordonmerlin1991: http://talk.maemo.org/showpost.php?p=1295049&postcount=59
20:14.10freemangordontklock leaks like mad :(
20:14.30freemangordonI need an advise and/or help what to do
20:15.05merlin1991let's start easy for me, what is tklock?
20:15.22freemangordonswipe-to-unlock thingie
20:15.37arceanoh nooo
20:15.55freemangordonarcean: yes :(
20:15.59freemangordontry it
20:16.01arceanlooks like everything with 'systemui' in a name leaks
20:16.05freemangordonyes
20:16.16merlin1991freemangordon: does it need anything special on device to start leaking like mad?
20:16.24freemangordonnothing afaik
20:16.35freemangordonwell, didn't tested on stock, only on -thumb
20:16.42freemangordonbut that should be irrelevant
20:16.52merlin1991anything special to test that?
20:16.58freemangordonnothing
20:17.05merlin1991does not even know how to get per process ram on linux :$
20:17.27freemangordoncheck /proc/`pidof systemui`/smaps
20:17.31freemangordon[heap] section
20:17.44freemangordonit leaks about 16k on unlock
20:18.15freemangordonnow, the real problem is that there is no x86 binary
20:18.45freemangordonand I am just not good enough with GTK to rewrite it
20:19.11merlin1991is the smaps output a huge thing?
20:19.21merlin1991for me it goes over the xterm backsroll buffer
20:19.31freemangordoncat /proc/`pidof systemui`/smaps | more
20:19.40freemangordonit is the 3rd thing
20:20.41freemangordonBTW that leak is without any sms-es, mails, etc
20:20.57freemangordondidn't check what happens if there is some icon on unlock screen
20:22.40merlin1991hm it happily stays @ 1296kb here after an unlock (stock device)
20:23.01*** join/#maemo-ssu dhbiker (~dhbiker@95.87.145.172)
20:24.22merlin1991leaks only from time to time, not always
20:24.35freemangordonyeah, in chunks of 48k
20:24.35merlin1991I managed todo some 3 unlocks without an increase in heap size
20:24.38freemangordonor something
20:24.49keriodafuq, osso-systemui-tklock can be uninstalled
20:24.49freemangordonyep 48k/3 unlocks
20:25.00merlin1991<PROTECTED>
20:25.07merlin1991kerio: obviously
20:25.15keriowill shit break if i do?
20:25.21merlin1991it was only hold by the old @nokia metapackge
20:25.23merlin1991kerio: nfc
20:25.37keriook, i have to make a backup anyway
20:25.45freemangordonwell, it is usefull for those of us who don't have cases
20:26.29merlin1991freemangordon: yep it definitely leaks when you use the slider
20:26.40freemangordonmerlin1991: yeah, I know :(
20:26.59merlin1991arcean: what else with systemui did leak?
20:27.07freemangordonbtw the first time you use it (after reboot) heap usage jumps from 700k to 1400k
20:27.27merlin1991freemangordon: that's probably a gtkpixbuf for the backgroundimage
20:27.41freemangordonso, not only it leaks, it seems to keep the background in memory
20:27.41keriomerlin1991: 700kb for a 800x480 bitmap?
20:27.45arceanmerlin1991: osso-systemui-alarm :P
20:27.57freemangordonmerlin1991: exactly my thoughts
20:28.16freemangordonarcean: well, that should be ok now, check the latest commits
20:28.21merlin1991kerio: do the maths, 3 byte each pixel
20:28.44freemangordonand that's pretty instane
20:28.47keriohm
20:28.51keriothat's about 1mb
20:28.56freemangordonyeah
20:28.56merlin1991yeah
20:29.07kerioneat!
20:29.11freemangordonof memory which gets lost
20:29.20freemangordoneffectively
20:29.22Woody14619Actually... IT shouldn't, as it reloads it on re-lock anyway...
20:29.42freemangordonmost probably it does not reload it
20:29.56Woody14619I say, having written a script that updates the screen, so I know it in fact does.
20:30.03merlin1991freemangordon: or it reuses the same pixbuffer and loads a new image into it ;)
20:30.04freemangordonwell, no idea what it does, but it is a piece of crap
20:30.11freemangordonmerlin1991: could be
20:30.22Woody14619merlin1991: That may be to.. It's a fixed-size picture.
20:31.31Woody14619I wonder which is worse?  Having the pages allocated, or freeing an allocing each time, causing fragmentation?
20:31.58merlin1991well I see a point in keeping the pixbuf around, but the leak is definitely a nogo
20:32.15freemangordonWoody14619: if you have pages allocated and DON'T LEAK makes sense
20:32.16keriojust keep dat shit on the stack
20:32.36Woody14619nods
20:32.49kerioor, better, uninstall it
20:33.10freemangordonthough if I am to write such a think, i'll free the pixbuf when not needed
20:33.16freemangordon*thing
20:33.41merlin1991freemangordon: well in this case the probably had a minimal delay till displayed requirement
20:34.13merlin1991and loading the image into memory produces "some" delay, especially when the phone does something else at the time the user hits the button
20:34.31freemangordonmerlin1991: agree, makes sense
20:35.25freemangordonthough by the time you need it, there is a very high probability it was already swapped ;)
20:35.30merlin1991also "grep -A 9 heap /proc/`pgrep systemui`/smaps" is way more readable than the huge output to more :D
20:35.47freemangordon:D
20:36.27freemangordonnow, we have a couple of options here:
20:36.30merlin1991theoretically swapping back in has better performance than reading from the the disc ;), plus you still get read of the alloc
20:37.02freemangordonmerlin1991: in case swap and fs does not clash :P
20:37.13freemangordonthe options:
20:37.18freemangordon1. RE
20:37.35freemangordonthat will be the harest way as there is no x86 binary
20:37.44freemangordon2. rewrite
20:37.49merlin1991hm I'd try to snoop the interfaces and rewrite
20:37.51keriohahaha
20:37.57kerioi uninstalled osso-systemui-tklock
20:38.09freemangordonmerlin1991: we have the interfaces
20:38.14merlin1991but the sms stuff probably is odd todo
20:38.29merlin1991also for the inlays such as missed calls, msgs and whatnot?
20:38.55DocScrutinizer05haha, now I see why I get uptimes of weeks while others suffer from swap fragmentation and low memory after 3..5 days - I never use that tklock screen
20:38.57merlin1991DocScrutinizer05: first time we have a valid reason (even in your book) to replace a closed component :D
20:39.01kerioi can't lock my screen
20:39.14DocScrutinizer05yes, definitely
20:39.17keriothis was fun :D
20:39.33kerioshould i try reinstalling it, or should i just restore the backup?
20:39.36merlin1991kerio: what happens if you hit the powerbutton and press the lock screen button?
20:39.42freemangordonwell, according to IDA tklock uses stuff like sqlite3_exec :)
20:39.51merlin1991uh
20:39.53keriomerlin1991: the powerkey menu disappears and nothing happens
20:40.07merlin1991kerio: well reinstall is probably enough
20:40.19DocScrutinizer05dafaq wut? sqlite3? in tklock?
20:40.27freemangordonyeah
20:40.35DocScrutinizer05are they mad now?
20:40.35merlin1991probably for the sms db
20:40.45merlin1991just my wild guess
20:40.56freemangordongouys, just do apt-cache show osso-systemui-tklock on your devices ;)
20:41.06freemangordonmerlin1991: yeah, most probably
20:41.15freemangordon*guys
20:41.30freemangordonlook at the maintainer fueld :P
20:41.34freemangordon*field
20:42.05freemangordonas kerio pointed, there is ext- part
20:42.10merlin1991kerio: the pkg has no install scripts and just provides a lib so installing should be all you need
20:42.21freemangordon(besides the maintainer is she)
20:42.23DocScrutinizer05freemangordon: hm?
20:42.44DocScrutinizer05yeah, ext- part
20:42.44freemangordonseems like it is not written by nokia, but some third party
20:42.44merlin1991freemangordon: should I contact her?
20:42.54DocScrutinizer05sure
20:42.55freemangordonmerlin1991: yeah, lets try
20:43.03DocScrutinizer05many things are outsourced
20:43.30merlin1991freemangordon: I guess the best attempt would be to ask for some information in order to write a replacement
20:43.41DocScrutinizer05that's one of main reasons not to open source stuff
20:43.44freemangordonmerlin1991: hmm, what info do you need?
20:43.52DocScrutinizer05Nokia doesn't hold (C)
20:44.11merlin1991freemangordon: well I'm most probably not going to rewrite it ;)
20:44.20freemangordontoldya, we have almost everything we need to write systemui plugins
20:44.25freemangordonif not everything
20:44.30merlin1991hm why contact then?
20:44.41freemangordonask for the source code :P
20:44.59merlin1991we can't possibly get a sourcedump unless she can get her and nokias legal department to relicense the fun
20:45.11freemangordonforget that
20:45.19freemangordonno way to happen
20:45.43merlin1991and I'm not going to push some under the hand source dump to the cssu repo
20:45.58freemangordonmerlin1991: ok, i'll push it :P
20:46.05freemangordonjust give it to me :D
20:46.15merlin1991btw freemangordon where are the docs on what we know about systemui plugins?
20:46.27freemangordonmerlin1991: no docs afaik
20:46.38freemangordonwell, there is some systemui-dev package
20:46.49merlin1991that's kinda something I miss about all the re work around maemo, nobody ever documents his findings for others
20:47.08freemangordonwith only docs in it, didn't look what exactly is written there
20:47.25DocScrutinizer05merlin1991: +1
20:47.27keriodafuq, what's that new osso-systemui-alarm?
20:47.40keriofreemangordon: !
20:47.47keriofreemangordon: !!!
20:47.53keriofreemangordon: ^_^
20:48.12arceankerio: fixed memory leaks :P I hope ;]
20:48.37freemangordonkerio: https://gitorious.org/community-ssu/osso-systemui-alarm/commit/373fbcaaafdedee51744a1b696814fa6555a7670
20:49.09keriofreemangordon: yay
20:49.38freemangordonmerlin1991: yes, you are right re documentation
20:49.55freemangordonon the other hand it is still WIP. alarmui that is
20:52.01freemangordonmerlin1991: i can do tklock replacement skeleton, but can't do the GTK part
20:52.12*** join/#maemo-ssu M4rtinK (~M4rtinK@mail.melf.eu)
20:52.31freemangordonon the other hand... can we use Qt?
20:52.32keriodon't do the gtk part
20:52.36merlin1991freemangordon: nah
20:52.44freemangordonreason?
20:53.15merlin1991afaik gtk is in memory all the time
20:53.56freemangordonso? only needed Qt pages will be in memory
20:53.57DocScrutinizer05don't use qt for system stuff
20:54.01freemangordonok, ok
20:54.05DocScrutinizer05my 2 cents
20:54.14freemangordonI know you are right, was just hoping... :D
20:54.25merlin1991yeah qt is nice to write :)
20:54.45merlin1991looks a billion times better when you look at the source compared to gtk for me
20:54.46freemangordonthough... shortcutd anyone?
20:55.15merlin1991hm?
20:55.22DocScrutinizer05waves and hopes for a break
20:55.25freemangordonit is written in Qt
20:55.37merlin1991well mags lock screen overlay is written in qt aswell
20:55.55freemangordonarcean
20:55.57freemangordon?
20:55.57DocScrutinizer05those are no system replacement stuff though
20:56.01freemangordonwanna do it?
20:56.08freemangordonDocScrutinizer05: :nod:
20:56.24DocScrutinizer05aiui on my stock n900 there's no qt installed at all
20:56.31merlin1991DocScrutinizer05: yep
20:56.39freemangordonDocScrutinizer05: no way
20:56.41merlin1991but cssu always ships qt
20:56.42freemangordonafaik
20:57.09DocScrutinizer05o/
20:57.18DocScrutinizer05--->dinner
20:57.23freemangordontoo bad nicolai is no longer interested much in CSSU
20:57.33merlin1991ah wait pr1.3 depends on qt
20:57.47freemangordonMohammadAG ???
20:57.51freemangordonMohammadAG: ping
20:58.06merlin1991but I do remember a time where I had to install qt on maemo in order to run some qt things
20:58.09merlin1991must have been 1.1
20:58.43DocScrutinizer05well, since then they fixed their dependencies ;-P
20:58.44freemangordonyeah, but >=PR12 ships Qt with it
20:59.49DocScrutinizer05publish a call for GTK-devels
21:00.04freemangordonmerlin1991: yeah ^^^
21:00.11DocScrutinizer05there have to be 1 or 2 left over
21:04.12arceanDocScrutinizer05: re context menu: http://gitorious.org/community-ssu/gtk/blobs/master/gtk/gtkmenu.c#line3175
21:04.46freemangordonarcean: i owe you a beer. Or whatever you like to drink
21:04.49arceanit's already implemented, but treshold value is low
21:05.13arceanfreemangordon: uhm why :D ?
21:05.13freemangordonthis is the next thing in maemo after the alarmui (stock) I hate :)
21:05.20freemangordoncontext menu
21:05.38freemangordonthe way it appears
21:06.10arceanyup, it's broken by design (tm) :)
21:06.18DocScrutinizer05arcean: g_object_get (gtk_widget_get_settings (widget), 3167                        "gtk-dnd-drag-threshold", &threshold, 3168                        NULL);  <--what does that mean?
21:07.36arceandeveloper can change the treshold value in the application's code
21:08.18*** join/#maemo-ssu freemangordon_ (~freemango@213.226.63.163)
21:08.26DocScrutinizer05err what? it's for fetching a hardcoded constant?
21:09.07DocScrutinizer05not a gconf key maybe?
21:09.16freemangordon_The fuck, power outage. What's going on with that recently :-(
21:09.25arceanDocScrutinizer05: no, it's read/write property
21:09.40freemangordon_Object property
21:09.50DocScrutinizer05sorry, nfc. gibberish to me
21:10.48DocScrutinizer05anyway this *should* be a gconf key
21:11.11DocScrutinizer05maybe not at this location, maybe somewhere in init
21:11.52DocScrutinizer05http://gitorious.org/community-ssu/gtk/blobs/master/gtk/gtkmenu.c#line3140
21:11.55arceanso the developer can overwrite our default value, it makes sense :)
21:12.32freemangordon_arcean: so the default is bad?
21:13.51arceanif you move slightly your finger, the context menu will disappear or even won't show
21:14.22freemangordon_Yeah, we all know that :-D
21:14.42arceanmaybe it's ok with stylus but for sure not with finger
21:14.51*** join/#maemo-ssu sixwheeledbeast (~sixwheele@cl-1547.lon-02.gb.sixxs.net)
21:15.14freemangordon_Hmm, still no power, wtf has happened?
21:17.29arceanheh, the default value is 8 pixels
21:17.37DocScrutinizer05arcean: the question is: can we fix it? preferably in a way so threshold is a gconf key (or otherwise user configurable)?
21:19.49DocScrutinizer05arcean: aiui replacing #3166 by a call to read a gconf key should already work
21:20.02DocScrutinizer05s/work/suffice/
21:21.58arceanI'll check
21:23.48DocScrutinizer05hmm, for anchor I found http://gitorious.org/community-ssu/gtk/blobs/master/gtk/gtkmenu.c#line2995 so far. will be fun to find where coords to show that popup menu are set
21:25.40*** join/#maemo-ssu freemangordon (~freemango@130-204-50-168.2074221835.ddns.cablebg.net)
21:26.04DocScrutinizer05hmmm http://gitorious.org/community-ssu/gtk/blobs/master/gtk/gtkmenu.c#line2914
21:27.48DocScrutinizer05or rather here: http://gitorious.org/community-ssu/gtk/blobs/master/gtk/gtkmenu.c#line2947 ?
21:28.13*** join/#maemo-ssu don_falcone (~Miranda@p5DDA9AB6.dip.t-dialin.net)
21:28.18DocScrutinizer05http://gitorious.org/community-ssu/gtk/blobs/master/gtk/gtkmenu.c#line2923
21:28.29*** join/#maemo-ssu FredrIQ|n900 (~FIQ@unaffiliated/fiq)
21:29.23DocScrutinizer05aiui that's for showing menu either above or below touchpoint?
21:30.42arceanthe gconf-library depends on gtk, so it's a bit problematic
21:32.50DocScrutinizer05yeah, when I click in lower right corner of screen, then popup menu will show to the upper left of touchpoint. So it's already all there, just conditions for picking one or the other are crap
21:32.54freemangordonarcean: afaik those properties have default values
21:33.15arceanfreemangordon: yes, and it's 8pix by default
21:33.21freemangordonWTF?
21:33.42freemangordonwell, lets change that to 128 or something. Problem solved
21:33.48arceanhttp://gitorious.org/community-ssu/gtk/blobs/master/gtk/gtksettings.c#line331
21:34.17DocScrutinizer05arcean: why is gconf-lib depends gtk a problem?
21:34.39DocScrutinizer05isn't that gtk we're looking at ?
21:36.21DocScrutinizer05arcean: I just can't believe all that stuff in line 331 and before is just a nice way to write a comment. There has to be some function and meaning behind all this
21:36.41DocScrutinizer05I.E. a way to change the value from default set there
21:37.09arceanDocScrutinizer05: we can change the default value to the another, hardcoded one
21:37.20DocScrutinizer05like hildon-desktop --gtk-dnd-drag-threshold=65
21:38.05DocScrutinizer05nobody would create sucha structure with comment and all, just to read "8" at another point in code
21:39.14DocScrutinizer05g_param_spec_int sounds pretty much like "specify parameter" to me
21:39.46DocScrutinizer05parameter in turn makes my think about commandline parameters or configfile parameters
21:41.15DocScrutinizer05and G_MAXINT is probably the upper limit allowable for that parameter. Who's going to check that, when, and where?
21:43.31DocScrutinizer05http://gitorious.org/community-ssu/gtk/blobs/master/gtk/gtksettings.c#line44
21:44.12DocScrutinizer05particularly GTK_SETTINGS_SOURCE_RC_FILE
21:44.30*** join/#maemo-ssu nox- (noident@freebsd/developer/nox)
21:45.54DocScrutinizer05I'd suspect sth like this whole crap looking for /etc/gtk/filemanager.rc and in there for a line gtk-dnd-drag-threshold=120
21:47.27DocScrutinizer05maybe should ask rasterman, he should know a bit about gtk afaik
21:48.31freemangordonDocScrutinizer05: not that I am much in GTK, but it most probably looks in the current theme
21:48.33DocScrutinizer05or just scrutinize that code a tad longer, and find out where else GTK_SETTINGS_SOURCE_RC_FILE is used
21:48.48DocScrutinizer05theme, YEAH
21:48.53DocScrutinizer05sounds about right
21:49.10freemangordon"/usr/share/themes/alpha/..." or whatever the path was
21:50.05DocScrutinizer05freemangordon: look at http://gitorious.org/community-ssu/gtk/blobs/master/gtk/gtksettings.c#line44 please. What's the ideas that gives you?
21:52.13DocScrutinizer05http://gitorious.org/community-ssu/gtk/blobs/master/gtk/gtksettings.c#line194 hmm
21:52.30freemangordonI am too tired right now to grok that
21:52.52arceanhmm, gtk-dnd-drag-threshold is defined in my gtkrc file
21:52.56freemangordonwell, default should come from the theme
21:53.34freemangordonarcean: and what is the value?
21:53.35DocScrutinizer05http://gitorious.org/community-ssu/gtk/blobs/master/gtk/gtksettings.c#line533
21:53.44arceanfreemangordon: 30pix
21:53.53arceandefault theme
21:54.14freemangordondoes not seem used
21:54.30freemangordonso it could be in a rogn section or something
21:54.37freemangordon*wrong
21:54.51DocScrutinizer05arcean: where's that file? (path)
21:55.13arceanDocScrutinizer05: /usr/share/themes/default/gtk-2.0
21:55.17DocScrutinizer05thnaks
21:55.47freemangordonarcean: no matter what, we should change the default
21:58.38freemangordonanyway, I need some sleep
21:58.41freemangordonnight
22:01.53don_falcone@FMG: what's the timezone of the channel? The log link you send me is in the future *g*
22:02.56DocScrutinizer05arcean: should I delete gtkrc.cache when I edit gtkrc?
22:04.30DocScrutinizer05freemangordon: 30 pixel are 78/800mm
22:04.35DocScrutinizer05~78 / 800
22:04.36infobot0.0975
22:04.44DocScrutinizer05insane
22:04.55freemangordondon_falcone: UTC+2
22:05.06freemangordonDocScrutinizer05: oh
22:05.08DocScrutinizer05err * 30
22:05.13DocScrutinizer05~78 / 800 * 30
22:05.13infobot2.925
22:05.20freemangordonyeah, you'right
22:05.21DocScrutinizer05still not it
22:05.29freemangordonwe want at least 10mm
22:06.18DocScrutinizer05so make that 150
22:06.19*** join/#maemo-ssu sixwheeledbeast (~sixwheele@cl-1547.lon-02.gb.sixxs.net)
22:06.50freemangordonDocScrutinizer05: that should be fixed in gtk, not in the theme
22:06.58DocScrutinizer05I'd test it if I knew what to do with the cache file
22:06.58freemangordonwhat about those with custom themes?
22:07.11freemangordonafaik you should rebuild it
22:07.17freemangordonbut don;t ask me how
22:07.32DocScrutinizer05gcc I guess
22:07.40freemangordonnoo, hildon-something
22:07.48freemangordonor gtk-something
22:07.53freemangordonon the device
22:08.31freemangordonhildon-theme-recache-all
22:08.34freemangordoniirc
22:08.39DocScrutinizer05yeah, on device. For openmoko we needed gcc to build some gtk stuff on device
22:08.52freemangordonDocScrutinizer05: ^^^
22:09.30DocScrutinizer05(([2012-11-16 23:06:49] <freemangordon> DocScrutinizer05: that should be fixed in gtk, not in the theme)) so you suggest to remove the whole parameter from gtk?
22:10.00DocScrutinizer05since if you don't, theme will override
22:10.05*** join/#maemo-ssu myuu_ (~miku@pool-108-27-88-90.nycmny.east.verizon.net)
22:10.08freemangordonno, I suggest to check it and if it is below 150 lets say, to use 150
22:10.20DocScrutinizer05OUCH!
22:10.34freemangordonwe cannot fix every theme out there
22:10.48DocScrutinizer05why not?
22:10.58DocScrutinizer05I fix that crap with a sed oneliner
22:11.03freemangordonbecause there are hundreds of themes
22:11.13freemangordonthats an ugly hack
22:11.26DocScrutinizer05I don't see fucking up gtk to fix broken themes
22:11.29freemangordonuglier than mine :)
22:11.52freemangordon#if defined MAEMO_CHANGES :P
22:12.17freemangordonanyway, i am going to sleep. for real this time
22:12.19freemangordonnight
22:12.24DocScrutinizer05n8
22:12.39DocScrutinizer05I'm going to have a shower and then dinner, this time for real
22:12.52DocScrutinizer05freemangordon: just one more thing
22:13.05freemangordon?
22:13.17DocScrutinizer05click on a file in filemanager, but do it in lower right corner ;-)
22:13.44DocScrutinizer05it's all there, we just need to "enable" it
22:14.18DocScrutinizer05should be sth like a 10 char 'patch'
22:15.00freemangordonyeah, seems so
22:15.12DocScrutinizer05o/ :D
22:15.16freemangordonI gues it won't be that hard
22:15.20freemangordon*guess
22:15.34freemangordonwell, make that 10 lines
22:15.47freemangordonnight
22:34.26*** part/#maemo-ssu sixwheeledbeast (~sixwheele@cl-1547.lon-02.gb.sixxs.net)
22:45.16*** join/#maemo-ssu kolp (~quassel@212.255.20.215)
23:03.06*** join/#maemo-ssu Jade (~jade@Jade.broker.freenet6.net)
23:03.06*** join/#maemo-ssu Jade (~jade@unaffiliated/jade)
23:03.11*** join/#maemo-ssu myuu_ (~miku@pool-108-27-88-90.nycmny.east.verizon.net)
23:05.34*** join/#maemo-ssu jon-kha (~jon-kha@hoasnet-fe32dd00-87.dhcp.inet.fi)
23:10.41*** join/#maemo-ssu myuu_ (~miku@pool-108-27-88-90.nycmny.east.verizon.net)

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.