[06:29] <oSoMoN> good morning desktoppers
[07:13] <duflu> Morning oSoMoN
[07:15] <didrocks> good morning
[07:20] <duflu> Hi didrocks
[07:20] <didrocks> hey duflu
[07:30] <oSoMoN> hey duflu, salut didrocks
[07:31] <didrocks> salut oSoMoN, bon week-end ?
[08:30] <Wimpress> Morning o/
[08:30] <seb128> gooood morning desktopers!
[08:30] <seb128> hey Wimpress, how are you? had a good w.e?
[08:31] <duflu> Morning Wimpress and seb128
[08:31] <duflu> Good holiday?
[08:31] <didrocks> salut seb128, bonne vacances ?
[08:32] <didrocks> hey Wimpress
[08:32] <seb128> hey duflu, didrocks
[08:32] <seb128> yes! was nice, sunny and relaxing!
[08:32] <seb128> we also managed to shake out our winter bugs/colds :)
[08:32] <didrocks> glad to hear that :)
[08:33] <Wimpress> Glad you had a good time seb128
[08:33] <Wimpress> I like the sound of some warm weather :-)
[08:34] <Wimpress> Good weekend here. Making Lego robots with my daughter during the day.
[08:34] <Wimpress> MATE 1.24 in Debian Unstable and Focal during the evening.
[08:35] <Wimpress> Helped fixed a thing for GunnarHj too :-)
[08:36] <didrocks> great!
[08:37] <jamesh> fyi: if you run into text entry problems in snapped desktop apps on 20.04, it is due to a change in the ibus socket path in the last update
[08:38] <jamesh> there's a fix in master, and it should be back ported to snapd 2.43.x
[08:38] <Saviq> hey all, did you guys ever see keyboard input randomly going away from snaps?
[08:38] <jamesh> Saviq: see two lines up :-)
[08:38] <Saviq> jamesh: d'uh!
[08:39] <Saviq> I was about to say I felt like it's ibus-related
[08:39] <Saviq> jamesh: known workaround?
[08:39] <Wimpress> popey: FYI: See above
[08:39] <duflu> bug 1863255
[08:39] <ubot5> bug 1863255 in snapd (Ubuntu) "Programs installed in Snap format do not detect the keyboard " [High,Confirmed] https://launchpad.net/bugs/1863255
[08:39] <jamesh> Saviq: "snap refresh --edge core" might be a good short term fix, but you'll probably want to switch back afterwards
[08:40] <jamesh> or try pinning to the old ibus version
[08:40] <jamesh> https://github.com/snapcore/snapd/pull/8139 <- here's the snapd change fixing the problem
[08:40] <gitbot> snapcore issue (Pull request) 8139 in snapd "interfaces/{desktop-legacy,unity7}: adjust for new ibus socket location" [Simple 😃, Closed]
[08:43] <seb128> jamesh, that's in this focal upload right https://launchpad.net/ubuntu/+source/snapd/2.43.3+git1.8109f8 right?
[08:44] <jamesh> seb128: looks like it, yeah.
[08:49] <Saviq> not sure if related, but I randomly started getting
[08:49] <Saviq> libgtk-3.so.0: cannot open shared object file: No such file or directory
[08:49] <Saviq> i.e. snaps losing the gtk runtime (?)
[08:55] <oSoMoN> Saviq, for the chromium snap, a workaround is to delete ~/snap/chromium/common/.cache, not sure about other snaps that are affected
[08:55] <marcustomlinson> morning oSoMoN duflu didrocks Wimpress seb128 jamesh and Saviq :)
[08:56] <seb128> lut oSoMoN, hey marcustomlinson
[08:56] <oSoMoN> didrocks, très bon week-end, my mom was visiting so we walked around Barcelona, that was nice
[08:56] <seb128> oSoMoN, is that a workaround for the libgtk missing? why is the cache getting in that state/creating that problem?
[08:56] <oSoMoN> salut seb128, hey marcustomlinson
[08:56] <didrocks> hey marcustomlinson, all good?
[08:57] <didrocks> oSoMoN: nice :)
[08:57] <marcustomlinson> all good thank you :)
[08:57] <duflu> Morning marcustomlinson
[08:57] <jamesh> Saviq: you could try running "sudo /usr/lib/snapd/snap-discard-ns $snapname" and try starting the app again
[08:57] <oSoMoN> seb128, the workaround is for the ibus change that broke keyboard input in snaps, I haven't had time to look into it further, it was suggested by someone on a duplicate of the bug report
[08:57] <jamesh> Saviq: see if there is anything interesting on the console
[08:57] <seb128> oSoMoN, ah ok
[08:58] <marcustomlinson> how you didrocks?
[08:58] <oSoMoN> not sure whether it would work for other snaps, but given that there is a proper fix already merged and being backported, I don't feel like spending too much time on this
[08:58] <Saviq> oi! marcustomlinson
[08:58] <oSoMoN> got plenty on my plate of the week already…
[08:58] <seb128> oSoMoN, a new snapd was just uploaded to focal with a fix for ibus, unsure if with that version removing the cache is still needed, if that's the case we probably need to force a cache refresh
[08:58] <seb128> jamesh, ^
[08:59] <didrocks> marcustomlinson: quite fine as well, thanks :)
[08:59] <oSoMoN> seb128, I'll test but I'd expect/hope that removing the cache wouldn't be needed with the new snapd
[08:59] <Saviq> jamesh: that did the trick https://pastebin.canonical.com/p/yZNy7mNjrv/
[09:01] <Saviq> on that note, is gdk-pixbuf-loaders.cache only generated once? I had to manually generate it having recovered `snap/firefox` from a backup
[09:01] <seb128> Saviq, looks like a topic for #snappy
[09:01] <seb128> you probably want zyga around
[09:01] <Saviq> but… but… jamesh is fixing all my issues here! ;)
[09:02] <Saviq> but yeah, will let zyga know
[09:02] <seb128> thx :
[09:02] <seb128> :)
[09:02] <Wimpress> Morning marcustomlinson o/
[09:03] <jamesh> Saviq: any time you need to use snap-discard-ns is probably a bug
[09:03] <Saviq> I'm sure
[09:03] <Laney> morning
[09:03] <marcustomlinson> hey Laney
[09:03] <didrocks> morning Laney, good week-end?
[09:03] <oSoMoN> morning Laney, Wimpress
[09:04] <Wimpress> oSoMoN: o/
[09:05] <marcustomlinson> popey, Wimpress, Laney: no flooding by you I hope?
[09:05] <Wimpress> Yep, flooding here.
[09:05] <marcustomlinson> :(((((
[09:05] <Wimpress> We're fortunate. On a hill.
[09:05] <seb128> hey Laney, how are you?
[09:05] <Wimpress> But we can't leave our road, because the bottom of the hill is 4 feet deep.
[09:06] <marcustomlinson> damn
[09:06] <Laney> hey marcustomlinson didrocks oSoMoN Wimpress seb128!
[09:07] <Laney> was a nice weekend, mainly hid inside from the storm though
[09:08] <Laney> no flooding here, not really near to any rivers
[09:08] <Laney> although once the drains were blocked up with leaves and the next road along became a river
[09:08] <Laney> that was amusing
[09:08] <Laney> seb128: feeling rested?
[09:08] <seb128> Laney, yes, holidays were great, thanks :)
[09:09] <Laney> heading south is the way
[09:09] <jamesh> if you head far enough south, you'll hit summer
[09:10] <seb128> indeed :)
[09:12] <oSoMoN> seb128, I confirm that installing snapd from focal-proposed is enough to fix the keyboard input problem with chromium, no need to delete the cache, it's just a useful workaround until the snapd update is available to everyone
[09:12] <jamesh> I wonder why deleting the cache changed the behaviour?
[09:13] <seb128> oSoMoN, great, thanks!
[09:14] <oSoMoN> it could be that chromium doesn't even try to use ibus in that case
[09:15] <oSoMoN> seb128, I'm sure you have plenty to catch up with, but could you suggest someone who could review https://code.launchpad.net/~osomon/software-properties/+git/software-properties/+merge/379239 ?
[09:21] <seb128> oSoMoN, didrocks or Laney maybe if they can spare some cycles for review
[09:21] <seb128> oSoMoN, I will try also to have a look once I'm done catching up with things, might not be today though
[09:22] <didrocks> it’s quite large and I still have plenty to catchup, but I’ll try later this week, like on Wednesday
[09:22] <didrocks> (if nobody beats me to it)
[09:26] <oSoMoN> thanks, I appreciate it! there's a PPA with test packages here: https://launchpad.net/~osomon/+archive/ubuntu/software-properties/+packages
[09:27] <didrocks> oh nice! thanks for publishing this
[09:28]  * didrocks adds that next to the list of ETOOMANYMIRs to review
[09:28]  * seb128 hugs didrocks, thanks for taking some for the team :)
[09:29] <seb128> hopefully those MIRs are easy enough
[09:32]  * didrocks hugs back. I didn’t look yet, I think 2 of them are needed before FF and the GameMode one can be post-FF as less important?
[09:34] <seb128> yes, I think it's a fair statement (unless Wimpress disagrees and would like to push to get gamemoded in earlier rather than later)
[09:34] <seb128> the gedit ones are just split of existing code and glib/gtk libraries
[09:34] <seb128> so shouldn't be too complex/security sensitive/...
[09:36] <didrocks> yeah, I plan that as well for Wednesday
[09:36] <Wimpress> I don't mind when Gamemode lands, so long as it features in Focal :-)
[09:36] <didrocks> (meaning: done by Wednesday at most)
[09:38] <seb128> brb, changing location
[09:49] <Saviq> jamesh: FYI: edge core (16-2.43.3+git1659.8fa09ac) didn't help with the ibus issue - downloading ibus did
[09:51] <Saviq> oSoMoN: FYI ↑
[09:53] <Saviq> s/downloading/downgrading/
[09:53] <amurray> Saviq: the other option would be running something like:
[09:53] <amurray> sudo sed -i 's|/tmp/ibus/|/home/*/.cache/ibus/|' /var/lib/snapd/apparmor/profiles/snap.gnome-calculator.gnome-calculator
[09:53] <amurray> sudo apparmor_parser -Tr /var/lib/snapd/apparmor/profiles/snap.gnome-calculator.gnome-calculator
[09:53] <amurray> but next update to the affected snap you would need to re-run it - but at least it will get you going for now
[09:54] <amurray> (and replace gnome-calculator.gnome-calculator with firefox.firefox or whatever snap in question)
[10:03] <Laney> yeah can probably look at some point
[10:04]  * Laney returns from the caves of mozjs
[10:10]  * duflu likes the sound of that
[10:10] <duflu> Also good morning Laney
[10:10] <duflu> And good night
[10:10]  * duflu is already cooking
[10:10] <Laney> hi & bye duflu
[10:20] <Laney> ...and now the tests are even running
[10:34] <jamesh> Saviq: I wonder if it is re-execing to the copy of snapd from the core snap?
[10:34] <jamesh> Saviq: "sudo ls -l /proc/$(pidof snapd)/exe" would probably prove that one way or another
[10:36] <Saviq> jamesh: looks like it, yes:
[10:36] <Saviq> lrwxrwxrwx 1 root root 0 lut 17 11:36 /proc/1928/exe -> /snap/core/8712/usr/lib/snapd/snapd
[11:50] <ricotz> hello desktopers :)
[12:06] <seb128> hey ricotz, how are you?
[12:10] <ricotz> seb128, hi, coould be better ;), did you have some nice holidays?
[12:11] <seb128> ricotz, oh, I hope things get better then!
[12:12] <seb128> ricotz, I had nice holidays yes, relaxing :)
[12:13] <ricotz> seb128, thanks, nothing serious though
[12:13] <ricotz> seb128, great to hear that
[12:14] <seb128> k, good then :)
[12:16] <seb128> ricotz, I saw your vala commits on #debian-gnome, do you need sponsoring for the update?
[12:17] <ricotz> seb128, oh, of course, that would be great! there is libgee-0.8 update too
[12:17] <seb128> ricotz, I will have a look
[12:18] <ricotz> seb128, I guess pushing vala to unstable would be possible?
[12:18] <seb128> up to you, you are the maintainer :)
[12:18] <seb128> but seems fine to me yes
[12:18] <ricotz> I think I saw some GNOME 3.36 beta releases landing in unstable already
[12:18] <seb128> if you are confident it's ready/isn't going to create too much issues
[12:19] <seb128> right, apps without major changes are usually fine for unstable/testing users
[12:19] <seb128> but as said, you know the package better so I will trust you if you believe it's ready for unstabl
[12:19] <ricotz> it should be fine and it is one of the toolchain packages which should land early in unstable
[12:20] <ricotz> so please target unstable for 0.47.91
[12:32] <seb128> k
[14:13] <ricotz> fyi, https://bugs.launchpad.net/ubuntu/+source/nodejs/+bug/1863463
[14:13] <ubot5> Ubuntu bug 1863463 in nodejs (Ubuntu) "Firefox 75 requires nodejs >= 10.19" [Undecided,New]
[14:27] <seb128> tkamppeter, hey, http://autopkgtest.ubuntu.com/packages/c/c2esp/focal/amd64 seems like it could be a real issue, it failed on all archs and a retry didn't make a difference, could you investigate the issue?
[14:47] <xclaesse> Hi there. Every time I get a kernel update on 20.04 I see those messages: https://pastebin.com/Rf9vVVBM. Not sure if that's harmless or not.
[14:49] <oSoMoN> seb128, I forgot to mention this morning: I prepared debian updates for tepl and gedit, merge requests are up for review on salsa
[14:49] <seb128> oSoMoN, ah nice, I will have a look
[14:50] <seb128> xclaesse, hey, no idea about those, maybe #ubuntu-kernel has a better clue?
[14:58] <tkamppeter> seb128, I am having a look into this.
[14:58] <seb128> tkamppeter, thanks
[14:59] <xclaesse> seb128: ok thanks :)
[15:00] <seb128> np!
[15:00] <xclaesse> seb128: while you're there, I think you should consider getting that gtk patch: https://gitlab.gnome.org/GNOME/gtk/merge_requests/1356
[15:00] <gitbot> GNOME issue (Merge request) 1356 in gtk "GtkSearchEngineSimple: Disable recursive search" [Merged]
[15:01] <seb128> xclaesse, thanks, that probably makes sense to get yes, I will keep an eye on it and backport if there is no release before the end of the cycle
[15:02] <xclaesse> seb128: and it would also be nice to make nautilus recommend tracker instead of depend. atm trying to uninstalled tracker also uninstall nautilus and ubuntu-desktop :(
[15:03] <xclaesse> I get that tracker gets installed by default, but personally I don't need my CPU to be at 100% for several hours each time I clone or move a git repo :p
[15:03] <xclaesse> and tracker does not even have a UI to set the dirs to ignore
[15:04] <seb128> xclaesse, I saw your report, I need to check how is nautilus behaving without tracker. Upstream insisted some cycle ago that tracker was a depends and some of the nautilus core features wouldn't work without it installed (like favorite files, batch renaming, ..)
[15:05] <xclaesse> or maybe just a way to disable/uninstall miners would do the trick
[15:05] <xclaesse> seb128: thanks a lot ! :D
[15:05] <seb128> np!
[15:05] <seb128> xclaesse, you can configure the tracker folders in gnome-control-center/search/files no?
[15:06] <xclaesse> seb128: I don't see how. I can only move "files" up and down
[15:06] <seb128> otherwise gsettings :p
[15:07] <diddledan> git clone into a place other than ~/Documents :-) I put all my git stuff in dirs below ~/Development and don't get any tracker shenanigans
[15:08] <xclaesse> it's supposed to ignore folders with .git, but it doesn't seems to work. or maybe it was using CPU for something else... dunno
[15:09] <xclaesse> the point is for me tracker is totally useless and I saw it at 100% CPU a few times
[15:10] <xclaesse> oh, I see in dconf I can disable index on battery, that would already help to mitigate my biggest issue with tracke :p
[15:10] <xclaesse> that definitely MUST be disabled by default
[15:10] <seb128> xclaesse, there is a 'search location' in the headbar of the search settings page
[15:11] <seb128> we know buttons in headerbar are not the most obvious thing :/
[15:12] <diddledan> the toggle in the header bar is worse than having buttons IMO :-p
[15:13] <seb128> xclaesse, but yeah, disabling indexing on battery might be a better default ... https://gitlab.gnome.org/GNOME/tracker-miners/issues/1
[15:13] <gitbot> GNOME issue 1 in tracker-miners "tracker-miners should not be running while on battery" [Opened]
[15:13] <xclaesse> seb128: oh, indeed that hearder button is what I was looking for I guess. There is no way to add exclude directories, but I can disable $HOME completely there
[15:13] <diddledan> that toggle should either be on the left menu list where you can choose the `search` option. or in the search pane itself above the list of apps
[15:14] <xclaesse> that will do the trick, thanks :)
[15:14] <seb128> np!
=== Laney changed the topic of #ubuntu-desktop to: Home of the Desktop Team, https://wiki.ubuntu.com/DesktopTeam | For help or questions, try #ubuntu | Work (read-only for non-developers): https://trello.com/b/mxaCZTVc | GNOME 3.36 work claiming / tracking: https://trello.com/b/z29JJK3q/gnome-336
[16:22] <tkamppeter> seb128, the problem with c2esp is that it is the only driver needing CMY CUPS Raster data (all the others use RGB) and Ghostscript segfaults on this format, at least for some input files. So it is a Ghostscript bug.
[16:23] <tkamppeter> seb128, I will report this to Ghostscript but until we get a fix it can take some time. What is affected in real life are the rather rare Kodak printers (never got a bug report about one not printing, are they still on the market?).
[16:24] <tkamppeter> seb128, should we perhaps add an exception to the autopkg tests so that this package gets skipped or ignored to keep CUPS updates getting through to the release quickly?
=== teward_ is now known as teward
[17:14] <oSoMoN> have a good evening everyone
[17:43] <tkamppeter> seb128, Ghostscript bug reported: https://bugs.ghostscript.com/show_bug.cgi?id=702133
[17:43] <ubot5> bugs.ghostscript.com bug 702133 in CUPS driver "Ghostscript does not correctly create CMY CUPS Raster and often crashes" [Normal,Unconfirmed]
[17:44]  * Laney squeals
[17:44] <Laney> some snaps have started spamming with apparmor denials
[17:44] <Laney> gnome-shell does NOT do well with hundreds of notifications
[19:04] <tkamppeter> seb128, c2esp problem seems to be solved. When Ghostscript did not segfault the output was messy and I found an older bug fixing this (but was not yet in our GS 9.50), https://bugs.ghostscript.com/show_bug.cgi?id=701625. I added the fix to our Ghostscript and this fixed also the segfault. It is uploaded now and I hope this makes all working.
[19:04] <ubot5> bugs.ghostscript.com bug 701625 in CUPS driver ""cups"/"pwgraster" output device: CMY output is messed up" [Normal,Resolved: fixed]
[20:27] <seb128> tkamppeter, great, thank you
[20:49] <xclaesse> Is it intentional there is no more "python"
[20:50] <xclaesse> I only have python2 and python3
[21:14] <mwhudson> xclaesse: yes