IRC log for #maemo-ssu on 20120410

00:25.33*** join/#maemo-ssu LaoLang_cool (~LaoLang_c@221.226.175.138)
00:34.01*** join/#maemo-ssu gri (~gri@muhkuh.net)
00:39.03*** join/#maemo-ssu NIN101 (~NIN@206.253.166.69)
00:41.38*** join/#maemo-ssu gri (~gri@muhkuh.net)
00:46.38*** join/#maemo-ssu LaoLang_cool (~LaoLang_c@221.226.175.138)
01:49.13*** join/#maemo-ssu M4rtinK (~M4rtinK@mail.melf.eu)
02:29.23*** join/#maemo-ssu int_ua (~int_ua@46.151.80.36)
02:43.06*** join/#maemo-ssu amiconn_ (amiconn@rockbox/developer/amiconn)
04:54.04*** join/#maemo-ssu merlin_1991 (~merlin@merlin1991.at)
05:33.49*** join/#maemo-ssu Jade (erika@unaffiliated/jade)
05:54.37DocScrutinizer<merlin1991> (you'll have the partition that is long gone in the list even if you reboot your n900)  WTF?!
05:56.54DocScrutinizermerlin_1991: arcean: could we go thru *all* gconfkeys eventually? I feel like quite a lot of mess there, maybe we can do a major refactoring
06:02.32DocScrutinizer(re partition table, labels) this is a problem that exists for all flavours of linux/unix. Actually you'll find yourself fixing upstream kernel stuff
06:03.45DocScrutinizerunix never planned to have hot swappable drives, and there are *still* quite a number of problems atound all that, which usually get solved the "windows way" aka "mandatory reboot"
06:06.16DocScrutinizeractually a really removable drive will see complete new initialization on plugin, afaik. For changes on fundamental drive structures/properties like partition table there's not yet a proper foolproof concept to do that re-initialization without such unplug&replug or reboot, afaik
06:09.33DocScrutinizermerlin_1991: NFC though how an obsolete drive-info could survive reboot. *might* be related to friggin partition table concept, which iirc has two redundant ways to describe drive and partitions, and not all tools work on both concurrently to keep them in sync
06:11.19DocScrutinizerfirst test to dissect the problem: create a uSD that shows the problem, see if the problem sticks to the uSD when you insert the uSD to a "new" device
06:12.44freemangordonDocScrutinizer, no need for SD card, a simple compcache drive is enough
06:12.57DocScrutinizer??
06:12.59freemangordons/drive/device/
06:13.18DocScrutinizerhow you gonna insert that to a "new" N900?
06:13.29freemangordonmodins?
06:13.42freemangordoninsmod, sorry, still having my coffe
06:13.46freemangordon:D
06:13.47DocScrutinizernfc what you're talking about
06:14.14freemangordonby doing inmod ramzswap.ko, you are creating /dev/ramzswap0
06:14.39DocScrutinizerthat's completely unrelated and irrelevant here
06:14.46freemangordonand that is listed by blkid
06:14.56freemangordonsee backscroll
06:15.49DocScrutinizerwhat in >>first test to dissect the problem: create a uSD that shows the problem, see if the problem sticks to the uSD when you insert the uSD to a "new" device<< makes you think this could be done with ramzswap?
06:18.36DocScrutinizerthere's a couple of potential causes around the topic at large - kernel's device tables not really being flushable is just one, properties/structure of partition-table of one drive is another
06:18.53freemangordonDocScrutinizer, if you are talking about blkid bug, it could be triggered by using a virtual device, no need for a real SD card partition
06:20.07DocScrutinizerfor dissecting the "sticky across boot" problem which is the most severe one in my book, we want to tackle partition table the way I suggested above first
06:20.16freemangordonand compcache/ramzswap is such a device, blkid reports /dev/ramzswap0: TYPE="swap" long afater there is no such device in /dev
06:20.31freemangordonok
06:21.04freemangordonbut don't really see the difference
06:21.16DocScrutinizerafter solving this problem, we check what persisted and tackle those
06:21.44freemangordonanyway, I need more coffee
06:21.55DocScrutinizerthe non-flushable device tables in kernel are a known problem, since ages
06:22.17DocScrutinizerbut they won't explain why problem is sticky across boot
06:22.48DocScrutinizeralso runs for another coffee
06:23.13DocScrutinizerthough daywork waiting for me, need to wake up first
06:25.36DocScrutinizeralso all please make damn sure you check back on stock fremantle with stock kernel and manual (u)mounting, to get a clear idea where from the problems stem that we're chasing
06:26.15DocScrutinizerI anticipate most of them appear on stock as well
06:30.37DocScrutinizerfor problems clearly introduced by new ke-recv we know whom "to blame" and fix. For problems that are also in stock kernel and system even, we have to ponder where and how, or if at all to fix them. Might be mission impossible if the problem even exists in upstream 3.x kernel still
06:39.43DocScrutinizerfreemangordon: actually it doesn't matter at all if you use ramzswap partition or whatever else to create the problem, the point is we create the problem on a partition table we can insert to a new system that never before seen this problem, so we find out if the problem sits (and persists across boots) in partition table itself or rather somewhere in the rootfs
06:41.35DocScrutinizeror (worst case) in both together, in an either AND or OR way
06:46.32DocScrutinizer1) create problem  2a) "swap rootfs" to a "clean" one (by moving uSD to new system, or by restoing a clean rootfs backup to the affected device) 2b) on device with freshly created problem swap MBR/part-tbl of the affected storage to a known good version, via dd; reboot 3) evaluate your findings to conclude what's the nature of the issue and where to investigate further
06:47.10DocScrutinizermy suggestion above been about 2a)
06:47.36DocScrutinizerclearly done the most easy way by swapping uSD to a "new" device
06:56.07*** join/#maemo-ssu DocScrutinizer (~halley@openmoko/engineers/joerg)
07:05.33*** join/#maemo-ssu dafox (~dafox@dyn-194208.nbw.tue.nl)
07:09.19*** join/#maemo-ssu dafox (~dafox@dyn-194208.nbw.tue.nl)
07:21.44*** join/#maemo-ssu dafox (~dafox@dyn-194208.nbw.tue.nl)
07:24.28*** join/#maemo-ssu LaoLang_cool (~LaoLang_c@221.226.175.138)
07:36.08*** join/#maemo-ssu dafox (~dafox@dyn-194208.nbw.tue.nl)
07:40.39DocScrutinizerman addpart, man delpart
07:44.34DocScrutinizerhttp://www.cyberciti.biz/tips/re-read-the-partition-table-without-rebooting-linux-system.html
07:47.07DocScrutinizerman partprobe
07:51.28DocScrutinizerit's highly unclear (yet, to me) who (which programs - like sfdisk - or which daemons) does inform kernel to reread partition tables, esp on fremantle
07:52.50DocScrutinizeralso it's unclear how much of the infra needed to support all this is actually implemented in fremantle kernel, not to mention whether all that got tested and is bugfree or not
07:54.37DocScrutinizeranyway keep in mind there's - afaik - nothing in kernel or userland that's supposed to keep sticky as in across-boot any info about partition tables of attached devices
07:54.47DocScrutinizermaybe except /dev fs itself
07:58.13DocScrutinizerdepending on what the system is utilizing to create device nodes (udev, devtmpfs, ke-recv, manual mkdev calls, whatever), you easily might find an obsolete devicenode in /dev, or miss a devicenode for a new device or partition. Esp when "hotplugged" or - worse - created "on the fly" as new partition on a storage dev
08:11.53DocScrutinizeralso I think that while /dev/sdx (example) gets created by e.g. a udev rule, yet /dev/sdxN etc most likely are created vy the kernel driver itself, on invocation
08:12.18DocScrutinizers/vy/by/.
08:16.50*** join/#maemo-ssu juzn900 (~juzn900@203-219-240-117.static.tpgi.com.au)
08:21.24*** part/#maemo-ssu juzn900 (~juzn900@203-219-240-117.static.tpgi.com.au)
09:25.29*** join/#maemo-ssu Guest50125 (~rd@p57B498FA.dip0.t-ipconnect.de)
09:26.25DocScrutinizeror put simply: "<merlin199> runing blkid as root shows you some info about all partitions in the system. but when I reformatted my sd card to only have one partition I still have ghost entries in the output from blkid. even after a reboot[!!!]" and would you comment/correct my thoughts regarding that, as of http://mg.pov.lt/maemo-ssu-irclog/latest.log.html#t2012-04-10T09:20:06 ff, please
09:27.45DocScrutinizeroops
09:27.55DocScrutinizerECHAN
09:38.42*** join/#maemo-ssu StyXman (~mdione@grulic/root/StyXman)
09:40.33*** join/#maemo-ssu arcean (~Arcean@aadd57.neoplus.adsl.tpnet.pl)
09:52.49*** join/#maemo-ssu M4rtinK (~M4rtinK@mail.melf.eu)
09:58.02*** join/#maemo-ssu ivgalvez (598c718a@gateway/web/freenode/ip.89.140.113.138)
09:58.21*** join/#maemo-ssu dafox (~dafox@dyn-194208.nbw.tue.nl)
10:25.05*** join/#maemo-ssu schen (~schen@203.91.121.133)
10:29.08*** join/#maemo-ssu lizardo (lizardo@nat/indt/x-idjrpoxofwohnuag)
10:43.47*** join/#maemo-ssu juzn900 (~tessa@203-219-240-117.static.tpgi.com.au)
10:47.20*** join/#maemo-ssu schen (~schen@tu094238.ip.tsinghua.edu.cn)
10:49.21*** join/#maemo-ssu wmarone_ (~wmarone@c-67-174-151-253.hsd1.ca.comcast.net)
10:51.12ivgalvezfreemangordon: ping
11:19.41freemangordonivgalvez, pong
11:29.31*** part/#maemo-ssu juzn900 (~tessa@203-219-240-117.static.tpgi.com.au)
11:30.41*** join/#maemo-ssu arcean_ (~Arcean@aaer151.neoplus.adsl.tpnet.pl)
12:03.51ivgalvezI have commented some questions about promotion of KPv50 in http://talk.maemo.org/showpost.php?p=1190361&postcount=183
12:04.24ivgalvezI'm afraid some people may complain about promoting it having issues with commercial applications
12:09.00freemangordonivgalvez, I saw that, but what are the issues , I am not sure that abc or bless n900 have problems because of KP
12:09.13freemangordonand joikuspot already should be ok
12:13.46*** join/#maemo-ssu merlin1991 (~merlin@Maemo/community/cssu/merlin1991)
12:30.24ivgalvezI didn't know Joikuspot was OK with KP50
12:30.46ivgalvezbut it wasn't at least until v48 right?
12:32.53ivgalvezand with BlessN900 / ABC it seems that reinstalling fcam drivers from devel is needed.
12:33.10ivgalvezas it's not a User's package, most people doesn't have the update
12:34.09merlin1991ivgalvez: about blessn900
12:34.16freemangordonivgalvez, see my post on TMO
12:34.16merlin1991or rather fcam drivers
12:34.30merlin1991that's actually f00bar on the side of the fcam drivers package
12:34.37freemangordon:nod:
12:35.17ivgalvezok I've read your response
12:35.28ivgalvezthanks that's clarifying
12:37.19freemangordonwell, there will be issues with KP50 going to extras because of the changed OC frequencies, but I will ask Pali (once again) to make some changes to kernel-power-settings, so old frequencies to be automatically replaced with new
12:37.30ivgalvezare you going to attend the mer-meeting about OBS?
12:38.00freemangordonivgalvez, what am I supposed to do there? My question is serius
12:38.12freemangordons/serius/serious/
12:38.36ivgalvezyou are more capable than most of the tipycal chit chatters
12:39.05ivgalvezs/tipycal/typical/
12:39.30freemangordonwell, i *might* be more capable as a coder, but still...
12:39.49ivgalvezand having a Community OBS for Maemo is something that in the short term could help in development
12:40.25ivgalvezI'm thinking about the possibilities of upgrading the toolchain
12:40.47ivgalvezAapo was trying to upgrade gcc to 4.6 with no luck in the autobuilder
12:41.01freemangordonagree, but AIUI SD69 will attend the meeting, and I expect more people from Maemo/Harmattan to join
12:42.04ivgalvezat least things are beginning to move again
12:42.17freemangordonivgalvez, lets look it from that angle - noone can expect a couple of people to do all the work, if there is no enough active community members, then let it be that way
12:43.03freemangordonyeah, lets see in what direction
12:43.06freemangordon:D
12:44.36freemangordonand re new toolchain - CSSU does not rely/use on autobuilder and if a new toolchain is needed that could be easily achieved
12:47.00ivgalvezgood to know
12:51.08freemangordonin fact I have working 4.6.2 in one of mine SB targets :)
12:52.48ivgalvezone more question, I have seen recent commits for tracker package
12:53.40ivgalvezare you going to upgrade the deprecated version we are using? I've seen a lot of supposed improvements in performance and battery consumption
12:53.50ivgalvezin latest tracker versions
12:56.47freemangordonivgalvez, better ask Pali, I am not aware what is the case with tracker :)
12:58.15ivgalvezok, thanks
13:01.00*** part/#maemo-ssu ivgalvez (598c718a@gateway/web/freenode/ip.89.140.113.138)
13:03.02gulywhich twitter client do people here use?
13:03.41freemangordonmIRC
13:04.05freemangordonoops
13:04.05freemangordontwitter?
13:04.23freemangordonsorry, don't use any :)
13:04.44gulymirc with pizza script? ghgh
13:16.49merlin1991guly: I use tweego
13:17.18merlin1991btw anybody got the obs meeting time and date at hand?
13:20.00DocScrutinizerbtw any comments on my comments?
13:23.29merlin1991yeah
13:23.42merlin1991it makes no difference if it's our ke-recv or the pr1.3 ke-rcv
13:23.55merlin1991blkid outputs nonsense regardless
13:47.08Lava_Croftfor the fans: http://forum.xda-developers.com/showthread.php?t=1547408
13:50.31DocScrutinizermerlin1991: so the problems are genuine maemo problems
13:50.58DocScrutinizerquite expected
13:51.40DocScrutinizersince renaming and changing partitions doesn't even work under a lot of "desktop" linux'
13:52.57DocScrutinizernevertheless, as mentioned this morning, your "sticky" problem is a class on its own, and needs some more investigaton
13:54.43DocScrutinizerfirst of all I'd like to see it reproduced/confirmed, and the simple swap-SD-to-other-rootfs/device test done, to rule out it's just your partitioning tool that is messing up part-tbk
13:54.48DocScrutinizertbl*
13:55.55Lava_Crofthttp://news.bbc.co.uk/2/hi/programmes/click_online/9711150.stm
13:55.56Lava_Crofter
13:59.30merlin1991DocScrutinizer: you can reproduce it without even using an sd card
13:59.40merlin1991if you create a swap device with ramzswapd
13:59.42merlin1991remove it
13:59.43merlin1991reboot
13:59.50merlin1991blkid still thinks you have it
14:00.18DocScrutinizerI'm not particularly interested in uSD-free reproduction of the bug, since uSD is the most convenient and easy case to triage
14:00.58merlin1991well anyway it got reproduced with and without uSD on 3 devices
14:01.09DocScrutinizerand I wouldn't bet a fly shit on what ramzswap does to system
14:01.36DocScrutinizerafter all that's SWAP
14:02.10DocScrutinizermight easily get an own early init job to create that partition during boot, or whatever
14:02.39merlin1991well to make you happy I've swapped the sd card to my pr1.3 n900
14:02.50merlin1991and blkid only reports the single partition that should be there
14:02.59Lava_Croftwas it DocScrutinizer asking for new N900's to buy, not too long ago?
14:03.04merlin1991Lava_Croft: yes
14:03.10Lava_CroftAccording to my wife, MediaMarkt here still sells them
14:03.13Lava_Croftfor 379euros orso
14:03.22DocScrutinizerand when you insert another SD to the afected device now, will it still show ghosts?
14:03.25Lava_Croftat least the store nearby here, in Alkmaar apparently has a few left
14:03.33DocScrutinizerLava_Croft: yep
14:03.46merlin1991DocScrutinizer: it even shows the ghosts if I don't insert it and reboot the affected device
14:03.48DocScrutinizerLava_Croft: o.O
14:03.55Lava_Croftexactly my reaction
14:04.10DocScrutinizermany thanks
14:04.27Lava_Crofti have not seen it myself
14:04.35DocScrutinizeralas ATM I'm broke, since my employer thinks I'm cheaper than a bank
14:04.39Lava_Croftand while my wife certainly knows what my n900 looks like, i cannot be sure 100% until i saw it myself
14:04.46Lava_Croftand she can read too
14:04.52Lava_Croftfine wife of mine
14:04.55merlin1991:D
14:05.13DocScrutinizerthank her from me :-D
14:05.19Lava_Croftmediamarkt website here in NL does not show any n900's
14:05.22Lava_Crofti will
14:05.37merlin1991DocScrutinizer: I jsut removed the sd card from the pr1.3 n900 and rebooted
14:05.44merlin1991blkid still reports the sdcard partition
14:05.49DocScrutinizerI wonder if MM here in germany can order goods from MM NL
14:06.03Lava_Croftno idea
14:06.14Lava_Crofti dont go to mediamarkt
14:06.18DocScrutinizermerlin1991: AHAAAA!
14:06.33Lava_Croftmerlin1991: magic
14:06.49DocScrutinizernot magic, probably friggin static /dev/*
14:06.56merlin1991no
14:07.02DocScrutinizerNO??
14:07.06merlin1991<PROTECTED>
14:07.12Lava_Croftheh
14:07.12merlin1991ONLY blkid still shows it
14:07.23DocScrutinizerW?T!F?!
14:07.31merlin1991see my pastebin from earlier today http://pastebin.com/qR5iMx01
14:09.34DocScrutinizermerlin1991: that looks like... thoroughly fsckedup :-/
14:12.00DocScrutinizermerlin1991: please rm  /etc/blkid.tab
14:12.16DocScrutinizeror rather
14:12.19DocScrutinizerls  /etc/blkid.tab
14:12.23DocScrutinizerls -l
14:12.36merlin1991oh that file contains all the evil entries
14:12.56merlin1991removing it yields in a perfect list
14:13.07DocScrutinizerand
14:13.16DocScrutinizer^W
14:13.29DocScrutinizer:-D
14:14.25DocScrutinizerbug squashed? ;-D
14:14.45merlin1991nah
14:15.12merlin1991I have to investigate if it is the desired behavious of blkid to store the info in such a way
14:15.14merlin1991but I smell bug
14:15.26merlin1991because there also is a /etc/blkid.tab.old file
14:15.28DocScrutinizerwhat's file perms?
14:15.43DocScrutinizerDUH?
14:15.46merlin1991which automatically gets created when you run blkid and already have a .tab file
14:15.57DocScrutinizershiiiiiit!
14:16.28merlin1991so my bet is that blkid should write the proper new info but doesn't
14:16.48DocScrutinizer<PROTECTED>
14:16.50DocScrutinizer<PROTECTED>
14:16.51DocScrutinizer<PROTECTED>
14:16.53DocScrutinizer<PROTECTED>
14:17.08*** join/#maemo-ssu Pali (~pali@unaffiliated/pali)
14:18.59merlin1991hm running blkid -g
14:19.05merlin1991followed by blkid
14:19.11merlin1991gives actually proper results
14:19.38merlin1991now is that weird cache behaviour intentional or not is the question
14:20.26DocScrutinizerI smell a bug introduced by a "fix" supposedly introduced during maemo adaption of blkid. This adaption probably be done due to >> If  none is given, all devices which appear in /proc/partitions are shown, if they are recognized.<< while we all know (and see in your pastebin) that /proc/partitions on maemo is "wrong"
14:21.48DocScrutinizerooh, double invokation of blkid resores the correct result? kinda anticipated behaviour, when yu mentioned .old
14:22.04merlin1991nah first invoking blkid with "-g"
14:22.22merlin1991which is epxlained as "garbage collect the cache file"
14:22.27DocScrutinizerBWAHAHA I missed that
14:22.53DocScrutinizer-g     Perform a garbage collection pass on the blkid cache to remove devices which no longer exist.
14:22.54merlin1991idly wonders WHO WANT A FRIGGIN REPORT FOR DEVICES THAT DON'T EXIST ANYMORE
14:23.32DocScrutinizerthat's ot intentional, that's to fix the known issue we ran into
14:23.37DocScrutinizernot*
14:24.09DocScrutinizersince probing all devices takes eternities, blkid uses a cache
14:24.39merlin1991hm I notice no difference between invoking blkid without a cache or with the cache
14:24.50DocScrutinizerusing this cache per definitionem forbids automatic updates of the cache when devices changed
14:25.00merlin1991in otherwords invoking it after removing the cache file, or when it still has one
14:25.12merlin1991DocScrutinizer: wrong
14:25.19merlin1991it actually overwrites in the cache
14:25.24merlin1991it only doesn't delete
14:25.28DocScrutinizermerlin1991: blkid is a general tool, no specialized one for maemo
14:25.55merlin1991I've repartitioned my sd from 2 times ext + 1 vfat (in that order) to 1vfat
14:26.07merlin1991and then blkid reported 1 vfat 1 ext 1 vfat
14:26.34DocScrutinizerhmm, it has intelligent cache ;-P
14:26.49merlin1991it has a foobar cache :D
14:29.02DocScrutinizerwhatever, you correctly stated it doesn't matter for maemo at all, how fast this shitty thing performs. So we want to wap it up with a wrapper script that changes "blkid $@" to "blkid -c /dev/null $@"
14:29.21DocScrutinizerwrap*
14:29.52DocScrutinizerwhich is an exemplary good CSSU fix of a maemo bug
14:32.55DocScrutinizermv /sbin/blkid /sbin/blkid.real; echo -e '#!/bin/sh\n/sbin/blkid.real -c /dev/null "$@"\n" >/sbin/blkid;chmod 755 /sbin/blkid
14:34.09DocScrutinizer>>
14:34.11DocScrutinizer-c cachefile
14:34.12DocScrutinizer<PROTECTED>
14:34.14DocScrutinizer<PROTECTED>
14:34.15DocScrutinizer<PROTECTED>
14:36.28DocScrutinizerof course it needs thorough testing nevertheless, maybe some idiotic script relies on the caching
14:37.06DocScrutinizeractually we should review rather than test
14:37.24DocScrutinizerall locations where blkid gets invoked
14:38.20DocScrutinizerand no, I'd not suggest to fix the intiscripts that invoke blkid, the wrapper solution is way more robust
14:43.58Palifreemangordon, if you finding upstream git repo of osso-gnome-vfs2, it is here: http://maemo.gitorious.org/maemo-af/osso-gnome-vfs2/commits/fremantle
14:48.27DocScrutinizeractually make that  echo -e '#!/bin/sh\n/sbin/blkid.real -c /dev/null\nif [ 4 -eq $? -o x$1 == x-h ]; then echo "via wrapper script $0 to pass -c /dev/null"; fi; "$@"\n" >/sbin/blkid
14:50.07DocScrutinizerugh
14:52.14DocScrutinizeractually make that  echo -e '#!/bin/sh\n/sbin/blkid.real -c /dev/null "$@"\nret=$?\nif [ 4 -eq $ret -o x$1 == x-h ]; then echo "via wrapper script $0 to pass -c /dev/null"; return $ret\nfi; \n" >/sbin/blkid
14:55.23merlin1991I think first we have to investigate what in maemo actually uses blkid
14:55.24merlin1991:D
14:55.41DocScrutinizereasy, grep is your friend
14:55.50merlin1991sure :)
14:55.55merlin1991grep -r is running soon
14:56.22DocScrutinizerI gues you can limit it to /etc /var
14:57.18DocScrutinizerthough... ohwell t900 has nothing to do anyway ;-D
15:04.21freemangordonPali, wrong, it is here git@gitorious.org:community-ssu/osso-gnome-vfs2.git :P
15:05.04Palifreemangordon, what is wrong?
15:18.17DocScrutinizermerlin1991: meh, seems blkid is used nowhere
15:18.48DocScrutinizerlibblkid is used 'a lot'
15:40.07freemangordonPali, I was joking, we already have those sources in CSSU (cloned from the address you pointed) plus a fix for wrong partition labels
15:40.39Palifreemangordon, then OK
15:41.00freemangordonbtw you can use cssu-devel repo to test the fix
15:41.54freemangordonmerlin1991, did you send HOWTO use -devel repo to others?
15:42.03amiconnWhat does maemo use blkid for, btw_
15:42.22amiconns/_/?/
15:42.29amiconnDamn keymap
15:44.05merlin1991freemangordon: I've sent it to Pali, still have to explain it to arcean
15:44.17freemangordonok
15:44.36merlin1991btw I think I've made a config mistake
15:45.00freemangordonwhy?
15:46.05merlin1991"distribution" is community-devel instead of fremantle
15:47.15freemangordonhmm, why is that?
15:47.28merlin1991because I configured it that way (by mistake)
15:47.33merlin1991technially it's no problem
15:47.41merlin1991it only looks "wrong" in the cataloges list
15:47.47freemangordonno, i meant why it should not be fremantle?
15:47.59merlin1991it should be fremantle
15:48.06freemangordonaaah, ok
15:48.10freemangordonmy old eyes
15:48.38freemangordonwell, I don't think anyone has this repo set up, so you still can change it
15:49.29freemangordonand maybe make an announcement thread on TMO after that
15:50.08freemangordonis it hard to change distribution to correct one?
15:50.17merlin1991nah should be easy
15:50.25merlin1991jsut need to find the right options
15:50.31freemangordondo it then :)
15:50.33merlin1991the config files are not exaclty straight forward :D
16:08.04DocScrutinizermerlin1991: I'm inclined to close your virtual ticket as INVALID
16:08.49DocScrutinizermerlin1991: seems nothing in maemo fremantle is using blkid. So if it doesn't behave as *you* expect, that's no valid ticket
16:09.46DocScrutinizermerlin1991: I thought you're describing an actual error showing up in maemo $whatever app
16:11.11DocScrutinizerlike e.g. your ghost partitions would show up in HFM
16:11.25freemangordonmerlin1991, BTW did you try osso-gnome-vfs2 from cssu-devel according to yesterday's plan?
16:12.11DocScrutinizerwhich, btw, made me enter panic mode
16:12.15DocScrutinizer;-P
16:12.31merlin1991yeah it seems to be fsckd by design
16:13.09freemangordonmerlin1991, this is a FEATURE, not a BUG :D
16:13.33freemangordonyou being a developer should know that
16:13.38freemangordon:P
16:14.30DocScrutinizeralso you should know how to set a proper SEVERITY tag to your error reports ;-)
16:17.14merlin1991I never said it is baaaaaaaaaaaaad :D
16:19.31freemangordonHmm, was it Raimu to report that renaming a partition usign filemanager screws volume labels?
16:20.04freemangordonRaimu, ping
16:25.37DocScrutinizermerlin1991: you actually said nothing regarding that
16:26.48DocScrutinizerI read that in context of our current ke-recv mess, and filled in the missing SEVERITY tag - obviously incorrect, due to missing input. Your name was the guidance
16:27.21merlin1991tbh I hade no idea about severity, I came across it when debugging ke-recv stuff
16:27.33DocScrutinizer:nod:
16:28.04DocScrutinizercommunication failed. Always a problem of both ends ;-)
16:28.57DocScrutinizeranyway a great opportunity to learn some stuff about the topic at large
16:29.33freemangordonmerlin1991, what exactly ke-recv stuff are you debugging?
16:29.38freemangordonthe rename bug?
16:29.57merlin1991nope had someone where ke-recv wouldn't lead to moutns at all
16:30.03merlin1991even with proper init.d script
16:30.20freemangordonaah, ok
16:30.43freemangordonPali, ping
16:42.18merlin1991freemangordon: please reupload your package
16:42.32merlin1991I've changed the distribution and everything but lost your package on the way
16:42.35freemangordonok, give me a minute
16:44.29freemangordonready
16:44.52freemangordonBTW I think all of us should have that repo enabled
16:45.00merlin1991dang
16:45.06merlin1991it went back into community-devel
16:45.11merlin1991seems there still is some gotcha
16:47.46freemangordonmerlin1991, seems it went in BOTH repos
16:48.34merlin1991ls
16:48.37merlin1991oops :D
16:48.45freemangordon.
16:48.47freemangordon..
16:48.57freemangordon0 bytes in 0 files
16:49.00freemangordon:D
16:49.21merlin1991hm it is in the fremantle dist
16:49.41freemangordonnp then
16:50.23merlin1991is it only 1 package or a few?
16:50.48freemangordon5 .debs
16:52.32merlin1991okay please upload once more :$
16:52.39freemangordonok
16:52.55merlin1991if it doesn't go to community-devel this time it's fine :)
16:55.43merlin1991okay seems the setup is proper now
16:56.00merlin1991btw I've created a .install file aswell http://maemo.merlin1991.at/cssu/community-devel/community-devel-fremantle.install
16:56.01freemangordonyep
16:56.33freemangordonyeah,i were just browsing from my n900 to use ot :D
16:57.59merlin1991watches ham
16:58.09freemangordonme too :)
16:58.37merlin1991it's currently at preparing installation, I guess that is when it adds the repos and refreshes
16:58.57freemangordonyeah, the same
16:59.21DocScrutinizersomebody over at #maemo mentioned there's allegedly some kind of dependencies conflict with new KP50 and KP50-multiboot|uboot (can't remember)
16:59.52merlin1991oh yes, apt-worker going insane
17:00.14merlin1991ham rally needs a busy indicator in the main window for when apt-worker is running in circles
17:00.24DocScrutinizerYEP!
17:00.49DocScrutinizeradd a statusbar icon to apt-worker
17:01.00merlin1991I always open a xterm and run top to see when I finally can use the ui again
17:01.03DocScrutinizerwill help as well on closing HAM
17:01.30DocScrutinizerwell, I got loadapplet for that ;-D
17:01.55freemangordonloadapplet?  and how is the battery life with it?
17:02.19DocScrutinizeran applet that should've been in maemo default metapr
17:02.20freemangordonisn't that python?
17:02.33DocScrutinizernah, don't think so
17:02.45freemangordonhmm,ok, if you say so
17:03.03merlin1991damn I want the connect now widget to work for bluetooth too :D
17:03.06DocScrutinizerbut actually you're right it's probably eating a few cpu cycles and causing wakeups
17:03.11merlin1991the only applet out there for that IS python
17:03.11*** join/#maemo-ssu BCMM (~user@unaffiliated/bcmm)
17:03.13merlin1991aka evil
17:04.06DocScrutinizerI don't mind if it's python, the problem is refresh cycle and suspend or not, and when
17:04.12merlin1991okay freemangordonwhich package do I have to upade? all of them or only libosso-gnomevfs2-0?
17:04.18freemangordonfew CPU cycles? possible. And...err... what about memory?
17:04.36DocScrutinizerI got "plenty of memory" here
17:04.49freemangordonn950? :D
17:04.50DocScrutinizerway more than average joe
17:06.02DocScrutinizeror maybe not... I'll investigate. Thanks for pointing me at it
17:06.03merlin1991DocScrutinizer: gimme a free -m on your device when it's idle
17:06.12merlin1991I wonder how much it differs from a mostly unmodified device
17:06.19DocScrutinizerIroN900:~# free
17:06.21DocScrutinizer<PROTECTED>
17:06.22DocScrutinizer<PROTECTED>
17:06.24DocScrutinizer<PROTECTED>
17:06.25DocScrutinizerTotal:      1031964       372420       659544
17:07.19DocScrutinizernot what I expected
17:07.34DocScrutinizerthus "or maybe not..."
17:08.04freemangordonNokia-N900:~# free
17:08.04freemangordon<PROTECTED>
17:08.04freemangordon<PROTECTED>
17:08.04freemangordon<PROTECTED>
17:08.04freemangordonTotal:      1342948       415772       927176
17:08.08merlin1991<PROTECTED>
17:08.08merlin1991Mem:        235260       219768        15492            0         3768
17:08.08merlin1991-/+ buffers:             216000        19260
17:08.08merlin1991Swap:       786424        76216       710208
17:08.59freemangordonbut i have PhoneME with Opera loaded and microb and 4 accounts (skype,facebook,gtalk and irc) connected
17:09.06merlin1991my pr1.3 device has a better ratio though
17:09.34BCMMDocScrutinizer: my gf's phone has the same ke-rcev bug. i followed the steps that fixed mine, and it says mp-fremantle-community pr is alread the newest version
17:09.49BCMMdo i continue with dsmetool anyway?
17:09.54merlin1991BCMM: then she updated already
17:09.58merlin1991this way you need
17:10.05merlin1991dpkg --purge --force-all
17:10.10merlin1991apt-get install ke-recv
17:10.13merlin1991dsmetool -b
17:10.28freemangordondpkg --purge --force-all ke-recv
17:10.31merlin1991yeah
17:10.35merlin1991what freemangordon said :D
17:10.41merlin1991silly me
17:11.12BCMMthanks, doing that
17:11.31freemangordonDocScrutinizer, you are on omap kernel?
17:12.03DocScrutinizerfreemangordon: stock kernel
17:12.24BCMMah, now i forgot to clear the mount point...
17:12.33merlin1991did it reboot already?
17:12.39BCMMoh silly me i can just expose it again with mass storage mode
17:12.47merlin1991well even if it did, you can just unmount clean remount
17:12.47BCMMnah, playing boot video now
17:12.54freemangordonyea, that is why your memory is 245540 vs 235260 on mine and merlin's
17:13.29merlin1991hm I just realized I have pk on my -stable, but omap on my -testing n900 xD
17:14.14BCMMthanks, mydocs mounts now
17:14.22DocScrutinizerhow would I spot the process of loadapplet? or is it just a "subroutine" of hildon-foo?
17:14.27BCMMfwiw, this phone had the same issue with rotation
17:14.31freemangordonshould make no difference(beside those additional 10MB for DSP and framebuffer)
17:14.38freemangordonDocScrutinizer, it is hildon-home
17:14.45DocScrutinizer:nod:
17:14.53DocScrutinizerthought as much
17:14.57freemangordonwait, hildon-status-manu
17:15.08DocScrutinizerwhaever
17:15.33merlin1991BCMM: I guess the issue is gone now?
17:15.42DocScrutinizerooh wait, we could compare length :-P err values of hildon-status-menu
17:16.00freemangordonmerlin1991, new gnome-vfs-whaecer installed?
17:16.03merlin1991yea
17:16.17freemangordonhow the things look like now?
17:16.22merlin1991now trying to find that usim
17:16.34freemangordonusim?
17:16.39merlin1991err usd
17:16.39freemangordonwhat for?
17:16.40merlin1991whatever :D
17:16.46freemangordonaah :D
17:16.54DocScrutinizergrrr
17:17.57DocScrutinizer<PROTECTED>
17:18.26DocScrutinizer<PROTECTED>
17:19.28DocScrutinizer0.0 CPU% 0.2 MEM% I'm not at all concerned
17:23.27*** join/#maemo-ssu javispedro (~javier@Maemo/community/contributor/javispedro)
17:31.48BCMMmerlin1991: yeah works now
17:33.19*** join/#maemo-ssu CepiPerez (~Matias_Pe@186.22.13.195)
17:35.40Raimufreemangordon, pong
17:36.44freemangordonraimu, was that you who had problems with volume labels incorrectly shown in filemanager after volume rename?
17:37.54freemangordonRaimu ^^^
17:39.32merlin1991hm I missed the #mer-meeting
17:39.53DocScrutinizerMEHs
17:40.16DocScrutinizermer vanished from my radar completely
17:40.51DocScrutinizerI just can't see it leading anywhere
17:40.54Raimufreemangordon: Yes.
17:41.25merlin1991DocScrutinizer: I read the minutes, and it looks like nokia is looking into funding parts of their obs structure
17:41.41freemangordonRaimu, ok, there is supposed to be a fix for that, dare to enable community-devel repo to test it?
17:41.50DocScrutinizerthat's ewlwvant how?
17:41.52Raimufreemangordon: Hokay.
17:41.54DocScrutinizerdang
17:41.56merlin1991and it also seems that nokia/maemo.org people seem to be interested into replacing autobuilder with obs aswell
17:41.57DocScrutinizerrelevant*
17:42.07merlin1991s/into/in/
17:42.22freemangordonRaimu, here http://maemo.merlin1991.at/cssu/community-devel/
17:42.42freemangordonthere is .install file to be opened directly from your n900
17:42.49Raimufreemangordon: Ahah, I got it from here - now what's the file I'm to update?
17:43.36freemangordonosso-gnome-vfs, but you need 2 .debs, better use HAM to upgrade
17:43.38merlin1991why did  I decide to get a dns entry with my nick
17:43.45merlin1991plenty of useless highlights on irc xD
17:43.57freemangordonyou want to be famous :D
17:44.03DocScrutinizerhaha
17:44.37freemangordonmerlin1991, you know, beware what you wish for
17:44.45freemangordon:D:D:D
17:44.53merlin1991:D
17:45.22merlin1991apart from the youtube results, everyhting for merlin1991 (I get) is actually me :)
17:45.50freemangordonis afk
17:46.40merlin1991wtf is that "is afk" you keep writing lateley :D
17:46.46merlin1991*lately*
17:50.05DocScrutinizer~afk
17:50.06infobotfrom memory, afk is Away From Keyboard
17:53.22*** join/#maemo-ssu trbs (~trbs@2001:470:d2ad:1:4a5b:39ff:fe7d:1623)
17:53.57*** join/#maemo-ssu CepiPerez (~Matias_Pe@186.22.13.195)
17:56.54*** join/#maemo-ssu Pali (~pali@unaffiliated/pali)
18:00.43Raimufreemangordon: Are you quite sure it can be found via HAM?
18:04.41merlin1991DocScrutinizer: but he should /me that and not privmsg it
18:05.14DocScrutinizer??
18:05.23merlin1991hm which sys / dev node had the fm_tansmitter power level?
18:05.38DocScrutinizermhm, yeah
18:05.44merlin1991DocScrutinizer: I meant in that case one writes
18:05.47merlin1991is afk
18:07.26freemangordonRaimu, just add the repo and update
18:08.18DocScrutinizererrr, really??
18:08.32merlin1991Raimu: apt-get install libosso-gnomevfs2-0
18:08.45DocScrutinizerthat's more like it
18:08.46freemangordonis not afk
18:08.54freemangordonmerlin, happy naow?
18:09.46merlin1991:D
18:09.47*** join/#maemo-ssu mirandir (~valentin@lec67-4-82-230-53-23.fbx.proxad.net)
18:11.55DocScrutinizerinsane, instagram: 30E6 app users, selling for 1E9 USD
18:12.23DocScrutinizerthat's 33USD/customer
18:12.38DocScrutinizersuckerberg
18:12.47RaimuUpgrading.
18:13.28*** part/#maemo-ssu mirandir (~valentin@lec67-4-82-230-53-23.fbx.proxad.net)
18:13.36DocScrutinizerwishes somebody would pay 33USD per h-e-n user
18:14.04merlin1991hrhr
18:14.13*** join/#maemo-ssu mirandir (~valentin@lec67-4-82-230-53-23.fbx.proxad.net)
18:17.02DocScrutinizerBWAHAHA another friggin portrait bug
18:19.08DocScrutinizeropening call history: LS. clicking an entry->PRT. closing this requester by clicking background-> call history in PRT. taskswitcher, select call history: LS
18:19.52DocScrutinizercongrats portrait mode, that's really fsckdup
18:28.43Raimufreemangordon: Okay, done. What to test now?
18:30.41DocScrutinizerhehe, the requester that appears after clicking an entry in call history also rotates back to LS, when you lock and unlock
18:30.46DocScrutinizerX-P
18:31.04DocScrutinizerdid I mention I *adore* portrait mode?
18:33.01Raimufreemangordon: Well, after the update renaming partitions randomly doesn't suddenly give all other partitions names too.
18:34.33Raimufreemangordon: Looks like fileman doesn't display the new names though they're renamed properly.
18:34.44RaimuI can live with that
18:36.18*** join/#maemo-ssu freemangordon_ (~freemango@213.226.63.182)
18:39.27DocScrutinizerwell, I bet there's no method in filemanager to rescan names of directories and partition names, in case they get renamed. It should, however, be aware of such renames when they are done inside filemanager itself
18:40.43*** join/#maemo-ssu M4rtinK (~M4rtinK@ip-89-102-207-166.net.upcbroadband.cz)
18:40.58freemangordon_actually there is, the problem is that even hal is not aware of the rename
18:55.11*** join/#maemo-ssu nox- (noident@freebsd/developer/nox)
18:55.31*** join/#maemo-ssu dafox (~dafox@ip51cc571d.speed.planet.nl)
18:56.27DocScrutinizerhow could it, it's not designed to monitor for changes ;-D
18:56.43DocScrutinizerat least not for changes of partition names
18:58.35DocScrutinizerrather some ahl-addon-foobar I guess
18:58.42DocScrutinizerhal*
19:16.55*** join/#maemo-ssu freemangordon_ (~freemango@92-247-227-116.spectrumnet.bg)
19:29.28*** join/#maemo-ssu gri (~gri@muhkuh.net)
19:49.24*** join/#maemo-ssu Kaptenen (~Kaptenen@81.216.60.47)
19:58.13*** join/#maemo-ssu Guest50125 (~rd@p57B498FA.dip0.t-ipconnect.de)
19:59.00*** join/#maemo-ssu M4rtinK (~M4rtinK@ip-89-102-207-166.net.upcbroadband.cz)
20:06.27*** join/#maemo-ssu Guest50125 (~rd@p57B498FA.dip0.t-ipconnect.de)
20:16.30*** join/#maemo-ssu javispedro (~javier@Maemo/community/contributor/javispedro)
20:17.24Palifreemangordon, what is state of RE cellular control panel plugin?
20:17.40freemangordon_bad
20:18.14freemangordon_it will take lots of time
20:18.59Paliok
20:44.35*** join/#maemo-ssu M4rtinK (~M4rtinK@ip-89-102-207-166.net.upcbroadband.cz)
21:44.33*** join/#maemo-ssu int_ua (~int_ua@93.126.96.47)
22:57.31*** join/#maemo-ssu freemangordon_ (~freemango@130-204-50-168.2074156771.ddns.cablebg.net)
22:59.09*** part/#maemo-ssu freemangordon_ (~freemango@130-204-50-168.2074156771.ddns.cablebg.net)
23:39.21DocScrutinizerpali sucks, my tab nick-completion never works for him
23:39.48DocScrutinizerwell, could be worse, he could have a nick like freemangordon
23:39.50DocScrutinizer;-P
23:40.07freemangordonhaha, very funny :p
23:40.13DocScrutinizerhihihi

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