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.37 | freemangordon | hmm, strange, if you snooze an alarm in ACT_DEAD mode, it does not power down but remains in ACT_DEAD |
11:59.21 | luf | freemangordon: world with zombies is more exciting :D |
11:59.52 | freemangordon | hehe |
11:59.58 | freemangordon | how is bluez going? |
12:00.40 | luf | freemangordon: I'm using it several weeks. No I finished with backporting the network stuff. |
12:00.57 | luf | * Now I'm finishing with back.... |
12:02.13 | freemangordon | why noone wants to test alarm UI? |
12:02.38 | freemangordon | comeon, the worst that could happen is one to be late for work and get fired :P |
12:03.08 | luf | freemangordon: be patient ... |
12:03.24 | luf | Maybe kerio is trying it .... |
12:03.27 | freemangordon | patient? |
12:03.30 | freemangordon | no |
12:03.39 | freemangordon | AFAIK |
12:04.04 | freemangordon | is going to find something for lunch, bbl |
12:07.04 | *** join/#maemo-ssu toxarisswe (~toxaris@s83-180-246-172.cust.tele2.se) |
12:16.07 | kerio | freemangordon: gimme a .deb |
12:16.37 | freemangordon | kerio: just a minute |
12:17.05 | luf | freemangordon: what? what minute? now! :D |
12:17.43 | kerio | he's setting an alarm to remind himself to upload the .deb |
12:18.11 | luf | kerio: it's bad. You never get the .deb in that case :D |
12:18.50 | freemangordon | http://merlin1991.at/~freemangordon/alarmui/ |
12:19.26 | luf | good alarmui passed first test. |
12:19.35 | freemangordon | hehe |
12:19.53 | *** join/#maemo-ssu kolp (~quassel@212.255.105.218) |
12:20.01 | luf | freemangordon: it's better than bluez PAN ;) |
12:20.45 | freemangordon | kerio: please check the correct .so is replaced |
12:21.07 | freemangordon | "/usr/lib/systemui/libsystemuiplugin_alarm_dialog.so" |
12:21.14 | kerio | that's the package... |
12:21.20 | kerio | you can just open it :) |
12:21.34 | freemangordon | i did that, but I want to be sure |
12:21.35 | kerio | well, unar it and then untgz the data.tar.gz file |
12:21.46 | freemangordon | ^^^ |
12:24.01 | kerio | freemangordon: i've got guests for lunch right now, though |
12:24.05 | kerio | so any testing will have to wait |
12:24.19 | freemangordon | ok |
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.31 | luf | Good it seems bluez + networking is working as I expected :) |
14:01.43 | freemangordon | :) |
14:01.56 | kerio | :D |
14:04.02 | luf | Ok 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.05 | freemangordon | _ade_: good. BTW do you have any problems with stock? |
14:21.36 | freemangordon | like 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.18 | freemangordon | yeah |
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.52 | povbot | Bug 12661: Popup menu fails with X Error while switching portrait/landscape |
14:42.04 | kerio | hey _ade_ |
14:42.16 | _ade_ | hello there |
14:42.23 | kerio | can you reduce the space between buttons so they look like gtk buttons? |
14:42.49 | freemangordon | _ade_: no, but why it is agains h-d and not against CSSU? |
14:43.10 | freemangordon | can you file another one against CSSU with link to the original? |
14:43.39 | _ade_ | freemangordon: okay, I will do that |
14:44.33 | freemangordon | _ade_: I suspect Qt here |
14:44.45 | freemangordon | though 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.40 | freemangordon | _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.04 | freemangordon | _ade_: gimme some name :P |
14:48.51 | _ade_ | Now I think of it, not only Qt. FAP has it too. |
14:48.52 | kerio | i have a serious problem with QT on the n900 |
14:48.53 | kerio | it sucks |
14:49.09 | freemangordon | kerio: you suck |
14:49.32 | tadzik | well, it would be nicer if it didn't reorder widgets every single time when you rotate the device |
14:49.42 | kerio | freemangordon: no seriously, qt doesn't use xkb apparently |
14:49.47 | kerio | so my keyboard is rendered half useless |
14:50.01 | freemangordon | tadzik: it depends on the program, not on qt |
14:50.03 | kerio | it also doesn't honour the setting to ignore the "hold key to sym" nonsense |
14:50.55 | freemangordon | _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.04 | kerio | freemangordon: 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.27 | freemangordon | _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.06 | freemangordon | I think so |
14:54.18 | freemangordon | and clicked on "open" button |
14:54.32 | freemangordon | well, maybe it is not popup |
14:54.57 | arcean | _ade_, the latest stable worldclock replacement and I can't reproduce |
14:55.08 | tadzik | freemangordon: 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.55 | freemangordon | tadzik: no, it receives a signal and changes the layout accordingly |
14:56.14 | freemangordon | if needed |
14:56.29 | freemangordon | QDesktopWidget::resize that is |
14:56.33 | freemangordon | (iirc) |
14:56.59 | *** join/#maemo-ssu kolp_ (~quassel@212.255.105.218) |
14:57.07 | freemangordon | tadzik: what is going on with opera 12? |
14:57.22 | freemangordon | any clue why it crashes as soon as started? |
14:57.35 | tadzik | yeah, 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.48 | tadzik | freemangordon: well, I have no such problem with it. Weird |
14:58.07 | freemangordon | tadzik: that is very strange |
14:58.16 | *** join/#maemo-ssu _rd (~rd@p57B488F6.dip0.t-ipconnect.de) |
14:58.26 | tadzik | did it happen to anyone else? Did you try re(naming|moving) its config file? |
14:58.28 | freemangordon | yes, it takes time, but not much to be done here |
14:58.37 | tadzik | so that is Qt's fault, aye? |
14:58.46 | freemangordon | tadzik: look at TMO, lots of people got hit by that |
14:58.59 | freemangordon | well, GTK does the same |
14:59.12 | tadzik | I don't have that impression |
14:59.23 | freemangordon | it just does it way faster :D |
14:59.39 | tadzik | yay, gtk finally better at something |
14:59.48 | freemangordon | gtk2.0? |
15:00.00 | tadzik | we have 3.0 on maemo? |
15:00.03 | freemangordon | no |
15:00.11 | tadzik | then yes, I mean 2.0 |
15:00.38 | tadzik | now that I look at it, fapman indeed does it too (visibly moving stuff around), and way faster indeed |
15:00.48 | freemangordon | see :P |
15:00.56 | freemangordon | anyway, gtg |
15:00.58 | freemangordon | bbl |
15:01.05 | tadzik | freemangordon: I'll poke Opera maintainer when I get back to the office, see if we can do anything about it |
15:01.11 | freemangordon | ok |
15:01.28 | freemangordon | tadzik: seems something has changed on the server side |
15:01.44 | freemangordon | which crashes opera on the device |
15:02.58 | tadzik | server side? What kind of server side could that be, Turbo? |
15:03.11 | tadzik | (Opera Turbo, that is) |
15:03.40 | tadzik | okay, I'll read the tmo thread and then start asking questions :) |
15:04.54 | arcean | _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.22 | arcean | _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.11 | arcean | _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.24 | ShadowJK | tadzik; 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.28 | ShadowJK | Also 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.54 | tadzik | that'd be UserJS I suppose |
15:36.12 | tadzik | (the fixes file) |
15:36.49 | tadzik | "Atleast one of the files is a big file" - one of what files, those fetched from Opera servers? |
15:37.01 | ShadowJK | that'd be the browser.js |
15:37.19 | ShadowJK | the "fixes" |
15:37.24 | ShadowJK | the rest seemed tiny |
15:37.57 | tadzik | so again: it crashes after opera start, or after website access? |
15:38.18 | ShadowJK | After a website has loaded |
15:38.51 | ShadowJK | when the spinning thing stops spinning and progress bar goes away |
15:39.31 | ShadowJK | On 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.08 | tadzik | curious. |
15:40.39 | tadzik | Okay, I'm guessing around and still haven't even looked at the tmo thread. Still have an exam to learn for :/ |
15:41.00 | ShadowJK | when loading something simple, like an image, there's about a second delay before crash |
15:41.48 | ShadowJK | Even more curiously, when launched from xterminal, it doesn't exhibit this behaviour, seems to run fine |
15:42.06 | luf | kerio: I upladed the new .deb on merlin.at for bluez-499 ;) Feel free to test it. |
15:42.21 | kerio | I'LL FEEL WHATEVER I WANT |
15:42.59 | luf | kerio: :D |
15:44.04 | kerio | luf: there's also a new obexd, isn't it |
15:44.14 | luf | I'll have to make some wiki for it ... |
15:44.28 | luf | kerio: It depends what is your version. |
15:44.59 | kerio | luf: 0.46-1maemo4+0cssu1 |
15:45.09 | kerio | so yes, there's 0.46-1maemo5+0cssu1 on your wobsite |
15:45.25 | luf | kerio: I fixed IrMC protocol last week or previous week. Thanks to don_falcone |
15:46.00 | luf | But it should be included in CSSU-testing ... |
15:46.03 | tadzik | ShadowJK: did anyone try stracing? |
15:46.48 | ShadowJK | not so far |
15:49.43 | luf | kerio: 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.08 | luf | kerio: it's fixed in 0.46-1maemo5+0cssu1 |
15:50.11 | kerio | k |
15:51.43 | *** join/#maemo-ssu NIN101 (~NIN@p5DD29231.dip0.t-ipconnect.de) |
15:53.26 | kerio | luf: what should we test? |
15:53.30 | kerio | remember, i don't have a carkit |
15:57.34 | luf | kerio: with bluez? I worked on PAN (network support). |
15:57.46 | luf | There is no need for pand now :) |
15:58.03 | kerio | oh, you figured how to connect to a NAP without pand? neat |
15:58.11 | luf | Yes. |
15:58.44 | luf | But from upstream it needed dbus connection all the time. |
16:00.06 | luf | permanent 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.26 | luf | I 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.08 | kerio | luf: and how can you disconnect? |
16:01.42 | luf | I 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.52 | luf | kerio: try to guess ;) |
16:02.08 | luf | /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.18 | kerio | neat |
16:02.58 | luf | org.bluez.Network{Peer|Hub|Router}.Register and org.bluez.Network{Peer|Hub|Router}.RegisterPermanent |
16:03.26 | luf | BTW I backported also config /etc/bluetooth/network.conf so it supports now the autoregistering of server parts. |
16:05.49 | luf | kerio: http://pastebin.com/DVuCbEtE |
16:06.29 | luf | What Interface is present (not commented out) that server role is started automatically during bluetoothd startup. |
16:07.19 | kerio | k |
16:08.01 | kerio | does it create the bridge by itself? |
16:13.32 | luf | Yes it can if none of such name exists. |
16:14.53 | luf | But you have to have kernel support for bridge driver (detected via /sys/module/bridge /sys/module/bridgedriver) |
16:21.10 | luf | cssu git with bluez refreshed so it contains the latest code. |
16:25.10 | kerio | luf: os x connected to my NAP :D :D :D :D :D |
16:25.14 | kerio | fucking sweet |
16:25.36 | luf | kerio: Welcome in real world ;) |
16:25.59 | *** join/#maemo-ssu arcean (~arcean@aaem131.neoplus.adsl.tpnet.pl) |
16:26.01 | luf | kerio: to put you back to the earth ... It's NAP only by the name ... |
16:26.14 | kerio | i just need a point-to-point connection anyway |
16:26.45 | kerio | :) |
16:26.51 | luf | GN and NAP has the same implementation inside bluez. |
16:26.51 | kerio | luf: is there a way to not create the bridge? |
16:27.05 | luf | Use PANU server role. |
16:27.31 | kerio | ooh good point |
16:28.38 | luf | After 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.16 | luf | BTW PANU is againist BT specification ... ;) |
16:29.37 | luf | PANU 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.25 | kerio | luf: nope, OSX can't trigger the connection |
16:33.21 | kerio | luf: ok, how do i configure btnap? |
16:33.26 | kerio | is it ifupped? |
16:37.47 | kerio | luf: ok, it's not ifupped :( |
16:45.37 | kerio | luf: how is one supposed to set the bridge up? |
16:48.40 | *** join/#maemo-ssu _rd (~rd@p57B488F6.dip0.t-ipconnect.de) |
16:49.35 | kerio | luf: ok, got it |
16:49.48 | kerio | now i have a reliable way to ssh to my n900 while i'm pooping :D |
16:52.45 | kerio | luf: awwww, i don't :( |
16:52.49 | kerio | it doesn't reach far enough |
16:52.57 | luf | kerio: I'm sorry I took my dinner. |
16:53.22 | kerio | luf: patch bluez so the range is big enough! |
16:53.23 | luf | kerio: I can do nothing how far the bluetooth reach ;) |
16:53.37 | kerio | that's what a lazy person would say! |
16:53.48 | luf | kerio: sure. I'm lazy. |
16:54.34 | luf | kerio: BTW you can use script in config file to configure the new device (gn, nap - bridge, panu the per connection device). |
16:54.40 | kerio | yep, that's what i did |
16:54.51 | kerio | but apparently i suck at shell scripting and i tried three times while using $0 as the interface name |
16:55.11 | kerio | apparently, ifconfig didn't want to configure the "/usr/local/bin/bluez-nap-up.sh" interface |
16:55.17 | luf | kerio: $1 is the interface name ;) |
16:55.27 | kerio | yeah, i realized that eventually :) |
16:55.47 | luf | kerio: welcome in whole new world :D |
16:55.55 | kerio | hm, i just realized that i can just configure the interface in /etc/network/interfaces and then tell bluez to use ifup |
16:56.25 | luf | kerio: it didn't work for me. No exact idea why. |
16:56.44 | kerio | then i'll leave it like this |
16:57.25 | luf | And bluez calls the script only during device up (so it doesn't cooperate with ifup well). |
16:58.25 | kerio | is bluetooth PAN more energy-efficient than wifi? |
16:59.31 | luf | I 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.57 | kerio | now i really wonder if i can plug an usb bt adapter to my router and get PAN there :D |
17:13.51 | luf | kerio: I see also that latency is quite higher with BT. You'll see if it's enough for you. |
17:16.56 | luf | I have a small problem that it seems that my NetworkManager 0.8.1 doesn't show me the BT connections (bnep0) :( |
17:17.16 | kerio | gnome sucks |
17:17.43 | kerio | hm, i wonder why nokia didn't use connman for the n900 |
17:17.47 | luf | I'm using quite old version you know RHEL 6 ... |
17:18.18 | luf | kerio: because using some closed source is sooo sexy. |
17:19.12 | luf | Uncle 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.16 | kerio | hm, it appears that bluetooth PAN is fucking awful |
18:07.20 | kerio | in 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.11 | freemangordon | hehe |
20:45.27 | freemangordon | be careful if you rely on your n900 to wake you up :P |
20:45.52 | arcean_ | it will be fun :P |
20:46.10 | freemangordon | well the fun is in stock one |
20:46.20 | freemangordon | look at the commits if you are curious |
20:46.28 | freemangordon | I really wonder how is that possibe |
20:46.32 | freemangordon | *possible |
20:46.47 | arcean_ | yeah, I have missed a couple of alarms |
20:47.04 | freemangordon | only a couple? lucky you |
20:47.30 | freemangordon | if it is not my GF to wake me up every day... |
20:47.33 | arcean_ | lol, is it really that bad? |
20:47.37 | freemangordon | yes, it is |
20:47.58 | freemangordon | toldya, look at what I've changed |
20:48.24 | freemangordon | stock was not meant to be used with more than one alarm :D:D:D |
20:48.41 | arcean_ | :D |
20:48.47 | freemangordon | global variables used all over the place, |
20:49.07 | freemangordon | with alarm cookies overwriting those on every new event |
20:49.10 | freemangordon | you can imagine |
20:49.14 | arcean_ | hmm, maybe some trainee wrote that ? :D |
20:49.20 | freemangordon | maybe |
20:49.32 | freemangordon | but 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.17 | freemangordon | arcean_: there was even one missing dbus_message_unref(message); |
20:51.45 | arcean_ | wtf :D |
20:51.51 | freemangordon | leading to one DBusMessage leak on every alarm event |
20:51.58 | freemangordon | yeah |
20:52.59 | freemangordon | no, wait, not one per alarm event |
20:53.07 | freemangordon | that one here https://gitorious.org/community-ssu/osso-systemui-alarm/blobs/master/osso-systemui-alarm.c#line389 |
20:53.23 | freemangordon | that function is called 7-8 times per alarm event |
20:53.27 | freemangordon | the fuck? |
20:53.49 | arcean_ | so far new alarm-ui works fine :) |
20:54.08 | freemangordon | and we're wondering why swap needs to be defragmented in a couple of days :D |
20:55.34 | freemangordon | arcean_: hope so |
20:55.55 | freemangordon | though maybe there are still some bugs to be found |
20:57.54 | freemangordon | I'll need to cleanup the code a bit |
20:58.01 | freemangordon | :( |
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) |