[10:14] <ikonia> waveform: that's incredibly useful, thank you, I've got to take that in and check a few things now, thanks so much for typing hat
[10:16] <waveform> ikonia, no prob -- I'll try and sort out (some of) the mess that is raspi-config shortly but it'll take a while to SRU from kinetic (where the fix will initially wind up) to jammy. And while I can fix it looking at the right location (/boot/firmware/config.txt instead of /boot/config.txt) some stuff is much more complex (e.g. raspi-config assumes a dhcpcd networking setup and has no knowledge of netplan so all the networking stuff in their may/may
[10:16] <waveform>  not work and may/may not get undone by the next netplan apply)
[10:20] <ikonia> waveform: I was about to offer some help tidying up raspi-config
[10:20] <ikonia> dissapointing that stuff is getting added to the repos like this (it's not the first I've seen)
[10:20] <waveform> ikonia, heh -- I'd look at the code before offering any help ;)
[10:21] <ikonia> waveform: I have the fear...but also the will
[10:21] <waveform> ikonia, imagine a mess of ~3000 lines of bash with a bit of lua thrown in for text manipulation (because ... why not)
[10:21] <waveform> lots of it *heavily* raspios specific, so it'll never fit ubuntu particularly well
[10:23] <waveform> (there's a reason I resisted calls for it to be added to the archive, but oh well)
[10:23] <ikonia> waveform: that's interesting, I will take a look
[11:02] <ikonia> I'm curious do you have any understanding/view why 'podman' isn't in the ubuntu repos until 22.04 ? I'm looking at my debian 11 pi host, which has podman in 'main' (an old version 3.0.1) but that's not in the ubuntu repos, yet Jammi has 3.4 in it
[11:07] <ikonia> also are any of you running Jammy yet ? I'm curious to how you're finding it (especially on a pi) I'm currently copying the image to my SD card to test
[11:07] <waveform> ikonia, erm - not sure I'm afraid -- looks like it was added in impish (https://launchpad.net/ubuntu/+source/libpod) but I'm not sure why it wasn't around before that -- I could hazard a guess it would be something to do with the dependencies
[11:08] <ikonia> waveform: I did think a similar thing on the dependencies, until I checked my debian host and at a glance they all line up with ubuntu 20.04
[11:08] <ikonia> it doesn't matter, it's in 22.04 which is what I'm porting to
[11:08] <waveform> (and I'm running jammy, but then I have to :)
[11:08] <ikonia> I was just curious as it seems an odd one to exclude
[11:09] <ikonia> waveform: I suspected you would be, curious to how you're finding it after you put a lot of work into it
[11:11] <waveform> a mixed bag -- on the one hand, I'm happy we've now got an LTS without u-boot in the default sequence (much less headaches for me!), and the server side of things is working pretty nicely (e.g. cloud-init handles wifi "out of the box" ... although not wifi regulatory domain which is still a bug-bear of mine because raspios does that "right" and we don't). So I can spin up a new pi server image, have my ssh keys imported, my keyboard layout set and
[11:11] <waveform>  within a minute of it booting it all "Just Works"
[11:12] <ikonia> that's cool, I've been working around that by having a puppet or ansible run straight after provisioining to pull in my settings
[11:13] <ikonia> maybe I can move away from that
[11:17] <waveform> the desktop side still has a lot of bits I (and others) need to work on, e.g. broken rendering of embedded browser controls, all the pain that the firefox snap caused (nativemessaging (argh!), initial seeding taking a while, etc.), wifi regulatory domain (again!), differing default user permissions for gpio (still!), and probably several other things I've forgotten (my bug bookmarks folder is currently several hundred items long)
[11:20] <ikonia> I'm still not feeling snap is a good way for ubuntu to move
[11:21] <ikonia> it feels like unity against, in terms of the attitude / disconnect from both the community and the wider linux world
[11:27] <waveform> I can understand the rationale for it but there's a couple of sides to snaps: there's the "shipping desktop apps" side (which is all the wider public tend to see of it), and the "embedded/secure infrastructure" side (Ubuntu Core and the like), which has far less visibility
[11:29] <waveform> the latter makes sense to me (but took a *long* time for me to get up to speed on, and I still get bitten by corner cases here and there)
[11:32] <waveform> the former (desktop apps) ... I understand the reasons: the modern browser release cycle is sufficiently brutal that it's basically impractical to ship a browser any other way (trying to keep them interwoven with the larger eco-system of stuff in the archive, especially across multiple releases and architectures, is all but impossible -- or at least far too expensive to contemplate). However (and I should stress this is my personal opinion), the
[11:32] <waveform> results so far are ... less than ideal. I'm still using the debs from the mozilla PPA on my pi desktop because otherwise I can't use my password database (keepassxc)
[11:34] <ikonia> odd that you see it like that, as I was coming from the server/security aspect that 'I' see mostly (although I'm sure I have gaps) and I do see the value in principal to things like ubuntu core
[11:35] <ikonia> the desktop stuff I've never really looked at because I don't use the desktop really any more, but also the model for the server/security stuff just seems wrong at a basic level and I can't imagine it working well translating to a more complex need of the desktop
[11:36] <ikonia> so that's really useful to hear your (acknwledged) personal view, different perspective is interesting
[11:42] <waveform> on the core/iot side of things: once I dug under the veneer that snapd plasters over it and understood things like snap-interfaces == apparmor-profiles, and (some bits of) the signing/boot-fallback mechanisms (there's still plenty there I don't get, but a lot of it doesn't apply to the pi (yet) so I haven't read far into it), it largely made sense, at least when seen from the perspective of an embedded device (something with limited/no user
[11:42] <waveform> interface that performs a single, or very limited number of tasks that you want to stay up to date and "Just Work")
[11:44] <waveform> at a server level (where you may well have an interactive console, and it's a much more complex prospect that's potentially running multiple services) that's a different story however
[11:49] <ikonia> waveform: so that part I can see the benifit off the linking into apparmor-profiles, I just wish it was more 'open' in terms of the work, but also more an approach across distros/pojects, it feels like this is another thing the wider community are not using inside ubuntu, and certainly not outside ubuntu
[11:49] <ikonia> so it's going to do the unity thing of making it a niche/propritary setup against the rest of the linux world
[11:50] <ikonia> eg: Ubuntu != Linux
[11:50] <ikonia> some quality ideas/things are being done in ubuntu, like netplan, but they are not being agreed with/adopted by the rest of the world
[11:53] <ogra> just be aware that the PPA might silently stop updating eventually ... mozilla asked to nuke all FF debs so i exoect this PPA to be gone eventually too
[11:54] <ikonia> really ?
[11:54] <waveform> ogra, indeed -- unfortunately that's my one option for password manager integration currently (the other workaround suggested was "use the auto-type facility" which .. doesn't work on wayland :)
[11:54] <ikonia> why would Mozilla ask for all FF debs to be removed ?
[11:54] <ogra> because they are not maintained
[11:55] <ogra> the PPA is a community thing
[11:55] <ikonia> yeah, but I thought that community PPA was still actively maintained ?
[11:55] <ogra> mozilla switched to the snap as default for ubuntu ... not sure they will accept community maintained packages that are not within the trademark agreement
[11:56] <ikonia> that's interesting, I hadn't realised that
[11:56] <waveform> (the old iceweasel/firefox story basically)
[11:56] <waveform> (or whatever the "non-trademark" name was)
[11:56] <ikonia> I think that's an interesting statement (not picking on your wording) 'switched to snap for ubuntu' - this is the point I was trying to make that ubuntu appears to be going it's own way
[11:56] <ogra> but i guess until the one major missing feature (nativee-messaging controller) is fixed they wont move
[11:57] <ogra> *native-
[11:57] <ogra> once that is there all missing features (gnome extension installation, keepassxc, smartcard support) should work
[11:58] <waveform> indeed -- and once that is in place, I will be moving back to the snap because (frankly) I *ought* to be using it to dog-food the ubuntu desktop experience on the pi (but, obviously, password manager integration is rather critical so I don't realistically have an option currently)
[11:59] <ogra> ikonia, well, this was really on mozillas initiative
[11:59] <ogra> (happily accepted on the ubuntu side indeed ... but they were the ones pushing for it basically)
[11:59] <ogra> snaps save immense amounts of manpower
[12:01] <ogra> packaging is 100x easier than debs (if you are actually not just re-packing deb binaries, which is usually creating an utter mess, but properly use snapcraft) and you only need to QA one single context, not 4 releases of different age with 5 architectures
[12:02] <waveform> this is indeed what I'd heard -- I'm not on the desktop team but had heard it was a request from mozilla which was eagerly jumped on because browser packaging/backporting/testing is a *very* time consuming and resource-intensive thing so offloading it to upstream is hugely preferable
[12:05] <ogra> sadly there is still some issue with FF first-startup time ... on the Pi this is hilarious 25sec for me ... (which is funny since chromium nearly starts instantly (well 5-8sec on first start 2-3 on subsequent)
[12:05] <ogra> theer must be somethign with the FF binary itself that makes it so slow ... since the packaging between FF and chromium doesnt really differ a lot
[12:08] <waveform> however, while I'm sure firefox is "100x easier" to package in snaps than debs (even the deb included a ton of vendored-in/statically-bound stuff), I'd take issue with that as a general statement (certainly wasn't my experience when taking over the rpi-imager snap; but then that largely seems to be down to "cross-arch qt5 stuff")
[12:09] <ogra> ah, yeah, cross is always awful, no matter what packaging system you use (probably with the exception of tarballs 🙂 )
[12:11] <ogra> i thought rpi-imager was electron though ?
[12:13] <waveform> nope, qt5
[12:13] <waveform> (it does "look" electron-esque though, it's true :)
[12:33] <ikonia> for all my moaning, it's still worth pointing out that the ubuntu pi images is pretty mega, and arguably the best modern linux image for the pi (hence keen to move to 22.04)
[12:34] <ikonia> the effort creating and maintaining it is appreciated and worth it, so easy to moan, but thanks is also due
[12:34] <waveform> ikonia, heh -- glad you think so -- still plenty to do on my side but nice to see it's appreciated!
[12:34] <ikonia> nothing is every pefect, and the worst critic are those involved, so I'd expect you to say that, but I get a huge ammount of value from it
[12:53] <Maik> honestley, 22.04 desktop is one of the best releases on the Pi 4


[19:13] <govatent> hey guys. I am running a google hang out here in miami with itnet7. if anyone is online you guys should drop in to see us


[02:53] <Bert_2> Hi, we updated all our servers from 14.04 to 16.04 this weekend except one, now everything seems to be working fine (apart from the usual migration issues) except for the one server left of 14.04. That server has since been having lots of issues with LDAP auth. Are there any known changes or issues with slapd in 16.04 that may leave 14.04 clients with issues but 16.04 clients fine? We see that it us
[02:53] <Bert_2> querying the different ldap slaves quite a few ...
[02:53] <Bert_2> ... times before accepting a login
[02:53] <Bert_2> s/us/is/
[02:54] <patdk-lap> well, upgrade to 16.04 isn't supported yet
[02:54] <patdk-lap> still like 2 months away
[02:54] <patdk-lap> but this is unlikely related to your issue
[02:56] <Bert_2> patdk-lap: yeah, we usually wait until the .1 release, but it didn't really fit with our schedule (we are a university student IT organisation and we have to do maintenance during the summer holliday and way ahead or after the summer exams and not too close to the beginning of the academic year)
[02:58] <tarpman> Bert_2: any more details than that on the specific issues you're having?
[02:59] <sarnold> Bert_2: any log messages on either server or client?
[02:59] <Bert_2> tarpman: not really, we have tried restarting basically everything, there's nothing useful in the logs, no high resource usage, the load is very low
[03:00] <Bert_2> Connecting through ssh stalls in a few places, most prominently after showing the MOTD (when it is supposed to show the shell)
[03:00] <Bert_2> we're pretty sure it's ldap cause NFS works fine and local root is very swift
[03:00] <tarpman> Bert_2: how did you discover that "it" (and what's "it"?) is trying multiple ldap servers before working?
[03:01] <tarpman> Bert_2: worth checking that everything is ok with your DNS setup and name lookups aren't timing out anywhere
[03:01] <Bert_2> we also have PHP performance issues, we presume because we use LDAP users on NFS as well as to execute PHP using PHP-FPM
[03:01]  * patdk-lap blames sarnold and goes to bed
[03:01] <Bert_2> tarpman: tcpdump/wireshark
[03:01]  * sarnold blames patdk-lap and goes for dinner
[03:01] <Bert_2> the weird thing is that the client seems to get swift responses but isn't happy about it
[03:01] <Bert_2> we also checked DNS because we had issues while upgrading dns
[03:02] <Bert_2> but dig is swift
[03:02] <tarpman> interesting, what's the client software in question? are you able to share any of the traces of clients failing and working (maybe with some scrubbing)?
[03:02] <Bert_2> tarpman: just regular pam with ldap
[03:03] <Bert_2> very vanilla
[03:03] <tarpman> that's still not very specific; could be almost any combination of {pam,nss}-{ldap,ldapd,sss}
[03:04] <Bert_2> pam-ldap, I think
[03:05] <Bert_2> tarpman: jep, pam-ldap
[03:07] <tarpman> Bert_2: I think in your position I'd be firing up gdb and figuring out what the clients are actually doing when they're being slow
[03:08] <tarpman> Bert_2: I'm afraid I don't have any "known issues" or such to point you at, the sort of software combination you're talking about should generally work
[03:08] <Bert_2> Well, you've got me on a new path
[03:08] <Bert_2> ns2 seems to be down
[03:08] <Bert_2> we mischecked that I think
[03:08] <Bert_2> so I'm going to fix that first and then probably still gdb
[03:08] <Bert_2> but maybe I should go to bed
[03:08] <Bert_2> it's 5AM...
[03:09] <tarpman> ah yes, the part I changed jobs to get away from.... :P
[03:10] <tarpman> Bert_2: if it's not DNS, and you get as far as nailing down a specific config that reproduces it, feel free to ping me - always happy to help out with LDAP related stuff if I can
[03:10] <Bert_2> tarpman: cool, thx
[03:10] <Bert_2> I hope it's DNS though
[03:10] <Bert_2> that would be convenient to fix :P
[04:26] <Bert_2> tarpman: you were totally right, I couldn't leave it alone so ended up fixing ns2
[04:26] <Bert_2> weirdly enough that fixes everything right away
[04:26] <Bert_2> we will have to investigate why that made such an impacyt
[04:26] <Bert_2> *impact
[04:26] <Bert_2> anyway, thanks a ton for pointing us in the right direction! :D
[04:45] <tarpman> Bert_2: awesome, glad it was that easy :)
[07:00] <lordievader> Good morning.
[08:16] <lbert> I have a question/problem with a root server with one interface with multiple IPs, kvm and bridging. Everytime I create a bridge, my network stops working. I followed the example in the docs but I think I somehow mess it up with the virtual IPs. Also logs don't give me any real hints. Can anybody help / explain how to do it with virtual IPs?
[08:20] <lordievader> Could you walk us through your network setup and how you setup the bridge?
[08:33] <lbert> One physical interface (p7p1) with 2 IPs (p7p1:1-2). All have public IP assigned. I can ping all IPs. I followed the guide: https://help.ubuntu.com/community/KVM/Networking (copy & pasted the br0 config and edited it). I want to use the p7p1:2 interface. Now I'm not sure how to set br0 up. Do I comment in the p7p1:2 inteface and use the p7p1 interface as bridge_ports interface but assign the IP-Address
[08:33] <lbert> I would have assigened p7p1:2? Somehow dont seems right.
[08:38] <lbert> Or is it the complete wrong setup for assiging public ips to kvm-guests?
[09:18] <cpaelzer> rbasak: adding apport hooks - is that something that is more or less ubuntu specific anyway (Debian has apport, but I never seen integration for it)
[09:19] <cpaelzer> rbasak: so when considering what of my dovecot cleanup to submit to debian I'd skip the apport hooks or am I guessing wrong and they would likely like&take it?
[09:22] <rbasak> cpaelzer_away: good question. I'm not sure. I've seen them take it. Maybe ask pitti in #ubuntu-devel?
[09:33] <xnox> jamespage, rbasak - i made the mistake of a no-change rebuild of percona-server and it's failing it's tests now =(
[09:34] <xnox> i wonder if i should keep miscompiled percona on s390x in xenial or somehow fix the tests.
[09:34] <xnox> do we still need percona in xenial for openstack and stuff?
[09:34] <xnox> and are there specific reasons why we are sticking to 5.6? or simply move to 5.7 never happened?
[09:35] <jamespage> xnox, yes and not sure
[09:35] <jamespage> we still need pxc - I suspect that percona lags oracle mysql somewhat
[09:35] <jamespage> xnox, do need it for s390x as well tho :-)
[09:35] <jamespage> I just want everything today don't I
[09:36] <xnox> let's not go into discussing EU =)
[09:36] <xnox> i did hit "rebuild" button on the failed amd64 build, but that already showed a failed test, will wait for build log.
[09:41] <xnox> awww magically it did build \o/
[09:43] <LaserAllan> hi there, I've been running a python script for a while but for some reason sometimes when I am to access the interface that the script is running it just refuses my connection, is there anyway can detemrine whats casuing this?
[09:44] <xnox> jamespage, wonder how to validate the cluster portion. deploy juju charm? /me will check them
[09:45] <jamespage> xnox, yah
[09:45] <jamespage> xnox, juju deploy -n 3 percona-cluster, juju set-config percona-cluster root-password=changeme sst-password=changeme
[09:46] <jamespage> juju set-config percona-cluster source=proposed
[09:46] <jamespage> will also install from the proposed pocket for you :-)
[09:46] <xnox> brilliant! thank you
[10:18] <jorgesanjuan> Hi all. I'm trying to boot an x-gene arm64 server with UEFI and a GRUB. It seems to hang when the grub boots the kernel. I've seen it happened to some other developers on the internet but I can't fix it.
[10:18] <jorgesanjuan> This is all I can get:
[10:19] <jorgesanjuan> EFI stub: Booting Linux Kernel...
[10:19] <jorgesanjuan> EFI stub: Using DTB from configuration table
[10:19] <jorgesanjuan> EFI stub: Exiting boot services and installing virtual address map...
[10:19] <jorgesanjuan> L3c Cache: 8MB
[10:19] <lordievader> lbert: Does it work when you add  the p7p1:1 interface to the bridge?
[11:20] <LaserAllan> hey guys, I have a python script that Ive been running for a few days but for some reason it just refuses my connection to the interface every now and then and so i have to restart the script to amke it work any idea how i can resolve this?, it doesn't seem to be in the application itself
[11:27] <lordievader> How are you so sure it is not the script/application?
[11:28] <LaserAllan> lordievader: I have looked through the logs and I cannot find anytrhing, it basically jsut refuses my connection, i thought it oculd have something to do with the SSL cert at first but i switched SSL off and it made no difference
[11:28] <lordievader> It refuses the connection how?
[11:31] <LaserAllan> lordievader: When i go tht URL it basically only sxays "Connection Refused"
[11:33] <lordievader> That sounds more server side that client side, actually.
[11:33] <lordievader> What happens when you connect with something else at that time.
[11:35] <LaserAllan> lordievader: That i haven't tried
[11:35] <LaserAllan> I guess i should try connecting with my phone or something but i can confirm the screen is beeing killed becuase the applicaiton stops working
[11:37] <mdeslaur> nacc: please turn the build tests on in php7.0 in yakkety like I did for xenial. Look at my xenial package for the required changes to do so.
[11:50] <lordievader> LaserAllan: Err, I'd connect to the service from the same box.
[11:59] <LaserAllan> lordievader: Its no really meant for that my friends
[12:30] <lordievader> LaserAllan: The reason I suggest that is because that gives a fair test. Testing on a different box doesn't tell you anything about a possible problem.
[12:32] <coreycb> jamespage, hello there, the following are ready for promotion to mitaka-updates when you have a moment please: http://paste.ubuntu.com/18023208/
[12:36] <jamespage> coreycb, looking now
[12:44] <jamespage> coreycb, ok all synced - did a load of other security fixes at the same time
[12:44] <jamespage> horizon is the only outstanding afaict?
[12:44] <coreycb> jamespage, ok thanks.  yeah that could use a little more time to bake but it has been tested successfully, manually too.
[12:49] <jamespage> coreycb, I normally gate on the main SRU being accepted...
[12:50] <coreycb> jamespage, yep, it needs that too :)
[12:50] <jamespage> \o/
[13:09] <LaserAllan> lordievader: I am not sur ehow to do that
[13:25] <Strykar> Hi, I need to use Ubuntu 12-04 to cross compile, but I can't seem to install build-essential. I'm unsure what the error means - http://paste.ubuntu.com/18025404/
[13:33] <cpaelzer> sometimes unicode tries to make me angry as just now "dpkg-maintscript-helper is not dpkg−maintscript−helper (from online man page)"
[13:33] <JanC> Strykar: did you "apt-get update" on that machine?
[13:33] <Strykar> JanC, yes, update, then upgrade, then dist-upgrade
[13:35] <JanC> cpaelzer: sounds like a bug in the manpage and/or in the software that puts it online?
[13:39] <Strykar> JanC, apt-get update threw some errors, I thought they could be ignored - http://paste.ubuntu.com/18026026/
[13:42] <JanC> strange
[13:42] <lordievader> LaserAllan: Get a screen/tmux run the program in one screen and an netcat in the other, or something.
[13:42] <JanC> did you re-try that?
[13:42] <Strykar> JanC, its the latest ISO too
[13:42] <Strykar> JanC, I did retry update a few times yes
[13:46] <Strykar> JanC, should I try reinstalling again? :/
[13:46] <JanC> the files seem to be there (in a .gz & .bz2 compressed version)
[13:48] <Strykar> anything I could try before reinstalling?
[13:48] <JanC> still, it shouldn't really matter, I guess
[13:49] <JanC> oh wait, it does matter, it's not only source packages but also i386 binary packages
[13:49] <cpaelzer> Strykar: the issue you had while updating might be the reason
[13:49] <cpaelzer> Strykar: you can re-update - it is somewhat of a race between archive updates
[13:49] <cpaelzer> Strykar: it got iterative improvements over the years and is finally fixed in newer releases
[13:50] <JanC> well, they said they already tried that
[13:50] <cpaelzer> JanC: I read i tas "it was updated but it threw some errors"
[13:51] <cpaelzer> Strykar: did you get an apt-get update through without issues in the meanwhile and your original issue still persists?
[13:51] <Strykar> cpaelzer, not once
[13:52] <JanC> you could try using another mirror
[13:52] <cpaelzer> Strykar: it seemed to be a common issue in the past, but I joined the company later so I don't have the solution "just with me" - let me try to search for a good guide
[13:52] <Bert_2> tarpman: we have a new ldap/pam issue, we think, for some reason pam is reporting auth failure and then auth success (which freaks fail2ban out), we think it's to do with that we first to pam against local files and then ldap and that it has decided now to start logging the first failure besides to follow-up success http://termbin.derhaeg.be/bok3 any tips on what might be the cause?
[13:53] <cpaelzer> Strykar: does that make update work for you ? "sudo apt-get clean; sudo apt-get update"
[13:54] <Strykar> cpaelzer, nope
[13:55] <cpaelzer> Strykar: so still the hash sum mismatch ...
[13:56] <Strykar> cpaelzer, yes
[13:56] <JanC> I would try the main mirror to see if the Indian mirror is broken...
[13:56] <cpaelzer> Strykar: next escalation level would be "sudo apt-get clean; sudo rm /var/cache/apt/* /var/lib/apt/lists/*; sudo apt-get update"
[13:56] <cpaelzer> Strykar: throws away more of the old local content
[13:57] <Strykar> cpaelzer, wouldnt that be rm -rf?
[13:57] <cpaelzer> Strykar: yes it would
[13:57] <cpaelzer> Strykar: I was afraid while copying to create a desctructive command and removed too muhc :-/
[13:58] <cpaelzer> Strykar: the post here is similar to what I suggested and the second answer has the next level you could try if even the current one fails http://stackoverflow.com/questions/15505775/debian-apt-packages-hash-sum-mismatch
[13:59] <Strykar> cpaelzer, thank you! fixed, trying the build-essential and other packages now :)
[13:59] <cpaelzer> Strykar: great, enjoy it
[14:13] <Strykar> cpaelzer, JanC, looking good, tyvm
[14:28] <Bert_2> We have a new ldap/pam issue since our upgrade to 16.04, we think, for some reason pam is reporting auth failure and then auth success (which freaks fail2ban out), we think it's to do with that we first to pam against local files and then ldap and that it has decided now to start logging the first failure besides to follow-up success http://termbin.derhaeg.be/bok3 any tips on what might be the cause?
[14:36] <smoser> rbasak, http://paste.ubuntu.com/18028721/
[14:36] <rbasak> smoser: yeah, that's a libvirt bug I think.
[14:37] <rbasak> smoser: "virsh vol-delete --pool uvtool x-uvt-b64-Y29tLnVidW50dS5jbG91ZC5kYWlseTpzZXJ2ZXI6MTYuMDQ6YW1kNjQgMjAxNjA2MjU=" will fail the same way I reckon.
[14:37] <smoser> have we filed ?
[14:37] <rbasak> I don't think we figured out steps to reproduce. rharper mentioned this too.
[14:37] <smoser> indeed.
[14:37] <smoser> s$ virsh vol-delete --pool uvtool x-uvt-b64-Y29tLnVidW50dS5jbG91ZC5kYWlseTpzZXJ2ZXI6MTYuMDQ6YW1kNjQgMjAxNjA2MjU=
[14:37] <smoser> error: Failed to delete vol x-uvt-b64-Y29tLnVidW50dS5jbG91ZC5kYWlseTpzZXJ2ZXI6MTYuMDQ6YW1kNjQgMjAxNjA2MjU=
[14:37] <smoser> error: cannot unlink file '/var/lib/uvtool/libvirt/images/x-uvt-b64-Y29tLnVidW50dS5jbG91ZC5kYWlseTpzZXJ2ZXI6MTYuMDQ6YW1kNjQgMjAxNjA2MjU=': Permission denied
[14:38] <rbasak> uvtool makes a point of doing all volume management via libvirt. It doesn't mess with permissions ever.
[14:38] <rbasak> Except in setting up the pool originally in the postinst I guess.
[14:38] <rharper> smoser: the debdiff I shared certainly fixes it; but I didn't have a machine that could recreate the issue after uninstalling the fixed package
[14:39] <rbasak> As a workaround, you can delete the file by hand. libvirt tends to notice and sort itself out.
[14:39] <rharper> rbasak: right, it's exclusively a libvirt issue w.r.t ownership/permissions
[14:40] <smoser> rharper, well, i'm seeing it on digglet.
[14:40] <smoser> where is your debdiff ?
[14:40] <rharper> http://paste.ubuntu.com/18028922/
[14:41] <rharper> if you look at the patch, it basically tells libvirt to not setuid unless it really needs to
[14:47] <rharper> smoser: diglett is xenail/yakkety?  it should have a libvirt new enough with the fix =(
[14:48] <rharper> ah, in yakkety, not xenial
[14:49] <smoser> hm..
[14:49] <smoser> we dont have nfs there
[14:49] <smoser> is the commit just wrong ?
[14:50] <smoser> it says: NFS with root-squash is the only reason we need to do setuid/setgid
[14:50] <rharper> smoser: no, the logic for when to apply setuid was broken
[14:50] <rharper> they found it via nfs, but the logic was still broken
[14:51] <rharper> libvirt ended up dropping it's setuid bit when it still needed it
[14:51] <rharper> the logic clears up when libvirt actually needs it
[14:52] <smoser> ah. ok.
[14:52] <smoser> file bug for sru rharper ?
[14:52] <rharper> I think we have an existing bug
[14:53] <smoser> yeah, nubmer XXXXXX
[14:53] <smoser> :)
[14:53] <rharper> maybe not
[14:53] <rharper> smoser: why don't you ubuntu-bug libvirt (or uvtool) on diglett =)
[14:54] <smoser> ok
[14:55] <dahlia_> hello
[15:23] <adac> for some reasons after a apt-get dist-upgrade I get:
[15:23] <adac> grub-install: error: cannot find a GRUB drive for /dev/disk/by-id/ata-QEMU_HARDDISK_QM00005.  Check your device.map.
[15:23] <nacc> mdeslaur: yep, will do and will add to the delta. Is that something that it would make sense to send to Debian?
[15:24] <adac> any ideas on how I re-install the grub correctly? I fear that my server will not come up at the next boot
[15:24] <mdeslaur> nacc: I think so...I think it just got disabled because it needed a bit of work to work with the new mysql version
[15:26] <rbasak> rharper, cpaelzer, magicalChicken, nacc, jgrimm: do you have any sponsorship outstanding for assigned bugs? I'm trying to clear up. Apart from the existing LP MPs I have in https://code.launchpad.net/~racb/+activereviews ?
[15:26] <nacc> mdeslaur: ack, i'll verify
[15:26] <jgrimm> rbasak, i'm good
[15:27] <nacc> rbasak: no, i'm waiting on testing results for all of mine right now, i think
[15:28] <rharper> rbasak: the strongswan one was pre-xenial; that's been closed now; should I reject the MP ?
[15:28] <magicalChicken> rbasak: Not atm, I'm testing 1534538 right now though, so I will have in a little while
[15:28] <rbasak> rharper: yes please
[15:30] <cpaelzer> rbasak: no I'm good - all are either completed, on your list, or not yet ready
[15:31] <rbasak> OK. Thanks all!
[15:39] <rbasak> nacc: do you want to import nss for jgrimm or shall I?
[15:39] <nacc> rbasak: if you could, that'd be great
[15:40] <nacc> rbasak: still catching up on e-mail and the various bugs from last night
[15:40] <jgrimm> thanks!
[15:40] <rbasak> nacc: also I wonder if it's time that we improved the import side of things. Since at the moment everyone seems to be generally happy with the quality of the import. Maybe we should start automating answering requests or something.
[15:40] <rbasak> ack, I'll import.
[15:41] <nacc> rbasak: yep, i was holding off until we decided what to do about uploads for certain
[15:42] <nacc> mdeslaur: just checking, i don't think there was a changelog entry for enabling the tests, was there?
[15:42] <rbasak> nss import in progress.
[15:42] <mdeslaur> nacc: last three lines of this one https://launchpad.net/ubuntu/+source/php7.0/7.0.4-7ubuntu2.1
[15:43] <nacc> mdeslaur: bah, i was grepping for 'tests' :)
[15:43] <nacc> mdeslaur: sorry for the noise
[15:43] <mdeslaur> heh, np :)
[15:48] <nacc> mdeslaur: one last question on review: is moving from ?= to := in the variable assignments intentional? doesn't htat mean if a user exports the environment variables, they won't override the makefile?
[15:48] <nacc> s/makefile/rules file/
[15:51] <mdeslaur> nacc: I was hitting an issue where using ?= would re-evaluate the statement each time it was used, which means the port was changing between when mysql was started and when the test was run
[15:52] <nacc> mdeslaur: oh weird, ok
[15:52] <mdeslaur> nacc: perhaps there's a better way to fix that, but I'm not sure
[15:53] <nacc> mdeslaur: that's fine, just wanted to understand for when i send to debian :)
[16:21] <magicalChicken> rbasak: 1519120, waiting for decision on whether or not it is okay to pull vlan into cdimage
[16:32] <Tokolytika> hi there :)
[16:33] <Tokolytika> could anyone give me an advice concerning the partitioning scheme for a webserver (lvm)?
[16:35] <Tokolytika> thought to make separate lv's for /, /usr, /home, /var, /var/log, /var/mail, and /tmp
[16:35] <Tokolytika> too much?
[16:39] <nacc> would you even need to make a separate /home if it's a webserver?
[16:40] <Tokolytika> good point...
[16:41] <nacc> Tokolytika: depends on whatyou're serving, i guess, and if there are per-user spaces (and if users have access)
[16:44] <Tokolytika> primarily i like to run some kind of groupware on it, like egroupware or similar... and maybe nagios
[16:46] <Tokolytika> i think /home isn't really necessary... but maybe i should seperate the db?
[16:47] <nacc> Tokolytika: that might make sense, i really don't know; was only comenting on /home :)
[17:02] <jayjo> I'm trying to use git on an aws server, and I'm getting the error "Problem with the SSL CA cert (path? access rights?)" Can I reinstall the CA Certs?
[17:41] <HankTheAi> Hello Ubuntu-server channel, I have a few systems that have onboard support for Intel Rapid Storage. However, I am trying to determine what the best solution would be for setting up RAID using onboard RAID controllers. Is there a solution built into the Ubuntu 16.04 LTS release that would work similar to how Intel Rapid Storage does on top of Windows Server?
[17:42] <HankTheAi> I also have SSD's in each system. Some with M.2 Samsung SSD, and some with SATA based SSD drives. Would something like bcache be recommended to cache data to the faster SSD storage first, and then automatically offload it to the larger spinning disks?
[17:43] <HankTheAi> lastly, would it be a bad idea to use both bcache in conjunction with Intel's Rapid Storage for Linux software RAID on the same system?
[17:44] <HankTheAi> I know this is a lot of questions, but I greatly appreciate the help. I tried to ask for help in the main Ubuntu channel and that did not go to well for this topic related to more complicated storage configurations.
[17:51] <nRy2> people in #ubuntu channel are acting dumb.
[17:52] <nRy2> any signs of intelligent life forms in this channel?
[17:52] <nRy2> ;-)
[17:52] <nacc> nRy2: do you have a question?
[17:52]  * tgm4883 sighs
[17:53] <tgm4883> nRy2: you catch more flies with honey than vinegar
[17:54] <specialedge> try !patience
[19:28] <nRy2> What is the best Ubuntu tool for checking storage IOPS?
[19:28] <nacc> nRy2: iostat ?
[19:29] <jrwren> i don't know of a best tool. i like dstat and netdata depending on what I want to see.
[19:29] <nRy2> Is it possible to have TOP read a live storage IOPS, read/write, and other storage performance info?
[19:29] <jrwren> do you want iotop?
[19:29] <nRy2> can I pipe iostat into TOP?
[19:29] <nacc> nRy2: do you mean `top` when you say "TOP"?
[19:30] <nRy2> nacc: yes
[19:30] <magicalChicken> nRy2: iotop is like top for io
[19:30] <nacc> nRy2: i've never tried piping anything to top, i think you'd just use iotop for that
[19:30] <nRy2> magicalChicken: cool, thanks!
[19:31] <jrwren> top accepts stdin and has commands. piping data to it would trigger those commands.
[19:31] <jrwren> pipes aren't magic.
[19:31] <nRy2> hmm, actually is there a way to get the raw data from Ubuntu via CLI? I am developing a web service based UI that I want to pipe the data to.
[19:32] <nRy2> jrwren: you read my mind! thanks ;-)
[19:32] <nacc> jrwren: right, i meant taking arbitrary data like iostat outputs and having top parse it, that's not what top is doing
[19:32] <nRy2> sometimes I type too fast, too strong coffee, too much ADHD or something like that...before seeing replies. LoL
[19:33] <jrwren> i'm sorry. I cannot follow this conversation.
[19:35] <sarnold> nRy2: sure, there's loads of tools that provide graphs on the web from performance data; munin, zabbix, netflix's vector, influxdb, BELK, .. there's practically too many. it makes it hard to choose one.
[19:36] <nRy2> sarnold: are there any that also provide GPU performance stats? In addition to RAM, CPU, Storage IOPS/performance monitoring of real time data, I am also very interested in the GPU data for my app requirements.
[19:37] <sarnold> nRy2: I've never owned a GPU worth looking up numbers for :) hehe
[19:37] <sarnold> nRy2: most of those tools make it insanely easy to write your own collectors though; if there's some way you can get numbers out of yours, most will support it.
[19:38] <nRy2> Some of the API's are garbage such as the AWS EC2 hardware performance real-time monitoring. I confirmed this past week that EC2's performance information is not accurate at all. At least on their most expensive HPC instance types.
[19:38] <sarnold> nRy2: here's an example collector for a tool that I was looking at jjust yesterday https://github.com/dagwieers/dstat/blob/master/plugins/dstat_zfs_zil.py
[19:40] <nRy2> Netflix vector sounds interesting if they rebuilt it from their AWS days. I know that Netflix has rebuilt their entire new non-AWS platform but I wonder if they are still using some of the same performance monitoring. It is amazing that they moved away from the AWS stronghold they were locked into for most of their history.
[19:41] <nRy2> sarnold: have you come across any good PHP based ones?
[19:42] <nRy2> I am building on Zend Framework.
[19:43] <sarnold> nRy2: heh, normally I use 'php' as a warning label :) though I'm afraid that's harder to do these days..
[19:44] <nRy2> ;-)
[19:47] <nRy2> I know a lot of people seem to give PHP a bad rap. My dev team convinced me to build on Zend/bootstrap and I can see were it is more difficult than some other frameworks. I love using it on top of Ubuntu Server as it has performed flawlessly for us; at least on our own internal project.
[19:48] <nRy2> IMHO, PHP at least with the ZendF2 platform is a great technology.
[19:48] <sarnold> I don't doubt that dedicated and determined engineers can write good software in php
[19:48] <nRy2> sarnold: thanks for the warning, but we are already heavily invested into Zend/PHP for years now. With that disclaimer, are there any PHP performance monitoring libs that you might be able to suggest?
[19:49] <sarnold> it just feels like the bar is automatically set a bit closer to "fail" with php.. maybe php 7 will improve things, it feels a hell of a lot saner.
[19:50] <sarnold> nRy2: not really, sorry. the 'nicest' things seem to be e.g. serving json to users and letting browser-side javascript sort it out, but damned if I can't get my head around JS in the slightest. :/
[19:50] <nRy2> Zend Framework does help as they have a lot of great tools available...you know to make PHP easier to work with.
[19:50] <sarnold> nRy2: here's something a pal put together to let him feed json streams to clients https://github.com/ahupowerdns/metronome/ -- but it's C++ so not immediately useful -- but the client-side portions may be instructive?
[19:51] <nRy2> yeah, the funny thing is that the only time we ever ran into any issues with Zend/Php on Ubuntu Server, is when we tried to integrate other non PHP libraries. That is when all hell breaks loose for sure.
[19:52] <sarnold> hmm, funny, I'd have expected cffi support to make that tolerable these days.
[19:53] <nRy2> I think the other non-php code is not stable.
[19:53] <sarnold> ah
[19:53] <nRy2> but it is AWS API based so it should be.
[19:53] <nRy2> shell scripts running on Ubuntu do not jive well with Zend.
[19:54] <nRy2> don't ask me why, I just know that it did not like me.
[19:55] <lamont> cyphermox: around?
[19:55] <sarnold> plausible. it's also best to make monitoring tools long-lived processes that do all the collection themselves rather than spawning a million shell utilities. collectd is pretty cool example of that, one nice C executable that runs forever and does the collection..
[19:55] <cyphermox> lamont: what's up?
[19:55] <lamont> cyphermox: wondering about how 1229458 is progressing (iz blocker)
[19:56] <nRy2> we were supposed to take the shell scripts and convert them to PHP, but our team member who wrote those complex scripts kept saying that Shell was fine, while another engineer kept saying that it was a bad idea not make them into PHP. Two years later the app broke because of the shell scripts, but I think that is because of AWS updating their platform. We will never use shell scripts again!
[19:57] <sarnold> shell's easy to smack something together
[19:57] <sarnold> and if they run every minute or something, meh. that's not terrible overhead.
[19:57] <nRy2> I will look into htop and variants mentioned that are native to Ubuntu. Maybe I can port them in an effort to not make things much more complex than they need to be.
[19:58] <sarnold> but most data gets interesting when you collect it every second or similarly high resolution, and you certainly don't want to be spawning a million processes just to check how things are going :)
[19:58] <nRy2> sarnold: thanks for the help! ;-)
[19:58] <cyphermox> lamont: I played with it a bit, until I bricked my laptop
[19:59] <nRy2> I have a lot to dig into now...R+D..blackboard, back back back........
[20:00] <cyphermox> lamont: I had a candidate git commit to backport; but I was unwilling to upload it before doing some testing
[20:02] <lamont> cyphermox: it's entirely possible that one of us may be able to help with testing, if that's still an issue later this week
[20:02] <lamont> (he says volunteering team members while he goes on vacation for a very long weekend)
[20:02] <cyphermox> who volunteers?
[20:02] <cyphermox> I'll build it in a PPA nao.
[20:03] <lamont> throw it at me... I'll almost certainly poke at it tomorrow
[20:03] <cyphermox> ok
[20:03]  * sarnold wonders who is going to be volunteered to brick their laptop :)
[20:04] <cyphermox> sarnold: laptop bricking was an unrelated incident, most likely due to sucky thinkpad firmware.
[20:04]  * lamont plans to possibly unbrick some vms on an ipv6-only subnet
[20:04] <lamont> sarnold: if you want to, look me up sometime when you have your laptop, and I have a brick. D:
[20:04] <sarnold> cyphermox: oh yes I'm sure firmware is -great- today :) hehe
[20:05] <sarnold> lamont: hehe
[20:05] <cyphermox> meh. it's hard enough to break again, I tried
[20:05] <lamont> just stay away from sarnold's rogue ntp server with certain devices until you upgrade.
[20:06] <sarnold> don't you want to relive the birth of the unix universe _every day_!? 00:00:00 jan 1 1970 was such a happening time!
[20:06] <lamont> lol
[20:07] <lamont> heat-birth of the universe, eh?
[20:07] <sarnold> and, in 2038, again the heat death :) heh
[20:07] <lamont> ah, good point
[20:07]  * lamont is glad they fixed that
[20:07] <lamont> and that they push so aggressively
[20:18] <arooni> when my ubuntu 14.04 lts vps appears to spontaneously reboot (serving a rails app/mysql/nginx); what are logs i should check?
[20:30] <cyphermox> lamont: are you familiar with the fun of self-signing grub or enrolling keys?
[20:30] <cyphermox> (since you want this for EFI)
[20:33] <lamont> cyphermox: clueless
[20:33] <lamont> maybe I'll nag the submitter into testing it. :D
[20:37] <akincer> apt-get seems to be dog slow across our organization to pull data over several cities with different internet providers with ample circuits. Any known issues?
[20:38] <akincer> I should say these are 14.04 boxes
[20:43] <akincer> nevermind. Networking just confirmed there are firewall issues blocking it
[21:51] <lamont> cyphermox: presumably there's a wiki page or such on the process?
[22:04] <jge_> probably not the best channel to ask this but any of you know how I can use a proxy with transmission?
[22:05] <nacc> jge_: i'd ask in #ubuntu, probably
[22:41] <cyphermox> lamont: we're updating one to make it easier to follow
[22:42] <Bert_2> We have a new ldap/pam issue since our upgrade to 16.04, we think, for some reason pam is reporting auth failure and then auth success (which freaks fail2ban out), we think it's to do with that we first to pam against local files and then ldap and that it has decided now to start logging the first failure besides to follow-up success http://termbin.derhaeg.be/bok3 any tips on what might be the cause?
[22:42] <Bert_2> tarpman: ^
[22:49] <sarnold> Bert_2: hmm; all those failures are from pam_unix; do you have local users on these systems? I wonder if a /etc/pam.d/sshd that doesn't include the unix PAM module might be more appropriate?
[22:49] <sarnold> Bert_2: (I really haven't had to fight pam in earnest, so that's more a question than a suggestion -- or, in other words, if you try it, _please_ keep a root shell open in order to fix any issues :)
[23:08] <Bert_2> sarnold: well, the only local use we use is the root user, to be sure we can get in if LDAP fails


[02:01] <MichaelP> 14.10 had some problems on update... qml-module-org-kde-extensionplugin not being installed... Had to install by it self
[02:01] <waddlesplash> yes
[02:01] <waddlesplash> well, apt-get install -f worked
[02:01] <MichaelP> funny how one package can cause so many problems...
[02:02] <valorie> the longer the name (and sometimes shorter the name...) the more trouble it can cause
[02:02] <MichaelP> now it done setting up... reboot see if eveything works
[02:02] <valorie> but anything with 'org-kde' in the name is gonna be sort of important
[02:03] <MichaelP> yeah
[02:03]  * valorie boots into neon5 for some testing
[02:09] <MichaelP> that qml-module-org-kde-extensionplugin ... was problem dophin not seeimg my usb drive... now it there.... now plug tv back in.. see if it gets full screen... it was only giving panel on 1/2 the screen size
[06:18] <soee> good morning
[06:23] <lordievader> Good morning.
[09:16] <Riddell> apachelogger: did you come up with a good short name for gpl+ev licence?
[09:16] <sgclark> morning
[09:17] <Riddell> it's sgclark!
[09:17] <sgclark> :)
[09:17] <Riddell> it must be pre-morning for you
[09:18] <sgclark> so is there a git version of bzr-buildpackage-ppa? or how does this work now?
[09:18] <sgclark> hehe yeah
[09:19] <sgclark> 2:18 am but I went to bed early, so it's good.
[09:20] <Riddell> sgclark: I just made one yesterday in kubuntu-automation scripts
[09:20] <Riddell> git-buildpackage-ppa
[09:20] <Riddell> sgclark: what are you looking to package?
[09:20] <sgclark> cool thanks
[09:20] <sgclark> I was going to help with plasma if it is still needed
[09:20] <Riddell> yep, let me write up on the notes page where I'm at
[09:21] <Riddell> sgclark: how's 14.04.1 in trusty?
[09:21] <sgclark> was done, let me double check
[09:23] <sgclark> yep, Riddell: green minus one active depend, but we dropped active
[09:23] <Riddell> https://notes.kde.org/p/kubuntu-ninjas-frameworks Plasma 5.0.95 updated
[09:24] <Riddell> sgclark: great, I'll copy over to ~kubuntu-ppa/backports
[09:24] <sgclark> ty, will start on plasma
[09:29] <Riddell> what we don't have is an equivalent of knextbzr
[09:29] <Riddell> knextgit should clone then checkout the right branch
[09:29] <Riddell> oh and be written in python, just to watch harald squirm :)
[09:29] <sgclark> lol
[09:56] <apachelogger> Riddell: I had multiple suggestions in debian-qt-kde :P
[09:57] <apachelogger> Riddell: hottest contenders IMHO are 'GPL-KDEeV' or 'GPL-2 or GPL-3 or GPL-KDEeV'
[09:58] <apachelogger> personally I would go with former because IIRC from a spec POV both versions are $random as as such are not considered a standard license
[10:01] <Riddell> groovy, GPL-KDEeV it is
[10:04] <sgclark> interesting, Riddell: kio-extras depends on a function added to kio in 5.3.0, which afaik has not been released has it?
[10:04] <Riddell> sgclark: aah fooey :(
[10:05] <apachelogger> Riddell: are you adjusting master to fix the lintians?
[10:07] <Riddell> sgclark: kwin will be the same, we may need to skip over those ones for now
[10:07] <sgclark> ok
[10:07] <Riddell> sgclark: sorry that's my upstream-hat-on fault
[10:07] <sgclark> np
[10:08] <Riddell> apachelogger: I'm adjusting kubuntu_utopic_next
[10:08] <Riddell> of plasma packages
[10:10] <apachelogger> Riddell: ok
[10:10] <apachelogger> going to get merges going against that then
[10:10]  * apachelogger actually wonders how to best automate merges from multiple different branches
[10:54] <apachelogger> Riddell: which repo already has a next branch?
[10:54] <apachelogger> or perhaps the question is... why do I look at repos and they have none? ^^
[10:55] <Riddell> apachelogger: all the plasma ones do
[10:55]  * sgclark is very confused
[10:55] <apachelogger> hm
[10:55] <sgclark> master does not match this kubuntu_utopic_next, is that right?
[10:55] <apachelogger> Riddell: computer says no
[10:55] <Riddell> sgclark: right, I'm working with kubuntu_utopic_next
[10:55] <sgclark> which alos does not match what is in ppa
[10:56] <Riddell> kubuntu_utopic_next should match ppa
[10:56] <sgclark> ok
[10:56] <apachelogger> Riddell: something is weird in jenkins
[10:56] <apachelogger> nevermind me
[11:16] <BluesKaj> Hiyas all
[11:17] <sgclark> hiyas
[11:17] <soee> hiho
[11:17] <soee> sgclark: working on P5.1b ?
[11:18] <BluesKaj> what's new today, sgclark?
[11:18] <sgclark> well, trying
[11:18] <sgclark> Riddell: I need a git for dummies. I can't seem to push to a branch. I only have experience with working with master. and nothing is working
[11:19] <soee> iv seen several pacvkages faild to build in staging
[11:19] <soee> git push -u origin development :D
[11:20] <soee> this is how i push my PHP code to devel branch -.-
[11:20] <sgclark> Riddell: also that git-buildpackage-ppa is erroring with missing files and debsign wants your key. Not sure what is wrong there, this is a new desktop, perhaps I missed a config setting somewhere
[11:21] <sgclark> soee: not sure how far I will get, some packages depend on frameworks 5.3.0 which doesn't exist yet.
[11:23] <soee> sgclark: 5.3.0 was not released ort just dont get into Kubuntu ?
[11:23] <Riddell> sgclark: got this in ~/.gitconfig ? http://paste.kde.org/pemfrk8wi
[11:23] <Riddell> and can you ssh in ?
[11:23] <Riddell> (with the right username)
[11:23] <sgclark> soee: tried your command, still get everything up to date, yet git diff says otherwise
[11:24] <Riddell> don't run soee's command that uses a different branch name
[11:24] <Riddell> sgclark: can you ssh<EMAIL_ADDRESS>?
[11:24] <Riddell> and run  group  it should tell you   jriddell-guest pkg-kde scm_pkg-kd
[11:24] <sgclark> I used kubunut_utopic_next
[11:24] <soee> sgclark: mine was example how i work with git but my personal codes, this has nothign to do with yours
[11:25] <BluesKaj> will KF5 and plasma5  remain optional in the 14.10 official release?
[11:25] <sgclark> Riddell: yes I can ssh in
[11:25] <Riddell> BluesKaj: yes
[11:26] <BluesKaj> Riddell, ok, thanks
[11:26] <sgclark> group: command not found
[11:27] <Riddell> sgclark: groups
[11:27] <sgclark> sgclark-guest pkg-kde scm_pkg-kde scm_sepwatch
[11:27] <Riddell> scm_sepwatch ? elite!
[11:27] <Riddell> anyway that looks fine
[11:28] <Riddell> sgclark: got ~/.gitconfig set up ?
[11:28] <sgclark> yeah that is set
[11:29] <Riddell> sgclark: groovy, so you have a branch?
[11:29] <Riddell> well a git repo clone ?
[11:30] <sgclark> git clone debian:plasma/libksysguard
[11:30] <sgclark> git checkout kubuntu_utopic_next
[11:31] <Riddell> looking good
[11:31] <Riddell> you've made a commit ?
[11:31] <sgclark> git diff shows my changes, but all push attempts says up to date.. so what is the push command?
[11:31] <sgclark> commit... lol duh, thanks
[11:32] <Riddell> commit is a two stage process in git too
[11:32] <Riddell> git add mychangedfile
[11:32] <Riddell> git commit -m "change mychangedfile"
[11:33] <Riddell> or you can go  git commit -a  to commit all modified files
[11:33] <Riddell> git log  to check it's been commmitted
[11:33] <Riddell> then   git push  should do the right thing to send it to git.debian.org
[11:35] <apachelogger> ehm
[11:35] <apachelogger> 99% of the time you want debcommit or debcommit -a
[11:35] <apachelogger> that is to say, if you do not use debcommit you'll get in a world of trouble with both debian and me
[11:36] <apachelogger> rule of thumb: did the changelog change? -> use debcommit
[11:36] <sgclark> ugh
[11:36] <Riddell> apachelogger: what's the difference?
[11:36] <sgclark> well too late for this one. noted for next time
[11:36] <apachelogger> debcommit will use what you wrote in debian/changelog
[11:37] <sgclark> ok
[11:37] <sgclark> I copy and pasted lol, debcommit sounds easier
[11:37] <apachelogger> *nod*
[11:37] <sgclark> now onto a debsign problem...
[11:38] <apachelogger> also when tagging I suppose everyone has to use debcommit to get the tags right
[11:38] <apachelogger> I did definitely see weird perl rejections hooks on the server side
[11:38] <apachelogger> oh yeah
[11:38] <Riddell> >cat ~/.devscripts
[11:38] <Riddell><EMAIL_ADDRESS>[11:38] <apachelogger> shadeslayer: there's a gigantic perl git hook on the server that does all sorts of weird shit :P
[11:38] <Riddell> sgclark: set that for your e-mail, otherwise it'll use whatever is in the latest debian/changelog
[11:38] <apachelogger> I didn't understand half the code
[11:38] <apachelogger> so I :q!
[11:39] <sgclark> did not exist. fixed, thanks
[11:39] <Riddell> sgclark: and I also get lots of "dpkg-source: warning: ignoring deletion of file" on running git-buildpackage, but I ignore them and it seems to be ok
[11:39] <apachelogger> sgclark: you could also define -kID or -kYourName or -kPartOfYourNameAssumingNoneElseInTheKeyringHasThatName
[11:40] <apachelogger> dpkg-buildpackage -s -kSitter is what I do, mind you I do have multiple keys for different purposes, so I kinda have to be explicit ^^
[11:40] <Riddell> sgclark: git-buildpackage seems to prefer you to have one of those weird branches with the upstream source in the branch too so I'm guessing this is just a bug from that preference
[11:40] <sgclark> ok
[11:40] <apachelogger> Riddell: you can make it not do that
[11:40] <apachelogger> unfortunately I lost my zsh_history for some reason
[11:40] <apachelogger> so I cannot tell you what pile of arguments you need to make it behave as bzr buildpackage
[11:41] <apachelogger> somthing to figure out on a rainy afternoon I suppose
[11:41] <Riddell> "git-buildpackage", "--git-ignore-branch", "--git-no-create-orig", "--git-ignore-new", "-S"   is what git-buildpackage-ppa uses
[11:41] <apachelogger> nah, that sounds more liberal than what I had
[11:42] <Riddell> you republican you, go back to the NRA
[11:42] <apachelogger> pft
[11:42] <apachelogger> it's important
[11:42] <apachelogger> if the stuff is too liberal it will take dirty bits from the repo, and we most certainly don't want uncommited nonesense in an upload
[11:42] <apachelogger> so caution is very much of use here
[11:43] <apachelogger> going to attempt a CI automerge rollout
[11:43] <sgclark> ok, almost 3 hours later.. one package done heh
[11:44] <Riddell> yay!
[11:44] <sgclark> lol
[11:44] <apachelogger> what does need doing anyway?
[11:44] <Riddell> plasma 5.0.95
[11:44] <apachelogger> AFAIK only breeze and kwin and maybe ksysguard should make problems
[11:44] <apachelogger> Riddell: yeah, but it's been mostly CId
[11:44] <sgclark> hmm, I think we are stuck on the 5.3.0 frameworks issue?
[11:44] <apachelogger> there shouldn't be any big issues
[11:44] <Riddell> two new packages
[11:45] <apachelogger> oh yeah, the frameworks bit in kwin probably is a biggy
[11:45] <Riddell> some new translations
[11:45] <Riddell> and kwin depending on frameworks 5.3
[11:45] <sgclark> kio-extras as well
[11:46] <Riddell> I don't suppose we can only update to the git versions of the required frameworks?
[11:46] <Riddell> the problem with this issue is it may end up with plasma schedule moving forward two weeks which means it can't be included in kubuntu
[11:53] <Riddell> hi shevron
[11:54] <shevron> hi Riddel
[11:56] <shadeslayer> why does frameworkintegration dep on oxygen?
[11:56] <shadeslayer> a build dep that is
[11:56] <shadeslayer> makes ENOSENSE
[11:57] <shadeslayer> wat
[11:57] <shadeslayer> blame shows me
[11:57] <shadeslayer> ok, no, I just moved things around
[11:57] <shadeslayer> Riddell: ^^ changelog mentions you
[11:58] <shadeslayer> Riddell: a90ac25f803889b75b7f7029baf9b3b611a77300
[12:00] <shadeslayer> and the actual runtime dep is missing ofcourse
[12:01] <Riddell> shadeslayer: not sure, check it builds without and remove if you want
[12:02] <shadeslayer> well
[12:02] <shadeslayer> Riddell: https://launchpadlibrarian.net/186046131/buildlog_ubuntu-utopic-amd64.frameworkintegration_5.2.0-0ubuntu1_UPLOADING.txt.gz
[12:02] <shadeslayer> :p
[12:02] <shadeslayer> it doesn't actually find oxygen
[12:03] <Riddell> hmm, that looks wrong
[12:08] <shadeslayer> apachelogger: what's the policy to update changelogs in debian ?
[12:09] <apachelogger> there is none
[12:09] <shadeslayer> so .. uh ..
[12:09] <apachelogger> what policy are you looking for anyway?
[12:09] <apachelogger> you make a change, you put it into changelog
[12:09] <apachelogger> unless it's kubuntu_unstable then you don't put it in a changelog because it currently makes things explode xD
[12:11]  * apachelogger is slightly scared of deploying the automerge change
[12:24] <Riddell> groovy, kio from git seems to compile and that makes kio-extras happy
[12:26] <Riddell> sgclark: 4.14.1 in kubuntu-ppa/backports tried on an ec2 and all installs and runs
[12:27] <Riddell> Pali: you may want to backport that to precise now ↑
[12:27] <sgclark> yay
[12:27] <tazz> o/
[12:27] <alvin> yay
[12:28] <Riddell> who was saying there were questions on google+ ?
[12:30] <Riddell> soee: you were? where about were those g+ queries?
[12:30] <soee> Riddell: what questions ?
[12:31] <soee> 4.14..1 ?
[12:31] <Riddell> soee: yeah
[12:31] <soee> Riddell: https://plus.google.com/110534757969145694671/posts/MMTeiYCudY4
[12:33] <Riddell> g+ really confuses me, we have a Kubuntu page, and that is a related Kubuntu community?
[12:37] <soee> Riddell: i think this is the officail community page
[12:37] <soee> it is created by Kubuntu user
[12:42] <Riddell> mm I see, not very obvious at all
[12:45]  * sgclark blogs..
[12:54] <Riddell> sgclark: you should probably also put 4.14.1 on kubuntu.org and slap it onto social media bits
[12:57] <sgclark> ok
[13:05] <soee> well it sthe only one im using actively on g+
[13:15] <sgclark> Riddell: g+, facebook done. I can't access twitter, you sent me the encrypted password, but failed to give me your key lol
[13:16] <Riddell> sgclark: it uses your key!
[13:16] <Riddell> you're not getting my private key, it's my precious
[13:16] <sgclark> hmm, it says unable to decrypt
[13:16] <sgclark> right, public key I think
[13:28] <SourBlue> aaah encryption :D
[13:29] <SourBlue> do you guys know a good gui to manage sql databases?
[13:37] <alvin> SourBlue: SQL Squirrel ( http://www.squirrelsql.org/ )
[13:38] <alvin> That's what I'm using on Kubuntu. There's no package though.
[13:47] <SourBlue> Thank you
[14:01] <shadeslayer> Riddell: all of these http://anonscm.debian.org/cgit/pkg-kde/plasma have the wrong maintainer
[14:01] <shadeslayer> should be : Maintainer: Debian/Kubuntu Qt/KDE Maintainers<EMAIL_ADDRESS>[14:01]  * shadeslayer will fix
[14:03] <Riddell> shadeslayer: yeah I noticed that earlier, thanks for fixing
[14:03] <Riddell> shadeslayer: also wrong Vcs fields
[14:05] <shadeslayer> mhm
[14:43] <alvin> Ah, there's my mail again. Thanks people.
[14:43] <apachelogger> Riddell: breeze-qt4 has neither kubuntu_unstable nor kubuntu_utopic_next branches
[14:47] <Riddell> apachelogger: sorted
[14:53] <sgclark> Riddell: seems we stuck at the frameworks version problem, did you decide what to do?
[14:54] <Riddell> thowing up a git snapshot of kio now
[14:54] <Riddell> sgclark: do you know what else kwin wants?
[14:54] <sgclark> no clue, didn't look after you said it will have same problem
[14:57] <sgclark> Riddell: kf5config, kf5configwidgets, kf5coreaddons, kf5crash, kf5globalaccel, kf5i18n, kf5init, kf5notifications, kf5service, and and good grief, pretty all of frameworks
[14:58] <sgclark> kf5plasma, kf5widgetaddons, kf5windowsystem
[15:03] <Riddell> wibble
[15:05] <Mamarok> Riddell: you will like this: https://www.youtube.com/watch?v=0YBumQHPAeU
[15:07] <Riddell> aah at last we can parody the posh boys in government, maybe that'll bring down the state
[15:09] <Riddell> shadeslayer: your cmake expertese is needed in libksysguard which installs a dbus file for kauth into /usr/etc
[15:10] <shadeslayer> moment
[15:15] <sgclark> Riddell: I have to leave for one hour, please ping me if there are things that need doing when I get back.
[15:16] <Riddell> sure
[15:24] <Riddell> looks like kwin just needs kwindowsystem updated so I'll throw up a git snapshot of that too
[15:25] <apachelogger> ehm, why don't we not ship kwin beta?
[15:27] <Riddell> we need to package it now to get the kubuntu-plasma5 image in a workable state, otherwise there's bugs I won't be able to fix
[15:35] <apachelogger> Riddell: does plasmashell require the new kwin?
[15:36] <Riddell> dunno, probably not
[15:36] <apachelogger> why would we need to spend time on making the beta kwin build then?
[15:36] <apachelogger> could just as well go with stable kwin and bump kwin once kf5 is out
[15:37] <Riddell> who knows what bugs might not be uncovered by that, there's a reason we have betas, unlike frameworks we are not perfect in plasma land
[15:38] <apachelogger> Riddell: I'll argue that the plasma team should make sure things build with released stuff then
[15:38] <Riddell> if I see the plasma release manager I'll be sure to tell him
[15:38] <apachelogger> this way every distro gets to spend their own silly effort on making it build
[16:09] <Riddell> E: kinfocenter source: no-human-maintainers  eh?
[16:09] <Riddell> shadeslayer: lintian doesn't like that you've taken away the humans
[16:09] <Riddell> "The Maintainer address for this package is a mailing list and there are no Uploaders listed. Team-maintained packages must list the human maintainers in the Uploaders field."
[16:10] <shadeslayer> Riddell: ah yeah, I guess it's complaining about Maintainers
[16:10] <shadeslayer> Riddell: mind fixing that?
[16:10] <Riddell> meh whatever, I'll override it in kubuntu-automation
[16:10] <shadeslayer> also, apachelogger is going to come at me with a club now
[16:10] <shadeslayer> because I probably made all of his ci red
[16:10] <Riddell> uh oh
[16:12]  * shadeslayer hides
[16:22] <apachelogger> yellow
[16:23] <apachelogger> oh
[16:23] <apachelogger> indeed red
[16:23] <apachelogger> cool beans
[16:23] <apachelogger> someone fix it
[16:27] <Antisound_> hi guys!
[16:27] <Antisound_> Is it possible to install the Plasma 5.1 beta already?
[16:28] <Riddell> hi Antisound, nope we're still packaging it, helpers welcomed http://qa.kubuntu.co.uk/plasma-status/build_status_5.0.95_utopic.html
[16:29] <Antisound_> Riddell: how can I help
[16:29] <Antisound_> ?
[16:30] <Riddell> Antisound_: become an elite kubuntu ninja and fix the packages :)
[16:30] <Antisound_> Riddell: sounds like hard work ;-)
[16:30] <Riddell> hard but rewarded with free hugs and irn bru
[16:31] <Riddell> testers and bugfixers also needed
[16:31] <Antisound_> Riddell: how much time is estimated for the packaging?
[16:31] <sgclark> Riddell: ok I am back, what else needs doing?
[16:32] <Riddell> Antisound_: plasma 5.1 beta I hope to get done by tomorrow
[16:32] <Antisound_> Riddell: ok. Thx!
[16:33] <Riddell> sgclark: just libnm-qt needs a copyright file fix
[16:33] <Antisound_> Riddell: i would love to help but i think i'm not such a "geek"  ;-)
[16:33] <Riddell> then it's waiting on kwin to compile to unblock the rest
[16:34] <sgclark> ok
[16:34] <sgclark> Riddell: how are we fixing the space error?
[16:35] <Riddell> sgclark: I'm using GPL-KDEeV or LGPL-KDEeV
[16:35] <sgclark> ok sounds good
[16:35] <Riddell> which seems to appease the lintian gods
[16:45] <Riddell> ** community council meeting in 1 hour 15min
[16:50] <sgclark> that isn't me right?
[16:52] <sgclark> Riddell: something is not right about libmm-qt. I noticed the fix was already in git, but not in ppa, I tried to build and put ppa2 up but it complains that orig.tar does not match
[16:57] <shadeslayer> most interesting https://bugs.launchpad.net/ubuntu/+source/kwalletmanager/+bug/1309955
[17:05] <valorie> isn't the CC meeting now?
[17:08] <valorie> according to http://fridge.ubuntu.com/calendars/fridge/ it is, but nobody is there
[17:14] <shadeslayer> do you guys want me around?
[17:14] <shadeslayer> because I wanted to leave in 20 minutes
[17:18] <valorie> finally starting
[17:19] <valorie> would be good to have you for a few mins at least, shadeslayer
[17:19] <shadeslayer> where is it?
[17:20] <valorie> #ubuntu-meeting - everyone is welcome to attend
[17:20] <shadeslayer> valorie: ping me when our turn comes? :p
[17:22] <valorie> sure
[17:31] <Riddell> ** community council meeting now apparantly
[17:36] <shadeslayer> I'm off to home
[17:36] <shadeslayer> cya tomorriow
[17:36] <soee> hiho
[17:37] <soee> i see 7 packages fail to build on amd4
[17:41] <snele> guys I just want to remind you that this important bug is still not fixed
[17:41] <snele> https://bugs.launchpad.net/ubuntu/+source/kde-runtime/+bug/1322968
[17:42] <snele> for example I was having some hieroglifs instead of serbian letters šđčćž . had to manually fix it
[17:42] <snele> I think it is important because 14.04 is LTS :)
[17:43] <snele> and who to ping about this bug? https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1369673
[17:46] <valorie> shadeslayer: :(
[18:22] <valorie> ...
[18:23]  * Riddell hand waves and ignores someone trying to restrict our community
[18:23] <Riddell> can I get on the CC now?
[18:23] <valorie>  http://ubottu.com/meetingology/logs/ubuntu-meeting/2014/ubuntu-meeting.2014-10-02-17.13.moin.txt
[18:24] <valorie> good idea, Riddell
[18:24] <valorie> moar committees!
[18:24] <sgclark> hehe
[18:24] <Riddell> hmm, got to wait until 2015-11-14 before I can stand on it
[18:24] <valorie> they might actually DO something though
[18:24] <sgclark> I do find it odd that we are few that have the concerns
[18:24] <valorie> which would be good
[18:25] <genii> It was pretty interesting to be a fly on the wall in #ubuntu-meeting just earlier.
[18:25] <Riddell> let's have a mass Kubuntu takeover of the communitiy council next November!
[18:25] <sgclark> lol
[18:25] <valorie> the others are small, and don't feel that they have any power
[18:25] <valorie> genii: your takeaway?
[18:28] <genii> valorie: I'm still thinking about it. But basically I think if Canonical wants to flex their muscles and go after other groups using their code, they are going to have an uphill battle. Especially with public opinion.
[18:28] <valorie> sure, but in the meantime, they are muddying the waters
[18:28] <valorie> and that hurts us
[18:29] <valorie> people stay away from areas with known bullies
[18:29] <valorie> it didn't use to be like this
[18:29] <valorie> they made their reputation as a champion of FLOSS
[18:30] <Riddell> reputation doesn't make money alas
[18:30] <valorie> now they are slowly destroying that
[18:30] <valorie> not directly
[18:31] <valorie> afk for awhile
[18:31] <genii> From what I've seen since I've been with *buntu, the troubles were starting pretty much around the time they wanted to go with Upstart, and it set a precedent there.
[18:31] <genii> Basically just degraded from there on
[18:31] <Riddell> upstart was a pioneering project, that's all good
[18:31] <Riddell> but the need for giving licence control to canonical killed it as a community project
[18:32] <Riddell> and lots of others like lightdm
[18:32] <Riddell> which is a bit hypocritical since qt also needs licence control
[18:32] <Riddell> but then qt doesn't need a dev community, the community needs qt (as a generalisaton)
[18:33] <Riddell> but the move away from gnome and to unity and also Mir is killer for a community project not to use community made software, and I'm surprised that wasn't brought up when they were talking about lack of new membership earlier
[18:35] <Riddell> anyway thanks for waking up so "early" valorie :)
[18:36] <genii> Yes, Mir vs Wayland put a lot of bitterness in the Canonical-Kubuntu relationship, that I could see.
[18:38]  * genii makes more coffee and goes back to work
[18:48] <jmux> Riddell: I'm just reading the the meeting backlog. I didn't know of the Ubuntu LiMux article before it got published, but AFAIK the LiMux Mgmt was asked if it was Ok and I guess they simply didn't realize.
[18:50] <jmux> I'll just ask them, if they want to write a mail and point them to the bug.
[18:51] <soee> woho 3 packages left for amd64 :)
[18:54] <Riddell> thanks jmux
[18:57] <rberg> Hi all not sure if this is the correct place to report this: I found that with kde 4.14.1 on precise kde no longer suspends on laptop lip close nor is there a button on the K menu / leave, pm-suspend still works
[18:57] <rberg> err not precise trusty
[18:58] <soee> after todays updates ?
[18:58] <rberg> yes
[18:59] <soee> Riddell: ^
[19:00] <Riddell> rberg: hmm, fooey
[19:00] <Riddell> that'll be faffy to debug
[19:00] <Riddell> solid not detecting the right thing again
[19:01] <Riddell> rberg: can you report a bug? https://bugs.launchpad.net/kubuntu-ppa/+filebug
[19:01] <Riddell> and ping us here with it
[19:01] <rberg> sure, might me a few min
[19:08] <sgclark> Riddell: I keep getting rejected on libmm-qt. Someone had already fixed the issue in git but never put in pa.
[19:08] <sgclark> ppa
[19:10]  * sgclark spots jriddell next to libmm-qt notes
[19:10] <Riddell> yeah I put something up didn't I?
[19:10] <sgclark> it never made it to the ppa
[19:10] <sgclark> still at ppa1
[19:11] <sgclark> but the changes are in git
[19:11] <shadeslayer> mmm
[19:11] <shadeslayer> Riddell: how was the meeting
[19:12]  * shadeslayer is full of food
[19:12] <sgclark> is there a space free version of gpl-2 + trolltech gpl exception version 1.0
[19:19] <soee> sgclark: is there any chance to get 5.1b ready today ?
[19:19] <sgclark> trying
[19:22] <rberg> Riddell: https://bugs.launchpad.net/kubuntu-ppa/+bug/1376895  let me know if there is any other info you folks could use. thanks.
[19:23] <Riddell> sgclark: just make one up I guess, GPL-2 or GPL-Qt  or something
[19:23] <sgclark> ok
[19:24] <Riddell> shadeslayer: oh the usual, hand waving and talk of complexity rather than any desire to stand up for free software
[19:24] <Riddell> shadeslayer: any thoughts on rberg's bug? suspend broken in 4.14.1 on trusty, have I forgotten to add in some patch?
[19:31] <shadeslayer> Riddell: not really sure
[19:31] <shadeslayer> check output of qdbus --system org.freedesktop.login1 /something/something/canHibernate
[19:32] <Riddell> rberg: ↑
[19:33] <rberg> false
[19:33] <rberg> qdbus org.kde.kded /org/freedesktop/PowerManagement CanHibernate false
[19:37] <shadeslayer> not really, but ok
[19:38] <shadeslayer> what about cansuspend?
[19:38] <shadeslayer> but yeah, that explains why you can't suspend, KDE thinks it can't suspend
[19:39] <shadeslayer> rberg: check qdbus --system org.freedesktop.login1
[19:39] <shadeslayer> it should have a can suspend method oto
[19:40] <rberg> updated the ticket with that output
[19:41] <Riddell> plasma5 has: >qdbus --system org.freedesktop.login1 /org/freedesktop/login1 org.freedesktop.login1.Manager.CanSuspend
[19:41] <Riddell> yes
[19:45] <shadeslayer> ^^
[19:47] <rberg> I dont see any sort of answer along with org.freedesktop.login1.Manager.CanSuspend()
[19:53] <rberg> sorry to bother, I rebooted my laptop and now I get a suspend button. Before I had just logged out and restarted lightdm after the upgrade
[19:57] <Riddell> rberg: ooh interesting
[19:57] <Riddell> and mysterious, I've no idea why it would be different
[19:57] <rberg> yeah, I wonder if something was left running or something
[19:58] <rberg> something in /tmp.. now I am just guessing
[20:19] <Riddell> ooh plasma 5 is all compiled
[20:19] <Riddell> brave people can test
[20:19] <sgclark> I just put up oxygen, had new files, wait a bit
[20:20] <sgclark> Riddell: libmm-qt is still broken
[20:21] <Riddell> hmm the .orig is indeed different
[20:22] <Riddell> aah watch is looking for libnm not libmm
[20:35] <Riddell> uploaded
[20:42] <sgclark> Riddell: are you sure? still shows failed ppa1
[20:43] <sgclark> Riddell: that is the last of them for serious errors, mind if I tidy up the last of the copyright bits tomorrow, I am quite tired now :(
[21:22] <Riddell> sgclark: me too, sleep well
[21:22] <sgclark> g'night!
[21:27] <Pali> Riddell: 4.14.1 for precise was compiled: https://launchpad.net/~pali/+archive/ubuntu/kubuntu-backports/
[21:28] <Pali> and one patch for backport-hooks: http://bazaar.launchpad.net/~pali/+junk/kubuntu-automation/revision/439
[21:55] <soee> hmm p5.1b packages ready ? :)
[21:56] <sgclark> soee: sure it is tester ready
[21:57] <soee> yup :)
[21:59] <soee> upgrading
[22:01] <soee> oks one error already
[22:03] <apachelogger> shadeslayer: oh yeah, btw, feel free to come up with an algorithm proposal for upgrade testing that covers as much as possible while wasting as little resources as possible ;)
[22:04] <soee> sgclark: problem with /var/cache/apt/archives/libkf5sysguard5-data_4%3a5.0.95-0ubuntu1~ubuntu14.10~ppa4_amd64.deb
[22:05] <sgclark> can you give me more details than that?
[22:06] <soee> im trying, i forget how to get command executed in english :/
[22:06] <soee> sgclark: http://paste.ubuntu.com/8481962/
[22:06] <sgclark> oh hmm. perhaps I will see when I upgrade. too tired to do it now
[22:07] <soee> ok ill tru with -f and force overwrite
[22:09] <apachelogger> transition fail most likley
[22:09] <apachelogger> i386 of ksysguard hasn't built yet, so -data is not available in the required version
[22:09] <soee> reboot
[22:09] <apachelogger> should autoresolve in an hour or so
[22:09] <soee> i did sudo apt-get -o Dpkg::Options::="--force-overwrite" install libkf5sysguard5-data
[22:10] <apachelogger> that doesn't solve the issue
[22:10] <apachelogger> unless you ran apt update as well ^^
[22:10] <apachelogger> (and that only helps in case the correct version built meanwhile)
[22:10] <apachelogger> at any rate that problem shouldn't have impact on anything but ksysguard anyway
[22:11] <soee> will try to reboot and see what happen
[22:11] <sgclark> apachelogger: what do you mean not built? all compiled except arm (of course)
[22:11] <apachelogger> sgclark: they weren't when soee ran apt update
[22:12] <sgclark> oh ok
[22:12] <apachelogger> even if, there's the publication step which might take longer for one arch than the other, depending on when teh build actually failed
[22:14] <soee> im back
[22:16] <soee> all seems to work fine, but if i open systray
[22:16] <soee> my kaptop starts to give strange sound
[22:16] <apachelogger> lol
[22:16] <apachelogger> soee: define strange sounds
[22:17] <apachelogger> and does it go away if you close the notification popup again
[22:17] <soee> yet it goas away, it saunds like very old TV when warming up
[22:17] <soee> mabe something with battery
[22:17] <sgclark> d_ed: I am told to bug you with this bug: https://bugs.kde.org/show_bug.cgi?id=339620
[22:18] <apachelogger> soee: that sounds veery strange
[22:18] <apachelogger> soee: does the sound come out the speakers?
[22:18] <soee> yup amd the otification item loading animation is active all the time
[22:18] <apachelogger> Riddell: apparently oxygen has no beta version on bugzilla
[22:19] <soee> apachelogger: hard to say
[22:19] <apachelogger> put your ear tot he speaker :P
[22:19] <apachelogger> if you move ear away, does it get less loud? :P
[22:19] <apachelogger> audio debugging for starters xD
[22:21] <soee> i have muted all but this happens all the time
[22:21] <soee> i would shoot into battery supply
[22:22] <apachelogger> totally weird
[22:22] <soee> btw i feel like all works 5 time faster now
[22:23] <sgclark> nice
[22:30] <soee> after logout and login again, plasmashell did not start
[22:30] <soee> had to start it manually
[22:32] <soee> ok time to get some sleep, ill test more tomorrow