[00:11]  * Unit193 Just installed Xubuntu and is stuck with 1280x1024
[00:11] <Cheri703> :(
[00:11] <Cheri703> I know nothing about xubuntu
[00:13] <BiosElement> Unit193: Isn't that an X.org issue?
[00:15] <Unit193> -reconfigure might help...
[00:16] <Unit193> Just installed as in I'm still running apt-get upgrade
[00:19] <Unit193> Cheri703: Do you use QSynergy?
[00:19] <Cheri703> uhm, I use synergy...not sure it's the qsynergy variant
[00:20] <Unit193> Lazyman GUI
[00:22] <Cheri703> ah, I think I tried, and it was dumb
[00:22] <Cheri703> there's a nice guide, give me a minute
[00:24] <Unit193> I know how, I was just asking if you used that GUI...
[00:24] <Unit193> quicksynergy is dumb...
[00:24] <Cheri703> the one link was dead, I think this is the info though: http://synergy2.sourceforge.net/running.html
[00:25] <Cheri703> I tried and it hated me
[00:25] <Cheri703> this too: http://www.mattcutts.com/blog/how-to-configure-synergy-in-six-steps/
[00:25] <Cheri703> *I tried the qsynergy and it hated me
[02:58]  * canthus13 hugs synergy.
[02:58] <Cheri703> lurv synergy
[02:58] <Cheri703> it's awesome
[02:58] <Cheri703> it lets me use my tvcomputer :)
[03:01] <Unit193> Having a TV computer would be nice...
[03:01] <Unit193> Dang you canthus13!!
[03:02] <canthus13> Unit193: What??
[03:03] <Unit193> That dang white jigsaw....
[03:03] <canthus13> HAHAHAHAHA!
[03:04] <Unit193> Did you ever finish it?
[03:04] <Unit193> Or how far did you get?
[03:09] <Unit193> Just started it tonight......
[03:10] <canthus13> I got through about 10 rounds, I think.
[03:14] <Cheri703> what are you talking about?
[03:14] <canthus13> Cheri703: A pure white jigsaw puzzle. a flash game.
[03:14] <canthus13> It's a fun distraction for a while.
[03:15] <Cheri703> nice
[03:15] <Cheri703> link?
[03:17] <canthus13> I don't remember...
[03:17] <canthus13> Unit193: POKE
[03:17] <canthus13> Cheri703: I played with it months ago for about 2 weeks straight.
[03:17] <Cheri703> heh, nice
[03:24] <Cheri703> Unit193: linky link?
[03:40] <canthus13> He's lost in the game....
[03:40] <Cheri703> I was just thinking that
[03:42] <Unit193> Hair cut...
[03:42] <Cheri703> ah
[03:43] <Unit193> http://www.gamedesign.jp/flash/whitejigsaw/whitejigsaw.html
[03:44]  * Unit193 was using the swf file he downloaded way back...
[04:15] <Unit193> Do your Scroll Lock Light indicator work?
[04:15] <Cheri703> I don't think I have one
[04:15] <Unit193> Does*
[04:16] <Unit193> Synergy uses it as the "lock to this screen" and when I hit it the nice little light doesn't light up... ( I know the light works...)
[04:17] <Cheri703> weird
[04:52] <Unit193> How do you like the jigsaw? (I don't like them much myself)
[04:53] <Cheri703> I went several levels, but then had to do other stuff
[20:34] <paultag> gilbert: ping :)
[20:35] <paultag> gilbert: I'm preparing 1.3.1~dfsg1-1, just for you :)
[20:36] <paultag> gilbert: it's +pending ;)
[20:36] <paultag> (yes fluxbox actually did a 1.3.1 release, I'm not a total dumbass ;) )
[20:37] <paultag> and, uploaded
[20:37] <paultag> huzzah
[20:39] <paultag> and natty / maverick hit my ppa
[20:40] <paultag> and lucid. great
[23:22] <Cheri703> o.O http://mansfield.craigslist.org/bar/2237949417.html]
[23:22] <Cheri703> http://mansfield.craigslist.org/bar/2237949417.html


[01:43] -queuebot:#ubuntu-release- Unapproved: unattended-upgrades (xenial-proposed/main) [0.90ubuntu0.5 => 0.90ubuntu0.6] (desktop-core, ubuntu-server)
[01:45] -queuebot:#ubuntu-release- Unapproved: unattended-upgrades (yakkety-proposed/main) [0.92ubuntu1.4 => 0.92ubuntu1.5] (desktop-core, ubuntu-server)
[01:54] -queuebot:#ubuntu-release- Unapproved: unattended-upgrades (zesty-proposed/main) [0.93.1ubuntu2.1 => 0.93.1ubuntu2.2] (desktop-core, ubuntu-server)
[04:36] -queuebot:#ubuntu-release- New: accepted linux-signed-lts-xenial [amd64] (trusty-proposed) [4.4.0-78.99~14.04.2]
[04:37] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe [amd64] (xenial-proposed) [4.8.0-52.55~16.04.1]
[06:36] -queuebot:#ubuntu-release- Unapproved: dpdk (yakkety-proposed/main) [16.07.2-0ubuntu<IP_ADDRESS> => 16.07.2-0ubuntu<IP_ADDRESS>] (ubuntu-server) (sync)
[07:42] -queuebot:#ubuntu-release- New binary: linux-signed-hwe-edge [amd64] (xenial-proposed/main) [4.10.0-21.23~16.04.1] (kernel)
[08:29] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe-edge [amd64] (xenial-proposed) [4.10.0-21.23~16.04.1]
[11:09] -queuebot:#ubuntu-release- New binary: fonts-open-sans [amd64] (artful-proposed/universe) [1.11-1] (no packageset)
[11:09] -queuebot:#ubuntu-release- New binary: openscap-daemon [amd64] (artful-proposed/universe) [0.1.6-1] (no packageset)
[11:09] -queuebot:#ubuntu-release- New binary: simple-obfs [ppc64el] (artful-proposed/universe) [0.0.3-1] (no packageset)
[11:09] -queuebot:#ubuntu-release- New binary: node-are-we-there-yet [amd64] (artful-proposed/universe) [1.1.4-1] (no packageset)
[11:09] -queuebot:#ubuntu-release- New binary: simple-obfs [amd64] (artful-proposed/universe) [0.0.3-1] (no packageset)
[11:10] -queuebot:#ubuntu-release- New binary: afterburner.fx [amd64] (artful-proposed/universe) [1.7.0-1] (no packageset)
[11:10] -queuebot:#ubuntu-release- New binary: haskell-tree-monad [i386] (artful-proposed/universe) [0.3-1] (no packageset)
[11:10] -queuebot:#ubuntu-release- New binary: haskell-tree-monad [s390x] (artful-proposed/universe) [0.3-1] (no packageset)
[11:10] -queuebot:#ubuntu-release- New binary: simple-obfs [i386] (artful-proposed/universe) [0.0.3-1] (no packageset)
[11:10] -queuebot:#ubuntu-release- New binary: haskell-tree-monad [amd64] (artful-proposed/universe) [0.3-1] (no packageset)
[11:10] -queuebot:#ubuntu-release- New binary: simple-obfs [armhf] (artful-proposed/universe) [0.0.3-1] (no packageset)
[11:10] -queuebot:#ubuntu-release- New binary: haskell-tree-monad [ppc64el] (artful-proposed/universe) [0.3-1] (no packageset)
[11:10] -queuebot:#ubuntu-release- New binary: simple-obfs [s390x] (artful-proposed/universe) [0.0.3-1] (no packageset)
[11:11] -queuebot:#ubuntu-release- New binary: haskell-tree-monad [arm64] (artful-proposed/universe) [0.3-1] (no packageset)
[11:11] -queuebot:#ubuntu-release- New binary: imexam [amd64] (artful-proposed/universe) [0.7.1-1] (no packageset)
[11:11] -queuebot:#ubuntu-release- New binary: haskell-tree-monad [armhf] (artful-proposed/universe) [0.3-1] (no packageset)
[11:11] -queuebot:#ubuntu-release- New binary: imexam [ppc64el] (artful-proposed/universe) [0.7.1-1] (no packageset)
[11:13] -queuebot:#ubuntu-release- New binary: imexam [arm64] (artful-proposed/universe) [0.7.1-1] (no packageset)
[11:13] -queuebot:#ubuntu-release- New binary: imexam [i386] (artful-proposed/universe) [0.7.1-1] (no packageset)
[11:13] -queuebot:#ubuntu-release- New binary: simple-obfs [arm64] (artful-proposed/universe) [0.0.3-1] (no packageset)
[11:13] -queuebot:#ubuntu-release- New binary: imexam [armhf] (artful-proposed/universe) [0.7.1-1] (no packageset)
[11:13] -queuebot:#ubuntu-release- New binary: imexam [s390x] (artful-proposed/universe) [0.7.1-1] (no packageset)
[11:29] <apw> bdmurray, was that note that yakkety was phasing meant to be a warning of badness ?
[11:34] <acheronuk> apw: would you maybe have some time to look at the new queue KDE applications packages?
[11:35] <acheronuk> they were the ones we were never able to get into zesty :/
[11:36] <acheronuk> but had to provide in a ppa post release http://kubuntu.org/news/kde-pim-update-now-available-for-zesty-zapus-17-04/
[11:36] -queuebot:#ubuntu-release- New: accepted haskell-tree-monad [arm64] (artful-proposed) [0.3-1]
[11:36] -queuebot:#ubuntu-release- New: accepted imexam [amd64] (artful-proposed) [0.7.1-1]
[11:36] -queuebot:#ubuntu-release- New: accepted imexam [armhf] (artful-proposed) [0.7.1-1]
[11:36] -queuebot:#ubuntu-release- New: accepted imexam [ppc64el] (artful-proposed) [0.7.1-1]
[11:36] -queuebot:#ubuntu-release- New: accepted simple-obfs [arm64] (artful-proposed) [0.0.3-1]
[11:36] -queuebot:#ubuntu-release- New: accepted haskell-tree-monad [armhf] (artful-proposed) [0.3-1]
[11:36] -queuebot:#ubuntu-release- New: accepted imexam [i386] (artful-proposed) [0.7.1-1]
[11:36] -queuebot:#ubuntu-release- New: accepted simple-obfs [armhf] (artful-proposed) [0.0.3-1]
[11:36] -queuebot:#ubuntu-release- New: accepted imexam [arm64] (artful-proposed) [0.7.1-1]
[11:36] -queuebot:#ubuntu-release- New: accepted imexam [s390x] (artful-proposed) [0.7.1-1]
[11:37] -queuebot:#ubuntu-release- New: accepted afterburner.fx [amd64] (artful-proposed) [1.7.0-1]
[11:37] -queuebot:#ubuntu-release- New: accepted haskell-tree-monad [amd64] (artful-proposed) [0.3-1]
[11:37] -queuebot:#ubuntu-release- New: accepted haskell-tree-monad [ppc64el] (artful-proposed) [0.3-1]
[11:37] -queuebot:#ubuntu-release- New: accepted node-are-we-there-yet [amd64] (artful-proposed) [1.1.4-1]
[11:37] -queuebot:#ubuntu-release- New: accepted simple-obfs [amd64] (artful-proposed) [0.0.3-1]
[11:37] -queuebot:#ubuntu-release- New: accepted simple-obfs [ppc64el] (artful-proposed) [0.0.3-1]
[11:37] -queuebot:#ubuntu-release- New: accepted fonts-open-sans [amd64] (artful-proposed) [1.11-1]
[11:37] -queuebot:#ubuntu-release- New: accepted haskell-tree-monad [s390x] (artful-proposed) [0.3-1]
[11:37] -queuebot:#ubuntu-release- New: accepted simple-obfs [i386] (artful-proposed) [0.0.3-1]
[11:37] -queuebot:#ubuntu-release- New: accepted haskell-tree-monad [i386] (artful-proposed) [0.3-1]
[11:37] -queuebot:#ubuntu-release- New: accepted simple-obfs [s390x] (artful-proposed) [0.0.3-1]
[11:37] -queuebot:#ubuntu-release- New: accepted openscap-daemon [amd64] (artful-proposed) [0.1.6-1]
[11:39] <apw> acheronuk, right at this instant no, but i'll try and get to them a little at a time
[11:40] <acheronuk> apw: that is great, and appreciated. can't ask for more than that. :)
[12:06] <LocutusOfBorg> test queue is finally settling down
[12:08] <Laney> sad!
[12:08] <apw> i love how 700 items is "settling down"
[12:09] <apw> no more parties for ADT
[12:09]  * Laney loves a phat queue
[12:09] <LocutusOfBorg> at least that is the "huge" queue, lower priority, right?
[12:11] <ginggs> would someone please remove bio-tradis binaries on armhf and s390x ?
[12:13] <infinity> ginggs: Not without rationale.
[12:15] <ginggs> infinity: it was built on architectures where it is not installable, please see the ubuntu1 changelog entry
[12:15] <xnox> infinity, this is not how one holidays =)
[12:15] <infinity> ginggs: Also would have helped to specify "artful-proposed".
[12:15] <infinity> ginggs: Done.
[12:16] <infinity> xnox: Yeah, can't sleep.
[12:16] <ginggs> infinity: thanks!
[12:22] <LocutusOfBorg> I would also remove from artful src:why on ppc64el and s390x please
[12:22] <LocutusOfBorg> they are not provided anymore in Debian and Upstream
[12:23] <infinity> LocutusOfBorg: Done ages ago.
[12:24] <infinity> LocutusOfBorg: But again, when that was requested, someone failed to point out that artful-proposed also had NBS binaries, I cleaned those half an hour ago or so. :P
[12:24] <LocutusOfBorg> interesting, so it doesn't migrate because of something else, lets check
[12:24] <LocutusOfBorg> oh ok :)
[12:24] <LocutusOfBorg> "infinity thanks!"
[12:52] -queuebot:#ubuntu-release- Unapproved: accepted unattended-upgrades [source] (precise-proposed) [0.76ubuntu1.3]
[13:03] <cpaelzer> rbasak: hi if you could take a look at the qemu in the xenial unapproved today that would be great
[13:03] <doko> hmm, gcc-7 migrated while it had a block-proposed bug, #1687912
[13:04] <cpaelzer> rbasak: I already wrapped a second SRU into this because it waited a while, but we now have found regression-update by a security fix of last summer
[13:04] <cpaelzer> rbasak: it would be great to sucessfully process the ongoing SRU out of the way until mdeslaur has prepared the next round that will fix this (and the usual set of CVEs)
[13:05] <rbasak> cpaelzer: OK, I'll take a look. Which bug is the regression-update?
[13:05] <cpaelzer> rbasak: regression-update is bug 1581936
[13:05] <ubot5`> bug 1581936 in qemu (Ubuntu Xenial) "Frozen Windows 7 VMs with VGA CVE-2016-3712 fix (2.6.0 and <IP_ADDRESS>)" [High,Triaged] https://launchpad.net/bugs/1581936
[13:05] <cpaelzer> was filed only with upstream qemu all the time, so no one did notice so far
[13:05] <jbicha> doko: I assume the block-proposed tag was added just a bit too late
[13:06] <infinity> doko: The bug was filed after it migrated.
[13:07] <cpaelzer> rbasak: the two bugs the current SRU in x-unapproved fixes are bug 1684239 and bug 1656112
[13:07] <ubot5`> bug 1684239 in qemu (Ubuntu Xenial) "vvfat core dump when enabling RW" [Medium,Fix committed] https://launchpad.net/bugs/1684239
[13:07] <ubot5`> bug 1656112 in linux (Ubuntu Xenial) "Power S822LC (8335-GTB) fails KVM guest cert test with kvm_init_vcpu failed: Invalid argument" [High,Confirmed] https://launchpad.net/bugs/1656112
[13:07] <rbasak> cpaelzer: OK, let me check I've got this straight. There are no in-flight SRUs, one unapproved regular SRU in bug 1684239, and one security regression-update bug 1581936. You're asking me to review/accept the fix for 239 from xenial unapproved, and then mdeslaur will deal with 936 through the security pocket?
[13:07] <ubot5`> bug 1581936 in qemu (Ubuntu Xenial) "Frozen Windows 7 VMs with VGA CVE-2016-3712 fix (2.6.0 and <IP_ADDRESS>)" [High,Triaged] https://launchpad.net/bugs/1581936
[13:07] <cpaelzer> "fortunately" all other qemu issues open atm are actually fixed in libvirt so no further collisions known so far
[13:08] <cpaelzer> rbasak: yes that summary matches my view
[13:08] <rbasak> cpaelzer: OK, and you're fine with the aging period for an accept from xenial unapproved now? Or will mdeslaur trump that?
[13:09] <rbasak> Either way, as long as you know :)
[13:09] <infinity> doko: Oh, fun, and that overwrote libgphobos68 from gcc-6. :/
[13:09] <mdeslaur> rbasak, cpaelzer: I won't get to my update before a couple of weeks anyway
[13:09] <cpaelzer> rbasak: I'm ok with a normal aging and so is mdeslaur according to our discussion if we start the aging period like now
[13:09] <doko> yep, noticed too late
[13:09] <infinity> doko: I can delete that and copy gcc-6 back overtop before it causes any real problems.
[13:09] <cpaelzer> mdeslaur: exactly, so if we start to process now it will be out of the way
[13:09] <doko> sure, that would be good
[13:09] <rbasak> cpaelzer, mdeslaur: understood, thanks. I'll review now.
[13:10] <cpaelzer> rbasak: and ping me if there is anything unclear I can help to rule out
[13:10] <cpaelzer> especially the ppc bug went a few iterations back and forth
[13:14] <rbasak> cpaelzer: I don't see that 2.5+dfsg-5ubuntu10.12 was ever published?
[13:15] <cpaelzer> rbasak: indeed which is why the changelog has both
[13:15] <cpaelzer> rbasak: as you see in the diff
[13:15] <infinity> doko: Okay, should fix itself on the next publisher run.
[13:15] <infinity> doko: https://launchpad.net/ubuntu/artful/amd64/libgphobos68
[13:15] <rbasak> Ah. Does bileto stop you squashing the two together?
[13:16] <doko> ta
[13:16] <cpaelzer> rbasak: yeah a bit like a burned version would do (only a bit)
[13:16] <cpaelzer> I'd need a new ppa and that was bad in this case as I had two external parties already having the links to them
[13:16] <cpaelzer> in many other cases I just fetch a new ticket and be good with it
[13:17] <cpaelzer> rbasak: ^^
[13:17] <rbasak> Trouble is the changes file lists only one (top) bug. I'm not sure what SRU tooling would make of it: https://launchpadlibrarian.net/316967280/qemu_2.5+dfsg-5ubuntu10.13_source.changes
[13:17] <cpaelzer> rbasak: but if you upload a second version it behave in the past like a dpkg-genversion -v<old>
[13:17] <cpaelzer> hmm
[13:17] <cpaelzer> the changes would mean not
[13:17] <rbasak> You can use -v manually when running dpkg-buildpackages.
[13:18] <cpaelzer> rbasak: I did in the past
[13:18] <infinity> cpaelzer: You would have had to manually do a dpkg-genchanges -v before uploading, bileto doesn't do anything fancy here, it just copies your upload around.
[13:18] <cpaelzer> rbasak: we could kill it from the queue I upload the version with a -v set for a better .changes file
[13:18] <cpaelzer> infinity: thanks
[13:18]  * cpaelzer belived to much in bileto at this then
[13:19] <cpaelzer> rbasak: cancel and dput then, I can do that like now and it would show up in the queue
[13:19] <cpaelzer> rbasak: or is there a rule on minumum unapproved queue time?
[13:19] <infinity> cpaelzer: At the end of the day, bileto isn't doing anything more for you than provisioning a PPA and running 'copy-package -b' to get your stuff from the PPA to the archive.
[13:19] <infinity> cpaelzer: There's no magic.
[13:19]  * cpaelzer is crying for his world of magic is destroyed :-)
[13:20] <rbasak> cpaelzer: no minimum unapproved queue time.
[13:20] <infinity> cpaelzer: As for "minimum unapproved queue time", it tends to amount to "the time required to generate a debdiff, if your reviewer doesn't want to download the source and diff it himself". :P
[13:20] <cpaelzer> hehe
[13:20] <rbasak> Well, there is that :)
[13:20] <rbasak> But for bileto syncs I have to download the source and diff it myself anyway :)
[13:20] <cpaelzer> rbasak: I'll do that then - pelase reject the current one
[13:20] <cpaelzer> wow pelase - please I meant
[13:21] <rbasak> My git import tooling is capable of making this easier, but currently we have the git empty directory issue and this qemu upload seems to hit it :-/
[13:22] -queuebot:#ubuntu-release- Unapproved: rejected qemu [sync] (xenial-proposed) [1:2.5+dfsg-5ubuntu10.13]
[13:22] <cpaelzer> rbasak: this issue grows wider and wider
[13:22] <cpaelzer> the empty dir one
[13:22] <rbasak> Yeah :-/
[13:24] <cpaelzer> rbasak: ok the changes now holds both as it should by manually creating it this time
[13:24] <cpaelzer> rbasak: should show up here any minute - I'll ping you then
[13:25] -queuebot:#ubuntu-release- Unapproved: qemu (xenial-proposed/main) [1:2.5+dfsg-5ubuntu10.11 => 1:2.5+dfsg-5ubuntu10.13] (ubuntu-server, virt)
[13:26] <cpaelzer> rbasak: here it is
[13:26] <rbasak> Looking
[13:26] <rbasak> Waiting for the debdiff :-)
[13:27] <cpaelzer> which confirms infinity theory on minimal aging time :-)
[13:31] <rbasak> And Launchpad has gone and diffed against < 0.11 :-/
[13:32]  * rbasak downloads from the queue manually
[13:32] <infinity> rbasak: It diffs against the last version that was in proposed.  It's not super smart about interim security updates.
[13:32] <rbasak> Ah, so that's the logic.
[13:32] <rbasak> The git stuff will make this moot as soon as I fix the empty directory issue :-/
[13:37] <rbasak> cpaelzer: are all three patches committed in upstream's master branch?
[13:37] <rbasak> cpaelzer: also, are they in stable-2.5?
[13:37] <rbasak> I could check, but if you know, that's quicker :)
[13:38] <tjaalton> what would it need to promote debhelper 10 backport to xenial-updates?
[13:40] <cpaelzer> rbasak: I know, just a sec for my log to read
[13:40] <cpaelzer> rbasak: master for sure
[13:40] <cpaelzer> rbasak: checking on stable branch details
[13:41] <rbasak> http://git.qemu.org/?p=qemu.git;a=heads suggests that stable-2.5 is no longer maintained upstream?
[13:41] <cpaelzer> yeah I haven't seen anything in a while
[13:42] <cpaelzer> still patches are old and could be in before if you need to now
[13:42] <rbasak> cpaelzer: have you reviewed the patches themselves yourself?
[13:42] <cpaelzer> rbasak: yes
[13:42] <rbasak> That's good enough for me then, thanks :)
[13:42] <cpaelzer> rbasak: that is me doing the work from upstream commit to d/p/patch
[13:43] <cpaelzer> rbasak: otherwise the Author in the dep3 would not hold me
[13:43] <rbasak> Oh, it didn't apply directly?
[13:43] <cpaelzer> rbasak: but I guess you can never rely on dep3 as it is optional
[13:43] <cpaelzer> rbasak: of the three one had fuzz that was unrelated IIRC
[13:43] <cpaelzer> rbasak: the others applied as is - maybe with offset - I don't remember
[13:44] <cpaelzer> rbasak: memory is hard on that as interim-wise that was like 9 patches
[13:44] <rbasak> No problem.
[13:44] <cpaelzer> rbasak: until I challenged IBM for their trick to sneak in power performance patches
[13:44] <rbasak> So I think that would be, in dep3, "Origin: upstream, <url>"
[13:44] <cpaelzer> yet by said patch review I identified they were not needed and dropped to the SRU-minimum
[13:44] <rbasak> (no need to change now)
[13:45] <rbasak> If you'd had to massage the patches, then it'd be "Origin: backport, <url>" and an additional "Author: Christian ..." line.
[13:45] <rbasak> (multiple Author lines are permitted)
[13:45] <cpaelzer> rbasak: I'm kind of proud of my dep3 compared to most I see
[13:45] <cpaelzer> rbasak: but always good to get more
[13:45] <cpaelzer> I usually have Author and Original-Author
[13:45] <rbasak> I do very much appreciate what you're put there already, thanks :)
[13:46] <cpaelzer> rbasak: I keep an ~/work/patch-template-dep8.patch that I always use as base
[13:51] -queuebot:#ubuntu-release- Unapproved: accepted qemu [source] (xenial-proposed) [1:2.5+dfsg-5ubuntu10.13]
[13:51] <LocutusOfBorg> can anybody look at virtualbox* in xenial unapproved queue?
[13:52] <cpaelzer> LocutusOfBorg: only one hypervisor at a time so people can fall back :-P
[14:06] <LocutusOfBorg> yeah, queue is now at 558 :)
[14:21] -queuebot:#ubuntu-release- Unapproved: debhelper (xenial-proposed/main) [10.2.2ubuntu1~ubuntu16.04.1 => 10.2.2ubuntu1~ubuntu16.04.2] (core)
[14:22] <apw> LocutusOfBorg, is that just for X
[14:24] -queuebot:#ubuntu-release- Unapproved: rejected virtualbox-ext-pack [source] (xenial-proposed) [5.0.38-0ubuntu<IP_ADDRESS>]
[14:24] -queuebot:#ubuntu-release- Unapproved: rejected virtualbox [source] (xenial-proposed) [5.0.38-dfsg-0ubuntu<IP_ADDRESS>]
[14:24] -queuebot:#ubuntu-release- Unapproved: rejected virtualbox-guest-additions-iso [source] (xenial-proposed) [5.0.38-0ubuntu<IP_ADDRESS>]
[14:32] -queuebot:#ubuntu-release- Unapproved: accepted virtualbox [source] (xenial-proposed) [5.0.40-dfsg-0ubuntu<IP_ADDRESS>]
[14:33] <LocutusOfBorg> apw, sorry ENOPARSE
[14:33] <apw> LocutusOfBorg, is that just for xenial, am i expecting any other series
[14:33] <LocutusOfBorg> nobody complained for yakkety and zesty
[14:33] <LocutusOfBorg> artful is good
[14:33] <LocutusOfBorg> but I can do the same there
[14:34] <LocutusOfBorg> (updating to 5.1.22)
[14:34] <LocutusOfBorg> now we also have a testsuite :)
[14:35] -queuebot:#ubuntu-release- Unapproved: accepted virtualbox-ext-pack [source] (xenial-proposed) [5.0.40-0ubuntu<IP_ADDRESS>]
[14:35] <jbicha> LocutusOfBorg: by the way, did you see https://bugs.debian.org/861683 ?
[14:35] <ubot5`> Debian bug 861683 in src:xorg "Install xserver-xorg-legacy by default for stretch" [Serious,Fixed]
[14:36] -queuebot:#ubuntu-release- Unapproved: accepted virtualbox-guest-additions-iso [source] (xenial-proposed) [5.0.40-0ubuntu<IP_ADDRESS>]
[14:36] <ginggs> LocutusOfBorg: suite!
[14:48] <slangasek> so who accepted the unattended-upgrades SRU in precise when we currently have no SRU test case on the bug?
[14:49] <slangasek> infinity, apparently
[14:49] <apw> slangasek, not me
[14:55] <LocutusOfBorg> jbicha, yes, and sad story
[14:56] <jbicha> LocutusOfBorg: yes, but it looks like there's a workaround now so it's not as bad
[14:57] <LocutusOfBorg> the workaround has always been there
[14:57] <LocutusOfBorg> I also had that dependency in vbox-guest-* for some time
[14:58] <jbicha> if you did a clean install of stretch any time in the past several months in VBox, gdm would not start
[14:59] <LocutusOfBorg> It starts if you install virtuabox-guest-x11
[14:59] <LocutusOfBorg> I override the *GL libraries there
[14:59] <LocutusOfBorg> so the vbox implementation works
[14:59] <jbicha> right, but how are people going to do that? :(
[14:59] <LocutusOfBorg> vbox people are trying to upstream the relevant patches
[15:00] <LocutusOfBorg> tjaalton, merge src:xorg please?
[15:00] <tjaalton> LocutusOfBorg: for artful?
[15:01] <LocutusOfBorg> yeah
[15:01] <tjaalton> k
[15:01] <LocutusOfBorg> I can do it, but meh, better ask :p
[15:01] <tjaalton> it's in git
[15:03] <LocutusOfBorg> nobody wants to sponsor a deboostrap upload? LP: #1685873
[15:03] <ubot5`> Launchpad bug 1685873 in debootstrap (Ubuntu) "please merge debootstrap from Debian" [High,Confirmed] https://launchpad.net/bugs/1685873
[15:13] <apw> LocutusOfBorg, there is a heck of a lot of merges and merging going on atm
[15:23] <LocutusOfBorg> ack
[15:23] <LocutusOfBorg> BTW I'm building vbox for yakkety/zesty FWIW
[15:23] <LocutusOfBorg> I'll setup two VM to test tonight
[15:25] <LocutusOfBorg> I have to admit, I lost interest in fixing bugs between an LTS and the other one :)
[15:25] <LocutusOfBorg> I would like to know popcon for yakkety/zesty and compare them with xenial
[15:27] -queuebot:#ubuntu-release- Unapproved: rejected debhelper [source] (xenial-proposed) [10.2.2ubuntu1~ubuntu16.04.2]
[15:29] -queuebot:#ubuntu-release- Unapproved: virtualbox (yakkety-proposed/multiverse) [5.1.6-dfsg-2 => 5.1.22-dfsg-0ubuntu<IP_ADDRESS>] (ubuntu-cloud)
[15:30] -queuebot:#ubuntu-release- Unapproved: virtualbox-ext-pack (yakkety-proposed/universe) [5.1.6-2ubuntu1 => 5.1.22-2ubuntu<IP_ADDRESS>] (no packageset)
[15:30] -queuebot:#ubuntu-release- Unapproved: virtualbox-ext-pack (zesty-proposed/multiverse) [5.1.18-1 => 5.1.22-2ubuntu<IP_ADDRESS>] (no packageset)
[15:30] -queuebot:#ubuntu-release- Unapproved: virtualbox-guest-additions-iso (yakkety-proposed/multiverse) [5.1.6-1 => 5.1.22-1ubuntu<IP_ADDRESS>] (no packageset)
[15:30] -queuebot:#ubuntu-release- Unapproved: virtualbox (zesty-proposed/multiverse) [5.1.18-dfsg-1build1 => 5.1.22-dfsg-0ubuntu<IP_ADDRESS>] (ubuntu-cloud)
[15:30] -queuebot:#ubuntu-release- Unapproved: virtualbox-guest-additions-iso (zesty-proposed/multiverse) [5.1.18-1 => 5.1.22-1ubuntu<IP_ADDRESS>] (no packageset)
[15:56] -queuebot:#ubuntu-release- New binary: gnutls28 [i386] (artful-proposed/main) [3.5.8-5ubuntu1] (core)
[16:00] -queuebot:#ubuntu-release- New binary: gnutls28 [s390x] (artful-proposed/main) [3.5.8-5ubuntu1] (core)
[16:01] -queuebot:#ubuntu-release- New binary: gnutls28 [amd64] (artful-proposed/main) [3.5.8-5ubuntu1] (core)
[16:06] -queuebot:#ubuntu-release- New binary: gnutls28 [armhf] (artful-proposed/main) [3.5.8-5ubuntu1] (core)
[16:11] -queuebot:#ubuntu-release- New binary: gnutls28 [arm64] (artful-proposed/main) [3.5.8-5ubuntu1] (core)
[16:13] -queuebot:#ubuntu-release- New binary: gnutls28 [ppc64el] (artful-proposed/main) [3.5.8-5ubuntu1] (core)
[16:23] <nacc> woo, fixed the last regression from src:php-defaults update
[16:27] -queuebot:#ubuntu-release- Unapproved: dh-autoreconf (xenial-proposed/main) [12~ubuntu16.04.1 => 12~ubuntu16.04.2] (core)
[16:31] -queuebot:#ubuntu-release- Unapproved: budgie-artwork (zesty-proposed/universe) [0.7.1 => 0.7.2] (no packageset)
[16:35] -queuebot:#ubuntu-release- Unapproved: rejected budgie-artwork [source] (zesty-proposed) [0.7.2]
[17:16] -queuebot:#ubuntu-release- New binary: node-browserify-rsa [amd64] (artful-proposed/universe) [4.0.1-1] (no packageset)
[17:17] -queuebot:#ubuntu-release- New binary: node-cryptiles [amd64] (artful-proposed/universe) [3.1.1-1] (no packageset)
[17:17] -queuebot:#ubuntu-release- New binary: node-extsprintf [amd64] (artful-proposed/universe) [1.3.0-1] (no packageset)
[17:17] -queuebot:#ubuntu-release- New binary: node-vm-browserify [amd64] (artful-proposed/universe) [0.0.4-1] (no packageset)
[17:17] -queuebot:#ubuntu-release- New binary: node-elliptic [amd64] (artful-proposed/universe) [6.4.0+dfsg-1] (no packageset)
[17:17] -queuebot:#ubuntu-release- New binary: node-getpass [amd64] (artful-proposed/universe) [0.1.7-1] (no packageset)
[17:18] -queuebot:#ubuntu-release- New binary: libpll [amd64] (artful-proposed/universe) [0.0+20160909+ds1-1] (no packageset)
[17:59] -queuebot:#ubuntu-release- Unapproved: openssh (zesty-proposed/main) [1:7.4p1-10 => 1:7.4p1-10ubuntu0.1] (core)
[18:33] <nacc> slangasek: I *believe* now that php-defaults has migrated, src:php7.0 can be demoted to universe? `reverse-depends -c main src:php7.0` is still saying the php-defaults binaries depend on it, but i think that's just a tooling catch-up issue.
[18:33] <nacc> slangasek: and the c-m has flipped around :)
[18:33] <slangasek> nacc: yeah, c-m is gospel; demoting
[18:34] <slangasek> nacc: it does show it as binary-only demotions however
[18:34] <slangasek> implying there are binaries still held in main by something
[18:34] <slangasek> nacc: and this is true on both c-m and c-m-proposed
[18:34] <slangasek> so not tied to the recent migration
[18:39] <nacc> slangasek: ok, i'll check again
[18:48] <nacc> slangasek: hrm, woulnd't either reverse-depends src:php7.0 or reverse-depends -b show whatever was holding it? I also did a grep-dctrl for the old phpapi and all the revdeps are themselves from src:php7.0 or one universe pacakge (sassphp) which is sort of buggy (and new in artful) that i'm working with debian on
[19:24] <slangasek> nacc: certainly, reverse-depends should show what the issue is
[19:25] <slangasek> but since that cache hasn't yet updated with the results of the php-defaults change, it's hard to see
[19:25] <slangasek> nacc: what I do see is that php.*dev were not in the list of binaries to be downgraded
[19:29] <nacc> slangasek: ah ok, i'll look into that, thanks for the hint
[19:31] -queuebot:#ubuntu-release- New: accepted libpll [amd64] (artful-proposed) [0.0+20160909+ds1-1]
[19:31] -queuebot:#ubuntu-release- New: accepted node-cryptiles [amd64] (artful-proposed) [3.1.1-1]
[19:31] -queuebot:#ubuntu-release- New: accepted node-extsprintf [amd64] (artful-proposed) [1.3.0-1]
[19:31] -queuebot:#ubuntu-release- New: accepted node-vm-browserify [amd64] (artful-proposed) [0.0.4-1]
[19:31] -queuebot:#ubuntu-release- New: accepted node-browserify-rsa [amd64] (artful-proposed) [4.0.1-1]
[19:31] -queuebot:#ubuntu-release- New: accepted node-getpass [amd64] (artful-proposed) [0.1.7-1]
[19:31] -queuebot:#ubuntu-release- New: accepted node-elliptic [amd64] (artful-proposed) [6.4.0+dfsg-1]
[21:31] <nacc> slangasek: so it would appear that php7.0-cli php7.0-common php7.0-dev php7.0-json php7.0-opcache php7.0-readline php7.0-xml all are still in main. I'm not sure why, all of the reverse-depends appear to be src:php7.0. Does the migrater need a hint to demote src:php7.0 itself? I expected it would notice it was all self-entangled and figure it out, but perhaps I am wrong
[21:51] <slangasek> nacc: I see php-all-dev/php-dev depends: php7.0-dev depends: php7.0-{cli,common}, [...] so how do you expect these to be dropped out?
[21:52] <nacc> slangasek: php-all-defaults 1:52ubuntu1 (now in a) depends on php7.1-dev, php7.1-json
[21:52] <nacc> slangasek: similarly php-dev 1:52ubuntu1 depends on php7.1-dev
[21:52] <nacc> slangasek: where do you see the php7.0 dependencies?
[21:54] <slangasek> nacc: in my stale packages files
[21:54] <nacc> slangasek: :)
[21:54] <slangasek> nacc: and in reverse-depends output which is also stale
[21:55] <nacc> slangasek: yeah, the r-d output is driving me crazy, since i can see in my chdist that it's incorrect ;)
[21:55] <slangasek> E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/artful/universe/source/Sources  403  Forbidden [IP: <IP_ADDRESS> 80]
[21:55]  * slangasek eyes IS
[21:58] <slangasek> yeah, ok, sources files appear to be awol
[21:59] <slangasek> that might explain some of the issues?
[21:59] <nacc> slangasek: ah that could be
[21:59] <slangasek> eh wait
[21:59] <nacc> hrm, i have deb-src lines in my chdist and it was `apt update`-ing earlier
[22:00] <slangasek> Sources.xz is there, Sources is not, sorry, this is just a local proxy issue that I didn't finish diagnosing before opening my big mouth
[22:00] <nacc> slangasek: ah ok
[22:01] <nacc> slangasek: nothing to apologize for! you're helping me verify my own sanity, as I feel like I've been going in circles on this for a bit now :)
[22:04] <slangasek> nacc: so, everything now LGTM in packages and I'm going to wait for reverse-depends to sort itself before trying to investigate further
[22:06] <nacc> slangasek: ok, that's fine with me
[22:06] <nacc> slangasek: i just wanted to have someone else agree that things look right :)
[22:08] -queuebot:#ubuntu-release- New source: gcc-7 (artful-proposed/primary) [7.1.0-3ubuntu1]
[22:11] -queuebot:#ubuntu-release- New: accepted gcc-7 [source] (artful-proposed) [7.1.0-3ubuntu1]
[22:11] -queuebot:#ubuntu-release- New: accepted gnutls28 [arm64] (artful-proposed) [3.5.8-5ubuntu1]
[22:11] -queuebot:#ubuntu-release- New: accepted gnutls28 [i386] (artful-proposed) [3.5.8-5ubuntu1]
[22:11] -queuebot:#ubuntu-release- New: accepted gnutls28 [s390x] (artful-proposed) [3.5.8-5ubuntu1]
[22:11] -queuebot:#ubuntu-release- New: accepted gnutls28 [amd64] (artful-proposed) [3.5.8-5ubuntu1]
[22:11] -queuebot:#ubuntu-release- New: accepted gnutls28 [ppc64el] (artful-proposed) [3.5.8-5ubuntu1]
[22:11] -queuebot:#ubuntu-release- New: accepted gnutls28 [armhf] (artful-proposed) [3.5.8-5ubuntu1]
[22:54] <slangasek> nacc: reverse-depends now returns clean.  seeded-in-ubuntu?
[22:56] <slangasek> nacc: ahhh it's germinate vs. the archive publisher.  I think these should all fall out on the next publisher run
[23:10] -queuebot:#ubuntu-release- New binary: gcc-7 [s390x] (artful-proposed/main) [7.1.0-3ubuntu1] (no packageset)
[23:12] -queuebot:#ubuntu-release- New binary: node-caseless [amd64] (artful-proposed/universe) [0.12.0-1] (no packageset)
[23:29] -queuebot:#ubuntu-release- New binary: gcc-7 [ppc64el] (artful-proposed/main) [7.1.0-3ubuntu1] (no packageset)


  All wood.  Have had up to 3 dehumidifiers running at a time.  Mold has stayed pretty minimal here.  Key is to never let it get a toe hold, then its hard to eradicate.
[06:21] <InHisName> Bah  you, JonathanD, I was typing real stuff, no fair!
[06:22] <JonathanD> real stuff?
[06:22] <JonathanD> none of those words are real.
[06:23] <InHisName> morning at 2:19am is pretty virtual too.
[06:24] <JonathanD> eh, I just woke up
[06:24] <JonathanD> therefore it is morning.
[06:25] <InHisName> No sign of a sun anywhere at this time.


[06:58] <Skuggen> nacc: About LP: #1686859, Apparmor blocks a test in ruby-riddle because it tries to read a file from the build directory
[06:58] <Skuggen> But this doesn't look like it's a new test, so not sure if it actually affects the build system?
[07:12] <meebey> hello everyone. I have noticed an issue recently that the launchpad auto builder feature seem to use the base xenial repository plus the xenial-updates repository. this creates a problem for Ubuntu LTS users that are disabling the xenial-updates one because packages build using the launchpad builder will have dependencies that cannot be satisfied on pristine xenial, without xenial-updates
[07:13] <meebey> does someone know if I can tell the auto builder to not use the xenial-updates repository so that the binary packages will avoid having higher versioned dependencies than needed?
[07:17] <sarnold> meebey: hit the 'edit ppa dependencies' link, then you can change between a handful of options
[08:08] <meebey> sarnold: so going from "Default" to "Security" should do the trick I guess
[08:08] <meebey> sarnold: I will give that a spin and I will check the next build if it dropped the xenial-updates depdency
[08:08] <meebey> sarnold: thanks for the pointer
[08:43] <mapreri> bdmurray: because in my screen if I put 2 vim instances side-by-side, 99 chars on both won't fit.
[08:44] <Unit193> "Dun do dat"
[08:44] <mapreri> Since I have a 2k display these days my actual limit is > 79, but still < 99.
[08:44] <mapreri> but I like to keep 79, as it happes from time to time to have to use a smaller display
[08:44] <mapreri> Unit193: don't you never copy from one file to another? :P
[08:45] <Laney> I got 99 chars but the screen too small
[08:45] <Unit193> :D
[08:45]  * Laney ahem
[08:54] <mapreri> bdmurray: also, PEP-8 recommends it :P
[09:22] <pitti> juliank: do you happen to know how to pipe apt-get and "| apt-listchanges --what=both --apt" together? i. e. how do I tell  apt-get upgrade to not do anything but print a "version 2 pipeline"?
[09:22] <pitti> I don't want to change "which" in /etc/apt/listchanges.conf (which defaults to "news" at least in Debian)
[09:23] <pitti> err, I mean s/--what/--which/ of course
[09:23] <juliank> pitti: No sorry
[09:25] <pitti> juliank: ok, thanks
[09:33] <doko> jbicha: gtk4.0: you write the gail packages are dropped, but these are still in the control file
[10:33] <smoser> slangasek, we spoke a bit yesterday, just fyi, https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1666573 is the open-iscsi bug that i think is the last bit of failure in its autopackage tests.
[12:36] <jbicha> doko: I was told gtk4 hadn't figured out accessibility yet; I don't know if that means they'll bring back gail or not
[13:37] <rbasak> bdmurray: I think bug 1683237's Zesty task is accurate. It needs someone to drive the SRU though.
[13:38] <rbasak> powersj: ^ I would drop server-next from that bug, as we don't have a ready patch for Zesty. But it's up to you, or we can discuss later as a team.
[13:42] <ahasenack> I can take a look perhaps, I'm familiar with kerberos
[13:45] <rbasak> Can someone remind me where I can find the sources that generate http://reqorts.qa.ubuntu.com/reports/ubuntu-server/ please?
[13:45] <powersj> rbasak: I agree
[13:45] <rbasak> It might be in the crontab only, in which case could someone take a peek please?
[13:46] <rbasak> I can't remember where the script that generates http://reqorts.qa.ubuntu.com/reports/ubuntu-server/merges.html is kept :-/
[13:46] <rbasak> And http://reports.qa.ubuntu.com redirects to ci.ubuntu.com, which seems a little evil to me :-/
[13:50] <rbasak> Aha:  lp:ubuntu-reports
[14:01] <rbasak> apw: I wonder if you can help with lp:ubuntu-reports? Do you (or know who) have access to the cronjob/system it runs on please? I'm asking because you're an admin via ~ubuntu-defect-analysts
[14:01] <apw> rbasak, i might, i have access to a lot of stuff
[14:02] <apw> rbasak, what you trying to do
[14:02] <rbasak> apw: http://reqorts.qa.ubuntu.com/reports/ubuntu-server/merges.html is out of date - it stopped working in September. I'd like to kick it.
[14:02] <rbasak> I'm running the script locally to check it still succeeds.
[14:02] <rbasak> Though I suspect a stale lock. IIRC, something else (sponsoring queue) had broken at a similar time.
[14:04] <apw> rbasak, ok i have access to that box it appears
[14:04] <apw> rbasak, oh but only for kernel perhaps
[14:10] <bdmurray> rbasak: I have access to it.
[14:11] <bdmurray> mapreri: I think you got the wrong nick that starts with bd
[14:11] <mapreri> right, that was meant to be bdrung, sorry
[14:12] <mapreri> bdrung: if you are still interested, look some dozen lines up for my messages :)
[14:15] <rbasak> apw: would you be able to add me to ~ubuntu-reports-dev please?
[14:15] <rbasak> That's so that I can push fixes to lp:ubuntu-reports/server as/when needed.
[14:16] <apw> rbasak, sounds reasonable
[14:20] <fossfreedom_> hi - for a debian package (via a postinst?) any suggestions on where I can setup an environment variable when a terminal session (gnome-terminal or tilix)?  I though about appending to /etc/bash.bashrc but that just seems wrong somehow.
[14:21] <fossfreedom_> s/terminal session/terminal session is run/
[14:22] <cyphermox> bdmurray: hey; looks like the desktop team uses desktop-bugs to track bugmail, but we look for things subscribed by desktop-packages for MIRs; do you know why we're not using just one team for this?
[14:23] <cyphermox> hysterical raisins?
[14:24] <bdmurray> cyphermox: It was some time ago but I don't think they agreed with the packages we thought they should be subscribed to and d-b went to their email and d-p went into the void.
[14:24] <cyphermox> ah
[16:41] <bdmurray> nacc: Did your comment in bug 1593489 mean you want to work on the SRUs for it?
[16:42] <nacc> bdmurray: yeah, i can
[16:56] <xnox> juliank, but the other spaces fix in apt-key / config parsing was good. Apport went down from 9 errors to 1 error.
[16:56] <xnox> =)))))
[16:56] <xnox> apport 2 - 1 juliank
[16:56] <juliank> xnox: Does it use any keys at all, did it use any keys before?
[16:57] <juliank> The problem is: If it just uses the wrong keyrings, fixing it breaks something else.
[16:57] <juliank> If it uses no keyrings, we can decide on how to deal with it :)
[16:57] <xnox> juliank, i think the difference from xenial is that, in the past the sandbox had trusted.gpg with all the keys; now the sandbox only has trusted.gpg.d/ with all the keys as snippets.
[16:58] <xnox> because we moved onto one key per snippet arrangement.
[16:58] <xnox> (as in archive changed, apport changed, and now this is exposed....)
[16:58] <xnox> maybe i need to set more things / settings when calling apt.Cache, I'm happy to do that.
[16:59] <xnox> but e.g. ideally i would not want to construct trusted.gpg keyring out of trusted.gpg.d snippets.
[16:59] <xnox> and my understanding was that trusted.gpg is not required.
[17:06] <juliank> xnox: It's just the LP-PPA key being in the keybox format instead of a public keyring format as required
[17:06] <xnox> juliank, oooooh
[17:06] <xnox> juliank, that would be my bug to fix, and i know even where.
[17:06] <xnox> juliank, thank you, did not spot that.
[17:07] <juliank> xnox: APT should be more helpful, but unfortunately public key packets do not contain a header, making it hard to identify reliably
[17:08] <juliank> There's some patterns we could detect I guess
[17:09] <xnox> juliank, i think i fixed that, and copying the keyring before. but then hit the space bug which is now fixed.
[17:09] <xnox> but i have since lost my fixed up test-suite to use apt-key for key retrieval (to not create keyboxes) and to copy through trusted.gpg.d snippets.
[17:09] <xnox> my bad.
[17:17] <xnox> juliank, and about accept keybox format, was that rejected forever?
[17:18] <juliank> Yup
[17:18] <xnox> juliank, and those who want elliptic curve cryptography can get lost - quantum computing will crack elliptic curve keys before it can crack RSA keys
[17:19] <juliank> Well, if you find a way to get public key packets out of it reasonably easy
[17:19] <xnox> without calling gpg, right?!
[17:20] <xnox> (forking out gpg)
[17:20] <juliank> Yes
[17:20] <juliank> We only have gpgv, we'd have to parse the file ourselves.
[17:43] <xnox> juliank, everything is awesome now =) apport 2 - 3 juliank
[17:43] <juliank> :D
[17:44] <xnox> https://code.launchpad.net/~xnox/apport/no-to-keybox/+merge/323513
[17:46] <juliank> xnox: I don't really want to know how that works in apt-key. There's some weird stuff going on
[17:48] <juliank> Thousand lines of shell script does not read that good.
[17:49] <juliank> I'm not sure we want to keep adv around forever, though
[17:53] <juliank> But well, I'm not sure we'll ever remove it
[18:00] <momken> Hello
[18:00] <momken> Is there any plan to upgrade (k)ubuntu to Qt 5.6.3 or Qt 5.8.1?
[18:01] <momken> These two versions contain certain bug fixes in inserting Persian/Arabic non-visible control chars for Qt text engines
[18:02] <momken> https://bugreports.qt.io/browse/QTBUG-42074
[18:02] <momken> https://bugreports.qt.io/browse/QTBUG-58364
[18:59] <juliank> xnox: So, how (?) did your testing with the systemd timers go?
[19:02] <juliank> I think the locking variant works well
[19:52] <slashd> For SRU, I have uploaded the following : nagios-nrpe | 3.0.1-3ubuntu17.04.1 in Zesty upload queue, but then noticed that I should have use "3.0.1-3ubuntu<IP_ADDRESS>" instead. Can you reject my upload so I can re-upload it with the corrected pkg version ==> https://launchpad.net/ubuntu/zesty/+queue?queue_state=1&queue_text=nagios-nrpe
[20:01] <slangasek> slashd: done
[20:01] <slashd> slangasek, thank you very much
[21:55] <tsimonq2> !info qtbase-opensource-src xenial
[21:55] <tsimonq2> Gah
[21:55] <tsimonq2> !info src:qtbase-opensource-src xenial
[21:56] <tsimonq2> !info qmake-qt5 xenial
[21:56] <tsimonq2> Oh for pete's sake, I'll just do this in a PM, sorry for the spam


[12:13] <leo-unglaub> hey guys..
[12:13] <leo-unglaub> ubuntu ist showing me that i have to do a dist-upgrade
[12:13] <leo-unglaub> http://pastebin.com/HtKDHujK
[12:13] <leo-unglaub> but is that right?
[12:13] <leo-unglaub> removing unity and ubuntu-desktop??
[12:19] <popey> leo-unglaub, if you do "sudo apt-get upgrade", what gets held back?
[12:19] <leo-unglaub> popey: libunity-core-5.0-5 linux-generic linux-headers-generic linux-image-generic unity unity-common unity-services
[12:20] <popey> leo-unglaub, what does apt-cache policy unity   return
[12:20] <leo-unglaub> unity:
[12:20] <leo-unglaub>   Installiert: 5.12+bzr2439ubuntu0+709
[12:20] <leo-unglaub>   Kandidat:    5.12+bzr2444ubuntu0+709
[12:20] <leo-unglaub>   Versionstabelle:
[12:20] <leo-unglaub>      5.12+bzr2444ubuntu0+709 0
[12:20] <leo-unglaub>         500 http://ppa.launchpad.net/unity-team/staging/ubuntu/ precise/main amd64 Packages
[12:20] <leo-unglaub>  *** 5.12+bzr2439ubuntu0+709 0
[12:20] <leo-unglaub>         100 /var/lib/dpkg/status
[12:20] <leo-unglaub>      5.12-0ubuntu1.1 0
[12:20] <leo-unglaub>         500 http://archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages
[12:20] <leo-unglaub>      5.10.0-0ubuntu6 0
[12:20] <leo-unglaub>         500 http://archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
[12:21] <popey> leo-unglaub, why are you using the unity team staging ppa?
[12:21] <leo-unglaub> popey: because the version witch was shipped with 12.04 was to broken on my system
[12:22] <leo-unglaub> i have 3 monitors here
[12:22] <leo-unglaub> and that was a hard one to work with
[12:25] <popey> the staging ppa isn't generally designed for end users to use on a production basis
[12:25] <leo-unglaub> i know...and i don't like it at all...but what else can i do if the "current stable" ist to broken on my system?
[12:25] <leo-unglaub> it was switching to the staging ppa or to a different distro..
[12:27] <popey> there are plenty of options in between bathing the baby and throwing the baby out with the bath water
[12:27] <popey> anway, which bug is fixed in staging which isn't in the stock unity?
[12:27] <popey> i.e. which bug is affecting you?
[12:30] <leo-unglaub> well, your example is not the same. but what would be the solution for that? ask you guys to backport a patch because otherwize it's not working?
[12:31] <popey> well I dont know what the bug you're experiencing is yet, so hard to say
[12:31] <leo-unglaub> i don't know the bug number...but my problem was...
[12:32] <leo-unglaub> if i have 3 monitors connected the mouse starts lagging
[12:32] <leo-unglaub> and the application switcher was sooo lame, it was simply imposible to work with
[12:34] <popey> you left a comment on bug 874619
[12:34] <leo-unglaub> i know, but thats not the one witch got fixed yet
[12:34] <popey> well that one is in commit 2470
[12:35] <leo-unglaub> yes, i know...but thats not the one witch was fixed yet
[12:37] <ugi> which and witch not the same. one has a pointy hat and broom for transportation
[12:38] <leo-unglaub> this is all very funny...but it isn't fixing my problem right now..
[12:38] <ugi> witches cant be fixed. must burn at the stake
[12:38] <leo-unglaub> ???
[12:38] <leo-unglaub> what are you talking about?
[12:39] <ugi> me? why are you talking witches?
[12:39] <popey> ugi, enough..
[12:39] <leo-unglaub> should that be funny?
[12:39] <popey> leo-unglaub, you could wait until that merge lands in the staging ppa
[12:40] <popey> and use do "sudo apt-get upgrade" rather than dist-upgrade till then
[12:43] <leo-unglaub> popey: but my current problem with the package upgrad is not on witch results from code changes..it's a dependency problem
[12:43] <leo-unglaub> in the debian files..
[12:45] <Fifo> Hello how do I enable Unity 3D in VMware?
[12:50] <popey> leo-unglaub, sure I'm just trying to get you back to using precise and precise/updates precise/proposed, rather than staging
[12:50] <ugi> seems not quite enough, but whichever ... or is that whatever? hmm  nm
[12:51] <leo-unglaub> popey: i know, but i can't do that because otherwize my desktop is not useable..
[12:51] <popey> how do you know that?
[12:51] <leo-unglaub> and ican't have a unuseable desktop for a few month
[12:51] <popey> we release stable release updates for unity
[12:51] <leo-unglaub> how i know? i just did the upgrade because otherwize i hade those problems
[12:51] <popey> they hit proposed then updates
[12:52] <popey> well this is why I was asking what the bug is, so I could trace where it is
[12:53] <popey> we cherry-pick updates for precise
[12:53] <leo-unglaub> i don't know the launchpad bug number..i have no idea if someone reported that...
[12:54] <leo-unglaub> there are so much buigs on launchpad that someone not involfed in the programm has problems to find anything
[12:54] <popey> i would recommend you purge the staging ppa, and take the version of unity in the precise updates
[12:54] <popey> and let me know if that's still an issue
[12:55] <popey> and if it is, file a bug
[12:55] <leo-unglaub> okay, if will do that...moment
[12:58] <Fifo> Hello how do I enable Unity 3D in Ubuntu 12.04 running in VMware?
[12:59] <popey> Fifo, does VMWare have some kind of guest extensions / drivers you can install?
[13:01] <popey> Fifo, personally i use virtualbox in which unity 3d works fine, I've never tried in vmware
[13:06] <Fifo> popey: Yes, VMware has VMware Tools, but it doesn't support Unity 3D
[13:06] <popey> bummer
[13:06] <Fifo> popey: I will try to use VirtualBox.
[13:07] <popey> with virtualbox, do the install and then in the guest just do "sudo apt-get install virtualbox-guest-x11"
[13:07] <Fifo> popey: Ubuntu 12.04 needs PAE. How do I enable it?
[13:08] <popey> Fifo, i have not had to enable that in virtualbox
[13:09] <Fifo> popey: But I noticed that it needs PAE to work.
[13:09] <popey> Fifo, looks like its enabled by default in virtualbox
[13:09] <popey> in settings -> system
[13:09] <popey> there's "Extended features: Enable PAE/NX" which on my system is ticked
[13:09] <popey> and I dont recall ticking that myself
[13:10] <Fifo> I have enabled that, it's booting now (why does it take 5 minutes to boot?)
[13:10] <Fifo> (I'm running it from a real CD)
[13:15] <popey> Fifo, takes very little time to boot from an ISO on the hard disk. I rarely boot a VM from optical media
[13:17] <Fifo> popey: I didn't want to waste my disk space because my HDD is low on disk space so I deleted the ISO file.
[13:18] <popey> gotcha
[13:20] <Fifo> It's working...
[13:20] <popey> cool
[13:22] <Fifo> :)
[14:15] <davidcalle> Yo popey
[14:20] <davidcalle> popey, if you are doing country specific requests in a lens, I suggest using http://geoip.ubuntu.com/lookup or http://geoiplookup.wikimedia.org, in addition of locale.
[14:32] <popey> davidcalle, yeah, i saw that you'd used that in the wikipedia lens, I'll probably do the same.


[06:19] <lordievader> Good morning
[06:28] <alkisg> o/
 How to fix wallpaper issue? If I set any desktop wallpaper it's comes to default wallpaper on every reboot
 @pepe -, How to fix wallpaper issue? If I set any desktop wallpaper it's comes to default wallpaper on every reboot
 @pepe -, Ok
 #kubuntu
[08:41] <kinas> hey anyone know how to make dark theme for only KDE software on kubuntu?
[09:00] <kumar29> Facing wallpaper issue . It reset on every boot. I am using kde desktop
[09:01] <diogenes_> kumar29, is it set to start a new session at boot?
[09:02] <kumar29> No
[09:02] <diogenes_> then try that.
[09:03] <kumar29> Only wallaper comes to default on reboot. Widget and everthing is working properly they did not change
[09:04] <kumar29> It does not start new sesion
[09:06] <kumar29> is there anyone?
[09:07] <kumar29> ?
[09:09] <kumar29> is there anyone?
[09:10] <bradh> no.
[09:12] <Maik> !patience | kumar29
[09:13] <kumar29> Thanks
[10:55] <alf75> WINE is ok in Kubuntu ?
[10:55] <alf75> i am using Kubuntu for professional everyday use
[10:55] <alf75> 20.04.02 LTS
[10:59] <Maik> alf1975: don't ask for a opinion because the experience may vary, just try it out yourself.
[11:01] <Maik> and what do you need Wine for? Playing games?
[11:06] <alf1975> Yes
[11:06] <ruenoak> alf1975: wine installs and works fine on Kubuntu I use Q4wine. It really depends on what you are installing and how compatible with wine the application is. I usually install old games that need nothing special to run, so they work well
[11:07] <ruenoak> I would check out Wine HQ for what works and doesn't under wine
[11:08] <bradh> It isn't going to make much difference where you run wine though.
[11:30] <Maik> lol... want Wine for playing Games while they say they use Kubuntu for professional use.....
[11:46] <BluesKaj> Hi folks
[14:37] <krytarik> Maik: But what if they do it professionally!? XD
 KDE Neon vs Kubuntu, which is faster and lighter?
[15:06] <Maik> @Kil opions do not belong in a support channel, telegram is linked to #kubuntu on IRC. So it's more of a offtopic question.
[15:07] <Maik> you could try them both from a live usb stick and make up your mind which is better for you
 @Maik, Yep, sorry :D
[17:18] <unknownentity> help
[17:18] <unknownentity> ls
[17:25] <tomreyn> hi unknownentity
[17:25] <tomreyn> what do you need help with?
[17:27] <unknownentity> hello guys
[17:28] <unknownentity> 1st time using the app. What exactly is it used for ?
[17:29] <Maik> you are in the Kubuntu support channel on IRC
[17:30] <Maik> if you have any Kubuntu related support questions you can ask them here
[17:30] <unknownentity> ok so its like a messaging app striped of its multimedia functions
[17:30] <Maik> it's an IRC client
[17:30] <unknownentity> @maik thank you
[17:30] <Maik> yw
[17:31] <Maik> if you don't have any support question and just want to chat then there's #kubuntu-offtopic or #ubuntu-offtopic
[17:32] <unknownentity> ok thanks
[17:35] <tomreyn> You're using the konversation IRC client, a commonly used IRC client on Kubuntu.
[17:54] <tomreyn> unknown__: if you have general questions on IRC, type   /join #freenode     (without leading spaces)
[17:55] <ilgenio00> we
[17:56] <tomreyn> ?
[17:56] <ilgenio00> im italian
[22:43]  * Euclide wish u "good night !"


[01:35] <Dragnslcr> What's the current "correct" way to install Skype? Using the deb package or the snap?
[01:44] <valorie> !skype
[01:44] <valorie> Dragnslcr: ^^^
[02:42] <Dragnslcr> Thanks valorie
[04:46] <IrcsomeBot1> Eduardo_Jose_Soares was added by: Eduardo_Jose_Soares
[06:22] <lordievader> Good morning
[06:43] <dodi> I want to install Kubuntu in a virtual machine (Virtual Box). How speed up installation?
[06:47] <dodi> nobody here?
[06:55] <oerheks> howto speed up ?
[06:56] <oerheks> get a faster ssd/cpu..
[06:58] <dodi> VM with no guest extensions installed is slow. Any cure?
[07:04] <oerheks> .. the obvious: install is free
[07:07] <dodi> it's free, but not automatic. How should I proceed?
[07:09] <dodi> I cannot remember such problems with my last install (2016)
[07:09] <lordievader> dodi: Did you investigate what is slow? CPU, disk,  etc.
[07:10] <dodi> Most probably it's access to all virtual drives, eventually virtual screen...
[07:11] <lordievader> Did you check?
[07:13] <lordievader> Does Virtualbox even support changing what type of disk you provide?
[07:13] <dodi> my old VM boots within a minute, the current one takes about 10 minutes
[07:14] <lordievader> You didn't check what the disk speed difference is between the virtual disk and where it  resides on?
[07:15] <dodi> I have 1 physical disk, so this cannot make a difference
[07:16] <dodi> Perhaps I have to install development support for compilation of guest additions?
[07:17] <lordievader> That is not what I mean. For example, if the physical disk gives you 50MB/s and the virtual block in the vm only 1MB/s, you know that the conversion from virtual to physical is very slow.
[07:17] <lordievader> But if both numbers are roughly the same, you know that the disk is not the problem.
[07:19] <dodi> I'm just doing a test installation for a friend. If the installation on his system is as slow as on mine, he'll never use nor recommend to use Kubuntu
[07:20] <oerheks> recommendation based on virtualbox install ? i only take bare metal install serious, or kvm
[07:21] <lordievader> oerheks: Same here, but if you want to run it on Windows, you have very little choice.
[07:21] <dodi> My friend has a defunct CD drive on his notebook. How can he install Kubuntu then?
[07:21] <lordievader> A usb stick?
[07:22] <dodi> How does he get Kubuntu on the stick?
[07:23] <oerheks> !usb
[07:24] <oerheks> # 5 #6 #7 from ubuntu, isx or windows
[07:24] <oerheks> or osx
[07:31] <dodi> thanks for the links, I'll check the alternatives. But alternate boot is not an option :-(
[10:48] <BluesKaj> Howdy all
[10:48] <IrcsomeBot1> Dr4g0nS was added by: Dr4g0nS
[12:49] <jim__> hi
[12:52] <jim__> I believe a graphics card is taking too long to initialize if four monitors are attached. if the fourth monitor is attached after the three displays comie up it will work, if all four are connected when the display initializes the display will lock up. is there a way to extend the initialization time?
 the aplicatios gnome is work to kubuntu kde ????
[13:22] <zztopless>  Evening folks.  I've just gone back to 14.04 (technically mint 17.3, but it's the same issue with kb 14.04) on one of my VMs, does anyone know how to turn off the dialog box that appears asking about configuring multiple monitors when using vmware workstation and cycling extra monitors?  I know out can be done, and used to know how, but have forgotten... :/
[13:56] <simulant_> hi can anyone help me out with my wifi please. It no longer shows or works in kubuntu anymore... not sure why, it used to work, then after some updates it no longer worked. then i upgraded to bionic and it still doesn't work
[13:58] <diogenes_> simulant_, open driver manager and see what's in there for wifi card
[14:02] <simulant_> diogenes_: it just says "your computer requires no proprietary drivers"
[14:02] <simulant_> diogenes_: nothing in there listed for graphics cards or wifi
[14:03] <diogenes_> simulant_, run: sudo rfkill list
[14:03] <simulant_> lspci shows: 02:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8191SEvB Wireless LAN Controller (rev 10)
[14:04] <simulant_> diogenes_: ah ok it says phy0: Wireless LAN - soft blocked: no, Hard blocked: yes
[14:05] <diogenes_> simulant_, so it's your key switch
[14:05] <diogenes_> some keyboard combination
[14:06] <simulant_> diogenes_: ah blimey you're right!
[14:06] <simulant_> diogenes_: thanks
[14:06] <diogenes_> :)
[14:06] <simulant_> diogenes_: much appreciated :)
[14:06] <diogenes_> no problem
[15:29] <viewer|64020> Hello, I am a total Linux noob (switched to kubuntu on my laptop yesterday), and I would really appreciate some help
[15:30] <viewer|64020> I can't seem to change my elan trackpad speed in the settings. I tried to change it using xinput, but to no avail
[15:31] <viewer|64020> I used xinput set-prop 11 301 3.000000, but it gave me an error
[17:09] <pavel_> hello. may be someone have problem with using fish:// (ssh) on Dolphin and krusader because download speed high 8MB/s but upload only 300 -500 KB/s. test using terminal download and upload speed high, test on nautilus the same high speed but on Dolphin and krusader slow upload
[17:09] <pavel_> May be someone know about it?
[17:54] <hangar18> does anyone know how long it takes for a new username to take effect across all of the ubuntu/openid sites
[19:03] <Novell> Hi, I upgraded to 18.04 today and now I'm missing kdesudo and can't seem to find it in any package.. What package is it I should install to get it back?
[19:15] <krytarik> Novell: Debian bug 875107
[19:17] <Novell> krytarik: right, but kdesu "kdesu: command not found"
[19:20] <krytarik> Well, it's in the package "kde-cli-tools", which is installed by default anyway.
[19:21] <Novell> I see, but not installed in a usable way (by default)
[19:21] <Novell> Guess a bug should be registered that it's installed in a path that isn't included in $PATH
[19:24] <krytarik> There actually is one already - Debian bug 853899
[21:07] <estan> hm. after the upgrade to bionic, it seems bionic-backports is enabled in my /etc/apt/sources.list. is that normal? i'm pretty sure i didn't have backports enabled before the upgraade.


[00:00] <hggdh> bcurtis, thank you for your help. You can follow the link on the chat topic for more information on what to do/how to triage
[00:00] <hggdh> bcurtis, this is a good start: http://wiki.ubuntu.com/HelpingWithBugs
[00:01] <bcurtis> hggdh, thanks I have skimmed them, and i think for me it's just a matter of hands on and hope i don't screw things up too bad
[00:01] <bdrung> bcurtis: and if you are unsure, what to do: ask
[00:03] <emgent> hello
[00:03] <hggdh> emgent, hello
[00:03] <hggdh> bcurtis, this is correct: when in doubt, ask. We will answer
[00:05] <bcurtis> ok, so for bug 260754, appears to be a wishlist but doesn't have any package associated and seems kind of vague.  just for experience.. whats the best way to handle it?
[00:06] <hggdh> heh
[00:07] <hggdh> this is actually a packaging request, but without the correct groups subscribed
[00:07] <hggdh> a suggestion, right now: do not touch it. See https://wiki.ubuntu.com/BugSquad/KnowledgeBase
[00:08] <bcurtis> so in your shoes, you wouldn't touch it?
[00:08] <bdrung> bcurtis: a good help are the standard responses:  without the correct groups sub
[00:08] <hggdh> specifically, see https://wiki.ubuntu.com/Bugs/HowToTriage#Special%20types%20of%20bugs. I am still trying to find and document exactly what is expected to be done with any of the special bugs
[00:09] <hggdh> bcurtis, indeed, I would not touch it. Not until I was to be completely clear on how to proceed
[00:10] <hggdh> s/was/were
[00:11] <bcurtis> ok
[00:11] <hggdh> bcurtis, another good approach to learning is to fix oneself on a few packages (those you more easily identify yourself with), and gain experience there
[00:12] <bcurtis> ok
[00:12] <bdrung> bcurtis: and going to bug jams
[00:12] <bcurtis> bdrung: which are?
[00:12] <bdrung> bcurtis: where do you live?
[00:13] <bcurtis> bdrung: outside of Washington DC USA
[00:13] <hggdh> yes, a bug jam is usually a good place to learn: each of them usually have a good triager/maintainer local, answering questions and explaining procedures
[00:15] <bdrung> bcurtis: have a look at https://wiki.ubuntu.com/GlobalBugJam . this was the global and recent
[00:21] <bcurtis> thank you all for your help
[00:21] <bdrung> i have edited bug #260754: modified title, added needs-packaging tag, checked if it is already in ubuntu or debian and then confirmed this bug. everyting beyond is something for motu
[00:27] <bcurtis> so if it isn't in either.. what do you then do?
[00:29] <bdrung> bcurtis: someone have to package it. if you are interested in packaging have a look at: http://www.debian.org/doc/manuals/maint-guide/
[00:29] <bdrung> there are more resources about it: https://wiki.ubuntu.com/PackagingGuide/Lists/DocumentationResources
[00:30] <bcurtis> ok.. then if you find it.. its marked as invalid and a reason would be "already in "debian unstable" ...?
[00:30] <bdrung> yes
[00:30] <bcurtis> ok
[00:30] <bdrung> if it isn't in either you confirm the bug
[00:31] <bcurtis> and mark a "needs packaging"
[00:32] <bdrung> whit hyphen
[00:32] <bdrung> change the title to look like "[needs-packaging] program-name"
[00:38] <bcurtis> bdrung, hggdh, Thanks!
[00:38] <bdrung> np
[00:39] <bdrung> helping people to get involved is good
[00:44] <bdrung> bcurtis: do you heard about 5-a-day?
[00:44] <bcurtis> i think so.. take care of 5 bugs a day if you can
[00:50] <bdrung> bcurtis: and interested?
[00:51] <bcurtis> yeah, i try to get 5 bugs a day
[00:52] <bdrung> bcurtis: have a look at https://wiki.ubuntu.com/5-A-Day/Reporting
[00:52] <bdrung> then you can see your result in http://daniel.holba.ch/5-a-day-stats/
[02:13] <marnanel> Should I be able to write:   bzr branch bzr+ssh://bzr-playground.gnome.org/fast-user-switch-applet/trunk/ bzr+ssh://bzr-playground.gnome.org/~tthurman/fast-user-switch-applet/awn/  ?  It says that "...f-u-s-a/trunk/" is not a branch.
[02:14] <marnanel> oops
[02:14] <marnanel> wrong channel entirely
[02:14]  * marnanel apologises.
[02:15] <james_w> hi marnanel, here is fine too
[02:16] <james_w> ah, no, sorry, it is the wrong channel, I assumed this was #bzr
[02:17]  * marnanel grins
[05:50] <aliciapg> so yeah...i need help with my soundcard
[05:57] <aliciapg> and i'm getting no help
[05:57] <aliciapg> yeah
[11:07] <cacf3b2074> hi
[11:08] <aron_> hi
[11:08] <cacf3b2074> process nm-applet has a bug, how to report it
[11:08] <cacf3b2074> same question for x-session-manager,  btw and how to find their description
[11:09] <afflux> https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+filebug
[11:09] <afflux> cacf3b2074: see link above for nm-applet
[11:09] <cacf3b2074> afflux: but which application
[11:09] <cacf3b2074> oh right
[11:09] <cacf3b2074> how do you easly find this information?  synaptic was not helpfull
[11:09] <afflux> cacf3b2074: what do you mean by "how to find their description"?
[11:10] <cacf3b2074> I want to find package name knowing the name of the process, sometimes its diffrent
[11:10] <afflux> cacf3b2074: "dpkg -S nm-applet", or, to be more specific: dpkg -S /usr/bin/nm-applet
[11:10] <aron_> first,check in launchpad if your bug has already commited,if not,commit
[11:11] <cacf3b2074> ok
[11:11] <afflux> cacf3b2074: note that launchpad records the bugs for source packages (which means, the names can differ from the actual packages you have installed)
[11:11] <aron_> yes
[11:11] <afflux> cacf3b2074: to find the source package for a binary package, you can use "apt-cache madison binary-package-name"
[11:12] <cacf3b2074> should flaws in philosophy that lead to sociall based attacks be reported as security issues, or just technical ones (like buffer overflow etc)
[11:13] <cacf3b2074> apt-cache madison x-session-manager    shows nothing
[11:16] <afflux> cacf3b2074: x-session-manager is a link to a different program. You can check to what it points to by writing: readlink -f /usr/bin/x-session-manager
[11:24] <cacf3b2074> thanks, that worked afflux
[11:28] <cacf3b2074> bad planning of how gnome session works can force user to disclose his password. security vulnerability or not?
[11:29] <cacf3b2074> *disclose password to 3rd party
[11:30] <afflux> cacf3b2074: can you explain it a bit more please?
[11:35] <cacf3b2074> afflux: 1. leave office with locked desktop
[11:35] <cacf3b2074> 2. thunderstorm
[11:35] <cacf3b2074> 3. call office maintaince or co-worker to turn off coptuer.... whooops.
[11:36] <cacf3b2074> eith you have to give them own password,  or ask them to force turn off (4 second on power key) but then FS corruption
[11:37] <afflux> cacf3b2074: to avoid FS corruption, use SysRQ keys (see google/wikipedia). Either you want security and noone can access the computer without a passwort, or you don't, and someone can do whatever he wants.
[11:37] <cacf3b2074> you can work around this by creating speciall user just for this purpose and giving password to that... but imho it would be better to add a  Turn-Off  option to the locked login screen instead
[11:38] <cacf3b2074> yes, I want noone to *access* my dekstop,  but I want to allow to turn off the computer by anyone with phisical access.   If anyone has phisical access then he always CAN turn off the compuer (plug out power) - so why not allow them to turn off the computer gracefully
[11:38] <cacf3b2074> *spelling
[11:39] <afflux> cacf3b2074: I'm not sure a bug is the right place to discuss this. Consider bringing this up at brainstorm.ubuntu.com or at the mailinglists
[11:42] <cacf3b2074> brainstorm is the place when people write down ideas, then vote for them, and finally - do nothing about them right?"
[11:42] <cacf3b2074> which ML ?
[11:51] <afflux> cacf3b2074: I'd guess ubuntu-devel-discuss, but I'm not sure there.
[12:00] <cacf3b2074> or perhaps it should be a blueprint?
[12:01] <cacf3b2074> I think overall that it ubuntu power-off desktop sucks,  and it would be fixed by  1) making password locks to have option to shutdown (esp. for physical access)       2) power key pressed several times will always shut down
[13:05] <Ampelbein> hi! could some member of bug-control please have a look at bug 260761 ? i think it could be set to triaged. Regarding importance I would say its high, since networking is a very core component of ubuntu/linux.
[13:08] <Ampelbein> Another one: Bug 259414 . I think this could also be set to triaged. regarding importance i'm undecided whether low or medium. i tend to medium. opinions?
[13:14] <lifeless> 1;2c1;2c1;2c1;2c1;2c/win 18
[13:15] <Ampelbein> ?
[13:15] <bdrung> lifeless: ???
[13:15] <lifeless> confused terminal
[13:16] <bdrung> Ampelbein: bug #260761 should be marked as regression
[13:16] <Ampelbein> ok. will add the tag.
[13:16] <bdrung> because it works in hardy
[13:17] <Ampelbein> didn't think of that. thanks for the reminder.
[13:18] <bdrung> and high is right (-> A problem with an essential hardware component (disk controller, laptop built-in wireless, video card, keyboard, mouse) )
[13:21] <bdrung> Ampelbein: does the wlan card not work or is only the card wrong detected?
[13:21] <bdrung> if it is only wrong named, its not high but low
[13:22] <Ampelbein> its only wrong detected. the card is working according to dmesg.
[13:24] <Ampelbein> but there may be some "special" functions and parameters not working since it is detected wrong.
[13:24] <Ampelbein> don't know, i'm too little a developer to judge this.
[13:26] <bdrung> "special" functions may be using the card as accesspoint point
[13:26] <bdrung> but if he can use the card to get an internet connection there is no need to set the importance to high
[13:27] <Ampelbein> ok, understood. so "low" would be correct?
[13:27] <bdrung> i have set it to low, if he reports any issues due to its wrong detections we can adjust the importance
[13:27] <bdrung> yes
[13:28] <Ampelbein> and should i add to the description explicitly that its working, just wrong detected?
[13:28] <Ampelbein> (i think yes)
[13:29] <bdrung> Ampelbein: yes
[13:31] <Ampelbein> bdrung: ok, thank you for your help.
[13:31] <bdrung> you're welcome
[14:56] <Rocket2DMn> can somebody please check if we can close bug 64324
[14:59] <Rocket2DMn> same with bug 161803 please
[16:00] <afflux> I wonder if this sentence is correct: "wondering *is* this still an issue for you" - https://wiki.ubuntu.com/Bugs/Responses#Old%20untouched%20bugs
[18:25] <Rocket2DMn> Can somebody with wireless debugging experience see bug 190144 and request any more information that is needed
[18:37] <chrisccoulson> Rocket2DMn, just looking at bug 190144
[18:37] <Rocket2DMn> thanks chrisccoulson
[18:37] <chrisccoulson> you should probably initially ask the reporter to provide all the information as per the kernel teams bug policy (I see they've already added their dmesg output)
[18:38] <chrisccoulson> in addition, I'd get them to attach their kern.log and their syslog (which might contain some messages from networkmanager)
[18:38] <Rocket2DMn> yeah the thought had occurred to me, i was hoping somebody also knew of a specific driver package that it could be assigned to, but it doesnt seem like it
[18:39] <chrisccoulson> the kernel is probably the best place for now
[18:39] <Rocket2DMn> chrisccoulson, do you want to take the triage from where i left off?
[18:39] <chrisccoulson> Rocket2DMn, i'll leave it to you if you want ;)
[18:40] <chrisccoulson> i'll subscribe and have a look through their logs when they've provided the information
[18:40] <chrisccoulson> although i probably wouldn't be that much help!
[18:40] <Rocket2DMn> If you think you can folow through with it, then it's all yours.  I've been going through and trying to close out old bugs.  Most users never get back, then I handle those that do, but the workload is piling up
[18:40] <Rocket2DMn> I can still try and follow through though
[18:41] <chrisccoulson> i'll ask for the extra info on that bug report in a bit
[18:41] <chrisccoulson> just looking at bug 180743 as well actually
[18:41] <Rocket2DMn> ok, thanks, i'm subscribed so i'll follow the progress
[18:42] <Rocket2DMn> I get the feeling that latter bug will just get closed
[18:42] <chrisccoulson> i can confirm that bug actually. i had a look through the code for apport and update-notifier a few weeks ago and i can see what is going on, but i never got round to posting my findings
[18:43] <chrisccoulson> and i'm not sure whether the bug should be update-notifier or apport (or both)
[18:46] <Rocket2DMn> well, which project code were you looking at exactly
[18:46] <Rocket2DMn> sounds like probably the notifier
[18:48] <chrisccoulson> the problem is that when files change in /var/crash, update-notifier calls apport-checkreports. This indicates that there are new reports if any files modified time is newer than their access time
[18:48] <chrisccoulson> the problem then is with the logic in update-notifier, which repeatedly displays the notification for system crash reports only
[18:49] <chrisccoulson> for user crash reports, it calls apport-gtk which pops up the dialog when the report is done
[18:49] <maco> you know you're looking at old bugs when they've got 5-digit bug numbers
[18:51] <chrisccoulson> update-notifier needs to wait until apport is done before it displays the notfication. apport currently takes out an exclusive lock on /var/crash/.lock when it is working, but i don't think there is any way of getting update-notifier to use this as a way of determining if apport is still running
[19:41] <crimsun> 260664 is definitely a popular one.
[19:41] <maco> yeah, seriously
[19:42] <maco> it seems more like "raise your hand if -21 *didn't* clobber your wifi"
[19:43] <maco> is bug 77435 more likely an OOo bug or an OpenBox bug?
[19:43] <crimsun> that would be me - thanks for unsupported devices needing ndiswrapper.
[20:37] <pwnguin> maco: actually, i think my wifi works fine
[20:38] <maco> pwnguin: crimsun and i each marked a dupe of that bug in a 5 minute time span, that's why we're commenting on it
[20:38] <pwnguin> ah
[20:38] <maco> ours are working just fine...seeing as we're using the library's wifi right now
[20:39] <pwnguin> "we"?
[20:39] <maco> crimsun and i
[20:39] <maco> we're having our own little 2-person bug jam
[20:40] <pwnguin> heh
[20:40] <pwnguin> im at work, watching debconf videos ;)
[20:41] <maco> haha.  im going through new/undecided bugs that show up in a search for "Edgy" and asking if the problem still exists so i can close them.
[20:42] <maco> done about 50 of those today, i think.  we were doing this for a few hours last night in a cafe too.
[20:42] <maco> im counting last night's since it was after midnight :P
[20:43] <pwnguin> so when you do that, do you try to duplicate it on your own first?
[20:44] <maco> if its an app i have or hardware i have, but a lot of them are hardware bugs that i dont have the equipment to reproduce
[20:44] <maco> s/a lot/most/
[20:45] <pwnguin> it might be handy to search for hardware you do have ;)
[20:46] <maco> oh yeah...
[20:46] <pwnguin> it'd generate less churn I think, but some people seem to think that's a goal
[20:47] <maco> i should also file 4 bugs i can think of off the top of my head
[20:47] <maco> well if they're edgy bugs, they might as well be closed. and if they're still open from then and reproducible, might as well get some more info on them.
[20:47] <maco> just sitting there being ignored doesn't really do any good
[20:48] <pwnguin> well sure. I'm just trying to thing of ways to improve the many eyes thing
[20:50] <pwnguin> by looking for stuff you have the hardware for, you reduce the number of round trips needed, and can get to fixing it that much faster ;)
[20:52] <pwnguin> obviously if you run out of such bugs, other low effort / low lying fruit are suitable
[20:52] <maco> the few bugs ive seen for my hardware (unlike crimsun i buy hardware because it is compatible...he's disappointed his sound card works properly because now he can't fix it) in launchpad...they seem to be "wontfix"
[20:53] <maco> there's one that is fixed upstream, kind of, but it'd require too much new stuff to get into intrepid
[20:53] <maco> but i guess i should file some bugs on my hardware
[20:54] <crimsun> it actually doesn't work correctly.  All the fixes that are required are mundane, rote ones.
[20:54] <crimsun> it->conexant patch
[20:54] <maco> what doesn't work?
[20:54] <maco> oh your sound card
[20:54] <maco> yeah neither does mine, but you dont want to fix my audio bugs
[20:55] <maco> on either of the two laptops that have them
[20:55] <crimsun> no, I don't want to fix them /right now/.  You'll get to the point where you understand how and why you need to fix what.
[20:56] <pwnguin> is crimsun training a replacement?
[20:56] <maco> how and why whom what?  i want you to teach me how these drivers work so i can at least make an attempt at either fixing it or letting the magic blue smoke out of my speakers
[20:56] <maco> preferably the former
[20:56] <crimsun> maco: I can't force-feed an understanding of the audio stack in a short term.
[20:57] <maco> you havent taught me anything in like...a month
[20:57] <crimsun> maco: actually, you haven't been watching ;p
[20:57] <maco> you're on the other side of the table
[20:57] <crimsun> maco: and for two of those weeks, you were in .eu
[20:57] <crimsun> so ;p
[20:57] <maco> well yes, but...
[20:57] <maco> the teaching started on IRC and i had IRC there
[20:58] <crimsun> anyhoo, this is quickly outside the scope of this channel.
[20:58] <maco> yes
[20:58] <maco> pwnguin: i asked him at the hardy release party if he wanted an apprentice
[20:59] <pwnguin> which channel has "making audio work" as it's scope?
[20:59] <crimsun> you'd need to constrain "making audio work" a bit.
[21:00] <maco> pwnguin: you want crimsun's "utterly unofficial support" channel?
[21:00] <pwnguin> "unofficial"?
[21:00] <crimsun> (I don't head up ubuntu-audio any more, so anything I recommend can only be considered and not taken to be the line.)
[21:02] <maco> hey look there *is* a bug filed for my webcam, and there's a driver that's known to work for it.
[21:03] <pwnguin> see, it's already more rewarding :)
[21:03] <maco> it doesn't appear to need a new libusb like my other unsupported device.  can it be nominated for inclusion in intrepid, then?
[21:04] <pwnguin> well anything can be nominated
[21:04] <pwnguin> and exceptions can always be made
[21:05] <maco> alright well its bug 215604
[21:06] <pwnguin> daniel drake again
[21:06] <maco> yes, he's responsible for both drivers that would bring my laptop up to nearly perfect support
[21:06] <pwnguin> fprint?
[21:06] <maco> his upeksonly driver for libfprint is the other one
[21:06] <maco> it requires a *way* newer libusb though
[21:07] <pwnguin> does thinkfinger not work?
[21:07] <maco> no
[21:07] <maco> this is a upek touchstrip sensor-only reader
[21:07] <pwnguin> fun
[21:07] <maco> as opposed to the upek touchstrip that processes the image internally
[21:07] <maco> which is also different from the thinkfinger one
[21:08] <pwnguin> what
[21:08] <pwnguin> no
[21:08] <maco> there are at least 5 drivers in libfprint now
[21:08] <pwnguin> yea
[21:09] <pwnguin> i have Bus 002 Device 003: ID 0483:2016 SGS Thomson Microelectronics Fingerprint Reader
[21:09] <pwnguin> been working since feisty
[21:09] <pwnguin> via thinkfinger
[21:09] <pwnguin> but yes, there are newer and unsupported devices
[21:09] <maco> http://reactivated.net/fprint/wiki/Driver_ID_assignments
[21:10] <maco> the driver i need was committed in july and requires libusb 0.9 which crimsun says is wayyy too new for intrepid
[21:10] <maco> apparently there are 9 now
[21:11] <pwnguin> the touchstrip that processes internally is the thinkfinger one
[21:11] <pwnguin> afaik
[21:11] <maco> oh ok
[21:11] <maco> theres that upektc and upekts idk which is which
[21:13] <pwnguin> our sysadmin and I have had fingerprint readers in laptops for a while, so i stole the debian fingerforce teams' thinkfinger package for our use
[21:13] <maco> gotcha
[21:13] <pwnguin> i should probably test out fprint on intrepid...
[21:17] <pwnguin> maco: given that we're transitioning to .27 it seems, you might be able to get gl860 in intrepid too
[21:19] <pwnguin> maco: do you know how to triage kernel bugs?
[21:20] <maco> no
[21:20] <maco> not really
[21:20] <pwnguin> https://wiki.ubuntu.com/KernelTeamBugPolicies
[21:20] <maco> i need to upgrade to intrepid soonish
[21:21] <pwnguin> yea
[21:21] <maco> i said yesterday that my relative lack of bugs is what's keeping me from being to anxious about upgrading, but if there's hope of the bugs i wasnt expecting a fix on being fixed...
[21:21] <pwnguin> have you considered dual booting?
[21:22] <pwnguin> intrepid doens't have to be an either or situation
[21:22] <maco> last time i did that, well...i like to share my /home partition, and then they fight and then lack of backwards compatibility makes the old version unable to understand my /home directory anyway, so i dont bother with dual booting stable/unstable anymore
[21:23] <pwnguin> i seem to get by okay
[21:23] <maco> i just havent really gotten around to upgrading. itd be easier if i had stable enough wifi to get an iso or to be sure i wouldnt drop in the middle of downloading the updates
[21:24] <pwnguin> the only bug ive found is that update-manager announces ubuntu+1 when running stable
[21:24] <maco> seeing as i'm in need of a pringle cantenna like xkcd has...
[21:37] <Ampelbein> Hi! Could some member of bug-control please check on bug 260941 ? I think it could be set to status triaged, low importance.
[21:41] <hggdh> Ampelbein, I set it to traiged/Low. Thank you (and, hopefully, you will be able to do same by yourself soon)
[21:41] <Ampelbein> ;-) Thanks.
[21:44] <dupondje> somebody any id if there are some probs with Intrepid atm ? cause when I'm logged in into gnome, I don't get a login sound, no icons, no panel :(
[21:44] <Ampelbein> dupondje: works for me. but you could check in #ubuntu+1
[21:45] <dupondje> its death there :p
[21:47] <dupondje> its kinda strange :s
[22:29] <hggdh> dupondje, you can check ~/.xsession-errors for messages
[22:29] <dupondje> ofc
[22:30] <dupondje> lotsa messages :)
[22:31] <hggdh> yay... now to filter what might be a real error from simple debug messages ;-)
[22:32] <dupondje> it cleans file after a gdm restart ?
[22:33] <dupondje> cause now I got it fixxed by changing the default session @ logon ...
[22:33] <dupondje> dunno what caused it :s
[22:48] <bdrung> how to gather information on kernel bug while shutdown?
[23:17] <hggdh> dupondje, .xsession-errors is recreated every login