00:04.56 | *** join/#maemo-ssu FlameReaper (~assassin@115.132.47.148) |
02:45.13 | *** join/#maemo-ssu kolp_ (~quassel@212.255.225.13) |
03:11.50 | *** join/#maemo-ssu LaoLang_cool (~LaoLang_c@14.151.28.5) |
03:11.59 | *** join/#maemo-ssu M13 (~M13@170.133-224-87.telenet.ru) |
03:33.54 | *** join/#maemo-ssu amiconn_ (amiconn@rockbox/developer/amiconn) |
04:01.17 | *** join/#maemo-ssu DocScrutinizer05 (~HaleBopp@openmoko/engineers/joerg) |
04:19.30 | *** join/#maemo-ssu Natch (~Natch@c-fecee155.25-4-64736c10.cust.bredbandsbolaget.se) |
05:45.56 | kerio | fucking hell |
06:10.37 | *** join/#maemo-ssu dhbiker (~dhbiker@95.87.145.172) |
06:42.37 | *** join/#maemo-ssu Pali (~pali@Maemo/community/contributor/Pali) |
06:49.14 | DocScrutinizer05 | eh? |
07:00.45 | *** join/#maemo-ssu Vlad_on_the_road (~Vlad_on_t@ip-66.net-82-216-1.versailles2.rev.numericable.fr) |
07:26.32 | *** join/#maemo-ssu M4rtinK (~M4rtinK@ip-86-49-81-87.net.upcbroadband.cz) |
07:27.13 | *** join/#maemo-ssu andre__ (~andre@wikimedia/aklapper) |
07:33.12 | *** join/#maemo-ssu Martix (~martix@ip-62-245-106-78.net.upcbroadband.cz) |
08:05.46 | *** join/#maemo-ssu Martix (~martix@eduroam-sci-dhcp67.sci.muni.cz) |
08:06.19 | *** join/#maemo-ssu Martix (~martix@dhcp-233-084.eduroam.muni.cz) |
08:09.23 | *** join/#maemo-ssu M13 (~Miranda@83.149.37.26) |
08:14.44 | *** join/#maemo-ssu ZogG (~zoggrules@bzq-79-176-192-238.red.bezeqint.net) |
08:14.44 | *** join/#maemo-ssu ZogG (~zoggrules@funtoo/user/ZogG) |
08:29.27 | *** join/#maemo-ssu Martix (~martix@eduroam-sci-dhcp67.sci.muni.cz) |
08:57.12 | *** join/#maemo-ssu rmxircmonkey (~rmxircmon@31.7.60.130) |
09:42.27 | *** join/#maemo-ssu kolp (~quassel@212.255.225.13) |
09:47.12 | *** join/#maemo-ssu _shadowx (~l4m3rx@195.24.90.254) |
09:59.51 | *** join/#maemo-ssu futpib (~futpib@89.106.197.50) |
10:00.52 | *** join/#maemo-ssu LauRoman (~LauRoman@5-14-91-244.residential.rdsnet.ro) |
10:57.23 | *** join/#maemo-ssu int_ua (~int_ua@46.96.150.201) |
11:14.51 | *** join/#maemo-ssu Pali (~pali@Maemo/community/contributor/Pali) |
13:00.59 | *** join/#maemo-ssu Martix (~martix@severus.mzk.cz) |
13:02.49 | *** join/#maemo-ssu Martix_ (~martix@severus.mzk.cz) |
13:06.32 | *** join/#maemo-ssu Martix (~martix@severus.mzk.cz) |
13:08.15 | *** join/#maemo-ssu Martix_ (~martix@severus.mzk.cz) |
13:18.54 | *** join/#maemo-ssu int_ua (~int_ua@ip-602f.proline.net.ua) |
14:54.15 | *** join/#maemo-ssu Martix_ (~martix@ip-62-245-106-78.net.upcbroadband.cz) |
15:16.12 | *** join/#maemo-ssu arcean (~arcean@apn-77-115-109-16.dynamic.gprs.plus.pl) |
15:27.19 | *** join/#maemo-ssu Pali (~pali@Maemo/community/contributor/Pali) |
15:44.45 | *** mode/#maemo-ssu [+o merlin1991] by ChanServ |
15:45.03 | *** topic/#maemo-ssu by merlin1991 -> 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-01-07): 21.2011.38-1Tmaemo7.2; Stable(2013-01-10): 21.2011.38-1Smaemo6 | Next meeting 06.03 |
15:45.07 | *** mode/#maemo-ssu [-o merlin1991] by ChanServ |
15:54.54 | *** join/#maemo-ssu LauRoman (~LauRoman@5-14-91-244.residential.rdsnet.ro) |
16:13.20 | *** join/#maemo-ssu NIN101 (~NIN@p5DD28ED7.dip0.t-ipconnect.de) |
16:26.27 | *** join/#maemo-ssu M4rtinK (~M4rtinK@ip-86-49-81-87.net.upcbroadband.cz) |
17:09.09 | *** join/#maemo-ssu LauRoman (~LauRoman@5-14-91-244.residential.rdsnet.ro) |
17:13.01 | *** join/#maemo-ssu Woody14619 (~Woody@2620:4:4000:11:9c58:32e6:8b6c:934c) |
17:13.01 | *** join/#maemo-ssu Woody14619 (~Woody@Maemo/community/contributor/Woody14619) |
17:13.31 | *** join/#maemo-ssu Martix (~martix@ip-62-245-106-78.net.upcbroadband.cz) |
17:13.55 | *** join/#maemo-ssu Pali (~pali@Maemo/community/contributor/Pali) |
17:52.14 | *** join/#maemo-ssu gregoa (~gregoa@chello212186052066.410.14.vie.surfer.at) |
17:59.25 | *** join/#maemo-ssu luf (~luf@217.194.70.18) |
18:04.27 | *** join/#maemo-ssu Martix (~martix@ip-62-245-106-78.net.upcbroadband.cz) |
18:41.40 | *** join/#maemo-ssu xes (~xes@unaffiliated/xes) |
18:47.52 | *** part/#maemo-ssu xes (~xes@unaffiliated/xes) |
18:48.54 | *** join/#maemo-ssu _rd (~rd@p57B48A8C.dip0.t-ipconnect.de) |
18:53.11 | *** join/#maemo-ssu LauRoman (~LauRoman@5.14.91.244) |
19:47.26 | *** join/#maemo-ssu _rd (~rd@p57B48A8C.dip0.t-ipconnect.de) |
19:52.50 | *** join/#maemo-ssu M4rtinK (~M4rtinK@46.227.13.46) |
20:11.49 | *** join/#maemo-ssu _rd (~rd@p57B48A8C.dip0.t-ipconnect.de) |
20:45.13 | luf | freemangordon: ping |
20:45.22 | freemangordon | luf: pong |
20:45.43 | luf | freemangordon: have you tried thumbnails with ftp, nfs, dav smb? |
20:45.58 | luf | I'm just curious how it's working with hildon-thumbnail |
20:46.14 | luf | ... and remote fs |
20:46.47 | freemangordon | luf: no |
20:47.09 | luf | :( Any idea if it's even working with N900? |
20:47.19 | freemangordon | no |
20:47.25 | luf | :D |
20:48.09 | *** join/#maemo-ssu T_X (~linus@2001:4dd0:fb22:203:13:13ff:fe13:1313) |
20:49.12 | luf | Any idea if it did even work in Diablo or any older maemo? |
20:50.43 | luf | I don't understand the code very well. I'm trying to locate the part which is responsible for obtaining the original picture. |
20:51.19 | luf | I was unable to find any info about hildon-thumbnail ... |
20:51.27 | luf | *I'm |
20:52.15 | freemangordon | luf: I still believe it is better to use some generic icon for remote fs |
20:52.21 | freemangordon | files |
20:52.54 | luf | freemangordon: I have to find the best place to ignore working with thumbnails. |
20:53.31 | freemangordon | yeah, I see |
20:54.12 | luf | First logs I get is from filemanager (using libhildon-thumbnail0) ... |
20:54.47 | Pali | luf, if you want I have some (old) source code of maemo filemanager |
20:54.58 | Pali | maybe it can help you (or not) |
20:55.12 | luf | So the best it to not even calling hildon-thumbnail via dbus. |
20:55.24 | luf | Pali: It would be great. |
20:56.00 | luf | BTW is there any chance to sign some NDA and get closed source parts from Nokia? |
20:56.18 | Pali | no :-( |
20:56.20 | freemangordon | luf: are you kidding? |
20:56.24 | Pali | :D:D |
20:56.35 | luf | This question is due to some new possibilities in bluez (but dialogs doesn't support it). |
20:57.06 | luf | No, I see some miracles when som devs (after signing NDA) get some additional info. |
20:57.21 | luf | ... not with Nokia :)\ |
20:57.59 | luf | Pali: what do you mean with (old) source? |
20:58.30 | T_X | hi, I'm currently a little confused about how to report bugs. I'm having an issue and a "workaround" for the sip client. which package in the extras classification on bugs.maemo.org would I report it to? |
20:58.31 | Pali | source code of osso-filemanager version 2007.17 |
20:59.10 | Pali | ok, found it, here is: http://skeiron.org/tablets-dev/nokia_770_os2008_hacker_edition/hacker2008-sources.tar.gz |
20:59.27 | Pali | luf ^^^ |
20:59.28 | luf | Pali: Ugh. it's quiet old but better than nothing. |
20:59.31 | luf | Pali: Thanks. |
20:59.34 | Pali | :-) |
21:00.13 | Pali | see README file in that tarball, very interesting :-) |
21:00.49 | luf | T_X: what is the sip client package name? |
21:02.06 | freemangordon | Pali: do you know what I need to add to sources.list in order to use jacekowski's repo? |
21:02.16 | freemangordon | Pali: nokia-binaries that is |
21:03.00 | luf | Pali: Where someone can find such open source things? :D |
21:03.54 | Pali | deb http://maemo.jacekowski.org/mirror/repository.maemo.org/ fremantle/4bc37c7c77ebe90177c050b805a8dc79 nokia-binaries |
21:04.21 | Pali | luf, gitorious, garage, maemo repo, google |
21:04.42 | luf | Pali: :D |
21:04.44 | Pali | I found that source code of filemanager when I looked at tables-dev |
21:04.51 | Pali | there is nothing more |
21:05.03 | Pali | (only old code of backup application) |
21:05.24 | T_X | luf: sorry, don't know. this standard telephone client. it's a telepathy based client, isn't it? |
21:06.42 | luf | T_X: I don't use it ... that's why I asked. I was curious if it should be part of CSSU or not. |
21:08.11 | T_X | luf: sorry, I was asking because I didn't quite know where else to ask. #maemo-bugs is pretty empty |
21:08.27 | T_X | luf: are you using a different sip client or non at all? |
21:08.48 | T_X | but still would like to prefer this issue somewhere, to at least have it documented somehow |
21:09.21 | Pali | T_X, SIP is handled by sofiasip telepathy module which is open source |
21:09.39 | Pali | so there is very very little chance that somebody can look at it |
21:09.57 | Pali | report bug at bugs.maemo.org into section Communitu SSU |
21:10.02 | T_X | (my issue was, that I wasn't able to hear the other side. with tcpdump I noticed that this standard maemo sip client was sending a wrong "connection address" in the SIP/SDP header, it was wrongly advertising the one from my usb0 interface) |
21:10.46 | luf | T_X: what's your default gateway? |
21:10.53 | Pali | T_X, look if somebody did not reported it already |
21:11.58 | T_X | luf: the default gateway is over the wifi interface. also the other sip client and sip server are on the wifi interface. even on the same link |
21:12.33 | Pali | https://bugs.maemo.org/show_bug.cgi?id=11957 |
21:12.34 | povbot | Bug 11957: Sofia SIP client always reports the WLAN IP as its local IP |
21:12.51 | T_X | Pali: hm, I hit "New" and I see sections "Documentation", "Extras" and "Website". I don't see a section "Communiti SSU" |
21:13.33 | Pali | T_X isnt it above bug ^^^ |
21:14.16 | Pali | T_X it is in Extras |
21:14.33 | *** join/#maemo-ssu tg (~irc@2001:738:2001:2078:0:215:11:82) |
21:16.34 | T_X | I'm looking at it, not quite sure. sounds similar indeed. not sure whether the "local-ip-address" is the same option as the "Connection address" |
21:17.36 | Pali | merlin1991: we have reported some bugs against SIP telepathy module, can we update it with new from upstream? |
21:18.15 | luf | Pali: why not if API will remain (or no change for other components)? |
21:18.18 | Pali | SIP and jabber telepathy modules are part of maemo5 |
21:18.31 | Pali | luf, with sip it could be maybe problem |
21:18.39 | luf | Pali: same as libpng, zlib, ... |
21:18.57 | Pali | upstream devs renamed it from telepahy-sip to telepahy-rakia |
21:19.12 | luf | Pali: let's try ... in worst case you have to backport just the fixes. |
21:19.35 | T_X | Pali: ah, there is a product "Maemo 5 Community SSU" in the extras category. somehow I would have expected to see "Maemo 5 Community SSU" as its own category. or seeing sofia as its own package in the extras category |
21:19.37 | luf | Pali: I don't think that renaming can't be reverted (or maybe it should stay) |
21:19.55 | T_X | it was a little confusing to have "Maemo 5 Community SSU" in the middle of actual applications |
21:20.07 | T_X | luf, Pali: but thanks a lot! |
21:20.19 | luf | Pali: My steps are usually to take a look in wheezy. |
21:20.29 | Pali | T_X: ping andre__ about bugzilla |
21:22.03 | T_X | Pali: and yes, it's probably the same bug. although the symptoms are different for me. I'll just add to that ticket for now |
21:23.20 | luf | T_X: I'm curious what is your "workaround"? |
21:27.00 | T_X | luf: deleting the ipv4 address from the usb0 interface |
21:27.27 | T_X | then it uses the one from the wlan0 interface instead and that one works fine |
21:28.36 | luf | T_X: It was my guess :) You can try the workaround from the bug. It seems to me to be a little bit more comfortable (if it works). At least you can confirm it. |
21:29.30 | T_X | luf: ah, might be, I'll check in a minute |
21:45.03 | T_X | luf: hm, can't find the telepathy-mission-control anymore. therefore don't have this mc-tool |
21:46.39 | luf | T_X: I think: http://wiki.maemo.org/N900_Mission_Control (but it's not working right now :( ) |
21:47.56 | luf | T_X: http://talk.maemo.org/showthread.php?t=37651 |
21:48.07 | luf | T_X: apt-get install libmissioncontrol-utils |
21:50.00 | T_X | luf: thanks! yes, also got that package name from the google cache a second ago |
21:50.17 | T_X | (had been searching for telepathy-mission-control first, that's how it's named on debian) |
21:51.19 | luf | T_X: Maemo is Debian squeeze (or how it's typed) based ;) |
21:53.18 | *** join/#maemo-ssu Vlad_on_the_road (~Vlad_on_t@82.216.1.66) |
21:57.46 | kerio | isn't it etch? |
21:58.24 | luf | kerio: You're right. Maybe I should go to the bed ... |
21:58.35 | kerio | sleeping is good! |
21:58.50 | luf | kerio: But it's so big vasting of my time! :D |
22:00.21 | kerio | *wasting |
22:00.44 | luf | kerio: ou're right. Maybe I should go to the bed ... |
22:00.52 | luf | *You |
22:06.19 | T_X | luf: hm, the workaround on #11957 does not seem to work for me. maybe it's actually a different bug, hm |
22:07.01 | luf | T_X: maybe not. |
22:07.03 | T_X | it still announces the address of the usb0 device |
22:07.30 | T_X | (or I did something wrong, possibly) |
22:07.47 | luf | T_X: put the comment into the bug. Hopefully Pali will take a look on the bug. |
22:07.53 | *** join/#maemo-ssu nox- (noident@freebsd/developer/nox) |
22:11.53 | Pali | here are prepared patches for 1) persistent /etc/fstab 2) auto fsck 3) auto filesystem detection: |
22:11.55 | Pali | https://gitorious.org/~pali/community-ssu/pali-upstart |
22:12.00 | Pali | https://gitorious.org/~pali/community-ssu/pali-ke-recv |
22:12.14 | Pali | I did not tested it yet, only commited changes |
22:12.41 | Pali | kerio, you already saw some parts, now there are all patches ^^^ |
22:13.17 | luf | Pali: auto fsck? When is it started? Is user informed somehow? |
22:13.29 | kerio | luf: it's preening |
22:13.34 | kerio | Pali: that shit won't work for me at all |
22:14.00 | luf | kerio: what's "preening"? |
22:14.01 | Pali | same as on desktop, called with arg which decide if fsck is needed or not |
22:14.17 | Pali | all options are configurable |
22:15.03 | luf | Pali: That's good but do you start auto_fsck during boot when no info for user (just booting N900 for very long time)? |
22:15.22 | kerio | Pali: you're making the assumption that $HOME_TYPE is either ext3 or ext4 there |
22:15.26 | kerio | other fscks don't have -p |
22:15.45 | Pali | fsck.vfat has it too |
22:16.14 | kerio | ok so you're assuming that $HOME_TYPE is either ext3, ext4 or vfat |
22:16.45 | kerio | and why are you bothering with $HOME_TYPE, just call fsck |
22:17.54 | kerio | the problem you had **COULDN'T** have been caused by ext3/ext4 confusion - fsck.ext3 and fsck.ext4 are both symlinks to e2fsck, which doesn't differentiate behaviour according to the name of the called binary |
22:18.23 | Pali | kerio, because once when I called fsck it detected my ext3 /home partition as ext4, fsck forced ext4 check |
22:18.42 | Pali | then kernel mounted it as ext3 and wrote errors |
22:18.44 | kerio | EXT4 IS BACKWARDS COMPATIBLE WITH EXT3 |
22:19.29 | Pali | when it was monting (as ext3 which was specified in fstab) it tried to do some recovery |
22:19.37 | kerio | without any changes in options, done with tune2fs, you can mount an ext3 fs as ext3, write to it, umount, mount as ext4, write to it, umount, mount as ext3 and it'll still work |
22:19.49 | Pali | but that failed because it was unable to do something with ext4 |
22:20.56 | Pali | fsck converted something in my home to ext4 and ext3 kernel module called some ext3 recovery functions |
22:21.00 | Pali | and then it was damaged |
22:21.38 | kerio | there's no such thing as an "ext3" file system |
22:22.00 | kerio | there is such a thing as an extfs filesystem, an extfs filesystem with journal, an extfs with journal and extents |
22:22.43 | kerio | e2fsck doesn't make mistakes such as **add extents to the options of the filesystem** |
22:22.58 | kerio | it's not a mount option, it's stored in the superblocks |
22:24.36 | kerio | i'm not even sure why i'm discussing this - e2fsck doesn't give a shit about argv[0] |
22:24.55 | kerio | so your claim that it somehow had a different behaviour because it was called as fsck.ext4 is bogus |
22:53.52 | andre__ | Pali, pong |
23:08.44 | luf | freemangordon: I have the point where deny to thumb obex:/// ;) |
23:09.23 | luf | freemangordon: I think I also see the point where to make the thumb for obex:/// (but it's for another day). |
23:10.37 | luf | merlin1991: ping |
23:11.23 | luf | merlin1991: please create on http://gitorious.org/community-ssu/ new repo for hildon-thumbnail |
23:12.56 | *** join/#maemo-ssu M4rtinK (~M4rtinK@ip-86-49-81-87.net.upcbroadband.cz) |
23:32.52 | freemangordon | luf: great |
23:33.25 | luf | freemangordon: I only have the point where to deny ... |
23:35.10 | freemangordon | even better :D |
23:37.25 | luf | freemangordon: it's not better. I'd like to see thumbnail support for obex:// ;) |
23:38.04 | freemangordon | luf: imagine the traffic and the delay. also thumbnails are stored on the device afaik |
23:44.37 | luf | Yes. So it's created only once. |
23:44.45 | luf | freemangordon: ^^^ |
23:45.28 | luf | freemangordon: because it's tested on file modify time ... |
23:46.15 | freemangordon | luf: hmm, and what about videos? |
23:46.45 | luf | freemangordon: It's too far. |
23:46.48 | luf | :) |
23:46.51 | luf | ... now |
23:48.00 | freemangordon | luf: BTW I really hate remote directory thumbnails, because of windows. It just does not feel right, not to say that it eats all the bandwidth. Which is not that big for BT |
23:48.17 | freemangordon | but it is up to you :) |
23:49.32 | luf | You already have thumbnails fore remote fs (except BT - it seems there is some missing support in gvfs) |
23:49.59 | freemangordon | luf: ok, ok :) |
23:50.37 | *** join/#maemo-ssu M4rtinK (~M4rtinK@ip-86-49-81-87.net.upcbroadband.cz) |