**** BEGIN LOGGING AT Mon Jan 30 03:00:01 2017 Jan 30 03:01:46 https://youtu.be/a9DG_9OiRdY?t=2m22s Jan 30 03:03:09 sounds like what's known to linux as a zombie process Jan 30 03:04:21 i guess Jan 30 03:04:35 zombie process dont get killed? Jan 30 03:04:42 cant* Jan 30 03:06:01 ...which - after years of oblivion - git re-introduced by systemd lately. Together with break of all system monitor meter values after a few dozen minutes of running ksysguard Jan 30 03:07:18 Juesto: nope, they are already dead, that's why they are called zombies. Just the scheduler/kernel can't remove them from process table since they still wait for their SIGCHILD signal getting handled by their parent process Jan 30 03:07:23 or somesuch Jan 30 03:08:28 pre-systemd PID1 inherited zombies and instantly killed / removed them completely. PID1==systemd fails pretty much on that Jan 30 03:10:09 how i can even close the handles normally? Jan 30 03:10:28 the most weird part is that theres an unknown SID in security info of the process Jan 30 03:10:35 and with system metering I tend to blame systemd of remounting /proc or something like that Jan 30 03:11:29 Juesto: a zombie process is a process that hasn't been wait(2)ed on. Jan 30 03:11:46 Juesto: so the parent doesn't necessarily know that it's exited. Jan 30 03:11:52 its taking away permissions from administrators and this account shows up with full permissions: Account Unknown(S-1-5-5-0-234896922) Jan 30 03:12:22 and that sid is absolutely non existant Jan 30 03:12:24 now THAT sounds rogue - though really NFC about windows here Jan 30 03:12:38 Juesto: the mechanism is basically there because you can't just poll a pid to see if your child is still running, since pids are reused. Jan 30 03:13:25 You instead have to keep the pid around until the parent knows it's dead, via some wait(2) call. Jan 30 03:13:33 okay... Jan 30 03:13:39 its simply stuck Jan 30 03:13:52 maybe you should start into a known-clean windows (from a CD or somesuch) and run a rootkit/virus scanner Jan 30 03:13:55 i could indefinitely kill the process and it wont go away Jan 30 03:14:03 if you have zombies, it might indicate that the parent process is broken. Jan 30 03:14:04 perhaps Jan 30 03:14:42 wait, you're talking about zombies in Windows? nvm, I don't know anything about those. Jan 30 03:14:42 Ah Jan 30 03:14:52 seems just a restart will solve this Jan 30 03:15:05 because new processes arent really affected Jan 30 03:15:27 i guess i should check it more Jan 30 03:15:36 i did clean up the computer Jan 30 04:03:06 After this guy worked on his N9, would it be highly likely that cellular woud be working? https://youtu.be/a9DG_9OiRdY?t=2m22s Jan 30 04:58:35 DocScrutinizer05: I was refering to this http://www.ebay.com.au/itm/301795331657 Jan 30 04:59:49 and what's your question? Jan 30 05:03:43 what that guy does in that video doesn't look professional or savvy Jan 30 05:05:09 A bit subjective. Is it difficult to install? I don't see any threads about it on TMO. Could success rate be low? Jan 30 05:06:20 When lining it up, would half a millimeter make any difference? Jan 30 05:06:46 but in theory there are chances he'll succeed in the end... unless he used up all the (I think missing anyway) flux on the solder points and oxidized the solder by 4 dozen exposures of molten solder to plain air. Or he fired components on bottom side of PCB where he heats up stuiff with the hot air. Or the defect is caused by something totally unrelated to that SIM holder. Or don't know what Jan 30 05:08:24 hmm. Thanks very much :-) Jan 30 05:08:27 if the solder was good and a premium class flux applied, and reflow done right, the sim holder should get pulled into position by the surface tension of molten solder Jan 30 05:09:10 pushing it around a 5 dozen times for sure is not a smart thing to do Jan 30 05:09:30 Scraches the contacts? Jan 30 05:09:43 no, it exposes solder to air Jan 30 05:09:55 it's at best totally pointless Jan 30 05:10:05 worst case oxidized solder Jan 30 05:10:24 wow Jan 30 05:10:32 somehow my settings were nulled Jan 30 05:10:36 of different programs i use Jan 30 05:10:37 wtf Jan 30 05:11:03 and you know, oxidized solder doesn't make any good solder joints Jan 30 05:11:13 Thanks, will tell this to my uncle (some soldering experience) & see if he's upto it (repair 16gb & 64gb). Jan 30 05:12:36 to someone experienced in SMT rework, replacing the SIM card holder should be a pretty easy job, with a 100% success rate Jan 30 05:12:48 uh, sim or sd? Jan 30 05:12:56 whatever Jan 30 05:13:32 the holders don't differ much Jan 30 05:15:54 All the "phone repair shops" say 'no' or offer to be a middle man. Any keywords I should try when looking for a business? Jan 30 05:16:04 &repair Jan 30 05:17:22 ~repair Jan 30 05:17:25 nvm Jan 30 05:17:30 oh good. SMT = Surface Mount Soldering Jan 30 07:13:07 who is responsible for repository.maemo.org ? Jan 30 07:13:23 http://maemo.org/packages/view/oscp/ says Old version cleaned by repository management Jan 30 07:13:52 but http://repository.maemo.org/extras-devel/pool/fremantle/non-free/o/oscp/ still shows that package version in repo Jan 30 07:14:25 so, could repo maintainer look into the problem of not cleaning old pkg versions? Jan 30 07:31:09 hey there Jan 30 07:44:50 morning Jan 30 07:56:47 morgen Jan 30 08:04:06 KotCzarny: what is the problem? Jan 30 09:34:52 hi Jan 30 09:43:39 hi Jan 30 09:49:15 hmm, looks like some people are really having a go at porting stuff to droid4 Jan 30 09:55:14 bencoh: coo didn't know that exsisted! Jan 30 10:06:27 it's probably the best specifications device you can still find in QWERTY-slider form factor Jan 30 10:08:22 apart from the closed bootloader, yes. Jan 30 10:09:17 if only motorola (google) included it in their unlock campaign it would be the de-facto alternative Jan 30 10:11:12 Based on the Droid name, its safe to assume this phone is a Verizon Wireless phone and Verizon are notorious for locking down the software on their phones. Jan 30 10:12:28 well, as long as there are hacks to run custom kernel it's better than nothing Jan 30 10:14:23 maybe Jan 30 11:01:15 freemangordon: old packages are not removed, even if removal is triggered, and if i see it on my package and have dozen of old files, what about repo as a whole neeedlessly consuming resources Jan 30 13:45:17 w00000t Jan 30 13:45:28 i just convinced a #reprap user to make me a model of the N900 Jan 30 13:45:50 :P his skill is bigger than mine in modelling, lets hope his model is perfect first try ;) Jan 30 13:51:57 what do you plan to use it for? Jan 30 14:05:25 i want to make nicer deskstands for N900 Jan 30 14:05:39 more like a 'dock' Jan 30 14:06:10 imho, all the stuff you find on thingiverse.com and other 'physibles' websites, are total shit Jan 30 14:24:44 bencoh: KotCzarny: did u eventually found solution for unlock playback clipping? Jan 30 14:25:55 im having different kind of problem now, which might or might not be related. I have panucci clipping sound every now and then even if my phone just plays audio in my pocket through headphones Jan 30 14:27:34 Vajb: not sure you actually mean "clipping" Jan 30 14:27:43 Vajb: stuttering? Jan 30 14:28:49 and no, adding player to mediasrc didn't really fix the issue in the end Jan 30 14:29:13 maybe you have both to be in this group and call libplayback (?) Jan 30 14:29:47 umm hard to explain. It plays and then i hear loud pop Jan 30 14:29:48 well actually you can always try adding the relevant rule for mplayer since mplayer already calls libplayback Jan 30 14:29:58 bencoh, mediasrc helps, but i suspect something resets settings Jan 30 14:30:01 it might be bad quality file too Jan 30 14:30:16 KotCzarny: I suspect restarting ohmd helps Jan 30 14:30:31 bencoh, yes, but its not the solution Jan 30 14:30:38 of course it is not Jan 30 14:31:02 hehe do we need alarmed restaring something by minute to fix that.. Jan 30 14:31:15 no, since mafw works properly ;) Jan 30 14:31:18 vajb: some formats are based on floating numbers, and decoders might not normalize them properly Jan 30 14:31:30 so maybe mafw does call that libplayback as well Jan 30 14:31:38 this is mp3 Jan 30 14:31:59 bencoh, so, similar problem as 'keep the buttons alive'? Jan 30 14:32:16 ie. poll something to not let the audio system get reset? Jan 30 14:32:42 would be nice to have a dbus log when tweak stops working Jan 30 14:32:51 KotCzarny: not necessarily, but dunno Jan 30 14:33:18 well I couldn't catch any call to mce regarding volume buttons Jan 30 14:33:24 so, dunno Jan 30 14:33:29 s/call/method/ Jan 30 14:33:36 (using mdbus, I mean) Jan 30 14:34:58 that skipping is cpu related Jan 30 14:38:31 I dont think so Jan 30 14:38:48 err, which one are you talking about? Jan 30 16:58:47 mce, vol buttons? hmm? Jan 30 17:22:55 ((It plays and then i hear loud pop)) doesn't sound [sic] like stuttering either, are you sure it's not a system sound for e.g. ts click event? Jan 30 17:24:20 stuttering is basically always dropout that doesn't involve loud pops except for the sharp high frequency edge when the sine wave drops to 0 and when it returns to its nominal level Jan 30 17:24:41 very fast stuttering is perceived as buzz Jan 30 17:30:00 DocScrutinizer05: yes im sure, because device is set to silent mode. I think it was bad quality file or some ripping error. Jan 30 17:31:34 those would be reproducible Jan 30 17:31:58 I.E listen same song a 2nd time, check if pop is on same time Jan 30 17:33:07 silent mode only results in the expected behavior when both the audio policy enforced and the apps using that policy/group/whatever behave as specified Jan 30 17:34:55 when you use arbitrary apps they might not obey silent mode. When you set or define new modes, or tweak mode settings of existing modes aka policies, you might find "silent mode" doesn't behave like silent mode anymore. When an app enforces a new policy, you might *think* you have silentmode set but actually device is already in a different mode Jan 30 17:47:47 DocScrutinizer05: i am inperceivable Jan 30 17:47:50 ;) Jan 30 18:24:46 oh, that took me to decode :-D Jan 30 21:52:42 hey there Jan 30 21:57:31 DocScrutinizer05: nonfarfetched humor is less amusing to me :) Jan 30 22:00:43 hi Juesto Jan 30 22:01:32 still trying to get it working lol Jan 30 22:03:05 /lc/lc Jan 30 22:03:07 oops Jan 30 22:03:15 getting gentoo running on n900? Jan 30 22:03:39 buZz: maemo on devuan i386 Jan 30 22:03:45 dont have a n900 Jan 30 22:04:01 ah :D nice! Jan 30 22:11:23 still struggling with the build and install Jan 30 22:16:49 does chromium 'private / incognito mode' care less about broken SSL certs than normal mode? Jan 30 22:18:08 DocScrutinizer05: it treats them the same way as normal mode Jan 30 22:18:20 ta! Jan 30 22:19:05 It's driving me nuts all my browsers refuse to flawlessly open my own LAN's router's WEB interface Jan 30 22:19:47 "cert broken here!" "cert flawed there!" STFU stupid browsers! Jan 30 22:20:17 DocScrutinizer05: your router's SSL uses HSTS? Jan 30 22:20:27 HSTS? Jan 30 22:20:36 if not, you can just click past the warning Jan 30 22:20:36 never heard of Jan 30 22:20:55 https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security Jan 30 22:20:56 I do not want to 'click past the warning' every other day Jan 30 22:21:02 oh ok Jan 30 22:21:09 replace the cert then :P Jan 30 22:21:17 DocScrutinizer05: incognito works the same in chrome and chromium, the only things it does is that it doesnt save history and downloads history and such Jan 30 22:21:24 I did, the new one is flawed as well Jan 30 22:21:40 it's self signed which already seems too much for chromium Jan 30 22:22:01 DocScrutinizer05: add an exception Jan 30 22:22:07 how? Jan 30 22:22:32 hold on Jan 30 22:23:55 https://www.linkedin.com/pulse/add-permanent-ssl-certificate-exception-chrome-andrey-batyrenko DocScrutinizer05 Jan 30 22:24:43 DocScrutinizer05, are you sure it doesn't just disable certain checks that are only done in non-incognito mode by telling google's server which sites you're visiting, or hashes that could be reversed Jan 30 22:24:48 actually, thats something chrome used to have Jan 30 22:25:43 ... Jan 30 22:26:02 LjL: no idea, I have no notion about that Jan 30 22:26:11 DocScrutinizer05: use firefox or another browser that lets you add an certificate exception Jan 30 22:26:19 DocScrutinizer05, well, Chrome does that sort of thing, and perhaps so does Chromium, unless you disable it Jan 30 22:26:33 actually, in chromium you can click advanced and continue Jan 30 22:26:38 FF or other browsers don't work with the crap the router offers as web-UI Jan 30 22:26:55 chrom* Jan 30 22:27:06 ((in chromium you can click advanced and continue)) which is wjhat I have to do every other day Jan 30 22:27:52 try to get the certificate and import it in https/ssl manage certificates DocScrutinizer05 Jan 30 22:28:40 i cant even find how to gather the certificate Jan 30 22:28:45 I did, I never managed to see a "Place all certificates in the following store" Jan 30 22:28:56 you export it Jan 30 22:29:04 I did Jan 30 22:29:14 see the page i linked Jan 30 22:29:37 thats old chrome, new chrome location is manage certificates under https/ssl Jan 30 22:29:38 I also did that Jan 30 22:29:39 welp Jan 30 22:29:44 I did, I never managed to see a "Place all certificates in the following store" Jan 30 22:30:08 use windows certificate importer? Jan 30 22:30:46 i mean, just import each ? Jan 30 22:30:52 or you can select multiple files Jan 30 22:30:53 idk Jan 30 22:31:55 how many certificates are you handling ? Jan 30 22:32:35 huh? one Jan 30 22:33:03 why you want a "place all certificates in the following store" then ? Jan 30 22:33:18 just import it Jan 30 22:33:29 and it shows up under "cert authorities" in "manage certificates" after import, and it's marked "not trusted" and I can't change that even when I say "trust for all three options" Jan 30 22:33:56 (why you want)) because the site you linked to says I need to Jan 30 22:34:24 the linked page is actually for a older chrom* and for windows Jan 30 22:34:26 i guess Jan 30 22:34:54 thing is that chrom uses the OS certificate manager Jan 30 22:34:59 >>On the "Certificate Store" screen of the import, choose "Place all certificates in the following store" and browse for "Trusted Root Certification Authorities." Restart Chrome.<< OOHHH, maybe the last 2 words do the trick Jan 30 22:35:27 ^^ That's for windows and a older version of chrome DocScrutinizer05 Jan 30 22:36:08 yes find a way to place it in the trusted area of your os certificates storage Jan 30 22:36:19 apologies for the mess Jan 30 22:36:36 hmmmmm, didn't nag when restarting. Excellent Jan 30 22:36:58 yeah Jan 30 22:37:11 good to hear its solved Jan 30 22:38:23 restart did the trick! FRIGGIN STUPID browser!!! http://wstaw.org/m/2017/01/30/plasma-desktopx17764.png cert trusted now Jan 30 22:38:45 lawl :D Jan 30 22:39:31 lol, >japanese goverment< Jan 30 22:39:35 thanks a lot! Jan 30 22:39:39 yw Jan 30 22:39:41 :) Jan 30 22:41:37 w00t im having less issues building and installing fremantle-gtk2 i386 packages Jan 30 22:43:27 freemangordon: missing configure for hildon Jan 30 22:48:26 okay, im stuck Jan 30 23:27:16 gconf? Jan 30 23:30:38 or /home/user/.config/hildon-desktop/{home.plugins|notifications.db} ? Jan 30 23:32:11 or /home/user/.local/share/applications/hildon/* Jan 30 23:32:50 what are you talking about Jan 30 23:34:07 about missing config for hildon Jan 30 23:34:19 like /var/lib/gconf/apps/osso/hildon-desktop/%gconf.xml Jan 30 23:34:57 /var/lib/gconf/apps/hildon/%gconf.xml Jan 30 23:37:55 /etc/gconf/gconf.xml.defaults/schemas/apps/osso/hildon-desktop/%gconf.xml Jan 30 23:40:12 hm Jan 30 23:40:37 gconftool -R /|grep hildon|wc -l Jan 30 23:40:39 151 Jan 30 23:44:00 welp, what i should remove if i want sound without pulseaudio? Jan 30 23:44:04 without breaking applications Jan 31 00:07:32 http://www.hecticgeek.com/2012/01/how-to-remove-pulseaudio-use-alsa-ubuntu-linux/ ? Jan 31 00:14:37 lol, no >> Yep, you can forget about this method now either. Removing pulseaudio in ubuntu 12.04 now removes the package ubuntu-desktop so if you try this you're effectively done with ubuntu.<< Jan 31 00:15:27 >>It must be said the ubuntu devs are very good in enforcing the use of crap packages.<< Jan 31 00:18:22 lol Jan 31 00:18:31 metapackages can remain uninstalled Jan 31 00:18:41 without uninstalling anything else Jan 31 00:43:59 * Maxdamantus installed pulseaudio on his gentoo system to experiment with bluetooth audio (apparently bluez no longer supports alsa) Jan 31 00:44:11 Nothing really seems to use it atm. Jan 31 00:44:45 though I had to set some configuration option somewhere so it wouldn't start the PA daemon when something tried to. Jan 31 00:45:21 Presumably if you have that set and you're not starting the daemon somewhere else, it shouldn't be used. Jan 31 00:46:11 $ cat ~/.config/pulse/client.conf Jan 31 00:46:12 autospawn = no Jan 31 00:47:01 though practically, this is all fairly irrelevant for maemo: everything seems to be fairly tightly integrated with PA there. Jan 31 00:52:09 i should keep PA installed but tune it in a different way perhaps Jan 31 01:12:04 should i configure it to work system-wide instead of a per-use basis? Jan 31 01:17:14 nfc, I never bothered to learn about PA, particularly since I didn't find any good docs either Jan 31 01:36:01 I mean, https://freedesktop.org/software/pulseaudio/doxygen/index.html looks pretty pathetic Jan 31 01:37:33 http://www.linuxfromscratch.org/blfs/view/svn/multimedia/pulseaudio.html isn't much better, also seems obsolete Jan 31 01:38:23 clearly poettering Jan 31 01:38:59 :| Jan 31 01:40:45 you know Jan 31 01:40:50 ~poettering Jan 31 01:40:53 'sth is poettering' means it acts invasive, possessive, destructive, and generally in an egocentric exacerbating negative way. ``this cancer is extremely poettering'', or you look here for Linus' notion on what's poettering: http://lkml.iu.edu/hypermail/linux/kernel/1404.0/01331.html, or http://lkml.iu.edu/hypermail/linux/kernel/1404.0/01488.html, or see ~systemd cabal Jan 31 01:51:08 nfc..? Jan 31 01:51:30 definitely not the proximity tech Jan 31 01:51:31 ~wtf nfc Jan 31 01:51:33 NFC: no fucking clue Jan 31 01:52:07 lol Jan 31 01:52:12 ~wtf Jan 31 01:52:18 Hmm Jan 31 01:52:30 awesome Jan 31 01:52:34 who coded infobot? Jan 31 01:52:35 btw here's maybe why systemd has journald >> Maybe we can just add rate-limiting to the interfaces that add messages to the kernel buffers, and work around this problem that way instead while waiting for Gregs fix to percolate? Or are the systemd debug messages going to so many other places too that that wouldn't really help?<< (from http://lkml.iu.edu/hypermail/linux/kernel/1404.0/01488.html) Jan 31 01:52:45 ~owner Jan 31 01:52:45 TimRiker is my owner Jan 31 01:52:46 ah riker Jan 31 01:52:51 ~author Jan 31 01:52:52 author is probably root Jan 31 01:52:57 yeah just noticed in the whois Jan 31 01:52:59 lawl Jan 31 01:53:06 ~+help wtf Jan 31 01:53:06  Desc: Interface to the BSD wtf command Jan 31 01:53:07  Usage: wtf Jan 31 01:53:07 Example: wtf iirc Jan 31 01:53:17 yeah i already saw the pm Jan 31 01:53:21 oh Jan 31 01:54:52 infobot is awesome Jan 31 01:55:05 and meanwhile adult Jan 31 01:55:19 ;) Jan 31 01:55:22 aka >18 yeras old Jan 31 01:56:14 ooh, not really, only 17y 24w 4d Jan 31 01:56:44 or that was the day she got her ID card ;-) Jan 31 01:57:21 Cool Jan 31 01:57:32 anyways Jan 31 02:24:31 ok, 22yo. https://en.wikipedia.org/wiki/Infobot Jan 31 02:24:51 :p Jan 31 02:25:04 my bday is on 26 march 94 Jan 31 02:54:17 can maemo work without PA? **** ENDING LOGGING AT Tue Jan 31 03:00:01 2017