Please run the following command in a terminal to attach useful
information to this bug:
apport-collect 1898849
** Changed in: firefox (Ubuntu)
Status: New => Incomplete
** Changed in: ubuntu-mate
Status: New => Incomplete
--
You received this bug notification because you are
** 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/1899473
Title:
gpg migration is st
Thanks for the report Matthias.
Given that this hasn't happened again, I'll mark the bug incomplete to let it
auto-expire in 60 days. If the problem happens again in the meantime, please
comment here and we can look into it.
** Changed in: firefox (Ubuntu)
Status: New => Incomplete
--
Y
rd (Ubuntu)
Assignee: Olivier Tilloy (osomon) => (unassigned)
--
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/1899473
Title:
gpg migration is stuck (gpg running at 100
I can confirm what you observe. Upstream builds exhibit the same visual
aspect though, so it seems it's an upstream design decision. Would you
mind filing an upstream bug at
https://bugzilla.mozilla.org/enter_bug.cgi#h=dupes%7CThunderbird and
sharing the link to it here?
** Summary changed:
- fol
This appears to be a known upstream bug
(https://bugzilla.mozilla.org/show_bug.cgi?id=1371309), which was fixed in
thunderbird 78 indeed.
Let's keep this bug open until 78 is backported to bionic.
** Bug watch added: Mozilla Bugzilla #1371309
https://bugzilla.mozilla.org/show_bug.cgi?id=13713
Thanks for the report Gunter.
Just to make sure I understand correctly the problem: we're talking
about certificates that chromium shows at chrome://settings/certificates
?
You had some personal certificates there in Ubuntu 18.04, and after
upgrading to 20.04 they are not there any longer?
Were
(probably fresh install)
** Affects: chromium-browser (Ubuntu)
Importance: High
Assignee: Olivier Tilloy (osomon)
Status: Fix Committed
** Tags: amd64 apport-bug groovy
** Changed in: chromium-browser (Ubuntu)
Assignee: (unassigned) => Olivier Tilloy (osomon)
** Ch
Fixed with https://bazaar.launchpad.net/~chromium-team/chromium-browser
/groovy-stable/revision/1552.
** 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 ch
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
** 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
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 Desktop
P
*** 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
@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 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:
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
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 Desktop
Packages, whic
>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 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
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
> That's still incorrect.
How so?
--
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/1887804
Title:
chromium-browser does not follow XDG base directory specification
Status in
Yes, that looks like the same issue indeed.
--
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] chromium unable to launch
Status in chromium-browser package
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
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
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 Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1884759
Tit
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
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 Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/186740
** Changed in: firefox (Ubuntu)
Status: Confirmed => Invalid
--
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/1866880
Title:
Firefox Speech Synthesis Not Working in Kubuntu By De
** 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 Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1888942
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.
--
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 Deskto
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.
¹
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 Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bug
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 Desktop
Packages, which is subscribe
*** 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
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
** 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 Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/
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: Incomplete => New
--
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/1887433
Title:
Print dialog from Thunderbird appears behing thu
*** 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 Desktop
Packages, whic
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
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]
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
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 Desktop
Packages, which is subscribed to firefo
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 Desktop
Packages, which is subscribed to chro
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 (
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 Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1886414
Title:
the chromium snap takes a lo
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 Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1886414
Title:
the chromium s
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
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
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
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
: 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 Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/189
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
https://launchpad.net/ubuntu/+source/thunderbird/1:78.2.0+build1-0ubuntu1
--
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 in thunderbird packa
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
** Changed in: firefox (Ubuntu)
Status: New => Invalid
--
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/1892779
Title:
Browser will not play videos
Status in firefox package in
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
*** 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
** 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/1891649
Title:
[snap] Gnome dash window tracking is broken when using chromium snap
Status in chromium-bro
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 Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1861262
Title:
Add message/rfc822 to
** 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
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
** Bug watch added: Mozilla Bugzilla #1653191
https://bugzilla.mozilla.org/show_bug.cgi?id=1653191
** Changed in: firefox
Status: Invalid => Unknown
** Changed in: firefox
Remote watch: Mozilla Bugzilla #1656045 => Mozilla Bugzilla #1653191
--
You received this bug notification becau
Indeed, deleting the ~/snap folder isn't a reasonable use case, it will
break much more than just window tracking (for starters it will remove
your entire chromium profile, including bookmarks and navigation
history, which you most likely don't want).
That said, I can't seem to reproduce the bug.
I cannot reproduce the problem is a stock GNOME session (neither by
logging out nor by abruptly killing the firefox process). I wonder
whether this is XFCE-specific?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https
** 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 subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1866732
Title:
[snap] Una
** Changed in: chromium-browser (Ubuntu)
Status: Confirmed => In Progress
--
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/1866732
Title:
[snap] Unable to add policies
** Changed in: chromium-browser (Ubuntu)
Status: Triaged => In Progress
--
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/1714244
Title:
[snap] apparmor denials on /etc/c
The following two commits are an attempt at fixing this:
https://git.launchpad.net/~chromium-team/chromium-browser/+git/snap-from-source/commit/?id=bfe4c3bf4e082ca6329040db23bdee858bd204d2
https://git.launchpad.net/~chromium-team/chromium-browser/+git/snap-from-source/commit/?id=6c9bd6a725fc7
The following two commits are an attempt at fixing this:
https://git.launchpad.net/~chromium-team/chromium-browser/+git/snap-from-source/commit/?id=bfe4c3bf4e082ca6329040db23bdee858bd204d2
https://git.launchpad.net/~chromium-team/chromium-browser/+git/snap-from-source/commit/?id=6c9bd6a725fc7
m change:
https://phabricator.services.mozilla.com/D84623
** Affects: firefox (Ubuntu)
Importance: High
Assignee: Olivier Tilloy (osomon)
Status: Triaged
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bug
$SNAP_DATA/policies is not writable by the snap, so the import of existing
policies won't work.
This would have to be implemented in the transitional deb package's postinst
script.
What can be done is to try $SNAP_DATA/policies, and if that folder
doesn't exist fall back to /etc/chromium-browser
Note to self for testing purposes:
https://www.chromium.org/administrators/linux-quick-start
--
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/1714244
Title:
[snap] apparmor den
** Also affects: chromium-browser (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: chromium-browser (Ubuntu Focal)
Assignee: (unassigned) => Olivier Tilloy (osomon)
** Changed in: chromium-browser (Ubuntu Focal)
Importance: Undecided => High
** Chan
** Description changed:
+ As a follow-up to bug #1889106, it was decided that the best solution to
handle recurring version bumps for chromium-browser updates in stable series
was to bump the package epoch to 1.
+ See the discussion in
https://lists.ubuntu.com/archives/ubuntu-devel/2020-August/
** Changed in: chromium-browser (Ubuntu Focal)
Status: Triaged => In Progress
--
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/1892724
Title:
Bump package epoch to 1 to
Please run `apport-collect 1893101` to attach useful debugging
information to this bug, thanks.
** Changed in: thunderbird (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
h
** Changed in: thunderbird (Ubuntu)
Status: Incomplete => New
--
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/1893101
Title:
Thunderbird 78.02.0 Crashes
Status in thunderbi
*** This bug is a duplicate of bug 1893021 ***
https://bugs.launchpad.net/bugs/1893021
This is bug #1893021, which I'm working on.
Please note that flash support will end on December 31st this year. See
https://www.adobe.com/products/flashplayer/end-of-life.html for details.
** This bug has
*** This bug is a duplicate of bug 1893021 ***
https://bugs.launchpad.net/bugs/1893021
That's clearly a separate bug, would you mind filing a new report for
it, so we can investigate?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to f
The problem is with GTK function stubs being declared in the wrong
sections in widget/gtk/mozgtk/mozgtk.c. Another recent upstream change
did that too: https://phabricator.services.mozilla.com/D82804.
And this patch fixes it:
https://bazaar.launchpad.net/~mozillateam/firefox/firefox.xenial/revisio
atus: Confirmed => Fix Released
** Changed in: chromium-browser (Ubuntu)
Assignee: (unassigned) => Olivier Tilloy (osomon)
** Changed in: chromium-browser (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Desktop
Packages, which
Upstream bug report:
https://bugzilla.mozilla.org/show_bug.cgi?id=1661715
** Bug watch added: Mozilla Bugzilla #1661715
https://bugzilla.mozilla.org/show_bug.cgi?id=1661715
** Also affects: firefox via
https://bugzilla.mozilla.org/show_bug.cgi?id=1661715
Importance: Unknown
Status
> How does one apply patch?
Just wait for the update to be available in xenial-security, which
should happen later today.
--
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/1893021
Title:
Patch submitted upstream:
https://phabricator.services.mozilla.com/D88588
--
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/1893021
Title:
Flash plugin symbol lookup error with firefox 8
> Interestingly, the new Chromium window now displays a "file not found"
> error for file:///snap/chromium/1275/firstrun/snap-en.html when launched.
Oh, good catch, this is an (unrelated) regression, fixed with
https://git.launchpad.net/~chromium-team/chromium-browser/+git/snap-
from-source/commit
Ok, so the issue with the launcher is that your favourite for Chromium
is 'chromium-browser.desktop', whereas it should be
'chromium_chromium.desktop'.
If you have the chromium-browser deb package installed, running /usr/bin
/chromium-browser (just once) should translate the desktop file name. If
Thanks for following up!
** Changed in: chromium-browser (Ubuntu)
Status: Incomplete => 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/1890939
Title:
[sn
Thanks for following up!
** Changed in: firefox (Ubuntu)
Status: New => Invalid
--
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/1892373
Title:
Firefox crashes on logout
Status
*** This bug is a duplicate of bug 1893021 ***
https://bugs.launchpad.net/bugs/1893021
No need to do anything, this bug is already marked as duplicate.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.l
treloar: the update is pending publication by the security team, thanks
for your patience.
--
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/1893021
Title:
Flash plugin symbol lookup err
The patch was accepted upstream: https://hg.mozilla.org/mozilla-
central/rev/5d87a8dae5fe55360890e4ea4ed12135a8e909ed
--
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/1893021
Title:
Fla
Chrome is distributed by Google, not Ubuntu, so the crash should be
reported upstream, at https://bugs.chromium.org/p/chromium/issues/entry.
Is chromium-browser (the package distributed and maintained by Ubuntu)
similarly affected?
** Changed in: chromium-browser (Ubuntu)
Status: New => In
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/~canonical-chromium-bu
Please note that an update of chromium-browser to version 85.0.4183.83
should be available very soon in the Ubuntu repositories. I would
appreciate if you could comment on this bug when you get the update to
let me know whether chromium-browser still works. Thanks in advance!
--
You received this
Thanks for the report rew.
For testing purposes, could you download the google chrome installer from
google.com/chrome, install it and test whether it is behaving similarly? That
would be a useful data point. Thanks!
--
You received this bug notification because you are a member of Desktop
Pack
301 - 400 of 4859 matches
Mail list logo
