[04:00] <Peddy> persia, are you there?
[04:03] <persia> My apologies.  I have poor diurnal habits.  Had you also installed libpulse-dev ?
[04:03] <Peddy> no problem :)
[04:05] <Peddy> ok, I''ve install libpulse dev 0.9.13, thing is, I can't log in without failsafe GNOME (I get an error saying "couldn't exec /usr/bin/pulse-session; no such file or directory), but with failsafe gnome I can log in. My question is, can I debuild openjdk with the 0.9.13 dev libs installed, and then revert back to 0.9.10?
[04:05] <Peddy> I've purged and reinstalled pulse etc.
[04:06] <persia> You can, but openjdk will be linked against a different version of pulse than you have installed, which may cause runtime errors.
[04:07] <persia> Depending on how the library packaging is set up, it may also cause issues with dependencies.
[04:07] <Peddy> Hm. Do you know how I could fix the current PA install, then?
[04:07] <persia> How do you mean "fix" and "current"?
[04:08] <Peddy> Fix it so that I pulse works, and by current I mean the version I have installed, which is 0.9.13 from themuso
[04:08] <Peddy> 's PPA.
[04:09] <persia> OK.  You'd have to track down why pulse is causing the GNOME session to crash, and fix that bug.
[04:09] <Peddy> Well, I have an idea.
[04:10] <persia> Then you're off to a good start :)
[04:11] <Peddy> At the end of the first post (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/294541) it says [pulse-access] is no longer needed, because pulseaudio is being started by a different mechanism.
[04:11] <Peddy> is 0.9.13 the version that's in Jaunty?
[04:11] <persia> Try running `rmadison pulseaudio`
[04:14] <Peddy> aha, Jaunty has 0.9.14. Are there significant changes in PA that would make it a bad idea to install the Jaunty version in Intrepid?
[04:14] <persia> I think that the solution of that bug is related to also having a newer libcanberra.  You can try ithe suggested solution, but I don't know how well it would work.
[04:15] <persia> It's almost never a good idea to install a version compiled for one release on another release.  The most common exceptional case is in the other direction (e.g. sometimes you can install things compiled for intrepid on jaunty).
[04:16] <Peddy> Ok.
[04:16] <persia> That said, you could try to see if the 0.9.14 version also compiles on intrepid (a backport), but I suspect it depends on the newer libcanberra, and you'd end up in fairly deep recursion.
[04:17] <Peddy> well, openjdk is actually still debuilding (it's been going for a long time now), after it's done have a look at the backport.
[04:17] <Peddy> if it doesn't work :/
[04:18] <persia> I'm tempted to think the answer to your original questions "Can Java use pulse for audio in intrepid" is "No", and that you'd be engaged in a long and arduous path to make it work if the current attempt fails.
[04:19] <persia> You'd probably do better to either work on something else, or, if you can, consider testing jaunty: if it doesn't work there, you can file bugs, and your patches and solutions may be applied to be part of Ubuntu.
[04:19] <Peddy> Well, themuso's 0.9.13 backport is supposed to work for Intrepid, and that's all the latest openjdk depends on, isn't it?
[04:20] <Peddy> How stable are people saying the Jaunty alpha is?
[04:20] <persia> Well, yes, but.
[04:21] <persia> You could ask in #ubuntu+1, but generally speaking, every development release is fairly unstable: remember that things are changing all the time.
[04:24]  * Peddy is still waiting for openjdk to debuild.
[04:37] <Peddy> persia, I assume you have Pulseaudio and Ubuntu, could I please have a look at your /usr/bin/pulse-session file?
[04:38] <persia> http://pastebin.ubuntu.com/109657/
[04:38] <persia> I think there's a typo in it :)
[04:39] <Peddy> hehe
[04:39] <Peddy> We should file a bug.
[04:39] <Peddy> bug report*
[04:41] <Peddy> after it's done debuilding, what should I do?
[04:44] <persia> You should end up with a .deb.  You can install this, and see if it works.
[04:46] <Peddy> I execute 'debuild' in the openjdk-6-6b12 directory, correct? It's been going for about 15 minutes now.
[04:48] <persia> Right.
[04:49] <persia> For more advanced usage, you'd execute `debuild -S` and then use something like pbuilder or sbuild to build it, but as long as you're only planning to use the result on your local system, just `debuild` is safe.
[05:08] <Peddy> persia, is debuild meant to just build a deb, or run tests or something? because it started a process called 'java', and it's still running.
[05:09] <persia> It does everything considered important to create a .deb.  For things like the Java runtime environment, this involves running a number of tests to make sure it isn't broken beforehand (as otherwise it might be hard to get it built again)
[05:14] <Peddy> aha, I thought so, because checkinstall makes a deb, and it only takes a few seconds :D
[05:14] <persia> checkinstall doesn't make a very reliable deb.
[05:18] <persia> But really, the normal process can also be fast, when it's not being so careful.
[05:18] <persia> In this case, it's extra-careful, because a bug in Java is a bug in *lots* of packages.
[05:23] <Peddy> when I download source code, can I use debuild instead of checkinstall (or make install, for that matter)?
[05:24] <persia> Yes, but you'd have to prepare the debian/ directory.
[05:24] <persia> !packaging
[05:25] <persia> The guide doesn't cover a lot of Java stuff, but it at least introduces many of the concepts.
[05:25] <persia> If you do package something, and it's working, it's best to try to get it into the repositories, so nobody else has to package the same thing.
[05:26] <persia> And, of course, if you get the source with apt-get source (for which you *don't* need sudo), it comes already packaged.
[05:28] <Peddy> awesome, thanks.
[06:07] <InHisName> Please install build and header for Kernel     - 2.6.24-21-generic    what apt-get do I do ?
[06:09] <Peddy> InHisName, sudo apt-get install linux-headers-2.6.24-21-generic
[06:10] <Peddy> persia, it's still running. Do these things usually take this long?
[06:12] <persia> https://launchpad.net/ubuntu/+source/openjdk-6/6b12-0ubuntu6/+build/748817 should give a guideline for expectations.
[06:12] <persia> I've had builds that finished in a few seconds, and ones that took 15 hours.
[06:13] <Peddy> excellent, thanks.
[08:22] <Peddy> persia, it just finished! :D
[08:37] <Peddy> persia, it finished debuilding and installing, and I fixed the pulseaudio problem, but the java app playing through openjdk's javaws does not play sound through pulseaudio. Am I doing something wrong?
[08:41] <Peddy> I'll be right back, rebooting for good measure.
[09:22] <Peddyt> persia, I'm now getting this from the Java programs: JavaSoundPlayer: mixer not found: Intel [plughw:0,0]. I'd really appreciate some help.
[09:33] <persia> Peddyt, My apologies, but I'm not sure how to debug that.
[09:56] <persia> That does look like an ALSA error though: are other applications working as expected with pulseaudio?
[12:52] <tvgv_> hello lucid
[17:54] <FuriousGeorge> hey all
[17:54] <FuriousGeorge> any way to get sun-java-1.6.10 on 8.0.4?
[21:44] <c00ldIcE> Hello, I'm searching for a code example which parde checkip.dyndns.org or print my IP
[21:44] <c00ldIcE> Can anyone help me?


[01:44] <dax> !20.04 is <reply> Ubuntu 20.04 (Focal Fossa) will be the 32nd release of Ubuntu, scheduled for April 2020 ( https://wiki.ubuntu.com/FocalFossa/ReleaseSchedule ). It will be a long-term support release. Join #ubuntu+1 for support and questions.
[01:44] <dax> !focal is <alias> 20.04
[01:44] <dax> !fossa is <alias> 20.04
[02:39] <valorie> woah, already named?
[02:39] <Unit193> Yeah!
[02:39] <Unit193> ...Can I upload there yet? :3
[02:41] <valorie> lol
[03:13] <el> hello i have the new bunty why is nothing different
[03:22] <valorie> lol
[04:48] <dax> el: because the bunty broke
[04:49] <el> bunty always does this but not arch why can't bunty be like arch i guess i'll hve to uninstall it now.
[04:49] <dax> install gentoo tbh
[04:49] <el> you're losing a valuable customer
[04:57] <valorie> it is getting colder here, so gen2 is an idea.....
[05:19] <el> one of these days they'll eventually make it to genthree
[08:42] <jussi> Morning all :)
[17:28] <dax> ubottu: no, isitout is <reply> It's out! Grab your party hats and cake at #ubuntu-release-party, and see ubuntu.com or your favorite flavor website for download links :)
[17:30] <dax> ubottu: no, 19.10 is <reply> Ubuntu 19.10 (Eoan Ermine) is the 31st release of Ubuntu, supported until July 2020. Release notes: https://wiki.ubuntu.com/EoanErmine/ReleaseNotes
[17:34] <dax> Pici, Unit193, other people I forgot: https://lists.ubuntu.com/archives/ubuntu-announce/2019-October/000250.html bot codename variable update time!
[17:34] <dax> !20.04
[18:01] <Pici> have a boring meeting now, a perfect time to update some factoid variables
[18:03] <Pici> well that went faster than I expected.  Now I need to pay attention to this call.
[18:07] <dax> Pici: thank you! did you handle the variables on your ubot clones too?
[18:07] <Pici> dax: er.. no. maybe thats why it felt like it took less time than normal.
[18:08] <dax> hehe


[11:07] <facubatista> ¡Muy buenos días a todos!
[11:17] <bthomas> Morning facubatista
[11:18] <facubatista> hola bthomas
[11:19] <bthomas> Looks like there is no easy way to debug charms on microk8s. juju debug-log does not show logging messages from the charm because even the smallest update interval of 1min is to slow to capture the logs. Any of the other means debug-hooks, debug-code etc are not supported on k8s.
[11:20] <bthomas> facubatista: if you have some time for a 1:1 anytime I will be much obliged.
[11:21] <facubatista> bthomas, in ~10' it's fine
[11:22] <bthomas> facubatista: awesome thank you ping me when you are ready
[11:33]  * facubatista could use a review on this dead simple branch https://github.com/canonical/charmcraft/pull/133
[11:33] <mup> PR charmcraft#133: Added a note in the release howto about sending a mail when done <Created by facundobatista> <https://github.com/canonical/charmcraft/pull/133>
[11:34]  * bthomas looking at https://github.com/canonical/charmcraft/pull/133
[11:36] <facubatista> bthomas, anytime now, I'm in https://meet.google.com/fqw-mdqc-dsf
[11:36] <bthomas> facubatista: going now
[11:59] <facubatista> bthomas, join #juju
[12:55] <moon127> hey all, I've added charmcrafters as a reviewer on the MP for unifi-poller charm being written in IS - https://code.launchpad.net/~moon127/charm-k8s-unifi-poller/+git/charm-k8s-unifi-poller/+merge/389643
[13:10] <facubatista> moon127, ack, thanks
[13:22] <justinclark> bthomas, I'm not sure about microk8s, but I can do juju ssh into units in a charmed-kubernetes bundle (the machines are LXD). Could you maybe juju deploy kubernetes-core and then deploy charms to that bundle?
[13:23] <justinclark> Not sure if that'll work, but just offering suggestions.
[13:28] <facubatista> another easy small PR for review, thanks! https://github.com/canonical/charmcraft/pull/134
[13:28] <mup> PR charmcraft#134: Use original permissions when creating a dir at building time <Created by facundobatista> <https://github.com/canonical/charmcraft/pull/134>
[13:41] <justinclark> I'll take a look now facubatista
[13:42] <facubatista> thanks
[14:02] <justinclark> I have a (potentially noob) question: When looking at the docs, I see that leader units can set application data [1], but the only way I've found to set application data is through a relation. So my question: is there a way to access the application data directly rather than through a relation?
[14:02] <justinclark> [1] https://ops.readthedocs.io/en/latest/index.html#ops.model.RelationData
[14:03] <bthomas> justinclark: thank. Will look into charmed kubernetes
[14:03] <justinclark> bthomas: just a heads up - it's pretty resource intensive. You might have better luck with kubernetes-core bundle.
[14:03] <bthomas> got it
[14:06] <justinclark> Context for my question: when a relation_changed hook fires, I want to save some data that comes through that relation (host and port) to the main application's data.
[14:08] <justinclark> I currently have a silly looking line like this: event.relation.data[self.app]['data-sources'][event.relation.id] = {...}
[14:10] <justinclark> I think it would be much nicer to access app data directly but I don't know if that even makes sense in the context of Juju / operator framework.
[14:10] <bthomas> I am looking at those docs myself and can see "They are allowed to read remote unit and application data." But it does not elaborate.
[14:10] <bthomas> "They" reffers to units.
[14:28] <facubatista> justinclark, what happens if you do ...
[14:28] <facubatista> relation_data = event.relation.data[self.unit]
[14:28] <facubatista> relation_data[somekey] = somevalue
[14:28] <facubatista> ?
[14:28] <justinclark> Yeah that would clean things up. Let me try something like that.
[14:30] <justinclark> facubatista, Is there a rule of thumb for what kind of data should be stored at the unit level vs. application level?
[14:30] <justinclark> (Again, probably showing my newness to charming)
[14:32] <facubatista> IIUC you set the information to the application at the other end of the relation
[14:33] <facubatista> not the unit
[14:33] <facubatista> that `[self.unit]` I'm doing above is because you have the data for the apps in both units
[14:39] <justinclark> So if my Grafana charm accepts a Prometheus relation, setting event.relation.data[self.app] would set prometheus app data rather than Grafana app data?
[14:43] <justinclark> Okay, so I think what I actually need is to store the data in the charm's StoredState: https://ops.readthedocs.io/en/latest/index.html#ops.framework.StoredState
[14:43] <justinclark> Basically, I'm just trying to make Grafana data source information (host/port/etc.) easily accessible.
[15:27] <facubatista> justinclark, yes, you can store stuff in the charm's StoredState (btw, you should call that "store", not "state", as we want to get away of tha misnaming: it's a general store, not the "state of the charm")
[15:31] <facubatista> another easy PR: https://github.com/canonical/charmcraft/pull/135
[15:31] <mup> PR charmcraft#135: Support the global options also after the command is given <Created by facundobatista> <https://github.com/canonical/charmcraft/pull/135>
[17:08] <facubatista> mthaddon, just took a look at the charm-k8s-gunicorn MP, added some comments
[17:45] <crodriguez__> Does anyone know if it is possible to define the metadata in pod_spec_set for a role ? I want to turn this into a pod_spec, and the metadata field is not recognized with the way I do it https://pastebin.canonical.com/p/zQSXfQGnkq/
[17:49] <crodriguez__> I get this https://pastebin.canonical.com/p/RYXNzDW6z6/
[17:59] <mup> Issue operator#390 opened: Only one role allowed <Created by camille-rodriguez> <https://github.com/canonical/operator/issues/390>
[18:02] <crodriguez__> I opened that bug in case you can do something about it in the framework itself. Idk if it is more juju than ops though
[21:28]  * facubatista eods
[21:28] <facubatista> and eows
[21:28] <facubatista> see you all on Monday


[14:57] <Guest21943> hey, I was wondering if I could obtain a copy of precise to test installation, since I'm going to reinstall anyway. is that possible?


[01:11] <jaggz> You guys still need people with the frozen step: "[-] Run configure hook of "core" snap if present" ?
[01:11] <jaggz> mine's doing it..
[01:13] <jaggz> fresh install in Debian-stretch of snapd, snap install meshlab (not sure how to install my meshlab-201612.snap file directly yet) and it installed core and is sitting there on the rotating progress of that line
[08:39] <zyga-ubuntu> jaggz: hey
[08:39] <zyga-ubuntu> jaggz: which version of snapd is that? (on that fresh install)
[08:54] <jaggz> zyga-ubuntu, 2.21-2+b1
[08:55] <zyga-ubuntu> jaggz: and can you run "snap version" now please
[08:56] <jaggz> snap    2.21-2+b1
[08:56] <jaggz> snapd   2.24
[08:56] <jaggz> series  16
[08:56] <jaggz> debian  9
[08:56] <jaggz> zyga-ubuntu
[08:57] <zyga-ubuntu> jaggz: interesting
[08:57] <zyga-ubuntu> jaggz: is the configure hook still running?
[08:58] <jaggz> Mm. I think i eventually killed it
[08:58] <zyga-ubuntu> jaggz: you can continue if you kill "snapctl" process that you may have
[08:58] <zyga-ubuntu> jaggz: right, what does "snap list" say about core now?
[08:59] <jaggz> It's my first time using snap btw.. first day seeing it! :)
[08:59] <zyga-ubuntu> I'm sorry for the bumpy experience
[08:59] <jaggz> No snaps installed, it says
[08:59] <jaggz> Aw, thanks. :)
[09:00] <zyga-ubuntu> yeah, it reverted when the configure hook failed
[09:00]  * zyga-ubuntu thinks
[09:02] <zyga-ubuntu> not sure really
[09:02] <zyga-ubuntu> you can perhaps try this
[09:02] <zyga-ubuntu> sudo snap install core --beta
[09:02] <zyga-ubuntu> I mean this bug was fixed but releases to debian are harder so the version in the distribution is older
[09:04] <jaggz> It's working on it :)
[09:07] <jaggz> It went in..
[09:07] <jaggz> I didn't try the original non-beta twice, btw
[09:08] <zyga-suse> great
[09:09] <zyga-suse> jaggz: so once you have the core installed
[09:09] <zyga-suse> jaggz: you can try installing other things
[09:09] <jaggz> Yeah installing meshlab now
[09:10] <jaggz> Not from the .snap i think though.. just did snap install meshlab
[09:11] <jaggz> Now to learn where snap puts these things
[09:13] <zyga-suse> jaggz: what do you want to know specifically?
[09:13] <zyga-suse> jaggz: where it stores your data? the code?
[09:13] <jaggz> Found the path.. /snap/
[09:15] <jaggz> The snap is a binary distribution, not source, right? I didn't notice a compilation, and the .snap download file i found on the web was amd64
[09:20] <zyga-suse> yes
[09:21] <zyga-suse> jaggz: we are working on adding meta-data so that snaps that are FOSS can declare where the source is and how to build it
[09:23] <jaggz> Nice
[09:23] <jaggz> It's an awesome project
[09:24] <jaggz> About time too
[09:27] <zyga-suse> :-)
[09:27] <zyga-suse> Thank you for using Debian
[09:28] <jaggz> Lol
[09:28]  * zyga-suse uses fedora, suse and ubuntu all the time but I don't have a debian machine to get the real experience
[09:40] <jaggz> Strictly Debian for years now for me
[09:41] <jaggz> Except one Ubuntu server
[09:47]  * zyga-suse cannot wait for debian 10 when we'll finally have snap confinement in place
[09:56] <jaggz> Guess I should read up on it more
[09:57] <jaggz> To know what your talking about :)
[10:28]  * zyga-suse returns to packing his life into boxes
[13:13] <Chipaca> jdstrand: “snap install --edge test-snapd-service-notify” for your consideration


[00:11] <snapresearch> HI, I have a quick question - how to integrate openvpn (client) into a snap?
[08:25] <shadeslayer> hey!
[09:29] <flux242> Hi, What does this mean?$ sudo snap refresherror: cannot refresh []: Post https://search.apps.ubuntu.com/api/v1/snaps/metadata: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
[10:09] <Chipaca> the package index is timing out; I've contacted IS.
[10:50] <mup> PR core#37 opened: install keyring (LP: #1670475), update pkglists <Created by ogra1> <https://github.com/snapcore/core/pull/37>
[10:55] <mup> PR core-build#10 opened: make /etc/environment writable <Created by ogra1> <https://github.com/snapcore/core-build/pull/10>
[11:00] <Chipaca> ogra_: will that work with atomic writes?
[11:00] <ogra_> Chipaca, no
[11:01] <Chipaca> ogra_: what needs doing so it does?
[11:01] <ogra_> like any ontgher single file we make writable like this
[11:01] <ogra_> unionfs ... aufs, overlayfs ?
[11:01] <Chipaca> ogra_: so this bind-mounts instead of being a symlink?
[11:01] <ogra_> yes
[11:01] <Chipaca> ogra_: how do you say "make it a symlink"?
[11:01] <Chipaca> NicolinoCuralli: you're making me wish i disabled join/part notifications
[11:02] <ogra_> you create a file in /etc/writable and link to it ...
[11:02] <ogra_> problem is ...
[11:02] <Chipaca> ogra_: any reason not to do that?
[11:02] <ogra_>  /etc/environment is hardcoded in half the world ... so that wont work here
[11:02] <Chipaca> why?
[11:02] <Chipaca> they won't follow a symlink?
[11:02] <ogra_> because i highly dbout anything reading it follows symlinks
[11:03] <ogra_> we could try ... but i really doubt it
[11:03] <Chipaca> people have to do extra work to not follow symlinks
[11:05] <ogra_> why is atomic so important for you ? we wont allow more than a proxy setting ... writing to a tmp file and mv is close to atomic
[11:05] <ogra_> it isnt like we could make the system unbootable or something if that fails
[11:06] <ogra_> (and i will surely fight adding other random stuff to that file that might make it break the boot)
[11:07] <Chipaca> ogra_: because if we don't, the file will get corrupted (most likely being zero'd out)
[11:07] <ogra_> how ?
[11:07] <ogra_> we dont open it
[11:08] <ogra_> you cp it to /tmp ... change the file in tmp and then you mv ...
[11:08] <Chipaca> ogra_: /tmp is a different filesystem, so mv is a cp, is an open and write
[11:08] <ogra_> (you could add an additional check between editing and mv if that makes you feel safer)
[11:09] <ogra_> well, then /var/tmp or whatnot ... you knwo waht i mean :)
[11:09] <Chipaca> _as far as i know_ (but we can test if you want) they're all different filesystems as far as rename is concerned
[11:09] <Chipaca> i mean, try it with python, easy enough to do
[11:10] <ogra_> well, i dont really want to add all the problems we have with /etc/writable to that file
[11:10] <ogra_> then i'll rather keep it readonly and have whatever adds the proxy add it differently
[11:11] <Chipaca> ogra_: every time we come to this area I'm closer to thinking we need to reverse the logic
[11:11] <Chipaca> ogra_: and make /etc writable except for <these things>
[11:12] <ogra_> Chipaca, we need to change it ... weather it is by reversing the logic, i dont know .... it was on the "to discuss" list for the sprint ... lets see what came out of it
[11:12] <Chipaca> ok
[11:13] <ogra_> /etc/writable is an ugly wart
[11:13] <Chipaca> lower your voice! don't want it to hear and throw a hissy fit
[11:13] <ogra_> lol
[11:30] <jfcastroluis> is snap store down?
[11:34] <jfcastroluis> I can't install snaps
[11:35] <jfcastroluis> Client.Timeout exceeded while awaiting headers
[11:35] <jfcastroluis> network is working ok
[11:35] <jfcastroluis> maybe the server?
[11:35] <jfcastroluis> anybody with problems also?
[11:45] <Chipaca> jfcastroluis: yes, the store is down, people are working on it
[11:47] <jfcastroluis> Chipaca: ok, thank you! :)
[11:47] <jfcastroluis> where is hosted snap store? aws?
[11:48] <Chipaca> jfcastroluis: I think it's in one of canonical's DCs
[11:49] <jfcastroluis> how you know is down? is there a status page? for next times (hope not many :)
[11:51] <Chipaca> jfcastroluis: I know the URL to the store?
[11:52] <Chipaca> and it times out
[11:52] <jfcastroluis> ok, ok! :)
[15:09] <sciencefyll> hellu
[15:09] <sciencefyll> i hear du guys liked feedback
[15:09] <sciencefyll> so i just wanted to say that on my fresh manjaro xfce install, it hangs right after you install it
[15:10] <sciencefyll> i've run both systemctl start/enable snapd.socket and systemctl start/enable snapd.refresh.timer
[15:10] <sciencefyll> running "sudo snap install discord" makes it hang at "[-] Run configure hook of "core" snap if present"
[15:12] <sciencefyll> force stopping it, and running it a second time gives the issue:
[15:12] <sciencefyll> "INFO snap "core" has bad plugs or slots: core-support-plug (unknown interface)"
[15:13] <sciencefyll> is this chat dead? xD
[15:17] <ogra_> sciencefyll, you are better off to post to the forum onn weekends (see the channel topic)
[18:06] <mup> PR snapcraft#1300 opened: tools: add a script to install autopkgtest dependencies <Created by elopio> <https://github.com/snapcore/snapcraft/pull/1300>
[18:46] <ali1234> hi. i made a sigrok snap ages ago but it never worked outside dev mode because it needs raw usb access. should i just make it use classic mode and put it in the store?
[18:46] <ali1234> and does anyone want to help me clean it up and do that?
[18:47] <ali1234> its here: https://github.com/ali1234/mysnaps/tree/master/sigrok
[18:47] <ali1234> upstream showed interest in it too
[18:50] <ali1234> oh there's a raw-usb interface now
[19:13] <ali1234> i built my snap to use the raw-usb interface and connected it but i still get "sr: backend: libusb_init() returned LIBUSB_ERROR_OTHER."
[19:13] <ali1234> type=1400 audit(1494097705.817:107): apparmor="DENIED" operation="create" profile="snap.sigrok.sigrok-cli" pid=8274 comm="sigrok-cli" family="netlink" sock_type="raw" protocol=15 requested_mask="create" denied_mask="create"
[19:21] <mup> PR snapcraft#1301 opened: recording: record global build-packages installed on the host <Created by elopio> <https://github.com/snapcore/snapcraft/pull/1301>
[19:26] <ali1234> it still works in devmode
[19:42] <fgfgffgfhfghsgh> ok
[19:43] <fgfgffgfhfghsgh> now, please tell me
[19:55] <ali1234> qt5 apps aren't themed correctly, not even in the store
[19:56] <ali1234> also "snapcraft cleanbuild" still fails: HTTPSConnectionPool(host='parts.snapcraft.io', port=443): Max retries exceeded with url: /v1/parts.yaml (Caused by NewConnectionError('<requests.packages.urllib3.connection.VerifiedHTTPSConnection object at 0x7fe2d6334898>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution',))


[05:43] <chelz> the topic in #ubuntu-server probably could do with some updating. still seems to refer to 10.04 server guide, and seems to make it seem like 12.04 isn't out yet
[06:43] <Tm_T> chelz: good now?
[06:44] <chelz> Tm_T: yep! :)
[10:16] <czajkowski> aloha, I was wondering if I could get a bot in #maas please ?
[10:16] <czajkowski> AlanBell: ^^^
[10:16] <AlanBell> hi czajkowski
[10:17] <czajkowski> AlanBell: can you make that happen or where do we need to request it
[10:17] <AlanBell> External, but Ubuntu related, IRC channel would be a job for ubot5
[10:18] <czajkowski> AlanBell: thanks
[10:18] <AlanBell> no problem
[21:16] <ButterflyOfFire> Hello :) is there any commands to use with lubotu3 such as !help for example ?
[21:17] <ButterflyOfFire> I didn't find any tuto on Ubuntu Wiki
[21:18] <Unit193> You have the package plugin, and factoids.
[21:20] <ButterflyOfFire> Could we add factoids to it Unit193 ?
[21:20] <Unit193> You can request them, they'll be forwarded to here so someone can decide if it's useful/correct/current
[21:21] <IdleOne> !lubotu3
[21:21] <IdleOne> !bot
[21:21] <IdleOne> ButterflyOfFire: http://ubottu.com/devel/wiki/Plugins
[21:22] <ButterflyOfFire> Merci ;)
[21:22] <IdleOne> De rien.
[21:25] <ButterflyOfFire> Okay, I'm starting to understand how it works. So we need, perhaps, to host our own Suppybot to give support/help in other languages such as arabic or berber for our LoCo rather then english ? Something like ubot-fr ?
[21:38] <ButterflyOfFire> !test
[21:39] <ButterflyOfFire> Humm okay okay
[22:26] <IdleOne> Would be really nice if there was a LP translation way of doing the ubottu factoids
[22:28] <ButterflyOfFire> yep
[22:30] <ButterflyOfFire> But some factoids are specific such as symbol ! followed by ops
[22:39] <ButterflyOfFire> Have a good night
[23:10] <JoseeAntonioR> Hello! Is anyone from the IRC Council available?
[23:20] <Pici> JoseeAntonioR: Yes, whats up?
[23:21] <JoseeAntonioR> Pici: Hey, I need +voOtif flags for ubuntu-co-bot in #ubuntu-co-meeting, ubuntu-co-bot is Ubuntu-CO's new meetingbot.
[23:21] <JoseeAntonioR> Actually, the person in charge of the flags is not available, and I need to test everything's working fine for the meetings
[23:22] <Pici> JoseeAntonioR: it needs +f?
[23:22] <nhandler> I was wondering the same thing. And +i ?
[23:23] <JoseeAntonioR> Pici: yes, +f to modify flags for adding bans and so on, and +i for inviting people for the meetings
[23:24] <Pici> JoseeAntonioR: +f is not needed to add normal bans.
[23:24] <Pici> Only if you were adding akicks, which is a fairly rare thing to need to do.
[23:24] <JoseeAntonioR> Pici: don't bans work by adding the +b flag to the user?
[23:24] <JoseeAntonioR> then, if it's not needed, no +f
[23:25] <Pici> You should use using the +b mode to ban people. the +b flag is something different, and not normally needed.
[23:26] <JoseeAntonioR> ok, then it's fine :)
[23:26] <JoseeAntonioR> I use @ban add username in the bot, that's why I was asking
[23:27] <benonsoftware> JoseeAntonioR: The bot does /mode +b nick then, which doesn't add the +b flag to ChanServ access list nor does it need +f to do it
[23:27] <Pici> 19:26:56 [freenode] -ChanServ(ChanServ@services.)- Flags +voOtiA were set on ubuntu-co-bot in #ubuntu-co-meeting.
[23:27] <JoseeAntonioR> Pici: great, thanks!