Thunderbird 102.2.2 was finally released to
{bionic,focal,jammy}-{updates,security}. Thank you for your patience,
and please excuse the delay.
I am now working on the 102.3.1 update.
** Changed in: thunderbird (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug
Yes, the update to thunderbird 102.2.2 is ready and awaiting validation
and publication by the security team.
** Changed in: thunderbird (Ubuntu)
Status: Confirmed => In Progress
** Changed in: thunderbird (Ubuntu)
Assignee: (unassigned) => Olivier Tilloy (osomon)
** C
It looks like the difference might be in using the Wayland backend
(default in the beta and edge channels), versus being an XWayland client
(default in the stable channel).
Can you switch back to the stable channel, and test again with
`MOZ_ENABLE_WAYLAND=1` ?
--
You received this bug
** Also affects: firefox via
https://bugzilla.mozilla.org/show_bug.cgi?id=1772586
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1976330
Title:
No
Confirmed, this now works in 22.04.
** Changed in: chromium-browser (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874415
Title:
[snap]
** Changed in: firefox (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969509
Title:
[snap] Unmaximized but not unfullscreened
To manage notifications
Did the upgrade succeed after killing that dialog?
Can you try reinstalling the firefox package and share the output here?
sudo apt reinstall firefox
** Changed in: firefox (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Funny, this looks like the opposite of bug #1970663.
Can you share more information on your setup? Screen resolution, desktop
environment, cursor theme, and maybe a screenshot or screencast
demonstrating the problem?
** Changed in: firefox (Ubuntu)
Status: New => Incomplete
--
You
Corrado, could you try an upstream nightly build (from
https://download.mozilla.org/?product=firefox-nightly-
latest-l10n-ssl=linux64)? If the problem can be observed there,
please file an upstream bug at
https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox, and link to
it here. Thanks!
--
Relevant output from DpkgTerminalLog.txt:
error: cannot perform the following tasks:
- Download snap "core20" (1494) from channel "stable" (received an unexpected
http response code (503) when trying to download
Relevant output from DpkgTerminalLog.txt:
error: cannot perform the following tasks:
- Download snap "chromium" (2000) from channel "stable" (received an unexpected
http response code (503) when trying to download
Troels, according to comment #6 this wasn't working with the beta snap
when it was version 100, and it's now working at version 102. Can you
test again the stable channel (currently at version 101) and let us know
whether this is working there?
--
You received this bug notification because you
** Bug watch added: Mozilla Bugzilla #1752414
https://bugzilla.mozilla.org/show_bug.cgi?id=1752414
** Changed in: firefox
Status: Invalid => Unknown
** Changed in: firefox
Remote watch: Mozilla Bugzilla #1767925 => Mozilla Bugzilla #1752414
--
You received this bug notification
Can you also please run the following command to attach additional debug
information to the bug report?
apport-collect 1973468
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973468
Title:
New
Indeed, by default file-roller will temporarily unpack files in the
user's cache folder (it can in some cases fall back to the user's home
directory, or a temporary directory, see
https://gitlab.gnome.org/GNOME/file-roller/-/blob/master/src/file-
utils.c#L55).
Given this, I wonder whether it
Relevant output from DpkgTerminalLog.txt:
error: cannot perform the following tasks:
- Run configure hook of "firefox" snap if present (run hook "configure": cannot
perform operation: mount --rbind /dev /tmp/snap.rootfs_GfGqr8//dev: No such
file or directory)
Does reinstalling the package
I'm closing this bug again, not because it's not a valid issue, but
because it's being tracked and addressed elsewhere. See details on the
ongoing work (which spans multiple teams and projects) at
https://ubuntu.com/blog/how-are-we-improving-firefox-snap-performance-
part-1 and
Indeed, this was fixed upstream to use the desktop portal when the
FileManager1 interface isn't available:
https://chromium.googlesource.com/chromium/src/+/cdc98cbb2a95d4a7d430b7ccece0d5433d94963a.
** Changed in: chromium-browser (Ubuntu)
Status: Confirmed => Fix Released
** Changed in:
That's right. But I wonder whether this is enough to guarantee that FLoC
is fully disabled?
In my profile directory, there's a folder named "Floc". Files under that
directory were last modified 2021-10-27 though, so it might be that this
was created by an older version of chromium and isn't used
The `TMPDIR` workaround has been removed with
https://github.com/canonical/firefox-
snap/commit/250d24a72953fd797a10ec2fe338fcd0fe2491ff in the beta branch.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Screenshots have been updated in the snap store.
** Changed in: chromium-browser (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1972020
Title:
** Changed in: chromium-browser (Ubuntu)
Assignee: (unassigned) => Nathan Teodosio (nteodosio)
** Changed in: chromium-browser (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Successfully tested by executing the test plan in the description in a
fully up-to-date jammy VM:
- installed the native messaging portal-enabled firefox snap
- installed the chrome-gnome-shell native connector
- installed the gnome shell integration extension in firefox
- browsed to
Reported the "unexpected operator" error here:
https://gitlab.freedesktop.org/xdg/xdg-
utils/-/merge_requests/52#note_1389020.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970594
Title:
Successfully tested by doing the following:
In a fully up-to-date jammy VM:
$ sudo apt -y install libkf5config-bin
$ export XDG_CURRENT_DESKTOP=KDE
$ export KDE_SESSION_VERSION=5
$ xdg-settings get default-web-browser
firefox.desktop
$ xdg-settings check
** Changed in: firefox (Ubuntu)
Status: Incomplete => New
** Also affects: firefox via
https://bugzilla.mozilla.org/show_bug.cgi?id=1769594
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Fix committed:
https://bazaar.launchpad.net/~mozillateam/firefox/firefox.focal/revision/1552
https://bazaar.launchpad.net/~mozillateam/firefox/firefox.impish/revision/1585
The update will make its way to the security and updates pockets with
the next stable update of firefox.
** Changed in:
** Changed in: chromium-browser (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1714244
Title:
[snap] apparmor denials on
** Changed in: chromium-browser (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1897454
Title:
[snap] Chromium has Wayland support disabled
To
the patch doesn't fix the issue it claims it resolves.
** Affects: xdg-desktop-portal (Ubuntu)
Importance: Medium
Assignee: Olivier Tilloy (osomon)
Status: Fix Released
** Affects: xdg-desktop-portal (Ubuntu Jammy)
Importance: Medium
Assignee: Olivier Tilloy (osomon)
** Description changed:
+ [Impact]
+
+ The firefox snap (default in 22.04) will always report that it thinks
+ it's not the default browser (even when it actually is) for KDE users
+ (this can be seen when browsing to about:preferences).
+
+ This is caused by an upstream bug in xdg-utils (using
** Changed in: xdg-utils (Ubuntu Jammy)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970594
Title:
"xdg-settings check default-web-browser
** Also affects: xdg-utils (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: xdg-utils (Ubuntu Jammy)
Status: New => Confirmed
** Changed in: xdg-utils (Ubuntu Jammy)
Assignee: (unassigned) => Olivier Tilloy (osomon)
** Changed in: xdg-utils (Ubuntu
Yes, this is now fixed with version 100.0-2 in the stable channel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971092
Title:
(touch broken: "glxtest: Could not connect to wayland socket" after
** Also affects: firefox via
https://bugzilla.mozilla.org/show_bug.cgi?id=1766854
Importance: Unknown
Status: Unknown
** Changed in: firefox (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Also affects: firefox via
https://bugzilla.mozilla.org/show_bug.cgi?id=1767316
Importance: Unknown
Status: Unknown
** Changed in: firefox (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
There's already an upstream bug report, so the issue is being tracked
there: https://bugzilla.mozilla.org/show_bug.cgi?id=1746759
** Bug watch added: Mozilla Bugzilla #1746759
https://bugzilla.mozilla.org/show_bug.cgi?id=1746759
** Also affects: firefox via
Would it make sense to propose an update to the browser-support
interface to allow read access to $HOME/.local/share/jupyter ? If it's
not totally unreasonable I'm happy to do it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It looks like the issue discussed here:
https://askubuntu.com/questions/1222627/cannot-open-snap-apps-cannot-
perform-operation-mount-rbind-dev-tmp-snap
Can you try the proposed solution there, and report whether this fixes
the problem?
--
You received this bug notification because you are a
This is the actual error:
error: cannot perform the following tasks:
- Ejecutar el enganche de configuración del snap "firefox" si está presente
(run hook "configure": cannot perform operation: mount --rbind /dev
/tmp/snap.rootfs_jnW6N5//dev: No such file or directory)
--
You received this
Lars, that's bug #1965636.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970148
Title:
Brave & Chrome browsers freezes on download and print to pdf
To manage notifications about this bug go to:
Those should be reported upstream at
https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970492
Title:
Firefox update pushing me to update to
@Jonathan, does it make a difference if you install xdg-desktop-portal-
gnome ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967539
Title:
All file downloads fail
To manage notifications about
** Changed in: firefox (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967539
Title:
All file downloads fail
To manage notifications about this bug go to:
://flags/#ozone-platform-hint to try out native Wayland support.
** Changed in: chromium-browser (Ubuntu)
Assignee: (unassigned) => Olivier Tilloy (osomon)
** Changed in: chromium-browser (Ubuntu)
Status: Confirmed => Fix Committed
** Changed in: chromium-browser (Ubuntu)
Impo
It is currently building in that PPA, and once built will have to
undergo testing and validation, before it can be released to bionic-
security and bionic-updates.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: xdg-utils (Ubuntu)
Assignee: (unassigned) => Olivier Tilloy (osomon)
** Changed in: xdg-utils (Ubuntu)
Status: Confirmed => In Progress
** Changed in: xdg-utils (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are
Also note that with version 100.0 (currently in the candidate channel,
to be released to the stable channel later today), you can force the use
of native Wayland by running the firefox snap with MOZ_ENABLE_WAYLAND=1.
** Changed in: firefox (Ubuntu)
Assignee: (unassigned) => Olivier Til
It turns out it's a known issue: https://gitlab.freedesktop.org/xdg/xdg-
utils/-/issues/10.
** No longer affects: kubuntu-meta (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970594
Title:
Those are good points. I'm a bit baffled that this was not noticed by
other users of xdg-settings earlier. Maybe KDE users don't usually rely
on it? I'll file an upstream bug.
** Bug watch added: gitlab.freedesktop.org/xdg/xdg-utils/-/issues #10
https://bugzilla.mozilla.org/show_bug.cgi?id=1767231
Importance: Unknown
Status: Unknown
** Changed in: firefox (Ubuntu)
Status: New => Fix Committed
** Changed in: firefox (Ubuntu)
Assignee: (unassigned) => Olivier Tilloy (osomon)
--
You received this bug notification b
As Aaron points out in the description, when I run `ubuntu-bug firefox`
here I'm seeing the dialog with the link to
https://support.mozilla.org/kb/file-bug-report-or-feature-request-
mozilla, so I'm not able to reproduce the problem. I wonder what might
be causing this different behaviour.
--
I suppose that would work (although I haven't actually tested to
confirm, but it looks correct and I'm trusting your shell-fu). The real
questions are:
* why is this working in stock Ubuntu (where /bin/sh is also a symlink
to dash) and not in Kubuntu?
* why does the upstream project declare
** Changed in: chromium-browser (Ubuntu)
Assignee: (unassigned) => Olivier Tilloy (osomon)
** Changed in: chromium-browser (Ubuntu)
Importance: Undecided => High
** Changed in: chromium-browser (Ubuntu)
Status: New => In Progress
--
You received this bug notification be
Thanks for following up. There was probably a way to remove the lock
file without stopping snapd and completely purging the chromium snap,
but I'm glad that it worked for you anyway.
The messages you're seeing are harmless, you can safely ignore them.
** Changed in: chromium-browser (Ubuntu)
The 91.8.1 update was released to the security pockets for bionic, focal
and impish.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970502
Title:
New release 91.8
To manage notifications about
No, this is in fact an upstream regression
(https://bugzilla.mozilla.org/show_bug.cgi?id=1751363).
Can you try running the firefox snap with MOZ_DISABLE_RDD_SANDBOX=1 and
report whether this works around the problem for you?
** Bug watch added: Mozilla Bugzilla #1751363
** Summary changed:
- apparmor denied when trying to load pkcs11 module for smart card
authentication
+ [snap] apparmor denied when trying to load pkcs11 module for smart card
authentication
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
*** This bug is a duplicate of bug 1967632 ***
https://bugs.launchpad.net/bugs/1967632
** This bug has been marked a duplicate of bug 1967632
apparmor denied when trying to load pkcs11 module for smart card
authentication
--
You received this bug notification because you are a member of
** Changed in: firefox (Ubuntu)
Status: Incomplete => Invalid
** Changed in: chromium-browser (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970459
The error message indicates that you already have a chromium instance
running. Can you try closing all instances (including hidden ones by
examining the output of `ps -ef | grep chromium`), and run chromium
again from the CLI ?
** Changed in: chromium-browser (Ubuntu)
Status: New =>
Can you open about:support in a tab, click the button to copy the raw
data to the clipboard, and attach it here?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970615
Title:
WebGL does not work in
Also affecting the firefox snap, from duplicate bug #1970607.
** Also affects: firefox (Ubuntu)
Importance: Undecided
Status: New
** Changed in: firefox (Ubuntu)
Status: New => Confirmed
** Summary changed:
- [snap] Libreoffice does not open files from thunderbird (more
*** This bug is a duplicate of bug 1790608 ***
https://bugs.launchpad.net/bugs/1790608
** This bug has been marked a duplicate of bug 1790608
[snap] Libreoffice does not open files from thunderbird (more general: from
/tmp)
--
You received this bug notification because you are a member
** Changed in: chromium-browser (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970148
Title:
Brave & Chrome browsers freezes on download and print to
If you're using the upstream tarball, this is not the place to report
the problem. Try https://bugzilla.mozilla.org/ instead. Note that in any
case, 91.0.2 is outdated: stable is currently at 99.0.1, and ESR at
91.8.0.
--
You received this bug notification because you are a member of Ubuntu
Can you please elaborate on how safe mode doesn't work? Is the
application not launching at all? Is its execution malfunctioning?
** Changed in: firefox (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
I'm reporting this issue from stock Ubuntu, but the problem is observed
only in Kubuntu (can be reliably reproduced in a Kubuntu 22.04 VM). The
version of xdg-utils is identical.
This problem was initially reported on the snapcraft forum:
Try this, and let us know whether this resolves the problem:
sudo apt install xdg-desktop-portal-gnome
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970148
Title:
Brave & Chrome browsers
« the import button just didn't do anything »
This sounds like you're missing the corresponding XDG desktop portal
implementation.
Try:
sudo apt install xdg-desktop-portal-gnome
** Changed in: firefox (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because
Support for firefox in Ubuntu 16.04 is provided through the snap
package, see
https://wiki.ubuntu.com/SecurityTeam/ESM/16.04#Firefox_.2F_Thunderbird_.2F_LibreOffice.
The versions that you're mentioning do not correspond to any supported
package in the Ubuntu archive.
** Changed in: firefox
Just tested this in a freshly installed Kubuntu 22.04 in a VM, and the
firefox snap is set as the default browser, and I can change back and
forth between it and other applications under System Settings >
Applications > Default Applications > Web Browser.
Also verified that it is actually used as
I cannot observe the problem described here when running the latest
stable version of google chrome in a fully up-to-date 22.04 VM.
Regardless, if this is a problem that happens in brave or Google Chrome,
it should be reported to the upstream projects. See
** Changed in: firefox (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969910
Title:
Firefox lost passwords, saved tabs, settings after upgrading to
In Ubuntu 22.04, firefox was automatically transitioned to the snap
package, which is published by Mozilla.
The snap will attempt to import existing profiles if it was never run before.
Could it be that you had installed/tried the firefox snap in the past, and thus
had already an existing
The gnome platform snap, which the firefox snap relies on for libva
drivers, comes with both drivers (i965 and iHD):
$ ls -1 /snap/gnome-3-38-2004/current/usr/lib/x86_64-linux-gnu/dri/ | grep
_drv_video.so
i965_drv_video.so
iHD_drv_video.so
nouveau_drv_video.so
This seems to be an upstream bug indeed:
https://bugzilla.mozilla.org/show_bug.cgi?id=1751363
** Bug watch added: Mozilla Bugzilla #1751363
https://bugzilla.mozilla.org/show_bug.cgi?id=1751363
** Also affects: firefox via
https://bugzilla.mozilla.org/show_bug.cgi?id=1751363
Importance:
** No longer affects: chromium-browser (Ubuntu Xenial)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851250
Title:
[snap] chromium-browser snap cannot upload files outside ~
To manage
(In reply to jaz.zimms from comment #8)
> Do you have more context on this fix? I could use some assistance on how to
> implement it.
There is nothing to implement: the issue is in gtk/mutter, and will be
worked around/fixed there. See
https://gitlab.gnome.org/GNOME/mutter/-/issues/2216 for
I can confirm MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 reliably makes the
problem go away for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968040
Title:
Blanked screen doesn't wake up after locking
Attaching the requested output of drm_info.
** Attachment added: "drminfo.txt"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1968040/+attachment/5580371/+files/drminfo.txt
** Changed in: mutter (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because
Now testing MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0, and it seems to fix my
problem. I'll continue experimenting with it some more to confirm.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968040
Title:
Just tested MUTTER_DEBUG_DISABLE_TRIPLE_BUFFERING=1, and I can still
observe the problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968040
Title:
Blanked screen doesn't wake up after locking
Yes, that's definitely the intention. Mozilla was concerned that they
didn't have automated testing in place to catch bugs and regressions in
a timely manner, hence the temporary revert. See
https://bugzilla.mozilla.org/show_bug.cgi?id=1725245 for more details.
** Bug watch added: Mozilla
Corrado is right, but that's a side effect of disabling native wayland
support in the firefox snap, thus having it use xwayland, rather than an
actual fix to the root cause of the problem. But as Daniel is pointing
out, a proper fix is coming.
Note that only the stable channel has been reverted
The contact URL for the firefox snap in the store was updated to
https://support.mozilla.org/kb/file-bug-report-or-feature-request-
mozilla, which makes it much easier to report a bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: firefox (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741074
Title:
[snap] chrome-gnome-shell extension fails to detect native host
*** This bug is a duplicate of bug 1741074 ***
https://bugs.launchpad.net/bugs/1741074
** This bug has been marked a duplicate of bug 1741074
[snap] chrome-gnome-shell extension fails to detect native host connector
--
You received this bug notification because you are a member of Ubuntu
I reverted to stock mutter (42.0-1ubuntu1), enabled KMS debug in mutter,
and observed that the problem persists. Attaching the corresponding
journal.
** Attachment added: "journal-with-kms-debug.log"
mutter 42.0-1ubuntu2~ppa1 is a locally-patched version with a work-
around for https://gitlab.gnome.org/GNOME/mutter/-/issues/2216, as not
being able to re-order my tabs in firefox was bothering me.
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2216
Update from the launchpad bug:
I bisected mutter and gnome-shell until I identified the revision in
mutter that caused the regression:
https://gitlab.gnome.org/GNOME/mutter/-/commit/26676a829e74859488154cd8c45de1d0b629f3ca.
More specifically, the changes to src/core/events.c. Indeed I rebuilt
I can reproduce the issue described here. I'm using stock Ubuntu dock,
no other gnome-shell extensions other than the ones enabled by default
in Ubuntu, and I'm on jammy fully up-to-date. After I lock my screen and
let the monitor blank, when I unlock it I find that one or several of my
fullscreen
Public bug reported:
Firefox 101+ requires rustc 1.59 and cargo 0.60 to build¹.
The beta phase for Firefox 101.0 begins on 2022-04-28 and release
candidates will be available from 2022-05-26.
We will need these in Ubuntu 22.10 and all supported releases: bionic,
focal, impish, jammy.
¹
I had a look at including geckodriver in the firefox snap, but the
problem is that the executable tries to execute the firefox binary
(/snap/bin/firefox), and under strict confinement it doesn't have the
permission to do that.
geckodriver binary releases can be downloaded from
** Changed in: firefox (Ubuntu)
Assignee: (unassigned) => Olivier Tilloy (osomon)
** Changed in: firefox (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
It's a bit unfortunate that apport uses a general contact URL, it would
be better if the store had an additional field for a bug reporting URL.
I have contacted Mozilla to suggest either changing the contact URL to
point to https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox, or
update the
Crash report for gnome-session-binary:
https://errors.ubuntu.com/oops/d5e2d4b2-b62f-11ec-a2f0-fa163ef35206
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968040
Title:
Blanked screen doesn't wake
** Changed in: apport (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968100
Title:
Reporting firefox bug redirect to general mozilla page
To manage
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2216
https://gitlab.gnome.org/GNOME/mutter/-/issues/2216
** Also affects: mutter via
https://gitlab.gnome.org/GNOME/mutter/-/issues/2216
Importance: Unknown
Status: Unknown
--
You received this bug notification because
Attaching my journal for the current boot, where I have observed the
issue a few times already.
I'm seeing some critical error messages for gnome-session-binary and one
segfault, unsure whether this is related to the problem though.
** Attachment added: "journal.log"
1 - 100 of 8828 matches
Mail list logo
