Your message dated Tue, 13 Aug 2024 20:55:12 -0700 with message-id <vy5yu3hw6p6ja6xdewivp7ktygpozrrooraqzkh5slftaogc6n@lgaqinjjov7w> and subject line Re: Bug#1078660: bugs.debian.org: Browser private window hangs in Wayland has caused the Debian Bug report #1078660, regarding bugs.debian.org: Browser private window hangs in Wayland to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1078660: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1078660 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: bugs.debian.org Severity: normal X-Debbugs-Cc: ken...@hotmail.com Dear Maintainer, * What led up to the situation? I installed both Firefox and Brave using Flatpak on debian testing. So far I have only observed the bug in the gnome desktop when using Wayland. * What exactly did you do (or not do) that was effective (or ineffective)? I right-clicked the application and chose to open a new private window. * What was the outcome of this action? The browsers each took far longer than usual to start. I opened htop and saw that (in the case of Firefox) the following command was using 100% of only one CPU: "/usr/bin/flatpak run --branch=stable --arch=x86_64 --command=firefox --file-forwarding org.mozilla.firefox --private-window @@u @@" A similar command hang while doing the same for Brave. * What outcome did you expect instead? A private window starting right away. I should mention that this behavior does not occur if a normal browser window has started and I start a private window from its menu. Also, this behavior is not observed in xorg in gnome, nor is it observed in KDE at all.
--- End Message ---
--- Begin Message ---On Tue, 13 Aug 2024, Kene Nwankwo wrote: > * What led up to the situation? > I installed both Firefox and Brave using Flatpak on debian testing. > So far I have only observed the bug in the gnome desktop when using > Wayland. > > * What exactly did you do (or not do) that was effective (or > ineffective)? > I right-clicked the application and chose to open a new private > window. > > * What was the outcome of this action? > The browsers each took far longer than usual to start. I opened htop > and saw that (in the case of Firefox) the following command was using > 100% of only one CPU: > "/usr/bin/flatpak run --branch=stable --arch=x86_64 --command=firefox > --file-forwarding org.mozilla.firefox --private-window @@u @@" > A similar command hang while doing the same for Brave. Thanks for filing a report against Debian. Unfortunately, we don't support the versions of firefox or brave that flatpak installs. Those would be supported by whoever provided the flatpak that you're running. Also, if this was Debian's version of firefox, the correct package to file the bug against is firefox, not bugs.debian.org. -- Don Armstrong https://www.donarmstrong.com Logs drowse in the pond Dreaming of their heroes Alligator and crocodile -- Vern Rutsala "Poetry in Motion" p77
--- End Message ---
