[06:19] <oSoMoN> good morning desktoppers
[06:31] <seb128> goood morning desktopers!
[06:36] <duflu> Hi oSoMoN and seb128 
[06:44] <oSoMoN> salut seb128 
[06:44] <oSoMoN> hey duflu 
[06:47] <seb128> heu duflun lut os
[06:47] <seb128> heu duflun lut oSoMoN, how are you?
[07:06] <pieq> Morning desktoppers!
[07:18] <oSoMoN> seb128, I'm not too bad, how are you?
[07:18] <oSoMoN> salut pieq 
[07:32] <duflu> Hi pieq 
[07:33] <duflu> seb128, two simultaneous family emergencies I'm helping the neighbour with. But I'm OK. Back now, for the moment
[07:33] <duflu> How are you seb128?
[07:45] <duflu> Ironically small children, causing drama at this end and delays at yours :)
[07:47] <marcustomlinson> ergh small children...
[07:47] <marcustomlinson> :P
[07:48] <marcustomlinson> morning desktoppers
[07:55] <oSoMoN> morning marcustomlinson 
[07:55] <duflu> Hi marcustomlinson 
[08:01] <seb128> hey marcustomlinson, how are you?
[08:02] <seb128> oSoMoN, I'm alright :)
[08:02] <seb128> duflu, oh ok, good luck with the emergy, things are going well here
[08:02] <marcustomlinson> hey oSoMoN duflu seb128
[08:02] <marcustomlinson> seb128: doing well thanks
[08:04] <Laney> lo
[08:06] <seb128> hey Laney, how are you?
[08:07] <oSoMoN> hey Laney 
[08:09] <Laney> hey seb128 oSoMoN!
[08:10] <Laney> can't complain
[08:11] <duflu> Hi Laney
[08:11] <Laney> hey duflu
[08:11] <Laney> actually
[08:11] <Laney> I CAN COMPLAIN
[08:11] <Laney> my desktop won't wake up!
[08:12] <pieq> and it's not even Monday anymore...
[08:19]  * Laney gives up and restarts
[08:27] <marcustomlinson> hi Laney
[08:34] <Laney> moin marcustomlinson 
[08:44] <jibel> it happens frequently that my machine doesn't wake up. Never figured out why, there is nothing in the journal.
[08:46] <pieq> jibel, and since the kernel logs are not kept by default between reboots... there is an option to modify this
[08:48] <duflu> jibel, is that Intel graphics or other?
[08:48] <duflu> I think such problems are more common with AMD or Nvidia
[08:51] <jibel> duflu, intel
[08:52] <duflu> pieq, the kernel logs are surely kept in the journal. Just go 'journalctl -b-1' to see the previous one
[09:00] <jibel> from the journal the system resumes but the graphics stack is dead
[09:01] <seb128> is that the same machine where you don't get the analog sound output working?
[09:02] <jibel> yes
[09:03] <seb128> not a lucky choice of config for you :-(
[09:03] <jibel> it's really nothing fancy
[09:03] <jibel> all intel, i7 10th gen
[09:05] <pieq> 10th gen...
[09:05] <jibel> i'll try to ssh next time it happens, since the system seems to be alive, just the display doesn't come back
[09:05] <pieq> jibel, does it have  a dmic?
[09:06] <duflu> jibel, is there still a gnome-shell process? Did that crash?
[09:06] <jibel> pieq, yes 
[09:07] <jibel> duflu, it didn't crash however I don't know if it was running
[09:07] <duflu> You probably want a gnome-shell process :)
[09:07] <jibel> duflu, right but from the color of the LEDs it's hard to tell :)
[09:08] <jibel> I mean I've no display, just the power led and the disk activity
[09:08] <duflu> Also check that Settings > Privacy > Diagnostics allows crash reports
[09:08] <jibel> it does
[09:09] <duflu> jibel, since the two are so different, maybe try 'Ubuntu on Wayland'?
[09:09] <duflu> two (backends)
[09:10] <jibel> Yeah, I'll try that. On my previous machine wayland was not so great but it was an AMD GPU.
[09:19] <pieq> jibel, yeah.... sorry about that. My work laptop is also facing this.
[09:19] <pieq> jibel, so I bought a USB headset with microphone
[09:23] <jibel> I'm currently using HDMI output
[09:23] <jibel> and the mic of the webcam
[09:24] <pieq> works too :) Actually, I'm having an issue with that. My screen has an audio jack output (no internal speakers), but every time I play some sound, it take 1~2 seconds before actually starting outputing sound
[09:24] <pieq> but I don't know if it's a PulseAudio issue or just a design issue with the screen (I don't have other OS at home I could try)
[09:25] <jibel> same setup, but I don't experience the delay
[09:27]  * pieq off, see you tomorrow!
[13:09] <heewa> While working on a calendar related bug, I came across some (probably unrelated) "user experience" difficulty, and I'm not sure how to go about understanding, diagnosing, and possibly addressing it (for the projects involved, not me personally as a single user). Is this the place I should ask about that, or is there a more appropriate channel?
[13:16] <oSoMoN> heewa, it depends on the actual question, really, but you can ask here and we will redirect you if it's not the right place
[13:16] <seb128> heewa, hey, depends of what softwares and problems you are talking about, upstream might be a better start point than ubuntu though
[13:21] <heewa> @seb128, I thought that might be the case. But I'm also curious about at what level Ubuntu tries to ensure a particular experience? 
[13:21] <heewa> In a new virtual machine, with a clean install of a recent daily ISO of Focal, I added a Google account in order to get Calendar events to show up in the gnome shell panel applet. The account was added successfully, but no events. I tried installing Gnome Calendar, nothing. Tried installing Evolution - mail shows up, but not calendars. Tried removing & readding Google account - nothing.
[13:26] <seb128> heewa, I would recommend opening a bug on launchpad and/or gitlab including the journalctl log from your system, that's not normal, calendar are supposed to show up immediatly after the google account is activated (if you allowed calendar access in the setting, which should be the case by default)
[13:30] <seb128> ok, it's meeting time here
[13:30] <seb128> #startmeeting Desktop Team Weekly Meeting - 2020-07-07
[13:30] <meetingology> Meeting started Tue Jul  7 13:30:43 2020 UTC.  The chair is seb128. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[13:30] <meetingology> Available commands: action commands idea info link nick
[13:31] <seb128> Roll call:  didrocks (out), duflu (out), heather, jamesh (out), jibel, kenvandine (out?), laney (out?), marcustomlinson, oSoMoN, tkamppeter, trevinho, robert_ancell (out)
[13:31] <hellsworth> o/
[13:31] <jibel> \o
[13:31] <Trevinho> o/
[13:31] <oSoMoN> o/
[13:31] <marcustomlinson> \o
[13:31] <hellsworth> (btw,good morning everyone)
[13:31] <oSoMoN> morning hellsworth 
[13:31] <kenvandine> sprinting :)
[13:31] <jibel> (good morning hellsworth )
[13:31] <seb128> (moooooorning :)
[13:31] <seb128> ok, let's get started
[13:32] <seb128> #topic rls-bb-bug
[13:32] <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-bb-incoming-bug-tasks.html
[13:32] <seb128> #isdesktopfree
[13:32] <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-bb-tracking-bug-tasks.html
[13:32] <heewa> @seb128, Haha, thanks again! Sorry for the dupes, trying to find the right place without annoying too many ppl.
[13:32] <seb128> heewa, no worry, good luck in the debugging!
[13:33] <seb128> bug #1882248
[13:33] <seb128> sounds like Hui from the oem team is handling that, i will assign to him
[13:34] <seb128> bug #1883497
[13:34] <seb128> tjaalton, I'm assigning the bionic line to you there
[13:34] <seb128> that's it for bionic
[13:35] <seb128> #topic rls-ff-bug
[13:35] <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-ff-incoming-bug-tasks.html
[13:35] <seb128> bug #1880258
[13:35] <tjaalton> ah right
[13:36] <seb128> does any one has an opinion on that one? I don't really, doesn't sound important to me
[13:36] <seb128> probably worth SRUing but I wouldn't rls nominate
[13:36] <seb128> rather to include with other fix when we do a SRU
[13:37] <seb128> unless someone disagrees I'm going to rls-notfixing this one
[13:37] <hellsworth> sgtm
[13:37] <oSoMoN> I don't disagree
[13:37] <seb128> k, done now
[13:39] <seb128> that was it (thanks L_aney for cleaning the noise)
[13:39] <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-ff-tracking-bug-tasks.html
[13:39] <seb128> bug #1874567 there
[13:39] <seb128> that's one for Trevinho who has a patch being worked on for some of the nvidia issues
[13:40] <Trevinho> yep
[13:40] <Trevinho> I wanted to upload before the holidays but failed as wanted to check few things more...
[13:40] <seb128> in fact it's already assigned, just the g-c-c line was not closed, I've done that now
[13:41] <seb128> Trevinho, should the driver side be marked invalid now as it as been confirmed to not be nvidia bug?
[13:41] <Trevinho> seb128: yep
[13:41] <seb128> thx
[13:41]  * Trevinho does that
[13:41] <seb128> and that's it for focal
[13:41] <seb128> #topic rls-gg-bug
[13:41] <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-gg-incoming-bug-tasks.html
[13:42] <seb128> the pulseaudio one still needs a reply from Hui
[13:42] <seb128> the other oens are topic to talk with foundations about, let's skip those today
[13:42] <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-gg-tracking-bug-tasks.html
[13:43] <seb128> bug #1886024 is an archive admin task, just needs to be acted on
[13:43] <seb128> and that's it for bugs
[13:43] <seb128> #topic update_excuses_by_team.html#desktop-packages
[13:43] <seb128> https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses_by_team.html#desktop-packages
[13:43] <seb128> bbswitch is going to be resolved by ^
[13:44] <seb128> nettle is a transition being worked on
[13:44] <seb128> the libxmlb/ppc issue needs to be investigated
[13:44] <seb128> any taker? I will trello card it, if you volunteer grab it
[13:44] <seb128> otherwise we will spin a bottle and see who is the winner :)
[13:45] <seb128> n-m / systemd should resolve itself with the updates from today
[13:45] <seb128> and that's it
[13:45] <seb128> #topic AOB
[13:45] <seb128> anything else?
[13:45] <oSoMoN> the libxml issue looks like https://github.com/hughsie/libxmlb/issues/59
[13:45] <gitbot> hughsie issue 59 in libxmlb "xb-self-test intermittently hang" [Open]
[13:46] <seb128> indeed
[13:46] <seb128> upstream basically baild out :/
[13:46] <oSoMoN> yeah
[13:48] <seb128> getting a gdb stacktrace might give a clue of where it hangs?
[13:48] <seb128> anyway, not one to sort out now
[13:48] <seb128> anything else?
[13:48] <oSoMoN> I can continue poking at it later, feel free to assign me to the card
[13:48] <oSoMoN> (nothing else from me)
[13:48] <seb128> thanks
[13:48] <seb128> it might fit well with your incoming +1 rotation :)
[13:49] <seb128> k, seems there is no other topic, nice efficient meeting
[13:49] <seb128> thanks team!
[13:49] <seb128> #endmeeting
[13:49] <meetingology> Meeting ended Tue Jul  7 13:49:11 2020 UTC.  
[13:49] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-desktop/2020/ubuntu-desktop.2020-07-07-13.30.moin.txt
[13:49] <hellsworth> thanks!
[13:49] <oSoMoN> thanks
[13:49] <marcustomlinson> dank
[15:02] <GunnarHj> Good afternoon, seb128. Any thoughts on when and how to address the ibus crashes?
[15:02] <GunnarHj> https://errors.ubuntu.com/?release=Ubuntu%2020.04&package=ibus&period=month&version=1.5.22-2ubuntu2
[15:15] <seb128> GunnarHj, hey, how are you? 'no particular though out of 'would be nice to have someone able to trigger the issue or at least describe what they do to hit it'
[15:19] <GunnarHj> seb128: I have been following one of the upstream bug trackers (ibus-avro) for a while, and my impression is that they just type and suddenly it stops working. This Ask Ubuntu question illustrates it: https://askubuntu.com/q/1256510
[15:20] <seb128> GunnarHj, k, I was wondering if that's a crash on shutdown or session closing
[15:20] <seb128> bug #1871625 states 'after I closed and reopened my session.'
[15:28] <GunnarHj> seb128: That bug report doesn't help much; we don't even know if the bug reporter uses IBus input methods. But I have seen several reports from users who use input methods and who complains that it suddenly stops to work. I'm assuming that the frequent ibus crashes have something to do with it.
[15:31] <GunnarHj> seb128: It would be good if someone with sufficient skill could dig into those error logs...
[15:47] <seb128> GunnarHj, right, the issue is that the stacktrace does sounds like a memory corruption so it's not clear the debug info we have are enough to give a proper clue about what could be going on :-/
[16:00] <GunnarHj> seb128: Sounds tricky. And few crash bug reporters stay long enough to help provide additional info and/or tell how to reproduce it.
[19:29] <KGB-0> glib pristine-tar c8335f5 Simon McVittie glib2.0_2.64.4.orig.tar.xz.delta glib2.0_2.64.4.orig.tar.xz.id * pristine-tar data for glib2.0_2.64.4.orig.tar.xz * https://deb.li/xd0x
[19:29] <KGB-0> glib upstream/latest d82757c Simon McVittie * pushed 18 commits * https://deb.li/3lTCE
[19:30] <KGB-0> glib tags 978c472 Simon McVittie upstream/2.64.4 * Upstream version 2.64.4 * https://deb.li/992l