[02:02] <aeoril> Hello! I am interested in becoming an Ubuntu developer - not apps, but Ubuntu itself
[02:03] <aeoril> I have bought the book "Tanenbaum, Andrew S.; Bos, Herbert (2014-04-02). Modern Operating Systems (4th Edition). Prentice Hall. Kindle Edition." to start learning OS theory
[02:04] <aeoril> but it has lots of typos and I am not sure of how accurate it is.  I am interested in low-level stuff, like kernel, module, vm, etc.
[02:06] <aeoril> What are good resources to get a background in theory to work my way into this type of development?  I have a background in C programming in embedded real time systems and simulation systems, as well as dabbling in Unix/Linux drivers, modules, etc.
[02:07] <aeoril> kernel, module, drivers, vms, etc*
[02:24] <aeoril> Note that I am currently reading the Ubuntu documentation on development (based on the link in the topic of this channel).  My question above is more geared toward theory, architecture and design of operating systems such as one might get in a computer science curriculum
[03:24] <hyperair> what's the equivalent for udisksctl power-off -b /dev/sdb on a machine without udisks?
[03:25] <hyperair> none of the /sbin/eject modes seem to do the right thing
[05:16] <pitti> Good morning
[05:17] <pitti> hyperair: correct, ther is no equivalent; eject is the closest thing to it
[05:50] <RAOF> pitti: Is a vivid machine booted with systemd expected to be able to shutdown at the moment?
[05:58] <pitti> RAOF: yes, of course
[05:59] <RAOF> In a related query, what are the interesting logs when it doesn't? :)
[06:00] <pitti> RAOF: /usr/share/doc/systemd/README.Debian has a section "Debugging boot/shutdown problems"
[06:00] <RAOF> Also, systemd dramatically regresses boot speed for me, because it seems to want to write 0s to my 8GB swapfile in /var/cache/swapfile each boot. But that's a simple bug report.
[06:00] <RAOF> pitti: Ta.
[06:00] <pitti> RAOF: i. e. enable the debugging shell, shut down, then switch to it, and see which job is hanging
[06:10] <hyperair> pitti: ugh really
[06:10] <pitti> hyperair: why "ugh"?
[06:11] <hyperair> pitti: because there's no proper eject tool aside from udisks?
[06:11] <hyperair> someone was asking on ##linux about usb_modeswitch
[06:11] <pitti> eject works fine
[06:11] <hyperair> and i was trying to get him to manually eject it, but there wasn't udisks so...
[06:11] <pitti> the "power down the host controller" of udisks does even more, but it's more like a goodie than a required thing
[06:11] <hyperair> hmm
[06:11] <pitti> e. g. for ipods and stuff which still warn if you merely eject
[06:12] <hyperair> kinda odd that we don't have an actual mass-storage eject tool though
[06:12] <hyperair> you'd think that eject would get that functionality
[06:12] <hyperair> instead of just doing a cdrom eject
[06:12] <pitti> what's missing in eject?
[06:12] <pitti> it doesn't just cd-rom eject
[06:12] <pitti> it also disconnects USB sticks, SD cards and the like, but just the medium
[06:12] <hyperair> oh yeah it does a scsi eject, which for some reason isn't the right kind of eject either
[06:12] <pitti> not the usb host controller
[06:13] <hyperair> it doesn't actually do a usb disconnect, does it?
[06:13] <pitti> usb-modeswitch is a special case for 3G sticks and the like
[06:13] <hyperair> yeah it is
[06:13] <hyperair> except sometimes it doesn't work, and all that's needed is a simple udisksctl power-off
[06:13] <pitti> eject doesn't do an USB disconnect, no (as I said); it merely ejects the medium
[06:13] <hyperair> that's the thing. i was kinda hoping for the usb disconnect stuff
[06:14] <hyperair> seems to be the kind of eject that usb devices actually expect
[06:14] <pitti> most of them don't
[06:15] <pitti> ipods are pretty much the only one I know
[06:15] <pitti> (bbl)
[06:15] <hyperair> hmm okay
[07:01] <darkxst> apw, what is the status of bug 1410480? this completely breaks installing via ubiquity  on Ubuntu GNOME and probably most other flavours
[07:01] <darkxst> and its alpha2 this week as well
[07:02] <pitti> yes, it's not flavor specific, happens for ubuntu as well
[07:03] <darkxst> pitti, how did it get though the automated tests then?
[07:04] <darkxst> hmm ubiquity autopilot tests havent run in 6weeks?
[07:05] <pitti> apparently yes, then
[07:49] <dholbach> good morning
[08:03] <maclin> Hi,  Ubuntu Installer Team,  could someone help to review the merge request: https://code.launchpad.net/~maclin.jun/ubiquity/fix_1304410/+merge/246064
[08:11] <ngaio> is it reasonable to assume Ubuntu vivid will feature QT 5.4?
[08:20] <LocutusOfBorg1> hi people!
[08:23] <Unit193> Howdy.
[08:54] <LocutusOfBorg1> hi folks, quick question: I'm trying to fix 1411507
[08:54] <LocutusOfBorg1> the problem: now the version in trusty is 4.3.10-1
[08:55] <LocutusOfBorg1> since I'm the maintainer I'm preparing the debdiff with 4.3.10-1ubuntu1 rather than ubuntu0.1 as suffix
[08:55] <LocutusOfBorg1> is that ok?
[09:17] <dholbach> @pilot in
[09:29] <ochosi> dholbach: in case you'll be reviewing xdg-utils MRs and you have any questions just lemme know!
[09:30] <dholbach> ochosi, there is nothing for xdg-utils on http://reqorts.qa.ubuntu.com/reports/sponsoring/?
[09:30] <ochosi> oh, i guess i need to subscribe ubuntu-sponsors on https://code.launchpad.net/~ubuntu-branches/ubuntu/vivid/xdg-utils/vivid/+activereviews
[09:31] <dholbach> no, that shouldn't be necessary - that's just for bug reports
[09:31] <dholbach> let me see
[09:31] <pitti> it's already approved, maybe that's why?
[09:32] <dholbach> yes, but it wasn't landed
[09:32] <dholbach> seb128,  can you comment on https://code.launchpad.net/~ochosi/ubuntu/vivid/xdg-utils/drop_xserver_patch/+merge/246101?
[09:32] <dholbach> https://code.launchpad.net/~thad-fisch/ubuntu/vivid/xdg-utils/lp1363540/+merge/246820 was approved by ochosi (who doesn't have upload rights)
[09:32] <seb128> dholbach, I already did?
[09:32] <dholbach> seb128, it wasn't landed AFAICS
[09:32] <seb128> dholbach, no, just approved
[09:32] <dholbach> right
[09:33] <dholbach> that got it off the sponsoring list
[09:33] <seb128> feel free to upload it
[09:33] <seb128> I just didn't get to it yet
[09:33] <seb128> what, approving?
[09:33] <dholbach> I wasn't complaining
[09:33] <dholbach> yes
[09:33] <seb128> why?
[09:33] <seb128> the intend was to say "it's ready to be sponsored"
[09:33] <dholbach> I tried to point out a workflow issue
[09:33] <seb128> to "it has been uploaded"
[09:33] <seb128> thanks for that
[09:33] <seb128> I though that only "merged" would get it out of the list
[09:34] <dholbach> right
[09:34] <dholbach> I'll take a look at the sponsoring script and see what the result would look like if we had "approved" MPs on there too
[09:35] <seb128> thanks
[09:35]  * ochosi apologizes if he has caused any sort of inconvenience here
[09:35] <seb128> sorry for the mistake, and thanks for pointing it out
[09:35] <seb128> ochosi, no, not at all
[09:35] <dholbach> no worries
[09:35] <seb128> I just assumed that if I reviewed without having the slot for actual upload it would still be useful
[09:35] <seb128> I didn't get that it would get it out of the list
[09:38] <ochosi> actually that's good to know
[09:38] <ochosi> i'll keep that in mind too
[09:38] <ochosi> i obviously made a similar mistake (even without having upload rights, i thought reviewing/commenting the code/MR would be useful)
[09:39] <dholbach> I'll play around with the sponsoring script now and let you know if the world breaks, if we add 'Approved' MPs as well.
[09:39] <dholbach> ochosi, no, I think it's great that you added your support for it
[09:40] <ochosi> oh ok, so just to get the most out of this: was it ok (procedure-wise) to come here and ask the current pilot? or what could i have done differently not to disrupt your workflow
[09:45] <dholbach> ochosi, yes, that was perfectly fine :)
[09:46] <dholbach> ochosi, I didn't expect the MP to fall off the radar when seb and you set it to 'Approved'
[09:46] <dholbach> so I'm just checking if there's a good way to fix the sponsoring overview :)
[09:46] <ochosi> sounds good :)
[09:46] <Laney> There's probably loads of approved-not-merged UDD branches
[09:47] <dholbach> Laney, yes, probably
[10:14] <dholbach> seb128, Laney, http://paste.ubuntu.com/9783833/ changed our list from 57 to 69 requests, with no xdg-utils MPs among them.......
[10:14] <dholbach> hum
[10:15] <apw> darkxst, still broken at the moment, working on it
[10:16] <seb128> dholbach, seems like a managable difference, do you know why xdg is missing still?
[10:16] <dholbach> no, no idea
[10:17] <dholbach> Laney, seb128, could it be that "review requested from <ubuntu-branches or something>" is missing on both xdg-utils MPs?
[10:18] <dholbach> like on https://code.launchpad.net/~xnox/upstart/systemd-local-bridge/+merge/246772 for example
[10:18] <seb128> could be
[10:18] <seb128> shouldn't that be added by default though?
[10:18] <dholbach> yeah
[10:18] <Laney> I think that a person takes over a team's review when they perform it
[10:18] <seb128> or is that because ochosi added me specifically for review?
[10:19] <Laney> maybe
[10:19] <Laney> ?
[10:19] <seb128> oh?
[10:19] <dholbach> ochosi, do you remember if you changed something in the "reviewer" settings or requested a particular review from somebody?
[10:19] <dholbach> Laney, I always thought that it was added
[10:19] <ochosi> dholbach: yes, because i had worked with seb128 on xdg-utils merges before, i specifically requested his review
[10:20] <dholbach> let me see what happens if I can add jodh to xnox' MP
[10:20] <ochosi> and it's possible that brainwash (aka thaddäus tintentfisch) directly requested my review
[10:20] <seb128> ochosi, but did you remove the team from reviewers?
[10:20] <ochosi> seb128: no, not actively/willingly
[10:20] <seb128> k
[10:20] <Laney> for example https://code.launchpad.net/~laney/ubuntu-system-settings/as-activation/+merge/225953
[10:20] <dholbach> Laney, seb128: looks like it's added and not replacing ubuntu-branches: https://code.launchpad.net/~xnox/upstart/systemd-local-bridge/+merge/246772
[10:20] <Laney> there's no team review
[10:21] <Laney> but I wouldn't have requested seb128 explicitly there
[10:21] <dholbach> Laney, maybe because it's not source package branch?
[10:21] <dholbach> s/not/no
[10:21] <Laney> doubt it
[10:21] <Laney> one sec
[10:21] <seb128> dholbach, I think what Laney is saying is that if a member of the team does a review and set approve, launchpad considers the review done and replace the team by the reviewer
[10:22] <seb128> Laney, something like that?
[10:22] <dholbach> ahh ok
[10:22] <Laney> ya
[10:22] <dholbach> which.... for https://code.launchpad.net/~thad-fisch/ubuntu/vivid/xdg-utils/lp1363540/+merge/246820 wouldn't quite explain it
[10:22] <dholbach> it's even still in "Needs review"
[10:22] <Laney> if you're looking for all MPs which ubuntu-branches has a requested review on then that won't be returned
[10:22] <Laney> is that what the queue is doing?
[10:23] <dholbach> Laney, yes - I think that's the only way how we can get a list of MPs
[10:23] <seb128> dholbach, Laney, one other possibility is that when you file a mp and directly put the reviewer on the filing page, then it leads to not have the default reviewers added
[10:23] <seb128> rather than filing and adding a reviewer then
[10:24] <dholbach> might be, yes
[10:24] <Laney> https://code.launchpad.net/~laney/ubuntu/vivid/0ad/test/+merge/246873
[10:24] <Laney> review that please
[10:25]  * seb128 tries
[10:25] <seb128> ja
[10:25] <seb128> that replaced the team
[10:25] <seb128> Laney, also, https://code.launchpad.net/~seb128/gallery-app/some-translations-tweaks/+merge/246874
[10:26] <seb128> that's buggy but I picked one of my vcs and mp it selecting you as reviewer in the optional entry on the mp filing page
[10:26] <seb128> the team is not there, only you
[10:26] <Laney> that replaces the default
[10:26] <Laney> it's probably by design there
[10:26] <Guest67718> That's correct.
[10:27] <seb128> right
[10:27] <xnox> dholbach: ubuntu-branches is default, at proposal time one can choose someone else to review (in that case ubuntu-branches is removed)
[10:27] <wgrant> It's rather odd, but that's the way it is.
[10:27] <seb128> which I guess is what happened on those xdg-utils reviews
[10:27] <xnox> dholbach: i typically keep ubuntu-branches and add extra people, that I would like to notify
[10:27] <ochosi> so, i should have not requested a reviewer when filing the MR but instead added one on top of the default?
[10:27] <seb128> ochosi, correct
[10:27] <xnox> dholbach: however, i have the benefit of knowing plenty of relevant people to notify.
[10:27] <ochosi> ok, good to know
[10:27] <Guest24387> The field on the MP form replaces the default reviewer, and once a team member reviews it the team request is replaced with a review from that person.
[10:27] <dholbach> hum, so we don't have a good way of finding MPs which have had ubuntu-branches removed :)
[10:27] <seb128> ochosi, yeah, some of us learnt something today ;-)
[10:28] <xnox> dholbach: apart from iterating across all open MPs..... not really
[10:28] <ochosi> seb128: hehe, indeed. i'll see that knowledge gets passed on in the xubuntu team
[10:28] <Laney> Is there an API way to find all ubuntu-branches MPs which are 'Needs Review'?
[10:28] <seb128> ochosi, thanks
[10:28] <dholbach> Laney, yes, that's what we're using
[10:28] <wgrant_> Laney: ubuntu-branches in which sense?
[10:28] <Laney> As target
[10:28] <wgrant_> As branch owner, or as reviewer?
[10:28] <Laney> that's what lp:ubuntu/... is an alias too, right?
[10:28] <Laney> to
[10:29] <xnox> pitti: i'm failing to create or start ubuntu-emulator on vivid, with a vivid image.
[10:29] <xnox> am I missing something obvious?
[10:29] <xnox> https://bugs.launchpad.net/ubuntu/+source/goget-ubuntu-touch/+bug/1412261
[10:29] <xnox> "Can't create tempfile to create emulator instance"
[10:29] <xnox> $ sudo ubuntu-emulator create --arch armhf --channel ubuntu-touch/devel-proposed --revision 68 vivid2
[10:30] <pitti> xnox: oh, it's been ages since I tried armhf; it's utterly slow, I only use i386 (the defualt)
[10:31] <xnox> pitti: i386 also fails
[10:31]  * xnox ponders if i need to create a magic directory somewhere for it to work.
[10:36] <pitti> xnox: creating one again
[10:36] <pitti> it was working just fine until Friday, for months anyway; but maybe something broke over the weekend
[10:37] <pitti> xnox: do you have a full /tmp/ or anything like thatZ?
[10:50] <LocutusOfBorg1> dholbach, pitti do you have time for a virtualbox/trusty review?
[10:50] <LocutusOfBorg1> https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1411507
[10:50] <LocutusOfBorg1> I fixed the bug ;)
[10:51] <dholbach> I'll check it out in a bit
[10:51] <LocutusOfBorg1> oh and BTW I added some packages here https://bugs.launchpad.net/ubuntu/+source/poedit/+bug/1408285
[10:52] <LocutusOfBorg1> (kbuild is still being worked in debian by me)
[10:52] <dholbach> hum... ok
[10:52] <dholbach> ubuntu-sponsors is not subscribed, let me re-add it
[11:06] <LocutusOfBorg1> thanks! :)
[11:54] <LocutusOfBorg1> dholbach, did you test virtualbox? :)
[11:54] <dholbach> LocutusOfBorg1, it's taking a bit longer to set up everything with trusty
[11:54] <dholbach> are you in a hurry?
[11:56] <LocutusOfBorg1> nope, just wonderinf if you were taking a look or not, sorry but I'm currently working on other 10 packages, and I forgot really soon things :)
[11:56] <dholbach> sure, take your time
[11:56] <LocutusOfBorg1> so can I forget about that bug, right? (until I get some mails)
[11:57] <dholbach> yes
[11:58] <LocutusOfBorg1> wonderful thanks
[11:59] <LocutusOfBorg1> do you think 3.18 will be backported to trusty too? just to cherry-pick something more, to step ahead the next build failure :)
[12:05] <apw> LocutusOfBorg1, v3.18 likely will not be backported to trusty, there will be an lts-vivid with whatever vivid has at release
[12:06] <apw> (which is looking currently like it would be v3.19)
[12:06] <LocutusOfBorg1> so apw the answer was "yes", but the question was "wrong" :)
[12:07] <LocutusOfBorg1> I mean, somebody will have that kernel and the build failure with virtualbox then
[12:07] <apw> LocutusOfBorg1, heh, very likely yes in the future, cirtainly i do already :)
[12:08] <LocutusOfBorg1> do you have any ppa for it? this way I can proactively fix also that build failure :)
[12:09] <dholbach> LocutusOfBorg1, so I created a trusty chroot, updated to the latest, installed virtualbox and linux-generic-lts-utopic (which has 3.16), but I don't see the issue happening......
[12:10] <dholbach> did you try this too?
[12:11] <LocutusOfBorg1> dholbach, nope I have a real machine and a virtualbox machine
[12:11] <LocutusOfBorg1> I tried and it failed
[12:11] <LocutusOfBorg1> chroot might not be enough ( pitti has something to say about the topic :p )
[12:11] <dholbach> ok... how do you reproduce the issue?
[12:11] <LocutusOfBorg1> try uname -a in the chroot, you will likely have the "host" kernel
[12:12] <pitti> of course, chroots don't have their own kernel; but you can install various linux-headers-* packages to build against
[12:12] <LocutusOfBorg1> I install trusty in a VM, update the kernel, reboot with the new one and install
[12:12] <LocutusOfBorg1> I found that having a VM, was easiest for testing and reproducing the issue ;)
[12:13] <LocutusOfBorg1> pitti, I tried also this solution, but for some reasons I didn't investigate virtualbox-dkms was picking the wrong kernel
[12:13] <LocutusOfBorg1> maybe because it does an "uname -a" to know the version to build modules against?
[12:13] <dholbach> ah ok
[12:13] <pitti> yeah, probably
[12:14] <LocutusOfBorg1> I think you can force the version somewhere, but again, I didn't investigate since setting up a VM takes less time :)
[12:14] <pitti> it might only build against the current kernel, not all instlaled linux-header-* ones
[12:14] <LocutusOfBorg1> and I think makes me more confident about the issue
[12:18] <apw> LocutusOfBorg1, dkms should build against the kernel version of the headers/image you are installing, not the runnnig kernel
[12:18] <apw> LocutusOfBorg1, that is passed into the dkms incantation, and dkms packages themsleves should not be using uname to work out the version to use
[12:20] <apw> LocutusOfBorg1, or is this on upgrade of the dkms package itself
[12:20] <LocutusOfBorg1> apw, yes, but "uname -a" was just a guess, I don't know what are they actually using, so your solution might be perfectly correct
[12:21] <apw> dholbach, you do need to install the dkms package before the headers to get the right version build
[12:21] <LocutusOfBorg1> nope apw I'm talking about virtualbox-guest-dkms
[12:21] <LocutusOfBorg1> not dkms itself
[12:21] <apw> in a chroot context
[12:21] <LocutusOfBorg1> wonderful apw :)
[12:21] <tseliot> apw, LocutusOfBorg1: if dkms packages call the right DKMS template (/usr/lib/dkms/common.postinst), they will pick up the correct kernel version
[12:22] <tseliot> even in a chroot
[12:22] <tseliot> (nvidia and fglrx do this in their postinst scripts)
[12:23] <apw> tseliot, so they would, that is a postinst and 3/4
[12:24] <tseliot> apw: I'm not sure I follow you
[12:24] <apw> (oh i was just agreeing and saying, "man that is a long postinst fragment"
[12:25] <tseliot> apw: hah, thanks, I worked on it myself :)
[12:25] <apw> tseliot, i noticed :)
[12:28] <apw> darkxst, ok ... i've just uploaded a casper change to move to proper overlay, which should avoid the overlayfs issue which is breaking live boot
[12:29] <apw> darkxst, i am still working the original issue in the kernel
[12:38] <sitter> cyphermox: upstream plasma-networkmanager dev asks when we are going to land networkmanager 1.0. will it be 15.04 or 15.10?
[12:54] <mlankhorst> do I need a MIR for clang? because the llvm source package is already in main..
[12:58] <seb128> mlankhorst, if it's a binary from a source already in main, no
[12:59] <mlankhorst> ok
[13:04] <rsalveti> pitti: I'm getting a race when starting whoopsie on latest ubuntu-touch image (vivid)
[13:04] <rsalveti> pitti: seems it's not started by the upstart job
[13:04] <rsalveti> removed the start line from the upstart job and it still got started, which would explain the race
[13:05] <pitti> rsalveti: so there's something else that runs "start whoopsie"?
[13:05] <pitti> or service whoopsie start or whatever
[13:05] <rsalveti> pitti: from ps it's not running with -f, just get /usr/bin/whoopsie
[13:05] <rsalveti> wonder if https://launchpadlibrarian.net/195012178/whoopsie_0.2.43_0.2.44.diff.gz made any difference
[13:05] <rsalveti> right
[13:05] <pitti> rsalveti: oh, it could actually do
[13:06] <ogra_> pitti, seb128 suggested there would perhaps be some dbus activation
[13:06] <pitti> rsalveti: I uploaded that as I started the emulator and saw the error message from init-d-script
[13:06] <seb128> ogra_, in fact not likely, just checked
[13:06] <ogra_> ah, k
[13:06] <pitti> rsalveti: no, whoopsie doesn't listen on dbus
[13:06] <ogra_> just wanted to carry the info along
[13:06] <pitti> rsalveti: so something indeed starts the init.d script
[13:06] <rsalveti> pitti: hm, what was the emulator error?
[13:06] <seb128> whoopsie-preference is the one which has a dbus service
[13:06] <rsalveti> pitti: yeah
[13:07] <pitti> rsalveti: I just saw init-d-script complaining about a malformed $DAEMON
[13:07] <rsalveti> oh, ok
[13:07] <pitti> but not what tried to start it
[13:07] <rsalveti> so you fixed the script and that caused the race
[13:07] <pitti> rsalveti: so, we've had the broken init.d script for ages, and indeed it's not supposed to be started in the first place
[13:07] <rsalveti> right
[13:08] <pitti> the phone does have the LSB hook to divert calling /etc/init.d/whoopsie to upstart, which makes this thing even weirder
[13:08] <pitti> /lib/lsb/init-functions.d/01-upstart-lsb
[13:09] <pitti> so, we can certainly "break" the init.d script again, or even drop it, but this might happen to other init.d scripts too
[13:09] <rsalveti> yeah
[13:09] <pitti> rsalveti: initially I thought this was just a side effect of running with systemd (which I did on Friday), I wasn't aware it also happens under upstart
[13:12] <rsalveti> maybe something is broken with that LSB hook
[13:12] <rsalveti> but guess that would cause some other bad side effects
[13:12] <pitti> yeah, it would mean that other init.d scripts woudl run too
[13:13] <pitti> I can't imagine something specifically calling the whoopsie init.d hook outside the boot process itself
[13:13] <pitti> i. e. /etc/rc2.d/*
[13:13] <pitti> s/hook/script/
[13:13] <xnox> and whoopsie-preferences does not start whoopsie?
[13:23] <shadeslayer> mvo: pitti could one of you approve https://code.launchpad.net/~rohangarg/synaptic/bug1375786/+merge/244005
[13:23] <shadeslayer> been over a month
[13:24] <rsalveti> pitti: added a debug line in /lib/lsb/init-functions.d/01-upstart-lsb and it didn't check for the whoopsie job (it did for quite a few others)
[13:25] <mvo> shadeslayer: ups, sorry, let me merge/upload
[13:26] <shadeslayer> mvo: thanks alot, can we also get a SRU fix for Utopic?
[13:26] <shadeslayer> would be supremely awesome
[13:27] <shadeslayer> mvo: tbh I'm not entirely sure if we need 2 desktop files
[13:27] <shadeslayer> http://paste.ubuntu.com/9785018/ < diff between the 2 desktop files
[13:27] <shadeslayer> not sure what X-KDE-SubstituteUID is
[13:28] <mvo> shadeslayer: I think that had the effect to start it with sudo, but I have little knowledge of kde, so if kde can use the normal file, that would rock
[13:28] <shadeslayer> mvo: we do have a pkexec helper
[13:29] <shadeslayer> mvo: just a sec, just let me use the normal file and see what happens
[13:30] <mvo> shadeslayer: ok
[13:31] <dholbach> LocutusOfBorg1, I'll change the version number to 4.3.10-dfsg-1ubuntu1, ok?
[13:31] <dholbach> apart from that it looks good to me
[13:32] <shadeslayer> mvo: yeah , I'd just nuke the kde desktop file, the regular one works in Plasma 5 on vivid
[13:35] <mvo> cool, I will push that to vivid
[13:36] <shadeslayer> mvo: thoughts about what to do for utopic ? just use the synaptic-pkexec patch?
[13:38] <shadeslayer> ( Also, just throwing it out there, you probably want to remove the NotShownIn line in the regular desktop file )
[13:38] <mvo> shadeslayer: if someone could test if dropping the synaptic-kde.desktop file (and removing the "not-show-in=kde" works for utopic as well I would prefer to also drop the file there
[13:38] <mvo> shadeslayer: http://bazaar.launchpad.net/~synaptic-developers/synaptic/trunk/revision/2167 :)
[13:39] <shadeslayer> mvo: I can do that
[13:40] <mvo> shadeslayer: great, please let me know and I can do the SRU
[13:40] <shadeslayer> awesome, give me 20 mins
[13:43] <Riddell> armhf builders all broken?
[13:44] <shadeslayer> Riddell: seems to be working fine https://launchpad.net/ubuntu/+source/kio-extras/4:5.1.95-0ubuntu3/+build/6731015
[13:45] <Riddell> ooh they just caught up, good good
[13:45] <cjwatson> Riddell: There was a power issue earlier that took them all out, but they've been back for most of an hour now.
[13:45] <shadeslayer> cjwatson: did someone trip over a power strip :P
[13:45] <cjwatson> shadeslayer: Not as far as I know :-P
[13:46] <rbasak> I think they're all in one chassis, aren't they?
[13:46] <rbasak> No need for a power strip :-)
[13:46] <cjwatson> There was some scheduled power maintenance but then some systems weren't quite as dual-power as one might hope.
[13:47] <cjwatson> And yes, the LP non-virt ARM builders are all in one chassis.
[13:48] <shadeslayer> curious, does anyone know how to pass a env var to the schroot setup scripts? I have a script that needs to read a env var that Jenkins sets
[13:51] <svenx> shadeslayer: schroot(1) explains it in its ENVIRONMENT section (bottom)
[13:51] <svenx> ref environment-filter
[13:51] <shadeslayer> svenx: isn't that explcitly to filter out env variables
[13:51] <shadeslayer> I want to whitelist something
[13:52] <svenx> hm, true
[13:52] <svenx> the text is ambiguous
[13:52] <shadeslayer> quite :)
[13:54] <svenx> related: https://bugs.debian.org/666274
[13:54] <svenx> "Arbitrary options may now be set in a chroot definition in schroot.conf.  These options are also set in the environment when running setup scripts, making this a simple means by which setup scripts may be customised without writing code."
[13:58] <xnox> cjwatson: i'm not going into the datacentre this time around.... i did leave a note that most things are single-power.
[14:01] <shadeslayer> svenx: aha figured it out
[14:01] <shadeslayer> thx
[14:01] <shadeslayer> this is awesome :3
[14:04] <ngaio> hi everyone! Is it safe to assume that Qt 5.4 is a certainty for inclusion in Vivid?
[14:08] <pitti> rsalveti: ok, that indicates that something was calling it as /etc/init.d/whoopsie instead of /etc/rc2.d/S??whoopsie
[14:12] <dholbach> @pilot out
[14:39] <shadeslayer> mvo:  seems to work in utopic as well
[14:39] <shadeslayer> plz go ahead and nuke it
[14:41] <cyphermox> sitter: I am landing 0.9.10 today; will get started on 1.0 right after that's done
[14:44] <sitter> cyphermox: awesome. do you think 1.0 is going to make it into 15.04?
[14:47] <sturmflut-work> If anybody has ideas about https://sturmflut.github.io/linux/ubuntu/2015/01/17/unprivileged-icmp-sockets-on-linux/ or https://sturmflut.github.io/linux/wireless/2015/01/19/designing-a-wifi-analyzer-app-for-ubuntu-touch/, please do let me hear them
[14:47] <sturmflut-work> Would be nice to know that I am completely wrong and there are other solutions
[14:48] <cyphermox> sitter: yes
[14:48] <sitter> cyphermox: groovy, thanks for the info :)
[15:06]  * xnox ponders to switch to CIRC irc client
[15:08] <didrocks> xnox: hey! so, on your email about systemd local bridge… I guess you will have to create virtual units for value then. (that's what I told you on the hangout on Friday, that I doubted * would work)
[15:09] <xnox> didrocks: correct, if there are virtual values in fact. cause in other places it seems like a forward-looking glob rather than a required one.
[15:10] <xnox> didrocks: but that means someone needs data/values for those, and then in the hw-override tarball or the android config do
[15:10] <didrocks> xnox: yeah, it doesn't reevaluate
[15:10] <xnox> postinst
[15:10] <xnox> systemctl enable<EMAIL_ADDRESS>[15:10] <xnox> systemctl enable<EMAIL_ADDRESS>[15:10] <xnox> systemctl enable<EMAIL_ADDRESS>[15:10] <xnox> as needed.
[15:10] <didrocks> yeah :/
[15:10] <xnox> .... adn then template the job as well....
[15:11] <didrocks> (btw, I would prefer android-property, as the property is accessible outside the container… but it's just a matter of taste ;))
[15:11] <didrocks> yeah, quite tricky…
[15:11] <xnox> i guess one only needs systemctl enable<EMAIL_ADDRESS>which should have wanted by =<EMAIL_ADDRESS>[15:12] <xnox> didrocks: "android-container" is a configurable string. In the upstart job it was "upstart-local-bridge --event android-container"
[15:12] <didrocks> ah ok, it's the parameter :)
[15:12] <xnox> didrocks: we can totally change the systemd unit to do "--event android-property"
[15:12] <didrocks> well, just a suggestion, but great it's easy to change
[15:12] <xnox> which in systemd world means "the name of the template target"
[15:12] <didrocks> yeah
[15:13] <xnox> didrocks: however ogra_ didn't get back to me with names of targets. And i don't have all the phones to check / test these.
[15:13] <xnox> didrocks: unless come CI thing has a dump of all the "getprops"
[15:13] <xnox> s/come/some/
[15:13] <didrocks> xnox: actually, we can go the other way around, units knows what property they expect
[15:14] <didrocks> and so, you scan the .service with WantedBy=
[15:14] <didrocks> and only expose/enable them dynamically?
[15:14] <didrocks> that would avoid creating tons of unwanted unit properties…
[15:15]  * didrocks tries to create a WantedBy= on unexisting target
[15:15] <xnox> didrocks: if the wanted by has the full name of the target, that one gets enabled, yes.
[15:15] <xnox> didrocks: that's how it currently works, it's just one cannot have a glob in it.
[15:15] <xnox> like what's currently used in upstart: maybe with, maybe without reason.
[15:16] <xnox> adbd.service should list all the wantedby's it wants to trigger on. If we need globbing, then I guess the upstart-local-bridge can
[15:16] <xnox> instead of activating<EMAIL_ADDRESS>[15:16] <xnox> activate:
[15:17] <xnox><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>[15:17] <xnox> but imho that's ugly.
[15:17] <didrocks> yeah, it is :/
[15:19] <xnox> i think it would be ok for, e.g. adbd.service if it needs<EMAIL_ADDRESS>to make itself<EMAIL_ADDRESS>"WantedBy =<EMAIL_ADDRESS>and do systemctl enable adbd@`seq 0 100`.service
[15:20] <xnox> templated instance .service <- 1 to 1 -> templated property instances
[15:20] <didrocks> xnox: I don't get why you don't rather do that:
[15:21] <xnox> ?
[15:21] <didrocks> adb.service -><EMAIL_ADDRESS>[15:21] <didrocks> then, the bridge look at the target in systemd memory
[15:21] <didrocks> sorry<EMAIL_ADDRESS>[15:21] <xnox> and do the globbing on the bridge?
[15:21] <didrocks> get that it needs to fetch and monitor "property"
[15:21] <didrocks> yeah
[15:22] <didrocks> and so, create that target/start/stop it as needed
[15:22] <didrocks> that way, you only create the targets that are needed on the system
[15:22] <xnox> i'm ok to implement that, however i would adb.service then list:
[15:22]  * xnox has no systemd-escape on this machine
[15:22] <didrocks> don't worry ;)
[15:22] <didrocks> I know about it
[15:23] <xnox><EMAIL_ADDRESS>[15:23] <xnox> where * is the systemd-escaped code.
[15:23] <didrocks> and you escape the *
[15:23] <didrocks> yeah
[15:23] <xnox> then the bridge can tell appart what should and shouldn't be globbed
[15:23] <didrocks> right
[15:23] <xnox> and it will start<EMAIL_ADDRESS>&<EMAIL_ADDRESS>[15:23] <didrocks> and create and start the target
[15:24] <xnox> .... stars escaped.
[15:24] <didrocks> which will then bring the unit
[15:24] <didrocks> (sure)
[15:24] <xnox> yeah, the whole thing.
[15:24] <didrocks> not sure if the API is good to list WantedBy targets
[15:24]  * didrocks looks at what status says
[15:24] <didrocks>    Loaded: not-found (Reason: No such file or directory)
[15:24] <didrocks>    Active: inactive (dead)
[15:25] <LocutusOfBorg1> thanks dholbach
[15:25] <LocutusOfBorg1> :)
[15:25] <didrocks> not sure, status doesn't know about it even if I enabled a unit which WantedBy= against it
[15:25] <dholbach> anytime
[15:25] <xnox> didrocks: correct.
[15:25] <xnox> didrocks: that's fine.
[15:25] <xnox> didrocks: as it's not loaded, start & stop the .target, then status will know about it.
[15:26] <didrocks> xnox: right, but how would you detect those patterns then?
[15:26] <xnox> didrocks: wantedby installs a file on disk, it's static and evaluated on the the instance start.
[15:26] <didrocks> xnox: you don't want to scan /etc/systemd/system/*target.d? :)
[15:26] <xnox> didrocks: i would have hoped systemd dbus api exposes wantedby's of the units themself.
[15:27] <xnox> didrocks<EMAIL_ADDRESS>[15:27] <didrocks> xnox: yeah, I hope as well. I can just tell you status (which is talking through the dbus api to systemd) doesn't know :/
[15:27] <xnox> didrocks: readonly as WantedBy = ['multi-user.target'];
[15:28] <xnox> didrocks: so with d-feet  / gdbus one can query iterate all units (e.g. adbd.service) and check theirs wantedby=a-c@
[15:28] <xnox> we do parsing of all jobs a lot in bridges.
[15:28] <didrocks> xnox: oh, we have the WantedBy fields over dbus for each units?
[15:28] <xnox> e.g. upstart-systemd-bridge & upstart-file-bridge iterates through all units and caches their start on / stop on.
[15:28] <didrocks> yeah, sounds good :)
[15:28] <xnox> to do things with file & socket events.
[15:28] <xnox> similar thing will be here.
[15:28] <didrocks> yeah
[15:29] <xnox> also will subscribe to NewUnit signal.
[15:29] <didrocks> and I guess on the android side, you have an event in the container when a property changes?
[15:29] <xnox> didrocks: there is no events  inside the android container.
[15:30] <didrocks> how do you track changes then?
[15:30] <didrocks> like I'm enabling developer mode
[15:30] <xnox> setprop -> changes shared bionic memory, we have a property-watcher daemon (bionic binary) running under android-init, that thing writes key=value pairs into the socket.
[15:31] <xnox> the socket is the one created by the upstart-local-bridge, and bind-mounted into the lxc container by lxc-android-config
[15:31] <xnox> and that's how propery changes arrive at upstart-local-bridge.
[15:31] <didrocks> ahah, tricky ;)
[15:31] <xnox> didrocks: upstart-local-bridge only listens to the container.
[15:31] <xnox> didrocks: as it's entirely android thing.
[15:32] <xnox> didrocks: ideally, we'd make systemd bionic aware and memory map android properities and expose them as native conditions.....
[15:32] <xnox> but my left half of the brain says that's crazy
[15:32] <didrocks> xnox: I guess for the transition period, reusing the local bridge is what makes more sense
[15:32] <didrocks> xnox: so, I guess we are mostly set on the solution in the least intrusive way? do you need any help on this?
[15:33] <didrocks> no hurry anyway, as Touch on systemd isn't for this cycle anyway (activation of it, we can have it nicely running in advance though :p)
[15:33] <xnox> didrocks: non-globbing bridge is in silo 0001, however i need it tested on the phone/emulator "does not explode under upstart, may do nothing under systemd"
[15:33] <xnox> didrocks: before i land it.
[15:34] <xnox> and emulator is not giving me any joy at the moment
[15:34] <didrocks> xnox: yeah, I saw that, works nicely (amd64) here, freshly created on Friday
[15:35] <xnox> didrocks: do you mind dist-upgrade with silo 1, and boot with upstart / boot with android? and verify that it generally works?
[15:36] <xnox> and e.g. you can see event with upstart-monitor when you do setprop under upstart
[15:36] <xnox> and target under systemd?
[15:36] <didrocks> xnox: can do in ~20 minutes, finishing up some plymouth stuff first
[15:36] <didrocks> will get back to you then :)
[16:18] <sturmflut-work> I'm on 15.04 and at random times a day a popup will appear, requesting me to enter my password to change my user data. The "Details" section states "Action: org.freedesktop.accounts.change-own-user-data" and "Vendor:". I have now idea where this comes from, and if I just cancel it nothing happens. Any ideas?
[16:19] <sturmflut-work> Couldn't find a matching bug report, but it seems to be the same issue as mentioned in http://askubuntu.com/questions/562355/seemingly-random-authentication-is-required-to-change-your-own-user-data
[16:22] <didrocks> xnox: after a "sudo setprop persist.sys.usb.config mtp", I see no new target with systemctl
[16:29] <xnox> didrocks: can you do that from inside android container?
[16:30] <xnox> didrocks: or for example boot emulator with upstart and "--debug" on the kernel command line and check that android events are generated with upstart
[16:30] <xnox> didrocks: are there any targets generated at all? systemctl status<EMAIL_ADDRESS>?
[16:30] <xnox> didrocks: possibly property watcher only works from container....
[16:31] <xnox> didrocks: i know that you can do $ socat - UNIX-CONNECT:/dev/socket/* persist.sys.usb.config=mtp
[16:31] <xnox> didrocks: maybe things explicitely echo stuff into the socket inside the android container.
[16:34] <mvo> shadeslayer: thanks,  I am very busy right now, would you mind reminding me again tomorrow if I haven't acted on this by then? sorry, work is very busy right now
[16:34] <shadeslayer> mvo: sure, I understand, it'd just be nice to have it fixed soonish, one of our downstreams has a release soon and would be nice to get it in
[16:36] <didrocks> xnox: actually, the bridge isn't started… what is supposed to start it? I don't see any upstart job doing that
[16:36] <pitti> apw: oh, "overlay" != "overlayfs" :) thanks for the casper fix/workaround!
[16:36] <pitti> apw: that avoids the weird char dev issue on renaming?
[16:36] <mvo> shadeslayer: yeah, if someone could prepare the sru diff (should be really) easy that would make it much simpler for me, a review/dput is quick for me
[16:37] <shadeslayer> mvo: sure, I can do that
[16:37] <apw> pitti, yes it should avoid it for new overlays such as those which the installer makes
[16:38] <apw> pitti, i am working on, actually testing the heck out of, a fix for the V1 support separatly from that
[16:38] <pitti> apw, the rescuer of alpha-2!
[16:39] <apw> pitti, the breaker of perhaps :)
[16:39] <apw> pitti, dunno if someone can respin something to test it sooner than tonight
[16:39] <mvo> shadeslayer: \o/
[16:39] <pitti> apw: heh -- I hope that overlay isn't an entirely new thing, but just the evolution of overlayfs?
[16:39] <xnox> didrocks: there are systemd unit and upstart job in lxc-android-config package
[16:39] <pitti> apw: the release team should be able to
[16:40] <didrocks> xnox: hum, I didn't see the upstart job, looking
[16:40] <xnox> didrocks: there is no stock upstart-job, as the user configures their own job with the required socket path & event name.
[16:40] <didrocks> xnox: I did the systemd unit in lxc-android-config, and I only started the container, (to mirror the upstart one)
[16:41] <xnox>  /etc/init/upstart-local-bridge.conf
[16:41] <xnox> and i don't see unit one sec.
[16:41] <apw> pitti, ack, have asked on #u-release ... it seems prudent to get ahead
[16:41] <pitti> apw: yes, absolutely
[16:42] <pitti> apw: it could in theory be hacked into break=casper-top, but that quickly gets tiresome
[16:42] <xnox> didrocks: and i did not upload lxc-android-config 0.215 well that's a fail.
[16:42] <didrocks> xnox: :)
[16:42] <xnox> didrocks: no idea where that upload is at now though.
[16:42] <xnox> didrocks: cause e.g. one needs upstart-bin to have local-bridge binary
[16:43] <pitti> stgraber: you are TIL for ifupdown; do you plan to merge it?
[16:43] <pitti> stgraber: if not, I'll upload it soon to provide the static-network-up counterpart for systemd
[16:43] <didrocks> xnox: works with the daemon started manually
[16:44] <pitti> stgraber: (i. e. I'll add those as a network-online.target dependency)
[16:44] <xnox> didrocks: systemd or upstart or both?
[16:44] <stgraber> pitti: merging it is on my todo but not extremely high on it at the moment
[16:44] <didrocks> xnox: systemd only for now
[16:44] <xnox> didrocks: that's cool.
[16:44] <didrocks> xnox: how do I try the upstart ones? I'm not as upstart-savy than systemd :)
[16:44] <didrocks> as you create an event
[16:45] <xnox> didrocks: sudo upstart-monitor; trigger the same way you triggered for systemd -> should see things from upstart-monitor stdou
[16:45] <xnox> didrocks: sudo upstart-monitor; trigger the same way you triggered for systemd -> should see things from upstart-monitor stdout
[16:45] <didrocks> ok :) uno memento!
[16:46] <xnox> however i think it's fine to let upstart in, and then i'll upload fixed up lxc-android-config
[16:46] <xnox> i don't have it locally anymore, so i'll have recreate
[16:47] <didrocks> xnox: hum, upstart-monitor is a gtk app?
[16:48] <didrocks> ah, it's telling it's fallbacking to cli
[16:48] <didrocks> but traceback :p
[16:48] <didrocks>     class UpstartEventsGui(Gtk.Window):
[16:48] <didrocks> NameError: name 'Gtk' is not defined
[16:48]  * didrocks edits to avoid the traceback
[16:48] <xnox> didrocks: sudo upstart-monitor -n
[16:48] <xnox> for the non-gui version
[16:49] <xnox> sorry forgot.
[16:49] <didrocks> xnox: yeah, it's puzzling that it's telling that it's fallbacking though :)
[16:49] <didrocks> even with -n, traceback
[16:49] <didrocks> so really an issue with the app/
[16:49]  * didrocks fires vi
[16:50] <xnox> didrocks: yeah..... =/
[16:51] <shadeslayer> mvo: https://launchpadlibrarian.net/195323505/patch
[16:54] <didrocks> xnox: hum, interesting, can't import Glib, despite having gir1.2-glib-2.0 installed on the phone
[16:55] <xnox> didrocks: apt-get install python -gi
[16:55] <xnox> didrocks: apt-get install python-gi
[16:55] <xnox> no?
[16:56] <didrocks> xnox: not that, you are trying to import Gtk first
[16:56] <didrocks> then, it bails out
[16:56] <didrocks> and so don't import the rest :p
[16:56]  * didrocks will do some patches to upstart-monitor :)
[16:56] <xnox> didrocks: option easier = boot emulator with "--debug" on the kernel command line
[16:56] <didrocks> xnox: too late, running ;)
[16:56] <xnox> didrocks: that your emulator console will be full of upstart events.
[16:56] <xnox> didrocks: than your emulator console will be full of upstart events.
[16:59] <didrocks> xnox: 2015-01-19 16:59:14.398513android-container SOCKET_TYPE='unix' SOCKET_VARIANT='named' CLIENT_UID='0' CLIENT_GID='0' CLIENT_PID='17531' SOCKET_PATH='/dev/socket/upstart-text-bridge' persist.sys.usb.config='mtp'
[16:59] <didrocks> \o/
[16:59] <xnox> cool.
[16:59] <didrocks> (needed to use socat, for some reason, couldn't lxc-attach to the container)
[17:00] <didrocks> xnox: so, seems to be good from my limited testing
[17:00] <xnox> didrocks: lxc-attach does not quite work on the android container - it's rootfs is unpacked into private tmpfs, which one cannot get into.
[17:00] <xnox> didrocks: so now i need to figure out which buttons to push for release.
[17:00] <didrocks> xnox: yeah, when I saw the "couldn't access to <mount point>", I reckoned that was the case :)
[17:00] <didrocks> xnox: ahah, I guess the publish one ;)
[17:00] <didrocks> or ask on #ubuntu-ci-eng
[17:01] <didrocks> xnox: so, filtering and globbing for the longer term solution, but seems like a nice step forward!
[17:01] <xnox> didrocks: well if https://ci-train.ubuntu.com/job/ubuntu-landing-001-2-publish/75/ fails then i'll ask stuff
[17:02] <xnox> Finished: SUCCESS
[17:02] <didrocks> sweet
[17:02] <xnox> looking good http://people.canonical.com/~platform/citrain_dashboard//#?distro=ubuntu&q=landing-001
[17:04]  * didrocks waves good evening
[17:10] <xnox> slangasek: looks like you are admin of ~ci-train-ppa-service can I get added to that team, such that I can dput packages into silos that are assigned to me?
[17:25] <LocutusOfBorg1> mdeslaur, hi, do you plan to merge openssl?
[17:25] <LocutusOfBorg1> I think we can almost drop all, since debian merged some ubuntu stuff
[17:38] <mdeslaur> LocutusOfBorg1: no, I'm waiting for when W opens
[17:39] <mdeslaur> LocutusOfBorg1: there are regressions and big changes in the current debian versions that I don't want for V
[17:39] <LocutusOfBorg1> ack, thanks for the reply! so I won't touch anything
[17:39] <LocutusOfBorg1> wonderful :)
[17:59] <apw> pitti, ok, a respin looks good, booted and installed ok here, so i think we are good should there be a milestone
[18:41] <Laney> cjwatson / someone else: could you moderate my mail to u-d-a please? The one with the correct subject line spelling, not the other one. :)
[18:41] <Laney> Oh right, I can cancel it can't I
[19:09] <rsalveti> xnox: hey, mind updating lp:ubuntu/upstart with the content from the latest version that got uploaded?
[19:09] <rsalveti> seem to be https://code.launchpad.net/~xnox/upstart/systemd-local-bridge/+merge/246772, but there is a conflict in there
[19:34] <asac> cjwatson: do you know if its normal that sshd doesnt start if one of the host keys referenced in /etc/ssh/sshd+_config is not avail?
[19:34] <asac> wonder because seems we gen these ed2... keys in openssh serer
[19:34] <asac> but seems that cloud-init doesnt generate them :/
[19:34] <asac> e.g. in code they only generate three
[19:35] <asac> so wonder how noone coudl have noticed and suspect there is a flag i am missing that will make sshd start ignoring that missing key
[19:35] <asac> seems you landed that key in trusty a year ago :)
[19:35] <asac> anyone else? :)
[19:36] <asac> kirkland: you around?
[20:46] <cjwatson> asac: not at a proper computer right now, but from what I can make out from browsing sshd.c on my phone, that should result in an error being logged but the server otherwise continuing to start up fine, as long as you have *some* protocol-2-suitable host key available.  this is not behaviour governed by any flag as far as I can see.  I would need to see logs to tell you any more.
[20:47] <cjwatson> Laney: done


[00:00] <micahg> Mathuin: anyone can contribute a patch to fix bugs in Ubuntu
[00:01] <Mathuin> Well, sure, anyone could contribute a patch to FreeBSD.  The fact that it took eighteen months for my two-line patch to be committed is one of the primary reasons I switched to Ubuntu.
[00:01] <Mathuin> I got tired of having to patch my kernel every time I ran "cd /usr/src && sudo make update".
[00:05] <Mathuin> https://code.launchpad.net/~doctormo/screenlets/options-rework/+merge/3935 -- oh dear.
[00:15] <greg-g> Mathuin: that seems like that ended well, no? (well, a year ago)
[00:16] <Mathuin> greg-g: crash and burn, with a bit of dead-cat bounce as the "new project" is pretty much dead as well.
[00:16] <Mathuin> To the point where I became the #2 recent contributor when I submitted a bug report asking if the project was alive. :-)
[00:20] <greg-g> well, yeah, I mean, it may be dead, but at least it didn't turn into a huge flame war
[00:20] <Mathuin> greg-g:  I learned from another bug in the UA database that the owner's looking to give it up.  I just sent in an offer to take it over.
[02:29] <bcurtiswx> Mathuin: join #empathy on irc.gimp.net or #telepathy here on freenode
[08:10] <hsm> If I see a bug in Ubuntu, what's the best channel to record it?
[08:14] <lifeless> $ ubuntu-bug packagename
[08:16] <hsm> lifeless: allright, can you help me with this? I see a wrongly displayed taskbar in ubuntu 10.04. What should I do to report this?
[08:22] <hsm> lifeless: ?
[08:35] <sense> hsm: Have you searched at Launchpad for the problem, to see if it isn't already reported?
[08:35] <kermiac> hsm: when you say "taskbar", are you referring to the top gnome panel? This is just a guess, but it might be bug 439448
[08:35] <ubot2> Launchpad bug 439448 in gnome-panel (Ubuntu Maverick) (and 5 other projects) "visual corruption affecting several panel applets (affects: 316) (dups: 80) (heat: 1751)" [Medium,Triaged] https://launchpad.net/bugs/439448
[08:36] <hsm> sense: yeah.. well i searched on taskbar and background
[08:36] <sense> hsm: kermiac's bug might be yours
[08:38] <hsm> kermiac: sorry, is missed your remark, i'm referring to the bottom bar (containing activie applications), but as I just found out it is for both bars..
[08:38] <hsm> kermiac: I will have a look into the bug you mentioned
[08:39] <hsm> kermiac: & sense: it's not the bug I mean.. What I am experiencing is that the background gradient of the taskbars keeps repeating itself when I scale the height of the bars.
[08:40] <sense> hsm: That is a theme-related issue, I suppose.
[08:40] <sense> hsm: It is how panel-backgrounds work.
[08:41] <sense> hsm: Although you could consider reporting a bug because different behaviour may be desired.
[08:41] <sense> Maybe there is already one.
[08:41] <kermiac> hsm: it might be easier if you could upload a screenshot of the issue, as sense said - it may be related to your theme. Does it happen when using the default theme?
[08:42] <hsm> sense: okay.. maybe these can be improved by scaling the background..
[08:42] <hsm> kermiac: where shall I upload this? In the bugreport?
[08:43] <kermiac> hsm | !screenshots
[08:43] <kermiac> !screenshots
[08:43] <ubot2> Screenshots can be made with the [PrtScr] button. Want to show us a screenshot of your problem? Upload an image to http://tinyurl.com/imagebin and post a link to it.
[08:44] <sense> hsm: But if you're trying to add screenshots to a bug report, please attach them there indeed. The pastebin is useful if you want to ask something here.
[08:49] <hsm> kermiac: http://imagebin.org/108056
[08:50] <hsm> sense: & kermiac: where shall I report this bug? launchpad bugs redirects me to another page..
[08:51] <sense> hsm: Have you read that page?
[08:51] <sense> hsm: I think that this bug has been reported before.
[08:53] <hsm> sense: I guess ..
[08:54] <sense> Let me search for it.
[08:56] <kermiac> sense: it *might* be bug 532309  see the screenshot in comment #34
[08:56] <ubot2> Launchpad bug 532309 in light-themes (Ubuntu) "Light-themes: panel-background isn't scaling (affects: 45) (dups: 8) (heat: 282)" [Low,Confirmed] https://launchpad.net/bugs/532309
[08:56] <sense> ah, there it is
[08:57] <sense> hsm: Your bug is probably bug #532309.
[09:00] <hsm> thanks sense! thats it! Will read it.. thanks so much
[09:01] <sense> hsm: You're welcome, and thank kermiac, because he did most of the work! :)
[09:06] <hsm> kermiac: THANKS kermiac! My problem is solved!
[09:06] <kermiac> hsm: no probs mate
[09:34] <sense> new tag: 'nautilus-desktop-icons'
[09:34] <vish> sense: :s
[09:34] <sense> For everything related to the icons that Nautilus puts on your desktop.
[09:35] <sense> vish: Why the :S?
[09:35] <vish> sense: how many bugs are there related to those icons?
[09:35] <vish> latest fad seems to be adding more tags :D
[09:35] <sense> It is really helpful to keep track of the different issues related to the desktop!
[09:36] <sense> Sebastien is seeing quite some of them, at least, and I've seen a few as well.
[09:37] <sense> The desktop probably needs a usability overhaul, but meanwhile we can categorise bugs to make it easier for the interested folks to find the issues.
[09:37] <vish> there are ~10 bugs , iirc
[09:37] <JoshuaL> People using icons on their desktop is a bug ;-)
[09:38] <vish> sense: well , if you are tagging them for personal interest seems good , but dont see the point in making it official
[09:44] <vish> sense: mainly more because , there have been already tagged upstream and aday is looking into them , and we aernt going to be doing much usability work separate from upstream :)
[09:44] <sense> ok
[09:44] <sense> Didn't know about that
[09:44] <sense> .
[12:12] <BrunoAlves> Hey! I couldn't find any mention on bugtracker.... but it's about plymouth... plymouth uses a file called boot-duration in /var/lib/plymouth to determine the duration of boot, and to properly draw the progress bar... but here this file is always an empty file... can anyone confirm this?
[12:17] <BrunoAlves> anyone?
[12:26] <BrunoAlves> I'm not seeing any messages... am I transmitting messages here?
[12:27] <devildante> We are here, just that we are all busy :(
[12:28] <BrunoAlves> thanks... and sorry
[12:29] <BrunoAlves> well... if anyone could please confirm if theirs /var/lib/plymouth/boot-duration is an empty file.....
[12:36] <mythos> BrunoAlves, -rw-r--r-- 1 root root 0 2010-07-27 20:37 /var/lib/plymouth/boot-duration
[12:38] <vish> bcurtiswx: :D
[12:39] <vish> bcurtiswx: we were on the same bug ;)
[12:39] <BrunoAlves> thanks!
[12:39] <bcurtiswx> vish: ah ha, and i'm talking to you in -desktop
[12:45] <gnomefreak> BrunoAlves: i dont have that file at all
[12:46] <gnomefreak> gnomefreak@Development:/var/lib/plymouth$ ls
[12:46] <gnomefreak> gnomefreak@Development:/var/lib/plymouth
[12:47] <yofel_> 2621812 0 -rw-r--r-- 1 root root 0 2010-07-17 21:30 /var/lib/plymouth/boot-duration
[12:47] <devildante> gnomefreak: weird, I have this (empty) file too
[12:47] <yofel> 0 byte file
[12:47] <devildante> -rw-r--r-- 1 root root 0 2010-08-04 10:44 /var/lib/plymouth/boot-duration
[12:47] <gnomefreak> are you 2 on maverick or lucid?
[12:47] <devildante> maverick
[12:47] <yofel> gnomefreak: maverick upgraded from lucid
[12:48] <devildante> me too upgraded from lucid :)
[12:48] <gnomefreak> maybe its because i cant get plymouth to show up at all
[12:48] <yofel> well, the file isn't part of any package, so it was created by plymouth at some point
[13:12] <stanley_robertso> hi vish
[13:18] <vish> stanley_robertso: hey
[13:19] <gnomefreak> i have to reboot but can someone try to confirm bug 598514 while im gone?
[13:19] <ubot2> Launchpad bug 598514 in gnome-screensaver (Ubuntu) (and 1 other project) "F-spot no longer works (affects: 1) (heat: 6)" [Undecided,Fix released] https://launchpad.net/bugs/598514
[13:20] <gnomefreak> ok be back in a few
[13:21] <devildante> @everyone: shouldn't this be "Invalid" for gnome-screensaver?
[13:22] <yofel> bdmurray: filed the merge request https://code.edge.launchpad.net/~yofel/canonical-qa-tracking/gm-response-pa/+merge/31694
[13:25] <stanley_robertso> vish,   wassup.. how is it going ?
[13:26] <yofel> devildante: probably, but I wouldn't change it as closed is closed
[13:26] <devildante> yofel: okay, thx
[13:36] <gnomefreak> vish: was it you that gets/got the passprase dialog when using auto login?
[13:37] <vish> gnomefreak: yup
[13:37] <gnomefreak> s/passprase/passphase
[13:37] <gnomefreak> vish: can you please confirm bug 611001
[13:37] <ubot2> Launchpad bug 611001 in gdm (Ubuntu) "Password prompt shows when automatically login (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/611001
[13:37]  * gnomefreak going through my bugs
[13:38] <seb128> gnomefreak, it's not a bug
[13:39] <vish> seb128: this is even when not using any stored password.
[13:39] <gnomefreak> seb128: ? its a feature?
[13:39] <vish> seb128: it just asks for keyring unlock always
[13:39] <seb128> something might be using a password
[13:39] <seb128> calendar, wireless
[13:39] <seb128> im
[13:40] <devildante> there is some discussion on ayatana mailing list about this
[13:40] <vish> seb128: for me its on a VM , not using anything in it  , its just for testing i have that there
[13:40] <vish> no im/wireless
[13:41] <seb128> vish, I will have to test an a3 install
[13:41] <seb128> but g-k didn't change since lucid
[13:41] <seb128> so I doubt it
[13:41] <gnomefreak> me neither. nothing should need to use that AFAIK
[13:41] <seb128> could be ubuntuone or something trying to use a password
[13:41] <seb128> gnomefreak, "that" being the keyring?
[13:41] <vish> yeah , U1 might be that!
[13:41] <seb128> we have tons of softwares using the keyring
[13:42] <seb128> it's really not a gdm bug in any case
[13:43] <gnomefreak> i disabled ubuntu1 from loading, but i still have ssh keyring loading at startup
[13:43] <gnomefreak> maybe that is why? seb128 yes that == keyring
[13:44] <seb128> dunno
[13:44] <seb128> in any case it's not a gdm bug
[13:44] <seb128> gdm has nothing to do with password after login
[13:44] <seb128> you probably just have a software running trying to use the keyring
[13:45] <gnomefreak> well ill disable ssh keyring on load and when i reboot i will find out
[13:47] <gnomefreak> seb128: can you please update the bug
[13:49] <gnomefreak> i guess it could be the gsettings data conversion
[13:49] <seb128> gnomefreak, I doubt it
[13:50] <seb128> why would that need a password?
[13:50] <gnomefreak> ok hmm
[13:50] <gnomefreak> seb128: not sure
[13:51] <gnomefreak> than the only other thing that is in startup menu is ssh . PA wouldnt need it and Nm gnome sound
[13:53] <gnomefreak> well i will reboot and see what happens with ssh disabled
[14:05] <gnomefreak> chrisccoulson: and seb128  thanks for updating bug. it seems it is ssh that caused it
[14:06] <seb128> weird
[14:06] <seb128> the ssh agent should not be used until you ssh somewhere
[14:06] <seb128> or do you have a ssh remote folder or something?
[14:11] <gnomefreak> seb128: i havent needed my ssh key in a while. i did accently changed a setting and im working on change remember currently running apps in the startup apps under option unless it only saves it when the box is checked
[14:12] <gnomefreak> i changed my passphrase under keys and encryptions
[14:12] <gnomefreak> back to needing one
[14:13] <gnomefreak> i will keep playing with it
[14:22] <yofel> vish: updated the no-package response on the wiki page with the one brian set for the gm scrpts (https://code.edge.launchpad.net/~yofel/canonical-qa-tracking/gm-response-pa/+merge/31694) does that sound good?
[14:27] <vish> yofel: looks good to me :)
[14:27] <yofel> actually that was the original merge
[14:27] <yofel> vish: https://wiki.ubuntu.com/Bugs/Responses#Bugs%20without%20a%20package
[14:35] <vish> yofel: oops! got distracted!  yeah , i was wondering why "ubuntu-bug" was removed from the wiki
[14:36] <vish> yofel: we could use: "When reporting bugs in the future please use 'ubuntu-bug' and the name of the package affected "
[14:36] <vish> yofel: no need to mention apport
[14:37] <gnomefreak> if you add the apport-collect
[14:37] <vish> gnomefreak: "reporting" ;)
[14:37] <gnomefreak> ah
[14:37] <vish> yofel: but the reason i didnt add it was because i dint know why it was removed
[14:37] <yofel> I'm just trying to find out..
[14:39] <yofel> actually, ubuntu-bug was never mentioned it seems
[14:40] <yofel> like here a rev from last year https://wiki.ubuntu.com/Bugs/Responses?action=recall&rev=265#Bugs%20without%20a%20package
[14:40] <vish> yofel: use the direct link to : https://help.ubuntu.com/community/ReportingBugs ,the wiki link is just a refresh page
[14:41] <gnomefreak> should i file the nvidia+kernel bug aganst linux or nvidia-current
[14:43] <yofel> vish: done for the wiki page
[14:45] <gnomefreak> yofel: the second link?
[14:45] <vish> yofel: also , "use apport by using 'ubuntu-bug'" > "use 'ubuntu-bug'"  ?
[14:46] <vish> my system is totally borked :(
[14:46] <yofel> IMHO it wouldn't be bad for people to know that they're using apport if we're already not using apport-bug
[14:47] <yofel> gnomefreak: second link?
[14:47] <vish> had a harddrive check failure , accepted to auto-correct and several things seem to have gotten reverted! :/
[14:47] <gnomefreak> the ReportingBugs link?
[14:48] <yofel> gnomefreak: I changed the 2nd one https://wiki.ubuntu.com/Bugs/Responses#Bugs%20without%20a%20package
[14:48] <vish> yofel: not sure why we need to mention that we use apport.. it would just confuse, that would be a response used for everyone, not just for those running a dev release
[14:48] <gnomefreak> yofel: thanks
[14:49] <vish> yofel: anyway , a second pair of eyes would be good too :)
[14:49] <gnomefreak> i also have buttonlacethong (not sure if that is current spelling or not
[14:49] <gnomefreak> damn
[14:49] <vish> gnomefreak: whaaaaaT1
[14:50] <vish> lol!
[14:50] <gnomefreak> i was talking to someone else.
[14:50] <gnomefreak> we are joking around on aim
[14:50] <yofel> ^^
[14:50] <Pici> riiight
[14:50] <vish> gnomefreak: yeah , right , you were only joking ;p
[14:50] <gnomefreak> :)
[14:51] <gnomefreak> apport is slow atm like really slow
[14:54] <gnomefreak> still going. that is about 5 minutes so far
[15:04] <vish> devildante: http://imgur.com/2NOVK nice work!
[15:05] <devildante> thx, vish :)
[15:05] <greg-g> vish: that is live in maverick?
[15:05] <greg-g> devildante: ^
[15:05] <vish> greg-g: not yet :)
[15:05] <greg-g> ahh
[15:05] <vish> thats his branch
[15:05] <greg-g> looks awesome though
[15:05] <greg-g> devildante++
[15:06] <devildante> still a little slow though, but mvo said he would take care of it :)
[15:06] <greg-g> awesome
[15:06] <vish> devildante: mpt is reviewing it as we speak :) !
[15:06] <devildante> oh oh oh great :p
[15:06] <vish> devildante: if you finish that fast , we can merge it for Maverick :)
[15:07] <devildante> yay!
[15:07] <devildante> It's already finished (for me)
[15:08] <devildante> because my pathetic python/pygtk skills mean I can't fix the slowness
[15:08] <devildante> So I think I'll just wait mpt's verdict :p
[16:44] <cjae> wow a bugs channel
[16:44] <cjae> : )
[16:45]  * cjae hopes there is someone nice enough to report a bug
[16:47] <devildante_> cjae: no, you have to do everything by yourself, muhaha :p
[16:47] <charlie-tca> cjae: this channel is for discussion of the bug reports filed. To see the actual bugs filed, there is #ubuntu-bugs-announce
[16:47] <cjae> No I just suck at reporting them since I never know the real underlying problem :P
[16:48] <devildante_> cjae: what's your problem?
[16:48] <cjae> one sec trying to ge t some detail
[16:51] <cjae> http://kde-look.org/content/show.php/Palmscan+?content=126482 ok I think maybe this is causing part of  it, it is my theme for kdm
[16:52] <cjae> might also be the shitty properitary ati driver but I think it was doing it with the opensource one as well
[16:54] <cjae> when I login the computer sometimes freezes on the kde splash screen and I mean freeze hard like no tty sometimes
[16:55] <cjae> like hard reset is the only way and sometimes it just works upon reboot
[16:55] <devildante_> cjae: does it occur when using the default kdm theme?
[16:55] <cjae> could that theme cause that kind of problem?
[16:56] <devildante_> cjae: idk, it could be
[16:56] <devildante_> cjae: it's preferable to use default settings
[16:57] <devildante_> cjae: can you test?
[16:57] <cjae> I think it did with it too but this is my first time with a ati system really, so I cant really judge the comparison with nvidia
[16:59] <cjae> but when I login with the default stuff the is sort of graphic tearing at the  top of the screen that seems to fixed by using a non-default theme in the ....
[16:59] <cjae> workspace theme
[16:59] <cjae> sorry trying hard to use right terminalogy
[17:00] <devildante_> cjae: can you precise when it does happen? (everytime, every 2 reboots...)
[17:01] <cjae> also the ati opensource driver really misdetects my tv via hdmi (my monitor is hooked up via dvi)
[17:01] <cjae> devildante_: every two, its very weird
[17:02] <cjae> brb 1
[17:04] <cjae> ok
[17:06] <cjae> so I think the theme - might - be the login thing but doesnt explain the tearing sometimes, the tearing is sort of like that bad tearing in kde 4.1 and such
[17:08] <cjae> I spoke about the ati opensource in #radeon but they told me it was tvs fault, hdmi overscan that couldnt be turned off or something, checked all menu, nothing, used properitary, worked fine
[17:10] <cjae> also when I FIrst installed 10.04 I had I nvidia card and the nouveau driver had vertical hold issue to tv too but that was via svideo, never got time to report that either
[17:11] <cjae> other than those things 10.04 has been pretty sweet
[17:14] <cjae> devildante_: what do you mean test?
[17:15] <cjae> like change the theme back and forth
[17:15] <devildante_> I meant test it with the default kdm theme
[17:17] <cjae> sure but I am lame at reporting because either I dont have enough info in the report or I get lame things back, like "have you tried upgrading" or this will not be passed on to devs
[17:18] <cjae> or too little time
[17:18] <cjae> :(
[17:19] <cjae> brb will test theme
[17:30] <cjae> ok so it wont do it now with either theme on and a bunch of apps open and restore session on/off in kde
[17:30] <cjae> but it really does happen
[17:31] <cjae> gf tried restarting system three times last night and nothing all hung on kdm then when I got home I restarted she watched and it just went
[17:32] <cjae> she is proficent enough to know to like she didnt press recovery mode or anything, it really hung after burning a bluray disc data failed
[17:33] <cjae> as well
[17:35] <cjae> oh which brings me to k3b is broken for bluray as well, sent a bug report for that as well, that report went well though, got am email from sabastian saying it had been fixed
[17:35] <cjae> think it was him anyway
[17:36] <cjae> think the k3b is still broken in 10.04 had to use nero linux
[17:36] <cjae> :(
[17:38] <cjae> also these are never upgraded systems either as a fresh install when distro changes
[17:39] <cjae> always as a *
[17:40]  * cjae loves the advancement on the opensource video drivers though
[17:42] <cjae> anyway have seriously cut into time much needed for other things, if anyone can make use of this then great, if not, then sorry plugging up channel :)
[17:43] <cjae> all ati issues where on 64 bit too
[20:32] <vish> who assigns bugs to the Ubuntu Desktop team?
[20:34] <vish> can anyone assign?
[20:35] <seb128> we stopped assigning bugs to that team
[20:35] <yofel> er, wasn't that their previous way of tracking thins?
[20:35] <yofel> ah
[20:35] <seb128> it was useful to list bugs on any components tracked by the team
[20:35] <seb128> but we have better way to do that nowadays
[20:36] <vish> seb128: yeah , thought so , was wondering if it had changed , thanks
[20:36] <yofel> you might want to fix https://wiki.ubuntu.com/DesktopTeam/Bugs then, it says 'Our bugs have the assignee desktop-bugs ' under 'Links'
[20:36] <seb128> right
[20:37] <vish> yofel:  nah , Bug 613198 got assigned to the team itself! so was confused
[20:37] <ubot2> Launchpad bug 613198 in indicator-sound (Ubuntu) "indicator-sound requests an invalid libido version (affects: 1) (heat: 6)" [Medium,New] https://launchpad.net/bugs/613198
[20:38] <yofel> ah
[20:59] <hggdh> wow!
[21:03] <vish> hggdh: ??? finally ,someone told you the bugsquad secret? :)
[21:04]  * vish hides
[21:05]  * vish pretty sure hggdh is gonna kick a few of our asses :D
[21:05]  * hggdh looks for vish, but cannot find him
[21:05] <vish> hggdh: when i our ro_bot coming back?
[21:06] <vish> is*
[21:09] <hggdh> bug 1
[21:09] <ubot2> Launchpad bug 1 in tilix (and 18 other projects) "Microsoft has a majority market share (affects: 509) (heat: 2644)" [High,New] https://launchpad.net/bugs/1
[21:10] <hggdh> vish: this one ^?
[21:10] <vish> now , i'm confused :D
[21:10] <vish> hggdh: i was asking about pedro_  :)
[21:12] <hggdh> vish: oh. Sorry, difficult to see the difference between them two
[21:12] <vish> true!
[21:12] <hggdh> I think he is in next week, had two conferences to go
[21:12] <vish> cool..
[22:24] <BUGabundo> evening
[22:27] <bcurtiswx> Hola
[23:38] <km0r3> I need to forward bug 613622 to project's bug tracker on SourceForge. I've opened a new bug and copypasted the information; is this the only way for forwarding bugs to SF?
[23:38] <ubot2> Launchpad bug 613622 in qtpfsgui (Ubuntu) "qtpfsgui crash (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/613622
[23:50] <micahg> km0r3: yeah, you can link the bug if there's an upstream project in LP
[23:52] <km0r3> micahg: ah, too bad :/
[23:52] <km0r3> micahg: well, thank you for th answer
[23:53] <micahg> km0r3: no, you have to do what you did first, but you can then link it in LP
[23:53] <micahg> km0r3: where's the SF bug?
[23:55] <km0r3> micahg: ok, I did that
[23:55] <km0r3> micahg: http://sourceforge.net/tracker/?func=detail&aid=3039712&group_id=183831&atid=906820
[23:56] <micahg> km0r3: yep, you did it, now I can mark our bug triaged
[23:56] <ubot2> km0r3: Error: <Bugtracker.plugin.Sourceforge instance at 0xb6b2d0c> bug 3039712 not found
[23:56] <km0r3> WTF?
[23:56] <micahg> km0r3: that's pretty useless both for upstream and us actually
[23:56] <micahg> they'll need a backtrace at a minimum
[23:56] <micahg> as would we
[23:57] <km0r3> micahg: so, we should mark it incomplete and request more information?
[23:58] <micahg> km0r3: yes, there should be a response requesting a backtrace
[23:59] <km0r3> micahg: so what's the attachment of the bug? http://launchpadlibrarian.net/53064364/_usr_bin_qtpfsgui.1000.crash


[13:01] <Unggnu> hi all
[13:01] <Unggnu> Could somebody please take a look at this report: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/421662
[13:01] <ubot3> Malone bug 421662 in linux "Intel 3945ABG WLAN doesn't work with Ubuntu Kernel in Karmic [regression]" [Undecided,New]
[13:01] <Unggnu> It is a regression to previous Ubuntu versions and the Vanilla kernel
[13:07] <Unggnu> bye


[21:25] <eQuiNoX__> Hi everyone, could I have some assistance in setting up networking for QEMU ARM.
[21:25] <eQuiNoX__> (ARM64)
[21:26] <eQuiNoX__> The state is explained here : https://unix.stackexchange.com/questions/214039/qemu-aarch64-and-networking-connections


[08:15] -queuebot:#ubuntu-ci-eng- paelzer, https://bileto.ubuntu.com/#/ticket/4753 Diff missing (jammy/ipxe, jammy/qemu, jammy/xen). Failed to build (jammy/libvirt)
[11:34] -queuebot:#ubuntu-ci-eng- sil2100, https://bileto.ubuntu.com/#/ticket/4770 No packages are being considered! If you are preparing sources manually, please upload them to the PPA now
[14:30] -queuebot:#ubuntu-ci-eng- sil2100, https://bileto.ubuntu.com/#/ticket/4770 Failed to build
[14:47] -queuebot:#ubuntu-ci-eng- xnox, https://bileto.ubuntu.com/#/ticket/4687 Needs rebuild due to higher version at destination
[17:24] -queuebot:#ubuntu-ci-eng- slyon, https://bileto.ubuntu.com/#/ticket/4704 Needs rebuild due to higher version at destination (jammy/glib2.0, jammy/linux, jammy/netplan.io, jammy/open-iscsi, jammy/systemd). Release pocket (jammy/dnsmasq)


[07:06] -GitHub[m]:#mir-server- **[MirServer/wlcs]** bors[bot] merged [pull request #275](https://github.com/MirServer/wlcs/pull/275): XDG stable: use mock methods instead of notification lists
[11:17] <Saviq> alan_g Morning o/
[11:17] <Saviq> We're due a call for testing on top of 2.12.1, on Frame we've added the live display configuration functions now. Or do we want a 2.13 soon to bundle it all up?
[11:23] <alan_g[m]> I don't think we want to wait. We should get the idle inhibit fix out
[11:23] <Saviq> I'll get the full set of CfTs out
[11:24] <alan_g[m]> The display configuration and app placement stuff can wait for 2.13 to be polished
[11:26] <Saviq> You mean Frame's live display config changes? That's on master, so the beta 2.12.1 build also has that now
[11:27] <Saviq> Or, some of…
[11:27] <alan_g[m]> The changes are there in source, but don't do anything with 2.12
[11:29] <Saviq> We need a stable branch for Frame :P
[11:30] <alan_g[m]> //o\
[11:52] <alan_g[m]> The current policy of hiding things behind feature flags works well enough
[11:53] <Saviq> Well, yes, but at least with this you'll be able to set display-layout and it will just have no effect. Though I suppose that's true for any other unsupported key 🤦♂
[11:54] <alan_g[m]> Right: Nothing changes
[11:54] -GitHub[m]:#mir-server- **[MirServer/mir]** AlanGriffiths opened [pull request #2853](https://github.com/MirServer/mir/pull/2853): Add an API for adding custom attributes to outputs
[11:54] -GitHub[m]:#mir-server-
[11:54] -GitHub[m]:#mir-server- > This is motivated by Frame needing a way to assign apps to outputs
[12:18] -GitHub[m]:#mir-server- **[MirServer/ubuntu-frame]** AlanGriffiths edited [pull request #129](https://github.com/MirServer/ubuntu-frame/pull/129): Allow configuration to assign applications to outputs
[12:25] -GitHub[m]:#mir-server- **[MirServer/mir]** AlanGriffiths requested a review from Saviq for [pull request #2853](https://github.com/MirServer/mir/pull/2853): Add an API for adding custom attributes to outputs
[13:31] <Saviq> Messed up my system downgrading back to kinetic… if only I had made a snapshot on this fantastic zfs root… recovery time now
[14:07] <alan_g[m]> Time for a retrospective
[14:51] <Saviq> Let's say I'm back.
[16:37] -GitHub[m]:#mir-server- **[MirServer/wlcs]** Saviq assigned  to [pull request #275](https://github.com/MirServer/wlcs/pull/275): XDG stable: use mock methods instead of notification lists
[16:37] -GitHub[m]:#mir-server- **[MirServer/mir]** Saviq assigned  to [pull request #2852](https://github.com/MirServer/mir/pull/2852): Use wayland::Weak in place of raw pointers in XDG surfaces
[16:41] -GitHub[m]:#mir-server- **[MirServer/mir]** Saviq assigned  to [pull request #2853](https://github.com/MirServer/mir/pull/2853): Add an API for adding custom attributes to outputs
[17:37] <Saviq> \o Good night all
[18:00] -GitHub[m]:#mir-server- **[MirServer/mir]** bors[bot] merged [pull request #2853](https://github.com/MirServer/mir/pull/2853): Add an API for adding custom attributes to outputs
[19:25] -GitHub[m]:#mir-server- **[MirServer/mir]** bors[bot] merged [pull request #2852](https://github.com/MirServer/mir/pull/2852): Use wayland::Weak in place of raw pointers in XDG surfaces


[19:38] <malev> does anyone here understand about gwibber? I want to run the latest  version from launchpad, but don't want to mess with my current version
[19:38] <malev> any clue?


[12:03] <jbailey> https://launchpad.net/people/jbailey/+branch/cdbs/cdbs-trunk
[12:05] <doko> I'll have a look. Does this include docs? :-P
[12:05] <jbailey> "debian/rules help" will work.
[12:05] <doko> will or does ;-P
[12:06] <jbailey> I think does now. =)
[12:11] <doko> ahh, the gconv thing doesn't work for the 32 bit archs building 64bit packages
[12:15] <jbailey> Oh?  Interesting.
[12:15] <jbailey> I didn't review more than the changelog.
[12:18] <doko> maybe just needs more additions in debian/sysdeps


[18:44] <valorie> damn it
[18:44] <valorie> I don't know what to do besides cancel it
[19:02] <valorie> ....and I can't cancel or edit according to the LP how-to
 Hey @Valoriez no worries, I am out at the moment, back in about 1.5hrs. will jump on my laptop and help out as soon as I can
[19:55] <valorie> sure -- this poll will go for four more days
 Hello, I'm on my laptop now
 So I figure that we want to create 3 polls, for Aaron, Rik and Rick. That operate something like this.
 https://launchpad.net/~kubuntu-members/+poll/kubunt-council-2019-ricktimmis
 Then email Kubuntu Members List and ask them to Vote
 Is there a Kubuntu Members only mailing list ?
 Or shall I just send an email to kubuntu-users and kubuntu-devel ?
 Here are the Polls
 https://launchpad.net/~kubuntu-members/+poll/ahoneycutt-kc-reelection-2021
 https://launchpad.net/~kubuntu-members/+poll/rikmills-kc-relection-2021
 https://launchpad.net/~kubuntu-members/+poll/ricktimmis-kc-relection-2021
 @ahoneybun has a script somewhere that finds all the LP email addresses for the members
 OK, I'll stand by and see what he says..
 I have this: https://github.com/ahoneybun/lp-election-helper
 Sorry about that.
 Cool, taking a look
 also forked here by the look of it: https://github.com/YokoZar/lp-election-helper
 Ah
 Ah he took my comment.
 Ah he took my commit
 linked to from: https://discourse.ubuntu.com/t/how-to-create-an-election/1387
 in the end, whichever works
 Hmmm so I'm getting a error
 ImportError: No module named launchpadlib.launchpad
 So I see that there is a python3-launchpadlib in the apt repo, but no python2 version. The script is Python 2, and fails to run under python3.
 So I'm just going to email it to the list, and those who are members can vote. This also means others will be informed too.
 OK.. all done..
 Off to bed now, ttfn
[21:09] <RikMills> I guess members who 'care' will likely still be on the lists ;)
[23:11] <valorie> ooops, sorry, I was not looking at IRC
[23:12] <valorie> yes you can email all Kubuntu Members right from LP
[23:13] <valorie> I'll do that if you have not, and I guess we'll just ignore my mistaken poll
 I most likely could port it to python3


[20:26] <_KaszpiR_> thinking how to detect certain things with ansible in some sane way
[20:27] <nacc> _KaszpiR_: if you know exactly what you run, then why do you care?
[20:27] <_KaszpiR_> was thinking about creating local fact
[20:27] <ioria> creating local fact
[20:27] <_KaszpiR_> naccc cause we are going to present automation tools to 3rd parties and they may do upgrades on their own, and we want to warn them in certain situatlions
[20:28] <_KaszpiR_> like 'your system was not upgraded in 3 months, pls die in a fire'
[20:28] <ioria> sweet
[20:28] <nacc> _KaszpiR_: that also will miss unattended-upgrades
[20:28] <nacc> etc.
[20:29] <_KaszpiR_> we disabled that
[20:29] <nacc> there are better ways to determine if a system is out of date
[20:29] <_KaszpiR_> such as?
[20:29] <pantera> I died in a fire once. Would not recommend it.
[20:29] <_KaszpiR_> apt pinning?
[20:29] <nacc> `apt-get update` and look for what it tells you? or emulate the same
[20:29] <nacc> _KaszpiR_: no, not apt pinning
[20:30] <nacc> that has nothing to do with what you just said
[20:30] <_KaszpiR_> yeah, bad idea
[20:30] <nacc> apt pinning is for holding packages at a specific version
[20:30] <_KaszpiR_> ye
[20:30] <_KaszpiR_> but still apt-cache policy can show interestig things
[20:30] <pantera> Like what version you have.
[20:31] <_KaszpiR_> ok you said that history.log will mis apt full-upgrades
[20:31] <pantera> Of the software.
[20:31] <nacc> pantera: please don't just chime in
[20:31] <nacc> _KaszpiR_: right, becuase you are searching for 'apt-get dist-upgrade'
[20:31] <_KaszpiR_> well, yes
[20:32] <nacc> _KaszpiR_: you can also run (apparently `apt list --upgradeable`) not sure if apt-get has something similar
[20:32] <_KaszpiR_> but does apt updates history.log?
[20:32] <ioria> wondering if sudo apt update has a return status if updates needed
[20:32] <_KaszpiR_> (not to mention ansible tries to invoke apptitude if available)
[20:32] <nacc> _KaszpiR_: it seems fragile to depend on some log file having the content you want
[20:33] <_KaszpiR_> yeah :/
[20:33] <akik> nacc: you can run apt-get with -s show it'll just show what it'd do
[20:33] <_KaszpiR_> welcome to ubuntu ;D
[20:33] <akik> so it'll just show
[20:33] <nacc> _KaszpiR_: i think that's short-sighted and insulting a bit to ubuntu
[20:33] <_KaszpiR_> that's why we switched to centos (hr hr hrrrr :D )
[20:33] <nacc> _KaszpiR_: you decided to implement it this way :)
[20:33] <nacc> akik: yeah that's true to
[20:34] <_KaszpiR_> not really, I asked how can I find when last time apt-get dist-upgrade was invoked ;D
[20:34] <nacc> akik: but if you olny care about if there are updates to install, simulating is still more expensive than you probably want
[20:34] <ioria> history.log
[20:34] <_KaszpiR_> ok, to be more generic, how to detect when someone did dist-upgrade or full-upgrade
[20:35] <nacc> _KaszpiR_: still the same file
[20:35] <nacc> _KaszpiR_: my point was you seem to be searchinng for the wrong thigs
[20:35] <_KaszpiR_> why so?
[20:35] <nacc> if you are tryingn to tell someone "hey your system is out of date", when they ran dist-upgrade is irrelevant
[20:35] <nacc> just see if there are packages to upgrade
[20:35] <_KaszpiR_> ah this way
[20:35] <_KaszpiR_> yes, you're right
[20:36] <nacc> because as root on your victim, i ca make your tool be dumb really easily
[20:36] <nacc> by always truncating history.log
[20:36] <nacc> just trying to save you some long-term pain
[20:36] <_KaszpiR_> so my general idea is to actually use exact package versions and then when we present to3rd party updated version it will show them which core packages needs to be updated
[20:37] <_KaszpiR_> that's why I was thinking about using apt-pin for certain packages, and maybe to give a note that 'its wort to pgrade after xxx days'
[20:37] <_KaszpiR_> that would rather not be an issue if we had proper CI/CD setup
[20:37] <_KaszpiR_> but client just wants to do certain things on their own
[21:07] <Transfusion> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743094?comments=all nice, meltdown patch breaks hibernation since kernel 4.13.0-25.
[21:11] <Ben64> Transfusion: should report that to mint
[21:34] <grym> i'm running 16.04.3 on aarch64 and having trouble installing a package; 'package sox is not available, but is referred to by another package ... sox has no installation candidate`.  How should i make apt tell me more about what's going on? `apt-cache search sox` returns nothing.
[21:36] <grym> (i have been able to install this package without issue on other machines with similar configurations, so i don't think this is an ARM problem)
[21:37] <kostkon> !info sox xenial
[21:37] <akik> grym: it should be in xenial/universe
[21:37] <grym> akik: i'm not super familar with apt; what does that imply i should do next?
[21:38] <kostkon> grym, make sure you have enabled all your repos, universe included
[21:38] <akik> grym: is aarch64 a platform that is supported by canonical?
[21:38] <grym> kostkon: ahh, yes.  just looked at sources.list
[21:38] <kostkon> oh aarch64
[21:39] <kostkon> grym, you mean arm64?
[21:39] <grym> kostkon: yes.  nomenclature vaires
[21:39] <grym> varies*
[21:39] <kostkon> grym, it should be availabe to you
[21:39] <grym> i'm on this: https://elinux.org/Jetson_TX1
[21:40] <grym> refreshing now
[21:40] <kostkon> grym, oh
[21:40] <grym> anyway, adding universe did the trick
[21:40] <kostkon> grym, unfortunately, for that very reason, messed up repo sources, we only support Ubuntu here
[21:41] <grym> kostkon: this _is_ ubuntu
[21:41] <grym> says so all over the os :)
[21:42] <grym> admittedly nvidia has plasted stuff on top
[21:42] <grym> anyawy, thanks!
[21:42] <kostkon> i thought elinux was some kind of Ubuntu derived distro
[21:43] <akik> kostkon: it's arm64 and supported
[21:43] <kostkon> akik, apparently
[21:50] <leftyfb> nacc: hey, can we continue with my libusb issue? Can you repeat your last post about it? I signed off, got a notification while driving but for some reason it's gone and can't refer to it
[21:53] <ks92> i want to download something from ssh server and type
[21:53] <ks92> scp username@hostname:/path/to/remote/file -p port /path/to/local/file
[21:53] <ks92> its not working
[21:53] <leftyfb> ks92: -P not -p
[21:54] <leftyfb> ks92: also, "not working" isn't as helpful as error codes
[21:54] <ks92> still not working
[21:54] <ks92> no error but i get nothing
[21:54] <ks92> its like the port its not using here
[21:54] <ks92> its look like the port in wrong place
[21:56] <leftyfb> ks92: I just typed it out exactly as you did and got an error message.
[21:57] <leftyfb> ks92: you should have got "/path/to/remote/file: Not a directory"
[21:57] <ks92> i have everything right
[21:57] <ks92> but my problem with -p
[21:58] <AmericanBlend> shouldn't you specify the port before specifying user@host?
[21:58] <AmericanBlend> that's at least what man says
[21:58] <leftyfb> ks92: again, -P specified port, not -p. Second, if you typed everything right, it would be working. Third, if you typed it like you first did but with -P, then you would get an error message similar to what I posted
[21:58] <mister> hello!
[21:59] <ks92> scp username@hostname:/path/to/remote/file -P port /path/to/local/file this is not working too
[21:59] <leftyfb> ks92: please copy and paste exactly what you're doing with all resulting messages to pastebin.ubuntu.com
[21:59] <ks92> dude i didnt get any error message
[21:59] <ks92> when i type it , nothing happends
[21:59] <leftyfb> ks92: what version of ubuntu are you running?
[21:59] <ks92> 17.2
[22:00] <leftyfb> That isn't a version of ubuntu
[22:00] <AmericanBlend> that's mint
[22:00] <ks92> 17.10 *
[22:01] <kostkon> ks92, lsb_release -a
[22:01] <misterboring> I've been testing out ubuntu 17.10 using the the installer iso on a usb drive. I'm typing "try ubuntu" environment right now. I tried to install VLC to run a video, but when I did it said "Unable to install VLC; failed to read from snapd: Error receiving data: Connection reset by peer."
[22:02] <ks92> No LSB modules are available. Distributor ID:	Ubuntu Description:	Ubuntu 17.10 Release:	17.10 Codename:	artful
[22:02] <kostkon> ks92, ok
[22:02] <leftyfb> ks92: scp -P port username@hostname:/path/to/remote/file /path/to/local/file
[22:02] <misterboring> then it says vlc is installed, and I can try and run it from the menu, but nothing happens when I launch it. trying to launch it from the terminal gets me: cannot create lock directory /run/snapd/lock: Permission denied
[22:03] <misterboring> this happens for every program I try to test. I'm worried that if I go ahead and install 17.10 onto my hard drive I won't be able to install or run anything.
[22:03] <yuznumara> sa
[22:03] <misterboring> what's going on?
[22:03] <ks92> not working
[22:04] <badboyjer> you have to edit /etc/apt/sources.list to install updates
[22:04] <leftyfb> ks92: please paste everything from your termial to pastebin
[22:04] <badboyjer> or just run synaptic
[22:04] <leftyfb> misterboring: I do not think your test is an adequate determination for the same functionality with ubuntu being installed
[22:05] <yuznumara> guysi how can i create something like a room ?
[22:05] <leftyfb> yuznumara: go to #freenode
[22:05] <ks92> worked
[22:05] <ks92> sry by bad
[22:05] <ks92> my*
[22:05] <ks92> thanks
[22:05] <misterboring> alright, thanks.
[22:05] <leftyfb> ks92: next time, please provide the requested information when people are trying to help you
[22:05] <dheenaxe> m8 do yo see mi rollin'
[22:05] <yuznumara> ye
[22:06] <dheenaxe> lul man
[22:06] <dheenaxe> its easier than i thought
[22:06] <yuznumara> f*ck that touchpad
[22:06] <leftyfb> dheenaxe: please stay on topic. This channel is for ubuntu support questions
[22:06] <dheenaxe> whoops sorry about that
[22:06] <yuznumara> what was that ?
[22:06] <leftyfb> !op
[22:07] <leftyfb> oops, didn't know it was that critical of a tool
[22:07] <rollingubuntu> hello! anyone who could help me troubleshoot a "workspace switching" problem in Ubuntu 14.04 on 32 bits?
[22:07] <badboyjer> yea ubuntu 14.04 doesnt have regular updates
[22:07] <yuznumara> guys how can i create something like a room ?
[22:07] <badboyjer> you should upgrade to a newer version
[22:07] <leftyfb> yuznumara: go to #freenode for help with that. It has nothing to do with ubuntu
[22:07] <yuznumara> #freenode
[22:08] <yuznumara> quit
[22:08] <kostkon> there you go. bye
[22:08] <leftyfb> 1 down
[22:08] <kostkon> :)
[22:08] <leftyfb> rollingubuntu: please detail your issue
[22:11] <misterboring> Is it possible to save any of the changes I make when I'm using the live-usb environment? Or keep any downloaded  files?
[22:11] <leftyfb> misterboring: not by default, no
[22:11] <leftyfb> misterboring: copy the downloaded files to another location/drive/network device
[22:11] <rollingubuntu> leftyfb: thanks!! :) some days ago I had the Automatic update popping up and I did the updates, then, few days later I realized I can not use CTRL + ALT + arrows any more to switch between workspaces; now, the only way I can stilldo this is by using the mouse and the workspace switcher icon on the launcher. Note: if I have an app running ona workspace and I click that app's icon from the launcher, the workspace will not change an
[22:12] <misterboring> leftyfb: alright. thanks again!
[22:18] <rollingubuntu> leftyfb: does this sound like a mystery? :D
[22:19] <leftyfb> rollingubuntu: it sounds like an incomplete post to me. I was waiting for you to finish your typing
[22:20] <rollingubuntu> leftyfb: right, apologies --> ... the workspace will not change and will not take me to the running app's window any more
[22:21] <leftyfb> rollingubuntu: I would open the "keyboard" utility, click on Shortcuts and verify and potentially set the shortcuts you prefer
[22:22] <rollingubuntu> leftyfb: been there, done that
[22:22] <leftyfb> rollingubuntu: any reason you haven't updated to 16.04?
[22:24] <rollingubuntu> leftyfb: yes... I am scared of updates, honestly... there could be something that does not work after one update (like this workspace switching for example) and while everything works, why bother?
[22:24] <badboyjer> yea i hear ya thats why im hesitating about updates
[22:24] <leftyfb> rollingubuntu: I used 14.04 for 2 years and never ran into your issue. I've been running 16.04 for 2 years and don't have those sorts of issues.
[22:26] <rollingubuntu> leftyfb: you are blessed I guess... I was telling the same to some of my friends who hesitated and eventually never went for Ubuntu because if there is anything that goes wrong, they felt they are screwed
[22:27] <leftyfb> yeah, cuz Microsoft does a much better job of supporing it's customers for free
[22:28] <wafflejo_> heh or Google with the chromebooks, good luck getting a hold of someone there (talk to the robot they say)
[22:28] <rollingubuntu> leftyfb: more people are used to microsoft than ubuntu, so, there is a bigger likelyhood to run to your neighbour and ask for some tips?
[22:28] <badboyjer> have robots came out already
[22:31] <rollingubuntu> leftyfb: if any similar issue (like mine) would happen to your OS, how would you approach it?
[22:33] <leftyfb> rollingubuntu: try looking for another task using the same keyboard shortcut. Try installing compizconfig-settings-manager and look through there for the similar settings and verify/change as needed
[22:36] <kevr> is requests-ntlm not included anywhere in ubuntu's repositories?
[22:37] <leftyfb> kevr: doesn't look like it
[22:37] <kevr> hmm.
[22:39] <nacc> leftyfb: sorry, was afk myself
[22:40] <nacc> leftyfb: i spun up a ubuntu:trusty/i386 lxd and it installed fine there
[22:40] <leftyfb> nacc: I did the same
[22:40] <nacc> leftyfb: and it didn't install there?
[22:40] <leftyfb> looks like libcgmanager0:i386 is my problem on these machines
[22:40] <leftyfb> correct
[22:40] <nacc> leftyfb: hrm, maybe a ppa or something?
[22:41] <leftyfb> doesn't look like it
[22:41] <leftyfb> same version from trusty backports
[22:42] <leftyfb> nacc: https://pastebin.ubuntu.com/26538151/
[22:42] <nacc> leftyfb: ah my system has backports enablled but did not install libcgmanager0 from it
[22:42] <nacc> leftyfb: i dont' believe backports go through the archive testing
[22:42] <leftyfb> none of those packages it's complaining about are installed as dependencies on the container with libcgmanager0
[22:42] <nacc> leftyfb: or through install verification (that they don't break any packages in the archive)
[22:44] <leftyfb> it would be great if we could track down what package or whatever is holding this up
[22:44] <nacc> leftyfb: my lxd has https://paste.ubuntu.com/26538159/
[22:44] <nacc> leftyfb: try tellinng it *not* to use the backports version
[22:46] <rollingubuntu> leftyfb: since the click on the launcher to a running app like Firefox or any other really does not switch to the correct work-space (it does not switch to any work-space), I doubt it is a shortcut issue (the keyboard is fully functional, other shortcuts wotk, ex open the terminal, or the home folder)
[22:47] <leftyfb> rollingubuntu: tried disabling and enabling multiple workspaces?
[22:47] <rollingubuntu> leftyfb: yes, no change though
[22:48] <leftyfb> nacc: I tried sudo apt -t trusty-updates install libcgmanager0:i386 and got the same issue
[22:48] <yuznumara> s
[22:48] <yuznumara> hi is there any chance to create room with password
[22:48] <yuznumara> ?
[22:49] <leftyfb> yuznumara: I told you before. Please go to #freenode.
[22:49] <nacc> leftyfb: i'm not sure, all i did was `lxc launch ubuntu:trusty/i386; lxc exec <container> bash` and in that shell apt-get update; apt-get install libusb-1.0-0-dev and it worked fine :)
[22:50] <leftyfb> nacc: I created a 64bit trusty ... same thing, not issues. I no it works with stock. I'm trying to track down where the issue lies with this install. It's prevalent in over 100 robots that will need this resolved :)
[22:51] <nacc> leftyfb: i see
[22:51] <imbezol> how can I adjust my mouse speed and scroll speed? the system settings section has no effect
[22:51] <nacc> leftyfb: as annoying as it is, the easiest is to resolve the conflicts for apt, imo
[22:51] <leftyfb> the odd part is the error complaining about a bunch of packages which aren't actual dependencies
[22:52] <leftyfb> nacc: there are no conflicts
[22:52] <leftyfb> nacc: none of the packages it's complaining about are installed here or on the working container
[22:53] <nacc> leftyfb: libcgmanager0 is installed here
[22:54] <nacc> leftyfb: so yeah that's reallly weird
[22:54] <leftyfb> nacc: to be fair, the testing should be done on a 64bit environment to take into consideration the dependencies on 32bit libraries which 64bit systems use to support 32bit applications that 32bit systems don't need
[22:55] <leftyfb> since installing libcgmanager0 working fine on the 64bit os, but not libcgmanager0:i386
[23:05] <Gencade> hey guys - I am wanting to try out a custom gtk3 theme, but i can't find the directory that gnome-tweak tool stores themes in.  Isn't it supposed to be ~/.themes ?
[23:05] <Gencade> or could someone give me the correct location if I am mistaken
[23:05] <Gencade> ubuntu 17.10
[23:05] <Gencade> vanilla gnome3
[23:11] <TJ-> leftyfb: the issue is installing on a multilib system as a foreign arch only?
[23:14] <leftyfb> TJ-: I don't follow. It's a 64bit arch. Trying to install a 32bit library to support a 32bit binary
[23:14] <AmericanBlend> you need multiarch
[23:14] <AmericanBlend> multilib/multiarch
[23:14] <TJ-> leftyfb: right, is the target requires multilib foreign architecture, which affects the way the packages resolve
[23:15] <leftyfb> TJ-: the problem is, this works fine on a fresh container, but not on an existing setup we have. I need to track down what the difference is
[23:16] <TJ-> leftyfb: Trusty still had some issues with separating out the i386/amd64 dependencies so I'd guess this may be one of them. You'll need to enable apt's debugging of the package resolver to pinpoint it
[23:16] <grapez> hello
[23:16] <leftyfb> TJ-: how do I do that?
[23:18] <TJ-> leftyfb: try "apt-get -o Debug::pkgProblemResolver=true install ..."
[23:18] <TJ-> leftyfb: see the Debug section of "man apt.conf" for other possible Debug names
[23:19] <TJ-> leftyfb: "Debug::pkgDepCache::Marker=True" might be useful too
[23:20] <leftyfb> HA!
[23:20] <leftyfb> got it working
[23:20] <leftyfb> I actually just forced it to install from backports
[23:20] <TJ-> leftyfb: I'll bet it's related to "libgl1-mesa-dev" (-dev package) which will draw in 'build' relationships
[23:21] <TJ-> leftyfb: one of the major challenges of the multiarch transition was separating the -dev packages into arch-specific versions where structures used different sized elements
[23:22] <leftyfb> TJ-: it was related to that actually
[23:22] <leftyfb> TJ-: even though on the container test environment that package isn't neccesary
[23:23] <TJ-> leftyfb: not surprised :)
[23:23] <leftyfb> TJ-: actually, it was libgl1-mesa-glx
[23:24] <leftyfb> https://pastebin.ubuntu.com/26538151/
[23:25] <leftyfb> i'm out for the night now though. Thanks for the assist nacc and TJ-
[23:25] <nacc> leftyfb: yw
[23:39] <lwizardl> I would like to convert a ubuntu install into a virtual machine. it was installed to an 200gb hdd but only is using around 10gb of space. Is there a way to create an image without the extra blank space?
[23:39] <AmericanBlend> rsync
[23:39] <AmericanBlend> then manually adjust configs and install a bootloader
[23:40] <TJ-> lwizardl: Depending on the file-system you can shrink it down to a minimal size, reduce the enclosing partition to match, and only copy the reduced image
[23:41] <AmericanBlend> create a self-expandable volume for the vm 9if your vm supports it that is), run another virtual system with that volume connected, format it, rsync the data or scp it, adjust the configs, install a bootloader, done
[23:41] <lwizardl> TJ-, I think it was ext3 partition
[23:41] <TJ-> lwizardl: ext is good; has the resize2fs tool for the job
[23:43] <TJ-> lwizardl: will you creating the VM image via a LiveISO boot, or another booted Ubuntu OS - as opposed to wanting to do this from the OS that needs shrinking?
[23:44] <lwizardl> TJ-, another booted system, I have pulled the drive from the other system
[23:45] <TJ-> lwizardl: can you show us the partition table of the target HDD so I can give you an idea of what would be required?
[23:48] <lwizardl> let me connect the drive, have to find a spare sata cable
[23:52] <respawn1> hello. I used ubuntu 17.10 a few months ago and had some issues with DNS leaking during VPN connections. I would like to use Ubuntu again as my daily driver. Does anyone know if this issue has been resolved?
[23:54] <hggdh> respawn1: do you have a bug number?
[23:55] <respawn1> hggdh: no, at the time I need a secure connection quickly so I never followed up with the correct procedure, I am just wondering generally if someone uses VPNs on ubuntu and is experiencing any DNS leaks
[23:57] <TJ-> respawn1: what kind of DNS leak? the host's public ISP DNS server being used instead of DNS on the VPN? Or DNS requests routing over the public connection rather than the VPN connection?