/srv/irclogs.ubuntu.com/2019/08/08/#snappy.txt

kenvandinehey hellsworth01:01
hellsworthhey sorry for the ping. it was an accident :)01:35
zygaGood morning04:52
AavarGood morning :)06:01
* zyga resumes work06:12
zygait rains heavily today06:21
zygapstolowski|afk: https://github.com/zyga/snapd-peer-demo <- something I made at the sprint, suggestions welcome06:45
* zyga breaks for breakfast06:46
=== pstolowski|afk is now known as pstolowski
pstolowskimorning07:12
zygahey Pawel07:12
pstolowskizyga: the peer demo looks nice, and serves as a useful example for practical use of interface hooks07:39
zygapstolowski: yeah, I'll write a short blog post about it07:39
pstolowskizyga: btw, in that peer demo you could have interface hooks on the slot side too. i'd also consider renaming foo/bar to something more descriptive, e.g. provider/consumer08:10
zygaI used to have it symmetric but I abandoned that idea08:13
zygayeah, the names are terrible :D08:13
zygain practice that will be juju and microk8s08:13
zygaor the other way around08:13
zygaone can then take advantage of the other08:13
zygaby reusing cached images08:13
zygaor some other content that is big and costly to download08:13
zygaI worked on this with Ian from the Juju team08:14
zygaIan Booth08:14
pstolowskizyga: i see; you could have just placeholders for the slot hooks, so that it's visibile they are there and could do something.08:15
pstolowskiogra: ping08:39
jameshzyga: when you've got time, could you give https://github.com/snapcore/snapd/pull/7042 another look over? I think the main blocker was your concerns over the number of mounts08:57
mupPR #7042: interfaces: add an interface granting access to AppStream metadata <Created by jhenstridge> <https://github.com/snapcore/snapd/pull/7042>08:57
zygajamesh: looking08:57
zygaah, I remember that08:57
zygajamesh: +1, let me look at spread09:01
zygajamesh: I commented in the thread with you and jamie09:01
jameshIIRC, the spread failure was unrelated to my code changes.  I didn't get round to asking someone to restart that job09:04
Aavarzyga, kenvandine: Regarding my problem with graphical snaps. I did try a few things yesterday and discovered something that might or might not be related.09:06
zygaoh, what did you discover?09:06
zygajamesh: restarted09:06
AavarI added a new user and that users home-directory (and everything in it) was owned by my original user.09:07
Aavarzyga, after chowning the files the snaps where still not working.09:07
AavarI allso tried to stop lightdm and start from startx, but still the same.09:08
Aavarzyga, I don't know if that tells you anything else than that my system if fucked :P09:09
zygaI'm still totally puzzled by what may be wrong on your system09:09
zygacan you do one more experiment09:09
zygaadd a new user that is independent from your current user09:09
zygaand see if that works09:09
jameshzyga: I wrote up a proposal for another problem we've run into on the desktop team here: https://forum.snapcraft.io/t/proposal-allow-snaps-to-specify-their-exact-desktop-file-id/1268909:09
Aavarzyga, that is what I did :)09:09
zygaAavar: but not owned by your user09:10
zygathat's really the same exact user09:10
zyga(same uid)09:10
zyganothing else matters in snapd world09:10
jameshzyga: I'm still working on session agent/user daemons/dbus activation right now, but it would be useful to get some feedback on the proposal at some point09:10
zygajamesh: ah, I think we were expecting this09:10
zygajamesh: I'll have a read but I think you need to discuss with samuele next week09:10
zygajamesh: I'm working on a fix for device cgroup and mount namespace (as always)09:10
zygajamesh: I think the proposal is sensible, we just need a way to control it properly09:11
jameshzyga: we finally found a use case where this is a blocker rather than just inconvenient :-)09:11
Aavarzyga, I'm sorry. I don't thing you understood. I did create a new user named "control" (via the gui in ubuntu) and the system added /home/control but it was owned by "aavar:aavar". I have no idea why...09:11
AavarI can try to add another user via the terminal.09:11
zygaoooh09:12
zygaI see09:12
zygaI misunderstood you09:12
zygawow that's really weird09:12
zygahmm09:13
Aavarzyga, I added a new user now via terminal and that did not happen.09:13
AavarLet me log back in09:13
zygajamesh: ^ Aavar is debugging an issue where none of the graphical snaps can start09:13
zygacannot talk to x09:13
zygawe are kind of lost, perhaps you have some ideas09:13
zygajamesh: what should snapd do for parallel installs in the new desktop proposal?09:14
jameshzyga: I wonder if this is abstract namespace X socket vs. /tmp/.X11-unix X socket?09:14
zygajamesh: the denial has addr=null09:14
zygaAavar: ^ am I correct? (dmesg | grep DENIED)09:14
zygaat the same time DISPLAY is set correctly09:15
zygaAavar: what is your desktop shell? gnome shell?09:15
jameshzyga: parallel installs would not be supported by my proposal.  But in the notification case, the app would need to own a bus name matching the desktop file ID.09:15
jameshand that is also not parallel install friendly09:15
zygaI agree09:15
zygaI think we should be able to say "this snap does not support parallel installs"09:16
zygaI think it's a topic for next week when the architect is back09:16
zygamaciej is also away this week, attending Flock09:16
jameshFair enough: I just want to make sure it is on the radar.  I've got other work to complete in the mean time09:17
zygaack09:18
Aavarzyga: still the same result with a new user. I guess I have to wait for kenvandine :)09:19
zygaAavar: ^ are you on gnome-shell?09:19
Aavarzyga: now i'm on unity, but I tried with gnome-shell (bot wayland and X11)09:20
zygahmmm09:21
Aavarzyga: i'm sorry. I am not familiar with gnome. Is gnome-shell the same as gnome3?09:22
zygayeah09:22
zygaI really don't know what is affecting your system09:22
zygaif you were anywhere close I'd love to have a look and inspect it myself09:22
zygabut I guess that is hard09:22
Aavarzyga: yeah :)09:23
AavarI think, if kenvandine or someone dont find anything useful in the next few days I will reinstall.09:24
jameshAavar: one last thing to help with debugging: could you provide a paste of the output of "ss -lxp | grep X11"09:35
Aavarjamesh: brb, lunch :)09:37
Aavarjamesh: p/qZ6hVy2YXF/10:06
Aavarhmm..10:07
Aavarjamesh: https://paste.ubuntu.com/p/qZ6hVy2YXF/10:07
jameshAavar: okay.  That basically disproves my theory from earlier about the abstract socket not being available10:16
jameshzyga: looks like your restart cleared the test failure for https://github.com/snapcore/snapd/pull/7042.  Thanks10:16
mupPR #7042: interfaces: add an interface granting access to AppStream metadata <Created by jhenstridge> <https://github.com/snapcore/snapd/pull/7042>10:16
jameshis there anything else needed before merging it?10:17
Aavarjamesh, so that shows that the socket is open?10:18
zygajamesh: let me look but I think that's good now10:19
jameshAavar: the command lists listening unix domain sockets.  The /tmp/.X11-unix/X0 socket is one you can see in the file system, while the @/tmp/.X11-unix/X0 socket is an "abstract namespace socket"10:19
zygajamesh: it's in10:19
jameshAavar: an unconfined app can connect to either, while a snap app is blocked from connecting to the first.10:20
mupPR snapd#7042 closed: interfaces: add an interface granting access to AppStream metadata <Created by jhenstridge> <Merged by zyga> <https://github.com/snapcore/snapd/pull/7042>10:20
jameshzyga: thanks!10:20
jameshAavar: if the abstract namespace socket was missing for some reason, that would explain your problems10:20
Aavarbtw, jamesh, zyga: When I log in via console or ssh (not x) it gives me an error: xhost:  unable to open display ""10:22
AavarIsn't that also weird?10:22
jameshAavar: that is normal if the DISPLAY environment variable isn't set10:23
Aavarjamesh: ok :)10:24
zygaAavar: yeah, that is to be expected10:24
zygabrb10:26
zygaActually. A longer break is needed10:28
* pstolowski lunch10:56
jonzen<jonzen> not sure if this is the right place but here goes   xubuntu 18.04 when i remove a snap as soon as it finishes my desktop goes black and then the login screen comes up     any1 have a solution for this11:28
jonzensorry  didnt identify11:28
jonzenmore info   sony laptop  i7 quad 4gb11:30
zygajonzen: hey11:47
jonzenyessir11:48
zygajonzen: can you please tell us what kind of GPU are you using?11:48
zygajamesh: is your system using wayland?11:48
zygajonzen: ^11:48
zygakenvandine: ^ looks like desktop session crashes on udev trigger/settle11:48
jonzennvidia11:48
jonzenhow do i find out about wayland11:48
zygajonzen: open a terminal and run: echo $XDG_SESSION_TYPE11:49
jonzenx1111:49
zygacan you pastebin your journal log? you can do that with journalctl | pastebinit # you may need to install pastebinit first11:51
jonzenok  gimme a min  i will do11:51
zygathank you11:52
jonzenhttp://paste.ubuntu.com/p/JVQ6dsSJyV/  your very welcome11:52
zygaAug 08 06:23:28 pd-VPCF133FX xfce4-notifyd[23765]: xfce4-notifyd: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.12:00
zygahmm, I'm not an expert on X stuff, can you please report a bug on snapd12:02
zygayou can do that on bugs.launchpad.net/snapd12:03
zygamake sure to include your system version and other relevant stuff; you may be able to report the bug with apport12:03
zygawhich may provide more relevant information12:03
zygaI understand that it is somehow snapd that is causing this but it seems X has crashed12:03
jonzenshould i put this pastebin in?12:03
zygaor perhaps not X12:03
zygabut the session in xfce12:03
zygayes, as an attachment12:04
jonzenok  will do   ty very much for your help12:04
* zyga goes for a walk12:07
jonzenzyga  ty again   i did as you asked12:13
mupPR snapd#7200 closed: recovery: update to latest fde-utils <Created by cmatsuoka> <Closed by cmatsuoka> <https://github.com/snapcore/snapd/pull/7200>12:17
=== ricab is now known as ricab|lunch
mupPR snapd#7222 opened: tests: show just the last log as part of the debug output when check journal logs <Simple 😃> <Created by sergiocazzolato> <https://github.com/snapcore/snapd/pull/7222>12:25
mupPR core-build#51 opened: Use /var/lib/snapd/seed/snaps/ as fallback when mounting core and kernel <Created by stolowski> <https://github.com/snapcore/core-build/pull/51>12:40
ograpstolowski, you pung ? (sorry. at a sprint this week)13:01
pstolowskiogra: hey, ah i didn't realize you're at the sprint; i'min the standup atm, will you have a moment for a HO later today?13:01
ograpstolowski, hmm, we have a training, might be late for you when i have a free spot13:02
ogra(and i actually have to go to class now ... perhaps drop an email with a quick summary)13:03
pstolowskiogra: i'll open a forum topic, perhaps you can reply there and help, ty13:03
=== ricab|lunch is now known as ricab
ijohnsonhey jdstrand, zyga when y'all get a chance could you re-review https://github.com/snapcore/snapd/pull/7010 ? it is pretty straight forward I think and the tests are finally all green :-)13:46
mupPR #7010: interfaces/docker-support: add controls-device-cgroup <Created by anonymouse64> <https://github.com/snapcore/snapd/pull/7010>13:46
jdstrandijohnson: hey, yes13:46
ijohnsonthanks jdstrand13:46
zygaI’m off for lunch now13:51
zygaijohnson: I’ll review when I am back but it feels like +114:19
ijohnsonack, thanks zyga14:19
ijohnsonhey cachio, I'm unable to reproduce this error in spread tests with qemu locally, any idea what might be different about the google spread machines than qemu?14:40
ijohnsonsee https://pastebin.canonical.com/p/zsQVWhP2CP/ and https://travis-ci.org/snapcore/snapd/jobs/56905796014:40
ijohnsonit seems like some kind of path error where python3 thinks it should be reading from the core snap and not from the snap itself (and indeed those files it's trying to access exist in the snap and load fine on my system and in qemu 16.04)14:41
cachioijohnson, checking14:44
cachioijohnson, we use different images on qemu and gce14:45
cachiolet me cehck which python we have14:46
cachioijohnson, do you have a qemu instnace opened?14:46
ijohnsonright, but inside the snap it sholdn't matter which version of python?14:46
ijohnsonone second let me reboot it (I think it's off14:47
ijohnsoncould I boot the google image with qemu locally if I downloaded it?14:47
cachioijohnson, I didn't try that14:48
cachiobut should be possible14:48
cachiobut not sure if you have the permissions to download the image14:49
cachiome neither14:49
ijohnsonah okay14:49
cachioit is using /usr/lib/python3.6/lib-dynload/termios.cpython-36m-x86_64-linux-gnu.s14:49
ijohnsonstill it's very odd that in one image a strictly confined snap tries to load python libs from the core snap, and that in another image it's loading python libs from the application snap14:49
cjp256who would be the chrome sandbox goto expert here? :)  I've got an electron 5 app I am trying to confine strict, but it gets cranky when I remove the chrome-sandbox binary and add --no-sandbox.  It runs fine in devmode, but otherwise fails with `audit: type=1400 audit(1565112543.140:3117): apparmor="DENIED" operation="open" profile="snap.<app>.<app>" name="/proc/8998/setgroups" pid=8998 comm="<app>" requested_mask="w"14:49
cjp256denied_mask="w" fsuid=1000 ouid=1000`  - i'm curious if anyone has ideas... it does look like the program bails after reading /proc/cpuinfo14:49
cachioijohnson, is it install as classic snapd o devmode?14:50
ijohnsonit's installed strict14:50
ijohnsoncachio: see https://github.com/snapcore/snapd/pull/7214/files#diff-82c7f368687a491cb7edc7d848e2b57eR1614:50
mupPR #7214: interfaces/network-setup-control: allow dbus netplan apply messages <Created by anonymouse64> <https://github.com/snapcore/snapd/pull/7214>14:50
ijohnsonactually I should probably have you review that spread test anyways since I'm still new on the spread tests14:51
ijohnsonalright I requested a review from you on that PR14:51
ijohnsoncjp256: do you have browser-support interface connected with allow-sandbox: true14:52
cachioijohnson, please check the python version which is being used on qemu14:52
cachioit is the main difference14:52
ijohnsoncachio: almost done preparing the image, will check in a minute14:52
ijohnsoncachio: it's python 3.5.214:53
cachioijohnson, could you try updating python14:54
cachioand see if this is hte problem?14:54
ijohnsonthe version of python3 in the snap though is python 3.6.814:54
ijohnsoncachio: I ran apt update && apt upgrade and still can't reproduce the problem14:56
ijohnsonI guess the version of python didn't change from the upgrade though14:57
cachioijohnson, lets try this14:58
cachiorun the test on google but in the spread.yaml14:59
cjp256ijohnson: i was trying to do it without allow-sandbox, but if that's the required route, that'll have to do for now.  Mostly curious if anyone else has had problems without allow-sandbox and using --no-sandbox?14:59
cachioadd the image14:59
cachioimage: ubuntu-os-cloud/ubuntu-1604-lts14:59
cachioto the ubuntu-16.04-64 system14:59
cachioand run the test14:59
cachiothis is a pristine image14:59
cachiowhich is more similar to qemu15:00
ijohnsoncachio: I have to get into a meeting right now actually, but where should I add that? to the system spec under qemu in the spread.yaml?15:00
cachioijohnson, in the spread.yaml in the google backend where you have all the systems15:01
cachioyou should configure https://paste.ubuntu.com/p/yw3wVnBvFR/15:01
ijohnsonah and then launch the google system instead of qemu15:01
cachioand run the test on google system15:02
ijohnsonack, I'll let you know how it goes when I'm done with my meeting15:02
cachioijohnson, so we can see if the problem is related either to google image or to the preparation of the suite15:02
ijohnsoncjp256: AFAICT that access only is allowed with allow-sandbox: true unfortunately15:02
cjp256alright, thanks ijohnson :)15:03
mupPR snapcraft#2656 closed: appstream: xslt support for ul nested in p <Created by sergiusens> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/2656>15:26
pstolowskii've created a forum topic re firstboot & initrd: https://forum.snapcraft.io/t/firstboot-seeding-failure-scenario-possible-fixes-and-boot-process-confusion-question/1269815:27
jdstrandcjp256: you shouldn't remove the chrome-sandbox binary. just let it have 755 permissions and use --no-sandbox.15:29
jdstrandiirc15:29
jdstrandpopey_ and Wimpress may have other tips15:29
diddledanwimpy's on his holidays right now, so only popey :-)15:30
cjp256jdstrand: I'll give that a shot, thanks!15:33
* cachio lunch15:36
mupBug #1839498 opened: xdgopenproxy: Outdated github.com/godbus/dbus dependency <Snappy:New> <https://launchpad.net/bugs/1839498>16:08
=== pstolowski is now known as pstolowski|afk
zygare16:26
zygapstolowski|afk: thank you for creating the topic16:26
zygaijohnson: looking now, sorry, took family out for dinner16:26
ijohnsonno worries zyga, thanks for the review16:27
zygaijohnson: I sent one comment but I need to make coffee to review this properly16:38
zygaijohnson: tomorrow I'd love to share my thoughts on the device cgroup topic16:39
zygaijohnson: we can perhaps join before or stay after the call16:39
ijohnsonoh actually what you commented on should be removed from the PR16:39
ijohnsonI missed that in my cleanup to address jdstrand's comment16:39
ijohnsons16:39
ijohnsonbut yes we can discuss more about the device cgroup tomorrow after SU16:39
zygaright16:42
zygait is unconditional now16:42
ijohnsonso that message shouldn't have been there at all16:42
zygaindeed16:42
* zyga checks the coffee pot16:42
zygawhen away from home I use this portable thing that you can just put on the stove16:44
ijohnsonnice16:44
ijohnsonI also have to step away for ~30 minutes16:47
ijohnsoncachio: I was able to reproduce the issue on that clean google image you provided, however I then realized that the shebang was hard-coding /usr/bin/python3, when I launch netplan with $SNAP/usr/bin/python3 then the issue goes away17:32
ijohnsonso I don't think it was an issue with the build env, it was an issue with my test snap rather17:32
ijohnsonand how that was calling python17:32
cachioijohnson, great, I am reviewing the test btw17:33
ijohnsonthank you17:33
cachioijohnson, mp17:33
cachioijohnson, happy to help17:33
* ijohnson lunches17:33
mupPR snapcraft#2657 closed: Release changelog for 3.7.2 <Created by sergiusens> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/2657>17:41
=== hellsworth_ is now known as hellsworth
mupPR core-build#50 closed: initramfs: run recover mode if trigger is detected <Created by cmatsuoka> <Merged by cmatsuoka> <https://github.com/snapcore/core-build/pull/50>18:28
zygare18:31
mupPR snapd#7223 opened: recovery: update fde-utils <Created by cmatsuoka> <https://github.com/snapcore/snapd/pull/7223>18:55
* cachio afk19:11
=== hellsworth_ is now known as hellsworth
mupPR snapd#7221 closed: tests: split the sbuild test in 2 depending on the type of build <Simple 😃> <Created by sergiocazzolato> <Merged by sergiocazzolato> <https://github.com/snapcore/snapd/pull/7221>20:27
cjp256I'm having a little trouble with multipass on Windows - anyone have any pointers? couldn't find much useful in the event logs... :) https://www.irccloud.com/pastebin/qHKIdUdC/20:37
cjp256probably more appropriate for #multipass I imagine20:38
ijohnsoncachio: thanks for the review on the PR, I addressed your points, can you re-review when you get a chance?20:46

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!