[04:19] <DarinMiller> any chance I can help package Remmina 1.2 in the Zesty release cycle?  I do not know much about packaging I usually only have time to learn on weekends.  But if someone wil guide me I will be happy to do the work.
[04:43] <jbicha> DarinMiller: I believe you'd need a newer freerdp first
[04:47] <jbicha> ooh, it's in Debian's new queue https://bugs.debian.org/814676
[04:48] <Son_Goku> it's not going to happen unless Debian is okay with breaking a few other packages
[04:48] <Son_Goku> we had to make a rather difficult choice in Fedora and actually break guacamole because Remmina needs FreeRDP 2.0
[04:49] <jbicha> Son_Goku: it looks like Debian is packaging it as 'freerdp2' in experimental
[04:50] <Son_Goku> ah yes, because upstream finally made the paths not conflict
[04:50] <Son_Goku> it's not in experimental yet, though
[07:18] <pitti> Good morning
[07:19] <pitti> mapreri: maintaining Testsuite-Triggers manually sounds fine -- dpkg just provides a  sane default
[07:19] <pitti> tsimonq2: 1647031> ah, thanks
[07:38] <cpaelzer> good morning pitti
[07:39] <pitti> hey cpaelzer, wie gehts? gut heimgekommen?
[07:39] <cpaelzer> pitti: a while ago you had good feedback on the sru review of bug 1546674
[07:39] <cpaelzer> pitti: the new version of the fix is in zesty and now waiting since 11 days for SRU - re-review - not sure how the process works to pick it up again - so *ping*
[07:39] <cpaelzer> pitti: ja war ja der einfachste Flug für mich (direkt)
[07:40] <cpaelzer> pitti: 30 Minuten parkhaussucherei, aber im Verhältnis zu den meisten Kollegen ist das ja nichts
[07:41] <pitti> cpaelzer: ah, will review
[07:41] <cpaelzer> pitti: thank you
[07:41] <pitti> cpaelzer: indeed, this now looks so much better
[07:43] <cpaelzer> pitti: was your way back smooth as well - or any travel-hickups on the way?
[07:44] <pitti> cpaelzer: no, all worked fine, just took a long time due to 4:30h layover in Madrid
[07:44] <pitti> but it was fine -- I hacked on apport, and almost forgot the time :)
[07:44] <pitti> had to run to my gate and was the last one to go through
[07:44] <cpaelzer> pitti: according to the messages I got US was a bit haunted by some storms and due to that delayed and cancelled connections - so in this case - happy EU trips
[07:44] <pitti> \o/
[07:45] <cpaelzer> pitti: work 'til you'll be left behind :-)
[08:51] <caribou> pitti: let me know if you want me to run stuff on my laptop for LP: #1647031
[09:26] <pitti> caribou: are you sure you have the exact same problem? this bug has become a mush of "me toos" where everyone experiences something different
[09:26] <pitti> caribou: like, Anders' bug is that he does not have systemd-resolved.service actually running (apparently)
[09:27] <pitti> (will follow up on that shortly)
[09:32] <caribou> pitti: I can de-dup my previous bug if you prefer
[09:35] <pitti> caribou: yeah, might be better as long as it's unclera
[09:57] <ginggs> pitti: do you know if there is a size limitation on autopkgtest artifacts?
[09:57] <pitti> ginggs: not a technical one, but be reasonable; don't have tests spit out multi-megabyte artifacts all the time
[09:58] <ginggs> pitti: ack
[10:49] <bigon> are there plans to push libsnap-glib in debian?
[12:02] <xnox> bigon, maybe willcooke can answer that.
[12:04] <willcooke> bigon, no concrete plan of action more than "we should" at the moment.  Once it's settled down and matured a bit I think we'll do it then
[12:05] <bigon> I had to disable the snap plugin in my last gnome-software upload in debian
[12:05] <willcooke> bigon, best person to speak to is robert_ancell, you want his email address?
[12:06] <bigon> I have his address somewhere :)
[12:09] <willcooke> bigon, I might speak to him tonight, so I will find out for sure and let you know, but yeah, do direct to him if you like
[12:43] <kmadac> Hello guys, I'm new to Ubuntu contribution. I found a bug in package isc-dhcp-client and I would like to propose a fix. I  have read Ubuntu contribution guides, but I'm stucked in pulling sources from bazzar. I'm getting error Not a branch: "bzr+ssh://bazaar.launchpad.net/+branch/ubuntu/isc-dhcp-client/". Any ideas what i'm doing wrong?
[12:45] <Bluefoxicy> when is cmiller waking up :|
[13:06] <sladen> kmadac: ideally first file a bug report saying what the but is, and how to reproduce it (ie. show that the bug exists)
[13:06] <sladen> kmadac: then attach the fix as a diff to the bug report (so it doesn't get lost, and is findable by Google)
[13:07] <sladen> kmadac: then propose the fix, showing that when trying to reproduce the bug using the original instruction, it is no longer possible
[13:10] <kmadac> sladen: thanks for answer. What do you mean by propose the fix? Diff is the fix, isn't it?
[13:10] <sladen> kmadac: the diff/patch is how implementation of the proposed fix
[13:11] <sladen> kmadac: eg. the diff to apply the fix against different versions of the same software will often be slightly different, (eg. changes in line numbers)
[13:12] <kmadac> sladen: great, should I then wait till someone from ubuntu devs implement the fix?
[13:13] <kmadac> sladen: or can I send pull/merge request somewhere?
[13:13] <sladen> kmadac: please file the bug first, so that then you can say $bug is fixed by $proposed_pull_request
[13:14] <sladen> kmadac: ideally we try and get bug fixes applied by upstream first if possible, so that everyone benefits; not just Ubuntu or Debian users
[13:15] <sladen> kmadac: the bug report also allows keeping track of what communication with upstreams
[13:17] <kmadac> sladen: ok I will fill a bug, but can you please elaborate more about proposing pull request? Or can you point me to some documentation how to do it? Is it still done over bazaar as is stated in public documentation, or was it changed?
[13:19] <sladen> kmadac: http://stackoverflow.com/a/20273376/839696
[13:20] <sladen> kmadac: (you need the bug number, to link the metadata together for what the proposed fix is)
[13:21] <kmadac> sladen: thanks :), I'm going to fill the bug report
[13:29] <Bluefoxicy> I wish goa-daemon wouldn't time out and break evolution
[13:29] <Bluefoxicy> requiring a manual killall goa-daemon and then a run of /usr/lib/x86_64-linux-gnu/gnome-online-accounts/goa-daemon
[13:30] <Bluefoxicy> Bill Gates recommended rebooting frequently to avoid problems like this
[13:36] <cjwatson> kmadac: The Bazaar importer has been mostly decommissioned since it was too unreliable.  There's a Git version in progress but it's not completely done.  In the meantime you're better off simply sending patches.
[13:37] <cjwatson> I don't think sladen's link is going to help much nowadays.
[13:37] <cjwatson> (Unless there is an obvious upstream repository that you can propose a merge into.)
[13:53] <caribou> rbasak: when you have a minute, could you please review my last comment on LP: #1176046 ?
[13:57] <rbasak> caribou: I don't understand your comment.
[13:58] <rbasak> "...if isc-dhcp-ddns Breaks/Replaces isc-dhcp and Recommends isc-dhcp-ddns..."
[13:58] <rbasak> It would Recommend itself?
[13:58] <rbasak> I don't really follow what Breaks/Replaces would do here.
[13:58] <rbasak> isc-dhcp-ddns in Xenial supplies /sbin/dhclient with a divert.
[14:03] <mterry> slangasek: is Foundations willing to look after libsmbios in main?  And if so, can you subscribe ~foundations-bugs to its bugs?  (this is re: MIR bug 1603072)
[14:26] <attente> hi, would it be possible to backport the bubblewrap package to xenial?
[14:28] <seb128> attente, hey, backport or SRU? any of those should be possible I think, depending why you need it
[14:29] <attente> seb128: i'm not sure the distinction tbh, it's needed so that the integration test for the snapcraft jhbuild plugin can pass there
[14:30] <seb128> do they have a ppa they are using where it could be added?
[14:30] <attente> seb128: the package doesn't seem to exist there atm, so it would be a new package in universe
[14:30] <seb128> I guess it's a question for the snappy team
[14:30] <seb128> like mvo should be able to guide you?
[14:30] <seb128> or ogra
[14:30] <attente> ok, thanks seb128, i'll ask there
[14:31] <seb128> I sort of pinged them
[14:31] <seb128> so maybe they reply here ;-)
[14:31] <attente> oh, right :)
[14:31] <mvo> attente: backport is trivial, just dput the package and target to xenial-backports in the changelog
[14:31] <mvo> attente: well
[14:32] <mvo> attente: or file a backport request, depends a little bit if it needs source changes or not
[14:32] <mvo> attente: see https://wiki.ubuntu.com/UbuntuBackports
[14:32] <mvo> attente: it should be pretty lightweight
[14:32] <mvo> attente: sru is a bit more work, you know the drill for this already I think :)
[14:32] <seb128> mvo, the question is rather from the snappy CI infra side
[14:33] <seb128> mvo, what env is used for snapcraft integration tests? does that include some ppas or backports?
[14:34] <mvo> seb128: snappy or snapcraft? snapcraft is a sergiusens question, I would assume they can easily use xenial-backports
[14:34] <attente> it's snapcraft
[14:34] <seb128> mvo, sorry, snapcraft indeed, should have bother sergiusens and not you ;-)
[14:34] <mvo> seb128: np
[14:34] <attente> i guess it's a backport since the package isn't there at all in xenial
[14:34] <seb128> sergiusens, ^ can snapcraft integration tests use xenial-backport or a ppa?
[14:35] <seb128> attente, well, you can SRU a package that was not there, we did it with snapd-xdg-open if you remember ;-)
[14:36] <seb128> but backport is an easier process
[14:36] <sergiusens> seb128 attente can adt? Maybe so, or maybe just disable the test for xenial and make your plugin query where it is running on
[14:37] <seb128> sergiusens, it means you are not using backports or a ppa? would be better to have things working rather than disabled...
[14:38] <attente> yeah, the integration tests seem to be passing on y and z already, so if we can just get the package on x too, that would be preferable
[14:38] <sergiusens> seb128 yeah, we are not using backports or PPAs, just xenial-updates
[14:39] <seb128> k
[14:39] <attente> should we sru it then?
[14:39] <seb128> sounds like it
[14:39] <seb128> or talk to sergiusens about enabling backports
[14:39] <seb128> or disable the test on xenial...
[14:39] <seb128> well maybe do that to unblock the landing
[14:39] <seb128> but then work on getting it SRUed
[14:40] <seb128> or change to use a tech which is available in xenial ;-)
[14:40]  * attente didn't hear the last one
[14:40] <seb128> lol
[15:07] <xnox> pitti, google-chrome does not like to die, upon logout, under systemd user session with unity7
[15:07] <xnox> is there any trigger that kills chrome under upstart session? (e.g. does upstart use a bigger hammer, faster?)
[15:07] <xnox> also nm-applet appears to be "slow" under systemd.
[15:08] <xnox> it takes me good 10-15seconds for both indicator-network and nm-applet to appear.
[15:08] <xnox> (fixing the fact that they are duplicates)
[15:16] <dobey> xnox: chrome doesn't have an upstart job afaik. it's just gnome-session killing things i think, or maybe just when X dies
[15:19] <dobey> xnox: if nm-applet and indicator-network are both slow to appear, maybe something lower level like communications with network-manager being slow
[15:22] <xnox> dobey, upon logout everything dies but chrome stays alive, from tty2 i can see that chrome has become a child of the user systemd session and somehow is still alive.
[15:23] <xnox> given all the rectangular bubbles I see, i think the chrome "extensions/apps" are simply respawning.
[15:24] <xnox> so something somewhere is not given a chance to kill chrome "properly" e.g. gnome-session/bamf killed without it given a chance to kill chrome, or chrome catching signals and respawning.
[15:24] <xnox> ack. will debug more.
[15:24] <dobey> xnox: yeah, it's sounding like an issue with systemd stuff to me, i mean.
[15:25] <xnox> https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1649309
[15:46] <slangasek> mterry: foundations-bugs subscribed to libsmbios
[15:47] <mterry> slangasek: oh thanks!
[15:55] <bregma> hey tjaalton is there an ETA for x.org 1.19 landing in Zesty?  I have some XMir bugfixes and I want to coordinate work
[15:59] <tjaalton> bregma: xmir needs to be ported first, and nvidia blobs need to support the new abi before it can land
[15:59] <tjaalton> bregma: so probably not before mid-january'ish
[16:00] <tjaalton> bregma: tseliot is out until then, and I'm off for two weeks as well
[16:02] <bregma> tjaalton, I have a 1.19 port for XMir already, but we need to land in 16.04 ASAP because it's blocking other stuff from landing
[16:03] <bregma> I can just SRU the patch short-term if a 1.19 landing is not imminent
[16:03] <xnox> dobey, tedg: what is unity-greeter-session-broadcast and is it needed in the all-snap world? and/or needs a rewrite for the all-snap world?
[16:03] <tjaalton> bregma: yeah it's not imminent
[16:04] <tedg> xnox: It handles sending messages from the greeter session to the user session.
[16:04] <dobey> xnox: no idea
[16:04] <tedg> xnox: Not sure it needs to be rewritten, but it should be in the U8 snap with the U8 greeter and U8 session.
[16:04] <tedg> xnox: It'll have to be a system service.
[16:05] <tjaalton> bregma: should git://git.launchpad.net/~xmir-team/xorg-server/+git/xmir have the latest? or haven't pushed there yet?
[16:05] <dobey> tjaalton: btw, did the mesa causing gtk+ (aka everything) to crash in zesty-proposed get fixed btw?
[16:05] <tedg> xnox: We're not entirely sure on the architecture there though, I imagine the greeter will be in the same snap as the session so we won't need any security stuff there.
[16:05] <tjaalton> dobey: yes
[16:05] <bregma> tjaalton, I haven't pushed there yet
[16:05] <tjaalton> bregma: gotcha
[16:05] <dobey> awesome
[16:05] <xnox> tedg, the things it does, have no systemd equivalent. e.g. one cannot start a systemd unit on per message (aka equivalent of the upstart-dbus-bridge events)
[16:06] <tjaalton> dobey: although it's still in proposed because of tests
[16:06] <xnox> tedg, and all i can see, it triggers url-dispatcher event.
[16:06] <tedg> xnox: Sure, it'll have to switch to be dbus-activation. So I guess it'll need refactoring, not rewriting.
[16:06] <xnox> tedg, a system thing that store greeter events and send them to session url-dispatcher make sense. I think it just needs to be done outside of systemd, just over dbus.
[16:07] <xnox> priviledged thing, that greeter talks to and stores "events" there, and then session which talks to priviledged thing to retrieve and action "events"
[16:07] <xnox> tedg, ack.
[16:07] <dobey> tjaalton: that's fine; it was blocking build of some stuff that runs binaries with gdk_init during tests
[16:07] <tjaalton> ubiquity, yes
[16:07] <dobey> tjaalton: so hopefully i can build now, and at least "land" a fix or two that we need for unity8 snap
[16:10] <jbicha> bigon: https://irclogs.ubuntu.com/2016/11/21/%23ubuntu-devel.html#t20:28
[16:17] <jbicha> (I'd rather not be the Debian maintainer for snapd-glib now)
[16:33] <bigon> jbicha: ok
[16:38] <seb128> bdmurray, hey, why did you assign bug #1647020 to our team? it seems a pretty random report without much details
[16:41] <bdmurray> seb128: because its from a canonical employee and seemed like a regression.
[16:42] <seb128> bdmurray, ok, thanks, I'm going to comment on it but it's more likely a kernel issue than a desktop one
[16:42] <bdmurray> seb128: okay, thanks for following up
[16:42] <seb128> yw!
[16:50] <caribou> rbasak: sorry, I missed your question and, indeed my comment is unclear
[16:51] <caribou> rbasak: I'll clarify my comment in the bug
[19:00] <rbasak> !dmb-ping
[19:01] <rbasak> Need one more for quorum.
[20:49] <fossfreedom> Hi all - David Mohammed here - project lead for Ubuntu Budgie.  Just hoping that someone can have a look over our pull request for lp:ubuntu-cdimage ?
[20:49] <fossfreedom> https://bugs.launchpad.net/ubuntu-cdimage/+bug/1647862
[20:54] <xnox> fossfreedom, have you considered to name this flavour "Bubuntu"?
[20:54] <xnox> =)
[20:55] <xnox> ikey would like that =)
[20:55] <fossfreedom> shudder
[20:55] <fossfreedom> no thanks!!
[20:55] <xnox> fossfreedom, hahaha =) fair enough! =)
[20:56] <xnox> fossfreedom, do you need and will you test i386 image? (btw it does not have uefi support, and e.g. ubuntu.com only advertises amd64 images across the board by default)
[20:57] <xnox> fossfreedom, official flavours should be teams by default, even if that team has a single person. As it's easier to manage ACL that way. E.g. said team will join ubuntu-devs and e.g. ubuntu core-devs will join the ubuntu-budgie-dev team etc.
[20:57] <fossfreedom> yep - there seems to be very few testers now who concentrate on i386 - would welcome any help once the ISO's start to be created.
[20:58] <fossfreedom> I've created a team here: https://launchpad.net/~ubuntubudgie-dev
[20:59] <xnox> fossfreedom, my question is kind of a devil's advocate - why not go amd64-only?
[20:59] <xnox> it's only 15 years old.
[20:59] <fossfreedom> Question really for the Ubuntu community - I know it has been recently floated again to drop i386.
[21:00] <jbicha> if Budgie goes amd64 only, Ubuntu GNOME might follow
[21:01] <fossfreedom> mind you - just today I had two people wondering if its possible to install the 386 version.  Answer given was to "try and let me know"
[21:01] <jbicha> I'm reluctant to have us do something like that if no other flavor is
[21:01] <cjwatson> fossfreedom: That's partly true, but there are different considerations that apply to adding a new flavour vs. changing existing flavours
[21:01] <cjwatson> They don't all have to be in sync
[21:02] <jbicha> supporting both i386 and amd64 is to some extent twice the work when testing iso release milestones
[21:02] <xnox> fossfreedom, removing an arch/image-type is pain; adding an arch/image-type if there is actual demand is trivial.
[21:02] <xnox> (ripping band-aid off versus putting one on)
[21:03] <fossfreedom> generally I soak in water first ... but yeah I know what you mean.
[21:03] <xnox> cjwatson, is it me, or the ubuntu-cdimage code is littered with lexical order comparison with all the self.config["DIST"] >= "xenial"
[21:03] <cjwatson> xnox: It's just you.
[21:03] <xnox> infinity, too ^
[21:03] <xnox> cjwatson, ok.
[21:03] <cjwatson> I was cleverer than that :-)
[21:03] <cjwatson> Look in lib/cdimage/config.py
[21:04] <cjwatson> Series is a magic thing that can do comparisons by series name but they're actually compared using their index in all_series
[21:05] <cjwatson> and self.config["DIST"] is a Series
[21:05] <xnox> nice =) you map them to index first, then compare.
[21:05] <cjwatson> Saves on a lot of verbiage
[21:05] <infinity> It's elegant in its perversion.
[21:05] <infinity> And best not examined too closely.
[21:07] <fossfreedom> jbicha - thanks for your kind thoughts BTW on my application.
[21:15] <jbicha> fossfreedom: I think lib/cdimage/tests/test_build.py shoudl be False, True
[21:18] <fossfreedom> ah - yes - good spot "unsupported" let me update
[21:21] <jbicha> honestly, I don't know what unsupported means
[21:24] <fossfreedom> corrected.
[21:27] <fossfreedom> hmm ... I don't remember "Ubuntu-Moblin-Remix" - what was that?
[21:28] <fossfreedom> ah - yes - netbook thingy
[21:59] <bdmurray> rbasak: Could you look at bug 1640823 again? Are you happy with what was most recently uploaded to -proposed?
[22:26] <fossfreedom> xnox re ~ubuntubudgie-dev - I have 'invited' ubuntu-devs to join
[22:27] <fossfreedom> xnox: re ~ubuntubudgie-dev - I have 'invited' ubuntu-devs to join
[22:33] <Bluefoxicy> Hooray, cmiller has arrived
[23:09] <Bluefoxicy> what's the appropriate way to ask for a package upgrade in Zesty?
[23:10] <Bluefoxicy> Monodevelop 6.1 supports Nuget 3 (finally) (6.2 supports Nuget 3.5, but it's not *stable* yet), and Zesty packages 5.10


[15:45] <hazmat> can we get bzr uploaded to pypi
[15:45] <hazmat> currently installing bzr from pypi requires rather inane arcana of
[15:45] <hazmat> pip install bzr --allow-external bzr --allow-unverified bzr
[15:46] <hazmat> which means it can be declared a dep for anything else in pypi, cause pip will barf without it
[19:11] <lifeless> hazmat: I suggest filing a bug and/or mailing list comment, since its likely that noone involved in the release process saw your request.
[19:12]  * hazmat files a bug
[19:13] <hazmat> oh.. someone beat me to it
[19:14] <hazmat> the last 3 bugs in bzr are the same..
[19:17] <lifeless> hah
[19:18] <hazmat> lifeless, you have upload rights to bzr in pypi :-)
[19:19] <lifeless> huh
[19:20] <lifeless> thats stale :)
[20:28] <jelmer> hazmat: you probably want jml or vila


[00:00] <TheMarius> same here, the bug is out there though
[00:00] <TheMarius> as in, reported
[00:01] <TheMarius> but i actually prefer the way it looks now anyway... more compact
[00:01] <TheMarius> functions the same way minus pause play etc if i click it, but id rather just have the quick access to volume control
[00:03] <fifty-sevenC> ok
[00:14] <TheMarius> but thanks for helping out, fifty-sevenC
[00:14] <TheMarius> :)
[00:14] <fifty-sevenC> np
[02:36] <alwan> i'm using umate 16.04.. it's probably the best linux distro for now
[02:39] <usedand> moonunitreed
[03:24] <odroid> is any body out there?
[03:38] <vm_unix> hey, I think I have a solution for a common problem in 16.04
[03:40] <ouroumov__> vm_unix, do say
[03:40] <ouroumov__> odroid, hi
[03:46] <vm_unix> I've heard time and time again about the wireless issue and I suffered from it too. I just upgraded my kernel and haven't had a problem since. I believe you should just patch the kernel to the latest upstream in your series.
[03:47] <vm_unix> which would be 4.4.11 at this point.
[03:49] <ouroumov__> vm_unix, what wireless issue?
[03:49] <vm_unix> the one where it cuts out upon suspend.
[03:49] <ouroumov__> On what hardware?
[03:50] <vm_unix> Do you want the exact hardware or just the wireless card?
[03:50] <ouroumov__> output of inxi -N should do it
[03:52] <vm_unix> Network:   Card-1: Intel Wireless 7260 driver: iwlwifi
[03:52] <vm_unix>            Card-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
[03:52] <vm_unix>            driver: r8169
[03:52] <vm_unix> That's a cool new one..thanks for that.
[03:52] <vm_unix> It is the n model btw
[03:52] <ouroumov__> Intel card, same as mine, with lower serial number - weird
[03:53] <vm_unix> It is the 7260-N
[03:53] <ouroumov__> actually higher *
[03:53] <ouroumov__> I have 3160
[03:53] <vm_unix> oh..
[03:53] <ouroumov__> So I guess it kind of make sense
[03:54] <vm_unix> I just got a newer kernel just because I thought it might be a bug in the current Ubuntu kernel. It's fine now.
[03:54] <ouroumov__> I've not had problems with wifi at all using the LTS kernel, but you're using a newer model
[03:54] <vm_unix> Ya, I'm fine now.
[03:55] <vm_unix> I just hope that other people had the same or a similar idea.
[03:55] <ouroumov__> vm_unix, so thanks for testing that out. If you want your tip to have visibility you should post the info on the community forums
[03:56] <vm_unix> I suppose I'll create an account..though I'm not a fan of making so many accounts..
[03:57] <ouroumov__> I get it. ^^ You're free to use a throw-away email/password, we won't hold that against you
[10:09] <fifty-sevenC> I don't see 4.4.11 linux-image in my package manager
[12:15] <mate|11477> hi
[12:15] <fifty-sevenC> Hello
[12:16]  * flexiondotorg would just like to thank the regulars here who offer help and assistance to people new to Ubuntu MATE.
[12:17] <mate|11477> i have problem with system temp. in windows and ubuntu the system temp. are similar but fan working in ubuntu mate is more than win. "amd gpu"
[12:17] <fifty-sevenC> Do you know which driver you are using? And what video card?
[12:18] <fifty-sevenC> It can also be that gpu load is averaging higher
[12:18] <mate|11477> open source  in only driver in 16.04 repo
[12:18] <mate|11477> amd 7400m
[12:19] <fifty-sevenC> Ok. Try this
[12:19] <fifty-sevenC> Click System -> Preferences -> Look and Feel -> MATE Tweak
[12:20] <fifty-sevenC> Click the Windows button. Which Window manager is it?
[12:21] <mate|11477> first defautl wm.
[12:21] <fifty-sevenC> What is the default for your system?
[12:21] <fifty-sevenC> Compiz?
[12:23] <fifty-sevenC> Try changing it to software or no compositor and see if your gpu fans spin up less often.
[12:25] <mate|11477> changed.no difference! also actived tlp.i think problem is open source driver.
[12:25] <fifty-sevenC> Give it a few minutes before deciding it had no effect
[12:27] <fifty-sevenC> Run this in a terminal
[12:27] <fifty-sevenC> cat /sys/class/drm/card0/device/power_dpm_state
[12:27] <fifty-sevenC> Is it battery or performance mode?
[12:29] <mate|11477> no batt
[12:30] <mate|11477> can i dasble amd gpu with editing grub?i dont know about my laptop hybrid ability. hp 8460p core i5. is it?
[12:32] <fifty-sevenC> You can blacklist it using modprobe
[12:33] <mate|11477> so is my pc using hybrid gpu?
[12:34] <fifty-sevenC> type lsmod | grep radeon
[12:35] <fifty-sevenC> Does it return anything?
[12:36] <fifty-sevenC> https://wiki.archlinux.org/index.php/hybrid_graphics#ATI_Dynamic_Switchable_Graphics
[12:43] <mate|11477> lsmod | grep radeon   what does this command?
[12:44] <fifty-sevenC> looks for the string 'radeon' in the list of loaded modules
[12:45] <mate|11477> what about add  redeon.modest 0  to grub?
[12:48] <fifty-sevenC> You can add radeon.modeset=0
[12:48] <fifty-sevenC> Or you can blacklist the driver in modprobe
[12:49] <fifty-sevenC> Both will disable your video card
[12:49] <mate|11477> is it safe?
[12:50] <fifty-sevenC> Should be.
[12:50] <fifty-sevenC> Blacklisting will tell the kernel to not interact with it entirely
[12:50] <fifty-sevenC> setting modeset=0 will just turn it off
[12:52] <mate|11477> so wich is better?
[12:52] <fifty-sevenC> up to you
[12:52] <fifty-sevenC> If after you reboot with either it is easy to fix from the command line
[12:53] <fifty-sevenC> You can try installing the propritary driver
[12:54] <mate|11477> how? in ubuntu 16.04?
[12:54] <fifty-sevenC> System -> Preferences -> Hardware -> Additional Drivers
[12:56] <mate|11477> remember. there is no propritary  amd driver in repo for now.
[12:56] <mate|11477> in ubuntu 16.04 version
[12:58] <fifty-sevenC> Ok
[12:58] <fifty-sevenC> then try the grub way of radeon.modese=0
[12:58] <fifty-sevenC> modeset=0
[12:59] <mate|11477> ok.if reboot with black screen how can i fix it?
[13:00] <ouroumov> flexiondotorg, and thank you for doing the heavy lifting. :]
[13:00] <ouroumov> Hi fifty-sevenC
[13:01] <fifty-sevenC> Hi ouroumov
[13:01] <fifty-sevenC> mate|11477, when booting jam the shift key
[13:01] <fifty-sevenC> enter recovery mode
[13:01] <fifty-sevenC> THen remove the line you added to grub
[13:02] <mate|11477> ok.thank u so much.i will test.
[13:03] <flexiondotorg> ouroumov, o/
[13:03] <fifty-sevenC> Hi flexiondotorg
[13:03] <flexiondotorg> fifty-sevenC, o/
[13:04] <fifty-sevenC> A shame about that hybrid amd-intel graphics
[13:06] <fifty-sevenC> I"m personally hoping radeon gains good support for being attached and detached without rebooting
[13:06] <fifty-sevenC> So when I build my VT-d computer I won't need a video card just for the windows VM
[14:11] <nickanon> Hello, I am using ubuntu mate 15.04. There's a problem. My battery status on top panel updates slow so it gives wrong information about battery status. Any idea How can I solve this?
[14:13] <fifty-sevenC> 15.04 isn't supported anymore.
[14:14] <ouroumov> Hi nickanon. As 57c mentioned you might want to update your machine.
[14:15] <nickanon> My machine is quite old, maybe of 2004. I dont think latest linux kernel will run smooth on it!
[14:16] <fifty-sevenC> What cpu?
[14:16] <nickanon> intel
[14:16] <fifty-sevenC> Intel what?
[14:17] <nickanon> intel core i3 , 2.13 Ghz
[14:17] <fifty-sevenC> Core i3 is from 2010
[14:18] <fifty-sevenC> It should work fine
[14:18] <nickanon> oh should I upgrade to 16.04 then?
[14:18] <fifty-sevenC> You can't skip upgrades
[14:18] <fifty-sevenC> You have to upgrade to 15.10 first
[14:18] <fifty-sevenC> Unless you want to wipe and fresh install
[14:18] <nickanon> I am thinking of fresh install
[14:19] <fifty-sevenC> Well, try upgrading first so you don't have to lose your data
[14:19] <nickanon> ok...
[14:19] <nickanon> thanks buddy
[15:00] <gall> is there here anyone that use ubuntu mate on raspberrypi3?
[17:24] <fifty-sevenC> Hi
[17:25] <alkisg> Hello
[21:52] <ubuntu-mate> hi everyone
[21:52] <fredy_> hey there
[21:55] <fifty-sevenC> Hi
[21:55] <fifty-sevenC> Oh he left :(
[22:04] <fredy_> im here
[23:07] <pierrot> good evening
[23:08] <fifty-sevenC> Hi pierrot
[23:09] <pierrot> hey fifty-sevenC. I'm trying to configure static IP but I'm having some trouble
[23:09] <fifty-sevenC> Alright, where are you having trouble with it?
[23:09] <pierrot> first of all, my network interfaces have weird names
[23:09] <pierrot> basically, enx followed by the MAC address of my network card
[23:09] <fifty-sevenC> That isn't out of the ordinary.
[23:10] <fifty-sevenC> type ip address
[23:10] <pierrot> Yes, I did that.
[23:11] <fifty-sevenC> Do you know the IP address and netmask you want?
[23:11] <pierrot> Yes, I know
[23:12] <fifty-sevenC> then do
[23:13] <pierrot> I want <IP_ADDRESS> and netmask <IP_ADDRESS>
[23:13] <pierrot> I used Ubuntu MATE 15.04 for a year and I had it with that static IP
[23:14] <fifty-sevenC> ip addr add <ipaddress> dev <deviceIFNAME>
[23:14] <pierrot> but today I upgraded to a new image (Ubuntu 16.04) so I'm configuring it again
[23:14] <pierrot> what's <deviceIFNAME> ?
[23:15] <fifty-sevenC> that enx name
[23:15] <pierrot> It should be 'eth0' but with this weird notation, I guess it's the name with enx
[23:15] <pierrot> right
[23:16] <fifty-sevenC> Then you will need to add it to your interface config file
[23:16] <pierrot> /etc/network/interfaces ?
[23:16] <fifty-sevenC> sudo nano /etc/network/interfaces
[23:16] <fifty-sevenC> yes
[23:17] <pierrot> and again, use the "enx" name instead of eth0
[23:17] <pierrot> ?
[23:17] <fifty-sevenC> If that is your device name yes
[23:20] <pierrot> iface enx*MAC* inet static ?
[23:21] <fifty-sevenC> Like this
[23:21] <fifty-sevenC> http://www.tecmint.com/ip-command-examples/
[23:22] <pierrot> done
[23:22] <fifty-sevenC> You should be set
[23:23] <pierrot> I wrote:
[23:23] <pierrot> auto enx*MAC* (the weird name)
[23:23] <pierrot> iface enx*MAC* inet static
[23:24] <pierrot> and then the desired address and netmask and the IP of my router as gateway
[23:26]  * pierrot is rebooting the Pi to know if the changes are persistent
[23:26] <fifty-sevenC> ok
[23:30] <pierrot> Nice, it worked !
[23:30] <pierrot> Thanks fifty-sevenC :)
[23:31] <fifty-sevenC> :)
[23:52] <YankDownUnder> Morning...anyone know if there's some issues with doing "apt-get" updates? "apt" is getting stuck - or at least for me...not sure how to resolve this...thanks
[23:53] <fifty-sevenC> Getting stuck with what
[23:55] <YankDownUnder> fifty-sevenC, When I do an "apt-get update" - after it reads everything from the PPA's, just just sits...the last "message", after doing a "fetch" is: "Fetched 94.5kb in 17s (5,366 B/s) => and just sits there...
[23:57] <fifty-sevenC> Might be a slow server


[01:18] <mup> PR snapcraft#922 closed: On gradle unit tests, unset the proxies <Created by elopio> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/922>
[03:06] <tsimonq2> cwayne: Quick, propose that your snap be merged: https://github.com/atom/atom/pull/13293
[03:06] <mup> PR atom/atom#13293: Add Flatpak support <needs-review> <Created by mattdangerw> <https://github.com/atom/atom/pull/13293>
[03:06] <tsimonq2> :P
[05:27] <hades007> how to put an apparmor profile in complain mode with ubuntu core 15.04 ? sudo  "apparmor_parser -rC /var/lib/apparmor/profiles/click_lxd_lxc_2.0.5-1" doesn't to work
[07:12] <foxmask> bonjello
[07:48] <dholbach> hey hey
[09:39] <mup> Bug #1643816 opened: improve systemd configuration support <Snappy:New> <https://launchpad.net/bugs/1643816>
[10:04] <markusfluer> Good morning,
[10:04] <markusfluer> How would I set the prefixes for nginx in a snap?
[10:05] <markusfluer> Or should they be just untouched and let autotools manage them
[10:10] <zyga> markusfluer: hey, you can try to set the prefix to /snap/nginx/current/ and use organize to strip that path from installation
[10:10] <zyga> markusfluer: as snapd will ensure that at runtime the content of your snap is visible from that location
[10:12] <markusfluer> zyga: Thank you very much.
[10:13] <zyga> markusfluer: I don't remember how to use organize to do this though,
[10:13] <zyga> markusfluer: experiment on hello world or something that builds quickly
[10:13] <zyga> markusfluer: and when you do, please share
[10:14] <markusfluer> zyga: I will try it out and comment it in the snapcraft.yaml.
[10:14] <markusfluer> I will publish it on github anyway
[10:15] <zyga> thanks
[10:23] <didrocks> zyga: I thought we shouldn't hardcode /snap though?
[10:23] <didrocks> this is what niemeyer told multiple times
[10:23] <didrocks> (but we don't have any other answer AFAIK)
[10:24] <zyga> didrocks: well, once we get a better answer people can adapt
[10:25] <zyga> didrocks: walk, run, fly :)
[10:48] <mup> PR snapcraft#923 opened: WIP pluginhandler: source management moved to the core <Created by sergiusens> <https://github.com/snapcore/snapcraft/pull/923>
[11:43] <jon___> hi I've just followed the ubuntu core setup steps, all ok until it now asks for a login and password, any ideas what this is for an initial boot?
[13:37] <mup> Bug #1643885 opened: ubuntu core image has different content between archs <Snappy:New> <https://launchpad.net/bugs/1643885>
[13:43] <mup> Bug #1643888 opened: first snap try doesn't install core snap <Snappy:New> <https://launchpad.net/bugs/1643888>
[13:55] <jdstrand> tedg: hey, if I wanted to file a bug against the results of locking snaps to the unity7 launcher, where would I file it?
[13:55] <tsdgeos> maybe someone should try to approach Valve since they seem to be leaning to trying flatpack https://forums.xamarin.com/discussion/comment/232301/#Comment_232301 maybe they can be convinced to use snappy
[13:55] <mup> Bug #1643893 opened: snapd doesn't handle well flaky network <Snappy:New> <https://launchpad.net/bugs/1643893>
[13:56] <jdstrand> JamieBennett, dholbach: fyi tsdgeos comment ^
[13:56] <Trevinho> jdstrand: what's the bug?
[13:57] <Trevinho> jdstrand: anyway... unity project I guess, but it depends...
[13:58] <jdstrand> Trevinho: I'm trying to find a simple reproducer
[13:58] <Trevinho> jdstrand: ok, ping me once you've it
[13:59] <jdstrand> Trevinho: basically what I see happen sometimes is that when I lock to the launcher, /snap/<name>/path/to/exe is used instead of /snap/bin/name
[13:59] <jdstrand> Trevinho: which is a pretty serious security bug because /snap/<name>/path/to/exe runs outside of confinement
[14:00] <Trevinho> jdstrand: I guess that's because the app didn't match properly to something, right?
[14:00] <Trevinho> jdstrand: howver, that's BAMF..
[14:00] <Trevinho> jdstrand: like you're running a snap from a shell, then you try to lock it, right?
[14:00] <seb128> tsdgeos, that's probably something worth mentioning on the snappy mailing list, IRC backlog info is likely to get lost
[14:00] <jdstrand> Trevinho: I guess?? tbh I've never, ever, ever understood how that matching was supposed to work, no matter how hard I tried
[14:01] <jdstrand> Trevinho: that is one scenario. I've also launched from the dash and seen the same thing
[14:01] <jdstrand> Trevinho: but not everything. eg, vlc is working fine
[14:01] <Trevinho> jdstrand: so..... I asked multiple times to include inside the wrapper script a BAMF env variable that points to the actual desktop file when possible...
[14:01] <mup> Bug #1642900 changed: libgcc_s.so.1 not found by app using ubuntu-app-platform content snap <Ubuntu App Platform:New> <https://launchpad.net/bugs/1642900>
[14:02] <Trevinho> jdstrand: so, in case that there's no other way to match the app, then we try to undestand what binary launched it... Thus the problem you mentioned. This actually worked well in non snap-world. But I guess we've to tune it too
[14:04] <Trevinho> jdstrand: have a look to this though: https://github.com/snapcore/snapd/pull/1580#issuecomment-234546220
[14:04] <mup> PR snapd#1580: wrappers: set BAMF_DESKTOP_FILE_HINT for unity <Created by mvo5> <Closed by chipaca> <https://github.com/snapcore/snapd/pull/1580>
[14:04] <Trevinho> jdstrand: if that was done in the wrapper script, then it would fix also the issue you're talking about
[14:05] <Trevinho> indeed we've to cover also the case where a desktop file is not provided, and avoid doing what you mentioned, but this would b already a good point
[14:05] <jdstrand> Trevinho: maybe I will file a bug against snapd then
[14:06] <jdstrand> Trevinho: then point you at it for comment?
[14:06] <Trevinho> jdstrand: ok
[14:07] <JamieBennett> Trevinho, jdstrand, After a quick search I see no confirmation of Valve using flatpak atm, just a bunch of very vocal non-Valve people talking about flatpak and discounting snaps for no apparent reason than it comes from Canonical (which is try but is also wrong as the snap format is governed outside of Canonical). ev_, dholbach, or popey may have more context though.
[14:07] <Trevinho> jdstrand: here there's more context https://trello.com/c/xP1hN3BF/152-improve-desktop-file-support-by-adding-a-new-bamf-desktop-file-hint-environment-hint
[14:07] <dholbach> I don't have much info on valve's use of snaps.
[14:11] <popey> me either
[14:14] <tsdgeos> seb128: i'm not on that list i think
[14:14] <tsdgeos> seb128: what's the list name/address/mailman/thing?
[14:15] <seb128> tsdgeos, seems JamieBennett is on the topic since he just mentioned it so I guess you can consider it as something the snappy team is aware of and probably no need to email the list
[14:16] <tsdgeos> ok :)
[14:22] <jdstrand> JamieBennett, dholbach: I think tsdgeos point was that perhaps we should be proactive rather the reactive, but I'll leave it in your hands
[14:22] <JamieBennett> jdstrand, understood
[14:26] <mup> Bug #1643910 opened: BAMF_DESKTOP_FILE_HINT not set in correct place for unity7 <Snappy:New> <https://launchpad.net/bugs/1643910>
[14:26] <jdstrand> Trevinho: ^
[14:26] <Trevinho> ack
[14:27] <jdstrand> mvo: fyi, I think bug #1643910 needs attention sooner than later. it can result in snaps running unconfined under certain circumstances under unity7
[14:27] <mup> Bug #1643910: BAMF_DESKTOP_FILE_HINT not set in correct place for unity7 <Snappy:New> <https://launchpad.net/bugs/1643910>
[14:30] <mhall119> jdstrand: panteon-mail needs #1590679, and so do most (or all?) KDE apps.
[14:30] <mup> Bug #1590679: Apps can't own session bus names (unity7 interface) <snap-desktop-issue> <snapd-interface> <Snappy:In Progress by jdstrand> <snapd (Ubuntu):Confirmed> <https://launchpad.net/bugs/1590679>
[14:31] <mhall119> sitter has said that it's the only blocker for most of his KDE snaps
[14:31] <mhall119> some of them have other blockers, but the simple ones just need that
[14:32] <jdstrand> mhall119: are there devmode apps for these things?
[14:32] <jdstrand> mhall119: I guess panteon-mail is devmode? are there any KDE apps that want to talk to each other?
[14:32] <jdstrand> sitter: ^
[14:33] <mhall119> jdstrand: I think they use dbus to talk to themselves (to prevent multiple instances) or with the plasma shell, but sitter can give better info
[14:34] <mhall119> jdstrand: http://distribute.kde.org/snappy-testing/ has all their CI builds of snaps
[14:35] <jdstrand> sitter: do any two snaps in http://distribute.kde.org/snappy-testing/ want to talk to each other?
[14:42] <ppisati> ogra_: have you ever happened to build a kernel snap from -proposed?
[14:43] <ogra_> ppisati, sure, all the time (for rpi) ... but it indeed only works if meta and the kernel are in sync (i'm on vacation btw ;) )
[14:44] <ppisati> ogra_: ah. stay in vcation then
[14:44] <ogra_> heh
[14:45] <ppisati> ogra_: because even if i ticked 'use proposed for the build' it picked only stuff from -updates
[14:45] <ppisati> ogra_: when you are back?
[14:45] <ogra_> next monday ... you need to add proposed in the tree too iirc
[14:48] <ogra_> ppisati, there is code to copy the sources.list from the outer build root to the inner one http://bazaar.launchpad.net/~snappy-dev/kernel-snap-makefile/trunk/view/head:/Makefile#L19 ... so you need to make sure our outer chroot has proposed
[14:50] <ppisati> ogra_: "cp /etc/apt/sources.list chroot/etc/apt/sources.list" - yeah, i saw that, and my build was against -proposed
[14:51] <ppisati> ogra_: so i expected it to be enabled
[14:51] <ppisati> Pocket for automatic builds:
[14:51] <ppisati>     Proposed
[14:51] <ppisati> ogra_: anyhow, you are on vacation so i won't bother anymore
[14:51] <ogra_> but the PPA isnt ... (whiczh you need additionally)
[14:51] <ogra_> here is some other code ... http://bazaar.launchpad.net/~ogra/+junk/kernel-snap-makefile-proposed/view/head:/Makefile
[14:51] <ogra_> (see line 24/25)
[14:52] <ppisati> ogra_: i see
[14:53] <ogra_> you coudl add a config file to the outer branch (the one with snapcraft.yaml) and then read a flag to make that dynamically switchable
[14:59] <gerry_> hi, i have succesfully uploaded my app to the snap store, what is the best way to edit its entry in "Software" ?
[15:00] <didrocks> gerry_: hey! I would say try to go to myapps.ubuntu.com and edit entries there (not sure you can edit them all those)
[15:01] <mvo> jdstrand: let me read the bug again
[15:02] <jdstrand> Trevinho: I think there may be a unity7 component to that. please see my comments and add the tasks if you feel it is appropriate
[15:03]  * Trevinho checks
[15:03] <Trevinho> jdstrand: ah, since I wanted to try your new interfaces... I tried to compile snapd but it seems it failed here... So, isn't there a daily ppa or something?
[15:03] <gerry_> didrocks:  thanks for your help its just at the moment all I have got is "version unknown, source unknown and nonfree!
[15:04] <didrocks> gerry_: oh right, you should edit them thus! :)
[15:04] <jdstrand> Trevinho: I think so, I don't know where it is
[15:04] <jdstrand> mvo: ^
[15:06] <jdstrand> Trevinho: refresh to see comment #5 as well
[15:06] <jdstrand> I feel like there are multiple things happening
[15:07] <jdstrand> like, maybe if things match (eg, vlc and gnome-easytag) things work, but if they don't, items are created in ~/.local/share/applications
[15:08] <mvo> Trevinho: please make sure you ran ./get-deps.sh to ensure your stuff is up-to-date
[15:10] <elopio> vila: ping. Have you seen this? bzr: ERROR: Connection error: while sending POST
[15:10] <jdstrand> Trevinho: ok, and comment #6
[15:10] <jdstrand> ah, you're notified, so I'll stop pinging you here
[15:11] <vila> elopio: that single line rings no bell, more context ?
[15:18] <mup> PR snapcraft#924 opened: New plugin: jhbuild <Created by attente> <https://github.com/snapcore/snapcraft/pull/924>
[15:21] <mup> PR snapcraft#812 closed: New plugin: jhbuild <Created by attente> <Closed by attente> <https://github.com/snapcore/snapcraft/pull/812>
[15:25] <elopio> vila: http://paste.ubuntu.com/23517256/ All our bzr test in arm are failing in a similar way.
[15:29] <vila> elopio: bzr: ERROR: Connection error: while sending POST /~joetalbott/%2Bjunk/testpart/.bzr/smart: [Errno 110] Connection timed out
[15:29] <vila> elopio: firewall issue ?
[15:31] <jdstrand> willcooke, JamieBennett: fyi, bug #1643910. both mvo and Trevinho are aware of it so fyi only. this is a pretty significant usability and security bug when it hits. Please see my comments as well as the description
[15:31] <mup> Bug #1643910: BAMF_DESKTOP_FILE_HINT not set in correct place for unity7 <Snappy:Triaged> <bamf (Ubuntu):Triaged by 3v1n0> <https://launchpad.net/bugs/1643910>
[15:31] <jdstrand> ratliff, tyhicks: also, fyi ^
[15:32] <jdstrand> willcooke, JamieBennett: not saying anything needs to be done more than what they are already working on, but wanted you guys to be aware of the unpredictable behavior and security implications
[15:33] <jdstrand> so that the bug doesn't get deprioritized
[15:33] <jdstrand> ok, is done with that bug for now :)
[15:34] <lof_mt> hi flexiondotorg can you spare some minutes right now?
[15:34] <jdstrand> mhall119: fyi, panteon-mail is not in the store
[15:35] <flexiondotorg> lof_mt, In a meeting. Give me 30mins...
[15:38] <jdstrand> mhall119: do you know which of the snaps in http://distribute.kde.org/snappy-testing/ work? kmahjongg for example does not
[15:39] <mhall119> jdstrand: try kblocks
[15:39] <mhall119> or ktuberling
[15:39] <jdstrand> neither does ktuberling
[15:40] <jdstrand> $ ktuberling
[15:40] <jdstrand> /snap/ktuberling/x1/bin/qt5-launch: line 75: /snap/ktuberling/x1/usr/games/ktuberling: No such file or directory
[15:40] <jdstrand> ok, I'll try kblocks
[15:43] <elopio> vila: perhaps. But in theory, the rules should be the same for all these machines, and it doesn't happen in amd64. I will ask IS anyway.
[15:43] <elopio> thanks!
[15:44] <mhall119> jdstrand: kblocks and ktuberling are both also in the edge channel of the store
[15:44] <jdstrand> mhall119: kblocks fails
[15:44] <mhall119> ok, maybe it's an issue with those builds
[15:44] <jdstrand> kalgebra launched
[15:46] <jdstrand> mhall119: what is the name of the platform snap again?
[15:47] <jdstrand> mhall119: for kde. ktuberling is 5M and is complaining about not finding kde libs
[15:47] <jdstrand> snap find is not helping
[15:48] <Elleo> jdstrand: heya, would you mind giving this a review when you have a chance? https://github.com/snapcore/snapd/pull/2328
[15:48] <mup> PR snapd#2328: Add download manager interface <Created by Elleo> <https://github.com/snapcore/snapd/pull/2328>
[15:48] <jdstrand> kde-frameworks-5?
[15:48]  * jdstrand tries
[15:48] <jdstrand> Elleo: ok, I'll add it to the list
[15:48] <Elleo> jdstrand: thanks :)
[15:49] <mhall119> jdstrand: yes, from --edge
[15:50] <mhall119> snap find won't help,  because they're not in stable
[15:51]  * jdstrand nods
[15:51] <jdstrand> seems like kde-frameworks-5 could've been in stable...
[15:53] <gerry_> I have filled in all the forms at myapp.ubuntu but for some reason it does not appear in my entry in "software" do I have to change how its listed in my yaml somehow?
[15:53] <mhall119> jdstrand: maybe, but without stable app snaps there wouldn't be much point
[15:54] <jdstrand> mhall119: fyi, installing that and making the interface connection results in the same issue
[15:54] <jdstrand> mhall119: I have to /usr/lib/snapd/snap-discard-ns ktuberling for it to work
[15:55] <gerry_> or do I have to find a way to re-publish my app?
[16:01] <kalikiana_> gerry_: doesn't appear meaning what? it's not listed at all?
[16:01] <kalikiana_> how did you upload it?
[16:02] <kalikiana_> can you see it in myapps in the list?
[16:06] <icey> how long does stuff usually take to get from master on github to Launchpad builders?
[16:07] <kyrofa> icey, you mean with git-to-git imports?
[16:07] <icey> kyrofa: I mean: once a patch to snapcraft lands, how long does it usually take before the patch is in the launchpad snappy builders?
[16:08] <kyrofa> icey, ah ha
[16:08] <kyrofa> icey, well, the release process of snapcraft involves an SRU. Are you familiar with that?
[16:08] <kyrofa> icey, long story short, about a week or so
[16:08] <icey> kyrofa: yea
[16:09] <icey> kyrofa: that's a nice timeline ;-) any chance for a review on my PR? https://github.com/snapcore/snapcraft/pull/908
[16:09] <mup> PR snapcraft#908: Let Rust plugin fetch dependencies in pull <Created by ChrisMacNaughton> <https://github.com/snapcore/snapcraft/pull/908>
[16:09] <kyrofa> icey, snapcraft releases weekly, with a little slosh for SRU
[16:10] <kyrofa> icey, don't worry, we'll go back through it!
[16:10] <icey> heh kyrofa, it should have everything asked for now, and it's passing tests :)
[16:10] <kyrofa> Excellent
[16:10] <icey> I'm hoping to get it in soonish, since I wrote about it and started talking about it to the Rust community :)
[16:11] <icey> kyrofa: and apparently people are interested: https://www.reddit.com/r/rust/comments/5e754t/making_rust_packages_for_linux_with_snappy/
[16:12] <kyrofa> icey, good to hear!
[16:23] <lof_mt> ping flexiondotorg
[16:24] <flexiondotorg> lof_mt, Hi there :-)
[16:24] <flexiondotorg> What's up?
[16:24] <lof_mt> do you have a bit of time to help me with the gsettings problem?
[16:24] <gerry_> kalikana: sorry phone call
[16:27] <flexiondotorg> lof_mt, I can try.
[16:27] <flexiondotorg> What is the issue?
[16:27] <lof_mt> flexiondotorg: This is the current snapcraft file: https://paste.ubuntu.com/23513341/
[16:27] <lof_mt> builds well under 16.10 (maybe on 16.04 too not sure about gtk).
[16:27] <mvo> jdstrand, Trevinho: I was a bit busy before but now I looked at the BAMF_DESKTOP_FILE_HINT issue. I'm not sure how what the behavior should be, what if the snap installs multiple desktop files that launch the same binary (say libreoffice with libreoffice --writer). trying to match what desktop file to pick sounds fragile. I think I could support the easy case but it seems far from ideal
[16:28] <lof_mt> But the application crashes when run, because it lacks gsettings schemas. And i could not find documentation about how to include it.
[16:28] <didrocks> lof_mt: you are using the desktop-gtk3 cloud parts
[16:28] <flexiondotorg> lof_mt, The first thing I notice is that you don't have any stage packages.
[16:28] <gerry_> it is listed there is just no summary or details all it has is "version unknown source unknown"
[16:29] <didrocks> lof_mt: all doc is on snapcraft define desktop-gtk3
[16:29] <mvo> jdstrand, Trevinho: e.g. "Exec=libreoffice --writer " and the user uses "libreoffice ~/some/doc --writer" , the parser would have to understand about reordering of args,  etc and probably stll get it wrong because for some apps reodering is legal for some its not etc
[16:29] <didrocks> basically you need:
[16:29] <didrocks> - the home plug for gsettings
[16:29] <didrocks> - and prepend your command with desktop-launcher
[16:29] <didrocks> desktop-launch*
[16:30] <didrocks> flexiondotorg: he doesn't need all stage-packages, the desktop part provides most of them (but yeah, maybe more will be needed)
[16:30] <flexiondotorg> Yep.
[16:37] <lof_mt> didrocks: What do you mean with "the home plug for gsettings"? I have both the home plug and the gsettings plug for the application.
[16:38] <didrocks> lof_mt: oh sorry, as they were not in ascii ordered, I missed it, yeah, you are good for that one :)
[16:38] <didrocks> you only miss desktop-launch prepending thus
[16:38] <flexiondotorg> lof_mt, I tried to build in lxd. You're missing dependencies.
[16:39] <flexiondotorg> Check the Cmake output.
[16:39] <lof_mt> Do you use the cloud or container image? I only checked with desktop and server.
[16:41] <mvo> jdstrand, Trevinho: followed up in the bug, happy to implement naive matching in snap run if that helps but see the bugreport for my questions
[16:43] <kyrofa> zyga, ping
[16:44] <flexiondotorg> lof_mt, I used 'snapcraft cleanbuild' which requires you have lxd installed.
[16:45] <flexiondotorg> It provisions a temporary lxc container to build the snap in.
[16:45] <lof_mt> will test that
[16:49] <lof_mt> When can you omit the bin/ in command:? I saw it in the leafpad example. https://github.com/ubuntu/snappy-playpen/blob/master/leafpad/snapcraft.yaml
[17:00] <rvr> ogra_: fgimenez: Are you aware of any problem with edge and pi2/pi3? I can't boot any image (Waiting for ethernet connection... unable to connect)
[17:02] <fgimenez> rvr, i haven't worked with it in a while, i'll give it a try and let you know how it goes
[17:14] <mhall119> jdstrand: I'm afraid you'll have to get sitter or sgclark to help you here, they know the apps better than I do
[17:18] <willcooke> jdstrand, ack re: #1643910.  thanks
[17:18] <mup> Bug #1643910: BAMF_DESKTOP_FILE_HINT not set in correct place for unity7 <Snappy:Triaged> <bamf (Ubuntu):Triaged by 3v1n0> <https://launchpad.net/bugs/1643910>
[17:53] <lof_mt> the lacking dependency was "gettext".
[17:54] <dslul> Hello, may I ask you, is the raspberry pi3 core16 image still 32bit only?
[17:59] <ogra_> dslul, yes
[18:01] <ogra_> (the 64bit one eats a lot more ram and you might be missing driver support for binary stuff ... there will be a 64bit image at some point, but thats rather low prio)
[18:05] <mattyw> cprov, ping?
[18:06] <cprov> mattyw: hi there
[18:06] <jdstrand> niemeyer: no rush, just fyi that I responded to your question in the pr
[18:06] <jdstrand> niemeyer: (and hi! :)
[18:50] <niemeyer> jdstrand: Heya
[18:50] <niemeyer> jdstrand: Looking
[18:56] <niemeyer> jdstrand: Your idea of allowing the alternation seems like the best option
[18:57] <niemeyer> jdstrand: So we have name: org.foo.bar, and it only matches against another org.foo.bar, but it's okay to use an interface with (-[0-9]*)?
[18:58] <niemeyer> actually, (-[0-9]+)?
[19:00] <stgraber> jdstrand: heya, sorry to nag but have you heard back from the store deploy (or whatever was needed) to have the "lxd" slot work on the lxd snap? had a few people ask about that interface lately as it was mentioned in some recent blog post...
[19:01] <plars> elopio: is there a built-in kill timeout on spread? I seem to be hitting that while it's still installing packages on dragonboard, so it can't even get to the first tests because it kills it too soon
[19:05] <lof_mt> Is there something built in to deploy gsettings schemas? Or do i need to add it to the launcher like in the plank example? → https://github.com/ubuntu/snappy-playpen/blob/af7154cc9cac61d55b17c4aa9517c4d7c003a1a0/plank/launcher
[19:10] <icey> kyrofa: I'm working on cutting out build-essential from the Rust plugin now
[19:11] <icey> kyrofa: looks like it's generally suggested to do build-essential though: https://users.rust-lang.org/t/installation-problem-on-debian-cc-linker/6192
[19:17] <jdstrand> niemeyer: yes. I committed some changes to show how it works
[19:17] <jdstrand> roadmr: hey, what revision is the store at now?
[19:18] <icey> kyrofa: pushed change without build-essential; does t he build environment for Snapcraft's CI look like the Launchpad builders?
[19:21] <jdstrand> roadmr: nm
[19:22] <jdstrand> stgraber: it looks like the store now has r798 of the review tools, so I'll update the lxd snap declaration.
[19:23] <jdstrand> stgraber: ok done. feel free to upload
[19:24] <stgraber> jdstrand: thanks
[19:26] <kkimdev> Q: is there a way to install a snappy package without root?
[19:30] <niemeyer> jdstrand: This looks super verbose: +    name=###DBUS_NAME###-{[1-9],[1-9][0-9],[1-9][0-9][0-9],[1-9][0-9][0-9][0-9],[1-9][0-9][0-9][0-9][0-9],[1-9][0-9][0-9][0-9][0-9][0-9]},
[19:30] <niemeyer> jdstrand: Is that the best we can have with apparmor?
[19:31] <niemeyer> jdstrand: What's the actually supported syntax there?
[19:32] <jdstrand> niemeyer: it is very precise to match pids. the aare is not normal regex
[19:32] <jdstrand> niemeyer: so, yes, that is the best
[19:32] <jdstrand> niemeyer: I mean, we could be less precise, but since we are trying to support pids, I went with very precise
[19:33] <niemeyer> jdstrand: That's good. The question was really if there wasn't richer syntax we could (ab)use
[19:34] <jdstrand> niemeyer: unfortunately, no. the aare is quite flexible but it has its rough spots
[19:36] <niemeyer> jdstrand: Can we nest {}?
[19:36] <niemeyer> Actually, we don't even have to
[19:37] <niemeyer> jdstrand: -[1-9]{,[0-9]}{,[0-9]}{,[0-9]}{,[0-9]}{,[0-9]}
[19:38] <jdstrand> I don't think that is going to eveluate right. note that I stole this from the apparmor upstream tunable for @{pid}
[19:38] <jdstrand> yes, that won't evaluate right
[19:38] <jdstrand> well, maybe
[19:38]  * jdstrand thinks
[19:39] <jdstrand> actually, it looks like it would. let me test something
[19:42] <jdstrand> yeah, that's fine
[19:42]  * jdstrand adjusts
[19:43] <niemeyer> Nice, thanks
[19:43] <niemeyer> jdstrand: Why the deny-connection in the base-declaration?
[19:43] <mup> Bug #1618095 changed: [SRU] 2.14.2 <verification-done> <Snappy:Fix Released> <snapd (Ubuntu):Fix Released> <snapd (Ubuntu Xenial):Fix Released> <https://launchpad.net/bugs/1618095>
[19:50] <dslul> hello, I installed ubuntu core 16 on my raspberry pi3, is it possible to configure it only via ssh? what are the login credentials?
[19:54] <roadmr> jdstrand: ... yes, 798.
[19:54] <roadmr> jdstrand: are you now using snap-declaration plugs/slots for lxd? \o/ Let me know how it works :)
[19:54] <roadmr> jdstrand: I used it for a test snap from the checkbox folks, seems to be working nicely
[19:59] <jdstrand> roadmr: yes, I just added a snap declaration for the lxd snap
[19:59] <roadmr> awesome :)
[19:59] <jdstrand> well, for the slots side. it already had the plugs side
[20:11] <niemeyer> jdstrand: Sent a review
[20:27] <dslul> Is it possible to do the initial configuration of Ubuntu Core using ssh and not with a usb keyboard and a screen?
[20:28] <dslul> I see that the ssh daemon is running, but I don't know the credentials
[20:43] <stgraber> jdstrand: lxd snap updated in all channels for the new slot
[20:43] <jdstrand> stgraber: nice! :)
[21:01] <dslul> nobody knows the answer?
[21:02] <mwhudson> dslul: no,  it is not
[21:02] <mwhudson> dslul: you can do it using serial as well
[21:03] <dslul> how can I do it using serial?
[21:03] <dslul> I mean, I know how to connect to a serial, but what then?
[21:05] <mwhudson> dslul: press enter when connected and it should work the same way as a the tty
[21:06] <dslul> ok thank you very much, I'll try this
[21:08] <kyrofa> icey, sorry for the delay, I was finally getting my couches delivered after nearly three months!
[21:09] <kyrofa> icey, I wouldn't rely on the snapcraft test infra being as vanilla as the LP builders-- you might want to double check there. But honestly, just make a clean lxc or run cleanbuild
[21:10] <kyrofa> And you should be able to determine if you've satisfied dependencies
[21:54] <wililupy> Question: Is there a specific reason why in the grub.cfg we use net.ifname=0?


[12:48] <BluesKaj> Hi folks
[19:25] -queuebot:#kubuntu-devel- Builds: Kubuntu Desktop amd64 [Focal <IP_ADDRESS>] (20210209.1) has been added
[19:28] <RikMills> Eickmeyer: it is on my todo list.
[21:10] <santa_> good evening everyone
[21:10] <santa_> RikMills: I have done most of frameworks the weekend + a couple of acc fixes during the week
[21:11] <santa_> - good news: I think it's ready, or at least almost ready
[21:12] <santa_> - bad news: I got several lintian warnings in my server because of files owner
[21:12] <santa_> http://tritemio-groomlake.duckdns.org/build-status/buildstatus_ubuntu-exp3/
[21:12] <santa_> for example:
[21:12] <santa_> E: akonadi-backend-sqlite: wrong-file-owner-uid-or-gid usr/lib/x86_64-linux-gnu/qt5/plugins/sqldrivers/libqsqlite3.so 114/118
[21:13] <santa_> I can tell you it's NOT related to the new frameworks
[21:13] <santa_> it started to happen very recently and I have the impression it's because of new glibc or doko-related packages
[22:23] <santa_> RikMills: it's also happening in LP: https://launchpadlibrarian.net/522205798/buildlog_ubuntu-hirsute-amd64.kwayland-integration_4%3A5.20.90-0ubuntu1~ubuntu21.04~ppa2_BUILDING.txt.gz
[22:24] <santa_> only with -proposed enabled