You're welcome, I'm glad we eventually figured it out.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960313
Title:
[snap] chromium crashes regularly
To manage notifications about this bug go to:
Thanks for the additional info and for the logs Chris. So Chromium was
abruptly killed, and the logs don't contain any hint as to why this
might have happened.
I wonder whether this could be an out of memory situation, where the
kernel decided to kill Chromium to free up memory. Could you inspect
Excellent, thanks for following up! I'm glad the issue is resolved for
you.
** Changed in: chromium-browser (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Excellent, thanks for following up Tommy. I'm glad the issue is
resolved. I'm closing this here, would you mind closing the upstream bug
report (https://bugzilla.mozilla.org/show_bug.cgi?id=1729901) yourself?
** Changed in: firefox (Ubuntu)
Status: Confirmed => Fix Released
--
You
If Chrome works for you, no need to re-install Chromium for now. The bug
report and the debug information you provided already contain valuable
information. Thanks!
** Summary changed:
- [snap] some pulldown menus corrupted in 21.10
+ [snap] Graphics corruption with bookmark menus on AMD Ryzen 3
You were using firefox 94.0+build3-0ubuntu0.21.10.1 at the time this bug
was reported, if you keep your system up-to-date with security updates,
you should now be at version 97.0+build2-0ubuntu0.21.10.1.
Check the output of `firefox --version`.
--
You received this bug notification because you
Henning, can you test whether the latest firefox update fixed the
problem, by any chance? The upstream bug report was closed, which makes
me think it should be fixed, so your confirmation would be welcome.
** Changed in: firefox (Ubuntu)
Status: New => Incomplete
--
You received this bug
Hi Joseph, and sorry for the lack of response until now. Is the latest
snap from the stable channel still affected by this problem?
** Changed in: chromium-browser (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
David, I wasn't suggesting to remove chromium, rather to install chrome
alongside to check whether they behave differently with regards to your
problem.
Note that Chrome is Google's proprietary and branded version of
Chromium, which is fully open-source. Chrome has some additional
features that
David, would you mind installing chrome from Google (from
https://www.google.com/intl/en/chrome/) to test and report whether it is
also affected by the same problem (error messages in chrome://gpu and
corrupted menus)?
--
You received this bug notification because you are a member of Ubuntu
These log messages from chrome://gpu are probably relevant:
[14846:14846:0214/054358.968962:ERROR:sandbox_linux.cc(377)] :
InitializeSandbox() called with multiple threads in process
gpu-process.
*
[14846:14846:0214/054359.464803:WARNING:angle_platform_impl.cc(49)] :
ProgramGL.cpp:989
** Changed in: firefox (Ubuntu)
Status: In Progress => 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/1960655
Title:
Firefox 97.0 is out since 3 days and not yet updated
To
Fixed with
https://bazaar.launchpad.net/~mozillateam/thunderbird/thunderbird.jammy/revision/675.
** Changed in: thunderbird (Ubuntu)
Status: Confirmed => Fix Committed
** Changed in: thunderbird (Ubuntu)
Assignee: (unassigned) => Olivier Tilloy (osomon)
--
You received th
Fixed with
https://bazaar.launchpad.net/~mozillateam/thunderbird/thunderbird.jammy/revision/674.
** Changed in: thunderbird (Ubuntu)
Status: New => Fix Committed
** Changed in: thunderbird (Ubuntu)
Assignee: (unassigned) => Olivier Tilloy (osomon)
** Changed in: thunderbird (
You shouldn't run apport-collect as root (with sudo).
Can you please attach the output of `lspci -v`.
Can you also open chrome://gpu in chromium, click the "Copy Report to
Clipboard" button, and paste it here? Thanks!
--
You received this bug notification because you are a member of Ubuntu
nee: (unassigned) => Olivier Tilloy (osomon)
** Changed in: firefox (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960655
Title:
Firefox 97.0 is ou
I'm going to close the bug task for Firefox, please file an upstream bug
at https://bugzilla.mozilla.org/enter_bug.cgi if you care about the snap
use case, because that's where we track snap-related issues. Thanks!
** Changed in: firefox (Ubuntu)
Status: Incomplete => Invalid
--
You
Interestingly, in the firefox deb opening webcal:// hyperlinks works
OOTB, without any change (after thunderbird has been registered as a
handler for them).
** No longer affects: firefox
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I have tested adding a custom protocol handler in Firefox by creating
the following entries in about:config :
network.protocol-handler.expose.webcal
network.protocol-handler.external.webcal
network.protocol-handler.warn-external.webcal
and I did manage to get a new entry for the webcal
Well, it does allow xdg-open to open thunderbird when passed a webcal://
URL, but it's not enough to instruct firefox to do the same, apparently.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960421
https://bazaar.launchpad.net/~mozillateam/thunderbird/thunderbird.jammy/revision/672
should do the trick.
** Also affects: thunderbird (Ubuntu)
Importance: Undecided
Status: New
** Changed in: thunderbird (Ubuntu)
Assignee: (unassigned) => Olivier Tilloy (osomon)
** Chan
Ok, that's because the deb package (which wraps the snap) isn't
installed.
Can you try the following:
sudo apt -y install chromium-browser
apport-collect 1948052
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The firefox and chromium snap both connect by default to the system-
packages-doc interface¹ which provides read-only access to
/usr/share/doc.
I'm pretty sure it wouldn't be hard to convince snapd folks to update
the interface to add access to /usr/share/gtk-doc.
Can you check whether the
** Changed in: firefox (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1956865
Title:
[snap] firefox webauthn not working with tomu u2f
To manage
Thanks for testing and confirming Jan.
I have filed https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1960220
to request kubuntu to install xdg-desktop-portal-gtk by default.
I think it is now safe to close this bug.
--
You received this bug notification because you are a member of
** This bug is no longer a duplicate of bug 1838038
[snap] Snapped apps do not work with .local mdns/avahi name resolution
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1956365
Title:
Firefox
I see that you're running firefox version 91.0.
This version is outdated, I strongly suggest you update to the latest version
(97.0) and check whether the problem is fixed there.
The problem sounds similar to this upstream bug:
https://bugzilla.mozilla.org/show_bug.cgi?id=1719988.
** Bug watch
Thanks David.
Can you please run the following command in a terminal?
apport-collect 1948052
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1948052
Title:
[snap] some pulldown menus corrupted
Have you tried registering a custom protocol handler, as described here:
https://askubuntu.com/questions/514125/url-protocol-handlers-in-basic-
ubuntu-desktop/1023143#1023143 ?
I did try to pass e.g.
*** This bug is a duplicate of bug 1838038 ***
https://bugs.launchpad.net/bugs/1838038
This is in fact a known problem: bug #1838038.
** This bug has been marked a duplicate of bug 1838038
[snap] Snapped apps do not work with .local mdns/avahi name resolution
--
You received this bug
To follow up on Michael Kaply's comment (#3), using the firefox snap one
can install Firefox from the beta channel, nightly, ESR, or even all of
them in parallel. See
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1515125/comments/3
for details.
--
You received this bug notification
** Changed in: firefox (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1515125
Title:
Ability to install Firefox Developer Edition on Ubuntu together
This is now possible using snapd's parallel installs feature¹:
$ sudo snap set system experimental.parallel-instances=true
$ sudo snap install firefox
$ sudo snap install firefox firefox_esr
$ sudo snap refresh firefox_esr --channel=esr/stable
$ sudo snap install firefox
I'm not seeing those when running firefox in a fully up-to-date impish
(21.10) VM.
Can you share details on the version of Ubuntu and version of Firefox?
Are those triggered by navigating to certain domains?
** Changed in: firefox (Ubuntu)
Status: New => Incomplete
--
You received this
Thanks for the report Evgeniy.
I'm not sure whether the problem is with installing chromium, or whether
the browser crashed while using it?
If the former, I'd advise trying to reinstall:
sudo apt reinstall chromium-browser
If the latter, are you observing the crash regularly? Is it still
Excellent, I'm glad the problem is resolved for you. This might have
been caused by a failure to use the default ANGLE renderer (bug
#1959416).
** Changed in: chromium-browser (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of
Can you please run `apport-collect 1956348` to attach additional debug
information to this bug?
Is this still happening with the latest revision of the chromium snap in
the stable channel?
** Summary changed:
- Chromium uses 100% CPU after upgrade to 20.04
+ [snap] Chromium uses 100% CPU after
Ian, would it be possible to consider mounting /usr/local/share/ca-
certificates in the snap's mount namespace, similar to what is done for
/etc/ssl ? Or would this present security concerns?
Alternatively, would it work for chromium to use the system-files
interface to expose
Thanks for the report Haggen, and sorry for the lack of feedback until
now.
The links to the screenshots are broken. Would you mind attaching the
screenshots to the bug report?
Also, please run `apport-collect 1955827` to attach additional debug
information to the bug. Thanks!
** Changed in:
Sorry for the lack of feedback until now Gary. I see that you closed the
bug as invalid, is it now working as expected?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1956365
Title:
Firefox snap
Hi David (and anyone else affected). Is this still happening with the
latest update of the chromium snap in the stable channel?
If so, can you please share more information about your system by
running `apport-collect 1948052`?
It would also be helpful if you could attach a screenshot or
I submitted https://github.com/snapcore/snapd/pull/11366 to get this
vendor/product combo added to the u2f-devices interface in snapd.
** Changed in: firefox (Ubuntu)
Importance: Undecided => Medium
** Changed in: firefox (Ubuntu)
Assignee: (unassigned) => Olivier Tilloy (
Stefan, that's a different problem, can you please file a separate bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821765
Title:
[snap] Missing icon in indicator
To manage notifications about
Thanks for the report Vladimir. Can you test again and let us know
whether the problem is still happening with the latest revision of
chromium in the stable channel?
** Changed in: chromium-browser (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a
What is the value of your system theme reported in about:support ?
On my system where the value is "Yaru / Yaru", I can see a difference in
the title bar color between focused and unfocused windows, so it's
probably a theme-specific problem.
** Changed in: firefox (Ubuntu)
Status: New =>
** Changed in: firefox (Ubuntu)
Importance: Undecided => High
** Changed in: firefox (Ubuntu)
Assignee: (unassigned) => Olivier Tilloy (osomon)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
Thanks for the additional info.
We can rule out a background refresh of chromium or any of its dependencies
(core20, gnome-3-38-2004, gtk-common-themes).
Since the crash reporter isn't enabled in chromium (it's a chrome-
specific thing), may I suggest that you run chromium from a terminal
with
No worries, this is understandable.
Given that this isn't a problem specific to the Firefox Ubuntu package,
and that fortunately you managed to work around the problem by using
Chrome to download the iso, I'm closing this bug.
Thanks again for the report.
** Changed in: firefox (Ubuntu)
Sorry for the lack of a timely response.
If this was a crash, no bug was opened, only a crash report which was
automatically uploaded to errors.ubuntu.com.
You can inspect the list of all the crashes you reported with the
following command:
xdg-open https://errors.ubuntu.com/user/$(sudo cat
Possibly related: https://forum.snapcraft.io/t/some-snap-apps-no-longer-
starting-up-on-amd-laptop/26403.
That post mentions that core20-based snaps aren't affected, and chromium
was recently updated to core20. To anyone affected, can you please test
again and let us know whether the problem is
Thanks for the feedback. Given that this is happening on Windows, would
you mind filing an upstream bug at
https://bugzilla.mozilla.org/enter_bug.cgi#h=dupes|Firefox, and sharing
the link to it here?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Could you please share the output of the following commands?
snap info --abs-time gnome-3-38-2004
snap info --abs-time core20
snap get core experimental.refresh-app-awareness
** Summary changed:
- chromium-browser has started closing regularly
+ [snap] chromium crashes regularly
Just tested this with Firefox 97.0 installed as a snap (candidate
channel) on Ubuntu 21.10, and the iso downloads fine from the http link
in the description.
Also tested in an Ubuntu 20.04 VM with Firefox 96.0.3 installed as a
snap (stable channel), and the iso also downloads fine from the http
This is the relevant output from DpkgTerminalLog.txt:
error: cannot perform the following tasks:
- Mount snap "chromium" (1897) (systemctl command [start
snap-chromium-1897.mount] failed with exit status 1: Job failed. See
"journalctl -xe" for details.
)
Could you please run the following
** Bug watch added: Mozilla Bugzilla #1754164
https://bugzilla.mozilla.org/show_bug.cgi?id=1754164
** Also affects: firefox via
https://bugzilla.mozilla.org/show_bug.cgi?id=1754164
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member
LDZ: the firefox snap is not classic, it is strictly confined, you won't
be able to install it with the "classic" mode.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1956005
Title:
Firefox Snap
I can confirm links to https://api.whatsapp.com/ do not open correctly
in the firefox snap, and they do in the deb. However replacing "api" by
"web" seems to be enough to work around the problem.
** Tags added: snap
** Changed in: firefox (Ubuntu)
Importance: Undecided => Low
--
You
Thanks for the report, and sorry for the lack of response until now.
You mentioned an error while installing the chromium-browser deb package, but
the contents of Snap.Info.chromium.txt show that chromium 97.0.4692.99
(revision 1878) was installed.
Can you elaborate on the error, and what it is
The format of the package is irrelevant for most end users, a warning
wouldn't be helpful (quite possibly the opposite, it would make them
think there is something wrong with the installation, when everything is
working as intended).
Advanced users can use apt to read the description prior to
Tentatively marking the xdg-desktop-portal-gtk task fixed, per my last
comment. Feel free to re-open if it's not working for you.
** Changed in: xdg-desktop-portal-gtk (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: chromium-browser (Ubuntu)
Status: Confirmed => Invalid
Just tested the following on a laptop running fully up-to-date 22.04, in the
default Wayland session:
- firefox snap (97.0)
- firefox deb (97.0)
- chromium snap (98.0.4758.80)
Screen sharing (entire screen and selected windows) works as expected in
all cases.
marco, could you please test
Revision 1899 (for amd64), with the fix, is now in the stable channel.
** 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.
Public bug reported:
See https://bugzilla.mozilla.org/show_bug.cgi?id=1753732 (especially
comment #8) for some context.
A number of desktop snaps are GTK apps, and without xdg-desktop-portal-
gtk installed on the host system the theming integration is poor.
ubuntu's desktop-minimal seed has
Sorry for the lack of responses until now Richard.
The problem is not likely a broken update of the chromium snap, but
rather the update mechanism itself that messes with font caches, so
reverting to a previous version, while possible (see
Note that I've kicked off rebuilds of the stable snap with the fix, so
it won't be necessary to wait for a new upstream release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959416
Title:
[snap]
/chromium-
browser/+git/snap-from-
source/commit/?id=35d0f6379f0d82a40e936b6dee48592add46d204.
** Changed in: chromium-browser (Ubuntu)
Status: Confirmed => Fix Committed
** Changed in: chromium-browser (Ubuntu)
Assignee: (unassigned) => Olivier Tilloy (osomon)
--
You received th
Robie: I just tested on jammy, and I'm seeing something different: with
the flag enabled, screen sharing works (although I do get the window
selection pop-up displayed twice, same as on impish). Without the flag,
I'm seeing a black screen with the mouse cursor, like you do.
Could you test again
Alberto, could it be the same issue that Robie is describing, that the
window selector pop-up appears twice? I'm seeing this too (on Impish),
although screen sharing only works if I confirm the second popup, not if
I cancel it.
--
You received this bug notification because you are a member of
Would you mind filing a bug at
https://bugzilla.mozilla.org/enter_bug.cgi#h=dupes%7CFirefox with all
this information? We're using the upstream bug tracker to manage firefox
snap bugs. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I can confirm most of these issues, after testing in a Kubuntu 22.04 VM,
with a Wayland session:
The issue with the font size (2) might be caused by the use of the
incorrect theme (3). The firefox deb reports in about:support that the
system theme is "Breeze / Adwaita-dark", whereas the snap
Yes indeed, the issue is being discussed in that upstream bug.
** Summary changed:
- I have on clean install some weird folder /home/user/Downloads/firefox.tmp/
+ [snap] I have on clean install some weird folder
/home/user/Downloads/firefox.tmp/
** Tags added: snap
** Also affects: firefox
I can also confirm that the default ANGLE renderer does work for Google
Chrome packaged as a deb when run in headless mode, whereas it doesn't
for the chromium snap.
I'm not sure why that is, but the following log is certainly relevant:
[0204/112747.679225:ERROR:angle_platform_impl.cc(44)]
I can confirm this didn't work in the snap version 97.0.4692.99
(revision 1878) previously in the stable channel, and it is now working
with version 98.0.4758.80 currently in the stable channel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Summary changed:
- unable to use jupyter-notebook package with snap'd browsers like firefox or
chromium
+ browser snaps and other apps can't read files under ~/.local/share/
** No longer affects: chromium-browser
** No longer affects: firefox
** Summary changed:
- browser snaps and other
Just tested on impish with thunderbird 91.5.1, and the problem persists.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1932328
Title:
Thunderbird under Wayland does not correctly close (or manage)
I can confirm the problem.
If I run with the "--use-gl=swiftshader-webgl" command-line option, I
can get WebGL to work in headless mode (as suggested in
https://bugs.chromium.org/p/chromium/issues/detail?id=1209250).
Can you confirm this works around the problem for you too?
** Changed in:
Right, and in this regard it's not a chromium or firefox -specific
problem, it potentially affects all snaps.
Can you access the notebooks when browsing to http://localhost:/ or
http://127.0.0.1:/ though?
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Summary changed:
- Thunderbird 91.5.0 regression: writes attachments to /tmp readable to everyone
+ [upstream] Thunderbird 91.5.0 regression: writes attachments to /tmp readable
to everyone
** Tags added: upstream
--
You received this bug notification because you are a member of Ubuntu
** Summary changed:
- Very high CPU and slow responsiveness in Thunderbird 91.5.0
+ [upstream] Very high CPU and slow responsiveness in Thunderbird 91.5.0
** Tags added: upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
> I notice ports (e.g. arm64) not all getting new build...
The update was built and published for all supported releases (bionic,
focal, hirsute, impish) and architectures. Could it be that you're using
a mirror that hasn't been updated yet?
--
You received this bug notification because you are
There are a number of upstream bug reports for incomplete dark theme
support, see this meta bug:
https://bugzilla.mozilla.org/show_bug.cgi?id=1720770.
** Summary changed:
- Thunderbird 91 does not honor the dark theme
+ Thunderbird 91 does not fully honor the dark theme
** Summary changed:
-
Thanks for the report Robert. Aside from these messages, does firefox
work as expected, or are you seeing problems that you think are linked
to these warnings?
** Changed in: firefox (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
Those are the packages that are typically installed by default for this
specific source package. It is possible that you have installed
additional binary packages (such as libgtk-3-dev or libgtk-3-doc), in
which case you would need to manually downgrade those, too.
The source package is called
bluppfisk, if you have installed the jammy packages on impish, enabling
impish-proposed won't offer the update because the version is greater in
jammy.
You will need to specify the version number to downgrade to the impish
proposed update:
sudo apt install libgtk-3-common=3.24.30-1ubuntu1.1 \
** Changed in: firefox (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/1958231
Title:
Firefox follows when I switch workspaces in Mate
To manage notifications
Simon, there are thunderbird 91.5.0 updates ready for testing in
https://launchpad.net/~ubuntu-mozilla-security/+archive/ubuntu/ppa.
Please use that PPA only for testing updates, it is NOT recommended to
keep it enabled permanently. Feedback welcome!
--
You received this bug notification because
According to /proc/cpuinfo, your processor doesn't appear to support
sse3, which is now a hard requirement for chromium, see
https://bugs.chromium.org/p/chromium/issues/detail?id=1123353. This has
been the case since version 89, released in April 2021.
There is unfortunately nothing that can be
** No longer affects: cargo (Ubuntu Hirsute)
** No longer affects: rustc (Ubuntu Hirsute)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1952104
Title:
rustc 1.57 and cargo 0.58 to build firefox 97
I re-opened the jammy tasks since the requirement was bumped to rustc
1.57 and cargo 0.58.
** Changed in: cargo (Ubuntu)
Status: Fix Released => Confirmed
** Changed in: rustc (Ubuntu)
Status: Fix Released => Confirmed
--
You received this bug notification because you are a
Andreas, please file a new bug to track this separately. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946599
Title:
Firefox break when returning from console with wayland (nvidia) on
** Summary changed:
- [upstream] can't manually sort bookmarks anymore
+ [upstream] regression: drag'n'drop broken
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1956888
Title:
[upstream]
*** This bug is a duplicate of bug 1956888 ***
https://bugs.launchpad.net/bugs/1956888
** This bug has been marked a duplicate of bug 1956888
[upstream] can't manually sort bookmarks anymore
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This appears to be fixed in chrome 99.0.4818.0 (currently in the dev
channel), as advertised in
https://bugs.chromium.org/p/chromium/issues/detail?id=1279532.
** Summary changed:
- can't manually sort bookmarks anymore
+ [upstream] can't manually sort bookmarks anymore
** Tags removed: snap
--
chrome installed as a deb appears to be similarly affected, so it's not
a chromium-specific problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1956888
Title:
can't manually sort bookmarks
I can confirm the original issue with dragging and dropping bookmarks to
re-order them, and I can confirm that the workaround suggested in
comment #11 (disable "Use system title bar and borders") works.
** Changed in: chromium-browser (Ubuntu)
Importance: Undecided => Medium
--
You received
** Changed in: firefox (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/1940417
Title:
On Wayland toolbar menus are sometimes invisible/flickering
To
** Changed in: chromium-browser (Ubuntu)
Status: Expired => New
** Tags added: snap
** Summary changed:
- apparmor warning when using chromedriver snap
+ [snap] apparmor warning when using chromedriver
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Unlikely to happen for hirsute, which will be EOL on January 20.
Tagging for consideration in impish.
** Tags added: rls-ii-incoming
** Tags removed: rls-jj-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Julian, how can the end-user tell the difference between ESM Infra and
ESM Apps, if the latter hasn't been properly announced yet?
I am now myself confused as to why ESM (Infra or Apps) would be enabled
at all on an LTS release that hasn't reached its EOL yet (we're talking
about 20.04 here).
Thanks for testing, and for the feedback Alberto.
Let's say it's okay to assume that the portal is already running and accessible
through the bus (i.e. the ListActivatableNames path won't be taken − there's an
upstream bug to track this:
201 - 300 of 8828 matches
Mail list logo
