[00:02] <zmoylan-pi> even now they still have the irish teletext page numbers... but its not on waybackmachine as robots.txt stopped it... http://www.rte.ie/aertel/desktopxhtml/103-1.html
[00:02] <ali1234> that's... not teletext
[00:02] <ali1234> looks like red button
[00:02] <zmoylan-pi> no but back when teletext was still in use. the pages looked identical to the teletext pages
[00:03] <zmoylan-pi> now it's more... digital service
[00:03] <ali1234> yeah
[00:03] <zmoylan-pi> but still the same page numbers
[00:03] <popey> About ready to lob my new laptop out the window thanks to bug 1522922
[00:03] <lubotu3`> bug 1522922 in xserver-xorg-video-intel (Ubuntu) "Screen flickering in Intel i915 driver" [High,Triaged] https://launchpad.net/bugs/1522922
[00:03] <ali1234> digital launched without page numbers. everyone hated it
[00:03] <ali1234> so they brought back the numbers, but it still sucks
[00:03] <zmoylan-pi> drink enough coffee to make you phase at same speed as blink? :-P
[00:04] <popey> tried patching out the bits that people say broke it, and kernel failed to build :(
[00:04] <zmoylan-pi> if you drop the screen res/colour depth does the flicker go away?
[00:05] <sebsebseb> woo popey pretty much  lives on IRC even now :d
[00:05] <daftykins> popey: that sounds like that skylake driver issues in older kernels, which ver you dealing with?
[00:05] <popey> its not an older kernel issue
[00:05] <daftykins> oh ok
[00:05] <popey> it affects these chips if you drive it less than the full capability
[00:05] <popey> so if it's capable of doing 4k external (e.g.) but has a 1080p you will see it
[00:05] <daftykins> i read about flickering happening on skylake without this preliminary support param being added
[00:05] <popey> as 1080p panel is less than capacity
[00:06] <daftykins> yay Linux
[00:06] <popey> It is allegedly two patches, they have a new patch (two in fact) but those got rejected by Intel QA
[00:06] <popey> some months ago
[00:06] <popey> and it's just sat there unfixed since
[00:06] <ali1234> i can't remember the last time i had a problem with nvidia :P
[00:06] <popey> and we ship this kernel on thursday
[00:07] <penguin42> popey: Then revert that pair?
[00:07] <popey> as i said, i tried but kernel biuld failed
[00:07] <popey> <- not a kernel hacker :)
[00:07] <penguin42> popey: Oh, got the error? It's probably pretty easy to fix the build error
[00:07] <ali1234> git revert?
[00:07] <popey> i have the two patch files and -R reverted them
[00:08] <popey> lemme try the build again, have rebooted since so lost scrollback
[00:08] <ali1234> did you commit the changes after?
[00:08] <popey> no, I'm not using git
[00:08] <penguin42> oh
[00:08] <ali1234> did it even reverse apply clean?
[00:08] <ali1234> lol why not??
[00:08] <popey> uh
[00:09] <popey> because i was building from the source that built the kernel I'm running
[00:09] <ali1234> building from the source deb?
[00:09] <popey> yes
[00:09] <ali1234> ew
[00:09] <popey> so i could shove it in a ppa
[00:09] <ali1234> i don't even know how to make that work
[00:09] <popey> okay, I'll do this on my own, never mind.
[00:09] <ali1234> without modifying the source
[00:09] <penguin42> popey: Yeh throw us the errors you get, it looks like it should revert OK
[00:10] <penguin42> popey: Remember to patch -R them in the opposite order to that they were applied
[00:10] <popey> ok
[00:10] <popey> ta
[00:10] <penguin42> why are you running the internal LCD at not-it's normal-res ?
[00:11] <popey> I'm not
[00:11] <popey> I'm running it at 1080p, native res
[00:11] <popey> the bug says if you run it less than the chipset capability
[00:11] <popey> I mean, it's entirely possibly I'm seeing a different bug
[00:11] <penguin42> oh less than chipset capacity, I thought it was less than panel capacity
[00:11] <popey> which is why I want to test reverting these two patches to see
[00:11] <popey> because others reported it worked
[00:12] <popey> hm
[00:12] <popey> http://paste.ubuntu.com/15884141/
[00:13] <penguin42> oh, you've got a machine called gort too :-)
[00:13] <popey> :)
[00:15] <penguin42> popey: OK, without understanding anything about the actual hardware.....
[00:15] <penguin42> popey: You see that line where it says train_set_valid = true;   ?   try making that false.
[00:16] <penguin42> popey: and leave the rest as is
[00:16] <popey> undo the patch revert?
[00:16] <penguin42> popey: Yeh, back to clean source
[00:16] <popey> ok
[00:16] <popey> ta
[00:16] <penguin42> popey: My theory goes that the whole thing is a cache and it only uses the cache if that flag is valid; so if it's never valid then perhaps it'll just do the old path
[00:20] <penguin42> popey: Or apply the patch in comment 31
[00:26] <ali1234> that's a really weird patch
[00:26] <ali1234> it doesn't actually introduce any new behaviour, it just sometimes avoids doing the old behaviour
[00:28] <penguin42> ali1234: What's so weird about that?
[00:29] <penguin42> ali1234: It's an optimisation to try and avoid doing that thing sometimes
[00:29] <ali1234> yes
[00:29] <ali1234> but
[00:30] <ali1234> it seems very long winded
[00:30] <penguin42> ali1234: I suspect there's a lot of ordering stuff about when you can avoid it and error recovery and stuff - which they've obviously not got right
[00:31] <ali1234> yeah that big bit with DRM_DEBUG_KMS
[00:31] <ali1234> it will always run if control reaches it
[00:31] <ali1234> i suspect that is the problem
[00:31] <ali1234> it tries to reuse the stuff, then always hits that bit of code and decides actually it can't reuse it
[00:32] <ali1234> that's the only bit that actually does anything
[00:33] <ali1234> but the logic of that is weird
[00:33] <ali1234> if (thing is valid) { thing is not actually valid};
[00:34] <daftykins> i'd heard from somewhere that intel engineers are finding their own hardware a bit of a challenge even under Windows these days
[00:34] <ali1234> i would have explicitly set the flag to not valid, reversed the if, and then set the flag back if it was successfully made valid
[00:34] <popey> The intel video driver has been awful on linux for a long time now
[00:35] <daftykins> mmm
[00:35] <penguin42> daftykins: The damn stuff is all getting very complicated - VGA was just nice and simple; this things having to do protocol negotiations with the LCD panel, and people care about really really low power and there's firmware blobs and who knows what
[00:36] <daftykins> oh totally
[00:36] <penguin42> (That probably means there's firmware on the panel as well? That's a scary thought)
[00:36] <daftykins> well VGA seems to be a constant hassle with EDID woes these days, judging from my time in #ubuntu giving support
[00:37] <daftykins> 9 times out of 10, switching to a digital interface would at least let you see what was going wrong more clearly, if not just solve it immediately
[00:37] <daftykins> the fact it's still delving into xorg.conf after all these years though is such cringe
[00:38] <penguin42> yeh fighting X seems to have got more common again
[00:38] <daftykins> a really gifted guy that comes in #ubuntu sometimes has an amazing setup of 5+ displays from a business line Dell laptop which he has an external graphics card connected into via expresscard
[00:39] <daftykins> amazing amount of fiddling to get his display setup going :D
[00:40] <penguin42> oh heck, is that one display at each point of the pentacle to get that to work?
[00:40] <ali1234> hmm i think i see the problem
[00:40] <ali1234> here is the context: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/i915/intel_dp.c?h=v4.4#n3735
[00:42] <penguin42> ali1234: That return is unusual
[00:42] <ali1234> immediately above that, intel_dp_reset_link_train was called
[00:42] <ali1234> then if the flag is marked as valid it is called again in the loop
[00:42] <ali1234> and then the return
[00:43] <ali1234> but presumably that doesn't happen if it didn't happen the first time
[00:43] <ali1234> then below it we have some "voltage_tries" stuff
[00:43] <ali1234> so that loop is designed to run a few times, maybe, before it works
[00:45] <ali1234> i suspect deleting lines 3724-3730 might actually be the correct fix
[00:45] <ali1234> maybe someone forgot to delete it
[00:46] <ali1234> or possibly only call it if (!intel_dp->train_set_valid)
[00:48] <penguin42> ali1234: I'm not sure - I don't understand how much it's trying; my reading is it's resetting that clock recovery stuff, if that comes up ok then it's done; only if that fails does it then go into the stuff where it tests the training set stuff?
[00:49] <ali1234> i read it like this
[00:49] <ali1234> before the patch: call intel_dp_reset_link_train, then make sure everything came up okay
[00:50] <ali1234> if not, call intel_dp_reset_link_train and loop
[00:50] <ali1234> up to 5 times
[00:51] <ali1234> so what's the point of the new bit of code?
[00:51] <ali1234> it only makes sense if they are trying to avoid the reset entirely
[00:51] <ali1234> in which case... the reset before the loop shouldn't happen
[00:51] <penguin42> ali1234: I'm not sure if it's one reset or a few; is the link training the same thing as the clock recovery?
[00:52] <ali1234> lines 3725, 3757, 3776
[00:52] <ali1234> all the same call
[00:53] <penguin42> hmm true
[00:54] <penguin42> ali1234: Yeh except the 2nd patch in the series changes the intel_dp_reset_link_train
[00:55] <ali1234> i'm looking at the 4.4 flat code
[00:55] <penguin42> ali1234: It avoids reseting the data if the flag is true
[00:55] <ali1234> second patch?
[00:55] <ali1234> you mean the memset?
[00:55] <penguin42> yeh
[00:56] <ali1234> i dont think that is relevant
[00:56] <ali1234> also that's the first patch
[00:56] <penguin42> ali1234: so in both cases it wiggles the training stuff, but after these patches it starts the training stuff from the previously cached settings
[00:56] <ali1234> you can tell because it adds the bool, the second one just uses it
[00:57] <penguin42> yeh, but I'm nots ure it's bad to call that dp_reset_link_train
[00:57] <ali1234> does it actually look at the flag inside that function?
[00:57] <penguin42> if it's just writing the same data back
[00:57] <penguin42> yeh
[00:57] <ali1234> oh is that the function where the memset happens?
[00:57] <ali1234> i see
[00:57] <penguin42> ali1234: https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/patch/?id=4e96c97742f4201edf1b0f8e1b1b6b2ac6ff33e7
[00:57] <penguin42> ali1234: See the first change in there
[00:57] <ali1234> yeah
[00:58] <popey> Heh, i love just mentioning something in here and you guys having fun with understanding the code :)
[00:58] <penguin42> popey: *trying* understanding the code
[00:58]  * penguin42 knows very little about eDP, the intel training stuff or any of that
[00:59] <penguin42> but I think most serial systems have training phases these days
[00:59] <ali1234> so...
[01:00] <ali1234> easiest way to revert this is to set the flag to false right before the line 3725
[01:00] <ali1234> then it should behave exactly as before
[01:01] <penguin42> hence my suggestion before of just removing the thing that ever set it to true
[01:01] <popey> ..still building
[01:02] <ali1234> yeah that should also work
[01:02] <ali1234> although... where does it get initialized the first time?
[01:02] <penguin42> popey: Still?
[01:02] <penguin42> popey: you're using -j   right?
[01:06] <ali1234> um
[01:06] <ali1234> train_set_valid is never initialized?
[01:06] <penguin42> hmmmm
[01:06] <ali1234> (possibly)
[01:06] <ali1234> so maybe it's just trying to use garbage?
[01:06] <ali1234> that would certainly explain the flickering
[01:07] <penguin42> that structure might be safely 0 initialised as a whole
[01:09] <penguin42> ali1234: I think it might be part of the intel_dig_port that they use kzalloc to allocate
[01:10] <popey> it's only doing j2 i think
[01:10] <ali1234> comes from enc_to_intel_dp which is converting some other thing
[01:11] <popey> oh, -j4
[01:11] <penguin42> popey: My normal thing is 2x the number of cores I have
[01:11] <penguin42> popey: The big problem with distro configs is they enable *everything*
[01:12] <penguin42> popey: There are probably no users of USB lego mindstorm drivers on the same machine as fibre channel storage and 100Gbps infiniband connections
[01:12] <penguin42> probably
[01:13] <popey> yeah, I'm trying to change as little as possible
[01:13] <popey> because in the past I have changed too much and knackered some other part of my daily workflow
[01:15]  * penguin42 did about 15 kernel builds during the week trying to bisect down a screwup that was breaking something I was using; slowly got more annoyed removing random USB drivers and the like to speed it u
[01:15] <penguin42> p
[01:16] <ali1234> yeah, it's in intel_digital_port which is kzalloc'd
[01:16] <popey> i wanted to try a really old kernel, turns out it didn't have the aes bit to decrypt my luks hdd
[01:16] <penguin42> really? Hasn't that stuff been there for ever?
[01:17] <popey> sure, but we switched to a new cypher
[01:17] <popey> from ~4.x
[01:17] <penguin42> oh
[01:17] <popey> so my default install can only be unlocked with a 4.x kernel
[01:17] <popey> which is a useful datapoint
[01:18] <popey> heh, building modules for TV cards I will never own
[01:19] <popey> I wonder how many of these drivers are in use by like one guy somewhere
[01:20] <penguin42> popey: Often the case some of this stuff is now none
[01:20] <ali1234> i know for a fact that some of those DVB drivers don't work any more
[01:20] <popey> what, kernel changed and they weren't updated?
[01:21] <penguin42> popey: I do have an unfortunate problem with one of my dads old laptops, the VGA/DRM driver for it was removed because someone noticed it was hopelessly insecure and no one wanted to spend the time to fix it; so the laptop is now using the generic drivers on 14.04 and is slow as hell
[01:21] <ali1234> i don't know why they don't work... they just don't
[01:21] <penguin42> popey: Welcome to bit rot
[01:21] <popey> ew
[01:21] <popey> vesa
[01:21] <penguin42> yeh
[01:22] <popey> ooh, it's building zfs
[01:23] <popey> which is separate it seems
[01:23] <popey> checking zfs license... CDDL
[01:23] <popey> heh
[01:26] <daftykins> whilst i'd be the first to say people should no longer be using them, those that insist on keeping using netbooks have basically got a non-workable system with a lot of modern stuff now because the intel driver seems to have regressed for GM965 since 12.04
[01:26] <penguin42> there's not that much choice on the low power x86
[01:27] <popey> The T43 I got given this week turned out to work quite well with Ubuntu MATE 16.04 :)
[01:27] <popey> Not bad for a >10 year old computer
[01:28] <daftykins> yeah anything but netbooks really
[01:28] <daftykins> that sounds like a possible core 2 duo?
[01:28] <popey> i _think_ so
[01:28] <daftykins> sometimes i just think there are some folk who are enabling bad decisions too much in #ubuntu for claiming lubuntu will resurrect some of the museum pieces out there
[01:28] <popey> Pentium M 2.0GHz
[01:29] <popey> Was hilarious getting the factory XP install on it
[01:29] <daftykins> ah the M
[01:29] <daftykins> :D
[01:29] <popey> watching all the IBM nonsense self-install was fun
[01:29] <penguin42> popey: Did you have to pass the force PAE during the install?
[01:29] <popey> no
[01:29] <penguin42> interesting; we had to do that for someone with a mate install the other week
[01:30] <popey> not all pentium M' are equal?
[01:30] <daftykins> i seem to recall the lubuntu installs had to be picked at some point as they came with a forcepae config as default or some such
[01:30] <daftykins> yeah i think later ones may've changed something
[01:30] <popey> maybe it's default yeah, dunno
[01:30] <penguin42> popey: Apparently not, and I don't really understand why - some of them have PAE, some of them don't; and apparently some of them have it but say they dont
[01:30] <popey> it's a cracking little laptop
[01:30] <popey> We are a 5 Thinkpad household now
[01:31] <popey> the T43 was apparently the last one made under IBM name
[01:31] <popey> and has no windows key
[01:31] <penguin42> I tend to use my Model M keyboard that's similarly windows-key-less
[01:31] <popey> there's a wiki page I found with a list of niche features people look for in thinkpads, with the list of models that fulfil the requirements
[01:32] <daftykins> i use super too much to go without
[01:32] <popey> I do find it odd that my T450 shipped with all the VT stuff switched off in the BIOS
[01:34] <penguin42> yeh this day and age
[01:34] <daftykins> that's pretty common across all manufacturers, i once read a claim that it's because 'malware could take over your host OS and turn it into a VM, inserting programs you couldn't see running'
[01:34] <popey> ahh
[01:35] <daftykins> actually the gifted guy i mentioned earlier helped me patch the BIOS on a Sony TZ i have which doesn't have the VT option in its' BIOS and was disabled
[01:35] <popey> speaking of which, i should play with coreboot one day
[01:35] <daftykins> quick edit after showing him a copy of the NVRAM i think for him to oonfirm the options position and hey presto - KVM got enabled :>
[01:35] <popey> now i have machines that can use it
[01:35] <penguin42> yeh I've heard that idea of rootkitting like that (I can't remember the name someone came up with); I find it unlikely but hmm
[01:36] <penguin42> right, it's apparently now -0c out there; which is very annoying for mid April
[01:36] <daftykins> :O
[01:37] <popey> lots of LDing now
[01:37] <popey> feels close to the end
[01:40] <popey> maybe not :)
[01:40] <daftykins> i was surprised to see VT-d and VT-x were off on my new skylake build as default, too
[01:48] <popey> bah, gonna leave it running and sleep
[01:48] <popey> thanks for the help chaps
[01:48] <ball> I remember sleep.
[01:48] <penguin42> yeh sleep sounds a good plan
[01:53] <daftykins> and then they were gone
[01:57] <ball> daftykins: Any sign of your package yet?
[02:01] <daftykins> nah still stuck in Germany i think on the last update, lets see if anything else has changed
[02:02] <daftykins> i'm not sure how it'd make it here from there, probably via London
[02:08] <daftykins> amazon reckon Wednesday!
[02:08] <daftykins> still, i think waiting is the best part of new things :)
[02:08] <ball> That's why I still shoot on film. ;-)
[02:08] <daftykins> hehehe
[02:09] <ball> That and I can't afford a Pentax K3
[02:09] <ball> ...and it's nice to have at least one hobby that's not computerised.
[02:10] <daftykins> one of my clients is hugely into his cameras, constantly buying new models that once again rename the RAW file extension they use and needing yet another program to open them
[02:10] <daftykins> often has these quite fancy super compact Leica models with huge displays on the back
[02:11] <ball> Sounds dismal. How do his prints look though?
[02:11] <daftykins> full size SLRs too, often goes on about all the ISO # stuff to me
[02:11] <daftykins> well in the true modern style nothing ever gets printed :)
[02:11] <ball> I use Ilford 400 film. 400 is my ISO. ;-)
[02:11] <daftykins> just dumped to disk and maybe viewed on screen
[02:14] <ball> I suppose if you're taking photographs for Web sites or something that might be ok.
[02:14] <ball> ...or to email to distant relatives.
[02:14] <daftykins> which way would be ok?
[02:15] <daftykins> images should never be emailed :)
[02:15] <ball> daftykins: Why's that?
[02:15] <ball> Because they double in size when you attach them? ;-)
[02:16] <daftykins> wasn't designed for it, just bad netiquette as well
[02:16] <ball> daftykins: I understand but in practice very few people know or care.
[02:16] <daftykins> oh yeah, they need some education :>
[02:16] <ball> ...but you can email a link to a download.
[02:17] <daftykins> it's quite funny seeing a client getting links to picasa from a guy that's managing his property refurbishment down in Spain right now
[02:17] <daftykins> the links aren't working :D
[02:17] <daftykins> "this one works for me" the guy says, he showed me it and i had to point out that well, of course it will if you're logged in as the owner... :D
[02:19] <ball> I've never used Picasa
[02:19] <daftykins> i thought i'd read Google were shuttering it
[02:19] <daftykins> yeah... they are
[02:20] <daftykins> oh it's become the main Google Photos instead, ok
[02:22] <ball> Ah, I've used that one.
[02:23]  * ball thinks about buying a new hard disk drive
[02:24] <daftykins> out of space?
[03:25] <ball> daftykins: No, I'm getting disk errors from the one I installed.
[03:26] <ball> It /might/ be because the case wants it installed upside down or it might just be a crummy old disk drive.
[03:26] <ball> If I buy a 2.5" SATA disk I can mount it the right way up.
[03:26] <daftykins> checked the ol' SMART table with smartctl?
[03:27] <ball> Yes. Let me check it again now.
[03:27] <ball> I get green lights all the way down and 0 reallocated sectors.
[03:27] <ball> Temp is +27C
[03:28] <ball> Write error rate is 1805
[03:28] <ball> ...which is odd.
[03:28] <ball> power-on hours 12,798
[03:29] <ball> ...that's less than two years.
[03:29] <ball> Perhaps I just need new cables or it doesn't like being upside down.
[03:30] <daftykins> nothing for current, pending or remapped sectors?
[03:30] <ball> Current pending sector 539.
[03:30] <ball> Offline uncorrectable 160
[03:30] <daftykins> oh dear, she's toast
[03:30] <ball> 0 remapped.
[03:31] <daftykins> yip that one needs to go to the great electronic graveyard
[03:31] <ball> daftykins: Oh good. I'll wipe it and throw it away then.
[03:31] <ball> I have a 7200 RPM 2.5" 500G disk picked out.
[03:31] <ball> I suppose I could order that tomorrow.
[03:31] <ball> brb
[03:31] <daftykins> so small!
[03:32] <ball> daftykins: No real benefit to a 1.8" in this case ;-)
[03:34] <daftykins> hehe
[03:34] <daftykins> i actually have been given a Sony VAIO TT21 by a client for decommissioning, it contains a 1.2" SSD
[03:34] <ball> If I go with 2.5" Vs. 3.5", I can at least put the disk the right way up.
[03:35] <daftykins> i can't argue with that, i feel weird mounting drives in odd positions - a lot of Dells i've put in for folk have them sideways o0
[03:37] <ball> It used to be that the manufacturers had approved orientations: upright or on one side but not upside down or on end.
[03:37] <ball> ...I date back to MFM and RLL drives though so that may be old information.
[03:37] <daftykins> makes sense to me
[03:58] <ball> hello knightwise
[04:17] <ball> Goodnight everyone.
[08:41] <brobostigon> morning boys and girls.
[12:19] <ali1234> !isitoutyet
[12:19] <lubotu3`> No, it's not out yet!
[14:43] <popey> penguin42: that one line fix has stopped the flicker
[14:43] <popey> thank you
[14:44] <MartijnVdS> popey: which fix?
[14:44] <penguin42> popey: Wahey!
[14:44] <penguin42> popey: I'm an expert voodoo programmer
[14:45] <zmoylan-pi> !isitcompiledyet
[14:50] <popey> MartijnVdS: uh, train_set_valid = true; set to false
[14:50] <popey> rebuilt kernel, installed no blanking flicker
[14:51] <MartijnVdS> popey: ah :) For me the enable_fbc thing worked well enough (on last year's XPS 13 Developer edition)
[14:52] <popey> what kind of flickering were you getting
[14:52] <popey> I have two separate issues
[14:52] <popey> random black screen blanking periodically, fixed by above
[14:52] <popey> random flickering in chrome/chromium
[14:53] <penguin42> popey: Is the flicker something just within the drawing area or the screen as a whole?
[14:53] <zmoylan-pi> doesn't chrome have hidden options to change how it handles video display?
[14:53] <MartijnVdS> I had random full screen flickers, sort of "out of sync" for a fraction of a second
[14:53] <popey> penguin42: which one? :)
[14:53] <penguin42> popey: The chrome one
[14:53] <popey> MartijnVdS: yeah, same here
[14:53] <popey> penguin42: blocks of the screen
[14:53] <MartijnVdS> but since 4.4/4.5 it's fine for me with default settings
[14:53] <popey> like a tile here/there
[14:53] <popey> MartijnVdS: tried 4.6, still broken here
[14:53] <MartijnVdS> (Debian testing)
[14:53] <MartijnVdS> popey: which model do you have?
[14:53] <popey> T450
[14:54] <MartijnVdS> Ah not a Dell
[14:55] <MartijnVdS> There are so many weird small issues with new Intel chips lately
[14:55] <popey> yup
[14:55] <penguin42> MartijnVdS: popey needs to have a nipple to keep him happy
[14:55] <popey> :)
[14:55] <MartijnVdS> penguin42: xD
[14:56] <MartijnVdS> I really love my XPS
[14:58] <penguin42> the t450 also has 3 real pad buttons as well I think which is a big plus
[14:58] <MartijnVdS> I just use 1/2/3 finger taps
[14:58] <MartijnVdS> And I've disabled the touch screen too because .. dirty screen
[15:00] <penguin42> the other day I saw someone using a touchscreen in a text editor surprisingly effectively
[16:25] <awilkins> So : now snappy is a part of Wily : what should I use it for? Currently still using apt for most things.
[16:25] <awilkins> Well, everything AFAIA
[19:19] <popey> ali1234: did we find out what's new in the pi3?
[19:19] <ali1234> the pi zero? no
[19:19] <popey> er, new pi zero
[19:19] <popey> yeah
[19:19] <ali1234> two weeks
[19:19] <ali1234> new information: connectors won't move
[19:20] <zmoylan-pi> unless you have a hammer...
[19:55] <daftykins> hrmm my favourite choice kornbluth seems to be having issues today
[19:58] <diddledan> https://twitter.com/swiftonsecurity/status/721786968795820033
[20:00] <zmoylan-pi> still part of the path then they laugh at you, then you win... :-)
[20:01] <diddledan> https://twitter.com/swiftonsecurity/status/721790151026810880
[20:02] <daftykins> that clip is so apt XD
[20:03] <diddledan> you mean, git apply; ./configure; make; make install!
[20:03] <daftykins> what was it that xubuntu was doing for me on a laptop, something that really goes against the basic use of a portable machine
[20:03] <zmoylan-pi> it worked?


[14:05] <coolbhavi> hey cwayne dpm highvoltage :)
[14:05] <coolbhavi> hey mhall119
[14:06] <cwayne> mornin coolbhavi
[14:06] <coolbhavi> cwayne, morning! how has it been?
[14:19] <cwayne> coolbhavi: not too bad, how about you?
[14:19] <coolbhavi> cwayne, going on mate :) nothing special :)
[14:25] <cwayne> coolbhavi: :)
[14:25] <cwayne> coolbhavi: i sent another email to the python guys, hoping to hear a response today about the logo
[14:26] <coolbhavi> cwayne, no issues :) Just ping me on list and I'll have another look. The code and packaging is fine btw


[09:14] <lathiat> phlaegel: you can get dbus to reload its configs, if thats what your concerned about
[09:14] <daniels> or just don't use unclutter at al
[09:14] <elmo> Kamion: I'm not
[09:14] <elmo> just 'unclutter'
[09:15] <Kamion> huh, the source seems to say it won't XGrabPointer() unless -grab
[09:15] <daniels> OH MY GOD
[09:15] <phlaegel> lathiat: I just don't want to see linux become reboot-happy. I don't like rebooting my desktop :-)
[09:15] <daniels> THIS IS A HORROR SHOW
[09:15] <daniels>                      * send a pseudo EnterNotify event to the parent window
[09:15] <daniels>                      * to try to convince application that we didnt really leave it
[09:16] <daniels> what could POSSIBLY go wrong
why's that so bad?
[09:17] <ogra> lets just morguify unclutter, who uses that anyway :P
[09:18] <daniels> so the alternative to using the grab method, is to have it create a tiny little window under the cursor
[09:18] <daniels> then it sends an event to the parent window and says 'hey, know how you lost focus to me?  it's all yours again!'
[09:19] <daniels> and does this awful event-mangling
[09:20] <elmo> ogra: the whole GSS situation's made so much more fun by comments like that, FYI
[09:21] <lathiat> gss?
[09:21] <daniels> elmo: seriously though, unclutter is completely pathological
[09:21] <daniels> elmo: -grab may actually be *better*
[09:21] <daniels> lathiat: gnome-screen-saver
[09:21] <Kamion> ogra: (what's wrong with the word "remove", anyway?)
[09:21] <lathiat> ah
[09:21] <ogra> elmo, belive me i get thrown cluebats after me all the day, no matter where i go...
[09:22] <ogra> Kamion, it just doesnt sound that cool with geran accent :)
[09:22] <ogra> *german
[09:23] <elmo> well -noevents does "fix" it
[09:23] <daniels> elmo: -root could also be vastly less shit
[09:24] <daniels> elmo: noevents> right, that's the pathological branch I was talking about
[09:24] <elmo> yeah, sorry I know I'm being dense, but I'm not clear on why it's pathological to send the fake event?
[09:24] <elmo> and why it's only GSS that gets upset
[09:25] <elmo> I mean, seriously, this code hasn't been modified since before some of you were born
[09:25] <elmo> (well, okay, not quite, but close)
[09:25] <daniels> eh, at the time, my workstation was running NT 4 Server with MSSQL and IIS
[09:25] <bddebian> w00t
[09:25] <ogra> elmo, xss lock screen was 15 years untouched when i started working on it...
[09:25] <daniels> so GSS could be more robust in handling this particular behaviour
[09:25] <daniels> but it's ... it's not something anyone should ever attempt to do
[09:26] <daniels> you know how you see people driving roofing nails through their testicles?
[09:26] <daniels> and they're all like 'don't try this at home, kids'
[09:26] <Kamion> not personally, no
[09:26] <daniels> this is that
[09:26] <bddebian> hahaha
[09:26] <daniels> Kamion: you need more bmevideo.com in your life
[09:26] <daniels> (MASSIVELY NSFW.)
[09:26] <daniels> if I could figlet NSFW, I would.  i don't think I can quite stress the point enough.
[09:26] <daniels> also, not safe for just-had-lunch
[09:27] <lathiat> "not safe at all"? ;)
[09:29] <Keybuk> what's worrying is that daniels probably has an account at that site
[09:30] <lathiat> daniels is a continual source of amusement
[09:30] <Keybuk> I'd go for "worry"
[09:30] <lathiat> Well either way amusement still stands
[09:30] <daniels> what's worrying is that you all went and looked
[09:30] <ogra> Keybuk, depends if as user or as committer...
[09:30] <ivoks> argh...
[09:30] <lathiat> daniels: no whats more worrying is that i already knew what it was
[09:31] <ivoks> gnome-screensaver is really broken
[09:31] <Keybuk> daniels: *shrug* nothing on there shocks me
[09:31] <Keybuk> I've seen worse from my friends <g>
[09:31] <lathiat> *by* your friends or *from* your friends
[09:32] <lathiat> the internet is a wonderous place
[09:32] <Keybuk> both
[09:34] <tseng> Robot101: ref me baby one more time
[09:34] <tseng> Robot101: PASS THE PIPE
[09:37] <Robot101> tseng: >:)
[09:41] <bddebian> Pipe?  Who's got the pipe?
[09:44] <sivang> Robot101: any new stuff on the design you showed me that other day? (re: clientlib etc)
[09:48] <tritium> Kamion, is there still a yaboot/os-prober problem in current daily install images?
[09:49] <Kamion> tritium: yes; the kernel issue that's blocking me fixing that is being fixed now
[09:49] <tritium> Kamion, oh, sounds close to resolution?
[09:49] <Kamion> tritium: well, the current images don't hang, at least, if that's what you're asking, but they don't detect OS X
[09:49] <Kamion> yes
[09:49] <Kamion> if you don't have OS X, current images should work fine for you
[09:49] <tritium> Great, thanks for the info.  I'll be glad to test on G5 iMac soon
[09:50] <tritium> I still do have OS X
[09:55] <Robot101> sivang: python prototype has got channel support now
[09:55] <sivang> Robot101: channel?
[09:56] <Robot101> sivang: our abstraction for all different services over IM/VOIP connections
[09:56] <sivang> Robot101: ah cool, you have it online somewhere?
[09:56] <Robot101> textchannel specifically
[09:56] <Robot101> floopily.org/darcs/ipcf-python
[09:59] <mdz> tech board meeting in #ubuntu-meeting
[10:06] <paines> hi
[10:07] <jdub> heh. lock dialogue in swap.
[10:08] <\sh> bmonty_laptop: ping ubuntu-meeting fast
[10:08] <kikidonk> hi there !
[10:08] <kikidonk> i'm planning to do an install party for the upcoming breezy version
[10:08] <jdub> rad!
[10:08] <kikidonk> but i was wondering, does the breezy install cd come with a way to repartition windows disks ?
[10:09] <jdub> yes
[10:09] <kikidonk> read: most likely ntfs stuff
[10:09] <paines> cedega stopped working with breezy pre install. i think due to nptl missing in glibc. is that possible ?
[10:09] <kikidonk> rad!
[10:09] <kikidonk> in the install process ?
[10:09] <jdub> yes
[10:09] <kikidonk> that rock
[10:09] <kikidonk> thanks :)
[10:09] <Robot101> kikidonk: it did in hoary :)
[10:10] <kikidonk> i didn't look to be honest
[10:10] <kikidonk> but it's very nice
[10:10] <Robot101> kikidonk: choose the ntfs partition off the partition manager menu, then you can choose a new size
[10:10] <kikidonk> cause i'm going to convert windows users of course, and they will very likely have a windows-only disk which must be resized to make room for linux
[10:10] <Robot101> it lacks feedback, but you can see parted's output on Alt+F3
[10:11] <kikidonk> cool
[10:11] <Robot101> I dunno if breezy added a progress bar for that
[10:11] <kikidonk> i can do without, a longs as it's happening under the hood
[10:19] <shackan> kikidonk, weren't you a gentoo guy ? :)
[10:22] <kikidonk> yes
[10:22] <kikidonk> but gentoo is broken
[10:22] <torkel> mjg59: ping?
[10:23] <Kamion> Robot101: no
[10:23] <Kamion> (sorry)
[10:23] <mjg59> torkel: Hi
[10:23] <torkel> mjg59: hi
[10:25] <mjg59> torkel: What's up?
[10:25] <torkel> mjg59: re #15582. It works for me with 0.34 if I change user=`finger| grep -m1 ":0" | awk '{print $1}'`
[10:25] <torkel> to user=`finger| grep -m1 ":0 " | awk '{print $1}'`
[10:25] <torkel> in getXuser
[10:25] <torkel> otherwise it matches root
[10:25] <mjg59> Ok
[10:25] <mjg59> Please file a bug
[10:26] <torkel> mjg59: ok. I do a followup
[10:26] <daniels> screw that
[10:26] <ogra> mjg59, did you follow the meeting decision for g-s-s ?
[10:26] <daniels> just search the server's memory space looking for MIT-MAGIC-COOKIE (or XDM-AUTHORIZATION-1 or whatever), get the auth key
[10:27] <mjg59> ogra: No
[10:27] <daniels> then search everyone's home directory looking for that key in .Xauthority
[10:27] <ogra> mjg59, seems we switch back
[10:27] <mjg59> ogra: Right.
[10:27] <ogra> :)
[10:28] <daniels> mjg59: back me up here
[10:28] <torkel> would be nice if acpi-support works with g-s-s anyway...
[10:28] <mjg59> torkel: REWAREWAFDS:OIUREWAFDSAREAREWAFDREW
[10:28] <ogra> that was loud
[10:28] <mjg59> (ahem)
[10:28] <torkel> daniels: it's not about Xauth, it's about dbus
[10:29] <daniels> torkel: if getXuser is wrong, then it's about xauth
[10:29] <daniels> my solution is simultaneously more foolproof and more elegant
[10:30] <torkel> mjg59: huh?
[10:30] <daniels> alternately, we could write a small script to gdb into the server, break on the first line of WaitForSomething or something equally well-known, and use that to drill down into the auth structures.
[10:30] <daniels> saves brute-forcing the memory space with strstr()
[10:31] <Kamion> mjg59,ogra: we switch back providing sabdfl accepts the TB's consensus
[10:31] <Kamion> which is not the same as "seems we switch back"
[10:31] <ogra> yes
[10:31] <torkel> daniels: no. becasue the only way to speek to g-s-s is through dbus, so you have to find DBUS_SESSION_BUS_ADDRESS, which getXuser does in 0.34
[10:31] <mjg59> torkel: Currently I wish every screensaver to die
[10:31] <mjg59> I would quite happily have acpi-support conflict with every one of them
[10:31] <ogra> Kamion, thus the careful "seems" in front
[10:31] <daniels> torkel: okay, so you didn't mean what you said about needing to change the line so it didn't match root
[10:31] <mjg59> When there's a decision, I'll fix xscreensaver support
[10:32] <mjg59> daniels: No, it does mean that
[10:32] <spayne> i got realplayer from marillat
[10:32] <daniels> spayne: bad idea
[10:32] <spayne> wrong channel :-)
[10:32] <mjg59> We need to find out which user owns the X session so we can find his gnome-session and then find the DBUS_SESSION_BUS_ADDRESS variable in /proc
[10:32] <spayne> what could you suggest daniels
[10:32] <torkel> mjg59: I can understand that. They are a mess...
[10:32] <daniels> mjg59: right
[10:32] <daniels> spayne: *shrug*
[10:33] <daniels> mjg59: hence my suggestion of gdb'ing the X server with a small script that prints out the currently active auth keys
[10:33] <daniels> mjg59: and looks through everyone's Xauthorities looking for that key
[10:33] <spayne> it is out of hoary extras
[10:33] <spayne> daniels: it is out of hoary extras
[10:34] <lathiat> spayne: that has nothing to do with us
[10:34] <spayne> i know
[10:34] <spayne> sigh
[10:34] <lathiat> it seems approximately 3000x less hackish
[10:34] <lathiat> any reason we are not doing that?
[10:40] <Riddell> seb128: would it be possible to separate libgstgdkpixbuf.so from the rest of gstreamer0.8-misc, is adds a lot of depends
[10:41] <seb128> Riddell: I don't want to divert from Debian
[10:41] <seb128> Riddell: I'll ping the Debian maintainer
[10:42] <Riddell> seb128: can you CC please if it's e-mail
[10:42] <seb128> nop, that's IRC
[10:43] <seb128> is that the only file of this package to be an issue?
[10:45] <pkern> Any clue what happens when lilo fails to install with LVM as root partition like that? "lookup_dev: number=FD00" "device-mapper ioctl cmd 12 failed: No such device or address" "Fatal: device-mapper: dm_task_run(DM_DEVICE_TABLE) failed"
[10:46] <mdz> Kamion: I've updated the seeds; please push an update to ~cjwatson and roll new metapackages
[10:47] <Riddell> seb128: seems to be just that file yes
[10:47] <pkern> Mailinglist suggests a problem in udev |:
[10:47] <mdz> Kamion: else I'll do it after lunch, but sooner is better
[10:49] <jlj> simple C# command line audio player: http://nanocrew.net/2005/09/20/snd123/
[10:50] <shackan> wow, john lech johansen :)
[10:51] <jlj> :-)
[10:52] <shackan> uhm wait, 12 megs of source code for a 'simple command line audio player' ?
[10:52] <dholbach> shackan: maybe it has some .oggs to test it with ;)
[10:53] <jlj> the command line interface source code is 1488 bytes, the rest is codecs :-)
[10:53] <jlj> all the supported codecs are included, there are no external deps besides mono and libesd
[10:55] <ogra> jlj, what kind of codecs does it support ?
[10:55] <jlj> MP2, MP3, AAC, Ogg Vorbis, Speex, FLAC, Apple Lossless, AC3, CDDA, WMA 1 and 2. MOD formats: MOD, XM, IT, S3M, 669, MTM, STM.
[10:56] <mjg59> jlj: What license is this under?
[10:57] <jlj> mjg59: GPL
[10:58] <shackan> seems something which would look pretty good with some frontend
[10:58] <ogra> jlj, how does that work with included proprietary codecs ?
[10:59] <jlj> proprietary? all the decoders are open source, most of the GPL'ed
[11:00] <jlj> *them
[11:00] <ogra> MP3 is patented and you have to pay for it
[11:00] <ogra> i think AAC is nonfree either
[11:00] <jlj> proprietary != patented
[11:00] <ogra> yes, sorry, wrong term
[11:00] <jlj> Ubunu ships libmad in main
[11:00] <mjr> correct; patented is a form of proprietary
[11:00] <jlj> err, Ubuntu
[11:01] <jdub> jlj: (which is an error that we'll be fixing before breezy goes out... finally...)
[11:01] <ogra> jdub, :)
[11:02] <shackan> jdub, so it'll be in universe ?
[11:02] <jdub> yes
[11:03] <shackan> will it come on the cd ?
[11:03] <ogra> universe ?
[11:03] <ogra> nope
[11:04] <shackan> people using the live cd won't be able to play their music, that's bad :(
[11:05] <Keybuk> sure they can
[11:05] <Keybuk> they can apt-get install the codec to play it
[11:05] <shackan> yes but it's not the same thing
[11:06] <Keybuk> no different than people using the install cd though
[11:07] <ogra> shackan, there was never a mp3 supporting player on the live CD you always had to install the codec
[11:07] <Keybuk> we can't put the codecs in main because people in suits will take all our money away and put jdub in jail
[11:07] <jdub> with elmo
[11:07] <Keybuk> and he refuses to be elmo's bitch
[11:07] <jdub> *REFUSE*
[11:07] <jdub> watch me
[11:07] <shackan> hahaha
[11:08] <shackan> why did elmo go to jail ? :D
[11:08] <jdub> he hasn't yet
[11:08] <jdub> but you are suggesting he should
[11:08] <shackan> !
[11:08] <jdub> YOU WOULD PUT ELMO IN JAIL FOR A LITTLE MUSIC?
[11:10] <shackan> argh, what have I done!
[11:19] <sivang> Keybuk: LOLOL
[11:23] <dholbach> good night everybody, i'll see you tomorrow
[11:30] <mdz> Keybuk: I reproduced the mice bug
[11:30] <mdz> Keybuk: with uber debugging enabled
[11:30] <Keybuk> oooh, how reproducible?
[11:30] <mdz> oh, not at all
[11:30] <mdz> just happened once
[11:31] <Keybuk> send your syslog :p
[11:31] <mdz> but I had that extra udev logging of yours enabled, if that helps
[11:31] <Keybuk> though I doubt it'll be interesting because I forgot to ask you to move syslog earlier into the boot sequence <g
[11:31] <mdz> Keybuk: sent
[11:32] <\sh> who is<EMAIL_ADDRESS>
[11:32] <mdz> Keybuk: how much earlier?
[11:32] <mdz> \sh: Diziet
[11:32] <\sh> AH OK
[11:32] <\sh> grmpf...caps lock
[11:32] <mdz> heh
[11:32] <Keybuk> mdz: from rc2.d/S20 to rcS.d/S20
[11:32] <sivang> does anybody know how I can use my ubuntu.com email addres now being an approved memeber in launchpad having signed the CoC ?
[11:33] <\sh> small keyboards...
[11:33] <\sh><EMAIL_ADDRESS>have to wait until the cron job rund
[11:33] <\sh> -d+s
[11:33] <elmo> sivang: it should work already
[11:33] <mdz> Keybuk: it's at rc2.d/S10 right now
[11:33] <mdz> anyhow, moved
[11:33] <mdz> I'll do some more rebooting
[11:34] <Kamion> mdz: sorry, I was away having my evening ;-)
[11:34] <Keybuk> right, but needs to be rcS.d so it's before /etc/modules is processed
[11:34] <Kamion> mdz: and I'm off to bed now
[11:34] <mdz> Kamion: night
[11:34] <Kamion> I imagine the seed mirrors have updated by now
[11:34] <\sh> how do i get a working pdf now from a ps output of firefox..
[11:34] <mdz> Kamion: yeah, I uploaded -meta already
[11:34] <Kamion> ok
[11:34] <\sh> ps2pdf doesn't work
[11:35] <mdz> \sh: that works for most pages
[11:35] <mdz> though not all
[11:35] <\sh> mdz: but not bugzilla printer formatted pages
[11:35] <mdz> Keybuk: it doesn't look very enlightening
[11:35] <\sh> mdz: #15916
[11:36] <\sh> mdz: and it's confusing, because in evolution e.g. u have the possibilty to print directly to pdf
[11:36] <\sh> next to .ps
[11:36] <ogra> mdz, eek
[11:36] <ogra> mdz, removed xscreensaver-data ?
[11:37] <mirak> honestly, does anyone manage to build packages with apt-build ?
[11:37] <mdz> ogra: xscreensaver depends: xscreensaver-data
[11:37] <mdz> ogra: or if it doesn't, I'd consider that a bug...
[11:37] <mdz> I just put it back the way it was before
[11:38] <ogra> i does phew
[11:38] <ogra> soryy
[11:38] <mirak> just wondering
[11:38] <mirak> does apt-build is adapated to ubuntu or not ?
[11:38] <mirak> I mean does the package management and naming in ubuntu can be a problem for apt-build ?
[11:38] <\sh> ok..going to bed...
[11:38] <\sh> good night gentlemen
[11:38] <bddebian> Later \sh
[11:39] <sivang> elmo: should it be like my irc name registered in launchapd? or what account does it use?
[11:39] <ogra> night \sh
[11:39] <elmo> sivang: what \sh said
[11:39] <Keybuk> mdz: were the devices missing after the boot, or after the suspend/resume ?
[11:41] <mdz> Keybuk: after the boot
[11:41] <mdz> it may even have been the next-to-last boot actually
[11:42] <tseng> mdz: bwar @ 6108
[11:42] <tseng> mdz: i was about to give into you being a seperate bug, too.
[11:42] <Keybuk> yeah there's not much there other than confirmation of the pattern of failure
[11:42] <Keybuk> moving syslog to /etc/rcS.d/S20sysklogd would help for next time
[11:42] <sivang> mdz: email sent, hope it's ok
[11:43] <mdz> Keybuk: ok, just got it again
[11:43] <mdz> Keybuk: was trying to replicate the conditions
[11:43] <mdz> it was a boot-instead-of-resume after hibernating, so the filesystem was unclean etc.
[11:43] <mdz> it just happened to be after a reboot -f into single-user
[11:44] <mdz> which is what I did befor etoo
[11:44] <Keybuk> wow, that was quick ;)
[11:44] <Keybuk> randomly, you don't have a /dev/input/mice, but do have mousedev loaded?
[11:44] <Keybuk> do you have a /dev/psaux ?
[11:45] <mdz> Keybuk: sent new syslog
[11:45] <mdz> and have the system in the broken state
[11:45] <mdz> I am missing psaux as well, yes
[11:45] <mdz> mousedev and psmouse are both loaded
[11:46] <Keybuk> what is in /dev/input ?
[11:46] <mdz> event[0-3] , mouse[01] , ts[01]
[11:46] <Keybuk> and in /sys/class/input ?
[11:46] <mdz> same, but also with mice
[11:47] <Keybuk> and cat /sys/class/input/mice/dev ?
[11:47] <mdz> 13:63
[11:48] <mdz> OUCH
[11:48] <mdz> I thought it would be clever of me to tar up sysfs for further examination
[11:48] <Keybuk> can you confirm that there's _not_ a /dev/.udevdb/class@input@mice file?
[11:48] <mdz> that causes a nice kernel panic
[11:48] <Keybuk> yeah, uh, don't do that
[11:48] <mdz> no, I cannot confirm that
[11:49] <Keybuk> kernel gets upset if you try and tar up its core state
[11:49] <mdz> I killed it
[11:49] <Keybuk> there's the memory maps of modules and shit in there (/sys/module/*/sections/*)
[11:49] <dieman> hah
[11:49] <dieman> nice
[11:49] <mdz> I'd done that before without ill effects
[11:50] <mdz> not for a while though
[11:50] <Keybuk> it's at that kind of point I like to say "BENC!"
[11:51] <mdz> Keybuk: has anyone checked to see if it's present in the initramfs /dev?
[11:51] <Keybuk> mdz: the /dev is moved over these days, isn't it?
[11:51] <mdz> Keybuk: yes
[11:52] <Keybuk> if you gunzip|cpio -t your initrd.img, you shouldn't find mousedev in it
[11:52] <mdz> I meant the "live" initramfs
[11:52] <mdz> where udevstart has been run
[11:52] <Keybuk> nope, didn't realise that you could still access that
[11:53] <mdz> Keybuk: passing 'break' as a kernel parameter should give you a shell at precisely the right place
[11:54] <Keybuk> interesting, worth a try
[11:54] <mdz> ok, it's not there
[11:54] <mdz> oh, mousedev isn't loaded there either
[11:55] <mdz> only hci, storage and core
[11:55] <mdz> nothing in /sys/class/input at all in initramfs
[11:55] <Keybuk> yeah
[11:55] <mdz> so by all indications rcS.d/S04udev sucks
[11:55] <Keybuk> it shouldn't even be possible for those kernel modules to end up in your initramfs image, so if they got loaded there, strange things would be afoot
[11:56] <Keybuk> actually, I don't think it's S:S04udev at all
[11:56] <Keybuk> that's just supposed to copy over the initramfs /dev and fix it up
[11:56] <mdz> should be plenty possible, by adding mousedev to mkinitramfs/modules
[11:56] <Keybuk> it's when the first udevsend event occurs as a result of S:S20modules-init-tools that we have problems
[11:56] <mdz> Keybuk: it doesn't copy it; initramfs does a mount -o move
[11:56] <mdz> and then S04udev is supposed to just run udevstart
[11:56] <Keybuk> right
[11:57] <Keybuk> the second udevstart should just return having done nothing, and acts as a safety measure
[11:58] <mdz> ah, right, so mice should be created by a hotplug/udevsend event
[11:58] <mdz> as with all other random udev races, the obvious solution is to run udevstart in more places :-P
[11:58] <Keybuk> just in case anything turned up in between initramfs and userspace
[11:58] <Keybuk> Sep 20 14:42:53 (none) udev[5460] : udev.c: action, subsystem or devpath missing
[11:58] <Keybuk> SCORE!
[11:59] <mdz> oooh
[11:59] <mdz> is that udevd or kernel's fault?
[12:00] <Keybuk> the kernel's input subsystem doesn't do hotplug properly
[12:00] <Keybuk> it's a known bug


[17:11] <waldo323> good afternoon
[17:12] <waldo323> trying to reproduce a failure but so far I keep failing at reproducing it...
[17:15] <cmaloney> So is that a success then?
[17:15] <cmaloney> not(not(failure))
[17:26] <waldo323> maybe?
[17:54] <cmaloney> ;)
[22:14] <jrwren> We need a python linux application developer.
[22:14] <jrwren> https://vivint.wd5.myworkdayjobs.com/en-US/vivintjobs/job/Lehi-Innovation-Center/Application-Developer_R106663
[22:14] <jrwren> Let me know if you apply so I can fast track it :)
[22:17] <cmaloney> That's in Boston
[22:17] <cmaloney> (in case anyone is wondering where it is located. ;) )
[22:25] <jrwren> it could be at your home.
[22:27] <greg-g> remotie for the win
[23:40] <cmaloney> jrwren: Is it remote?


[19:40] <yannick> hi, I added a test case for ekiga here: https://wiki.ubuntu.com/Testing/Cases/UbuntuDesktop


[00:40] <hazmat> smoser, is there some trick needed to get cloud-init in a seeded nocloud mode to execute all the handlers.. i'm passing in cloud-init file.. and it seems to short circuit without executing any of the package or runcmds.. http://pastebin.ubuntu.com/918245/
[01:31] <hazmat> it only seems to run the cloud_init_modules, not the cloud_config_modules


[02:04] <callmepk> good morning
[02:27] <jamesh> hi callmepk
[02:27] <callmepk> hi jamesh
[05:18] <didrocks> good morning
[05:39] <duflu> Hi didrocks, and callmepk and jamesh
[05:45] <didrocks> hey duflu
[06:11] <oSoMoN> good morning desktoppers
[06:18] <didrocks> salut oSoMoN
[06:20] <marcustomlinson> top o the mornin desktoppers
[06:22]  * didrocks tries to find something funny to answer, but no inspiration yet, so good marcustomlinson morning, a coffee I need
[06:23] <marcustomlinson> I think the official response to that in Ireland is "and the rest of the day to you"
[06:24] <marcustomlinson> but that's only about a 4.1 on the funny scale
[06:24] <marcustomlinson> also, hey didrocks
[06:26] <didrocks> marcustomlinson: depends on your funny scale limit, is it 5 - 10 - 20?
[06:27] <oSoMoN> salut didrocks
[06:27] <didrocks> (4.1 seems insanely accurate btw :p I’m waiting for the 2 digits precision)
[06:27] <oSoMoN> mornin' marcustomlinson
[06:28] <marcustomlinson> it's a scale of 1.3 to Z
[06:28] <didrocks> so… supposively, I finally have an electric meter in the new house! I should be wired to the electric circuit this afternoon \o/
[06:29] <marcustomlinson> hey oSoMoN
[06:30] <marcustomlinson> didrocks: https://youtu.be/j1BNcSBApOU
[06:32] <didrocks> marcustomlinson: I will be in that state of mind once connected to the wired phone grid. This will take between 3 and 6 months apparently
[06:33] <oSoMoN> that long?
[06:33] <didrocks> …and, to get fiber, you need the wired phone cable, ofc, no procedure without it
[06:33] <didrocks> oSoMoN: monopole orange
[06:33] <didrocks> took already 3 months to instruct the deposit pieces
[06:33] <oSoMoN> man, that's even worse than where I live
[06:33] <didrocks> just to say that everything is there
[06:33] <didrocks> (and you need to take photos of *their* infrastructure
[06:34] <didrocks> like the number written on the phone infrastructure, where they are located, and so on
[06:35] <didrocks> (and for all that service or rather non service, you still pay 100€ to instruct your demand)
[06:35] <oSoMoN> sigh
[06:35] <didrocks> oSoMoN: is it better in spain?
[06:35] <didrocks> or still a nightmare, but slightly better?
[06:36] <oSoMoN> I was lucky that fiber was already in my street, but it took me 3 months to convince the phone company to wire my house
[06:37] <didrocks> but no need for phone cable at least?
[06:37] <oSoMoN> (and numerous phone calls)
[06:37] <oSoMoN> no, in the meantime they provided a 4G router
[06:37] <didrocks> I’m looking for a 4G modem for the interim period, because you can’t subscribe to a 4G box by one the operator, as the neighbours have fibers, even if the address is unknown… it’s a kind of a dead loop
[06:37] <didrocks> waow, way better service than here
[06:38] <oSoMoN> so, not a great experience overall, but could've been worse
[06:39] <didrocks> yeah, could be in France :)
[06:39] <didrocks> but really “ you can’t subscribe to a 4G box ” and “ you are not connected yet ” (even by Orange) is … ok, I will buy a 4G modem/router myself and a 4G phone line
[06:53] <duflu> Morning oSoMoN and marcustomlinson
[06:53] <marcustomlinson> yo duflu
[07:38] <callmepk> Hi duflu didrocks marcustomlinson oSoMoN
[07:38] <didrocks> hey callmepk!
[07:38] <marcustomlinson> hi callmepk
[07:49] <seb128> goood morning desktopers
[07:50] <seb128> hey callmepk marcustomlinson oSoMoN
[07:50] <callmepk> hi seb128
[07:53] <marcustomlinson> hey seb128
[08:03] <Laney> |o/
[08:04] <duflu>    \o|
[08:09] <duflu> (o_
[08:11] <didrocks999> /o/
[08:12] <Laney> ~~~\o/ - - - ¬_o/
[08:12] <duflu> Very graphic
[09:12] <thumper>  /o\
[09:41] <oerheks> ~~~~/\~~~~~\o/~~~~~
[10:36] <ricotz> oSoMoN, hey, applied the search-engine changes to ff80, seems fine so far :)
[10:36] <ricotz> hello desktopers!
[10:43] <Laney> moin ricotz
[11:09] <seb128> hey ricotz!
[11:18] <oSoMoN> hey ricotz, thanks!
[11:29] <ricotz> hey Laney seb128 oSoMoN
[13:15] <ricotz> oSoMoN, hmm, nodejs still in groovy-proposed
[13:15] <oSoMoN> ricotz, yes, there are still a bunch of reverse deps that need fixing, I've been working on them on and off, need to resume that
[13:16] <ricotz> oSoMoN, ah ok, thought there is just some formality missing, thanks
[13:16] <oSoMoN> ricotz, https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#nodejs if you're interested in what's blocking
[13:17] <Laney> what did I do wrong in a past life
[13:17] <Laney> to have to be working on an autotools build system again
[13:18] <ricotz> oSoMoN, oh dear
[13:18] <oSoMoN> Laney, you must have been very naughty
[13:19] <oSoMoN> ricotz, that list was more than twice as long at the beginning, so there's been progress…
[13:20] <ricotz> oSoMoN, I see
[15:36] <GunnarHj> Good afternoon all!
[15:36] <GunnarHj> Question to anybody who knows: Is the XDG_CURRENT_DESKOP value for respective flavor documented somewhere? I know I can find out by running live sessions, but would prefer to not do that if possible.
[23:34] <guiverc> intruder alert:  http://cdimage.ubuntu.com/daily-live/current/ still shows 8-July-2020 as latest amd64; shouldn't this be fixed? for those of us not using web & have really dumb scripts