IRC log for #maemo-ssu on 20121111

00:24.11*** join/#maemo-ssu Skry (~skry@81-175-148-89.bb.dnainternet.fi)
01:53.39*** join/#maemo-ssu Jade (~jade@unaffiliated/jade)
02:14.00*** join/#maemo-ssu toxaris (~toxaris@s83-180-246-172.cust.tele2.se)
03:34.53*** join/#maemo-ssu amiconn_ (amiconn@rockbox/developer/amiconn)
04:00.35*** join/#maemo-ssu DocScrutinizer05 (~HaleBopp@openmoko/engineers/joerg)
04:37.20*** join/#maemo-ssu Jade (~jade@unaffiliated/jade)
04:58.10*** join/#maemo-ssu Jade (~jade@unaffiliated/jade)
05:04.21*** join/#maemo-ssu dhbiker (~dhbiker@193.2.218.150)
05:55.30*** join/#maemo-ssu Jade (~jade@unaffiliated/jade)
06:00.04*** join/#maemo-ssu Mihanizat0r (~Miha@5.199.210.185)
06:33.53*** join/#maemo-ssu dhbiker (~dhbiker@193.2.218.150)
06:52.00*** join/#maemo-ssu dhbiker (~dhbiker@193.2.218.150)
07:30.12*** join/#maemo-ssu jonwil (~jonwil@27-33-137-199.static.tpgi.com.au)
09:07.58*** join/#maemo-ssu dhbiker (~dhbiker@193.2.218.150)
09:35.17*** join/#maemo-ssu NIN101 (~NIN@p5DD29231.dip0.t-ipconnect.de)
09:50.05*** join/#maemo-ssu _rd (~rd@p57B488F6.dip0.t-ipconnect.de)
10:18.23*** join/#maemo-ssu luf (~luf@ip-89-103-223-164.net.upcbroadband.cz)
10:33.55*** join/#maemo-ssu Woody14619a (~Woody@2620:4:4000:1:c95a:a95d:2340:5acd)
10:33.55*** join/#maemo-ssu Woody14619a (~Woody@Maemo/Community/council/Woody14619)
10:34.26*** join/#maemo-ssu _rd (~rd@p57B488F6.dip0.t-ipconnect.de)
10:35.48*** join/#maemo-ssu M4rtinK (~M4rtinK@mail.melf.eu)
10:41.39*** join/#maemo-ssu toxarisswe (~toxaris@s83-180-246-172.cust.tele2.se)
10:58.31*** join/#maemo-ssu _rd (~rd@p57B488F6.dip0.t-ipconnect.de)
11:14.35*** join/#maemo-ssu NIN101 (~NIN@p5DD29231.dip0.t-ipconnect.de)
11:23.38*** join/#maemo-ssu Pali (~pali@unaffiliated/pali)
11:46.24*** join/#maemo-ssu arcean (~arcean@aaem131.neoplus.adsl.tpnet.pl)
11:57.37freemangordonhmm, strange, if you snooze an alarm in ACT_DEAD mode, it does not power down but remains in ACT_DEAD
11:59.21luffreemangordon: world with zombies is more exciting :D
11:59.52freemangordonhehe
11:59.58freemangordonhow is bluez going?
12:00.40luffreemangordon: I'm using it several weeks. No I finished with backporting the network stuff.
12:00.57luf* Now I'm finishing with back....
12:02.13freemangordonwhy noone wants to test alarm UI?
12:02.38freemangordoncomeon, the worst that could happen is one to be late for work and get fired :P
12:03.08luffreemangordon: be patient ...
12:03.24lufMaybe kerio is trying it ....
12:03.27freemangordonpatient?
12:03.30freemangordonno
12:03.39freemangordonAFAIK
12:04.04freemangordonis going to find something for lunch, bbl
12:07.04*** join/#maemo-ssu toxarisswe (~toxaris@s83-180-246-172.cust.tele2.se)
12:16.07keriofreemangordon: gimme a .deb
12:16.37freemangordonkerio: just a minute
12:17.05luffreemangordon: what? what minute? now! :D
12:17.43keriohe's setting an alarm to remind himself to upload the .deb
12:18.11lufkerio: it's bad. You never get the .deb in that case :D
12:18.50freemangordonhttp://merlin1991.at/~freemangordon/alarmui/
12:19.26lufgood alarmui passed first test.
12:19.35freemangordonhehe
12:19.53*** join/#maemo-ssu kolp (~quassel@212.255.105.218)
12:20.01luffreemangordon: it's better than bluez PAN ;)
12:20.45freemangordonkerio: please check the correct .so is replaced
12:21.07freemangordon"/usr/lib/systemui/libsystemuiplugin_alarm_dialog.so"
12:21.14keriothat's the package...
12:21.20kerioyou can just open it :)
12:21.34freemangordoni did that, but I want to be sure
12:21.35keriowell, unar it and then untgz the data.tar.gz file
12:21.46freemangordon^^^
12:24.01keriofreemangordon: i've got guests for lunch right now, though
12:24.05kerioso any testing will have to wait
12:24.19freemangordonok
12:26.34*** join/#maemo-ssu arcean (~arcean@aaem131.neoplus.adsl.tpnet.pl)
12:37.01*** join/#maemo-ssu _rd (~rd@p57B488F6.dip0.t-ipconnect.de)
13:14.09*** join/#maemo-ssu arcean (~arcean@aaem131.neoplus.adsl.tpnet.pl)
13:18.13*** join/#maemo-ssu _rd (~rd@p57B488F6.dip0.t-ipconnect.de)
14:01.31lufGood it seems bluez + networking is working as I expected :)
14:01.43freemangordon:)
14:01.56kerio:D
14:04.02lufOk so not fully. I see bug in removing interface when stopping bluetoothd.
14:13.54*** join/#maemo-ssu _ade_ (~arno@52481E0B.cm-4-1a.dynamic.ziggo.nl)
14:20.41_ade_freemangordon: installed your osso-systemui-alarm. First alarm showed up fine ;-)
14:21.05freemangordon_ade_: good. BTW do you have any problems with stock?
14:21.36freemangordonlike those on 720p thread
14:23.10_ade_Will test the stock clock as well. But you had problems with multiple alarms in a short notice as I understood. Never tested that.
14:23.18freemangordonyeah
14:40.51_ade_freemangordon: question; does this bug I reported ring any bells: https://bugs.maemo.org/show_bug.cgi?id=12661 I did not get a response since I registered it months ago
14:40.52povbotBug 12661: Popup menu fails with X Error while switching portrait/landscape
14:42.04keriohey _ade_
14:42.16_ade_hello there
14:42.23keriocan you reduce the space between buttons so they look like gtk buttons?
14:42.49freemangordon_ade_: no, but why it is agains h-d and not against CSSU?
14:43.10freemangordoncan you file another one against CSSU with link to the original?
14:43.39_ade_freemangordon: okay, I will do that
14:44.33freemangordon_ade_: I suspect Qt here
14:44.45freemangordonthough I've never seen such behaviour
14:45.55_ade_Strange, on both my N900's I get it consitently. Very annoying, I have to kill these programs when this happens
14:46.40freemangordon_ade_: any other program besides worldclock that behaves like that?
14:47.48_ade_yes, every (Qt?) program that shows up a dialog and has had this rotation order
14:48.04freemangordon_ade_: gimme some name :P
14:48.51_ade_Now I think of it, not only Qt. FAP has it too.
14:48.52kerioi have a serious problem with QT on the n900
14:48.53kerioit sucks
14:49.09freemangordonkerio: you suck
14:49.32tadzikwell, it would be nicer if it didn't reorder widgets every single time when you rotate the device
14:49.42keriofreemangordon: no seriously, qt doesn't use xkb apparently
14:49.47kerioso my keyboard is rendered half useless
14:50.01freemangordontadzik: it depends on the program, not on qt
14:50.03kerioit also doesn't honour the setting to ignore the "hold key to sym" nonsense
14:50.55freemangordon_ade_: is there any "stock" application behaving like that?
14:51.46_ade_I think I can state: every application that uses popup/dialog windows
14:52.04keriofreemangordon: QT sucks
14:52.24_ade_I did not test if forced rotation could solve it.
14:52.59_ade_I my opinion Maemo is not aware there was a rotation in these cases
14:53.27freemangordon_ade_: no forced rotation here, cannot reporoduce it with pdf reader
14:53.59_ade_You tested in the order as described in the bugreport?
14:54.06freemangordonI think so
14:54.18freemangordonand clicked on "open" button
14:54.32freemangordonwell, maybe it is not popup
14:54.57arcean_ade_, the latest stable worldclock replacement and I can't reproduce
14:55.08tadzikfreemangordon: so the program is free to somehow precompute both orientation layouts and not do it every single time?
14:55.43_ade_It should be something like a QDialog window. I was always wondering why other people never reported it.
14:55.55freemangordontadzik: no, it receives a signal and changes the layout accordingly
14:56.14freemangordonif needed
14:56.29freemangordonQDesktopWidget::resize that is
14:56.33freemangordon(iirc)
14:56.59*** join/#maemo-ssu kolp_ (~quassel@212.255.105.218)
14:57.07freemangordontadzik: what is going on with opera 12?
14:57.22freemangordonany clue why it crashes as soon as started?
14:57.35tadzikyeah, but then reordering stuff on screen takes some visible amount of time; look at OMP for example. I wonder if it could be avoided somehow
14:57.48tadzikfreemangordon: well, I have no such problem with it. Weird
14:58.07freemangordontadzik: that is very strange
14:58.16*** join/#maemo-ssu _rd (~rd@p57B488F6.dip0.t-ipconnect.de)
14:58.26tadzikdid it happen to anyone else? Did you try re(naming|moving) its config file?
14:58.28freemangordonyes, it takes time, but not much to be done here
14:58.37tadzikso that is Qt's fault, aye?
14:58.46freemangordontadzik: look at TMO, lots of people got hit by that
14:58.59freemangordonwell, GTK does the same
14:59.12tadzikI don't have that impression
14:59.23freemangordonit just does it way faster :D
14:59.39tadzikyay, gtk finally better at something
14:59.48freemangordongtk2.0?
15:00.00tadzikwe have 3.0 on maemo?
15:00.03freemangordonno
15:00.11tadzikthen yes, I mean 2.0
15:00.38tadziknow that I look at it, fapman indeed does it too (visibly moving stuff around), and way faster indeed
15:00.48freemangordonsee :P
15:00.56freemangordonanyway, gtg
15:00.58freemangordonbbl
15:01.05tadzikfreemangordon: I'll poke Opera maintainer when I get back to the office, see if we can do anything about it
15:01.11freemangordonok
15:01.28freemangordontadzik: seems something has changed on the server side
15:01.44freemangordonwhich crashes opera on the device
15:02.58tadzikserver side? What kind of server side could that be, Turbo?
15:03.11tadzik(Opera Turbo, that is)
15:03.40tadzikokay, I'll read the tmo thread and then start asking questions :)
15:04.54arcean_ade_, when I click really fast, a couple of times, on the label displaying time (worldclock main window), it will open a couple of dialogs :P
15:05.14_ade_I know ;-)
15:05.22arcean_ade_, ok :)
15:05.32_ade_I could see if I can prevent it
15:06.04_ade_Have to go now also, thanks for the responses here
15:06.11arcean_ade_, all in all I have just switched to your worldclock app :)
15:06.27_ade_Good to hear that!
15:06.50*** part/#maemo-ssu _ade_ (~arno@52481E0B.cm-4-1a.dynamic.ziggo.nl)
15:34.24ShadowJKtadzik; just speculation, but right after a website is loaded, opera accesses 3 opera servers. It crashes right after. Atleast one of the files is a big file with site-specific "fixes", of which there's also a local copy in .opera/ ?
15:35.28ShadowJKAlso a fourth access to some opera turbo servers on socks port (even with turbo switched off), but i dont know the timing of that
15:35.54tadzikthat'd be UserJS I suppose
15:36.12tadzik(the fixes file)
15:36.49tadzik"Atleast one of the files is a big file" - one of what files, those fetched from Opera servers?
15:37.01ShadowJKthat'd be the browser.js
15:37.19ShadowJKthe "fixes"
15:37.24ShadowJKthe rest seemed tiny
15:37.57tadzikso again: it crashes after opera start, or after website access?
15:38.18ShadowJKAfter a website has loaded
15:38.51ShadowJKwhen the spinning thing stops spinning and progress bar goes away
15:39.31ShadowJKOn news.bbc.co.uk it takes awhile for everything to load, so you get some time to scroll around the half-loaded page before it crashes
15:40.08tadzikcurious.
15:40.39tadzikOkay, I'm guessing around and still haven't even looked at the tmo thread. Still have an exam to learn for :/
15:41.00ShadowJKwhen loading something simple, like an image, there's about a second delay before crash
15:41.48ShadowJKEven more curiously, when launched from xterminal, it doesn't exhibit this behaviour, seems to run fine
15:42.06lufkerio: I upladed the new .deb on merlin.at for bluez-499 ;) Feel free to test it.
15:42.21kerioI'LL FEEL WHATEVER I WANT
15:42.59lufkerio: :D
15:44.04kerioluf: there's also a new obexd, isn't it
15:44.14lufI'll have to make some wiki for it ...
15:44.28lufkerio: It depends what is your version.
15:44.59kerioluf: 0.46-1maemo4+0cssu1
15:45.09kerioso yes, there's 0.46-1maemo5+0cssu1 on your wobsite
15:45.25lufkerio: I fixed IrMC protocol last week or previous week. Thanks to don_falcone
15:46.00lufBut it should be included in CSSU-testing ...
15:46.03tadzikShadowJK: did anyone try stracing?
15:46.48ShadowJKnot so far
15:49.43lufkerio: since obexd-0.46-1maemo3 the IrMC contains bug which prevents from using IrMC protocol :( At least for some clients as one info wasn't on the right path.
15:50.08lufkerio: it's fixed in 0.46-1maemo5+0cssu1
15:50.11keriok
15:51.43*** join/#maemo-ssu NIN101 (~NIN@p5DD29231.dip0.t-ipconnect.de)
15:53.26kerioluf: what should we test?
15:53.30kerioremember, i don't have a carkit
15:57.34lufkerio: with bluez? I worked on PAN (network support).
15:57.46lufThere is no need for pand now :)
15:58.03keriooh, you figured how to connect to a NAP without pand? neat
15:58.11lufYes.
15:58.44lufBut from upstream it needed dbus connection all the time.
16:00.06lufpermanent dbus connection: /usr/bin/dbus-send --system --print-reply --type=method_call --dest=org.bluez /org/bluez/$(pidof bluetoothd)/hci0/dev_<BT ID> org.bluez.Network.Connect string:{panu|gn|nap}
16:00.26lufI added /usr/bin/dbus-send --system --print-reply --type=method_call --dest=org.bluez /org/bluez/$(pidof bluetoothd)/hci0/dev_<BT ID> org.bluez.Network.ConnectPermanent string:{panu|gn|nap}
16:01.08kerioluf: and how can you disconnect?
16:01.42lufI did the same for registering server parts and also path changed: org.bluez.Network{Peer|Hub|Router}.Register (as in bluez-4.60)
16:01.52lufkerio: try to guess ;)
16:02.08luf/usr/bin/dbus-send --system --print-reply --type=method_call --dest=org.bluez /org/bluez/$(pidof bluetoothd)/hci0/dev_<BT ID> org.bluez.Network.Disconnect
16:02.18kerioneat
16:02.58luforg.bluez.Network{Peer|Hub|Router}.Register and org.bluez.Network{Peer|Hub|Router}.RegisterPermanent
16:03.26lufBTW I backported also config /etc/bluetooth/network.conf so it supports now the autoregistering of server parts.
16:05.49lufkerio: http://pastebin.com/DVuCbEtE
16:06.29lufWhat Interface is present (not commented out) that server role is started automatically during bluetoothd startup.
16:07.19keriok
16:08.01keriodoes it create the bridge by itself?
16:13.32lufYes it can if none of such name exists.
16:14.53lufBut you have to have kernel support for bridge driver (detected via /sys/module/bridge /sys/module/bridgedriver)
16:21.10lufcssu git with bluez refreshed so it contains the latest code.
16:25.10kerioluf: os x connected to my NAP :D :D :D :D :D
16:25.14keriofucking sweet
16:25.36lufkerio: Welcome in real world ;)
16:25.59*** join/#maemo-ssu arcean (~arcean@aaem131.neoplus.adsl.tpnet.pl)
16:26.01lufkerio: to put you back to the earth ... It's NAP only by the name ...
16:26.14kerioi just need a point-to-point connection anyway
16:26.45kerio:)
16:26.51lufGN and NAP has the same implementation inside bluez.
16:26.51kerioluf: is there a way to not create the bridge?
16:27.05lufUse PANU server role.
16:27.31kerioooh good point
16:28.38lufAfter some playing I decided that it'll be the best to backport old behaviour so it should be backword compatible with implementation in bluez-4.60.
16:29.16lufBTW PANU is againist BT specification ... ;)
16:29.37lufPANU should be only client side but in older bluez it's also server role.
16:30.15*** join/#maemo-ssu kolp (~quassel@212.255.105.218)
16:30.25kerioluf: nope, OSX can't trigger the connection
16:33.21kerioluf: ok, how do i configure btnap?
16:33.26keriois it ifupped?
16:37.47kerioluf: ok, it's not ifupped :(
16:45.37kerioluf: how is one supposed to set the bridge up?
16:48.40*** join/#maemo-ssu _rd (~rd@p57B488F6.dip0.t-ipconnect.de)
16:49.35kerioluf: ok, got it
16:49.48kerionow i have a reliable way to ssh to my n900 while i'm pooping :D
16:52.45kerioluf: awwww, i don't :(
16:52.49kerioit doesn't reach far enough
16:52.57lufkerio: I'm sorry I took my dinner.
16:53.22kerioluf: patch bluez so the range is big enough!
16:53.23lufkerio: I can do nothing how far the bluetooth reach ;)
16:53.37keriothat's what a lazy person would say!
16:53.48lufkerio: sure. I'm lazy.
16:54.34lufkerio: BTW you can use script in config file to configure the new device (gn, nap - bridge, panu the per connection device).
16:54.40kerioyep, that's what i did
16:54.51keriobut apparently i suck at shell scripting and i tried three times while using $0 as the interface name
16:55.11kerioapparently, ifconfig didn't want to configure the "/usr/local/bin/bluez-nap-up.sh" interface
16:55.17lufkerio: $1 is the interface name ;)
16:55.27kerioyeah, i realized that eventually :)
16:55.47lufkerio: welcome in whole new world :D
16:55.55keriohm, i just realized that i can just configure the interface in /etc/network/interfaces and then tell bluez to use ifup
16:56.25lufkerio: it didn't work for me. No exact idea why.
16:56.44keriothen i'll leave it like this
16:57.25lufAnd bluez calls the script only during device up (so it doesn't cooperate with ifup well).
16:58.25keriois bluetooth PAN more energy-efficient than wifi?
16:59.31lufI didn't measure it. But I think I read somewhere that it's more energy efficient. But the throughput is also lower via BT.
17:09.00*** join/#maemo-ssu dhbiker (~dhbiker@95.87.145.172)
17:11.57kerionow i really wonder if i can plug an usb bt adapter to my router and get PAN there :D
17:13.51lufkerio: I see also that latency is quite higher with BT. You'll see if it's enough for you.
17:16.56lufI have a small problem that it seems that my NetworkManager 0.8.1 doesn't show me the BT connections (bnep0) :(
17:17.16keriognome sucks
17:17.43keriohm, i wonder why nokia didn't use connman for the n900
17:17.47lufI'm using quite old version you know RHEL 6 ...
17:18.18lufkerio: because using some closed source is sooo sexy.
17:19.12lufUncle Google doesn't help me with bluez + NetworkManager a lot :(
17:56.26*** join/#maemo-ssu _rd (~rd@p57B488F6.dip0.t-ipconnect.de)
17:57.47*** join/#maemo-ssu kolp (~quassel@212.255.105.218)
18:07.16keriohm, it appears that bluetooth PAN is fucking awful
18:07.20kerioin power consumption
18:37.00*** join/#maemo-ssu dafox (~dafox@ip3e8380c8.speed.planet.nl)
18:53.12*** join/#maemo-ssu arcean (~arcean@aaem131.neoplus.adsl.tpnet.pl)
19:17.02*** join/#maemo-ssu Sc0rpius (~naikel@190.79.197.57)
19:25.53*** join/#maemo-ssu _rd (~rd@p57B488F6.dip0.t-ipconnect.de)
19:32.37*** join/#maemo-ssu Sc0rpius (~naikel@190.79.197.57)
20:45.02*** join/#maemo-ssu infobot (~infobot@rikers.org)
20:45.02*** 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): 21.2011.38-1Tmaemo5.1; (stable): 21.2011.38-1Smaemo4.1
20:45.02*** mode/#maemo-ssu [+v infobot] by ChanServ
20:45.11freemangordonhehe
20:45.27freemangordonbe careful if you rely on your n900 to wake you up :P
20:45.52arcean_it will be fun :P
20:46.10freemangordonwell the fun is in stock one
20:46.20freemangordonlook at the commits if you are curious
20:46.28freemangordonI really wonder how is that possibe
20:46.32freemangordon*possible
20:46.47arcean_yeah, I have missed a couple of alarms
20:47.04freemangordononly a couple? lucky you
20:47.30freemangordonif it is not my GF to wake me up every day...
20:47.33arcean_lol, is it really that bad?
20:47.37freemangordonyes, it is
20:47.58freemangordontoldya, look at what I've changed
20:48.24freemangordonstock was not meant to be used with more than one alarm :D:D:D
20:48.41arcean_:D
20:48.47freemangordonglobal variables used all over the place,
20:49.07freemangordonwith alarm cookies overwriting those on every new event
20:49.10freemangordonyou can imagine
20:49.14arcean_hmm, maybe some trainee wrote that ? :D
20:49.20freemangordonmaybe
20:49.32freemangordonbut I wonder about QA
20:49.34*** join/#maemo-ssu rd_ (~rd@p57B488AA.dip0.t-ipconnect.de)
20:51.14*** join/#maemo-ssu nox- (noident@freebsd/developer/nox)
20:51.17freemangordonarcean_: there was even one missing dbus_message_unref(message);
20:51.45arcean_wtf :D
20:51.51freemangordonleading to one DBusMessage leak on every alarm event
20:51.58freemangordonyeah
20:52.59freemangordonno, wait, not one per alarm event
20:53.07freemangordonthat one here https://gitorious.org/community-ssu/osso-systemui-alarm/blobs/master/osso-systemui-alarm.c#line389
20:53.23freemangordonthat function is called 7-8 times per alarm event
20:53.27freemangordonthe fuck?
20:53.49arcean_so far new alarm-ui works fine :)
20:54.08freemangordonand we're wondering why swap needs to be defragmented in a couple of days :D
20:55.34freemangordonarcean_: hope so
20:55.55freemangordonthough maybe there are still some bugs to be found
20:57.54freemangordonI'll need to cleanup the code a bit
20:58.01freemangordon:(
21:15.21*** join/#maemo-ssu rd_ (~rd@p57B488AA.dip0.t-ipconnect.de)
21:41.01*** join/#maemo-ssu rd_ (~rd@p57B488AA.dip0.t-ipconnect.de)
21:45.03*** join/#maemo-ssu int_ua (~int_ua@ip-602f.proline.net.ua)
22:00.54*** join/#maemo-ssu MrPingu (~MrPingute@86.92.226.97)
22:30.30*** join/#maemo-ssu MrPingu (~MrPingute@86.92.226.97)
22:43.10*** join/#maemo-ssu Jade (~jade@modemcable021.180-203-24.mc.videotron.ca)
22:43.10*** join/#maemo-ssu Jade (~jade@unaffiliated/jade)
22:46.58*** join/#maemo-ssu Jade (~jade@modemcable021.180-203-24.mc.videotron.ca)
22:46.58*** join/#maemo-ssu Jade (~jade@unaffiliated/jade)
22:48.56*** join/#maemo-ssu Jade (~jade@modemcable021.180-203-24.mc.videotron.ca)
22:48.56*** join/#maemo-ssu Jade (~jade@unaffiliated/jade)

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