[04:59] <pbek> since yesterday my snappy builds (e.g. https://code.launchpad.net/~pbek/+snap/hswitch/+build/205732) get an error message "Store upload failed: Authorization failed.". Is this something I can fix myself?
[04:59] <pbek> I guess I post this in #launchpad
[05:06] <jamesh> pbek: have you changed your Ubuntu One password since setting up that recipe?
[05:08] <jamesh> you might be able to get LP to ask for new auth details by updating the recipe to stop uploading to the store, then enable it again
[05:08] <jamesh> if that doesn't help, perhaps ask on #launchpad
[05:50] <pbek> jdstrand: thank you, no, I did no password change
[07:43] <popey> pbek: I had some fail yesterday too
[09:38] <jamesh> Is there something wrong with the google:debian-9-64 spread backend machines? I've been getting a number of CI failures on my PRs that seem to be unrelated to my changes.  It's either a timeout cleaning up the debian VM, or a sometimes a failure in interfaces-network test
[09:48] <Chipaca> jamesh: I'm seeing lots of TLS failures, or timeouts waiting for shutdown
[09:48] <Chipaca> jamesh: also the interfaces-network one yes
[09:48] <Chipaca> jamesh: so, to answer your question, yes :-)
[09:50] <Chipaca> jamesh: I'm hoping whatever it is unglues on its own, because the rest of the team is out
[09:50] <Chipaca> and I'm working on a 20%
[09:50] <Chipaca> or hoping to :-)
[09:56] <zyga> jamesh: I think there's a real race or rare bug on debian
[09:57] <zyga> jamesh: I restarted your branches a few times
[09:59] <Chipaca> zyga: is that about the interfaces-network test?
[09:59] <Chipaca> zyga: also what are you doing here, you're supposed to be off :-)
[10:10] <Chipaca> ooooh
[10:10] <Chipaca> nice one
[10:11] <Chipaca> niemeyer: a spread run just ended in spread throwing an index-out-of-range panic. https://pastebin.ubuntu.com/p/6y65bmWYgR/ (full log at https://api.travis-ci.org/v3/job/373097606/log.txt )
[10:11] <Chipaca> i'll leave that one up for now
[10:12] <Chipaca> (that's running tests from #5121 fwiw)
[10:12] <mup> PR #5121: interfaces:minor autoconnect cleanup <Simple> <Created by stolowski> <https://github.com/snapcore/snapd/pull/5121>
[11:09] <Chipaca> zyga: I'm getting 'permission denied' with a snap that uses layouts. Is {/: $SNAP/base} a supported layout?
[11:11] <Chipaca> zyga: [316407.549782] audit: type=1400 audit(1525172894.246:2070): apparmor="DENIED" operation="mount" info="failed mntpnt match" error=-13 profile="snap-update-ns.netscape-navigator" name="/" pid=26597 comm="3" srcname="/snap/netscape-navigator/x1/base/" flags="rw, rbind"
[11:11] <Chipaca> fwiw
[11:34] <zyga> Chipaca: re
[11:34] <zyga> Chipaca: layouts on / are unsupported
[11:34] <Chipaca> zyga: mimics on / also?
[11:34] <zyga> Chipaca: correct
[11:34] <zyga> Chipaca: we cannot support that yet
[11:34] <zyga> Chipaca: we might with mimicfs or something
[11:34] <Chipaca> zyga: i tried {/bin: $SNAP/bin} with the base not having /bin and it failed also
[11:34] <zyga> but it would have to be one that is mounted at /
[11:35] <zyga> Chipaca: that's expected
[11:35] <zyga> we cannot make / writable
[11:35] <Chipaca> zyga: I was trying to use layouts as a stepping stone to a base
[11:35] <zyga> (technically)
[11:35] <zyga> Chipaca: nah, use a proper base
[11:35] <Chipaca> zyga: that's a lot more commitment :-) also i _liked_ the idea of using layouts as a steppinig stone to bases
[11:36] <zyga> Chipaca: what do you need to create?
[11:36] <Chipaca> zyga: could a readonly / layout work?
[11:36] <zyga> no
[11:36] <zyga> we cannot do the mimic on /
[11:36] <Chipaca> zyga: i mean i know it doesn't
[11:36] <zyga> so no matter if it writable or not
[11:36] <zyga> maybe use a chroot?
[11:36] <zyga> a snap with a chroot inside would be easier
[11:38] <Chipaca> zyga: nm, i'll get it working
[11:41]  * zyga gets back to cleaning the house
[12:27]  * Chipaca remembers lunch, all of a sudden
[12:58] <Chipaca> "$thing doesn't work as expected" "hm, that looks like $other_thing isn't running automatically, can you start it by hand?" "that's a very generic answer that doesn't apply here"
[12:58] <Chipaca> wellp, glad you know what's going on, person
[13:11] <zyga> Chipaca: Hmm?
[13:12] <Chipaca> zyga: nm
[13:12] <Chipaca> zyga: just me grumbling
[13:12] <zyga> All Good?
[13:13] <Chipaca> zyga: yep
[13:13] <zyga> I’m stuck at a family event
[13:14] <zyga> Waiting till we can run and bike away
[13:59] <pbek> popey: my QOwnNotes build today works, but hswitch is still failing. I'll try re-authenticate be disabling and enabling automatic store uploading
[14:50] <dougie> What's the status of HiDPI on Snap packages? I've tried a few snaps (Such as notepadqq) and there have been problems on my display.
[14:51] <seb128> what sort of problems? are you sure those issues are due to the fact that they are distributed as snaps and not by the upstream code not handling hidpi?
[14:55] <dougie> For Electron apps, I'm noticing that it scales perfectly, but the cursor is super tiny. With Notepadqq, which uses Qt5, the cursor looks fine but the UI is 1/2 the proper scale.
[14:57] <dougie> It appears the tiny cursor issue is also apparent in Chromium.
[14:58] <dougie> The notepadqq issue might go away if I find a way to pass the variable QT_AUTO_SCREEN_SCALE_FACTOR to the snap app.
[15:00] <Chipaca> dougie: if you do 'snap run --shell the-snap', is it set in there?
[15:02] <dougie> Just did that and typed "env". Odd, looks like that variable is already there.
[15:02] <dougie> And it's set to the proper value - 1
[15:03] <Chipaca> dougie: the next step would be to look at how the app is being launched; maybe it's via desktop-launcher and it's somehow fumbling the environment
[15:06] <Chipaca> dougie: or maybe the qt libraries in the snap don't understand hidpi
[15:07]  * Chipaca knows nothing
[15:13] <dougie> Maybe you're right about that. Pretty sure that this thread indicates that: https://github.com/giowck/symphytum/issues/48
[15:21] <Chipaca> dougie: interesting link, i wonder if popey is aware (and if popey is the right person that needs to be aware)
[15:22] <popey> I will take a look,thanks!
[17:44] <popey> om26er: number of android studio installs has doubled in the last week
[19:22] <klaasvakie> hi, I am using Ubuntu 16.04 and have the lxd snap installed. When running the "lxc" command, a "snap" directory appears under my home dir. Is it possible to move this somewhere less visible, like somewhere in .config?
[19:39] <kyrofa> klaasvakie, I'm afraid not, that's where snapd places all snaps' user data
[19:40] <kyrofa> klaasvakie, please see bug #1575053
[19:40] <mup> Bug #1575053: Please move the "$HOME/snap" directory to a less obtrusive location <julyshakedown> <snapd:Confirmed> <snapd (Ubuntu):Confirmed> <https://launchpad.net/bugs/1575053>
[19:42] <klaasvakie> kyrofa, thanks, wow didn't realise I was stepping into such a high profile bug. ... tiptoes away ...
[19:42] <kyrofa> klaasvakie, hahaha
[20:23] <mup> PR snapcraft#2114 opened: meta: stop creating empty snap directory in prime <Created by kyrofa> <https://github.com/snapcore/snapcraft/pull/2114>
[20:53] <mup> PR snapcraft#2095 closed: lxd: proper error classes for container errors <Created by kalikiana> <Merged by kyrofa> <https://github.com/snapcore/snapcraft/pull/2095>
[20:56] <mup> PR snapcraft#2115 opened: storeapi: ensure snap ID is sane before using it <Created by kyrofa> <https://github.com/snapcore/snapcraft/pull/2115>
[21:15] <mup> PR snapd#5122 opened: snap: add support for `snap advise-snap --from-apt` <Created by mvo5> <https://github.com/snapcore/snapd/pull/5122>
[23:18] <mup> PR snapcraft#2116 opened: storeapi: handle 5xx error codes for all store endpoints <Created by kyrofa> <https://github.com/snapcore/snapcraft/pull/2116>
[23:24] <mup> PR snapcraft#2117 opened: pluginhandler: correctly dedent the run script <Created by sergiusens> <https://github.com/snapcore/snapcraft/pull/2117>