[03:15] <ahoneybun> hey guys and gals I'm having a problem logging into the wiki: http://pastebin.ubuntu.com/10601070/
[03:30] <dobey> ahoneybun: was a little slow for me, but worked fine here just now. i think you also want #canonical-isd for help with that sort of issue
[03:53] <Nikhil> Heya everyone
[03:54] <Nikhil> can anyone tell me in which programming language should I learn to develop software for ubuntu
[03:57] <sarnold> Nikhil: depends what you want to do..
[03:58] <Nikhil> I want to develop GUI stuff in ubuntu
[04:00] <Nikhil> any idea of programming language, I know C++ presently
[04:13] <ScottK> Nikhil: Learning Qt5 (which is built on C++ would be a good start then).
[04:17] <Nikhil> ok, ScottK. What are the libraries that include ubuntu os
[04:19] <ScottK> If you're on an Ubuntu system, you can try the command "apt-cache show unity8" and that will show you the different libraries that the Ubuntu GUI depends on (in the Depends section).
[04:31] <Nikhil> ScottK: Are they already installed in the system?
[04:34] <ScottK> Not all the headers are.  If you do "sudo apt-get build-dep unity8" that will install the headers and anything else needed to build the package.
[04:35] <Nikhil> ok thank you ScottK
[08:24] <ginggs> Hi, do I need a FFe to fix a FTBFS that will bring a new version out of proposed? https://launchpad.net/ubuntu/+source/abyss
[08:28] <darkxst> ginggs, that seems a bit extreme, why not just cherry-pick the patch that fixes the FTBS?
[08:29] <ginggs> darkxst: the new version has been sitting in proposed for some time. it couldn't migrate because of the FTBFS
[08:29] <infinity> ginggs: Nothing wrong with fixing the version in proposed, no.
[08:30] <infinity> ginggs: If there were too many negatives in that sentence, go for it.  Fix that FTBFS.  Woo!
[08:30] <ginggs> infinity: thanks
[09:21] <darkxst> infinity I having way to much fun trying to inject import hooks into gdb for the auto-load scripts, probably mis-read the original question!
[09:25] <darkxst> it aint working though, guess I might need to patch gdb
[15:52] <zyga> xnox: hey, ubuntu-drivers looks pretty neat!
[15:53] <zyga> xnox: I have a question about intel microcode
[15:53] <zyga> xnox: what are the consequences of enabling that?
[16:23] <kunal21> hiii everyone .... please help me.... I just want to know how to package a phython app developed using QUICKLY toolkit on Ubuntu 14.04LTS
[16:25] <kunal21> #debian-python     hiii everyone .... please help me.... I just want to know how to package a phython app developed using QUICKLY toolkit on Ubuntu 14.04LTS
[20:40] <melodie> hi
[21:26] <infinity> zyga: The consequence of installing intel (or amd) microcode is that your CPU's microcode is hotpatched at boot to the latest upstream version.  This is all scary black box binary blob nonsense, but so is your CPU to start with, so it's not really making the situation worse. :P
[21:27] <infinity> zyga: Intel and AMD regularly update said black boxes for bugs, security issues, etc.  Sadly, they rarely tell us WHY they're updating them, so you don't get to make much of an informed decision, just "update" or "don't update".
[21:28] <infinity> zyga: All that negativity aside, if you own such a CPU, it's probably saner to use the updates than not, even given all the caveats.
[21:32] <infinity> zyga: Be warned, though, that because it's a black box, we can't in any way guarantee it does sane thing.  Like the Intel update last year that disabled an entire instruction due to it being buggy, which led to us having to SRU glibc so it wouldn't crash trying to use it.
[21:32] <infinity> s/sane thing/sane things/
[21:51] <melodie> infinity what means "to SRU" please?
[21:58] <infinity> melodie: SRU == stable release update.  As in, we had to push a new glibc to old stable releases to cope with intel-microcode breaking the world.
[21:59] <zyga> infinity: thanks for explaining that, I was hoping there would be more transparency but I guess this is as good as it gets
[21:59] <zyga> infinity: TXT fiasco, yeah I remember that
[22:00] <zyga> melodie: stable release update
[22:00] <melodie> infinity ok thank you
[22:00] <zyga> melodie: it's a process where we release something to all the supported releases
[22:00] <melodie> zyga thanks
[22:00] <zyga> melodie: https://wiki.ubuntu.com/StableReleaseUpdates
[22:01] <melodie> reading
[22:04] <melodie> infinity so it was not possible to do it reverse side, as downgrading the intel microcode firmware (is it a version available in the repositories?)
[22:05] <infinity> melodie: We could have downgraded it in the distro (and did until the glibc updates happened), but that doesn't prevent people from using the upstream microcode directly.
[22:07] <melodie> infinity this is what I feared, always the same problem with non free code. :-(
[22:07] <infinity> zyga: TSX, not TXT, but yes.
[22:10] <infinity> melodie: To be (sort of) fair, Intel doesn't make a habit of breaking ABI in their own CPUs.  But this was the exceptional case that goes to demonstrate how scary microcode updates can be.
[22:11] <melodie> infinity has anyone from the Ubuntu/Canonical teams got in touch with them when this happened?
[22:12] <melodie> even non free codes could get a bug report once a while, especially when microcodes for the most currently used cpus are involved
[22:15] <zyga> infinity: transactional memory? IIRC that was TXT (or was that trusted execution again)
[23:37] <melodie> where exactly is setup the method allowing to get the default configuration files in the home's new user created? It's not in /etc/skel although this is what is written in /etc/adduser.conf, is it possible that it's in the sources of each desktop's session manager? (such as lxsession, gnome-session and so on?)
[23:57] <melodie> diving in all the configuration files didn't help, and neither did googling