[21:43] <IgorKaminski> hello
[21:45] <IgorKaminski> Has anyone tried Ubuntu for Android? How accessible is it?
[22:03] <AlanBell> IgorKaminski: nobody outside Canonical has tried it at all


 When booting after the splash im stuck at a black background with mouse cursor and nothing else
[01:20] <aaron1234> Tried deleting my users kde folder
[01:21] <ahoneybun> aaron1234: ctrl + alt + f2
[01:21] <ahoneybun> and type sudo killall Xorg
[01:21] <aaron1234> Whats weird is if i su to root and startx a default session comes up fine
[01:21] <ahoneybun> yea
[01:21] <ahoneybun> are you are 15.04 or 15.10?
[01:21] <aaron1234> K let me try that
[01:22] <aaron1234> Haha i forget how can i check
[01:22] <aaron1234> Oh 15.04
[01:22] <ahoneybun> ok
[01:23] <aaron1234> Interesting when i do the killall
[01:23] <aaron1234> It brings me to the kde gui login
[01:23] <aaron1234> But if i login im back to black background
[01:24] <ahoneybun> that is very odd
[01:25] <ahoneybun> using startx gets you back to a desktop?
[01:25] <aaron1234> Yeah i always manage to screw stuff up
[01:25] <aaron1234> Only as root
[01:25] <aaron1234> If i do it as my user its the same black
[01:26] <ahoneybun> yea startx might have permissons for only root
[01:26] <aaron1234> Its probably related to my video card
[01:26] <aaron1234> Nvidia quadro k4000 and the ubuntu drivers wont work i have to use sgfxi
[01:26] <ahoneybun> what card
[01:27] <aaron1234> After the last update it wouldnt boot until i set the gfxmode to "keep" in grub config
[01:27] <ahoneybun> high end graphics card there
[01:27] <aaron1234> Was giving me a "invalid video mode text"
[01:27] <aaron1234> Yeah
[01:27] <aaron1234> Nightmare with linux :(
[01:28] <ahoneybun> there are a few problems drivers related being worked on
[01:28] <ahoneybun> best to stick with free nvidia driver perhaps
[01:29] <ahoneybun> I have the nvidia prime setup (intel+nvidia) and it was a pain in the beginning
[01:29] <aaron1234> It doesnt work at all
[01:30] <aaron1234> I spent sooo many hours trying to get it to work any other way but the proprietary driver jnstalled with sgfxi has been rhe only to work
[01:31] <valorie> but once you startx with root, doesn't that mean your user *cannot* use it anymore?
[01:31] <valorie> in other words, using root privs wrecked it
[01:32] <valorie> !sudo
[01:32] <aaron1234> Really?
[01:32] <valorie> one can use chmod to fix, but startx is pretty deep in the stack
[01:33] <valorie> aaron1234: we get people here who have done that, all the time
[01:33] <valorie> unfortunately
[01:33] <aaron1234> What do i need to chmod to fix it
[01:34] <valorie> !chmod
[01:34] <valorie> good question
[01:34] <valorie> dunno the answer though
[02:46] <cano> Hola!
[02:49] <cano> Hi
[02:49] <cano> hello
[02:49] <cano> Xd
[02:49] <cano> XD
[04:01] <Schokoriegel> Is there any way how to get the burning Windows effect in KDE? I'm really desperate I had them in Ubuntu 12.04 but they took them out in the 14.04 release :/ there not available in the repos anymore either
[04:05] <valorie> burning windows?
[04:06] <valorie> no clue what you're talking about?
[04:08] <Schokoriegel> The burning Windows effect when minimizing Windows like in 12.04
[04:10] <valorie> http://askubuntu.com/questions/833/how-can-i-make-my-windows-burn-when-i-close-them ?
[04:10] <valorie> not something we've ever had in KDE or Kubuntu
[04:10] <valorie> but of course you can use compiz if you prefer on kubuntu
[04:11] <valorie> Schokoriegel: ^^^
[04:11] <Schokoriegel> compiz-fusion-plugins-extra no I prefer Kwin
[04:13] <valorie> sorry, no idea
[04:13] <Schokoriegel> would be nice to have something like that on kwin
[04:13] <Schokoriegel> wait I send you a youtube then you maybe know what i am talking about
[04:13] <valorie> perhaps ask on kubuntuforum or so
[04:13] <valorie> perhaps on KDE forums then, if you want a change in kwin
[04:14] <Schokoriegel> ]like this https://www.youtube.com/watch?v=XnbPe33ofr4
[04:14] <Schokoriegel> I know it's compiz not Kwin
[04:14] <Schokoriegel> but I like Kwin better
[04:16] <Schokoriegel> do you now know what i am talking about
[04:26] <Schokoriegel> ?
[04:26] <valorie> I agree, kwin is the best
[04:26] <Schokoriegel> did you see
[04:26] <valorie> and I've never seen that on the list of effects available
[04:27] <valorie> since, like .... ever
[04:27] <valorie> but you can certainly request it
[04:27] <Schokoriegel> looks nice doesn't it?
[04:28] <Schokoriegel> would be so epic to have that in kwin
[04:28] <Schokoriegel> in addition to all the other effects :O
[04:30] <Schokoriegel> how can you request stuff?
[04:40] <valorie> Schokoriegel: you can file a bug against kwin, and cite the video as a "wish"
[04:40] <valorie> and no, I don't use many effects
[04:40] <valorie> would never use that
[04:41] <Schokoriegel> why?
[04:41] <Schokoriegel> Kde is made to look eye catchy
[04:43] <Schokoriegel> do you have a link or something?
[04:43] <valorie> I'm fine with you having what you like!
[04:44] <Schokoriegel> thx me to :D... I had those flame effects in ubuntu back and it would fit perfectly to KDE
[05:07] <Finetundra> I agree
[05:09] <valorie> Schokoriegel: sorry, I missed you asking for a link
[05:09] <valorie> https://bugs.kde.org
[05:13] <Schokoriegel> wow thanks and just say it is a wish?
[05:14] <valorie> exactly
[05:14] <valorie> what changes a wish into a feature is someone willing to make it happen
[05:38] <Schokoriegel> Damn I never find the right topic in there? there is way to much
[05:39] <valorie> kwin is the product
[05:40] <valorie> effect is what you want
[05:40] <Schokoriegel> should I just search kwin
[05:40] <Schokoriegel> oh ok thx
[05:40] <valorie> search for kwin effects and see what you find
[05:41] <Schokoriegel> thx for all you help
[05:41] <Schokoriegel> r
[05:41] <valorie> good luck, Schokoriegel
[05:42] <Schokoriegel> thx
[05:44] <Schokoriegel> there is nothing under effects?
[05:48] <Schokoriegel> but I think I can go from here
[05:51] <Schokoriegel> I think I just put it under kwin
[05:54] <Schokoriegel> Ok found effects
[06:08] <valorie> cool
[06:25] <Schokoriegel> is it there? https://bugs.kde.org/show_bug.cgi?id=350335
[08:33] <lordievader> Good morning.
[10:50] <BluesKaj> Hiyas all
[11:12] <mparillo> Hiyas. Do you know where Plasma5 stores its wallpapers?
[11:23] <BluesKaj> mparillo,  I use a wallpaper from a regular file that contains pics that I chose to use as wallpapers
[11:26] <BluesKaj> one can transfer pics to the default desktop wallpapers file
[11:30] <mparillo> BluesKaj: TY, and I have done that. I was wondering the path / file name file type for the default breeze wallpaper.
[11:34] <mparillo> Looks like /usr/share/wallpapers/Next/contents.
[11:36] <BluesKaj> yeah it's differnt for me since I'm on debian atm
[11:38] <naftilos76> Hi my bluetooth adapter is not working (not even recognized). Can you pls see the dmesg text here? https://gist.github.com/anonymous/7cc6e786fed5da423c4d
[11:38] <naftilos76> I am using kubuntu 15.04
[11:38] <BluesKaj> mparillo,  but  /usr/share/wallpapers/ is the same path here
[11:39] <naftilos76> hcitool dev results is no devices being recon
[12:53] <pauletin> Hi. I am using kubuntu 15.04, and the file chooser dialogs (for opening, saving as etc.) show no files at all. Is this a common problem?
[12:55] <pauletin> for Kate, it doesn't work. But for Kile, it works.
[12:56] <pauletin> so kde4 stuff is fine, but kf5 stuff is not
[13:07] <soee_> BluesKaj: are you on Vivid maybe and an test it ^
[13:08] <soee_> or lordievader maybe
[13:14] <BluesKaj> soee_, no Vivid install here , just Wily and Debian Jessie now
[13:15] <soee_> BluesKaj: ok :)
[13:18] <pauletin> never mind. I figured it out. Replacing baloo4 with baloo-kf5 fixed it.
[13:44] <naftilos76> Can anybody confirm if my bluetooth can be of any use in kubuntu 15.04 ? https://gist.github.com/anonymous/50304f1a9032640e9337
[13:44] <naftilos76> Doing "hcitool dev" in a terminal shows no devices
[16:14] <tmares98> good morning
[16:15] <tmares98> could anyone help me with dual boot problems using windows 7 and kubuntu
[16:16] <tmares98> i created the partitions and kubuntu seemed to have installed properly and also created a swap partition. yet when i restart the pc, it only boots to windows 7
[16:36] <BluesKaj> tmares98,   open your live media with the kubuntu image on it , then choose run kubuntu , once you have a desktop open a terminal and do sudo grub-install /dev/sda/  assuming sda is the partition your windows install is using. Then run sudo update-grub and the windows OS should show up in grub list and you're done
[16:39] <tmares98> ok so just to see if i understand correctly, i boot from cd and choose try ubuntu?
[16:39] <BluesKaj> yes
[18:07] <konversationtrye> BluesKaj: same poop different pile... just xchat was there when I started on redhat 5.2 and never changed
[18:09] <konversationtrye> and I believe I leaned on gnome due to the smaller resource footprint....
[18:15] <doug_> yep
[18:23] <fknupp> hi
[18:24] <fknupp> can anyone help me?
[18:24] <fknupp> i want to install the open intel graphiks driver to kubuntu 15.04
[18:26] <fknupp> i downloaded the  source code but i do not found wich compiler i need?
[20:38] <watsug> Hi I have a problem, try to use the Ubuntu SDK. When it start I get this error; click-chroot-agent[4326]: Could not  register DBUS service. Why is this and what can I do about it?
[20:41] <ahoneybun> watsug: does the SDK still start up?
[20:42] <watsug> Yes
[20:44] <watsug> It has some error messages in the log when trying to run a HTML5 app, even just the default  that is created with a new project.
[20:46] <ahoneybun> watsug: I had that message put it as well. Not sure of the cause
[20:46] <ahoneybun> I know it does not come up in Ubuntu though
[20:46] <watsug> Ok, so maybe there's some file missing that is included with Unity.
[20:47] <ahoneybun> maybe, we could be using something different in dbus for something KDE related
[20:47] <watsug> This is the errors in the log when I try to run a new project, the app still start. http://pastebin.com/aJe3xXZj
[20:53] <watsug> Guess I will install Ubuntu then.
[20:53] <watsug> Thanks for the help ahoneybun
[20:54] <ahoneybun> watsug: the message does not break anything from what I can tell
[20:54] <ahoneybun> I've been using Kubuntu for development
[20:55] <watsug> Hmm, guess no need to switch then :)
[20:55] <ahoneybun> yea
[20:55] <ahoneybun> no real reason really
[20:55] <ahoneybun> unless you like Unity or something
[20:56] <ahoneybun> I've done development in Ubuntu GNOME and Xubuntu as well
[20:56] <watsug> May I ask, have you gotten --inspect working like it is described in the "Meanings app guide"?
[20:57] <watsug> No, I really like the way plasma 5 look :)
[20:58] <ahoneybun> --inspect?
[20:59] <watsug> If you launch it in terminal --inspector enables debugging server
[20:59] <watsug> That can be connected to with a webkit browser
[20:59] <watsug> $ ubuntu-html5-app-launcher --www=www --inspector
[20:59] <watsug> as per this tutorial; https://developer.ubuntu.com/en/apps/html-5/tutorials/meanings-app-html5-tutorial/
[21:05] <ahoneybun> oh
[21:05] <ahoneybun> have not used it
[21:13] <watsug> ok
[21:15] <watsug> In this tutorial they also talk about a /js/app.js, "the app specific javascript file" But my app base instead has application.js, are they the same, maybe it was changed during developtment?
[22:11] <thickyholden> quit
[22:14] <jon___> hola
[22:14] <jon___>  tengo un problema con la configuracion de colortes en firefox,alguna ayuda?
[22:55] <mparillo_> !es


[00:20] <nacc> rbasak: if you get a chance take a look at the latest commits on lpusip:memcached#ubuntu/yakkety,{-proposed}
[00:20] <nacc> rbasak: those are achieved with the importer/ namespace implemented and with upload/ tag support (so in this case, I had the upload/ tag in my local repository that i then used as the basis for import)
[00:46] <halvors1> Hi. There is core dumps in systemd for last patch for systemd in xenial as well as yakkety.
[00:47] <halvors1> What happend here? Everything worked just fine before the "security update" and the last "change" in yakkety way after the freeze zone...
[00:55] <sarnold> halvors1: what bug number?
[01:17] <halvors1> sarnold: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1633274
[01:20] <sarnold> halvors1: very nice, thanks
[01:23] <halvors> I don't know exactly how yakkety is affected as well, the bug seems to be appearing only when i attach the VTI interface to a physical interface.
[02:09] <Bluefoxicy> I can't find the bug for "flash is completely broken in 16.10"
[05:29] <pitti> Good morning
[08:46]  * Mirv frequently refreshes https://launchpad.net/ubuntu/+series
[08:53]  * acheronuk prays for a slight break with the animal theme (zombie)
[09:44] <rbasak> nacc: nice!
[09:44] <rbasak> Interesting that the commit date appears to go backwards.
[09:44] <rbasak> (in ubuntu/yakkety)
[09:45] <rbasak> I guess that's just a consequence of the test using historical data in this case.
[11:12] <tsimonq2> cyphermox: Hello, what should I reply with here? https://www.reddit.com/r/Lubuntu/comments/57eg8q/vpn_icon_in_applet_tray/
[11:12] <tsimonq2> cyphermox: Afair, that's your specialty ;)
[11:18] <brendand> tsimonq2, ask them to post 'nmcli conn'
[11:22] <tsimonq2> brendand: ok
[11:50] <pitti> smoser: I revisited bug 1629797 and now sent a D-Bus patch upstream which solves this in a more intrusive, but also much more elegant way, FYI
[11:50] <pitti> smoser: so I'll see to getting this into z and Debian unstable soon, and at some point we can backport it to x and lose that workaround in cloud-init.service
[11:59] <rbasak> pitti: do you have a link to the upstream patch please? I'm curious.
[12:23] <vip> hello
[12:55] <pitti> rbasak: I linked it from the bug, freedesktop bug 98254
[12:56] <rbasak> Thanks!
[13:04] <smoser> pitti, link to upstream in the bug ?
[13:05] <pitti> smoser: I did
[13:09] <coreycb> pitti, hello, bug 1623107 is ready for another look if you have a chance
[13:15] <pitti> coreycb: http://launchpadlibrarian.net/289337158/python-mock-services_0.2-0ubuntu3_0.2-0ubuntu<IP_ADDRESS>.diff.gz looks a bit strange -- why did you remove the changelog?
[13:16] <pitti> coreycb: this is a build dep only, right? so it'll go into universe
[13:16] <coreycb> pitti, hmm, confused.. I didn't think python-mock-services existed in xenial
[13:17] <coreycb> pitti, it is a build dep only, yes.  I adjusted the changelog from yakkety so that the version is < yakkety
[13:17] <pitti> coreycb: I mean normally you'd take the y package, add a new changelog record for 0.2-0ubuntu3~16.04 (or ~xenial) and keep the rest
[13:17] <pitti> coreycb: but, nitpicking
[13:17] <coreycb> pitti, yeah I should have done that
[13:18] <pitti> coreycb: accepted; I'll let it build and binNEW it after that, then pylxd should start building
[13:18] <coreycb> pitti, thanks
[13:23] <coreycb> infinity, RAOF:  hello, any chance one of you could put xenial nova and neutron* in your sru review list for next week?
[13:23] <pitti> coreycb: …done
[13:23] <coreycb> pitti, thanks again
[14:44] <smoser> is there some tool that i can point at a changelog and it will download me the right orig tarball from launchpad ?
[14:46] <smoser> i'm aware of pull-lp-source, but basically want to run 'get-orig-source' in some directory, have it read the debian/changelog, and downlaod the .orig.tar.gz (or .tar.xz)
[14:46] <smoser> probably of the last non-UNRELEASED version
[14:46] <pitti> no, I don't think there's something that general
[14:46] <pitti> well, uscan --download-current-version --rename
[14:46] <pitti> that shold actually do what you want
[14:46] <cjwatson> only if it actually matches upstream
[14:47] <cjwatson> I'd be inclined to build something out of dpkg-parsechangelog + dget
[15:02] <nacc> smoser: to make it easier to build with teh importer, right?
[15:04] <smoser> yeah.
[15:05] <smoser> i just git clone, but then build says E_NO_ORIG_TARBALL
[15:05] <cjwatson> I always preferred the pristine-tar approach to this personally, although I've sensed that falling out of favour a bit
[15:05] <nacc> rbasak: yeah, i think that's an artifact of my local git-dsc-commit reconstruct having been done a few days ago, and the publish actually haveing occurred a week ago
[15:05] <cjwatson> and it does require tool support
[15:06] <nacc> cjwatson: right, that's what i was considering adding, although it will slow down our importer more
[15:06] <cjwatson> (all my git-dpm-managed packages have a pristine-tar branch that stores deltas versus commits on the upstream branch)
[15:06] <nacc> smoser: but agreed, it's a needed functionallity
[15:06] <smoser> i'm working on one.
[15:07] <rbasak> I imagined a tool that would use a cache somewhere in .git, and populate that if required, only on user demand.
[15:08] <nacc> rbasak: ack, i'm just worried about how large that cache might get, and it's a bit of complication to the 'importer' code proper -- i guess it could live in a different tool, though
[15:09] <barry> smoser: http://paste.ubuntu.com/23323900/
[15:09] <rbasak> Different tool is what I had in mind. Though if somehow the same cache could be used for both, that would be nice.
[15:09] <barry> that's what i've been using for a while now.  requires chdist.  not sure it's what you want, but you can easily run `gbp build-package` over the result
[15:10] <smoser> barry, thanks.
[15:11] <nacc> rbasak: ack, agreed
[15:12] <nacc> rbasak: at the minimum, i think the importer can stash the 'last' imported debian and ubuntu orig tarballs in there
[15:12] <nacc> rbasak: as those seem the 'most' valuable for the development side
[15:12] <rbasak> Yeah, but in smoser's clone use case, his cache would start off empty.
[15:13] <nacc> ack, we'd need to have a separate tool still, no matter what i tihnk
[15:13] <nacc> which is good, as 'building' is different from 'importing' :)
[15:21] <nacc> smoser: in your c#3 to LP: #1633114, doesn't that leave the trailing maintainer entry
[15:22] <rbasak> Perhaps even a tool that shares its cache with pull-lp-source?
[15:22] <rbasak> Using ~/.cache (XDG-ized) etc perhaps.
[15:23] <rbasak> But YAGNI, perhaps.
[15:27] <smoser> cjwatson, dget would require deb-src lines, right ? nacc that was by design
[15:27] <smoser> shoot
[15:27] <smoser> sorry, cjwatson . that was just in by buffer
[15:27] <cjwatson> er possibly, yeah
[15:28] <smoser> nacc, that was by design, as it is in the commit Author
[15:28] <smoser> right?
[15:29] <nacc> smoser: i agree, but it *does* leave the line in my case -- but in your comment
[15:31] <nacc> *but not
[15:31] <nacc> http://paste.ubuntu.com/23324002/
[15:32] <nacc> git diff import/1.4.1-1^..import/1.4.1-1 -- debian/changelog | sed -e '/^[+]/!d' -e 's/^[+]//' -e '/^ /!d'
[15:49] <smoser> alright...
[15:49] <smoser> so
[15:49] <smoser>  https://launchpad.net/ubuntu/+archive/primary/+files/isc-dhcp_4.3.3-5ubuntu14.dsc
[15:49] <smoser> dget https://launchpad.net/ubuntu/+archive/primary/+files/isc-dhcp_4.3.3-5ubuntu14.dsc
[15:49] <smoser> always fails for me, and i have to pass '-u'
[15:49] <smoser> what is the right way to m ake it pass ?
[15:52] <bdmurray> happyaron: Are you about? Your fcitx upload has no Launchpad-Bugs-Fixed in it.
[15:52] <smoser> nacc, did you figure it out ? i probably changed something and didn't update what i put inthe comment
[15:52] <nacc> smoser: no, i just wanted to make sure i wasn't missing something obvious, i can tweak the regexs
[15:57] <nacc> smoser: for dget, wouldn't it need to know the public key for whoever uploaded that version? is that what is' verifying?
[15:57] <nacc> *it's
[15:57] <cjwatson> smoser: there isn't necessarily a good reason to expect that you'll have the necessary public key, for Ubuntu.  For Debian, where that tool was written, they're generally in the debian-keyring package.
[15:58] <cjwatson> smoser: transport security is probably OK in this case ...
[16:00] <smoser> cjwatson, yeah. thats what i was thinking. i justdidn't know if in general i was missing some obvious thing.
[16:07] <rbasak> nacc: do you have SRU information for bug 1629241 please?
[16:07] <nacc> rbasak: let me fill it out
[16:08] <smoser> https://gist.github.com/smoser/fa77f61a2b650d115b5fc2a8ab028ede
[16:08] <smoser> nacc, cjwatson that is probalby over-engineered in many ways, but works for me.
[16:08] <smoser> bad thing is that it downloads more than just the dsc and the orig tarball (gets the debian tarball too)
[16:12] <rbasak> nacc, caribou: you have both uploaded an SRU for multipath-tools in Trusty for different bugs. Could you coordinate and consolidate these into one upload, please?
[16:12] <rbasak> So I propose to reject both from the queue unless you object?
[16:13] <caribou> rbasak: I'm fine with it, I'll ping nacc to coordinate
[16:14] <nacc> rbasak: fine with me, sorry about that!
[16:14] <nacc> rbasak: LP: #1629241 updated; however, I'm not sure the test case is sufficient
[16:16] <rbasak> nacc: will you be able to exercise that test case if required? If not, I suggest asking the reporter to commit to doing the SRU verification - otherwise we sometimes end up stuck blocking other SRUs and have to reject it in the end.
[16:16] <rbasak> bdmurray: any opinion?
[16:16] <bdmurray> rbasak: The reporter verified from a PPA so I think they are willing
[16:17] <caribou> nacc: I just pulled your source, want me to merge it with mine (got two patches)
[16:17] <rbasak> caribou, nacc: sounds like you could have fun with the git workflow there :-)
[16:18] <caribou> rbasak: nacc: this is something that came up within our team : how do we handle post-merge uploads to dev
[16:18] <nacc> rbasak: bdmurray: yeah, they already were very prompt in our testing
[16:18] <nacc> *prior testing
[16:18] <rbasak> bdmurray: OK, so shall we accept that one?
[16:18] <nacc> caribou: fine with me, thanks!
[16:18] <caribou> rbasak: nacc: do we keep using the git repo or just debdiffs
[16:19] <nacc> caribou: yeah, that's on my todo list for today (hopefully)
[16:19] <nacc> caribou: using the git workflow for bugfixes
[16:19] <caribou> nacc: ok, will merge both & post the debdiff in a few minutes
[16:20] <nacc> caribou: debdiffs will also still be supported and handled, but if one knows to use the git repo (and hopefully that population grows), then MRs can be used, etc.
[16:24] <caribou> nacc: here is the debdiff : http://paste.ubuntu.com/23324297/
[16:25] <nacc> caribou: looks good to me!
[16:25] <caribou> nacc: ok, uploading
[16:28] <caribou> rbasak: nacc: ok, merged multipath-tools trusty SRU uploaded
[16:29] <rbasak> Thanks!
[16:29] <nacc> apw: query on the overlay stuff in y -- given that overlayfs is no longer recognized, should there be something that goes into /etc/schroot/chroot.d/ and post-install of an appropriate kernel ensures that it says overlay for each schroot? I guess that could be a sbuild change. Wasn't sure if there was already a bug for this
[16:30] <nacc> apw: i'll re-ask that in #ubuntu-kernel
[16:36] <nacc> smoser: if we import a version and it's a copy-forward from another release, do you want the most recent chagnelog entry to be present still?
[16:36] <rbasak> nacc: could you add SRU paperwork to bug 1628723 please?
[16:38] <rbasak> caribou: looks like someone messed with the bug status in bug 1621835, but it should have been Fix Released in the development release if it already has the fix.
[16:40] <nacc> rbasak: done, similar statement regarding testing as the strongswan one (they already tested via PPA)
[16:40] <rbasak> OK, thanks.
[16:42] <smoser> nacc, i guess all the interim, wouldnt you think ?
[16:43] <nacc> smoser: what do you mean by interim? e.g., 1.4.25-2ubuntu1 published in x, then copied to y, what do you think should be in y's importer commit message
[16:45] <nacc> keeping in mind that x's commit message may also be affected by your choice (because it was copied from x-proposed)
[16:48] <smoser> hm..
[16:48] <smoser> i dont know.
[16:52] <nacc> smoser: yeah it's tricky, if we say it's the most recent changelog entry (whcih corresponds to the version in that import), then i have to probably use dpkg-parsechangelog or similar manual munging (btw, i'm basically taking the middle route on that issue, after talking with rbasak, i'll add some manual fallback in the code if dpkg-parsechagnelog fails, so hoepfully we won't need source patches anymore
[16:52] <nacc> (but we'll still keep that support around))
[16:52] <nacc> smoser: if we say it's the diff, it might be empty often
[16:52] <smoser> when would it be empty ?
[16:53] <smoser> only rally on "first copy to branch"
[16:53] <nacc> and every series starts with that :)
[16:53] <nacc> and some series get no updates
[16:53] <nacc> so it depends on 'often'
[16:53] <nacc> i'm fine either way, just trying to match what you expect
[16:54] <nacc> diff is probably easier for me to code, tbh
[17:03] <nacc> smoser: let me generate an example tree and we can use that as the basis for discussion
[17:07] <smoser> nacc, another possibity is to just push this to a tool
[17:07] <smoser> that looks at git log debian/changelog
[17:11] <nacc> smoser: sorry, i'm a bit confused; i thought the point was you wanted to see the corresponding changelog entry in the `git log` ?
[17:13] <smoser> right. i did.
[17:13] <smoser> and i do think that woudl be useful.
[17:14] <smoser> but if you can't figure out the right way to do it, i thin it may be sufficient to say "thats a user problem"
[17:14] <nacc> smoser: ah ok :)
[17:15] <nacc> smoser: i think i can get us something that is useful, and i agree in principe that our current `git log` output is not the most helpful
[17:38] <smoser> so lets say i had a fix for a bug (bug 1629972)
[17:38] <smoser> where would i upload that ?
[17:38] <smoser> shall ijust upload it to yakkety-proposed ?
[17:42] <nacc> smoser: iiuc, based upon prior discussions, you can just upload to ubuntu and it will dtrt?
[17:43] <nacc> smoser: ah but you mean because z isn't open yet?
[17:43] <smoser> right
[17:44] <nacc> good question :)
[17:50] <slangasek> smoser: yes, yakkety-proposed for now.  I guess this is an SRU candidate regardless, right?
[17:53] <smoser> slangasek, yes.
[17:53] <slangasek> then definitely yes :)
[17:55] <nacc> slangasek: process-wise, given that the 'development release' should always have the fix first, how is the devel release defined right now?
[17:55] <nacc> *for an SRU, I mean
[18:04] <nacc> smoser: any idea why the single-quote escape isn't working? http://paste.ubuntu.com/23324761/
[18:07] <smoser> to escape single ticks you need '\''
[18:07] <smoser> but probably best to avoid the shell interpretation
[18:07] <smoser> unless you're just asking about you typing things.
[18:08] <smoser> or if you prefer, "" can do same as \ there: echo 'you can'"'"'t do that.'
[18:09] <nacc> smoser: well, i mean if i do git commit -m '<result of git-diff>' and git-diff contains '
[18:09] <nacc> smoser: it doesn't go so hot :/
[18:10] <smoser> but why are you passing that to the shell
[18:12] <nacc> smoser: sorry, not sure i understnd? we use subprocess.call(shell=True) throughout th eimporter
[18:12] <smoser> yeah, thats wrong.
[18:12] <smoser> almsot always
[18:12] <nacc> smoser: i could switch those around, but i ran into plenty of other issues
[18:13] <smoser> almost always better to not have the shell involved.
[18:16] <nacc> smoser: ok, so not using the shell, i probably need to pass absolute paths to everything?
[18:16] <nacc> smoser: as just switching shell=True off broke just about every subprocess call :)
[18:16] <smoser> yeah, because you invoke with "git log" rather than ["git", "log"]
[18:20] <nacc> smoser: ah ok
[18:20]  * nacc switches over to shlex.split
[18:20] <smoser> nah.
[18:20] <smoser> just drop the shell
[18:20] <smoser> i promise, it will only get in the way.
[18:21] <nacc> dropping the shell requires me to switch everything to []
[18:21] <nacc> which i just did by using shlex.split
[18:21] <nacc> the only ones that still use shell are those using pipes
[18:21] <nacc> i will change those over later
[18:23] <nacc> lol, shlex.split also has an issue with nested '
[18:25] <smoser> nacc, http://paste.ubuntu.com/23324843/
[18:25] <smoser> that handles ithink all but the pipes
[18:25] <smoser> ican fix those too
[18:26] <nacc> smoser: right, that is what shlex.split() is supposed to be doing :)
[18:26] <nacc> let's just say it doesn't work so hot :)
[18:26] <nacc> ok i'll do the same locally
[18:26] <smoser> well, no.
[18:27] <smoser> it is actually doing the righ tthing
[18:27] <smoser> its splitting as the shell would split
[18:27] <smoser> which is why you have bug for bug compatibility
[18:27] <nacc> even if i use shlex.quote first, it bugs out
[18:27] <nacc> it's fine
[18:27] <nacc> i'm changing to your format
[18:45] <slangasek> nacc: we batch-copy packages forward from yakkety-proposed to z-proposed once it opens
[20:49] <smoser> bah
[20:49] <smoser> slangasek, i remember at soem point in the long past making changes to dhclient so that if it failed to get a lease it would die
[20:49] <tsimonq2> smoser: bah
[20:49] <smoser> and exit failure
[20:50] <smoser> but it seems it does nto do that now
[20:51] <smoser> dhclient -v -4 ... echo $?; seems to say 0
[20:51] <smoser> http://paste.ubuntu.com/23325534/
[20:52] <slangasek> smoser: did you forget the -1 option?
[20:52] <slangasek> not according to your pastebin
[20:52] <smoser> no. i typo'd -4 for -1 above
[20:53] <slangasek> ok
[20:53] <smoser> do you remember doing this too ? or did i make it up.
[20:53] <smoser> the man page seems to say it will act like i expect
[20:53] <slangasek> smoser: dhclient was always supposed to work that way on -1, we changed other things to make use of that behavior
[20:54] <slangasek> smoser: so clearly that's misbehaving per manpage; file a bug with deets?
[20:54] <smoser> deets ?
[20:54] <slangasek> details ;)
[20:55] <nacc> heh
[20:56] <smoser> people commonly over-guess on my hipness factor.
[20:56] <smoser> thats either because a.) i just look hip
[20:57] <smoser> b.) i'm more lame than people expect is possible.
[20:57] <slangasek> you've apparently ruled out c) slangasek uses dated slang to keep people guessing if he's retro or just old
[20:59] <nacc> all of the above?
[21:06] <dobey> when people say "deets" it makes me think of https://en.wikipedia.org/wiki/DEET
[21:07] <smoser> https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1633619
[22:12] <srwarren> Does anyone know how/why/when /etc/default/locale is created when running the Ubuntu installer?
[22:12] <srwarren> Related, if a system is being installed a different way, e.g. by untaring a root file system .tar file supplied by Canonical, what's the suggested way of creating config files like that; just untar another overlay .tar with manually created file content, do something at first-boot, or ?
[22:19] <nacc> smoser: if you're around: https://git.launchpad.net/~nacc/ubuntu/+source/memcached
[22:19] <nacc> smoser: that has changelog entries


[04:24] <hikiko> hello
[08:00] <Laney> ahoy ahohohohohohoy
[08:04] <Laney> bleddy europeans
[08:08] <willcooke> morning Laney
[08:11] <Laney> how do willcooke?
[08:11] <willcooke> typical lazy lefties
[08:12] <davmor2> Laney: you know we are Europeans right :P
[08:14] <davmor2> willcooke: you leave left handers out of it :P
[08:14] <Laney> I've ordered the tug boats to start pulling
[08:14] <Laney> by the end of the week we'll be 500m off NYC
[08:15] <willcooke> :D
[08:15] <davmor2> Laney: can you make it florida instead be nice to get some actual sun
[08:16] <Laney> pastrami
[09:13] <willcooke> 16GB USB flash drives are now 3 quid.
[09:13] <willcooke> ?!
[09:14] <duflu> willcooke: Yes. Or AUD$8-$10
[09:14] <duflu> They may not last more than a week though
[09:14] <willcooke> haha!
[09:14] <willcooke> Very true
[09:15] <duflu> Although the only one I remember dying of late was SanDisk brand
[09:15] <duflu> willcooke: More amazing are 128GB and now 256GB microSDs
[09:15] <willcooke> This is Toshiba, but I very much dobut that anyone who actually works at Toshiba has anything to do with it
[09:15] <duflu> Just stare at them in wonder
[09:16] <willcooke> O_o
[09:16] <willcooke> The world has gone mad
[09:16] <duflu> willcooke: I found the former recently for around 40 quid equivalent
[09:16]  * willcooke grumbles about kids today
[09:17] <willcooke> 1TB SSDs are still pricey, but I expect people want those to last a few years min.
[09:17] <duflu> More amazing that I can measure they do get the advertised 80MB/s
[09:18] <willcooke> incredible
[09:18]  * duflu also looks at the box of floppy disks he never sorted, and has no drive to read
[09:19] <willcooke> ha! yes.
[09:52] <happyaron> willcooke duflu for performance I'd recommend sandisk cz80
[09:52] <happyaron> it's about 26gbp for 64gig
[10:00] <willcooke> happyaron, good to know, thanks
[10:03] <davmor2> duflu: http://www.ebay.co.uk/itm/like/221953327364?limghlpsr=true&hlpv=2&ops=true&viphx=1&hlpht=true&lpid=122&chn=ps&googleloc=1007249&poi=&campaignid=207297426&device=c&adgroupid=13585920426&rlsatarget=pla-131843261346&adtype=pla&crdt=0&ff3=1&ff11=ICEP3.0.0-L&ff12=67&ff13=80&ff14=122 no excuses
[10:05] <duflu> davmor2: OK then. I claim laziness now
[10:05] <duflu> Also time to make dinner :)
[10:41] <Trevinho> hikiko|ln: hey, there are several MPs about the expo/scale fixes for bottom launcher... I mean some from handsomefeng, other yours... They're almost the same, but not sure if I'm missing something... Why this duplication?
[10:45] <hikiko|ln> Trevinho, I think that handsome_feng is trying to fix the maximised window bug and for some reason he cloned my branches instead of starting from scratch
[10:45] <hikiko|ln> if you see the branches they are identical
[10:46] <hikiko|ln> I don't know why he used mine
[10:46] <Trevinho> mh, I see
[10:46] <Trevinho> well, unity side is different...
[10:47] <hikiko|ln> well, my branches fix the scale and the expo
[10:48] <hikiko|ln> feel free to merge them if they are ok
[10:48] <hikiko|ln> and then we just add a depends on ... branch to handsome feng's
[10:48] <hikiko|ln> so that we don't have duplicate changes
[10:51] <Trevinho> hikiko|ln: ok, as his branch is not relly using your commit... But the raw diff. Anyway, yours fine... BUt you've to do an one line change:
[10:51] <Trevinho> workArea.setBottom (optionGetYBottomOffset ());
[10:51] <Trevinho> has to be come:
[10:51] <Trevinho> workArea.setBottom (workArea.bottom () + optionGetYBottomOffset ());
[10:51] <Trevinho> hikiko|ln: can you fix this, so I can add it to the landing list?
[10:51] <hikiko|ln> sure give me a minute
[10:51] <hikiko|ln> 5 minutes :p
[10:51] <hikiko|ln> brb
[10:52] <Trevinho> hikiko|ln: ok
[11:04] <hikiko|ln> Trevinho, are you sure this is needed?
[11:05] <hikiko|ln> it won't make the area appear larger?
[11:07] <Trevinho> hikiko|ln: mhmhmh.... Well, let me think... it should be workArea.bottom () - offset actually... isn't it?
[11:07] <hikiko|ln> no
[11:07] <hikiko|ln> it should be == bottomYOffset
[11:07] <hikiko|ln> because when the workarea quad is made
[11:08] <hikiko|ln> the bottom is subtracted
[11:08] <Trevinho> hikiko|ln: well, workarea bottom could be not zero when you've two monitor stacked vertically
[11:08] <Trevinho> well, sorry I didn't want to mean 0.. but monitor height
[11:08] <hikiko|ln> certainly not 0 but I think it should be ybottom offset
[11:09] <Trevinho> hikiko|ln: yeah, but you've to take in consideration the old value for botom()
[11:09] <hikiko|ln> let me check
[11:09] <Trevinho> if you've two monitors stacked vertically, the top one has a bottom that is non zero...
[11:10] <hikiko|ln> right
[11:10] <hikiko|ln> I got it
[11:11] <hikiko|ln> so on single monitor bottom = 0
[11:11] <hikiko|ln> and we can safely do bottom + offset
[11:12] <hikiko|ln> ok :) give me a minute to run it and I push it
[11:36] <hikiko|ln> Trevinho, I pushed the change, thank you
[11:40] <hikiko|ln> wait a min where's the expo change :
[11:42] <hikiko|ln> Trevinho, wait a sec the expo change is missing from this branch
[11:43] <hikiko|ln> no it's there
[11:43] <hikiko|ln> :p
[11:43] <hikiko|ln> ignore :)
[11:46] <desrt> hello humans
[11:46] <willcooke> hi desrt
[11:47] <hikiko|ln> hi desrt
[11:49] <hikiko|ln> ttys again \m/ reboot :/
[11:58] <desrt> good morning willcooke, hikiko|ln
[11:58] <desrt> everyone have a good weekend?
[11:59] <hikiko> wow, I forgot it's monday :)
[12:37] <a1fa> ood day guys
[12:39] <andyrock> hey guys
[12:44] <a1fa> hikiko: i was finally able to document the bug with the disappearing windows
[14:42]  * Laney is attacking 3.20 css
[14:43]  * davmor2 sounds like the 3.20 css is winning, put some effort in laney ;)
[14:49] <Laney> I SHALL BE VICTORIOUS
[15:30] <Trevinho> Laney: you will
[15:32]  * davmor2 bets £80 on 3.20 css and £100 on Laney I like to edge my bets :)
[15:37] <Laney> quite bad currently
[15:37] <Laney> less bad than it was though
[17:08] <willcooke> gnight all
[18:07] <willcooke> meh, forgot about meetings later
[18:07] <willcooke> going afk, back to speak to robert_ancell later
[20:25] <Trevinho> Ouch, I'm getting a build failure in unity in yakkety ppc64el....  How can i debug that... I guess quemu isn't the best thing, right?
[20:25] <Laney> TREVINHOOOOOOOOOOOOOOOO
[20:25] <Trevinho> LANEEEEEEEEEYYYYYYYYYYYYYYYYYYYYYYYY
[20:26] <Laney> link?
[20:26] <Laney> can probably sort out access to a box
[20:26] <Laney> but tomorrow
[20:26] <Trevinho> Laney: https://launchpadlibrarian.net/259848746/buildlog_ubuntu-yakkety-ppc64el.unity_7.5.0+16.10.20160516.1-0ubuntu1_BUILDING.txt.gz
[20:26] <Trevinho> Laney: oh, that would be coooool
[20:26] <Laney> did you retry?
[20:26]  * Trevinho checks if there's something in the code that could trigger it... But that test lived there for years with no issue in all archs
[20:26] <Trevinho> so.....
[20:27] <Trevinho> Laney: yep
[20:27] <Trevinho> twice
[20:27] <Trevinho> same crash, same pos
[20:27] <Laney> k
[20:27] <Trevinho> Laney: thanks
[20:27] <Laney> pitti can also help with that
[20:31] <Trevinho> Mh, actually there's something that could trigger it in code.... But.... I see it only in that arch, so it's quite bizarre
[21:05] <willcooke> morning robert_ancell
[21:05] <willcooke> *pounce*
[21:05] <robert_ancell> willcooke, hikiko
[21:05] <willcooke> :)
[21:05] <robert_ancell> willcooke, or hi
[21:05] <willcooke> he!
[21:05] <willcooke> heh
[21:05] <willcooke> robert_ancell, attente - gimme 5 mins to finish this email and I'll be with you
[21:06] <hikiko> robert_ancell, hi
[21:06] <robert_ancell> hikiko, hi!
[21:12] <willcooke> robert_ancell, attente ok done
[21:50] <willcooke> g'night all
[21:52] <attente> robert_ancell: the branch is on git.gnome.org as wip/temp/ubuntu-xenial-rebased-corrected
[21:53] <attente> robert_ancell: at some point, i gave up on properly amending commits and just did a fix-up patch in the end
[21:53] <robert_ancell> attente, cool
[21:53] <attente> but basically it should be the same result as a resolved merge between GNOME_SOFTWARE_3_20_2 and wip/ubuntu-xenial
[21:57] <robert_ancell> attente, ok, I pushed to wip/rancell/ubuntu-xenial-rebase
[21:58] <robert_ancell> I think the merge commit got confused, but hopefully it worked..
[22:02] <attente> robert_ancell: ok, i'll check the diff after dinner
[22:39] <a1fa> xset m 0 0
[23:45] <a1fa> Andrea, you here?
[23:46] <a1fa> thanks for picking up that bug ;)