[05:27] <didrocks> good morning
[05:31] <duflu> Morning didrocks
[05:38] <didrocks> hey duflu
[05:47] <duflu> didrocks, do you use Nvidia by any chance?
[05:48] <duflu> I need to check what other /devices other Nvidia machines have
[05:49] <jibel> hi all
[05:49] <jibel> duflu, I do what do you need?
[05:50] <duflu> jibel, can you please tell me the driver version, what /dev/nv* you have and what kernel command line you use? :)
[05:50] <duflu> Also good morning
[05:51] <jibel> $ ls /dev/nv*
[05:51] <jibel> /dev/nvidia0  /dev/nvidiactl  /dev/nvidia-modeset  /dev/nvidia-uvm  /dev/nvidia-uvm-tools  /dev/nvme0  /dev/nvme0n1  /dev/nvme0n1p1  /dev/nvme0n1p2
[05:52] <jibel> you can ignore nvme*
[05:52] <jibel> $ cat /proc/cmdline
[05:52] <jibel> BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic root=UUID=fb5bb713-8b3f-4979-ab03-db3bb9c5ec45 ro quiet splash vt.handoff=1
[05:52] <jibel> duflu, ^
[05:53] <duflu> jibel, thanks. That's what I thought. Unfortunately a couple of the devices don't appear till late :/
[05:54] <didrocks> duflu: I have an intel/nvidia card, indeed
[05:55] <didrocks> /dev/nvidia0  /dev/nvidiactl  /dev/nvidia-modeset  /dev/nvidia-uvm  /dev/nvidia-uvm-tools
[05:55] <didrocks> BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic root=UUID=699713f7-86ae-4f11-a032-be77e24bd4e1 ro quiet splash vt.handoff=1
[05:55] <duflu> Thanks. Unfortunately the dev list is different during boot
[07:01] <oSoMoN> good morning desktoppers
[07:01] <duflu> Hi oSoMoN
[07:01] <oSoMoN> hi duflu
[07:01] <Wimpress> o/
[07:01] <oSoMoN> hey Wimpress
[07:13] <didrocks> hey oSoMoN
[07:13] <didrocks> morning Wimpress
[07:14] <oSoMoN> salut didrocks
[07:15] <duflu> Hi Wimpress
[07:17] <duflu>      \⚇
[07:17] <marcustomlinson> morning WimoSoflubelrocks
[07:18] <oSoMoN> morning marcustomlinson
[07:18] <duflu> Erm, hi marcustomlinson
[07:18] <marcustomlinson> :)
[07:59] <willcooke> moin
[08:02] <Laney> moin
[08:03] <duflu> Morning willcooke and Laney
[08:04] <didrocks> hey willcooke, Laney
[08:07] <seb128> hey willcooke Laney, how is u.k today?
[08:07] <seb128> Laney, had a nice long w.e?
[08:07] <seb128> hey again other desktopers :)
[08:07] <oSoMoN> hey seb128
[08:07] <oSoMoN> morning willcooke, Laney
[08:09] <didrocks> hey seb128
[08:09] <seb128> lut oSoMoN didrocks, en forme ?
[08:09] <didrocks> ça va, et toi ?
[08:09] <Laney> hey duflu didrocks seb128 oSoMoN
[08:09] <willcooke> seb128, the sun is out, but thunderstorms forecast
[08:09] <seb128> ça va !
[08:10] <marcustomlinson> morning willaney128
[08:10] <oSoMoN> seb128, ça va, et toi?
[08:10] <Laney> weekend was very good yes!
[08:10] <seb128> nice
[08:10] <Laney> lots of being a pirate
[08:10] <seb128> oSoMoN, ça va bien :)
[08:11] <seb128> Laney, did you drink rhum on a boat and found treasures? ;)
[08:13] <Laney> yep, we plundered the spanish fleet
[08:13] <willcooke> :DD
[08:13] <Laney> hey marcustomlinson
[08:14] <Laney> basically it was about 20 pubs with different groups in them
[08:14] <Laney> and lots and LOTS of buskers, including us
[08:19] <oSoMoN> sounds fun!
[08:21] <seb128> indeed :)
[08:22] <lis> good morning everyone :)
[08:22] <seb128> didrocks, I don't remember the details, but the preference with go is to bundle depends rather than using a proper depends system? those vendors dir with the world dumped in it makes reviewing tedious :-/
[08:22] <didrocks> seb128: yes, that's the preferred way, vendorized everything (as not all deps are in main)
[08:22] <seb128> hey lis! 2 consecutive days of activity on the desktop channel :)
[08:23] <didrocks> hey lis
[08:23] <lis> seb128: i miss you guys :)
[08:23] <seb128> didrocks, well that component isn't going in main is it? (since it's only test it can be in universe right?)
[08:23] <seb128> lis, :-)
[08:23] <lis> also, i'm writing glib stuff now, so i'm feeling a bit desktopy :)
[08:23] <didrocks> seb128: this one won't as it's only autopkgtests, however, we don't have all deps packaged separately
[08:24] <RAOF> 😀
[08:24] <lis> RAOF: hey :)
[08:24] <seb128> didrocks, ok, I see, I keep reviewing then :-/ thx
[08:24] <RAOF> Hey lis !
[08:24] <seb128> hey RAOF
[08:24] <RAOF> Hey seb128 !
[08:25] <RAOF> Hey didrocks, Laney, duflu and everyone!
[08:25] <duflu> Hi RAOF. After-dinnering again?
[08:27] <RAOF> Yah. It's a big night of meetings for me! 9pm Mir, 5:30am SRU. It'll be rad!
[08:28] <didrocks> hey RAOF ;)
[08:38] <seb128> didrocks, NEWed, sorry for the delay in the review (I did finally start yesterday but the vendor thing make it took even longer at the end :-/)
[08:38] <didrocks> seb128: thx! I'll let you binary NEWing as well if you want to double check?
[08:38] <seb128> k
[13:06] <oSoMoN> kenvandine, I believe you're familiar with what it takes to have a snap preseeded on images? ubuntu kylin needs chromium, and vorlon mentioned I needed to open and close a stable/ubuntu-19.10 channel for the snap, is that all that's needed?
[13:06] <oSoMoN> (that's bug #1832656)
[13:07] <kenvandine> Open and close the channel plus add it to the seed
[13:08] <kenvandine> Looks like they seeded it already
[13:08] <kenvandine> So just need the channel
[13:11] <oSoMoN> kenvandine, a bit of a n00b question: do I need to release for all 4 supported architectures in that new channel, or just one?
[13:11] <kenvandine> Yes
[13:11] <kenvandine> All 4
[13:11] <oSoMoN> ok
[13:21] <oSoMoN> kenvandine, done, I release the 4 stable revisions to that channel and closed it afterwards, now I can't see it list anywhere, I suppose that's expected?
[13:21] <seb128> oSoMoN, I hadn't paid attention to the chromium snap transition post on discourse, quite some feedback there, thanks for keeping up with user comments!
[13:21] <seb128> kenvandine, tkamppeter, one week later, what's the status of fixing the n-m autopkgtests?
[13:21] <oSoMoN> seb128, I haven't fully caught up yet, that's the bad thing with long week-ends away from the computer
[13:22] <seb128> haha
[13:22] <seb128> there isn't much you didn't address from what I can see
[13:22] <seb128> mostly haters liking to rant about world changing
[13:23] <oSoMoN> seb128, I think that for this transition to be really successful we need to pay close attention to user feedback and fix whatever problems they find as early as possible
[13:23] <seb128> right
[13:23] <oSoMoN> yeah, the inevitable rants of people afraid of change
[13:24] <oSoMoN> but even those need to be addressed politely
[13:24] <oSoMoN> there are valid concerns
[13:27] <seb128> indeed
[13:28] <kenvandine> oSoMoN: yup
[13:30] <seb128> oh, it's meeting time!
[13:31] <seb128> sorry, was caught up in a discussion
[13:31] <seb128> #startmeeting Desktop Team Meeting - 2019-06-18
[13:31] <meetingology> Meeting started Tue Jun 18 13:31:27 2019 UTC.  The chair is seb128. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[13:31] <meetingology> Available commands: action commands idea info link nick
[13:31] <seb128> Roll call: didrocks, duflu (out), jamesh (out), jibel, kenvandine, laney, marcustomlinson, oSoMoN, tkamppeter, trevinho, robert_ancell (out)
[13:31] <marcustomlinson> \o
[13:32] <Laney> hi
[13:32] <oSoMoN> o/
[13:32] <seb128> k, we have some people around so let's get started :)
[13:32] <kenvandine> \o
[13:32] <seb128> #topic rls-bb-bugs
[13:33] <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-bb-incoming-bug-tasks.html
[13:33] <seb128> desktop free
[13:33] <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-bb-tracking-bug-tasks.html
[13:33] <Trevinho> hey
[13:34] <seb128> still the same japense era things there, that needs to be sorted out but hasn't been yet, sorry about that
[13:34] <seb128> otherwise the other items I've sorted out after lunch but the report didn't refresh yet
[13:34] <seb128> so we can ignore them
[13:34] <seb128> #topic rls-cc-bugs
[13:34] <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-cc-incoming-bug-tasks.html
[13:34] <seb128> desktop free
[13:35] <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-cc-tracking-bug-tasks.html
[13:35] <seb128> same era bug and that's it
[13:35] <seb128> (I also wontfixed some lines, mostly the gnome-software ones from Robert, I don't think we are going to see another cosmic SRU for it)
[13:36] <seb128> kenvandine, ^ fyi, would be nice to remind Robert to not let his assigned bugs go stalled
[13:36] <seb128> #topic rls-dd-bugs
[13:36] <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-dd-incoming-bug-tasks.html
[13:36] <seb128> desktop free too
[13:37] <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-dd-tracking-bug-tasks.html
[13:37] <seb128> same era bug
[13:37] <seb128> #topic rls-ee-bugs
[13:37] <tseliot> o/
[13:37] <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-ee-incoming-bug-tasks.html
[13:37] <seb128> desktop free
[13:37] <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-ee-tracking-bug-tasks.html
[13:37] <seb128> that's in shape
[13:37] <seb128> #topic update_excuses_by_team.html#desktop-packages
[13:37] <seb128> https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses_by_team.html#desktop-packages
[13:38] <seb128> Laney, it's yours :)
[13:38] <Laney> thx
[13:38] <Laney> probably going to need to MIR lmdb, I will handle that one
[13:38] <seb128> thx Laney
[13:38] <Laney> otherwise just the NM thing
[13:38] <Laney> ...
[13:39] <seb128> kenvandine said that Till starting poking at it now, he hadn't understood that he was owning it until the discussion at the previous meeting apparently
[13:39] <seb128> so hopefully that does get sorted out this week now
[13:39] <kenvandine> tkamppeter: ^^
[13:39] <seb128> thx Laney!
[13:39] <seb128> #topic AOB
[13:39] <seb128> other topics?
[13:40] <tkamppeter> Yes, I have alreasy reproduced it and now I was looking through the nm.py code to find out what it is doing.
[13:41] <seb128> thx tkamppeter, let us know how it goes and it you need help
[13:41] <seb128> 30 seconds for other topics
[13:41] <Laney> the 1.10.14 update, would be good to have a status report on that next week maybe?
[13:42] <seb128> indeed, I think we mostly dropped the ball again on that :-/
[13:42] <seb128> tkamppeter, kenvandine, ^ can we get that?
[13:42] <Trevinho> Shell updates/SRU, some fixes landed upstream some not, maybe would be also the case to include what we have as distro-patch and try with those?
[13:42] <Laney> propose merges
[13:42] <Laney> please
[13:42] <Trevinho> to salsa/ubuntu you mean..
[13:43] <seb128> that doesn't seem a team/meeting topic
[13:43] <seb128> we can discuss it after wrapping though
[13:43] <Laney> as appropriate
[13:43] <tkamppeter> seb128, Laney, I have got some answers on bug 1829566, they could be helful to find out bthe cause.
[13:43] <Laney> thx
[13:43] <seb128> but yeah, mps and reviews sound like the way to go
[13:43] <kenvandine> tkamppeter:  we really need that too, but unblock the migration first
[13:44] <tkamppeter> OK.
[13:44] <Laney> ok another topic
[13:44] <seb128> ok, let's wrap the topics don't really need to be meeting ones we can continue chatting here
[13:44] <seb128> ok
[13:44] <seb128> :)
[13:44] <Laney> are we supposed to reply to the rls bugs email or not?
[13:44] <Laney> like the point of it was to keep things moving
[13:45] <seb128> good comment
[13:45] <seb128> willcooke is not around now though, I think we better discuss it with him or maybe via email
[13:46] <Laney> k
[13:46] <seb128> but yeah, I don't feel like we have an handle on stalled items atm
[13:46] <seb128> those being rls bugs or trello cards or stalled SRUs
[13:46] <seb128> part my/Will's fault for not having done those tooling/report improvements yet
[13:46] <Laney> the formatting that the script generates could be tweaked to be in markdown so that it can be c+p to discourse
[13:46] <Laney> even if the cool auto posting isn't done
[13:47] <seb128> right
[13:47] <Laney> k end of point
[13:47] <seb128> let's start a review of the process/situation and discuss what to do
[13:47] <seb128> maybe discourse is the right place to post about that :)
[13:47] <seb128> but let's see with Will once he's back onlune
[13:47] <seb128> online
[13:47] <seb128> other topic?
[13:48] <seb128> seems not, let's wrap then
[13:48] <seb128> efficient meeting, thx team!
[13:48] <seb128> #endmeeting
[13:48] <meetingology> Meeting ended Tue Jun 18 13:48:41 2019 UTC.
[13:48] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-desktop/2019/ubuntu-desktop.2019-06-18-13.31.moin.txt
[13:49] <seb128> Trevinho, we can discuss SRUs now if you want, did you have specific things in mind?
[13:49] <Trevinho> seb128: regression updates fixes, I think the main ones landed now upstream
[13:49] <seb128> Trevinho, also do you think there is anything we could do to help moving the shell search provider topic upstream? if we want to get ride of those distro changes and have an upstream solution for the next LTS we ideally should get that landed this cycle
[13:49] <Trevinho> but there's one for stack, for which we might avoid a crash triggering a warning.
[13:50] <Trevinho> seb128: don't know... I need to ping Florian again, but he's not much in IRC lately
[13:50] <seb128> Trevinho, if you think we should distro patch I think we should do what L_aney recommends, MP the change to the packaging and we can evaluate/comment there
[13:50] <seb128> Trevinho, upstream doesn't have a mailing list?
[13:51] <Trevinho> yes, not really active these days thoug
[13:51] <seb128> would it help to just work on the code for what you suggest? would code review motivate them more to comment?
[13:53] <Trevinho> seb128: might be, but I'm expecting that if the solution isn't totally matching the design they've in mind, might still stay there and wait
[13:54] <Trevinho> as for bionic, I think backporting is trivial
[13:54] <Trevinho> but the latest package is still in phased updates, as per increased crash rate
[13:55] <Trevinho> which I've looked at, but that is basically impossible to detect as the log is just mozjs stuff with no JS dump
[13:58] <Trevinho> but in any case none of them is a pure regression of this SRU, maybe of the previous one... https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832869 is the main one thugh, but there were previous errors tracked similar to this
[14:06] <seb128> Trevinho, k, so looking around, https://errors.ubuntu.com/problem/d5de4eff621a9ad0777d271a9aabf26458debf5a was already reported on launchpad with an older version and likely due to an extension, you can reply to Brian to ignore that one
[14:06] <Trevinho> Ah, this one is new, but I didn't  reply yet
[14:10] <seb128> Trevinho, the one you just listed, it has reports from the version currently on bionic-security so you can also tell Brian that it doesn't make sense to block the newest SRU
[14:10] <seb128> Trevinho, and for the rate increase just tell him we looked at the reports/errors and didn't see any sign that tell us it's a problem with the SRU or worth blocking it further
[14:10] <seb128> that should be enough to let him unblock the updat
[14:15] <seb128> Wimpress, if you ever get some free cycle could you give a try to see if you still can hit bug #1765053?  that file md5 is identic between the i386 and amd64 debs so the error is weird and we can't reproduce
[14:15] <Trevinho> seb128: ok, good..
[14:15] <seb128> Trevinho, thx
[14:15] <Trevinho> just emailed
[14:15] <Trevinho> as per disco, I can re-prepare the branches
[14:16] <Trevinho> while I wrote about unlinsting https://errors.ubuntu.com/problem/1a63c83d1c90f48036a2f839bf608738eefde4c8 since it's not a shell issue, there's a report on lib account that can be reproduced also with a test case + the lib, so no shell problem
[14:17] <seb128> k
[14:17] <seb128> but disco has valid regressions which have been fixed upstream now so it needs another upload to get unblocked right?
[14:20] <seb128> jdstrand_, hey, I'm reviewing the desktop section from http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-bb-tracking-bug-tasks.html for stalled item, bug #1788929 for evince has been assigned to you and marked as in progress since septembre, it looks like it could do with a status update (either get the fix finally upload, or wontfix/unassign/...)
[14:23] <seb128> willcooke, jibel, can you get https://trello.com/c/nCvZPipl/18-qa-keep-an-history-of-desktop-images updated in some way? it had a target date in february, unsure if it should be wontfixed or kept in the backlog?
[14:37] <kenvandine> wow... google calendar is down!
[14:42] <jdstrand_> seb128: ack
[14:42] <Wimpress> seb128: Yep, I'll try to reproduce it again.
[14:43] <Wimpress> Do you want to this testing on 19.04 or 19.10?
[14:45] <Wimpress> seb128: Looks like I could reproduce that issue following a newer 18.04 daily - https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1765053/comments/5
[14:45] <Wimpress> *could NOT
[14:49] <Thr0r> I was just wondering why the latest version of DigiKam - ver.6,0 is not in the SW shop. I recently installed and I got ver. 5,6,0
[19:50] <seb128> Wimpress, thx for testing, I was not aiming at testing on a particular serie, just to know if that is still happening to someone. It was reported on 18.04 so it's good if it stopped happening there for you
[19:53] <seb128> Thr0r, that's not something #ubuntu-desktop is working on but it looks like it's also outdated in Debian, https://packages.qa.debian.org/d/digikam.html
[19:55] <Thr0r> seb128: Ok, Thanks. Seems no channel is responsible for keeping SW updated in SW Center...
[19:57] <sarnold> looks like no one has a digikam snap package up yet -- you could upload the new version there :) https://snapcraft.io/search?q=digikam
[20:01] <Thr0r> I don't know how that works so I'd better not..