**** BEGIN LOGGING AT Thu May 04 03:00:03 2017 May 04 07:16:20 how up to date is Pidgin on Maemo? May 04 07:52:18 maemo debug tools: https://github.com/maemo-tools-old It seems that our repo has only an older version of these tools May 04 08:58:01 NotKit: old. May 04 08:58:34 why you ask? :-) we would be happy for someone to update it for us May 04 09:00:34 to check if it can be compiled with fremantle-gtk2 May 04 09:04:34 ok. we're looking forward. i use it daily for Telegram and Skype for Business/Lync (IM only) May 04 09:06:41 I've meant non-N900 devices with Hildon UI May 04 09:12:55 alright May 04 10:21:43 no opus decoding huh :( May 04 10:22:07 where? May 04 10:23:28 media player May 04 10:23:33 gstreamer, whatever May 04 10:23:42 oscp? :P May 04 10:25:32 :p May 04 10:26:05 i mean i guess i can just see if any of the gstreamer0.10-* adds opus support May 04 10:26:10 since it's a codec in the ogg container May 04 10:51:54 kerio: gst-inspect might help you May 04 11:52:28 xes: yes, our tools are pretty aged now May 04 12:03:32 http://paste.ubuntu.com/24510812 May 04 12:04:52 xes: actually I got no idea how community would/could/should update tools repo (et al) May 04 12:05:16 could CSSU cover this? May 04 12:05:50 or should tools go to maemo-extras repo? May 04 17:35:28 Hello. I have written an account about how I managed to boot Devuan on the N900. It's a pdf document (8 pages), intended mainly as a promemoria for myself. If anybody is interested, I'd share it for review, adjust what is needed to, and then make it public. Please let me know if you wish to read it. May 04 17:37:41 please do :) May 04 17:39:15 parazyd Just let's decide how to share it. I'd prefer first to do that privately, for reviewing purposes. May 04 17:40:05 you can send me a query here on irc i guess May 04 17:43:22 Enrico_Menotti, when do you want to release it? May 04 17:43:49 maybe i have some time to get my old data off my N900 and then try to install devuan on N900 May 04 17:43:56 but may not be soon... May 04 17:45:53 ravelo I'd like to share it privately for the moment. If you agree, I may query you and find a convenient way. May 04 17:46:48 Also, for now I did not really install the system - just booted it (uploaded the kernel to ram). May 04 17:47:11 And I didn't try a desktop environment yet. May 04 19:18:47 ~flasher May 04 19:18:47 refer ~flashing; http://www.jedge.com/n810/flasher/maemo_flasher-3.5_2.5.2.2.tar.gz (also .exe!), or http://www.chakra-project.org/ccr/packages.php?ID=5027 or generally http://www.google.com/search?q=maemo_flasher-3.5_2.5.2.2.tar.gz. HARMattan(N9): https://aur.archlinux.org/packages/fl/flasher-harmattan/flasher-harmattan.tar.gz; list of filenames/md5sums: http://pastebin.com/sYKdNJSH, or http://galif.eu/nokia/ May 04 19:19:27 Oh, the chakra-project link is dead May 04 19:19:39 ~lf May 04 19:19:40 well, #maemo lazyflashing is http://wiki.maemo.org/Updating_the_tablet_firmware#The_Lazy_Approach May 04 19:32:19 Erf, flashing my n900 did not solve my problem :( The screen stays black :( May 04 19:32:43 do you get anything on reboot? May 04 19:33:27 might be faulty lcd ribbon May 04 19:33:32 if nothing at all May 04 19:34:05 No, nothing on screen :/ May 04 19:34:25 which isnt bad in itself because fried modem spares are good candidates for parts ;) May 04 19:34:38 and swapping is quite easy May 04 19:34:55 I think I have a broken n900 somewhere around ^^ May 04 19:35:17 But I completly wasted the screw hole when trying to get the screen apart. May 04 19:35:26 The screws behind the screens. May 04 19:35:29 :/ May 04 19:35:32 there are screw removal tools May 04 19:35:37 search ebay/aliexpress May 04 19:35:53 but get good one May 04 19:36:56 Yep, also thougth about making a cut in the screws to unscrew them with a flat end screwdriver. May 04 19:37:07 But I don’t have the tool to do that -_- May 04 19:37:37 just grab a screw removal tool, it works and will come handy more than once May 04 19:37:47 Ok :) May 04 19:40:00 https://www.youtube.com/watch?v=8jliBOo10bA Maybe this method could to the trick :D May 04 19:50:18 do you get any sound/vibration at boot / when touching the screen? May 04 19:50:41 or trying to play with the widgets (even if screen seems off) May 04 19:51:28 I don't really remember what's the default behavior after reflashing but iirc it should show some signs of life in touchscreen is working and only display is defective May 04 19:51:52 you could also try the tv output, maybe (assuming this is enabled by default) May 04 19:52:06 tv output wont work without working lcd May 04 19:52:16 x is set to wrong res May 04 19:52:34 which is a pity May 04 19:52:54 but maybe it's fixable in software somewhere May 04 19:53:04 hmm are you sure about that? I somehow recall someone troubleshooting display issues with tvout May 04 19:53:28 yeah, i have tried by disconnecting lcd module from my working testing n900 May 04 19:53:48 and while physically broken lcd MIGHT work May 04 19:54:05 Enrico_Menotti: best is Wiki .. and no need to make anything private . . . errors and omissions are perfectly acceptable and will be corrected by yourself or anyone else. that's what wiki is all about May 04 19:54:09 if ribbon is broken, tv out wouldnt work either because x server wont work May 04 19:54:29 bencoh: At boot only the led light up, but there is no vibration :/ May 04 19:54:33 And no sound also. May 04 19:54:55 But the riboon seems good. May 04 19:55:05 uh, strange May 04 19:55:49 I guess you could try booting rescueOS using flasher and try doing a hw check from there May 04 19:56:03 that's probably how I'd go and debug it if I had to May 04 19:56:48 err, that's assuming rescueos enables usb/telnet by default May 04 19:57:13 I'm not sure about that know that I think about it, so you'd need to patch rescueOS initrd first May 04 19:57:25 s/know/now/ May 04 19:57:25 bencoh meant: I'm not sure about that now that I think about it, so you'd need to patch rescueOS initrd first May 04 19:57:46 yeah, it should, i've mentioned to nin101 that it's good to autostart telnetd May 04 19:58:10 so with most recent version there should be telnetd working May 04 19:58:15 did you add it / update binaries? May 04 19:58:20 neat May 04 20:00:07 sicelo Well, I could publish on Wiki, but since I'm really not experienced with this, I'd prefer some suggestions. What I have written is quite long, and I think it should be shortened a bit. But for this I'd need advice. May 04 20:14:31 https://n900.quitesimple.org/rescueOS/rescueOS-1.3/CHANGELOG It seems that telnet start automatically at rescueOS boot :) May 04 20:17:05 told'ya May 04 20:53:41 telnetd starts automatically, usb networking doesn't May 04 21:05:23 DocScrutinizer05: concerning the tools i think no one ever tested those new versions. After some check i think extras would be the right place - if someone knows such tools and is interested into comparing the behavior with the old ones May 04 21:05:48 xes: ack May 04 21:06:25 xes: unrelated: my ssh fails to connect to a remote sshd. Last local debug line: "debug1: Local version string SSH-2.0-OpenSSH_6.2" - known? May 04 21:07:43 http://paste.ubuntu.com/24513204 May 04 21:10:20 the next line should contain the version of remote ssh. Are you using the right port? May 04 21:11:34 yes May 04 21:11:59 it seems like remote sshd doesn't respond to the version inquiry May 04 21:13:25 but might as well be something arcane around ssh1 vs ssh2 protocol or whatever. My local ssh config file is pretty ancient May 04 21:14:49 bfc how to tackle that May 04 21:14:55 nfc even May 04 21:15:49 have you checked also with a telnet? sshd should reply with openssh version May 04 21:17:02 xes: http://paste.ubuntu.com/24513228 May 04 21:17:52 is the remote sshd in paranoid mode or whatever? May 04 21:24:11 oh.. is that a vbox natted vm with port forward for ssh? May 04 21:27:43 if yes please check again the vbox nat forward rule. sshd must reply with his version in any case (if you are knocking at the right door) May 04 21:31:30 freemangordon: have you ever tried to increase the video encoder buffers into libgstdsp to limit the random frame drop with HD resolutions? May 04 21:32:27 DocScrutinizer05: you *are* geting the wrong version of openssh May 04 21:32:34 that's not the version in the vagrant box May 04 21:33:01 err what? May 04 21:33:10 that's my local ssh version May 04 21:33:30 this nevertheless is supposed to connect to a different version sshd May 04 21:33:31 ah May 04 21:33:41 i thought that was the sshd version May 04 21:34:24 xes: my vagrantbox seems to be the culprit, it's "too old" Vagrant 1.7.4 May 04 21:34:53 it works with the devuan jessie vagrantbox before RC1 May 04 21:36:41 DocScrutinizer05: anyway, also ssh protocol incompatibilities are checked after ssh version hello message May 04 21:37:27 DocScrutinizer05 As you suggested a couple of days ago, I made notes about my work on Devuan for the N900. Before making them public, I'd like some feedback, so I'm proposing anybody who's interested to read them. Would you like to? May 04 21:39:43 Enrico_Menotti: please paste it on an etherpad page. Many guys here will be ready to read it and review some part if needed May 04 21:39:50 xes: parazyd: http://wstaw.org/m/2017/05/04/plasma-desktopj22054.png http://paste.ubuntu.com/24513347 May 04 21:40:30 xes It's a pdf file - is there some place where I may upload it? May 04 21:40:32 Enrico_Menotti: what xes said May 04 21:41:20 please paste the plain ascii text to an etherpad May 04 21:41:39 DocScrutinizer05 xes I'm a bit unexperienced with these things. Could you please suggest a specific page? May 04 21:41:45 or worst case to a pastebin May 04 21:43:13 how about https://public.etherpad-mozilla.org/ or worst case http://paste.ubuntu.com/ May 04 21:43:52 Enrico_Menotti: https://etherpad.net/ and create a new pad May 04 21:44:29 I'm just looking the one suggested by xes. May 04 21:45:07 ...then open another browser and play with yourself while pointing at the same pad ;) May 04 21:46:00 * DocScrutinizer05 found etherpad.net to be relatively fail-happy May 04 21:46:17 might have changed since May 04 21:46:56 DocScrutinizer05: have you tried to ssh to eth0's ip -p 2200? May 04 21:48:24 no May 04 21:50:06 jr@saturn:~/Downloads/devuanVGtest> telnet 192.168.4.21 2200 May 04 21:50:07 Trying 192.168.4.21... May 04 21:50:09 telnet: connect to address 192.168.4.21: Connection refused May 04 21:51:05 DocScrutinizer05: dunno, i'm using virtualbox5 May 04 21:51:22 * DocScrutinizer05 needs to update vagrant, which is a PITA since they don't provide a rpm for opensuse May 04 21:53:19 obviously whatever vagrant1.7.4 expects to find in the vagrantbox image isn't provided by vagrant1.9.1 anymore, so my old vagrant fscks up the sshd setup May 04 21:55:03 i think to recal that to use the virtualbox nat port redirection you can't point at localhost since the nat is defined starting from primary host network interface May 04 21:56:22 * DocScrutinizer05 HMMMMs @ http://paste.ubuntu.com/24513413 May 04 21:56:51 then, maybe an old vagrant version expects a different virtualbox nat behavior (that has been changed 2 years ago..more or less) May 04 21:57:11 aaah, now that sounds like sth May 04 21:57:48 though, the connection seems to get established, so NAT can't be the culprit? May 04 21:59:38 change the virtual IF definiton and use a bridged network interface May 04 21:59:59 it works with an old vagrantbox! May 04 22:00:57 if it's not in the vagrantbox image and not in http://paste.ubuntu.com/24513413 and not in vagrant executable, then I don't know May 04 22:02:01 aaah, maybe I changed the network interface in VB config of old vagrantbox? May 04 22:13:36 http://paste.ubuntu.com/24513620 May 04 22:15:25 DocScrutinizer05: maybe you are recalling a trick/tweak that you made to address it? May 04 22:16:10 nope, wish I could recall what I did May 04 22:19:09 https://github.com/mitchellh/vagrant/issues/3232 May 04 22:23:01 changed syntax .... port fwd definition conflict between guests... May 04 22:24:34 hmm, my vagrant is 1.7.1 May 04 22:25:12 and works with a 1 year old devuan vagrantbox (though I *might* have tweaked something in virtualbox config) May 04 22:25:49 then, I can't see how any tweak I did in virtualbox only applies to the old vagrantbox and fails on the new one May 04 22:29:00 xes: do you see any mistakes I made, or tweaks I applied, in http://paste.ubuntu.com/24513620 ? May 04 22:32:19 where is the network definition into the Vagrantfile you are using? May 04 22:33:41 if it is not there, it should be hand-made into vbox May 04 22:35:25 To anybody who's interested: https://oasis.sandstorm.io/shared/rRUHLjKxQz-owubUREr0FXnJh9ZCTpyLEpjmTTNflW4 (you may comment directly the file). (Devuan on N900.) May 04 22:36:20 DocScrutinizer05 xes sicelo parazyd (and anybody else) ^^^ May 04 22:38:34 Enrico_Menotti: thanks for sharing May 04 22:41:33 xes: I can't find any vbox config specific to that ~/vagrant-test/kicad-devuan-amd64 dir May 04 22:41:57 so I assume there's none May 04 22:42:11 unless it's in vagrantbox file May 04 22:42:47 http://paste.ubuntu.com/24513413/ May 04 22:43:01 xes You're welcome. :) May 04 22:46:48 Bedtime. G'night. May 04 22:47:31 goodnight May 04 22:51:15 DocScrutinizer05: net definition is at the beginning of .box file May 04 22:51:37 I don't touch the .box file May 04 22:52:19 ugh, so I need to open it in vbox, then edit it there, then store May 04 22:52:34 which might well be what I've done, back when May 04 22:53:11 no port fwd definition there... May 04 22:53:32 the port is fine, no? May 04 22:53:45 no May 04 22:53:54 I mean, the shit thing *connects* May 04 22:54:16 I see it listening on the port, in netstat May 04 22:54:53 the old vm is still there? May 04 22:55:59 tcp 0 0 127.0.0.1:2200 0.0.0.0:* LISTEN 18460/VBoxHeadless May 04 22:56:03 the new one May 04 22:56:19 I meanwhile stopped the old one May 04 22:56:56 and the new one also fails on port 2222 when I start it with no concurrent box running May 04 22:57:19 it's evidently the sshd that blows chunks May 04 22:57:27 or some firewall or whatever May 04 22:58:01 no idea. i have downloaded a piece of ~15MB of .box and at the beginning there is the box.ovf definition May 04 23:42:14 I suspect vagrant 1.7.1 patches some stuff in the .box file, and the format changed since May 04 23:42:44 I tend to blame sshd config May 04 23:45:29 probably vagrant injects some stuff into the box during boot via console. And one of that is a config file for sshd May 04 23:46:47 and vagrant1.7.1 does use a sshd.conf that's incompatible to new version of sshd as in devuan-rc May 04 23:47:44 there were quite a few CVE-patches against sshd recently, no? May 04 23:52:18 yes there are a few... but from my point of view the problem is at nat level May 04 23:53:38 it's time to close the eyes. Have a good night Doc May 05 00:07:22 * DocScrutinizer05 is lost: http://paste.ubuntu.com/24514051 **** ENDING LOGGING AT Fri May 05 03:00:01 2017