also, this bug should happen with 19.04 too, but so far I haven't seen
anyone file it
just for reference, the downgrade of libdrm probably helps because the
new version enabled a new feature which the new mesa supports. With old
libdrm the new DRI driver probably can't trigger the failure path.
s
radeonsi_dri.so comes from mesa, so please try with
ppa:ubuntu-x-swat/updates, which has mesa 19.0.8
which one do you have currently installed? 'apt-cache policy libgl1
-mesa-dri' should tell.. I'm assuming it to be 19.0.2
** Changed in: libdrm (Ubuntu)
Status: Confirmed => Incomplete
**
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: libdrm (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net
Public bug reported:
email plain text file will be likely cause problem. gzip the save file
could help lots of back and forth.
Proposed to gzip the file if filename ends with ".gz".
** Affects: apport (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notificatio
I just built a package that just reverts it for Bionic and Disco :
https://launchpad.net/~bryanquigley/+archive/ubuntu/1796501
Will confirm results tomorrow but so far with DNSSEC=yes:
Bionic with DVE-2018-0001 patch: Can't resolve europa.eu
Bionic with patch reverted: Can resolve europa.eu
Disc
patch attached for ubuntu/devel branch.
** Patch added: "allow-local-save-more-aggressively.patch"
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1837173/+attachment/5277979/+files/allow-local-save-more-aggressively.patch
--
You received this bug notification because you are a member
Public bug reported:
For command, apport-cli -p PKG -f --save=local-save.log, if the PKG is a
local test one, it won't save the log.
Let's skip package check if --save option is used.
** Affects: apport (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notificat
[Expired for totem (Ubuntu) because there has been no activity for 60
days.]
** Changed in: totem (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gstreamer0.10 in Ubuntu.
https://
[Expired for gstreamer0.10 (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: gstreamer0.10 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gstreamer0.10 in
I have this problem on Linux Mint 19.1, which is based on Ubuntu 18.04.1
(although admittedly I am running the alpha of Mint 19.2).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/
Public bug reported:
Greetings,
The last update of libdrm-amdgpu1 caused a bug on Kodi package, making
it to crash after loading any video or reproduce a black image.
Version: 2.4.97-1ubuntu1~18.04.12019-07-03 15:07:54 UTC
libdrm (2.4.97-1ubuntu1~18.04.1) bionic; urgency=medium
* B
** Changed in: mesa (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1836772
Title:
Xorg crash on 3d-enabled virgl (Haswell host
** Summary changed:
- /usr/bin/gnome-shell:gnome-shell:
../src/gallium/drivers/radeonsi/si_state_viewport.c:239: si_emit_guardband:
Assertion `left <= -1 && top <= -1 && right >= 1 && bottom >= 1' failed.
+ gnome-shell crashed with assertion failure
../src/gallium/drivers/radeonsi/si_state_view
** Description changed:
- I’m not exactly sure if this belongs here, libva, mesa, or upstream
- somewhere. But, it doesn’t seem to be a Kodi bug, buggy is that program
- is.
+ Buggy as Kodi is, this seems to be a problem specifically with mesa-va-
+ drivers.
Kodi has worked just fine on my sy
Sweet mother of the Muses, I just downgraded the mesa-va-drivers package
to 18.0.0~rc5-1ubuntu1 (since that’s the one from the non-updates Bionic
repository) and Kodi works again! Then, this is a problem specifically
with the mesa-va-drivers package. I’ll have to update the description
accordingly.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: polkit-qt-1 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to policykit-1 in Ubuntu.
https://bugs.lau
There was an update to Mesa over in the Ubuntu-X-Swat PPA today (by
which I mean the “Updates” one), from 19.0.2-1ubuntu1.1~18.04.1 to
19.0.8-0ubuntu0~18.04.1. …Sadly, as I discovered—after installing the
updates, then restarting and trying Kodi again—this bug is still present
and still works exact
The link is not working. Skip that. I have the following commands in case it
helps:
*-usb
description: Mass storage device
product: DataTraveler 3.0
vendor: Kingston
physical id: 1
bus info: usb@2:1
logical name: scsi0
version: 0.01
seria
This bug was fixed in the package base-files - 10.1ubuntu7.1
---
base-files (10.1ubuntu7.1) cosmic; urgency=medium
* debian/motd-news.timer: Change the timer to use an OnCalendar entry as
that is correct for oneshot services. (LP: #1829968)
-- Brian Murray Mon, 08 Jul 2019 1
** Tags removed: verification-needed-xenial
** Tags added: verification-failed-xenial
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to base-files in Ubuntu.
https://bugs.launchpad.net/bugs/1637800
Title:
add a motd script fo
Following https://help.ubuntu.com/community/CommonAccessCard
Does not work to get the smartcard reader working.
pcsc_scan returns
'Waiting for first reader'
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pcsc-lite in Ubun
The information Nick previously provided was how they got around the
issue using the Kali opensource drivers. Would you like us to follow
https://pcsclite.alioth.debian.org/ccid.html#support to get you that
information.
--
You received this bug notification because you are a member of Ubuntu
Tou
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1837081
Title:
xorg crashes on virgl with 3d enabled (Haswell on the
Does this cert indicate only Realtek is certified?
The lsusb output is:
Bus 001 Device 002: ID 0a5c:5832 Broadcom Corp.
Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass0 (Defined at Interface level)
bDeviceSubClass
I installed the version of base-files from Ubuntu 18.04's proposed
repository and after installation of the package not timer was running
for motd-news. I rebooted to see if that would active the timer and it
did not.
bdmurray@clean-xenial-amd64:~$ ls -lh /var/cache/motd-news
-rw-r--r-- 1 root ro
> I've sponsored this for disco
lol, looks like we collided :)
since our uploads are identical (I assume) it shouldn't matter which the
ubuntu-sru team approves.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to modemmanager i
To add to this the following URL suggests the support and drivers should be
bundled:
https://certification.ubuntu.com/hardware/201803-26164/
The Dell OEM image does not house the drivers, nor does the Canonical
image. Is this expected? Should there be documentation on how to get
this working wi
Tested 19.0.8 from ppa:ubuntu-x-swat/updates locally and the fix works.
Any idea when the fix will be available in the ubuntu repo for Bionic
release? I haven't found any way to install from ppa on Heroku.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packa
I have checked the gtk+3.0 SRU in bionic-proposed now and could
reproduce the bug before updating and encountered correct behavior after
the update. So I am marking this SRU as verified.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-d
I've sponsored this for disco
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to modemmanager in Ubuntu.
https://bugs.launchpad.net/bugs/1828102
Title:
Regression in ModemManager
Status in modemmanager package in Ubuntu:
Fi
Cosmic has reached EOL, today:
https://lists.ubuntu.com/archives/ubuntu-announce/2019-July/000246.html
However, I uploaded this for disco.
Note to sru reviewers, this patch was applied to bionic already in bug
1819615
** Also affects: modemmanager (Ubuntu Bionic)
Importance: Undecided
To add a bit of clarity, I can't *choose* to print in monochrome from
and of the UI. The system print dialog shows no options to select
monochrome.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.
Public bug reported:
Printer is a Samsung C430W connected over wifi and using driverless
printing. Everything is discovered and I can print in colour just fine.
In Bionic I was able to toggle in to monochrome, but in Disco I am not.
I now have to print everything in colour.
$ lpoptions -l
PageS
Jason, the message you mention has nothing to do with the bug reported
here, it is from the color management daemon and in no case prevents a
job from printing. The bug reported here is about a problem of the
GTK/GNOME print dialog not handling printer driver updates correctly. It
only happens when
** Summary changed:
- Lubuntu Eoan Daily Image fails to boot after install on KVM
+ update-initramfs -k all -c does not create initrd images anymore
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
h
There was some discussion regarding this particular bug in #ubuntu-
release on 20190620 - https://irclogs.ubuntu.com/2019/06/20/%23ubuntu-
release.html. I will not summarize the conversation here but only
capture what I understand the bug in initramfs-tools to be.
update-initramfs no longer uses w
Oh, you moved it to the initramfs-tools package maintenance group. My
apologies. I thought you closed the bug report.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1
Yes it does. I'm running an unpatched Ubuntu Studio 19.04 because when I
install updates the system crashes on next reboot. There's a serious
problem here.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubu
This issue seems to have occurred to me today (and several times
previously) - when I returned to my computer after a while (the screen
had entered power saving mode), the gnome-shell process (on XWayland)
failed.
Neither after logging in to gnome-shell / Xwayland nor after logging out
and back in
** Also affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: ubuntustudio
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bu
I am experiencing this same problem in Linux Mint 19.1. After creating a
print job, there is no response from the printer (it doesn't wake up or
anything), there is no printing, but the only message in the error log
is "CreateProfile failed:
org.freedesktop.ColorManager.AlreadyExists:profile id \'M
Added description changes from comment #5.
Please could someone with appropriate rights sponsor the uploads of the
attached debdiffs (SRUs)? Thanks.
It would be great if at least the SRU for Disco could get uploaded and
rolled out. Cosmic is very close before EOL, so it can easily happen
that the
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: apport (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net
** Description changed:
[Impact]
+ ModemManager disconnects from CDMA modem after 30 sec failing to check
+ signal status due to incorrect error handling
+
[Test case]
+
+ connect to a cdma device without an extra AT channel (Eg. Samsung
+ brightside phone) and modemmanager will terminate
https://bugzilla.redhat.com/show_bug.cgi?id=1652274 is a duplicate
** Bug watch added: Red Hat Bugzilla #1652274
https://bugzilla.redhat.com/show_bug.cgi?id=1652274
** Also affects: xorg (Fedora) via
https://bugzilla.redhat.com/show_bug.cgi?id=1652274
Importance: Unknown
Status: U
Public bug reported:
I have recently files this bug:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1836772 and decided
to test if it affects Ubuntu 19.04.
Just to remind you, this was about xorg crashing in a virtual machine
that uses virtio VGA with virgl enabled. The host is Arch Linux, t
Public bug reported:
Maintainers explains that this option should be off :
https://www.rsyslog.com/doc/master/configuration/action/rsconf1_repeatedmsgreduction.html
> This parameter models old sysklogd legacy. Note that many people, including
> the rsyslog authors, consider this to be a misfeatu
** Tags removed: rls-dd-incoming rls-ee-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1835809
Title:
AMD Ryzen 3000 series fails to boot
Status in systemd packa
Could you try if the followup SRU made a difference there?
https://bugs.launchpad.net/ubuntu/+source/openssl/1.1.1-1ubuntu2.1~18.04.3
** Tags added: regression-update
** Tags added: rls-bb-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, w
** Tags removed: rls-ee-incoming
** Tags added: rls-ee-notfixing
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1829805
Title:
Lubuntu Eoan Daily Image fails to bo
** Tags removed: rls-ee-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1834226
Title:
update-notifier doesn't respect "automatically check for updates
And the verification for Ubuntu 18.10 (cosmic) has also passed:
bdmurray@clean-cosmic-amd64:~$ apt-cache policy base-files
base-files:
Installed: 10.1ubuntu7.1
Candidate: 10.1ubuntu7.1
Version table:
*** 10.1ubuntu7.1 100
100 /var/lib/dpkg/status
10.1ubuntu7 500
500 htt
** Changed in: mesa (Ubuntu Bionic)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1836721
Title:
Black screen after updating mesa from 1
** Changed in: xfwm4 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1835622
Title:
Cannot start desktop session with compositor enabled
well, perhaps not a dupe but would be nice to know if the new upstream
bugfix version helps
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1835622
Title:
Cannot start desktop
please test ppa:ubuntu-x-swat/updates
seems to be a duplicate of bug 1836721
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1835622
Title:
Cannot start desktop session with
18th July repeated 100% CPU use for over 5 minutes. Eventually cleared.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to avahi in Ubuntu.
https://bugs.launchpad.net/bugs/1836738
Title:
avahi-daemon takes 100% cpu over many m
Dimitri,
We fixed chrony's autopkgtest issue by allowing stderr during the test.
This case is still "on" as the dhclient hooks were the ones causing
stderr to chrony's tests (fyio). I have marked LP: #1832053 as a
duplicate of this and marked affecting systemd only.
Thanks!
** No longer affects:
*** This bug is a duplicate of bug 1832050 ***
https://bugs.launchpad.net/bugs/1832050
** No longer affects: ubuntu
** No longer affects: chrony (Ubuntu)
** No longer affects: chrony (Ubuntu Eoan)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded package
Have the same issue in Ubuntu 18.04.2 LTS.
In pavucontrol or in blueman-applet:
If select A2DP sound works;
If select HSP/HFP sound/mic do not work.
bluetoothctl output:
Name: Jabra Elite 65t
** Also affects: chrony (Ubuntu)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: ubuntu
** No longer affects: Ubuntu Eoan
** Changed in: systemd (Ubuntu Eoan)
Status: New => Confirmed
** Chan
*** This bug is a duplicate of bug 1832050 ***
https://bugs.launchpad.net/bugs/1832050
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Also affects: chrony (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: Ubuntu Eoan
** Changed in:
Thanks for confirming, adjusting the bug status accordingly.
** No longer affects: twinkle (Ubuntu)
** Also affects: qtdeclarative-opensource-src (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: qtdeclarative-opensource-src (Ubuntu)
Status: New => Fix Released
*
cool, the fix is on the SRU queue now, waiting for review
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1836721
Title:
Black screen after updating mesa from 18.2 to 19.0 on
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: network-manager (Ubuntu Xenial)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://b
Exactly the same issue on 18.04. Why was this closed?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1716654
Title:
[System Product Name, Realtek ALC1220, Pink Mic, Re
I have just updated from ppa:ubuntu-x-swat/updates, now everything is
fine on i386 Ubuntu 18.04
~# apt-cache policy libgl1-mesa-glx
libgl1-mesa-glx:
Installed: 19.0.8-0ubuntu0~18.04.1
Candidate: 19.0.8-0ubuntu0~18.04.1
Version table:
*** 19.0.8-0ubuntu0~18.04.1 500
500 http://ppa.la
excellent, that version is on the SRU queue already, waiting for review
** Changed in: xorg-server (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.
It works.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1836772
Title:
Xorg crash on 3d-enabled virgl (Haswell host)
Status in mesa package in Ubuntu:
Incomplete
Status i
please test 19.0.8 from ppa:ubuntu-x-swat/updates once it has built
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1835922
Title:
missing gl* symbols in version 19.0.2
Statu
please test 19.0.8 from ppa:ubuntu-x-swat/updates once it has built
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1836721
Title:
Black screen after updating mesa from 18.2 t
please test 19.0.8 from ppa:ubuntu-x-swat/updates
** Changed in: mesa (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1836772
Title:
** Changed in: linux (Ubuntu Cosmic)
Status: New => Won't Fix
** Summary changed:
- Black screen on skylake after 18.0 => 18.2 update
+ [bionic] drm/i915: softpin broken, needs to be fixed for 32bit mesa
--
You received this bug notification because you are a member of Ubuntu
Touch seede
okay, adding the revert again.. this should've been fixed in the kernel
after 18.04.2 but that didn't happen
since we don't support 32bit installs in newer releases, bionic is the
only one that will get this
** Also affects: mesa (Ubuntu Bionic)
Importance: Undecided
Status: New
** Cha
fixed upstream in 19.0.5
** Bug watch added: freedesktop.org Bugzilla #109659
https://bugs.freedesktop.org/show_bug.cgi?id=109659
** Also affects: mesa via
https://bugs.freedesktop.org/show_bug.cgi?id=109659
Importance: Unknown
Status: Unknown
** Also affects: mesa (Ubuntu Disco)
> That's weird, do you understand why? The update was deleted so you should be
> back to initial
> situation, we had no change to the previous package build
Other package changes? Certainly systemd-resolver although we don't use
that (because of a previous VPN DNS leak problem) we use dnsmasq.
seb128, it seems that dwmw2 NEEDS this SRU, without he does not get his
environment working correctly, with SRU he gets it at least working
setting the parameters he mentioned. I asked the posters of the
regressions whether they get their situation fixed when using this SRU,
the systemd SRU and dwm
> Then the NM update was pulled, and new installations aren't working at
all, even if we don't set the DNS config as described.
That's weird, do you understand why? The update was deleted so you
should be back to initial situation, we had no change to the previous
package build
Also Till is still
This bug was fixed in the package iputils - 3:20161105-1ubuntu3
---
iputils (3:20161105-1ubuntu3) bionic; urgency=medium
* debian/patches/git_after_free.patch,
debian/patches/git_routing_ipv6.patch:
- backport fixes for ipv6 routing commands not working (lp: #1798313)
-- S
it's also weird because
/usr/share/polkit-1/actions/org.freedesktop.login1.policy has
...
auth_admin_keep
auth_admin_keep
yes
Which means the active session should be allowed
Is yo
The verification of the Stable Release Update for iputils has completed
successfully and the package has now been 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 encounter a
This bug was fixed in the package base-files - 10.1ubuntu9.1
---
base-files (10.1ubuntu9.1) disco; urgency=medium
* debian/motd-news.timer: Change the timer to use an OnCalendar entry as
that is correct for oneshot services. (LP: #1829968)
-- Brian Murray Mon, 08 Jul 2019 11
This bug was fixed in the package base-files - 10.1ubuntu2.5
---
base-files (10.1ubuntu2.5) bionic; urgency=medium
* debian/motd-news.timer: Change the timer to use an OnCalendar entry as
that is correct for oneshot services. (LP: #1829968)
-- Brian Murray Mon, 08 Jul 2019 1
The verification of the Stable Release Update for base-files has
completed successfully and the package has now been 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 encounte
It's not ignored but the bug is about a 3 years old version of Ubuntu
and it got only one report in that time with 2 affect users, that makes
it a pretty low priority issue.
Also suspend on idle does work under Unity so maybe the issue is not the
with the permission but with the action xfce is usi
Do we have any idea when this will be fixed? Most of my users used to
get away with the DNS leakage and it was "only" a security problem but
stuff actually worked. Then the NM and other updates were shipped, we
set ipv4.dns-priority=-1 and ipv4.dns-search=~. and it all worked fine.
Then the NM upda
86 matches
Mail list logo
