**** BEGIN LOGGING AT Sun Aug 27 03:00:02 2017 Aug 27 06:37:26 What hostname is irreco looking for? Because cannot resolve it. Aug 27 06:40:41 use pierogi Aug 27 06:40:46 much etter applicatio Aug 27 06:40:57 (sorry for missig letters, my keyoard dies) Aug 27 06:52:26 Trying it out. Does it include database of remotes, instead of Internet-loading it? Aug 27 06:52:43 Neither neoniq nor onyx tvs are in the list Aug 27 06:58:01 yes Aug 27 06:58:12 ut you ca write author if you get the codes Aug 27 06:58:18 he is active ad resposive Aug 27 06:58:46 ad gettig codes is easy (ad you ca sed the lircd cofig to him too ad he will iclude the codes) Aug 27 07:02:01 also, e sure to use versio from extras-devel Aug 27 07:02:09 it's more curret Aug 27 09:01:53 irreco works fine for me Aug 27 09:02:35 you can add codes for new TVs Aug 27 09:03:29 the lirc server is a config item in irreco Aug 27 09:51:46 when irreco doesn't find the host, it probably means lircd isn't started Aug 27 10:06:01 DocScrutinizer05: my n900 boots! I owe you a beer Aug 27 10:06:40 Wikiwide: iirc irreco/lircd is originally configured to start lircd via /etc/init.d/lirc during boot time. Ideally this should get changed in a way so starting irreco does a "sudo /etc/init.d/lirc start" and something similar in a `trap "sudo /etc/init.d/lirc stop" exit` in irreco (wapper script) Aug 27 10:07:43 rhn: it booting doesn't mean it's ok already. There might still be water causing electrolytic corrosion - if you want to be sure the device coniniues to work, make absolutely sure all water is gone Aug 27 10:08:23 DocScrutinizer05: that still gives hope though. but you're right, I'll leave it out to dry for a week, since I'm away anyway Aug 27 10:09:59 :-) Aug 27 10:10:13 DocScrutinizer05: I still consider myself in debt of a beer! if you're in Köln, let me know Aug 27 10:11:02 I'm also ready to hear about OpenMoko from an insider (proud owner of a dead GTA02) Aug 27 10:14:57 ooh, why it's dead? Aug 27 10:16:03 I'm really eager to learn about long term endurance of all components and manufacturing involved. I've been in charge of that aspect :-) Aug 27 10:16:35 DocScrutinizer05: drowned, like all my other dead devices Aug 27 10:26:52 rhn: in case you missed: Aug 27 10:26:55 ~joerg Aug 27 10:27:06 damn bot!!! Aug 27 10:29:30 ~joerg Aug 27 10:29:30 methinks joerg is a natural born EE, ex HW-developer and engineer of Openmoko. Usually known as DocScrutinizer. Initiator of http://neo900.org Aug 27 10:31:08 aha, I was wondering why there's multiple Joergs :) Aug 27 10:31:33 oh, the last bit I actually didn't realize! Aug 27 11:02:44 jonwil: lwhat exactly was wrong with my /etc/certs & secure? i'm again getting verify_result=19. Aug 27 11:03:33 i'll need to track what changes my cert store Aug 27 11:17:52 Weird Aug 27 11:39:25 I do have an idea to try that might help further. Aug 27 11:45:57 ~DocScrutinizer Aug 27 11:45:58 i heard docscrutinizer is Joerg (signature: 'jOERG'), a HW-developer and engineer of Openmoko. See ~joerg and http://wiki.openmoko.org/wiki/User:JOERG Aug 27 11:51:44 jonwil: sure. i'm up for anything Aug 27 11:52:31 Ok do you have the maemosec-certman-common-ca_0.2.9_all.deb file on your N900? Aug 27 11:52:48 yes Aug 27 11:53:37 Ok so you connect to your phone and run commands via SSH? Or do you use terminal? Aug 27 11:56:14 I hope the former ;^) Aug 27 11:56:39 though I guess for sicelo that fails with lack of PC to run the ssh client on Aug 27 11:56:48 i'm on terminal right now. Aug 27 11:56:48 no laptop at hand :-) Aug 27 11:56:55 :-D Aug 27 11:57:33 Ok so open terminal and switch to root. Aug 27 11:57:58 did you consider using H-E-N and a usb fullsize keyboard, plus CA-4711 TV cable? Aug 27 11:58:13 then change to the directory containing the .deb file Aug 27 11:58:38 sicelo: done that yet? Aug 27 11:58:43 ~hen Aug 27 11:58:43 somebody said hen was hostmode-easy-now, or http://talk.maemo.org/showthread.php?t=65232, or see ~hostmode Aug 27 11:58:50 ~hostmode Aug 27 11:58:51 hmm... hostmode is http://talk.maemo.org/showthread.php?p=652330, or http://www.youtube.com/watch?v=fkCDyUO0sKQ, or see ~hostmode-powered Aug 27 11:59:10 that YT vid Aug 27 11:59:45 DocScrutinizer05: i have stowaway (SU-8W lookalike) Aug 27 11:59:53 :-D Aug 27 12:00:19 You got terminal open? Aug 27 12:01:16 jonwil: yes. Aug 27 12:01:30 Ok, now run this command Aug 27 12:01:31 dpkg --force-depends -P maemosec-certman-common-ca Aug 27 12:01:42 It will remove maemosec-certman-common-ca including all the certificates Aug 27 12:01:51 You will be reinstalling it in a sec, dont worry Aug 27 12:02:05 Done that? Aug 27 12:02:55 yes Aug 27 12:03:18 Now do ls /etc/certs and tell me what you see Aug 27 12:03:49 the 3 directories Aug 27 12:03:54 what 3 directories? Aug 27 12:03:58 what names Aug 27 12:04:09 blacklist, common-ca, trusted Aug 27 12:04:27 ok, do rm /etc/certs/blacklist/* then rm /etc/certs/common-ca/* Aug 27 12:04:31 leave trusted alone Aug 27 12:04:44 That will remove any left over certificate crap on your system Aug 27 12:05:07 Then do ls /etc/secure/s and tell me if you see any files listed Aug 27 12:05:54 for reference: certman.blacklist certman.common-ca Aug 27 12:06:39 you should see no files in /etc/secure/s at all Aug 27 12:06:45 donenothing is there Aug 27 12:06:47 since you just removed maemosec-certman-common-ca Aug 27 12:06:52 Ok, great Aug 27 12:07:07 Now that you have nothing in /etc/certs/blacklist, /etc/certs/common-ca and /etc/secure/s you can do dpkg -i maemosec-certman-common-ca_0.2.9_all.deb and reinstall the package Aug 27 12:07:21 That will give you a 100% clean set of certificates matching the latest version. Aug 27 12:07:36 installing Aug 27 12:09:39 going to need a reboot, i guess :-/ Aug 27 12:09:43 ~#maemo clean certs is http://mg.pov.lt/maemo-irclog/%23maemo.2017-08-27.log.html#t2017-08-27T15:00:19 Aug 27 12:09:43 DocScrutinizer05: okay Aug 27 12:10:36 ~clean certs Aug 27 12:10:36 * infobot nukes certs's room and says to certs: Und zie problem is solved Aug 27 12:10:45 ~fu Aug 27 12:10:45 FFFFFFFFUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUU- Aug 27 12:11:16 ~forget #maemo clean certs Aug 27 12:11:16 DocScrutinizer05: i forgot #maemo clean certs Aug 27 12:11:27 ~#maemo clean-certs is http://mg.pov.lt/maemo-irclog/%23maemo.2017-08-27.log.html#t2017-08-27T15:00:19 Aug 27 12:11:27 DocScrutinizer05: okay Aug 27 12:11:35 ~clean-certs Aug 27 12:11:35 hmm... clean-certs is http://mg.pov.lt/maemo-irclog/%23maemo.2017-08-27.log.html#t2017-08-27T15:00:19 Aug 27 12:16:35 If this still doesn't work or if it stops working again, I am all out of ideas. Aug 27 12:17:00 Short of cloning location-proxy (not easy) and adding a bunch of debugs to it to see whats going on. Aug 27 12:19:33 and no I am not going to clone location-proxy :P Aug 27 12:24:05 no gps lock yet :-/ Aug 27 12:24:31 let me t me check something Aug 27 12:45:46 ok my N900 is sick .. i'll investigate a little later Aug 27 15:04:01 a-gps working again. hope it lasts Aug 27 17:04:04 Pali: poke, you still maintain kdepim-noakonadi? Aug 27 17:04:25 luke-jr: probably yes Aug 27 17:08:08 Pali: I got latest kdepimlibs 4 to build without akonadi. It breaks kalarm from noakonadi though. Aug 27 17:08:46 also apparently some gpgme stuff in https://github.com/a17r/kdepim/commits/noakonadi Aug 27 17:12:17 it is rebased my branch on top of the last kdepim? Aug 27 17:12:28 or what does it mean latest kdepim 4? Aug 27 17:15:36 kdepimlibs 4.14.10_p20160611 as in Gentoo Aug 27 17:15:55 kdepim or kdepimlibs? Aug 27 17:15:59 the latter Aug 27 17:16:20 based on https://github.com/a17r/kdepimlibs/tree/KDE/4.14 Aug 27 17:16:42 my branch is https://github.com/luke-jr/kdepimlibs/tree/noakonadi Aug 27 17:17:01 ok, I have not modified kdepimlibs, just kdepim Aug 27 17:17:11 as kdepimlibs worked without akonadi server... Aug 27 17:17:35 it required akonadi to build Aug 27 17:17:41 which conflicted with KDE 5 stuff :/ Aug 27 17:17:49 yes, client libraries were required Aug 27 17:22:50 anyhow, got rid of that Aug 27 19:41:32 I updated libplayback pull request after Pali comments earlier, not sure if there were notifications Aug 27 19:42:00 github does not send any notification after git's force push Aug 27 19:45:15 I do not see any obvious error, deb package is successfuly created in scratchbox and contains all needed files (like original nokia package), then no problem from my side **** ENDING LOGGING AT Mon Aug 28 03:00:00 2017