A snap with the tentative fix is now available in the candidate channel
(amd64 only, revision 1221).
Everyone affected by the bug, could you please refresh to that revision
("snap refresh chromium --candidate") and run it for some time,
reporting here whether the problem went away? Thanks in advan
Daniel: any chance you can test this with the chromium snap from the
beta channel, and confirm the fix?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1811219
Title:
High pre
Right, my testing was incomplete indeed.
I enabled focal-proposed for universe in a fully up-to-date focal VM (amd64),
and verified that issuing "apt install chromium-browser" installed version
83.0.4103.97-0ubuntu0.20.04.1, and that the installation completed successfully
and installed the chro
Thanks for confirming the fix Daniel!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1811219
Title:
High precision touchpad scrolling doesn't work in Wayland sessions
(but
Thanks for the feedback Chris. The garbled icons problem is a different
one indeed, tracked by bug #1867402.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1864365
Title:
[sn
=chromium-vaapi).
** Summary changed:
- vaapi snap does not work with nvidia proprietary drivers
+ [snap] VA-API does not work with nvidia proprietary drivers
** Tags added: snap
** Changed in: chromium-browser (Ubuntu)
Assignee: (unassigned) => Olivier Tilloy (osomon)
** Changed in: chr
Excellent, thanks Dmitry for the feedback!
** Changed in: chromium-browser (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/
Thans for the report Albert.
The fact that chromium is now a strictly confined snap means that you cannot
use /home/albert/.config/google-chrome as your profile directory.
The profile directory has to be under
/home/albert/snap/chromium/{common,current}/.
The default value is $HOME/snap/chromium
This desktop file contains NoDisplay=true because it is meant to be
replaced by the desktop file installed by the snap package, which lives
in /var/lib/snapd/desktop/applications/chromium_chromium.desktop. If
both were visible, desktop environment would show two entries for
chromium, which would be
: chromium-browser (Ubuntu)
Assignee: (unassigned) => Olivier Tilloy (osomon)
** Changed in: chromium-browser (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
ht
Note that the feature is behind an experimental flag which isn't enabled
by default: chrome://flags/#enable-experimental-web-platform-features
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launch
I suspect adding the bluez plug would help, I'm going to push a revision
in the candidate channel with this so you can test and let me know if it
helps.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://b
Tentative fix: https://git.launchpad.net/~chromium-team/chromium-
browser/+git/snap-from-
source/commit/?id=9dbd890c5c48305ad3acc97f8098f6ff8173eeae
** Changed in: chromium-browser (Ubuntu)
Assignee: (unassigned) => Olivier Tilloy (osomon)
** Changed in: chromium-browser (Ubu
Currently building in the candidate channel, should be available for
testing in ~24hrs.
** Changed in: chromium-browser (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser
*** This bug is a duplicate of bug 1868117 ***
https://bugs.launchpad.net/bugs/1868117
** This bug has been marked a duplicate of bug 1868117
[snap] Adapt chromium user agent to avoid "not supported browser"
--
You received this bug notification because you are a member of Desktop
Package
** Tags added: snap
** Changed in: chromium-browser (Ubuntu)
Importance: Undecided => Medium
** Changed in: chromium-browser (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in
Relevant output from DpkgTerminalLog.txt:
=> Installing the chromium snap
==> Checking connectivity with the snap store
==> Installing the chromium snap
fout: cannot communicate with server: timeout exceeded while waiting for
response
Can you try reinstalling, and let us know how this goes?
Now available as revision 1228 in the candidate channel. Please test and
let me know whether this works:
snap refresh chromium --candidate
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launc
Sorry the bug status was incorrect indeed.
So the value of XDG_DATA_DIRS is incomplete, which explains why your
desktop environment doesn't find the desktop file installed by the snap.
Can you verify that /usr/lib/environment.d/990-snapd.conf is present,
and share its contents here?
** Changed i
Possibly related: https://forum.snapcraft.io/t/electronplayer-snap-
acting-strange-in-lubuntu/12624
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1887227
Title:
desktop laun
It seems it's a known bug in LXDE: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=906288 (found by reading
https://forum.snapcraft.io/t/snaps-not-appearing-in-debian9-stretch-
lxde-menu-not-wayland-bug/6866).
** Bug watch added: Debian Bug tracker #906288
https://bugs.debian.org/cgi-bin/bug
*** This bug is a duplicate of bug 1887442 ***
https://bugs.launchpad.net/bugs/1887442
** This bug has been marked a duplicate of bug 1887442
snapd not setting XDG_DATA_DIRS correctly
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed t
Relevant apparmor denial:
juil. 14 15:06:18 bribon dbus-daemon[3041]: apparmor="DENIED"
operation="dbus_method_call" bus="session"
path="/org/freedesktop/FileManager1"
interface="org.freedesktop.FileManager1" member="ShowItems" mask="send"
name="org.freedesktop.FileManager1" pid=6024
label="snap.
This would require a new interface in snapd.
** Also affects: snapd
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1887195
Title:
Note that you will need to manually connect the bluez interface:
snap connect chromium:bluez
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1887201
Title:
[snap] web blu
I installed the snap from the candidate channel, and after enabling the
experimental feature flag, I get a popover dialog that appears to be
searching for compatible bluetooth devices, so it seems to work as
expected. I cannot fully confirm as I don't own a compatible device
though.
David, please
Thanks for the feedback David.
By default the bluez interface is not connected automatically (see
https://snapcraft.io/docs/bluez-interface). Having it auto-connected
would require a store assertion that needs to be requested and approved
by a team of reviewers.
--
You received this bug notifica
** Changed in: firefox (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1863463
Title:
Firefox 75 requires nodejs >= 10.19
Status
** Changed in: firefox (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1859083
Title:
Global menu in Kubuntu is gone in Firefox Be
Chromium 84.0.4147.89 is now in the stable channel (amd64 for now, other
architectures are still building).
** Changed in: chromium-browser (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribe
*** This bug is a duplicate of bug 1776800 ***
https://bugs.launchpad.net/bugs/1776800
** This bug has been marked a duplicate of bug 1776800
Unable to start snap applications if user's home directory is not /home/$USER
--
You received this bug notification because you are a member of Des
Sorry for the lack of timely feedback Konstantin.
Is the latest version of the chromium snap still affected by this bug?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1854091
*** This bug is a duplicate of bug 1875860 ***
https://bugs.launchpad.net/bugs/1875860
** This bug has been marked a duplicate of bug 1875860
local documentation is not accessible from the chromium snap
--
You received this bug notification because you are a member of Desktop
Packages, wh
Note that as a mitigation to bug #1616650, the chromium profile
directory, which was previously versioned in $SNAP_USER_DATA is now
under $SNAP_USER_COMMON, so problems should be much less visible to end
users.
--
You received this bug notification because you are a member of Desktop
Packages, wh
** Changed in: chromium-browser (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1877593
Title:
[snap] Needlessly cats ~/.
Thanks David, your contribution is much appreciated. I talked to the
forum admins, and I've been told you should now be able to post your
original auto-connection request without limitations. Can you please try
again?
--
You received this bug notification because you are a member of Desktop
Packa
Thanks David. The updated snap with the bluez plug is now in the stable
channel (for amd64, other architectures will follow shortly), so I'm
marking this bug fixed. Let's follow up on the auto-connection topic on
the snapcraft forum.
** Changed in: chromium-browser (Ubuntu)
Status: Fix Comm
The plug has been added to all channels, the next builds will have it
(I'm about to push new builds to the edge channel for chromium
85.0.4183.26).
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.l
** Changed in: chromium-browser (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1854091
Title:
[snap] traps on start
Status in chromium
(note that snapd in the edge channel does have the interface)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1887795
Title:
snap "chromium" has bad plugs or slots: system-pac
When I added that plug I was told by the snapd team that unknown/not-
available-yet interfaces would be silently ignored.
It turns out silence is a loud and scary warning.
I'll revert the addition of the plug for now, until snapd 2.46 is
available.
--
You received this bug notification because
https://git.launchpad.net/~chromium-team/chromium-browser/+git/snap-
from-source/commit/?id=91e623624e3cca87bbadfa7db567059d6b8b1ef8
** Changed in: chromium-browser (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, wh
Can you please refresh again to revision 1229 and run the snap with the
following command, and share the output?
chromium --enable-logging=stderr --v=1
** Changed in: chromium-browser (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
The chromium snap is strictly confined, and that means that it cannot
read/write to hidden directories inside the user's home folder (such as
$HOME/.config or $HOME/.cache). That's a security feature to prevent
snap applications from reading other applications' data.
Instead, as you've found out,
The upcoming update to thunderbird 78 will have the calendar features of
lightning integrated, thus fixing this bug.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1849162
Title:
** Changed in: chromium-browser (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1873996
Title:
DevTools does not open at
Not released until in the stable channel.
** Changed in: chromium-browser (Ubuntu)
Status: Fix Released => Fix Committed
** Tags added: snap
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs
** Summary changed:
- chromium unable to launch
+ [snap] chromium unable to launch
** Tags added: snap
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1887793
Title:
[snap]
Thanks Mattias. Could you also try the suggested workaround at
https://forum.snapcraft.io/t/chromium-snap-kernel-has-no-file-
descriptor-comparison-support-operation-not-permitted/18921/2 and let us
know whether this "fixes" the problem for you too?
--
You received this bug notification because y
*** This bug is a duplicate of bug 1575053 ***
https://bugs.launchpad.net/bugs/1575053
Please do not confirm your own bugs.
> Change the folder it's confined to.
As I explained earlier it's a security feature implemented by snapd, the
chromium snap doesn't get to choose where its data is sto
Can you please share the output of the following command?
snap changes --abs-time chromium
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1881923
Title:
No icons in file
Tentative fix to enable building on !amd64: https://git.launchpad.net
/~chromium-team/chromium-browser/+git/snap-from-
source/commit/?id=d8f8bf958810e0b48a1dd9e480fbe2def7e8f9f1
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-bro
https://git.launchpad.net/~chromium-team/chromium-browser/+git/snap-
from-source/commit/?id=ff07991f41f89a21355b6e1c77a4db4393321d47
hopefully fixes it
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bu
** Changed in: firefox (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1879742
Title:
When using Google Meet on Firefox, delay sending soun
Unfortunately if you have to manually delete some caches it's not a
proper fix, merely a workaround. I'm glad it solved the problem for you,
but let's keep this bug open to track the issue and hopefully get to the
bottom of it.
** Changed in: chromium-browser (Ubuntu)
Status: Incomplete =>
** Changed in: thunderbird (Ubuntu)
Assignee: (unassigned) => Olivier Tilloy (osomon)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1888157
Title:
Thunderbird 78
Status
Thanks for testing and the feedback Liz.
The version of mesa-va-drivers in the snap is the one from bionic-
updates (20.0.8-0ubuntu1~18.04.1), as confirmed from the build log and
by comparing checksums after unpacking the snap.
What's the output of `LIBVA_MESSAGING_LEVEL=2 snap run chromium` ?
-
Unfortunately that command shows only very recent changes, and there
doesn't appear to be a switch to make it show older changes.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/
That's great news Liz!
What does chrome://media-internals report as the video decoder when
watching H264 videos?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1816497
Title:
Mojo is the decoder you want for hardware-accelerated video decoding. So
you're good with H264. As for VP9 and AV1, I suppose your GPU doesn't
support those?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
http
** Tags added: snap
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1888380
Title:
Give better experience of migration of deb to snap
Status in chromium-browser package in Ub
This upstream commit fixes the crash:
https://chromium.googlesource.com/chromium/src/+/5fc11d04896442c8941ca0afba364a4d641c926e
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/18
Fixed with https://bazaar.launchpad.net/~chromium-team/chromium-browser
/xenial-stable/revision/1484.
** Changed in: chromium-browser (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromi
This has been reported separately here: https://discourse.mozilla.org/t
/webgl-context-errors-in-firefox-83/70924 (although for different HW
configurations).
Are you running firefox with apparmor confinement? (check the output of
`sudo apparmor_status`).
Can you open about:support and share the c
Glad you found a workaround, but this is a bit concerning.
Let's keep the bug open for now, in case more people report similar
problems.
** Summary changed:
- Chromium does not start
+ [snap] Chromium crashes at startup, deleting fontconfig caches "fixes" it
--
You received this bug notificati
Starting with Ubuntu 20.04, chromium-browser indeed is a transitional
package that installs the chromium snap. But for some reason snapd
doesn't appear to be running on your system.
Can you share the output of the following commands?
systemctl status snapd.service
systemctl start snapd.s
** Changed in: chromium-browser (Ubuntu)
Importance: Undecided => Medium
** Summary changed:
- U2f yubikey stopped working in chromium snap
+ [snap] U2f yubikey not recognized until unplugged and plugged back in
** Tags added: snap
--
You received this bug notification because you are a mem
Thanks for the report Timo. I'm not sure what's happening here. I tested
this like so in a VM:
- generated a custom root CA (e.g. using instructions at
https://help.f-secure.com/product.html?business/threatshield/latest/en/task_50407934989D4923AB76367EA0E627CA-threatshield-latest-en)
- imported
Thanks for the report Patrick.
Are we talking about scaling the webcontents, or the user interface
(tabs bar, address bar, …), or both?
Can you test whether upstream firefox builds (which you can download
from https://www.mozilla.org/firefox/download/thanks) are similarly
affected?
I see that yo
Thanks for the details Pat. Not sure what is going on, but it is good to
know that this is fixed in the upcoming firefox 84. Let's see if
upstream can shed some light on the problem in the bug report you filed
there.
--
You received this bug notification because you are a member of Desktop
Packag
Thanks for the report Vasu, and sorry for the late reply. Is this still
happening with the latest firefox update?
It looks like you're using the nvidia proprietary driver. Could you try
with the free driver (nouveau) and report whether the same problem
happens?
** Changed in: firefox (Ubuntu)
It seems very similar to bug #1894417.
>From your description, you can consistently reproduce the problem?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1899250
Title:
Firefox's vie
Thanks for the report, and sorry for the late reply. Is this still
happening with the latest firefox update?
If I understand correctly, this is not a problem of missing codecs, as
the videos would play if enough buffering was done, right?
** Changed in: firefox (Ubuntu)
Status: New => Inco
I see that CoinMP support was disabled in Ubuntu (it is enabled in
Debian) 5 years ago¹, because of dependency issues. This could/should
probably be revisited.
¹
https://git.launchpad.net/~libreoffice/ubuntu/+source/libreoffice/commit/?h
=ubuntu-groovy-7.0&id=3d9c888b38a35b39f282e6aedfd4ad6d447faf
Thanks for raising again the issue Jan. The github issue is the right
place to track the problem, as it's not specific to chromium. So I'm
closing this bug, but I've put the issue on my radar and I am going to
investigate further.
** Changed in: chromium-browser (Ubuntu)
Status: New => Inva
If you have some time to spare, could you test whether the upstream
builds (which can be downloaded from
https://www.mozilla.org/firefox/download/thanks) are similarly affected,
and if so, file an upstream bug report at
https://bugzilla.mozilla.org/enter_bug.cgi#h=dupes%7CFirefox ?
** Changed in:
What is the output of `systemctl start snapd.service` ?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1904769
Title:
[snap] chromium-browser fails to install the snap becaus
Heather, this is not groovy-specific. It was re-enabled recently in
Debian, but the Ubuntu packages have additional logic that override
this, and force-disable it. See the commit I linked to in comment #1,
which is inside a [ifeq "$(DEB_VENDOR)" "Ubuntu"] conditional.
--
You received this bug not
** Summary changed:
- [snap] Chromium USB enumeration fails with usbmon module is loaded
+ [snap] Chromium USB enumeration fails when usbmon module is loaded
** Tags added: snap
** Changed in: chromium-browser (Ubuntu)
Importance: Undecided => Critical
** Changed in: chromium-browser (Ubuntu
** Tags added: snap
** Changed in: chromium-browser (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1905457
Title:
[snap] Chromium
> I install all localization files and set in Firefox russian language
manually.
Do you mean that you installed language pack extensions from within
firefox?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs
That's right, and upstream langpack extensions will, at best, conflict
with the packaged langpacks.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1905122
Title:
firefox xubuntu.20.04
Thanks for the clarifications Patrick.
I couldn't find an upstream bug report for this issue, would you mind filing
one at https://bugzilla.mozilla.org/enter_bug.cgi#h=dupes%7CFirefox and sharing
the link to it here?
Thanks in advance.
** Changed in: firefox (Ubuntu)
Status: Incomplete =>
Excellent, thanks Timo for the feedback. Let's do that, and leave the
bug status set to incomplete, which will make the bug report auto-expire
if nothing happens within the next 60 days.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chr
Can you share the output of running the following command in a terminal?
find ~/.mozilla/firefox -name *.xpi
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1905122
Title:
firefox
Comment #14 in
https://bugs.chromium.org/p/chromium/issues/detail?id=1128405 suggests
that this might be a hardware issue. Are you able to observe the problem
with other mouses?
** Changed in: chromium-browser (Ubuntu)
Status: New => Incomplete
--
You received this bug notification becaus
** Changed in: firefox (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1896722
Title:
Mozilla Firefox Multiple Arbitrary Code Executio
t for xenial builds.
** Changed in: chromium-browser (Ubuntu)
Status: Confirmed => Fix Committed
** Changed in: chromium-browser (Ubuntu)
Assignee: (unassigned) => Olivier Tilloy (osomon)
--
You received this bug notification because you are a member of Desktop
Packages, which is
** Summary changed:
- firefox crashes with MOZ_WAYLAND_ENABLE=1
+ firefox crashes with MOZ_ENABLE_WAYLAND=1
** Summary changed:
- firefox crashes with MOZ_ENABLE_WAYLAND=1
+ firefox crashes with MOZ_ENABLE_WAYLAND=1 when apparmor profile is enforced
--
You received this bug notification becaus
I can reproduce with firefox 83 on Ubuntu 20.04, and I can confirm that
the suggested addition to the apparmor profile fixes the problem.
** Changed in: firefox (Ubuntu)
Status: New => Confirmed
** Changed in: firefox (Ubuntu)
Importance: Undecided => Medium
--
You received this bug n
The additional rule should probably be:
owner /{dev,run}/shm/wayland.mozilla.ipc.[0-9]* rw,
** Changed in: firefox (Ubuntu)
Assignee: (unassigned) => Olivier Tilloy (osomon)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
Fix committed to all the beta branches
(https://bazaar.launchpad.net/~mozillateam/firefox/firefox-
beta.hirsute/revision/1387), this will become available as updates when
Firefox 84.0 is released.
** Changed in: firefox (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug
For the record, back in April 2019 Canonical requested a separate MLS
API key to use in geoclue in Ubuntu, and the request was initially
acknowledged, but then it was put on hold on Mozilla's end and we never
heard back from them, despite a couple of follow-up e-mails.
>From the discussion in the
Thunderbird 78.5.0 is now available in focal-proposed for wider testing.
See https://wiki.ubuntu.com/Testing/EnableProposed on how to enable updates
from focal-proposed.
Everyone interested, please test and share your feedback here, especially on
how the transition from 68 to 78 goes. Thanks!
--
Note that this update in focal-proposed goes together with enigmail
2:2.2.4-0ubuntu0.20.04.1, also in focal-proposed. If you're using
enigmail, be sure to install both updates together.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thun
Thanks!
** Also affects: firefox via
https://bugzilla.mozilla.org/show_bug.cgi?id=1679335
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs
Jimmy, the guide is correct. The line in your sources.list should look
something like that:
deb http://archive.ubuntu.com/ubuntu/ focal-proposed main universe
Please note that it is safer to selectively update the packages you are
interested in (in this case, thunderbird* and possibly enigmai
(In reply to Virginia Balducci from comment #2)
> I'll add this ticket to the Widget GTK component in the hope their team can
> take a look at this and share their feedback.
Thanks for triaging Virginia. Unfortunately the patch¹ I submitted
almost a month ago hasn't received any feedback yet. How
librsvg 2.50.2+dfsg-1 is now in hirsute. We can proceed with the SRU.
** Changed in: librsvg (Ubuntu)
Status: Triaged => Won't Fix
** Changed in: librsvg (Ubuntu)
Status: Won't Fix => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages,
Uploaded librsvg 2.48.9-1ubuntu0.20.04.1, now sitting in the focal
unapproved queue, waiting for the SRU team to review and accept it.
** Changed in: librsvg (Ubuntu Focal)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, w
101 - 200 of 4859 matches
Mail list logo
