[06:28] <oSoMoN> good morning desktoppers
[06:39] <duflu> Hi oSoMoN 
[06:49] <oSoMoN> hey duflu 
[07:00] <seb128> goood morning desktopers
[07:00] <seb128> hey duflu, lut oSoMoN, how are you?
[07:01] <duflu> Hey seb128, going OK. You?
[07:01] <oSoMoN> salut seb128 ! I'm a bit tired, getting out of bed was extra difficult today, but now that I'm awake I'm good. How are you?
[07:16] <seb128> bah IRC
[07:16] <seb128> duflu, I'm alright thanks :)
[07:16] <seb128> oSoMoN, I hope your day isn't going to be a struggle, good luck, weekend is coming
[07:17] <oSoMoN> it'll be fine, it was only a slow start :)
[07:21] <didrocks> forgot to press enter on my good morning here :p
[07:25] <oSoMoN> good morning didrocks <Enter>
[07:28] <duflu> Hi didrocks 
[07:28] <didrocks> ahah :) salut oSoMoN. hey duflu 
[07:54] <oSoMoN> Eickmeyer, hey, regarding comments like https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1971608/comments/1 , I was wondering whether there would be a way to convey that despite the bug tracking happening upstream, the Ubuntu Desktop team is still actively involved in triaging and addressing these issues?
[07:56] <oSoMoN> It's never pleasant when you took the time to file a bug somewhere, to be told to go file it somewhere else. Knowing that Ubuntu developers care and will take a look at it might motivate them to take the extra step, wdyt?
[07:56] <oSoMoN> (thanks for the triaging work btw!)
[08:00] <duflu> I've been working on the assumption that the snap makes https://bugs.launchpad.net/ubuntu/+source/firefox effectively unused so we're free to declare it is for tracking bugs in the snap. No need to forcefully redirect people upstream, just suggest it
[08:20] <seb128> duflu, do you know if there are known issues on 22.04 / nvidia (probably hybrid) where the lockscreen doesn't display after resume? someone here asked me about it saying that doing a VT switch workaround it/correctly display the password prompt
[08:21] <seb128> duflu, 'doesn't display' as the screen is still locked but there is no visible password prompt
[08:21] <duflu> seb128, there's always a bunch of bug reports like that for AMD/Nvidia with each release. I'll see if we have one for Nvidia yet
[08:21] <seb128> he said nvidia but that's a laptop so I assume it's an hybrid
[08:22] <duflu> It's really a never ending problem -- suspend and resume is always failing for some people
[08:22] <seb128> :(
[08:22] <duflu> Hopefully just fewer people as time goes on
[08:22] <seb128> right
[08:23] <seb128> do we have standard workarounds for those sort of issues?
[08:25] <duflu> seb128, just triage. Sometimes it turns out to be a crash. Other times it turns out to be kernel bugs (especially amdgpu)
[08:25] <seb128> k, thanks
[08:27] <duflu> seb128, I can't find suspend-resume (which is a tag) bugs relating to Nvidia since impish. But even if I could I would recommend logging a new bug because it's a whole class of problem and not something that different systems should share
[08:27] <seb128> speaking about amdgpu, I've a friend who upgrade from F to J yesterday and complains that youtube video are laggy since the update (in firefox and chromium), that's an amd cpu and radeon card/driver
[08:28] <seb128> should video acceleration work on such configs?
[08:28] <duflu> seb128, people have different definitions of "lag". I think the most common issue is probably just rendering/decoding performance
[08:28] <duflu> Not in browsers it won't work, unless I'm out of date (oSoMon?)
[08:29] <seb128> he has software rendering according to firefox about:
[08:29] <seb128> well, he said playing was smooth on focal before the update
[08:30] <seb128> I've asked him to report using ubuntu-bug but I don't think he did yet
[08:30] <duflu> Oh three definitions of "software rendering" too: (1) make sure the shell is not software rendering; (2) firefox 99 _is_ using software rendering [workaround is refresh to --beta]; (3) hardware VP9/AV1 decoding is probably not implemented in the browser yet either
[08:30] <oSoMoN> VAAPI is known to be broken in firefox atm (still deemed experimental), running with MOZ_DISABLE_RDD_SANDBOX=1 might help
[08:31] <oSoMoN> (that's not just the snap)
[08:31] <duflu> Oops, firefox 99 is using Xwayland, not software rendering. Still, native Wayland is noticeably faster so refresh to --beta
[08:31] <oSoMoN> --candidate will do
[08:32] <duflu> Cool
[08:32] <oSoMoN> no, wait, it has to be candidate with MOZ_ENABLE_WAYLAND=1
[08:32] <duflu> about:support will tell you "Xwayland" or "Wayland"
[08:34] <seb128> chromium has the same issue so probably not a firefox specific problem
[08:34] <seb128> I will get him to check 1/
[08:35] <duflu> Fundamentally a browser is an OpenGL app and should perform as well as a game, even if it is software decoding
[08:36] <oSoMoN> if chromium was playing back videos smoothly in FF and not in JJ, then there must be something else at play
[08:40] <seb128> ack
[09:24] <diddledani> morning
[09:26]  * diddledani waves to diddledani (purposely mis-tabbed because nobody has tagged me instead of didrocks lately ;-p)
[09:28] <didrocks> :p (and hey!)
[09:28] <diddledani> morning :-)
[13:08] <Eickmeyer> oSoMoN: That was just my understanding of it based on the output of apport when one tries to file via 'ubuntu-bug firefox', especially when it's clearly an internal working of firefox an not so much how it interacts with the desktop.
[13:19] <oSoMoN> Eickmeyer, your understanding is absolutely correct, I'm just wondering if we could word the response in a way that doesn't discourage people who report bugs on LP to go the extra mile and report them upstream too
[13:20] <Eickmeyer> oSoMoN: Yeah, I was just brainstorming that. Perhaps marking as incomplete and instead requesting that the mozilla bug be linked in a comment so that it can be tracked in Launchpad?
[13:20] <oSoMoN> yeah, I think that would be useful, it gives a sense that we're not throwing away the LP bug, it remains useful
[13:21] <Eickmeyer> And that they understand that bug reports aren't for filing complaints, but for helping others.
[13:21] <Eickmeyer> Ok, I'll reword it as such. :)
[13:24] <Eickmeyer> oSoMoN: "Thank you for taking the time to report this bug and help make Ubuntu better. Firefox is provided by a snap published by Mozilla, and they may not be aware of this issue. Please contact them via https://support.mozilla.org/kb/file-bug-report-or-feature-request-mozilla and link the bug report here so it can be further tracked. Thank you!"
[13:24] <Eickmeyer> I should also add "Then mark the bug as new".
[13:26] <oSoMoN> We (you, me, other triagers) can take care of the status change, once there is an upstream bug
[13:30] <Eickmeyer> oSoMoN: Sure.
[13:48] <Eickmeyer> oSoMoN: I just went back through every one of those bug reports and fixed the comments, and marked them as incomplete. In one case I had to make a CoC warning (they kinda lashed-out at my previous wording, my fault), so now they're all trackable again. It was about 15 reports overall. One remained invalid since it was really a support request and unrelated to firefox (converted to
[13:48] <Eickmeyer> question).
[13:48] <oSoMoN> thanks Eickmeyer, that's much appreciated!
[13:49] <Eickmeyer> No problem. :)
[18:20] <KGB-0> libnotify tags d0cfaab Marco Trevisan upstream/0.7.12 * Upstream version 0.7.12 * https://deb.li/3Ohv0
[18:20] <KGB-2> libnotify upstream/latest 19c06c4 Marco Trevisan * pushed 13 commits (first 5 follow) * https://deb.li/O9BG
[18:20] <KGB-2> libnotify upstream/latest 997115b Marco Trevisan (Treviño) docs/notify-send.xml * docs/notify-send: Add --transient option to manpage * https://deb.li/3vd6i
[18:20] <KGB-2> libnotify upstream/latest c99aacd Marco Trevisan (Treviño) tools/notify-send.c * notify-send: Move server capabilities check to a separate function * https://deb.li/hfDv
[18:20] <KGB-2> libnotify upstream/latest a674e61 Marco Trevisan (Treviño) tools/notify-send.c * notify-send: Add debug message about server not supporting persistence * https://deb.li/3CTsn
[18:21] <KGB-2> libnotify upstream/latest 1fba04b Marco Trevisan (Treviño) libnotify/notification.c * notification: Include sender-pid hint by default if not provided * https://deb.li/o9zs
[18:21] <KGB-2> libnotify upstream/latest 6e6d523 Patrick Griffis libnotify/notifynotification.xml * Delete unused notifynotification.xml * https://deb.li/igUwU