That's suspicious, can you please share the output of `ls -l
/snap/chromium/current/usr/lib/chromium-browser/chrome-sandbox` ?
Is the latest update (revision 1269) similarly affected?
** Changed in: chromium-browser (Ubuntu)
Status: New => Incomplete
--
You received this bug notification
** Changed in: chromium-browser (Ubuntu)
Status: New => Confirmed
** Changed in: chromium-browser (Ubuntu)
Importance: Undecided => Medium
** Summary changed:
- [snap] Gnome dash window tracking is broken when using chromium snap
+ [snap] No separate icon/window tracking for app launch
When you do report it upstream, please share the link to the upstream
bug report here. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1861262
Title:
Add message/rfc822 to thunderbird.desktop
** Tags added: snap
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891649
Title:
[snap] Gnome dash window tracking is broken when using chromium snap
To manage notifications about this bug go to:
h
*** This bug is a duplicate of bug 1886414 ***
https://bugs.launchpad.net/bugs/1886414
** This bug has been marked a duplicate of bug 1886414
the chromium snap takes a long time to install without visible user
feedback, seems stuck
--
You received this bug notification because you are a
If a user installs the chromium-browser package afresh, without any
existing profile, I would argue that they don't care that the browser is
packaged as a snap, because they haven't used it before (not on that
machine at least).
Manually installing chromium-browser with apt does display messages t
** 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/1892779
Title:
Browser will not play videos
To manage notifications about this bug go to:
This appears to be a timeout when downloading the chromium snap from the
store. Can you please try again, and let us know how this goes?
sudo apt install chromium-browser
** Changed in: chromium-browser (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because
Relevant log from DpkgTerminalLog.txt:
==> Installing the chromium snap
error: cannot perform the following tasks:
- Download snap "chromium" (1260) from channel "stable" (received an unexpected
http response code (408) when trying to download
https://api.snapcraft.io/api/v1/snaps/download/XKEcB
https://launchpad.net/ubuntu/+source/thunderbird/1:78.2.0+build1-0ubuntu1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888157
Title:
Thunderbird 78
To manage notifications about this bug go to:
h
: High
Assignee: Olivier Tilloy (osomon)
Status: Fix Committed
** Description changed:
For a complete rational, see comments #4, #5, #7 and #8 in bug #1889106,
and the discussion in https://lists.ubuntu.com/archives/ubuntu-
devel/2020-August/041127.html.
+
+ This needs to be
1:84.0.4147.135-0ubuntu1 uploaded to groovy.
** Changed in: chromium-browser (Ubuntu)
Status: Triaged => 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/1892724
Title:
Bump packa
Quoting the ubuntu-devel@ conversation here for easier future reference:
« In doing SRU reviews today, I came across LP: #1889106 which is a
request for a no-change rebuild to bump the version so it beats the
versions presented in previous releases.
The problem is real, but it seems suboptimal to
Tests now pass with nodejs 12.18.2~dfsg-1ubuntu2 in groovy-proposed:
https://autopkgtest.ubuntu.com/packages/n/node-sha.js/groovy/ppc64el
https://autopkgtest.ubuntu.com/packages/n/node-crypto-browserify/groovy/ppc64el
https://autopkgtest.ubuntu.com/packages/n/node-create-hash/groovy/ppc64el
Verified working.
For convenience I used a slightly different testing method than the test case
in the bug description: I downloaded and installed (with `dpkg -i`) the
chromium-browser, chromium-browser-l10n and chromium-codecs-ffmpeg-extra debs
from
https://launchpad.net/ubuntu/+source/chromiu
Thanks Robie for the suggestion. I hadn't thought of an epoch bump, but
it sounds like a good solution to the recurring problem at hand.
This is the ubuntu-devel@ discussion for reference:
https://lists.ubuntu.com/archives/ubuntu-devel/2020-August/041127.html.
I am going to test the package in fo
Thanks Łukasz.
In the meantime the 84.0.4147.105 update was published to
{xenial,bionic}-{security,updates}, so the version number needs bumping
again, for the upgrade path to really work.
I have uploaded 84.0.4147.105-0ubuntu1 to groovy-proposed, and
84.0.4147.105-0ubuntu0.20.04.1 is now in the
Fixed with https://git.launchpad.net/~chromium-team/chromium-
browser/+git/snap-from-
source/commit/?id=9dfbfe4fd02e254354ec038a9aa3da26980b89d2.
** Changed in: chromium-browser (Ubuntu)
Assignee: (unassigned) => Olivier Tilloy (osomon)
** Changed in: chromium-browser (Ubuntu)
Sta
Reported as an upstream Node.js bug:
https://github.com/nodejs/node/issues/34666
** Description changed:
Since nodejs 12.18.1 entered groovy-proposed, autopkgtests that rely on
node-sha.js to compute SHA-1 hashes started failing reliably on ppc64el.
This affects the following packages:
** Description changed:
From this e-mail thread: https://admin.hostpoint.ch/pipermail/enigmail-
users_enigmail.net/2020-August/005691.html
JSUnit hasn't been and won't be ported to Thunderbird 78. Thunderbird 78
is currently building in groovy-proposed, once it migrates (together
with
Public bug reported:
>From this e-mail thread: https://admin.hostpoint.ch/pipermail/enigmail-
users_enigmail.net/2020-August/005691.html
JSUnit hasn't been and won't be ported to Thunderbird 78. Thunderbird 78
is currently building in groovy-proposed, once it migrates (together
with enigmail 2.2)
If so that kind of feedback isn't constructive, and this bug report
isn't the right place for it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886414
Title:
the chromium snap takes a long time to
Unfortunately, that was a red herring. I rebuilt nodejs for ppc64el with
that commit reverted, but it didn't help.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887144
Title:
autopkgtest failures o
Sorry, I'm not sure what you mean with that last comment. Can you please
elaborate?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886414
Title:
the chromium snap takes a long time to install withou
Just a wild guess that will need testing: https://chromium-
review.googlesource.com/c/v8/v8/+/1649711 might be related, would
reverting it help?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887144
T
(note that I'm not suggesting the above as a workaround, we need to dig
deeper and understand where this incorrect optimization comes from)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887144
Title:
To further prove the point, adding `eval('')` to the body of ft()
ensures that the function is not optimized by V8, and the tests reliably
pass.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887144
T
** Summary changed:
- autopkgtest failures on ppc64el with nodejs 12.18.1
+ autopkgtest failures on ppc64el with nodejs 12.18.2
** Also affects: nodejs (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
Some progress: running one of the failing tests through nodejs with the
--no-opt flag (for no optimizations) makes it consistently pass.
It looks like V8 is optimizing too aggressively, and incorrectly.
I can observe that when values start diverging, ft() is being called
with s===2, and despite t
Some notes while I continue investigating the problem:
- while I used the last test in test/test.js to highlight the problem,
it isn't the only one that is failing
- both sha.js and sha1.js are affected (unsurprisingly, as they have
very similar implementations), other algorithms (sha224, sha25
As pointed out by Evangelos in
https://groups.google.com/a/chromium.org/g/chromium-packagers/c/ZytNtRam5II/m/4o9ql5IaAwAJ?pli=1,
geolocation started working again on July 29th.
Marking the bug fixed accordingly, let's hope this doesn't break unexpectedly
again.
** Changed in: chromium-browser (
Can you try re-installing the package, and let us know how this goes?
sudo apt reinstall chromium-browser
** Changed in: chromium-browser (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
Relevant excerpt from DpkgTerminalLog.txt:
Preparing to unpack .../19-firefox_79.0+build1-0ubuntu0.20.04.1_amd64.deb ...
/var/lib/dpkg/tmp.ci/preinst: 1: awk: Too many levels of symbolic links
Exception ignored in: <_io.TextIOWrapper name='' mode='w'
encoding='utf-8'>
BrokenPipeError: [Errno 32]
Can you try running the following command in a terminal, and let us know
how it goes?
sudo apt reinstall firefox
** 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.
htt
This is most likely the snap strict confinement that prevents communication
with the serial device.
Can you please run the following command in a terminal, then run chromium and
reproduce the problem, and share the output of the terminal here?
journalctl -f | grep chromium
** Changed in: ch
Although the absence of a global menubar in GNOME by default did
influence this particular decision, the main factor was the increasing
difficulty to maintain the firefox patch that enabled the feature. The
patch was quite large (several thousands LOC) and heavily relied on
internal APIs that have
Yes, this would need to be removal + sync blacklist for groovy, to be on
the safe side (although it's unlikely that Debian would ever upload a
new version).
I think it's OK for the package to be broken in focal. No one has ever
complained thus far, so my guess is that no-one uses it.
--
You rece
Public bug reported:
>From https://sourceforge.net/u/pbrunschwig/tinyjsd/wiki/Home/:
« Note: due to the massive and rapid changes in the Mozilla Platform,
TinyJSD is no longer actively maintained. The last version supports
Thunderbird 60/SeaMonkey 2.57. We recommend to use the standard
Develope
*** This bug is a duplicate of bug 1877109 ***
https://bugs.launchpad.net/bugs/1877109
** This bug is no longer a duplicate of bug 1864365
[snap] Dialog font missing
** This bug has been marked a duplicate of bug 1877109
incompatible host fonts cache causing snap app instability
--
You
*** This bug is a duplicate of bug 1877109 ***
https://bugs.launchpad.net/bugs/1877109
** This bug has been marked a duplicate of bug 1877109
incompatible host fonts cache causing snap app instability
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Unfortunately no, the patch doesn't affect the outcome of tests on
ppc64el (I did try reverting it, and the problem has also been reported
upstream, which doesn't carry the patch).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
** Changed in: thunderbird (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/1887433
Title:
Print dialog from Thunderbird appears behing thunderbird window
To
While we appreciate this is effectively a functional regression, it is
intended. Exposing firefox's menus to the global menu bar involved a
non-trivial distro patch that was increasingly difficult to maintain
(because it relied on many internal APIs), so it was dropped before
20.04 (see
https://baz
** Changed in: thunderbird (Ubuntu)
Status: New => Confirmed
** Changed in: thunderbird (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890148
Title:
While the 68.x series isn't the current series (78.x is), it is still
officially supported, with point releases for security fixes. We are
working on updating thunderbird to the 78.x series in Ubuntu, and it
will be backported to 20.04 in due course.
It is fair to assume that unless it's a critica
(the above comment applies to the last test in test/test.js with the
label "call digest for more than MAX_UINT32 bits of data".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887144
Title:
autopkgte
Added some logging to the Sha1._update() method which is called
repeatedly, and the problem doesn't appear to be deterministic: it
doesn't always start diverging at the same place (although it's always
early, within the first 100 iterations).
--
You received this bug notification because you are
** Description changed:
Since nodejs 12.18.1 entered groovy-proposed, autopkgtests that rely on
- node-sha to compute SHA-1 hashes started failing reliably on ppc64el.
+ node-sha.js to compute SHA-1 hashes started failing reliably on ppc64el.
This affects the following packages:
- node-
*** This bug is a duplicate of bug 1575053 ***
https://bugs.launchpad.net/bugs/1575053
> `$XDG_CONFIG_HOME/$SOFTWARE_NAME` is the de facto way
That's different from "does not follow the XDG base directory specification".
A specification (hopefully) is unambiguous. Anything else has little obj
The update to version 84 is in progress, but as I wrote earlier it's
targetting 16.04 and 18.04 only. You may try to run the 18.04 packages
on 20.04, but there's no guarantee it will run at all.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
The plot thickens. Can you reliably reproduce this situation, where
unplugging and plugging again the 5C makes it work, but it doesn't after
a reboot?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884
I don't think the specification¹ mandates how folders should be
structured under $XDG_DATA_HOME and $XDG_CONFIG_HOME. Or is there a
follow-up specification that does that?
Hopefully snapd behaves (mostly) the same on all supported
distributions, so distro-hopping shouldn't be a concern either.
¹
There are chromium-browser deb packages with debug symbols (chromium-
browser-dbgsym) published in the Ubuntu archive for Ubuntu 16.04 and
18.04. In newer Ubuntu releases the deb is a wrapper that installs the
chromium snap.
--
You received this bug notification because you are a member of Ubuntu
Additionally to what Sébastien requested, can you do the following:
Open firefox, then press the keyboard shortcut Ctrl+Shift+J. This should
open the browser console. Select everything, copy and paste it here in a
comment, or as an attachment if there is a lot of content.
Thanks in advance.
--
** Also affects: firefox via
https://bugzilla.mozilla.org/show_bug.cgi?id=1656045
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/1888942
Title:
marked
** Changed in: firefox (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1866880
Title:
Firefox Speech Synthesis Not Working in Kubuntu By Default
To manage
Does the following command appear to fix the problem (after restarting
chromium)?
rm -rf ~/snap/chromium/common/.cache
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867402
Title:
[snap] Icons
This behaviour looks intentional to me. Can you please file an upstream
bug report at
https://bugzilla.mozilla.org/enter_bug.cgi#h=dupes%7CFirefox, and share
the link to it here? Thanks!
** Changed in: firefox (Ubuntu)
Status: New => Incomplete
--
You received this bug notification becaus
Can you share the last few lines of `dmesg` after plugging in your
yubikey, to get more information about the device?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884759
Title:
U2f yubikey stopped
Please see my comment on bug #1887396:
https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/1887396/comments/6.
Try moving your profile folders over to the common directory, which is
unversioned. Hopefully this helps.
** Changed in: chromium-browser (Ubuntu)
Status: New => Inco
Indeed, the code to import an existing profile isn't multi-profile
aware, it will only import a profile in the default location.
Contributions to improve this are welcome (the code is there:
https://git.launchpad.net/~chromium-team/chromium-browser/+git/snap-
from-source/tree/launcher/chromium.laun
Yes, that looks like the same issue indeed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887793
Title:
[snap] chromium unable to launch
To manage notifications about this bug go to:
https://bugs.
> That's still incorrect.
How so?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887804
Title:
chromium-browser does not follow XDG base directory specification
To manage notifications about this
See my comment on the upstream bug report:
https://bugs.chromium.org/p/chromium/issues/detail?id=1106509#c21
I'm unable to reproduce the crash locally, unfortunately. Let's keep
this bug open, and continue the conversation on the upstream bug report,
which has more useful data and input from upstr
Thanks for the upstream bug, I'll be following it closely.
Regarding the other half of the problem (XDG base directory
specification compliance), bug #1575053 does say this in its
description:
Therefore snap packages should base the value of SNAP_USER_DATA on
the value of XDG_DATA_HOME (or it
>From the contents of DpkgTerminalLog.txt, it looks like you interrupted the
>installation.
The chromium-browser package is now a transitional package that installs the
chromium snap, which might take some time depending on your internet connection
and on the snap store CDN.
Since the snap is d
Thanks for the feedback Steven.
I'm tentatively marking the bug fixed. Feel free to re-open it if the issue
happens again.
** Changed in: chromium-browser (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Just tested in a fully up-to-date Kubuntu 20.04 VM (amd64), and I cannot
observe the problem. Printing an e-mail does pop up the print dialog in
front of the thunderbird window.
Can you share the exact steps you're taking to reproduce the problem?
Can you maybe attach a screencast demonstrating it
This looks like an intermittent failure. Relevant log from
DpkgTerminalLog.txt:
==> Installing the chromium snap
error: cannot perform the following tasks:
- Download snap "chromium" (1165) from channel "stable" (unexpected EOF)
Can you please try to reinstall and let us know how it goes:
@mpaq: sorry for the lack of feedback when you originally reported the
problem. Are you still seeing it with the latest thunderbird update on a
supported release of Ubuntu?
** Changed in: thunderbird (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are
*** This bug is a duplicate of bug 1875841 ***
https://bugs.launchpad.net/bugs/1875841
This looks like an intermittent problem, whereby the chromium snap was
already being installed. Can you try reinstalling chromium-browser?
sudo apt install --reinstall chromium-browser
and share the ou
Sorry for the lack of feedback Alexey.
I have just tested with my Yubikey 4, using
https://demo.yubico.com/playground, and U2F appears to work as expected.
Are you still seeing the problem with the latest chromium snap?
--
You received this bug notification because you are a member of Ubuntu
Bu
** Summary changed:
- Upgrading from 18.04 to 20.04 will keep the 18.04 chromium-browser due to a
higher version than the transitional deb in 20.04
+ [SRU] Upgrading from 18.04 to 20.04 will keep the 18.04 chromium-browser due
to a higher version than the transitional deb in 20.04
--
You recei
to the deb package, they are being tracked at
https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bugs?field.tag=snap. Auto-upgrading users from the deb to the
snap is the desired behaviour though.
** Affects: chromium-browser (Ubuntu)
Importance: High
Assignee: Olivier Till
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
This upstream commit fixes the crash:
https://chromium.googlesource.com/chromium/src/+/5fc11d04896442c8941ca0afba364a4d641c926e
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881751
Title:
Chromium
** Tags added: snap
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888380
Title:
Give better experience of migration of deb to snap
To manage notifications about this bug go to:
https://bugs.launch
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1816497
Title:
[snap] vaapi chromium n
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881923
Title:
No icon
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` ?
-
** Changed in: thunderbird (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.net/bugs/1888157
Title:
Thunderbird 78
To manage notifications ab
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: firefox (Ubuntu)
Status: New => 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/1879742
Title:
When using Google Meet on Firefox, delay sending sound from microphon
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/181
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881923
Title:
No icons in file picker
To manage notifi
*** 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
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
** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887793
Title:
[snap] chromium unable to launch
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/18877
** 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/1873996
Title:
DevTools does not open at 84.0.4115.5
To manage no
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849162
Title:
Lightning extension
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,
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
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
(note that snapd in the edge channel does have the interface)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887795
Title:
snap "chromium" has bad plugs or slots: system-packages-doc
To manage noti
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 Ubuntu
Bugs, which i
** 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/1854091
Title:
[snap] traps on start
To manage notifications about this bug go t
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887201
1201 - 1300 of 8832 matches
Mail list logo