[00:00] if it's a known issue, is there a plan to, or has it been, solve(d)? [00:03] snapcraft seems to have trouble with non-ascii === cwayne_ is now known as cwayne [00:04] yeah. that's crazy considering that 90% of the population aren't English [00:05] of course 87% of all statistics are made up on the spot, but you get my point [00:05] lol [00:31] 502 proxy error? [00:35] hmm? [00:35] probably https://bugs.launchpad.net/launchpad/+bug/1683819 [00:35] Bug #1683819: Continuous 502 proxy error on snap upload to store [00:58] diddledan: https://bugs.launchpad.net/snapcraft/+bug/1662456 [00:58] Bug #1662456: snapcraft fails if desktop file included "ascii" cannot decode byte [00:58] ah, thankyou [00:58] * diddledan clicks that it affects me [00:59] so now i get: desktop interfaces (x11) specified without meta/gui/*.desktop. Please provide a desktop file via setup/gui/*.desktop if using snapcraft or meta/gui/*.desktop otherwise. It should reference one of the 'apps' from your snapcraft/snap.yaml. [00:59] i have no idea what this means [00:59] ali1234: does your yaml refer to the desktop interface? [00:59] no? [01:00] it refers to x11 [01:00] ali1234: right, that's what the above messages says is "desktop interfaces" [01:00] okay but what is setup/gui/*.desktop? [01:00] ali1234: a .desktop file for yoru application [01:00] what is the setup/gui part? [01:01] ali1234: i'm guessing a path in your snap's source [01:01] its nothing to do with anything i am trying to build [01:02] ali1234: hrm? you're tyring to use an interface that apparently requires .desktop files [01:02] ali1234: so ... absolutely has to do with wha tyou're building (a snap) [01:02] it doesn't require them, the snap works fine when i build and install it locally [01:02] setup is a snapcraft-specific thing that if desired needs to be a folder along-side your yaml file [01:03] ali1234: could be a disagreement about the version of snapcraft you're using and the one the builder is using? [01:03] so it is telling me to create setup/gui/pulseview.desktop, and then put it in the snap somehow? [01:03] ali1234: you put it in the repository containing your yaml [01:03] it'll put it in there automatically [01:03] ali1234: at that path [01:03] ali1234: and it will dtrt [01:04] so i just create it? [01:04] how does it know what filename to look for? [01:04] let me screenie my tree [01:04] https://usercontent.irccloud-cdn.com/file/I0ALdl5B/ [01:04] so i do have to make the directories? [01:04] ali1234: presumably via the application name that is using the interface? [01:04] and what is your app called? [01:04] ali1234: yes, you ahve to make the directories [01:05] ali1234: it's telling you, you need a file at setup/gui/.desktop [01:05] the app is called pulseview but it shows up as sigrok.pulseview when installed, because the snap has two apps [01:05] ali1234: so of course you need the directgories [01:05] ali1234: how else would you create the file in the directories? [01:05] well, i would use dump plugin with a line like organize: pulseview.desktop: setup/gui/pulseview.desktop [01:06] that's how you normally get a file into the snap [01:06] ali1234: this is not into the snap [01:06] ali1234: this is in the 'source' [01:06] the error comes from store review of the built snap [01:06] ali1234: the same place your yaml lives [01:06] ali1234: right, so you put in the source and snapcraft will put it in the right place [01:06] so i would expect it means it wants the file in the snap [01:06] that's my reading [01:07] it's an automatic thing [01:07] you don't do anything with it other than create it [01:07] ali1234: i don't think you do anything with teh built snaps [01:07] that's all snapcraft's job [01:07] you build them [01:07] i.e. don't try to put it in the build process [01:07] except maybe organize them [01:08] snapcraft handles the setup/ folder automatically [01:08] so what did you put in the .desktop file? [01:08] ahi found an example [01:09] diddledan: right that makes sense, it's like custom parts [01:21] I'm getting closer to finally achieving a custom gtk build [01:21] corebird 1.5 (released a few days ago) requires more recent gtk deps than xenial provides so my snap needs custojobby [01:22] I have managed a complete compile but I'm still working out the right stuff to force into the snap === chihchun_afk is now known as chihchun [07:12] ogra_, it looks like --extrausers is not working for chfn command in latest core snap (for armhf at least), which prevents "snap create-user" to work, is that a known issue? [07:41] abeato: we found that yesterday and ogra_ created a new core snap which should fix that problem [07:41] abeato: that should be fixed in edge [07:43] morphis, great... the perils of using edge ;) [07:43] abeato: yes :-) [07:55] PR snapd#3281 opened: tests: add test for empty snap name on revert [08:13] re [08:13] good morning [08:19] morning zyga ! [08:23] good morning peeps! [08:24] morning [08:25] all that stuff last night about meta gui? turns out its just a warning, not an error [08:25] so now i have 6 versions of the same snap pending review in the store [08:25] Chipaca: hey hey :) [08:25] pstolowski: good morning! [08:25] morning! [08:25] * zyga coundn't help it and had to take a walk in the morning [08:26] morphis: o/ [08:26] zyga: can you give https://github.com/snapcore/snapd/pull/3274 another look? I've added more test cases and printing a warning whenver a confinement check is ignored [08:26] PR snapd#3274: cmd/snap,tests/main: add force-devmode switch instead of spread system blacklisting [08:26] morphis: I already am, I'm mid way through the new commit [08:26] great [08:40] PR snapcraft#1295 closed: recording: record build packages installed in the snap [08:44] fgimenez: do we use travis oauth tokens? [08:45] fgimenez: (good morning, also :-) ) [08:51] Chipaca: hey :) if you mean github oauth tokens from travis nope we let travis interact with github [08:52] fgimenez: ah alright [08:52] asking because of https://blog.travis-ci.com/2017-05-08-security-advisory [08:52] but if we don't, great :-) [08:52] “Various GitHub OAuth tokens and secure environment variables that users included in their builds were accidentally exposed via inclusion in build logs on Travis CI.” [08:52] Chipaca: yep, no problem for us, we push to gh, but from our side of the vpn [08:57] morphis: quick suggestion, perhaps the skip part could be a function that we source so that we don't have to copy-paste the same line for consistency in behavior [08:58] zyga: you mean the snap forced-devmode check? [08:58] morphis: otherwise looks ok, I was doing some other things but I'll +1 it (again) in a moment [08:58] morphis: yeah, something about that, it's tricky because it's simetimes if ... then exit; but sometimes not [08:58] zyga: I was thinking about that before but actually like this to be really explicit and as it might be used in different combinations [08:59] morphis: yeah, I understand [09:00] lets leave it lets see how complex the logic gets into the future [09:00] I will have multiple changes for fedora too which makes things more complicate and might refactor a few of these tests again [09:00] zyga, hey, wrt to the problem of hanging configure hook on debian; I found out (by examining and comparing strace for that hook on both debian ubuntu) that a posible suspect is: "bind(3, {sa_family=AF_INET6, sin6_port=htons(0), inet_pton(AF_INET6, "::1", &sin6_addr), sin6_flowinfo=htonl(0), sin6_scope_id=0}, 28) = ? " [09:01] zyga, i'm not familiar with ipv6 peculiarities, any idea what may be different in that aspect on debian? [09:01] pstolowski: hey [09:02] pstolowski: isn't that what jdstrand found when initially looking at the bug? [09:04] morphis, oh, where did he mention that? [09:04] https://bugs.launchpad.net/snappy/+bug/1674193/comments/16 and https://bugs.launchpad.net/snappy/+bug/1644573 [09:04] Bug #1674193: core snap's configuration hangs on debian | openSUSE | mainline kernel [09:04] Bug #1644573: snapctl causes hooks to attempt to open ip/ipv6 tcp connection [09:04] pstolowski: the thing is that there was a fix merged in 2.23.6 merged which broke with 2.24 again [09:05] pstolowski: verified once ago that this problem was fixed with 2.23.6: https://bugs.launchpad.net/snappy/+bug/1674193/comments/25 [09:07] morphis, oh, wonderful! thanks for these links [09:07] pstolowski: they* are on your forum post already :-) https://forum.snapcraft.io/t/tests-broken-in-master/457/8 [09:08] morphis, oh indeed.. [09:08] * pstolowski embarassed [09:08] happens :-) [09:08] so i finally have an approved snap in the store. do i just click release now? [09:17] ali1234: as you wish :-) [09:18] what does the release button do? [09:18] what is the difference between releasing and publishing? [09:19] ali1234: if my memory serves, the release button takes you to a page where you choose which channels to publish it to [09:20] oh [09:20] so it has a terrible name [09:21] ali1234: the button? [09:21] and it should just say "edit channels" [09:21] ali1234: you don't edit channels with it though [09:21] really? [09:21] ali1234: editing a channel means changing the channel itself [09:21] why does it show a form labelled channels: which i can edit then? [09:21] "Select the channels to release current revision." [09:22] yep [09:22] no, you mean publish [09:22] PR snapcraft#1297 closed: sources: validate unknown source-type in yaml [09:22] "Select the channels to [publish] current revision [in]." [09:22] ali1234: i'd suggest you open a forum topic about this [09:22] it's possible the store uses publish and release inconsistently [09:23] but i don't know; there might be nuance [09:23] if you have a button with a verb on it i expect clicking it will do that verb [09:23] but it's definitely not "edit a channel"; it's editing a channel assignment, which seems to be called releasing [09:23] ali1234: as i say, please open a forum topic [09:23] unless you're just ranting, that is :-) [09:23] ranting is fine btw [09:24] i can rant on the forum if you want [09:24] ali1234: forum is for constructive, long-term engagement [09:24] well, long-term in internet time :-p [09:24] rants are fine here [09:24] okay. where do i go to just report a list of problems? [09:25] i am not interested in long term engagement. i will just come back in another 9 months and see if you have fixed all the problems [09:25] ali1234: the forum is fine to just report a list of problems [09:25] ali1234: (the 'long-term' side of that kind of post comes from the people going through the list and addressing them) [09:26] maybe a better term would be 'asynchronous' actually [09:27] vs irc that is synchronous [09:27] should i create one topic for each issue? [09:27] or just make one long rant post? [09:27] ali1234: just one long one is probably easier for you [09:27] ali1234: i believe moderators can then split it up [09:28] yeah but we both know they won't [09:28] dude [09:28] someone will come along and address one of the problems (probably by saying "that isn't in scope of the project") and then the rest will be ignored [09:28] that's what happened yesterday [09:28] ali1234: where? [09:29] https://forum.snapcraft.io/t/trying-to-build-sigrok-snap/503 [09:30] ali1234: that looks like the opposite [09:31] really? i was told to use launchpad, which addresses exactly one of the four problems i raised [09:31] it's not being ignored; you even got ev following up a day later [09:31] which was less than an hour ago [09:32] Chipaca, mind giving a second thumbs up on https://github.com/snapcore/core/pull/37 ? (trivial changes) [09:32] PR core#37: install keyring (LP: #1670475), update pkglists [09:33] * ogra_ hugs Chipaca [09:34] PR core#37 closed: install keyring (LP: #1670475), update pkglists [09:35] ali1234: about the snapcraft.yaml in the root of the repo, I *think* (but am not sure) that you can also make it .snapcraft.yaml, or snap/snapcraft.yaml [09:35] you can [09:35] upstream will put it at cross-compile/snap/snapcraft.yaml because that is how their repository is organized [09:36] Hi, I'm trying to create a snap of my app (https://github.com/tizonia/tizonia-openmax-il) and I'm currently facing problems with pulseaudio. The snap I've created installs correctly in Fedora 25 but it can't access pulseaudio (Access Denied)...is there any good reference or tuturial on how to create snaps that need access to pulseaudio? [09:36] juanrubio: is it using the pulseaudio interface? [09:36] Chipaca: we don't ahve any confinement on Fedora so the interface is useless unless its a seccomp issue [09:37] juanrubio: can you give us the exact error message? [09:37] yes, plugs section contains 'pulseaudio' [09:37] juanrubio: is the plug connected? [09:37] morphis: point [09:37] the error message is coming from my app [09:37] * Chipaca goes back to work [09:38] juanrubio: is there an error in dmesg or journalctl? [09:38] "Access denied" (which comes from pulseaudio's api) [09:38] i can't seen any errors in journalctl's output [09:39] juanrubio: and you're running your app with the same user you're logged into the system [09:39] morphis: i thought the plug would be automatically connected? [09:40] yes, same user [09:40] juanrubio: is it connected or not? [09:41] if I connect the plug with 'sudo snap connect tizonia:pulseaudio :pulseaudio' i get the same result [09:41] juanrubio: can you share the .yaml? [09:42] oh it's there in tools/snapcraft.yaml [09:42] yes, in tools [09:44] I created my snap in Ubuntu 16.04 and Fedora 25 runs on a Virtualbox VM [09:45] juanrubio: and does it work in ubuntu 16.04? [09:45] actually, I have not tried it in ubuntu [09:45] please do [09:46] ok, let me give it a try in an 16.04 VM i have over here [09:48] pstolowski: re [09:48] pstolowski: sorry, I was in a call [09:48] PR snapd#3282 opened: hooks: default timeout [09:49] pstolowski: so the problem is snapctl and golang's network stack that checks if you have ipv6 connectivity/support by creating that socket [09:49] pstolowski: as you know on ubuntu & linode we disable ipv6 (as there was some problem with routing, historically) [09:49] pstolowski: but I don't think we disable that on debian [09:49] pstolowski: we may thus hit a confinement issue where seccomp kills part of snapctl [09:50] pstolowski: I think in addition the actual hook, before it tries snapctl, checks something else which on ubuntu is blocked by apparmor [09:50] pstolowski: so when the plug (core-support-plug) is disconnected, the hook exits gracefully [09:52] juanrubio: hey [09:53] hi zyga, i've filed this bug https://bugs.launchpad.net/snappy/+bug/1689332 wrt the issue with the 2.25 ubuntu-core snap and the hardcoded snap-confine path [09:53] Bug #1689332: internal error with any command using ubuntu-core snap on classic [09:53] juanrubio: intersting, what is your snap doing with audio? just playback or something more? [09:53] fgimenez: thank you! I'll assign it to myself [09:54] zyga, my understanding - after looking at comments from jdstrand and later morphis - is that yes, it's ipv6 reatlated, Jamie recommended a specific policy rule. the problem was fixed but by mistake not included in the 2.24 release, but according to morhpis it's in the new release (https://forum.snapcraft.io/t/tests-broken-in-master/457/8?u=pstolowski) [09:54] morphis, https://github.com/snapcore/pi3-gadget/pull/6 [09:54] PR pi3-gadget#6: make pi-bluetooth name more generic [09:54] zyga: great thanks! :) do you think this issue should block the 2.25 sru? [09:54] pstolowski: I'm not sure I understand, what do you aim to achieve in the end? [09:54] Bug #1689332 changed: internal error with any command using ubuntu-core snap on classic [09:55] fgimenez: well, hard to say, it only affects people that are on ubuntu-core (not just core) [09:55] zyga, and i've just proposed a PR to have a default timeout in case we have a task created by old snapd with no timeout set [09:55] PR snapcraft#1288 closed: store: collaboration UI for snaps [09:55] zyga: audio playback [09:55] fgimenez: I think it is not so critical but perhaps my view is just too optimistic [09:56] zyga: ok thanks, we can talk later in the meeting [09:56] juanrubio: so fedora 25 may have a more recent version of pulseaudio than ubuntu 16.04 but I bet that pulseaudio still supports the older protocol [09:56] juanrubio: and even on fedora 26 I saw snaps play audio [09:57] juanrubio: could you please open a forum topic for this (on forum.snapcraft.io), perhaps other people are facing the same issue and even if not we can try to help you there [09:57] juanrubio: if your snap is public I could try it on my f26 machine [09:57] juanrubio: and try to debug it there [09:57] zyga: these are my first steps with snaps, so I'm sure I'm missing something [09:57] juanrubio: does it work on ubuntu? if so, it should work on fedora too [09:57] zyga: i think there's another issue with https://github.com/snapcore/snapd/pull/3218/files, i'm getting "Bad system call" trying to use systemd-cat from a snap, will file a bug about this too [09:57] PR snapd#3218: interfaces: allow writing to /run/systemd/journal/stdout by default [09:58] zyga: I'm currently updating a 16.04 VM that I have here. I will try it out in 16.04 in a few minutes [09:58] morphis, thx [09:58] ogra_: np [10:04] fgimenez: in lxc? [10:04] zyga: nope, on a regular classic vm [10:05] I'm opening a forum topic for this, which category 'snap' or 'snapcraft'? [10:08] hmm [10:08] fgimenez: what was the system call? do you have the error message? [10:08] juanrubio: snap please [10:08] zyga: sure, [ 910.074185] audit: type=1326 audit(1494320944.576:31): auid=1000 uid=12345 gid=12345 ses=1 pid=30704 comm="systemd-cat" exe="/usr/bin/systemd-cat" sig=31 arch=c000003e syscall=48 compat=0 ip=0x7fcdee899987 code=0x0 [10:09] fgimenez: 48 is "shutdown" [10:09] fgimenez: hmm, probably closing some socket [10:09] hm, did anyone run into this one with spread already: in test-snapd-tools.channels: extra keys: {'latest/candidate', 'latest/beta'} [10:09] fgimenez: where did that fail? was it a specifi test? [10:09] that is for tests/main/snap-info [10:09] morphis: yep on it [10:10] fgimenez: great! [10:10] morphis: nope, but Chipaca wrote that so I bet he groks he messages [10:10] where what? [10:10] * Chipaca reads up [10:10] Chipaca: https://travis-ci.org/snapcore/snapd/builds/230270742?utm_source=github_status&utm_medium=notification [10:11] zyga: not yet, i was adding it while reviewing the 2.25 changelog https://github.com/snapcore/snapd/compare/master...fgimenez:spread-interfaces-default?expand=1#diff-e2f8bc979b0f080a4b32db7b71057b46R9 [10:11] morphis: that looks like a snap/snapd version mismatch [10:12] as in, snapd sending track/channel, snap expecting channel [10:12] but let me look at it a moment [10:13] morphis: Chipaca probably related, i just uploaded an updated version of test-snapd-tools and the snap-info test started failing, reverted back to the previous version and keep failing [10:13] fgimenez: it might be that the test expects it to be only in certain channels [10:13] and you published it to more of them [10:13] it'd look like this, also [10:14] i.e. it used to only be in stable and edge, and now it's also in candidate and beta [10:14] Chipaca: i tried to keep the same channels, rev 3 was in stable, candidate and beta (as it is now) [10:15] Chipaca: aha, let me try to remove it from candidate and beta [10:16] so, yes, the snap-info test expects it only in stable and edge [10:16] morphis: found the problem :-) [10:16] ("channels", check, [10:16] ("latest/stable", matches, verRevNotesRx("-")), [10:16] ("latest/edge", matches, verRevNotesRx("-")), [10:16] ), [10:17] that will fail if the channels key has more entries than those two [10:18] actually, I said before that journalctl didn't show any messages, but actually i didn't realise that the older messages were at the top.. so yes I see a bunch of errors, not sure I understand much... what should I look for? [10:19] juanrubio: anything with 'audit' in it [10:19] juanrubio: can you paste those somewhere? [10:22] I've pasted some of it here: https://gist.github.com/juanrubio/d7ed44344ef2e7a659dede5f788d07f5 [10:22] PR snapd#3280 closed: configstate: return error if patch is invalid [10:23] permissive=0 is curious, [10:23] ogra_: remind me, how long does the prepare-device hook take on the bbb, worst case? [10:24] Chipaca, i havent tested in a while but it should not take long anymore [10:25] it used to be 10-15min in the wrst times [10:25] *worst [10:25] and this are the steps I'm following to install the snap on Fedora 25 : https://gist.github.com/juanrubio/4ca10f5a6468fc12bcbed6bf01a7d8f7 [10:25] Chipaca: now i begin to rant about the release page too :) do you know if i can unpublish a released revision from a channel somehow? [10:26] fgimenez: yes, you click on the channels and edit the map as you please [10:26] fgimenez, i dont think you can "unrelease" but you can release a former version [10:26] fgimenez: i think i should be able to do it [10:26] * Chipaca looks [10:26] PR snapd#3276 closed: tests: additional setup in docker test for core systems [10:26] juanrubio: why do you had to do $ mkdir -p ~/snap/tizonia/x1/.config/tizonia ? [10:27] iirc the store spills an error if you just try to unrelease [10:28] juanrubio: was that just because of ~/snap/tizonia/x1/.config missing or did even ~/snap/tizonia/x1/ not exist? [10:28] Chipaca: releasing a former version leaves the candidate and beta channels in snap-info's output http://paste.ubuntu.com/24542209/ not sure if the test would pass with this? [10:30] that looks like a bug [10:30] noise][: are you around? [10:30] morphis: my app needs this 'tizonia.conf' located in $HOME/.config/tizonia [10:30] fgimenez: i mean, what looks like a bug is the not being able to remove channels [10:30] juanrubio: so ~/snap/tizonia/x1/ was automatically created? [10:30] maybe it's always been this way but i thought not [10:31] so I currently copy this manually [10:31] ~/snap/tizonia/x1 is automatically create [10:31] ~/snap/tizonia/x1 is automatically created [10:31] ok [10:31] the idea of opening a channel, having a snap in it, and then closing it has existed forever [10:33] Chipaca: yep i think so, the message from the release page is clear though "Released channels cannot be removed." [10:35] Chipaca: this fixes the tests http://paste.ubuntu.com/24542214/ should i propose it? [10:35] right, thats the typüical message [10:37] fgimenez: if it can wait a bit, i'd rather first determine whether the store is broken in this way [10:37] or if it's how it should be, in which case yes let's fix the test [10:38] Chipaca: ok [10:38] Chipaca, it has always been like this (at least with the web UI) [10:38] fgimenez: if determining this takes more than an hour, let's fix the tests [10:39] the above is the message you get when unticking the channel checkbox ... but ticking it on an older version will override and release that version instead [10:39] Chipaca: ok sounds good [10:45] hmm something wrong with my snap. i now have both meta/gui and setup/gui [10:45] My 16.04 is taking a bit long to update. I've uploaded the snap package to this location, in case someone might want to give it a try on Fedora 25 or 26: http://www.juanrubio.me/tizonia/tizonia_0.7.0_amd64.snap [10:45] actually it looks like it dumped everything from the source repo into the snap [10:46] pstolowski: hey, I read https://github.com/snapcore/snapd/pull/3282/files and it looks OK but I recall you said it didn't work, do I remember that correctly? [10:46] PR snapd#3282: hooks: default timeout [10:50] zyga, I said that, yes, but later I figured out (correct me if I'm wrong) that the test I was using in qemu re-execs into new snapd from core image, so I wasn't really testing my change at that time [10:51] pstolowski: I think you were, because the "new" snapd was the one from the package [10:51] pstolowski: and the package is built [10:51] pstolowski: I mean we re-write the core snap [10:51] juanrubio: getting a 404 [10:52] juanrubio: ah now it worked [10:53] Chipaca: anyway, something strange has happened with test-snapd-tools, it seems that beta and candidate have been used since rev 1 http://paste.ubuntu.com/24542284/ (i actually checked the channels used by rev 3 before releasing rev 6, and those included candidate and beta), how was snap-info test passing before? [10:53] I've created a forum topic: https://forum.snapcraft.io/t/pulseaudio-access-denied-accessing-pulseaudio-for-audio-playback-in-fedora-25/519 [10:54] juanrubio: what do i do to run it? [10:54] * Chipaca knows nothing about tizonia [10:54] fgimenez: ¯\_(ツ)_/¯ [10:55] fgimenez: let's see what facu says [10:56] fgimenez, the pi2-kernel in edge is pretty outdated, i'll sync the newer one from beta into it (runs fine here, just FYI in case any tests start to misbehave in edge) [10:59] ogra_: ok thanks! i'll give it i try [11:00] zyga, hmm.. ok, i'm confused. i understand what you're saying, just not sure about my findings anymore. I could manually kill -9 the hanging configure script and this is what we do in hookmgr. [11:02] * Chipaca hugs Facu [11:02] juanrubio: the help output for tizonia talks about ~/.config/tizonia/tizonia.conf, which is wrong [11:02] pstolowski: I could try your branch and experiment [11:03] morphis, hmm, who owns the wifi-ap snap ? seems i cant run the setup wizard anymore ... http://paste.ubuntu.com/24542320/ [11:03] Chipaca: I was using it with my Spotify account, but the pulseaudio problem should be seen while trying to play a local mp3 file [11:03] Chipaca: why do you say the help output is wrong? [11:04] ogra_: we do [11:04] juanrubio: because a snap won't be able to read ~/.config/tizonia/tizonia.conf [11:04] /find nikc "we" [11:04] *nick [11:04] :P [11:04] juanrubio: apps usually set XDG_CONFIG_DIR (or whatever it was) to something inside ~/snap/ [11:04] ogra_: you ping'ed the right one :-) [11:04] zyga, feel free to if you have a few moments [11:04] ogra_: which syscalls are denied? [11:04] morphis, werll, seems "socket" [11:05] Chipaca: right now I am only concerned about making it work on Fedora as a test, will deal with those other things later [11:05] ogra_: are all plugs connected? [11:05]