[15:57] <jamespage> o/
[15:57] <roaksoax> o/
[15:58] <zul> hola
[15:59] <marcoceppi> o/
[16:00] <hallyn> \o
[16:00] <arosales> hello
[16:00] <smb> \o
[16:01] <hallyn> #startmeeting ubuntu-server-team
[16:01] <meetingology> Meeting started Tue Jun 11 16:01:05 2013 UTC.  The chair is hallyn. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[16:01] <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
[16:01] <hallyn> #topic Review ACTION points from previous meeting
[16:01] <adam_g_> o/
[16:01] <Daviey> \o
[16:01] <hallyn> (carried forward) arosales to follow up with Norvald regarding SRU
[16:01] <arosales> hallyn, I still have to todo to create a server cloud burndown.  I am working on it now. should have an a topic by eod.
[16:01] <arosales> hallyn, that one can be removed
[16:01] <hallyn> cool, thanks
[16:02] <Daviey> arosales: thanks
[16:02] <hallyn> arosales create a overview topic bp for servercloud
[16:02] <hallyn> oh that's that
[16:02] <hallyn> arosales: the bp one can be removed, wht about the SRU item?
[16:02] <arosales> hallyn, reverse
[16:02]  * hallyn confused
[16:02] <hallyn> ok
[16:02] <arosales> sru can be removed
[16:02] <arosales> topic can stay
[16:03] <arosales> to ensure I get it done :-)
[16:03] <hallyn> but you intend to get that done today
[16:03] <arosales> hallyn, correct
[16:03] <hallyn> #action (carried over) arosales: create a overview topic bp for servercloud
[16:03] <meetingology> ACTION: (carried over) arosales: create a overview topic bp for servercloud
[16:03] <hallyn> #topic Saucy Development
[16:04] <hallyn> Release Tracking Bug Tasks - http://reports.qa.ubuntu.com/reports/rls-mgr/rls-s-tracking-bug-tasks.html#server
[16:04] <hallyn> there are 4 critical bugs in that link
[16:04] <hallyn> bug 1175028
[16:04] <Daviey> defer
[16:04] <Daviey> currently being discussed by TB
[16:04] <hallyn> ok, bug 1176686
[16:05] <hallyn> is that server?
[16:05] <Daviey> hallyn: nah
[16:05] <hallyn> ok, bug 969733
[16:05] <hallyn> also not server i'm guessing
[16:06] <hallyn> ok, so nm the critical ones - anything you wanted to bring up here, Daviey?
[16:06] <Daviey> Nope. :)
[16:06] <Daviey> Things seem to be progressing well.
[16:06] <Daviey> Just really, make sure bluepritns are totally nailed. :)
[16:07] <hallyn> are there any that are worrying you?
[16:07] <Daviey> And do add WI's as more stuff appears
[16:07] <Daviey> hallyn: not specifically
[16:07] <hallyn> hm, yeah i might have some WIs to add...
[16:07] <hallyn> ok, do you want an action to do one more once-over on all our blueprints,?
[16:08] <hallyn> #action everyone look over blueprints one more time
[16:08] <meetingology> ACTION: everyone look over blueprints one more time
[16:08] <hallyn> #topic Ubuntu Server Team Events
[16:08] <hallyn> anything coming up?
[16:08] <Daviey> Nothing I can think of..
[16:08] <Daviey> arosales: know of anything?
[16:09] <hallyn> ok, moving on
[16:09] <hallyn> #tpic Weekly Updates & Questions for the QA Team (plars)
[16:09] <hallyn> bleh
[16:09] <hallyn> #topic Weekly Updates & Questions for the QA Team (plars)
[16:09] <hallyn> plars: all well?
[16:09] <plars> nothing big from me at the moment, there were some failures late last week with the server image
[16:09] <plars> but all is well now
[16:09] <plars> except the floodlight test still of course
[16:09] <arosales> Daviey, for events just oscon coming up
[16:09] <hallyn> awesome.  questions for plars?
[16:09] <plars> kernel team has a kernel to bisect for that
[16:10] <plars> going to try to get to it this week if I can, but the other guy that does production qa (psivaa) is out right now
[16:10] <plars> so I'm covering a lot at the moment
[16:10] <plars> will get to it as soon as I can
[16:10] <hallyn> thanks, plars
[16:10] <Daviey> plars: Thanks for the update
[16:10] <hallyn> #topic Weekly Updates & Questions for the Kernel Team (smb)
[16:10] <smb> Kernel is good (until we slap in 3.10 at least). Questions?
[16:10] <hallyn> your irc comment pasting reflex time may be better than the brake reflex time of most drivers around here
[16:10] <Daviey> smb: Are kernel uploads being regression tested against dkms packages yet?
[16:11] <smb> Daviey, Have you told us which?
[16:11] <smb> Officially I mean
[16:11] <smb> Or better plars
[16:11] <Daviey> smb: When this was last discussed, i suggetsed all dkms packages
[16:12] <hallyn> *
[16:12] <plars> smb: jibel mentioned yesterday that he has a prototype of this, not sure on the details other than that
[16:12] <Daviey> At least having a documented history of when the regression was introduced has value.
[16:12] <smb> This would be a few and maybe not all with a naming scheme to detect and not necessarily server related
[16:12] <Daviey> plars: Oh splendid.  Can you find out the details for next weeks meeting please?
[16:13] <plars> Daviey: why wait a week? I'll either send smb an email, or have jibel do it since he's closer to the action on that piece
[16:13] <Daviey> smb: Right, it's not actually that many.  Listing the reverse dependencies of dkms itself should suffice
[16:13] <smb> plars, Sounds good
[16:13] <hallyn> no action needed for that?
[16:14] <hallyn> ok, moving on
[16:14] <Daviey> plars: pls keep me in the loop
[16:14] <hallyn> #topic Weekly Updates & Questions regarding Ubuntu ARM Server (rbasak)
[16:14] <rbasak> Nothing new to report. Any questions for me?
[16:14] <hallyn> hi rbasak
[16:14] <jamespage> rbasak, is the go 1.1 issue in saucy resolved now?
[16:14]  * jamespage is being lazy
[16:14] <rbasak> Oh, good question. I don't think there's been any progress on it. I need to follow up.
[16:15] <Daviey> rbasak: How are the arm saucy images looking?
[16:15]  * rbasak makes a note
[16:15] <hallyn> #action rbasak to follow up on go 1.1. saucy arm issue
[16:15] <meetingology> ACTION: rbasak to follow up on go 1.1. saucy arm issue
[16:15] <hallyn> thanks, moving on in 3,
[16:15] <hallyn> 2, 1,
[16:15] <hallyn> #topic Open Discussion
[16:16] <hallyn> anything?
[16:16] <rbasak> \o
[16:17] <rbasak> Just a note for meeting chairs, while they're all here.
[16:17] <rbasak> There's been some confusion lately about what needs to be done after a meeting.
[16:17] <Daviey> good thinking
[16:17] <hallyn> There's a good list in the Knowledgebase
[16:17] <rbasak> I just wanted to point out that the steps are enumerated at the bottom of https://wiki.ubuntu.com/ServerTeam/KnowledgeBase
[16:17] <rbasak> Right.
[16:17] <hallyn> yes, everyeone please follow that and fill in if anything is missing
[16:18] <hallyn> I think we've done a good job of keepign it uptodate
[16:18] <hallyn> thanks rbasak.  is there anything in particular that isn't being done?
[16:18] <hallyn> (regularly)
[16:18] <Daviey> specifically, "move yourself to the back" hasn't been done for a while it seems
[16:18] <rbasak> Sometimes minutes aren't being done also.
[16:19] <rbasak> It causes confusion in subsequent meetings, since action items go missing or are from older meetings that have already been resolved.
[16:19] <hallyn> i think it might help if we say it should be done by either thu or friday
[16:19] <rbasak> I think it's just due to all chairs not knowing that the process is documented.
[16:19] <rbasak> So now it's documented :)
[16:19] <hallyn> once it gets into monday, i think ppl feel that it's too late
[16:20] <hallyn> but i'll wait for someone else to recommend that :)  moving on?
[16:20] <Daviey> +1
[16:20] <rbasak> I think part of the problem is that individually we chair quite infrequently
[16:20] <hallyn> feels frequent to me :)
[16:20] <rbasak> A reminder at the end of the meeting might help. Perhaps we could add it as a standing action item in the agenda?
[16:20] <Daviey> rbasak: Fancy being the resident chair? :)
[16:21]  * hallyn takes a step back and admires rbasak's team spirit
[16:21] <hallyn> :)
[16:21] <rbasak> As resident chair, I delegate the task of doing this week's minutes to hallyn :-P
[16:21] <hallyn> rbasak: a remidner at most should consist of a pointer to the wiki page
[16:21] <Daviey> +1, super
[16:22] <Daviey> remember, moin minutes are generated courtesy of meetingology.
[16:22] <hallyn> yeah but i prefer manually generated, actually meaningful notes
[16:22] <hallyn> moin generated ones aren't actually helpful imo.  just to fill in a chekcmark in your todo list
[16:22] <Daviey> True.
[16:22] <rbasak> I use the moin notes as a starting point
[16:23] <rbasak> But one step at a time. Step 1: do something for the minutes. Anything.
[16:23] <Daviey> The chair can take care to word their action points suitably to make a more useful autogenerated moin output
[16:23] <hallyn> #action rbasak consider telling hallyn to add a todo item to meeting checklist to remind meeting chair about the wiki page checklist.
[16:23] <meetingology> ACTION: rbasak consider telling hallyn to add a todo item to meeting checklist to remind meeting chair about the wiki page checklist.
[16:23] <rbasak> I'll do it now :)
[16:23] <hallyn> INVALID
[16:23] <hallyn> all right, moving on,
[16:23] <hallyn> #topic Announce next meeting date, time and chair
[16:24] <Daviey> same time, same place?
[16:24] <hallyn> That'll be next tuesday, June 18 at 16:00 UTC in #ubuntu-meeting.
[16:24] <hallyn> thanks, everyone.
[16:24] <arosales> thanks for charing hallyn :-)
[16:24] <Daviey> thanks for chairing hallyn
[16:24] <hallyn> #endmeeting
[16:24] <meetingology> Meeting ended Tue Jun 11 16:24:32 2013 UTC.
[16:24] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-06-11-16.01.moin.txt
[16:24] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-06-11-16.01.html
[16:25] <rbasak> Thanks hallyn!
[17:00] <jsalisbury_> #startmeeting
[17:00] <meetingology> Meeting started Tue Jun 11 17:00:48 2013 UTC.  The chair is jsalisbury_. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[17:00] <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
[17:00] <jsalisbury_> ##
[17:00] <jsalisbury_> ## This is the Ubuntu Kernel Team weekly status meeting.
[17:00] <jsalisbury_> ##
[17:00] <jsalisbury_> [LINK] https://wiki.ubuntu.com/KernelTeam/Meeting
[17:00] <jsalisbury_> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Saucy
[17:01] <jsalisbury_> # Meeting Etiquette
[17:01] <jsalisbury_> #
[17:01] <jsalisbury_> # NOTE: '..' indicates that you are finished with your input.
[17:01] <jsalisbury_> #       'o/' indicates you have something to add (please wait until you are recognized)
[17:01] <jsalisbury_> Roll Call for Ubuntu Kernel Weekly Status Meeting
[17:01] <ppisati> o/
[17:01] <cking> o/
[17:01] <apw> o/
[17:01] <rtg_> o/
[17:01] <henrix> o/
[17:01] <kamal> o/
[17:01] <sforshee> o/
[17:01] <sconklin> o/
[17:01] <ogasawara> o/
[17:01] <jsalisbury_> [TOPIC] ARM Status (ppisati)
[17:01] <ppisati> Q/master: lp1176977 ("XFS instability on armhf under load") - turned out some
[17:01] <ppisati> xfs tests failure that i was experiencing were already present in 3.5.y
[17:01] <ppisati> vanilla for arm, so none of the backported patches were responsible for it.
[17:01] <ppisati> On the other hand, there's a new 100% reproducible hang while running
[17:01] <ppisati> tests/generic/0368. Still working on it, collecting patches, pinging upstream,
[17:01] <ppisati> etcetc.
[17:01] <ppisati> */highbank: lp1182637("cpu_offlining fails to run on ARM") - according to
[17:01] <ppisati> robherr this is due to a different u-boot that we are using, waiting for an
[17:01] <ppisati> update.
[17:02] <ppisati> S/master: did some testing of 3.10-rcX for omap[34], imx6 and vexpress, so
[17:02] <ppisati> far so good.
[17:02] <ppisati> ..
[17:02] <jsalisbury_> [TOPIC] Release Metrics and Incoming Bugs (jsalisbury)
[17:02] <jsalisbury_> Release metrics and incoming bug data can be reviewed at the following link:
[17:02] <jsalisbury_> [LINK] http://people.canonical.com/~kernel/reports/kt-meeting.txt
[17:02] <jsalisbury_> ..
[17:02] <jsalisbury_> [TOPIC] Milestone Targeted Work Items (ogasawara)
[17:02] <ogasawara> [LINK] https://launchpad.net/~canonical-kernel-distro-team/+upcomingwork
[17:02] <ogasawara> [LINK] http://status.ubuntu.com/ubuntu-s/canonical-kernel-distro-team.html
[17:02] <ogasawara> || ogasawara || foundations-1305-kernel || 1 work item ||
[17:02] <ogasawara> ||           || mobile-power-management || 1 work item ||
[17:02] <ogasawara> || sforshee  || foundations-1303-phablet-kernel-maintenance || 1 work item ||
[17:02] <ogasawara> || smb       || servercloud-s-virtstack || 1 work item  ||
[17:02] <ogasawara> ..
[17:03] <jsalisbury_> [TOPIC] Status: Saucy Development Kernel (ogasawara)
[17:03] <ogasawara> Our Saucy unstable branch has been rebased to the latest v3.10-rc5
[17:03] <ogasawara> upstream kernel.  We are still holding off on a v3.10 based upload due
[17:03] <ogasawara> to missing AUFS support as well as some DKMS package failures we would
[17:03] <ogasawara> like to resolve.  We have however gone ahead and rebased our Saucy master
[17:03] <ogasawara> branch to the recent v3.9.5 upstream stable and plan to upload that
[17:03] <ogasawara> today.
[17:03] <ogasawara> On the mobile front I'm hearing news that the container flip should
[17:03] <ogasawara> hopefully be happening this week.
[17:03] <ogasawara> Important upcoming dates:
[17:03] <ogasawara> Thurs June 20 - Alpha 1 (opt in)
[17:03] <ogasawara> ..
[17:04] <jsalisbury_> [TOPIC] Status: CVE's (sconklin)
[17:04] <sconklin> == 2013-06-11 (7 days) ==
[17:04] <sconklin> Currently we have 68 CVEs on our radar, with 9 CVEs added and 0 CVEs retired in the last week.
[17:04] <sconklin> See the CVE matrix for the current list:
[17:04] <sconklin> [LINK] http://people.canonical.com/~kernel/cve/pkg/ALL-linux.html
[17:04] <sconklin> Overall the backlog has decreased slightly this week:
[17:04] <sconklin> [LINK] http://people.canonical.com/~kernel/status/cve-metrics.txt
[17:04] <sconklin> [LINK] http://people.canonical.com/~kernel/cve/pkg/CVE-linux.txt
[17:04] <sconklin> ..
[17:04] <jsalisbury_> TOPIC] Status: Stable, Security, and Bugfix Kernel Updates - Raring/Quantal/Precise/Lucid/Hardy (bjf/henrix/sconklin)
[17:04] <sconklin> Status for the main kernels, until today (Jun. 11):
[17:04] <sconklin> *   Lucid - Awaiting Certification Testing;
[17:04] <sconklin> * Precise - Awaiting Certification Testing and Regression testing;
[17:04] <sconklin> * Quantal - Awaiting Certification Testing;
[17:04] <sconklin> * Raring  - Awaiting Certification Testing and Regression testing;
[17:04] <sconklin> Current opened tracking bugs details:
[17:04] <sconklin> * http://people.canonical.com/~kernel/reports/kernel-sru-workflow.html
[17:04] <sconklin> For SRUs, SRU report is a good source of information:
[17:04] <sconklin> * http://people.canonical.com/~kernel/reports/sru-report.html
[17:04] <sconklin> Future stable cadence cycles:
[17:04] <sconklin> * https://wiki.ubuntu.com/RaringRingtail/ReleaseInterlock
[17:04] <sconklin> ..
[17:05] <jsalisbury_> [TOPIC] Open Discussion or Questions? Raise your hand to be recognized (o/)
[17:05] <jsalisbury_> Thanks everyone
[17:05] <jsalisbury_> #endmeeting
[17:05] <meetingology> Meeting ended Tue Jun 11 17:05:35 2013 UTC.
[17:05] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-06-11-17.00.moin.txt
[17:05] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-06-11-17.00.html
[17:05] <kamal> thanks jsalisbury


 Going OK, and you?
[08:41] <seb128> I'm fine, the cold is starting being a bit less annoying \o/
[08:41] <oSoMoN> salut seb128
[08:41] <seb128> (which means I slept better)
[08:42] <seb128> oSoMoN, en forme? thanks for the libreoffice build fixes, seems to build fine now :)
[08:45] <seb128> oSoMoN, re bug #1801383 I think it's just removing that line https://bazaar.launchpad.net/~mozillateam/firefox/firefox.disco/view/head:/debian/apport/source_firefox.py.in#L1448 ... can you stage that in the vcs so it's in the next upload? or do you me to propose a mp for it? (also unsure but maybe the lines before can/should be dropped as well)
[08:46] <oSoMoN> seb128, la forme, oui! not sure this is the end of the story for libreoffice, there were some unit tests failures on amd64 yesterday, j_bicha retried it before I got a chance to investigate, let's see if it was just flakiness or something to really look into
[08:47] <seb128> :/
[08:47] <oSoMoN> seb128, on it (re bug #1801383)
[08:47] <seb128> the build log might still be available if you have the url?
[08:47] <seb128> oSoMoN, thx
[08:48] <oSoMoN> seb128, yeah, he sent me the URL, but at this point we're pretty far into the build already, so if it fails it will do so pretty soon, and if it doesn't then great
[08:48] <seb128> oSoMoN, it built on several arches, finger crossed that it works this time on amd64 as well :)
[08:49] <seb128> jamesh, hey, weekly summary reminder?
[08:49] <jamesh> seb128: on it.
[08:49] <oSoMoN> there's a trick: several arches ignore unit test failures… amd64 is the real test :/
[08:49] <seb128> jamesh, thx :)
[08:49] <didrocks> hey again seb128
[08:49] <seb128> oSoMoN, ah, I see, then let's see :/
[08:50] <willcooke> morning
[08:50] <seb128> hey willcooke, how are you today?
[08:51] <willcooke> I'm ok!  How about you seb128?
[08:51] <oSoMoN> 'morning willcooke
[08:51] <andyrock> morning
[08:51] <oSoMoN> hey andyrock
[08:52] <seb128> willcooke, I'm good, got a few annoying days with a cold which was bothering we enough that I couldn't sleep properly but this night/today starts being better
[08:52] <seb128> hey andyrock! had a good long w.e? ;)
[08:52] <andyrock> seb128: long w.e. \o/
[08:53] <andyrock> long = good
[08:53] <andyrock> seb128: what about you?
[08:53] <willcooke> seb128, get yourself a flu shot :) The boy will be brining all sorts of nasty stuff home with him :)
[08:55] <seb128> haha
[08:55] <seb128> I did that one once, I don't think I'm going to make it again
[08:55] <andyrock> you mean babies or flu shots?
[08:56] <popey> Morning desktoppers :)
[08:56] <andyrock> 😂
[08:56] <seb128> it made me sick the year I did it, and I never really got a flu otherwise (or maybe once now, this year in january for the trip to south africa)
[08:56] <seb128> andyrock, lol :)
[08:56] <seb128> hey popey
[08:56] <seb128> willcooke, but yeah, with the kid the situation might be different :)
[09:00] <oSoMoN> seb128, https://bazaar.launchpad.net/~mozillateam/firefox/firefox.disco/revision/1239 (and in the process of applying the same change to the branches for all supported series)
[09:00] <seb128> oSoMoN, thx!
[09:01] <seb128> oSoMoN, did you see my comment about the previous lines? unsure how useful alsa/network info are, I guess alsa ones are not a privacy problem in any case
[09:02] <seb128> oSoMoN, but in any case wifi is a known problem/what the bug was about so should be good enough
[09:03]  * duflu blinks
[09:03] <Laney> hey ho
[09:03] <duflu> Oh good morning willcooke, andyrock, popey, Laney
[09:04] <seb128> hey Laney! how are you today?
[09:04] <seb128> did you recover fine from yesterday morning?
[09:04] <Laney> seems fine
[09:04] <Laney> getting a cough/cold now though :<
[09:06] <seb128> :(
[09:06] <seb128> I hope it's not the same I got
[09:07] <Laney> yeah that sounds like it's been annoying
[09:07] <Laney> hopefully it just goes away
[09:08] <seb128> yeah
[09:11] <Laney> hey duflu too ;-)
[09:31] <seb128> oSoMoN, reading your weekly summary, you say that bug #1795169 is fixed in gnome-shell 3.31, it would probably be a good idea to update the bug to add/reassign to gnome-shell and maybe reference the commit so we can see if andyrock or Trevinho can look at backporting the fix to disco/cosmic/bionic?
[09:33] <oSoMoN> seb128, indeed, will do
[09:33] <seb128> thx
[09:37] <seb128> I hate those OSK flakyness issues around GTK_IM_MODULE
[09:38] <seb128> andyrock, do you still have work/fixes around that you wanted to land?
[10:01] <oSoMoN> seb128, I marked that bug (and another one) as duplicate of bug #1765304
[10:01] <oSoMoN> shall I nominate for bionic
[10:01] <oSoMoN> ?
[10:02] <seb128> oSoMoN, sure, thx
[10:06] <oSoMoN> done
[10:06] <seb128> great
[10:07] <seb128> seems like the fix also has been commited to 3-30 upstream, so should be easy to backport/SRU to cosmic
[10:12] <andyrock> seb128: the GTK_IM_MODULE is a different one
[10:12] <andyrock> basically on a wayland session we're still using the ibus im-module instead of the wayland one (text-input protocol)
[10:13] <andyrock> the password problem is due to the fact that gnome-shell uses ibus to track focus changes
[10:13] <andyrock> and ibus does not track password fields
[10:13] <andyrock> oSoMoN: ^^^
[10:14] <andyrock> gnome-shell used to have a different mechanism to track the cursor
[10:15] <andyrock> but osk is broken in x11 in general because usually the ibus method is disabled
[10:15] <oSoMoN> seb128, andyrock: the firefox problem with password fields only affects bionic, cosmic and disco are fine
[10:16] <seb128> oSoMoN, so it's not that gnome-shell commit that fixes it, since that's not in cosmic/disco
[10:16] <andyrock> yeah because 1765304 has nothing to do with osk?
[10:17] <andyrock> I thought we were talking about a different bug :)
[10:17] <oSoMoN> hrm, need to read the whole thing again, I'm confused now, just a minute, multitasking doesn't help
[10:18] <andyrock> I guess the problem is in ibus
[10:19] <andyrock> "because it only happens (in 18.04) when the environmental variable GTK_IM_MODULE is at its default value (which is "ibus")"
[10:19] <andyrock> that variable basically forces a gtk application to load the ibus module
[10:20] <andyrock> not loading that module seems to fix the issue, but what about languages that actually nead ibus?
[10:22] <andyrock> seb128: in a nutshell, yeah we should understand why we still have that enviroment variable
[10:22] <andyrock> seb128: g-s-d should be smart enough to enable ibus when required
[10:23] <seb128> right, I'm adding that to my backlog of things I would to discuss/get sorted out
[10:23] <seb128> but maybe not today, I guess you are busy or on other thing and same here (also on my way to lunch now)
[10:24] <seb128> andyrock, thx, also g-c-c/cosmic looks good but it needs a SRU bug (standard GNOME update one, see #1790876 for a minimalistic example)
[10:26] <andyrock> kk let me finish the fix for update-manager before
[10:26] <andyrock> I'm trying to understand how to properly do threading with glib and python
[10:27] <andyrock> they suggest to use the threading library but it's not clear how to handle cancellation properly
[10:28] <andyrock> seb128: is this good enough for SRU https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1804424
[10:28] <andyrock> or do I need to create a separate SRU bug?
[12:23] <acheronuk> libreoffice amd64 failed again :(
[12:58] <seb128> acheronuk, oSoMoN, libreoffice amd64 build :(
[12:58] <seb128> andyrock, I think it's best to have one for the version update
[13:18] <acheronuk> seb128: looks like the tests. those I have no idea on
[13:31] <andyrock> seb128: https://code.launchpad.net/~azzar1/update-manager/fix-lp-1805118/+merge/359621
[13:35] <seb128> andyrock, oh, nice one. Is that different from what you were talking about earlier or did it turn out to be simpler that what you were first poking at?
[13:47] <andyrock> seb128: simpler
[13:48] <seb128> \o/
[13:48] <andyrock> nothing to do with threading and bla bla
[13:48] <andyrock> looked like it
[13:49] <seb128> heh, I like it better this way :I've to day :)
[13:49] <seb128> say
[13:57] <seb128> jamesh, weekly summary re-reminder?
[14:07] <andyrock> seb128: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1805441
[14:07] <seb128> andyrock, thx
[14:07] <andyrock> seb128: let me update the changelog entry too
[14:09] <seb128> andyrock, great work on the description! :) (also probably no need to do that much of a good job for a standard GNOME update next time, but it's up to you)
[14:10] <andyrock> I followed La_ney's standards
[14:10] <andyrock> :D
[14:10] <seb128> :)
[14:21] <willcooke> kenvandine, we lost you
[14:30] <willcooke> #startmeeting Desktop Team Meeting 2018-11-27
[14:30] <meetingology> Meeting started Tue Nov 27 14:30:37 2018 UTC.  The chair is willcooke. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[14:30] <meetingology> Available commands: action commands idea info link nick
[14:30] <willcooke> Hi all
[14:30] <Nafallo> o/
[14:30] <willcooke> Roll call: andyrock, dgadomski, didrocks, duflu (out), jbicha, jamesh (out), jibel, kenvandine, laney, oSoMoN, seb128, tkamppeter, trevinho, robert_ancell (out)
[14:30] <seb128> _o/
[14:30] <tseliot> o/
[14:30] <jibel> o/
[14:30] <kenvandine> o/
[14:31] <willcooke> Just give people a couple of mins
[14:31] <tjaalton> \o
[14:31] <didrocks> hey
[14:32] <willcooke> Oki
[14:32] <willcooke> So rls bug updates from the bullet list looks pretty good.
[14:33] <oSoMoN> o/
[14:33] <willcooke> So we can go through the incoming, then hand over to laney for the other bugs, then AOB
[14:33] <willcooke> bb incoming
[14:33] <willcooke> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-bb-incoming-bug-tasks.html
[14:34] <willcooke> That url-dispatcher one as always, but nothing new
[14:34] <seb128> I'm going to get that one of the list
[14:34] <willcooke> should I assign one of the tasks to you?
[14:35] <andyrock> o/
[14:35] <willcooke> or all of them, or none of them>?
[14:35] <willcooke> or nothing
[14:35] <seb128> none, just wontfix for that serie
[14:35] <willcooke> ack
[14:35] <seb128> the initial problem was worked around
[14:35] <willcooke> thanks seb128
[14:35] <seb128> so that's non important to fix the remaining in bionic
[14:35] <seb128> np
[14:35] <willcooke> cc incoming: http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-cc-incoming-bug-tasks.html
[14:35] <willcooke> 1 bug, twice.  Assigned to tjaalton.
[14:35] <willcooke> Nothing new
[14:35] <seb128> he has a package in a ppa for testing
[14:36] <willcooke> cool
[14:36] <tjaalton> yeah
[14:36] <seb128> if anyone feels like giving it a try (I might, just failing to get to that point of my todo atm)
[14:36] <tjaalton> marked it 'incomplete' now
[14:36] <tjaalton> was only for disco
[14:36] <willcooke> I will spin up a VM this afternoon
[14:37] <willcooke> dd-incoming: http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-dd-incoming-bug-tasks.html
[14:37] <willcooke> 2 bugs.
[14:37] <Laney> (we should be deleting incoming when nominating, that cosmic one was already accepted)
[14:38] <andyrock> removed
[14:38] <willcooke> thanks Laney
[14:38] <willcooke> I went to change it but you already had
[14:38] <Laney> :3
[14:38] <willcooke> :)
[14:38] <seb128> I though the report was smart enough to not list things with an accepted serie targetting, seems not :/
[14:38] <willcooke> https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1805200
[14:39] <willcooke> assigned, and targetted so I assume it's accepted too
[14:39] <willcooke> oh
[14:39]  * willcooke reads it
[14:39] <willcooke> ah right
[14:39] <willcooke> oki, we should talk about it then
[14:39] <willcooke> I would be +1 for accepting since we need it for fractional scaling under x
[14:39] <seb128> +1
[14:40] <willcooke> anyone against?
[14:40] <kenvandine> +1
[14:40] <Laney> tjaalton accepted it himself already, not much to say there I don't think
[14:40] <willcooke> oki, removed the tag
[14:40] <seb128> Marco got upstream comments now which is good :)
[14:40] <willcooke> \o/
[14:41] <willcooke> Here ends the bug review.  Not too shabby
[14:41] <willcooke> Laney, over to you
[14:42] <Laney> yeh
[14:42] <Laney> so
[14:42] <Laney> #link https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses_by_team.html#desktop-packages
[14:42] <Laney> idea is to see if there's anything on there that should be worked on
[14:43] <Laney> I saw seb128 asked foundations to look at that n-m failure caused by dnsmasq, seems sensible
[14:43] <willcooke> +1
[14:44] <Laney> apart from that...
[14:44] <Laney> jbicha: did you want to say something about that sane thing or tracker?
[14:45] <Laney> there's some history with those two that I don't fully know
[14:46] <Laney> maybe we can talk about those later on
[14:46] <willcooke> yeah
[14:47] <Laney> so I think v4l-utils and at-spi2-core could do with being handled
[14:47] <Laney> udisks2 just needs the hint updated
[14:47] <Laney> (done)
[14:48] <seb128> the at-spi2-core tests seem flackyness, I retried
[14:48] <seb128> (first was blocked on depwait from meson, but that got cleared yesterday)
[14:48] <seb128> or said differently I'm looking at that one
[14:48] <seb128> v4l-utils seems a real build issue, I just looked at debian/upstream, no obvious report/fix there
[14:49] <Laney> thx
[14:49] <seb128> does anyone to have a look to that one?
[14:49] <Laney> maybe we can ask foundations if anyone can look at apport to de-flake the tests
[14:49] <jbicha> sane-backends probably needs a transitional package added in Ubuntu & Debian
[14:50] <Laney> k, are you handling it?
[14:50]  * Laney didn't follow that situation and is happy to not know about it :-)
[14:50] <jbicha> see LP: #1804550 and Debian bug 913346
[14:51] <seb128> @apport, I can do that, but the failing tests had "WARNING: cannot connect to: https://api.launchpad.net/devel.." so I wonder if that was a temp infra problem
[14:51] <jbicha> https://gitlab.gnome.org/GNOME/tracker/issues/61 & https://gitlab.gnome.org/GNOME/tracker/issues/59 are blocking the autopkgtests
[14:51] <gitbot> GNOME issue 61 in tracker "tracker-miner-fs test: Parent recursive/4 not indexed yet" [Opened]
[14:51] <gitbot> GNOME issue 59 in tracker "functional-16-collation test failures" [Opened]
[14:51] <Laney> http://autopkgtest.ubuntu.com/packages/apport/disco/amd64
[14:51] <Laney> they probably want to handle it being unreliable in the tests / apport itself
[14:51] <jbicha> the tracker autopkgtest failures are fallout from my switching the package to meson
[14:52] <seb128> Laney, fair enough
[14:52] <seb128> I take that item as well
[14:52] <jbicha> I'm not handling sane-backends right now
[14:53] <Laney> k, well that can sit there then
[14:53] <jbicha> I don't think tracker being stuck is blocking anything yet
[14:54] <Laney> if you can work with upstream on those tracker failures please
[14:54] <Laney> not sure it was required to ping me about debootstrap, I'm sure you can manage that, but if you really can't then I can help I guess
[14:54] <Laney> that's the end
[14:54] <willcooke> thanks Laney
[14:54] <Laney> except someone to look at https://launchpad.net/ubuntu/+source/v4l-utils/1.16.1-2/+build/15637736 - not super urgent but we should do it at some point
[14:54] <willcooke> Do we still need a volunteer for v4l-utils
[14:55] <willcooke> ?
[14:55] <willcooke> ha
[14:55] <willcooke> yes
[14:56] <willcooke> We'll see if we can find a volunteer by EOW
[14:56] <seb128> or wait, I don't think it's blocking anything else atm
[14:56] <willcooke> kk
[14:56] <willcooke> #topic AOB
[14:57] <willcooke> popey, you had one
[14:57] <popey> ya
[14:57] <seb128> unsure how to handle best those non urgent items, if we keep asking, or just force an owner
[14:57] <popey> I thought you might appreciate an "Ubuntu Desktop in the wild".
[14:57] <popey> "CuriousMarc" YouTube channel has a series of videos where they're repairing the Apollo Guidance Computer
[14:57] <Laney> should eventually assign someone
[14:57] <popey> I keep seeing Ubuntu pop up in it.
[14:57] <popey> Mike Stewart - one of the experts doing the repair (and actual Space Engineer for SpaceX) uses Ubuntu on a ThinkPad. :)
[14:57] <oSoMoN> nice
[14:57] <popey> https://www.youtube.com/watch?v=2KSahAoOLdU is episode 1
[14:57] <popey> Worth a watch if you like historic electronics, space, or seeing random 50 year-old document scans on Ubuntu :)
[14:57] <popey> https://usercontent.irccloud-cdn.com/file/6H5u76yG/Screenshot%20from%202018-11-27%2014-31-10.png
[14:57] <kenvandine> cool
[14:58] <popey> EOM
[14:58] <seb128> nice one popey :)
[14:58] <willcooke> seb128, Laney - yeah, if it's still hanging around next week then we can assign someone.  Is that sort of timescale acceptable, or does it need attention in days?
[14:59] <seb128> imho waiting a week is fine, but then we can as well find an assignee now and state that it can be looked at when possible/not as an high priority
[15:01] <Laney> you guys think about who you might want to assign before the next meeting :-)
[15:01] <Laney> looks like it's around gl stuff
[15:01] <willcooke> kk, lets look more in to it
[15:01] <willcooke> any more business?
[15:02] <didrocks> nothing for me
[15:02] <willcooke> sounds like not
[15:02] <andyrock> nope
[15:02] <willcooke> #endmeeting
[15:02] <meetingology> Meeting ended Tue Nov 27 15:02:35 2018 UTC.
[15:02] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-desktop/2018/ubuntu-desktop.2018-11-27-14.30.moin.txt
[15:02] <willcooke> thanks all
[15:02] <willcooke> I see the gl errors now
[15:02] <andyrock> thx
[15:03] <didrocks> thx
[15:03] <oSoMoN> thanks
[15:03] <willcooke> perhaps something to do with qt too
[15:04] <seb128> thx!
[15:06] <seb128> andyrock, I sponsored your update-manager fix to disco and handled the bionic SRU as well, g-c-c next :)
[15:06] <andyrock> thx!
[15:06] <andyrock> seb128: I'm preparing dash-to-dock
[15:06] <andyrock> I need to review some fixes from Marco before
[15:07] <seb128> k, thx
[15:10] <willcooke> andyrock, oooooh, does your dash-to-dock update include: https://github.com/micheleg/dash-to-dock/issues/639 by any chance?
[15:10] <gitbot> micheleg issue 639 in dash-to-dock "[request] Do not reorder window thumbnails after clicking on them" [Enhancement, Open]
[15:11] <willcooke> oh, actually, ignore that, seems its still in a branch, and would probably need config UI which we dont have yet
[15:11] <andyrock> mmm I was not planning to sync dash-to-dock with ubuntu-dock
[15:11] <willcooke> yeah, no worries
[15:17] <seb128> andyrock, also that didn't land to dash-to-dock, it's just a branch
[15:17] <willcooke> that v4l-utils is only arm64
[15:17] <seb128> willcooke, it would be useful if you could reach out to Michel maybe via email to ask if we can do anything to help that one landing or if he would be fine if we distro patched it
[15:18] <willcooke> seb128, good idea, will do
[15:18] <seb128> thx
[15:19] <seb128> willcooke, @v4l-utils, yeah, could be specific to the arch or could be that some other package was updated before it built and other archs would hit the same problem now...
[15:23] <willcooke> ahh
[15:23] <willcooke> I found mention of a patch that fixed similar errors, but was a year old
[15:30] <seb128> andyrock, that g-c-c segfault mentioned in the SRU changelog, the bug was no SRU compliant, I fixed that for you now. But the segfault from the bt/change is in the power code but you description states "Fix crash in region panel" so I just want to check there is no confusion/wrong bug being referenced
[15:30] <andyrock> there are two crashes in the region panel
[15:31] <andyrock> let me check again
[15:32] <andyrock> oh yeah it's power
[15:32] <andyrock> fixing
[15:32] <andyrock> sorry about that
[15:32] <seb128> no worry
[15:32] <seb128> thx :)
[15:39] <seb128> andyrock, let me know when you are done amending your changelog
[15:45] <andyrock> seb128: done!
[15:45] <seb128> andyrock, thx!
[15:45] <andyrock> I also divided the commits again
[15:46] <seb128> andyrock, can we do without the pq-rebasing changes?
[15:47] <andyrock> why?
[15:47] <seb128> SRU team doesn't like diff "noise"
[15:47] <seb128> makes the review harder
[15:47] <andyrock> kk
[15:47] <seb128> thx
[15:47] <andyrock> let me check which patches I need to drop
[15:47] <seb128> sorry about that, I though I mentioned it at first when we discussed that SRU
[15:48] <seb128> well, no need to drop things
[15:48] <seb128> just discard the useless pq changes of the day
[15:49] <andyrock> mmm there are quilt patches that need to be removed because already upstream
[15:49] <andyrock> only one iirc
[15:50] <seb128> that's fine, just git rm and edit the serie?
[15:50] <seb128> I mean no need to use pq for that right?
[15:51] <andyrock> yep
[15:51] <andyrock> I mean there was just a couple of lines more
[15:52] <andyrock> but if SRU team does not like them :P
[15:55] <andyrock> seb128: https://git.launchpad.net/~azzar1/ubuntu/+source/gnome-control-center/commit/?id=306a080877c0d8e1e6719496fa05fe3d5670debc
[15:55] <andyrock> I building it just to make sure it works
[15:56] <seb128> andyrock, great, thx
[16:04] <andyrock> seb128: it builds
[16:06] <seb128> andyrock, ship it! :)
[16:06] <andyrock> I pushed it already
[16:08] <andyrock> seb128: do you know if there has been any progress about removing ubuntu-one reviews from gnome-software upstream ?
[16:09] <seb128> I don't know about that one, maybe kenvandine does
[16:09] <seb128> I read that they enabled odrs reviews in the snap
[16:09] <seb128> but unsure where we are for Ubuntu/deb
[16:09] <kenvandine> it's in the snap-store snap
[16:10] <kenvandine> i'll check the deb
[16:12] <kenvandine> seb128: odrs is enabled in disco but so is ubuntu-reviews
[16:12] <kenvandine> i'll talk to robert
[16:12] <seb128> andyrock, minor but you can't re-use the same version between series, I change g-c-c to be 3.30.2-1ubuntu<IP_ADDRESS>
[16:13] <seb128> kenvandine, thx
[16:13] <seb128> andyrock, you want it disabled because it's blocking other work right?
[16:14] <andyrock> kenvandine, seb128: yeah we can't merge the work I proposed to use gnome-online-accounts in gnome-software until the reviews plugin is still there
[16:15] <kenvandine> we should completely remove it upstream as the servers are going away
[16:15] <seb128> andyrock, kenvandine, maybe best to use email to ask a status update from Robert?
[16:16] <seb128> kenvandine, or do you just talk to him and keep us updated tomorrow?
[16:16] <kenvandine> i will talk to him this afternoon
[16:17] <seb128> thx
[16:17] <kenvandine> np
[16:18] <andyrock> seb128: thx for the change. I didn't know that
[16:19] <seb128> andyrock, np, uploaded now!
[16:56] <Laney> https://paste.ubuntu.com/p/DCkJgcCw6g/
[16:56] <Laney> think that'll fix v4l thingy
[16:56] <willcooke> typo on line 17
[16:57] <willcooke> also: thank you!
[16:57] <Laney> line 17 is context
[16:57] <willcooke> ohhh
[16:57] <willcooke> right
[17:01] <Laney> that diff is incomplete though, I missed the third line of the depends and the second alternate in the first line
[17:02] <Laney> is building https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3538/+packages
[17:11] <andyrock> Trevinho: https://github.com/micheleg/dash-to-dock/pull/838
[17:11] <gitbot> micheleg issue (Pull request) 838 in dash-to-dock "docking: Fix leaking signal connection " [Open]
[17:11] <andyrock> Trevinho: I updated the patch
[17:11] <andyrock> Trevinho: I'm also taking a look at https://github.com/micheleg/dash-to-dock/issues/835
[17:11] <gitbot> micheleg issue 835 in dash-to-dock "Anyone maintaining this issue tracker?" [Open]
[17:12] <Trevinho> good thanks
[17:12] <andyrock> sorry wrong link
[17:13] <andyrock> Trevinho: also if you can merge it in the ubuntu-dock branch too
[17:13] <andyrock> Trevinho: https://github.com/micheleg/dash-to-dock/pull/825
[17:13] <gitbot> micheleg issue (Pull request) 825 in dash-to-dock "dash, docking: remove Shell.GenericContainer" [Open]
[17:13] <andyrock> would this break live-updating ?
[17:13] <andyrock> we don't care about live-updating in ubuntu-dock
[17:13] <Trevinho> live updating... you mean?
[17:13] <Trevinho> ahhhh
[17:13] <Trevinho> ok
[17:14] <Trevinho> yeah, should not to be honest, but in any case yes... I've the branch locally already I think
[17:14] <Trevinho> I push that to Ubuntu
[17:14] <andyrock> https://bugzilla.gnome.org/show_bug.cgi?id=688973
[17:15] <andyrock> wondering if that has been fixed
[17:22] <Trevinho> andyrock: pushed https://github.com/micheleg/dash-to-dock/commits/ubuntu-dock
[17:23] <andyrock> ah you pushed your change, I meant mine :D
[17:24] <Trevinho> ouch :D
[17:24] <andyrock> Trevinho: ^^^
[17:24] <Trevinho> well, that should be there anyways, I'll do both
[17:24] <andyrock> we're going to increase the delta between ubuntu-dock and dash-to-dock
[17:25] <andyrock> seb128: wdyt?
[17:25] <Trevinho> said that... both changes are proposed in both branches
[17:25] <andyrock> a bit of context: without this change dash-to-dock/ubuntu-dock does not work on gnome-shell upstream
[17:25] <Trevinho> and i theory I could merge upstream too, but don't want to overstep
[17:25] <Trevinho> (soon to be 3.32)
[17:26] <andyrock> and last commit on dash-to-dock was months ago :(
[17:26] <andyrock> if we all agree I can prepare the upload right now
[17:30] <Trevinho> andyrock: I've synced the changelog already https://github.com/micheleg/dash-to-dock/commits/ubuntu-dock so just need to prepare the src
[17:32] <Trevinho> on other lands, anyone looked at https://bileto.ubuntu.com/#/ticket/3519 yet?
[17:32] <Trevinho> And this needs sponsor too https://bileto.ubuntu.com/#/ticket/3448
[18:39] <willcooke> bon nuit
[18:50] <cyphermox> hey, is there a way I can deactivate the on-screen keyboard from ever showing up when I use a touch-screen?
[18:51] <sarnold> apt-get purge nano is the first thing I do on new ubuntu / debian systems.. it might be overkill but might help :)
[18:52] <sarnold> (or is it pico I purge? I can never remember which is which)
[18:54] <cyphermox> we do ship nano by default in standard
[20:08] <kenvandine> andyrock: robert_ancell is going to submit an MR for gnome-software removing the ubuntu-reviews plugin
[20:08] <andyrock> thx
[20:16] <robert_ancell> andyrock, kenvandine https://gitlab.gnome.org/GNOME/gnome-software/merge_requests/145
[20:16] <gitbot> GNOME issue (Merge request) 145 in gnome-software "ubuntu-reviews: Retire Ubuntu Reviews plugin" [Opened]
[20:16] <robert_ancell> andyrock, is the ubuntuone plugin only used by the Ubuntu reviews plugin?
[20:17] <andyrock> yep!
[20:17] <andyrock> snap is using is own auth
[20:38] <xnox><EMAIL_ADDRESS>[20:38] <xnox> looks like g-ir-scanner is failing on ppc64el in disco?
[20:38] <xnox> search for:
[20:39] <xnox> FAILED: gir/dep1/MesonDep1-1.0.gir
[22:35] <seb128> Trevinho, andyrock, having ubuntu-dock/dash-to-dock diverging if it's temporary should be ok
[22:35] <seb128> robert_ancell, andyrock, kenvandine, did we migrate ubuntu proper (the archive deb) to use ODRS now?
[22:35] <robert_ancell> seb128, not yet
[22:36] <robert_ancell> seb128, just the snap store version
[22:36] <seb128> robert_ancell, k, the description of that mp made me unsure :)
[22:36] <robert_ancell> seb128, yeah, I thought I'd keep it simple for upstream rather than go into all the gory details of where we're at
[22:36] <seb128> but that's what I though, I didn't see that change uploaded/in the deb
[22:37] <seb128> k


[09:40] <superfly> zquish102: it's fine, my wife is american, and we're going to be staying with her family for the first bit, so we're good
[09:41] <superfly> good morning inetpro ;)
[12:01] <Kilos> hi inetpro superfly zquish102 paddatrapper and others
[12:39] <gremble> Good afternoon
[18:27] <superfly> o/
[18:31] <kulelu88> hey superfly .
[18:32] <superfly> hi kulelu88
[18:32] <kulelu88> howzit? family landed safely?
[18:32] <superfly> yup, they're safe and sound
[18:32] <superfly> all bags intact, all sanity intact
[18:33] <superfly> kulelu88: do you like puzzle games?
[18:33] <kulelu88> I wouldn't doubt bag safety at a decent airliner. SAA, I'm not so sure
[18:33] <superfly> Qatar and American
[18:33] <kulelu88> yep, you have a link?
[18:34] <superfly> sorta, let me get it for you
[18:35] <superfly> https://play.google.com/store/apps/details?id=com.FireproofStudios.TheRoom
[18:38] <kulelu88> aah, I don't own a device that can run that :'D
[18:38] <superfly> pity, that's an amazing game
[18:40] <kulelu88> superfly: you seen this: http://www.replicant.us/
[18:52] <superfly> kulelu88: I think I've seen that before
[18:53] <kulelu88> I'd preferably like to get an ubuntu phone though
[20:15] <zquish102> superfly: I guess you need to buy a lot of electronics now that you in US. A good site to use and wait for a deal is slickdeals.net
[20:15] <superfly> zquish102: I'm not there quite yet
[20:16] <superfly> still waiting for my visa
[20:17] <zquish102> oh, ok :) that is still the site I put a deal watch on before i buy something (also buy stuff i don't really need because it is 60% off!)
[20:22] <zquish102> wtf, bf1 is a 40 gig dl


[04:55] <noalternative> How do you change the wallpaper clock to 12 hour time instead of military time?
[04:56] <noalternative> Does anyone here know.  PM me if I am not around for an answer.
[04:57] <noalternative> Also how do you make file associations in in budgie's file manager, when some of the apps are not mentioned?
[04:57] <noalternative> particularly snap apps have trouble associating
[22:04] <noalternative> How do you change the wallpaper clock to 12 hour time instead of military time?
[22:06] <noalternative> nswer.
[22:06] <noalternative> [23:57:09] Also how do you make file associations in in budgie's file manager, when some of the apps are not mentioned?
[22:07] <noalternative> particularly snap apps have trouble associatin
[22:46] <fossfreedom> noalternative, budgie-desktop-settings - click on the showtime applet and you can change the time format
[22:48] <fossfreedom> budgie's file manager is Files (Nautilus) in 18.04 and 18.10 - so any GNOME answer is applicable here.
[22:48] <fossfreedom> not sure on snap's but the experts for snaps hang out here https://forum.snapcraft.io/