The issue occurs under both xorg and wayland sessions.
Here is the journalctl output:
$ journalctl -b 1
Hint: You are currently not seeing messages from other users and the system.
Users in groups 'adm', 'systemd-journal' can see all messages.
Pass -q to turn off this notice.
-- Logs
Reproducible on desktop system (Lenovo Thinkstation S30) with Ubuntu 20.04.1
LTS with Gnome Shell 3.36.4-1ubuntu1~20.04.2.
Steps: log in, physically unplug USB keyboard, plug it again.
Keyboard switchers show the switching happens, but layout is not changing
actually.
It's also reproducible on T
** Changed in: gnome-shell (Ubuntu)
Importance: Undecided => Medium
** Changed in: gnome-shell (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchp
I didn't about that bug.
But how come that it was implemented in 18.04 and it's not implemented in 20.04?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell-extension-desktop-icons
in Ubuntu.
https://bugs.launchpad.net/bugs/19
"The desktop is not handled by nautilus anymore, that's a bug in the new
gnome-shell-extension-desktop-icons component."
What was the point of this change? Now everything has to be implemented
again and there are a bunch of new bugs in the Desktop.
--
You received this bug notification because y
I think most of us agree it was an undesirable change. It was made by
the upstream developers a couple of years ago now. The reasoning is
detailed in https://gitlab.gnome.org/GNOME/nautilus/-/issues/158
We can't just reintroduce nautilus-desktop either. The change was huge,
a long time ago (so can
Adam Niedling: That's a long story. Very briefly, about 2 years ago the
GNOME project, which develops Nautilus, decided to remove support for
desktop icons from Nautilus, controversially:
https://www.omgubuntu.co.uk/2018/01/gnome-desktop-icons-removed-3-28
Ubuntu still wants desktop icons, so
Hi, this is the link to the uploaded oops:
https://errors.ubuntu.com/oops/f9043ff6-1530-11eb-bd53-fa163ee63de6
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-
Came here over from bug https://bugs.launchpad.net/ubuntu/+source/gnome-
control-center/+bug/1870356
I have installed the -proposed updates (gnome 3.36.3) and the issue of
reconnecting to a previously paired device has been resolved, namely the
toggle switch in the gnome bluetooth section for said
It looks like the problem might have come from:
/home/ack/.local/share/gnome-shell/extensions/sound-output-device-
choo...@kgshank.net/
Is there any way to trigger it without that extension?
** Summary changed:
- Session crash when switching audio output
+ gnome-shell crashed with SEGV in ?? (l
Thanks for testing and verifying the fix!
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-bluetooth in Ubunt
Thanks for the comment and details, unsure why it does pick Ubuntu font
as an alternative to CourierStd and if that's a problem with the fonts
or configuration
Gunnar do you have any clue maybe about the issue there or an opinion
about the proposed config?
--
You received this bug notification b
Which change do you expact to be made availble? The issue there is due
to clients not handling the fact that the old unsecure protocal is
disabled by default now, that's not coming back though...
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subsc
The issue has been reported upstream also on
https://gitlab.gnome.org/GNOME/gnome-power-manager/-/issues/12
** Bug watch added: gitlab.gnome.org/GNOME/gnome-power-manager/-/issues #12
https://gitlab.gnome.org/GNOME/gnome-power-manager/-/issues/12
** Changed in: gnome-power-manager (Ubuntu)
There is also a fix being proposed by a contributor on
https://gitlab.gnome.org/GNOME/gnome-power-manager/-/merge_requests/11
** Also affects: ibam-applet via
https://gitlab.gnome.org/GNOME/gnome-power-manager/-/issues/12
Importance: Unknown
Status: Unknown
--
You received this bug
** Changed in: flameshot (Ubuntu)
Importance: Undecided => Low
** Changed in: gnome-shell-extension-appindicator (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell-extension-appindi
Thank you for your bug report, could you report it directly upstream on
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues ?
** Changed in: gnome-settings-daemon (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Desktop B
If I use the builtin settings app to change output it doesn't creash,
but it also doesn't seem to be doing anything. Output output keeps going
through BT headset even if I switch to something else.
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
--
You received this bug noti
This bug was fixed in the package accountsservice -
0.6.55-0ubuntu12~20.04.2
---
accountsservice (0.6.55-0ubuntu12~20.04.2) focal; urgency=medium
* debian/patches/0010-set-language.patch:
- Don't dismiss C.UTF-8 as an invalid locale name (LP: #1873678)
-- Gunnar Hjalmarsson
Thank you for your bug report, the title isn't really clear, is the
problem about newly connected devices? if so it does sound like
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/555
** Bug watch added: gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues #555
https://gitlab.gno
Thank you for your bug report, what Ubuntu version and desktop
environment do you use? Could you describe steps to trigger the bug and
maybe include a screenshot showing the problem?
If it's an upstream issue it would also make sense to report it on
https://gitlab.gnome.org/GNOME/evolution-data-se
Thanks for upstream it, it was not unexpected they would close it,
indeed the issue is probably in pango, still they use a feature which
isn't correctly working and it's reflecting negatively on the
application so they could have decided to revert the filter until the
api behavior is corrected...
Reported to Gnome: https://gitlab.gnome.org/GNOME/gnome-settings-
daemon/-/issues/564
** Bug watch added: gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues #564
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/564
--
You received this bug notification because you are a membe
*** This bug is a duplicate of bug 1900729 ***
https://bugs.launchpad.net/bugs/1900729
** Changed in: gnome-terminal (Ubuntu)
Importance: Undecided => Low
** This bug has been marked a duplicate of bug 1900729
gnome-terminal font settings show only italic version of ubuntu mono
--
You
** Changed in: gedit (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/1901446
Title:
Add gir1.2-tepl-5 package depedency
To manage notifi
** Package changed: nautilus (Ubuntu) => gnome-shell (Ubuntu)
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/
Upstream closed the request now seems something they are not interested
doing
** Changed in: gedit (Ubuntu)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
https://bugs.launchpad.net/bugs/194904
This bug was fixed in the package gnome-bluetooth - 3.34.3-0ubuntu1
---
gnome-bluetooth (3.34.3-0ubuntu1) focal; urgency=medium
* New upstream release (lp: #1898068):
- Work-around intermittent connection problems by disabling
discovery when connecting to devices
-- Seba
The verification of the Stable Release Update for gnome-bluetooth has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you enc
On 2020-10-26 10:33, Sebastien Bacher wrote:
> Gunnar do you have any clue maybe about the issue there or an
> opinion about the proposed config?
One thing I know is that no Ubuntu font is mentioned at all in the
default fontconfig configuration, neither on Ubuntu nor Kubuntu.
But the dconf setti
Public bug reported:
[System]
- Freshly installed Ubuntu 20.04.1 LTS with 3rd party software/drivers enabled
- pulseaudio 1:13.99.1-1ubuntu3.7
- NVIDIA graphics card (GeForce GTX 650 Ti Boost) using nvidia-driver-450
- Monitor with build-in (stereo) speakers connected via HDMI to graphics card
- E
I unfortunately don't have a smartcard device handy to test/debug/
but if I compare with RHEL which is known to be working...
Redhat has the following configuration "gdm-smarcard" which includes
"smartcard-auth", a symlink pointing to "smartcard-auth-local"
I think we should 'mimic' this (at
Oh I dunno, maybe the "Fix Released" part? You do realise there is code
out there that fixes this that hasn't hit 20.04, right? It was solved in
later 19.10, now broken in 20.04.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in
Public bug reported:
A Lenovo P53 is installed with ubuntu 18.04.5 LTS.
Graphics Intel UHD Graphics 630 (main display), nvidia quadro RTX 5000 also
installed but not used for main display.
Laptop is domain joined. When logging to the local ubuntu user, there is
no problem detected. Then, if we
** Attachment added: "auth.log"
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1901552/+attachment/5427390/+files/auth.log%20-%20bug-report
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon
Ignore the comment about the duplicate status,
https://gitlab.gnome.org/GNOME/gvfs/-/issues/506 is about a request to
implement a new protocol which is what is needed, updating the reference
so the status is correct
** Changed in: gvfs
Status: Fix Released => Unknown
** Changed in: gvfs
R
The upstream bug closing seems buggy since they pointed it as a
duplicate of https://gitlab.gnome.org/GNOME/gvfs/-/issues/506 and that
doesn't make much sense. Unsure also there was anything solved in 19.10,
it's just that the situation is confusing and comments don't always
speak about the same is
The log has error about
acvpnagent[1117]: Function: OnOpenRequestComplete File:
../../vpn/Common/IP/HttpProb
eAsync.cpp Line: 313 Invoked Function: CHttpSessionAsync::OnOpenRequestComplete
Return Code: -31588316 (0xFE1E0024
) Description: SOCKETTRANSPORT_ERROR_CONNECT_TIMEOUT
it could be the pr
The issue went away for me in 19.10 not long after I saw reports that a
fix was released. And same system, the issue came back when I upgraded
to 20.04.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
https://bugs.launc
Hello Christian, or anyone else affected,
Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.43 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
http
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-shell (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.ne
Public bug reported:
After upgrading from Ubuntu 20.04 to 20.10, evolution is unable to
display my mails.
Launching from a shell, I get this error message: "bwrap: setting up uid
map: Permission denied"
Also, double clicking on a mail shows: "Something has gone wrong when
displaying the message
Still not fixed in Groovy.
** Tags removed: disco eoan
** Tags added: groovy
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1819375
Title:
Unable to launch applications from Naut
The reporter didn't mention this was happening after resuming from
suspend, though.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1893217
Title:
[nvidia] Chrome window is corrupt -
Also notice that setting apparmor in complain mode for usr.bin.evolution
is not enough to get it working. You have to disable the profile...
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evolution in Ubuntu.
https://bugs.launchpad.ne
The upstream determined that gvfsd as a systemd user session is starting
too early in Ubuntu, before the desktop enviroment variables are set.
Specifically, KRB5CCNAME env var is missing at the time gvfsd is
started, causing this bug. See the detailed report at
ttps://gitlab.gnome.org/GNOME/gvfs/-/
I would argue that this is more a bug than a wishlist item.
Functionality is being moved from gedit into tepl (a "Text editor
product line" library). For instance, gedit_utils_str_middle_truncate()
was deprecated in gedit 3.36 and removed in 3.38[1], replaced with
tepl_utils_str_middle_truncate().
CourierStd is not defined in any of the config files at
`/etc/fonts/conf.d`, so it falls back to sans-serif, not monospace. On
my computer, the sans-serif fallback is set to Ubuntu.
In config files at `/etc/fonts/conf.d`, creating duplicate rules for
"CourierStd" each time "Courier" or "Courier Ne
** Attachment added: "Screenshot"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1901603/+attachment/5427586/+files/2020-10-26%2020-25-11.png
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center
Public bug reported:
Connection to my nextcloud account with Gnome-Online-Accounts is not possible
This happened after upgrading Ubuntu to 20.10.
It worked fine with 20.04.
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: gnome-control-center 1:3.38.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.
Right xiota, and I think adding CourierStd to 45-latin.conf is
sufficient.
I could reproduce the problem on Ubuntu 20.10, so it's not a Kubuntu
specific issue as I first suspected. Instead, just as you said, it's
because CourierStd isn't currently mentioned anywhere in the config
files.
Proposed
** Attachment removed: "ProcMaps.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1901603/+attachment/5427584/+files/ProcMaps.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubunt
Thank you for your bug report, could you perhaps report it directly
upstream on https://gitlab.gnome.org/GNOME/gnome-online-accounts/issues/
?
** Changed in: gnome-control-center (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
De
I never had this issue until I upgraded from 20.04 to 20.10... I'm still
looking for a solution
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator
in Ubuntu.
https://bugs.launchpad.net/bugs/1846944
Titl
Attached prevboot.txt as instructed. Thanks for your assistance.
** Attachment added: "Output of 'journalctl -b-1 > prevboot.txt'"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1901342/+attachment/5427638/+files/prevboot.txt
--
You received this bug notification because you are
I would like to see the time in the top bar or my notifications while
playing full screen on the primary screen from steam. Is it too much to
ask?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.laun
Public bug reported:
This problem seems to come and go. It was gone in Ubuntu 20.04 and it's
back in Ubuntu 20.10.
I have both Flameshot and Yubico Authenticator configured to launch on
login. They are supposed to put app indicator icons in the top bar. The
icons are not there even though both ap
This bug still exist, 2020 here.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to eog in Ubuntu.
https://bugs.launchpad.net/bugs/1374403
Title:
EOG - CMYK jpg colors are saturated and not correct
To manage notifications about this b
** Tags removed: gnome-17.10
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1682542
Title:
Add support for top bars on all monitors to allow for multi-monitor
support in prim
** Bug watch added: bugzilla.gnome.org/ #679609
https://bugzilla.gnome.org/show_bug.cgi?id=679609
** Changed in: mutter
Remote watch: gitlab.gnome.org/GNOME/mutter/-/issues #181 =>
bugzilla.gnome.org/ #679609
** Changed in: mutter (Ubuntu)
Status: Confirmed => Fix Committed
** Change
Yeah that's just another reason to keep this bug separate.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1893217
Title:
[nvidia] Chrome window is corrupt - has a hole in it showing
Yes, unfortunately--I disabled extensions with the main toggle at the
top of the Extensions tool, logged out and logged back in, and still see
the on-screen keyboard on my touchscreen laptop after interacting with
the touchscreen. ("Screen Keyboard" is still disabled in "Universal
Access.")
Thank
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1900196
Title:
On-screen keyboard can't be disabled on touch
** Also affects: gnome-software via
https://gitlab.gnome.org/GNOME/gnome-software/-/issues/191
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-software in Ubuntu.
https://bugs.laun
Bumped importance. I've been having to answer reports of this crash from
both Ubuntu and upstream Gnome in the past 24 hours.
** Changed in: gnome-shell (Ubuntu)
Importance: Medium => High
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscrib
OK, that's a different issue though (and requires a different bug). This
particular crash appears to be unique to the extension:
sound-output-device-choo...@kgshank.net
so you should report it to the extension author.
** Changed in: gnome-shell (Ubuntu)
Status: New => Opinion
--
You r
** Tags added: groovy
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1880405
Title:
High CPU and journal flooded with: JS ERROR: TypeError: null has no
properties
_onFocusC
Launchpad has imported 23 comments from the remote bug at
https://bugzilla.gnome.org/show_bug.cgi?id=679609.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help
*** This bug is a duplicate of bug 1880405 ***
https://bugs.launchpad.net/bugs/1880405
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1880405, so it is being marked as such. Please look
As a workaround, try selecting 'Ubuntu on Wayland' on the login screen
just before you enter your password.
** Summary changed:
- Xorg freeze on Intel Core 2 T5800
+ Xorg sessions fail to start on Intel Core 2 T5800: modeset(0): drmSetMaster
failed: Permission denied
** Also affects: gdm3 (Ubun
This looks like it might be related to bug 1872159, which can also occur
on single monitor systems in theory.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1901342
Title:
Xorg sess
You said:
> After upgrading to Groovy Gorilla, my laptop hangs on the Ubuntu
splash screen after login
Please clarify if "after login" means you have successfully entered your
password.
** Changed in: gdm3 (Ubuntu)
Status: New => Incomplete
** Changed in: mutter (Ubuntu)
Status: N
You have been subscribed to a public bug:
Displays are corrupted after upgrading to 20.04. No video players appear
to work (VLC, mplayer), crashing with "Segmentation fault".
If I boot up in recovery mode and then continue to normal bootup, the
screen appears fine and the video players work.
Pro
*** This bug is a duplicate of bug 1867668 ***
https://bugs.launchpad.net/bugs/1867668
We need to treat display corruption and crashes as separate issues. So
this bug will be about the corruption and please report new bugs for any
crashes you find.
** Summary changed:
- Displays corrupted a
This kind of looks like bug 1866194, but you also appear to have the fix
for that installed. Regardless, please try:
cd ~/.config
rm -rf pulse
and then reboot.
** Changed in: gnome-control-center (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you a
*** This bug is a duplicate of bug 1867668 ***
https://bugs.launchpad.net/bugs/1867668
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1867668, so it is being marked as such. Please look
All autopkgtests for the newly accepted systemd (237-3ubuntu10.43) for bionic
have finished running.
The following regressions have been reported in tests triggered by the package:
linux-hwe-5.4/5.4.0-52.57~18.04.1 (armhf)
lxc/3.0.3-0ubuntu1~18.04.1 (ppc64el)
openssh/1:7.6p1-4ubuntu0.3 (s390x, ar
[Expired for gnome-shell-extension-ubuntu-dock (Ubuntu) because there
has been no activity for 60 days.]
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
[Expired for gnome-shell-extension-desktop-icons (Ubuntu) because there
has been no activity for 60 days.]
** Changed in: gnome-shell-extension-desktop-icons (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https:/
You have been subscribed to a public bug:
[Regression from 20.04]
Tested using Ubuntu 20.10 on Both Xorg and Wayland.
Earlier (and expected behaviour):
On pressing Ctrl+Alt+shift+r , a screen record would start, accompanied
by an orange icon on the top bar. On pressing it again, the screen
reco
*** This bug is a duplicate of bug 1901391 ***
https://bugs.launchpad.net/bugs/1901391
** Package changed: ubuntu => gnome-shell (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpa
I've updated the description with the SRU bug template. I think this
includes all the relevant info?
** Description changed:
- I'm trying to run chromium installed via snap in Ubuntu 20.10 when
- running Ubuntu Wayland session. Unfortunately, chromium wouldn't start:
+ [Impact]
- > chromium
** Summary changed:
- screen recording not working
+ Ctrl+Alt+Shift+R screen recording not working anymore in 20.10
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1901391
Title:
*** This bug is a duplicate of bug 1901391 ***
https://bugs.launchpad.net/bugs/1901391
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1901391, so it is being marked as such. Please look
85 matches
Mail list logo