IRC log for #maemo-ssu on 20130704

00:27.08*** join/#maemo-ssu infobot (~infobot@rikers.org)
00:27.08*** topic/#maemo-ssu is Maemo Community Seamless Software Update "CSSU" channel, http://wiki.maemo.org/Community_SSU | Known bugs: http://j.mp/communityssu-bugs | Channel logs: http://mg.pov.lt/maemo-ssu-irclog/ | Sources: http://gitorious.org/community-ssu/ | Latest version: Testing(2013-06-14): 21.2011.38-1Tmaemo8.2; Stable(2013-01-10): 21.2011.38-1Smaemo6
00:27.08*** mode/#maemo-ssu [+v infobot] by ChanServ
00:30.09*** join/#maemo-ssu _jester_ (~jester@182.188.227.105)
00:30.16_jester_hello world
00:30.21_jester_are the repos down ?
01:49.03*** join/#maemo-ssu LaoLang_coo_ (~LaoLang_c@120.85.133.215)
02:11.31*** join/#maemo-ssu Martix_ (~martix@static-84-242-103-180.net.upcbroadband.cz)
02:59.34*** join/#maemo-ssu amiconn_ (quassel@rockbox/developer/amiconn)
05:25.56*** join/#maemo-ssu kolp (~quassel@212.255.20.92)
05:53.31*** join/#maemo-ssu tg (~x@unaffiliated/tg)
06:57.04*** join/#maemo-ssu LauRoman (~LauRoman@5-14-93-43.residential.rdsnet.ro)
07:15.09Raimufreemangordon: Happy belated birthday!
07:29.16*** join/#maemo-ssu M4rtinK (~M4rtinK@ip-89-177-124-122.net.upcbroadband.cz)
07:37.31LauRomanthis is my first "manual install" of an n900 app on my phone and the readme for it says i should copy the icon file and .desktop file to the apropriate system folders. Can anyone tell me what those folders are?
07:50.39*** join/#maemo-ssu Pali (~pali@Maemo/community/contributor/Pali)
08:27.09*** join/#maemo-ssu andre__ (~andre@ip-89-176-96-40.net.upcbroadband.cz)
08:27.09*** join/#maemo-ssu andre__ (~andre@wikimedia/aklapper)
09:12.56*** join/#maemo-ssu Martix_ (~martix@static-84-242-103-180.net.upcbroadband.cz)
09:19.01*** join/#maemo-ssu arcean (~arcean@aaeu223.neoplus.adsl.tpnet.pl)
09:25.22*** join/#maemo-ssu Martix (~martix@static-84-242-103-180.net.upcbroadband.cz)
09:25.29*** join/#maemo-ssu arcean_ (~arcean@aaeu223.neoplus.adsl.tpnet.pl)
09:25.45*** join/#maemo-ssu povbot (~supybot@office.pov.lt)
09:25.45*** mode/#maemo-ssu [+v povbot] by ChanServ
09:29.02*** join/#maemo-ssu Pali_ (~pali@Maemo/community/contributor/Pali)
09:30.52*** join/#maemo-ssu macmaN_ (~chezburge@138.167.190.90.dyn.estpak.ee)
09:30.57*** join/#maemo-ssu DocAvalanche (~lagrange@openmoko/engineers/joerg)
09:36.23*** join/#maemo-ssu psycho_oreos (~no@unaffiliated/tuxsavvy)
10:15.12*** join/#maemo-ssu futpib (~futpib@89.106.197.21)
10:22.50*** join/#maemo-ssu M13 (~Miranda@83.149.37.103)
10:33.50*** join/#maemo-ssu discopig (~discopig@unaffiliated/discopig)
10:44.20*** join/#maemo-ssu piscodig (~discopig@unaffiliated/discopig)
10:56.18*** join/#maemo-ssu piscodig (~discopig@unaffiliated/discopig)
11:36.23*** join/#maemo-ssu Pali (~pali@Maemo/community/contributor/Pali)
12:11.31*** join/#maemo-ssu lizardo (lizardo@nat/indt/x-hzgnqaowjhcoywpn)
12:14.59*** join/#maemo-ssu lizardo (lizardo@nat/indt/x-icurkixitjyuxddn)
12:40.56*** join/#maemo-ssu lizardo (lizardo@nat/indt/x-jugxcyszfiysburc)
12:43.56*** join/#maemo-ssu futpib (~futpib@89.106.197.21)
13:42.59*** join/#maemo-ssu sunny_s (~sunny_s@business-092-079-020-027.static.arcor-ip.net)
13:46.59*** join/#maemo-ssu Pali (~pali@Maemo/community/contributor/Pali)
14:02.19*** join/#maemo-ssu Pali_ (~pali@Maemo/community/contributor/Pali)
14:05.30*** join/#maemo-ssu mkaindl_ (~mkaindl_@ama-dablam.markus-kaindl.de)
14:21.14*** join/#maemo-ssu freemangordon (~freemango@130-204-50-168.2074221835.ddns.cablebg.net)
14:23.58*** part/#maemo-ssu mkaindl_ (~mkaindl_@ama-dablam.markus-kaindl.de)
14:24.22*** join/#maemo-ssu mkaindl_ (~mkaindl_@ama-dablam.markus-kaindl.de)
14:39.20*** join/#maemo-ssu M4rtinK (~M4rtinK@ip-89-177-124-122.net.upcbroadband.cz)
14:52.32*** part/#maemo-ssu mkaindl_ (~mkaindl_@ama-dablam.markus-kaindl.de)
14:53.16*** join/#maemo-ssu mkaindl_ (~mkaindl_@ama-dablam.markus-kaindl.de)
14:55.47*** join/#maemo-ssu kolp (~quassel@212.255.20.92)
15:03.38*** part/#maemo-ssu mkaindl_ (~mkaindl_@ama-dablam.markus-kaindl.de)
15:15.16Pali_there are two CSSU pending merge request: https://gitorious.org/community-ssu/calendar-backend/merge_requests/1 https://gitorious.org/community-ssu/qt-x11-maemo/merge_requests/5
15:15.24Pali_merlin1991, freemangordon ^^^
15:15.33Pali_I think that qt one is OK
15:37.43*** join/#maemo-ssu M13 (~MirandaLS@170.133-224-87.telenet.ru)
15:38.49*** join/#maemo-ssu M13 (~MirandaLS@170.133-224-87.telenet.ru)
15:40.23*** join/#maemo-ssu M13 (~MirandaLS@170.133-224-87.telenet.ru)
15:47.17*** join/#maemo-ssu oldtopman (~oldtopman@unaffiliated/oldtopman)
15:59.10*** join/#maemo-ssu NIN101 (~NIN@p5DD2BE0C.dip0.t-ipconnect.de)
15:59.41*** join/#maemo-ssu futpib (~futpib@89.106.197.21)
16:12.39*** join/#maemo-ssu sixwheeledbeast (~paul@cl-1547.lon-02.gb.sixxs.net)
16:26.05*** join/#maemo-ssu sixwheeledbeast (~paul@cl-1547.lon-02.gb.sixxs.net)
17:00.55*** join/#maemo-ssu discopig (~discopig@unaffiliated/discopig)
17:25.18*** part/#maemo-ssu mkaindl (~mkaindl@ama-dablam.markus-kaindl.de)
17:29.32*** join/#maemo-ssu smps (~smps@brk.ehet.net)
17:41.36*** join/#maemo-ssu futpib_ (~futpib@89.106.198.173)
17:58.30psycho_oreosHi, I've just updated from T7.1 to T8.1 using fapman, I know awhile ago I put a hacked fmtxd binary to enable more than allowed frequencies. Since then I have not noticed any constant high CPU usage apart from this update (to T8.2). I checked the changelogs from wiki and there was nothing detailing in regards to fmtxd being updated. Any insights? TIA.
18:01.36psycho_oreosCorrection, /usr/sbin/fmtxd and /usr/bin/pulseaudio are pretty much topping out the whole CPU consumption, with fmtxd ranging from 50% to 65% and pulseaudio taking up to 35% or so.
18:13.55*** join/#maemo-ssu Vlad_on_the_road (~Vlad_on_t@ip-66.net-82-216-1.versailles2.rev.numericable.fr)
18:19.23keriothat's about standard for pulseaudio, isn't it :D
18:19.28keriotry the stock fmtxd
18:19.38kerioit shouldn't change anything
18:21.51psycho_oreosI was about to add, I've stopped pulseaudio and restarted pulseaudio. This time pulseaudio takes up the entire CPU, it even lags the device as well which I'm thinking is far worse than when CPU was to be shared between fmtxd and pulseaudio. I tried running pulseaudio without going through start/stop processes however I have been unsucessful in obtaining errors into a file which I can read easily later on.
18:22.22psycho_oreosI read that there was a downgrade in pulseaudio for performance-wise choice.
18:27.56psycho_oreosHmm funny how running pulseaudio through manual intervention creates no new entries in syslog. Besides the information contained in syslog is insanely old. I'm going to merge old syslog info, bzip2 it and try again. I think these were optified but cannot see why it won't write to the new symlinked location
18:56.07*** join/#maemo-ssu Martix (~martix@46.227.13.46)
18:58.11*** join/#maemo-ssu M4rtinK (~M4rtinK@46.227.13.46)
18:59.33psycho_oreosHere is the output of "pulseaudio --system -v --log-target=syslog": http://pastebin.com/Eb4JExDA I have only ran the process for only 5 seconds before sending out interrupt (Ctrl+C) signal.
19:01.02psycho_oreoskerio, yes as much as I would love to say pulseaudio is really lame, there aren't much other alternatives for N900. I have had issues with pulseaudio in the past and this brings back those haunts.
19:05.24*** join/#maemo-ssu M13 (~MirandaLS@170.133-224-87.telenet.ru)
19:07.02*** join/#maemo-ssu M13 (~MirandaLS@170.133-224-87.telenet.ru)
19:08.54DocScrutinizer05*sigh* I heard somebody been so brave and hacked PA
19:09.19DocScrutinizer05idly wonders how QA for *that* might look like
19:36.40*** join/#maemo-ssu DocScrutinizer05 (~saturn@openmoko/engineers/joerg)
19:38.35*** join/#maemo-ssu g3kk3r_ (torrkull@lehtori.cc.tut.fi)
19:42.11*** join/#maemo-ssu NIN101 (~NIN@p5DD2BE0C.dip0.t-ipconnect.de)
19:42.20*** join/#maemo-ssu M4rtinK (~M4rtinK@46.227.13.46)
20:03.56*** join/#maemo-ssu ruskie (ruskie@sourcemage/mage/ruskie)
20:07.56*** join/#maemo-ssu s1gk1ll_ (~sigkill@2.82.37.208)
20:08.16*** join/#maemo-ssu _rd (~rd@p57B48558.dip0.t-ipconnect.de)
20:34.43*** join/#maemo-ssu futpib__ (~futpib@89.106.197.101)
20:48.54*** join/#maemo-ssu arcean (~arcean@aaeu223.neoplus.adsl.tpnet.pl)
20:52.10*** join/#maemo-ssu LauRoman (~LauRoman@5-14-93-43.residential.rdsnet.ro)
20:59.55*** join/#maemo-ssu _rd (~rd@p57B48558.dip0.t-ipconnect.de)
21:04.12*** join/#maemo-ssu nox- (noident@freebsd/developer/nox)
21:10.07*** join/#maemo-ssu mkaindl_ (~mkaindl_@ama-dablam.markus-kaindl.de)
21:17.44*** join/#maemo-ssu arcean (~arcean@aaeu223.neoplus.adsl.tpnet.pl)
21:33.31*** join/#maemo-ssu xes (~xes@unaffiliated/xes)
21:36.19*** join/#maemo-ssu BCMM (~BCMM@unaffiliated/bcmm)
21:38.20freemangordonpsycho_oreos: how did you update ti T8.2?
21:38.24freemangordon*to
21:45.35*** join/#maemo-ssu Martix (~martix@46.227.13.46)
21:47.02DocScrutinizer05fapman, he said
21:47.15freemangordonhmmm
21:47.25DocScrutinizer05yep
21:47.36freemangordonI bet he has different versions of PA and the libs
21:47.51DocScrutinizer05no surprise with fapman, eh?
21:48.16freemangordonnever used it, so can't judge ;)
21:48.26freemangordonbut won;t be surprised
21:48.36DocScrutinizer05same here, but judging by the reports and public info
21:48.44freemangordonyep
21:49.32DocScrutinizer05fapman needed 12,5 minutes to waste its chance on my device
21:49.48freemangordon:)
21:49.54freemangordonnever installed here
21:49.56DocScrutinizer05ok, that's several years ago
21:50.44DocScrutinizer05but - you know - there's a certain user experience that makes it extremely unlikely that a package will ever get a second chance
21:51.10freemangordonyeah, esp if it son supported
21:51.24freemangordons/it son/ it is not/
21:51.58DocScrutinizer05supported or maintained?
21:52.16freemangordonhowever, I'll wait psycho_oreos to report his PA and Pa libs versins
21:52.20freemangordonDocScrutinizer05: both
21:56.02DocScrutinizer05know what? I had a weird phantasy a few days ago: every garage- and/or tmo-user would pay 10ct per month to pay techstaff and maintainers for their work. I probably could live with that, literally
21:56.43freemangordonhm? why is that?
21:56.54DocScrutinizer05why is what?
21:57.15freemangordonthe payments
21:57.19DocScrutinizer05why I got phantasies? dunno
21:58.06DocScrutinizer05the payment, why? nfc
21:58.15DocScrutinizer05I don't think it ever will happen
21:58.56DocScrutinizer05wouldn't know why any user would be willing to pay 10ct/month for using maemo.org services
21:59.09DocScrutinizer05after all they all paqid for their N900 already
22:01.39DocScrutinizer05I just had that weird equation in front of my inner eye: 80k garage users + (50k tmo users * NN% for those who got both accounts) * 0.10$
22:03.36DocScrutinizer05heck, for two ct/month from each of them, I'd dedicate my time to maemo.org exclusively
22:03.59DocScrutinizer05ooops there's the problem, I already do that, even without those 2ct/user
22:05.03DocScrutinizer05but sometimes I suddenly face reality and realize I can't sustain that indefinitely
22:05.23RaimuThe problem I think is that there is a huge leap to be made in mentality when stepping from free to any kind of payment, even ridiulously low like $.1
22:05.49DocScrutinizer05yep, exactly
22:07.01*** join/#maemo-ssu int_ua (~int_ua@ip-602f.proline.net.ua)
22:07.18DocScrutinizer05that's why [2013-07-04 23:58:15] <DocScrutinizer05> I don't think it ever will happen
22:07.51xesi think that a big banner "buy a beer to your techstaff" would be better...
22:08.01DocScrutinizer05a pity since basically I like that job
22:08.32xeshello there..
22:08.38DocScrutinizer05oh, hi xes. Could you have a look at our firewalls?
22:09.09DocScrutinizer05I think they might have gotten a bit upset with our blade-a boot
22:09.32xesone guy arrives, starts talking about beers and.. this is your reply?
22:09.40DocScrutinizer05www.m.o is very slow, despite no particular load
22:10.17DocScrutinizer05:-) well, beer is a nice beverage
22:10.25DocScrutinizer05sometimes
22:11.22DocScrutinizer05you might have noticed it from icinga
22:11.36DocScrutinizer05(slowness of www.m.o that is)
22:12.05xeslet me check
22:12.21kerioDocScrutinizer05: i'd send you HUNDREDS of satoshis
22:12.54DocScrutinizer05is this a currency that you need to pay to get rid of?
22:13.15kerio100M satoshis = 1 BTC
22:13.24DocScrutinizer05mhm
22:13.41DocScrutinizer05so yeah, obviously you need to pay to handle that
22:14.14kerio1 BTC goes for 78.23248 USD on mtgox
22:14.34DocScrutinizer05what??
22:14.44kerioi know, the price dropped quite a lot
22:14.58keriothere were some huge spikes
22:15.00DocScrutinizer05nah
22:15.22DocScrutinizer05I never thought 1BTC was so valuable
22:15.37keriothey were worth at least 300$ at some point
22:15.47DocScrutinizer05ugh
22:16.15kerioalso, they need to be worth at least the cost of mining them
22:16.49keriootherwise you get no miners, and the blockchain becomes unsafe and slow
22:16.52DocScrutinizer05now those weirdos with their own powerplant to feed all the PCs with monster GFX cards, and the AC for that, make more sense
22:17.12keriolots of people have made ASICs
22:19.03DocScrutinizer05mhm
22:19.13DocScrutinizer05will paypal accept BTC?
22:19.18kerioanyway, the fact that the whole system is reliant on miners to keep the blockchain going is a longevity issue
22:19.39kerionope
22:20.45DocScrutinizer05good ;-P
22:22.30DocScrutinizer05I recently realized that I might have to learn about BTC, for darknet
22:23.13keriolike, buying drugs on silkroad?
22:23.26DocScrutinizer05for now I have a fuzzy idea of how that stuff works, at best
22:24.53DocScrutinizer05so yeah, please send me a few of those satoshi, never seen any
22:25.03kerioi actually don't have any
22:25.03DocScrutinizer05maybe they feel nice
22:25.40kerioand there's an almost mandatory transaction fee for transactions below... 0.01BTC or something
22:25.50xesnow www should work better
22:26.03DocScrutinizer05what did you doß
22:26.06DocScrutinizer05?
22:26.47DocScrutinizer05yeah, way better
22:27.10DocScrutinizer05firewalls?
22:27.59xeswith actual settings every apache should die in at max one hour or two. If you find a process with a longer uptime (excluding the parent executed as root) it's blocked doing ..(wtf... i still can't understand)
22:28.28xes..some script or bot query
22:29.37DocScrutinizer05mhm, so you killed stale apache processes?
22:29.42xesyep
22:29.47DocScrutinizer05:nod:
22:30.39DocScrutinizer05yeah, makes sense as well. I thought it's fw since I haven't seen extraordinary load but still even *connect* to www too ages
22:30.46DocScrutinizer05took*
22:31.25xesthere wasn't too much requests or traffic, just those apache asking for the meaning of life..
22:31.32DocScrutinizer05usually on high load it connects fast but takes ages to deliver responses
22:31.43DocScrutinizer05:-D
22:31.46DocScrutinizer0542
22:31.51xes..so i had to kill them to explain the sense
22:32.19DocScrutinizer05killall -42 apached
22:32.38DocScrutinizer05wonders what's signal 42
22:32.46DocScrutinizer05prolly siguserNN
22:32.54xesno, only the childs living too much
22:33.12DocScrutinizer0542) SIGRTMIN+8
22:33.34DocScrutinizer05:nod:
22:34.04DocScrutinizer05maybe we/I could bang together a scriptie to run every 5 min
22:34.34DocScrutinizer05man ps :-S
22:35.44DocScrutinizer05couldn't figure how to select processes that have a certain livespan
22:37.19DocScrutinizer05since I don't consider parsing output of ps or even htop a brilliant idea, probably man procfs
22:39.00xesthe best approach would be find what is creating this zombies..
22:46.07DocScrutinizer05sure
22:46.55DocScrutinizer05check which wchan they're on?
22:47.24DocScrutinizer05I'd not be surprised to find it related to NFS
22:53.13xesa quick check:  ps -eo etime,pid,user,command| grep apache| grep -v grep | sort
23:07.48DocScrutinizer05xes: yes, that's fine for interactive
23:07.59DocScrutinizer05xes: not though for a script
23:32.02*** join/#maemo-ssu RST38h (marat@wsip-184-180-40-182.ri.ri.cox.net)
23:37.03*** join/#maemo-ssu Martix (~martix@static-84-242-103-180.net.upcbroadband.cz)

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