> should it fail how can I get the log when my system completely locks
up and dies?
My understanding of the bug is that it occurs when the NVIDIA driver
tries to bring up the DisplayPort link on certain DisplayPort monitors.
You should be able to drive the system in text mode with a failing
Hello, NVIDIA employee here.
Can those who are still experiencing problems please provide the
following information?
* NVIDIA driver version installed
* NVIDIA GPU model
* Exact model of affected monitor
An nvidia-bug-report.log will capture the driver version and GPU model,
along with some
Tested in a clean focal chroot. The dependency resolution works as
expected, allowing the package to be installed without pulling in all of
GNOME, but only if the "universe" repository component is enabled. If I
have only "main" enabled, then dependency resolution fails with the
following:
# apt
Public bug reported:
In Bionic, screen-resolution-extra has a dependency on policykit-1-gnome
| polkit-1-auth-agent. Focal replaces this with a dependency on gnome-
shell | policykit-1-gnome | polkit-1-auth-agent. As a result, when
install screen-resolution-extra (e.g. as a dependency of nvidia-
The workaround suggests that there's an interaction between the NVIDIA
driver and another kernel module at play here. Presumably, adding the
NVIDIA kernel modules to the initrd causes them to be loaded before the
other module. Maybe video.ko, which registers its own brightness
handler?
The
Can somebody with an affected system please try with one of the recently
released 460.xx drivers? There were some brightness regressions that
were resolved in the 460 series that may be related.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
In newer Ubuntu 18.04 HWE kernels, it is possible for GPU HDA
controllers to be dynamically runtime-suspended if the HDA's
power/control mode is set to "auto". However, pm-utils explicitly sets
this to "on" when resuming, which prevents runtime power management of
these
Is there any plan to add this functionality to the 18.04 HWE stack?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1839555
Title:
X server backports for PRIME render offloading
To manage
Sorry, I didn't notice that this bug had expired, or that it was waiting
on log files. I don't have the system that I originally reproduced the
issue on set up any more, but it should be easily reproducible.
I'll set up another system to reproduce and generate the requested log
files, but in the
Public bug reported:
Configuring PRIME render offloading requires changes to the X server
which have been accepted upstream but are not yet present in any
release. These changes do not break the driver ABI and should be safe to
backport to existing X servers shipped in distributions like Ubuntu.
Would it be possible to change the "intel" profile to no longer alias
the nvidia.ko and nvidia-uvm.ko modules to "off"? The blacklisting can
remain, and would prevent the modules from being loaded automatically in
response to the device being present, but wouldn't prevent them from
being
amd64 counts as x86 for the purposes of supported architectures in
Linux, and x86 does have the C version of recordmcount. Comment #3
includes a list of architectures that lack the C version of
recordmcount. Of those architectures, ppc64le is the only one that is
supported by the NVIDIA driver
** Patch added: "Patch generated from the upstream commit that fixes this issue"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831945/+attachment/5269215/+files/hda.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
When using HDMI or Displayport audio, the EDID-like Data (ELD) fails to
update properly when hotplugging or hot-unplugging displays. This in
turn prevents tools like the GNOME sound settings control panel from
accurately presenting the system's current audio capabilities.
Public bug reported:
The old-style NVIDIA package (used prior to Bionic) installs an X
configuration snippet to:
/usr/share/X11/xorg.conf.d/50-nvidia-drm-outputclass.conf/nvidia-drm-
outputclass.conf
The purpose of this configuration snippet is to configure DRM
OutputClass-based driver matching
Yes, that's the one. The kbuild maintainer modified the commit message
to add a maintainer Signed-off-by line.
I would say that any kernel versions that are shipped for actively
maintained versions of Ubuntu that support hardware platforms that don't
use the C version of recordmcount:
for file
Public bug reported:
When LANG is set to a non-English language with the relevant language
pack installed, Kbuild's recordmcount.pl script fails to function
correctly when building out-of-tree kernel modules on architectures that
do not use the C version of recordmcount (e.g. ppc64le). This can
I'm confused about the above message. This bug never affected the kernel
in Bionic AFAIK. Or is this referring to the HWE kernel for Bionic from
Cosmic for 18.04.2? In that case, why isn't this change already included
in the HWE kernel as it was imported from Cosmic, rather than needing to
be
Yes, I do see the expected behavior now with signed modules, both when
the signing key is enrolled in the MOK (module loads, no verification
error) and when it is not enrolled in the MOK (module fails to load due
to verification error.) However, the behavior is not quite what I expect
when a
Just to confirm, this is with the 4.18.0-12-generic x86_64 kernel from
cosmic-proposed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798863
Title:
18.10 kernel does not appear to validate kernel
Cool, glad you were able to track down the problems. Sorry if my report
that module signature verification was disabled and couldn't be re-
enabled was misleading. That's what I thought was happening; I didn't
think to imagine that the enforcement of the "valid signature required"
policy wasn't
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1798863/+attachment/5204919/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798863
Title:
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1798863/+attachment/5204913/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798863
Title:
apport information
** Tags added: apport-collected cosmic
** Description changed:
On a system with Ubuntu 18.10, with secure boot enabled, and a key
enrolled in the MOK database, I am observing the following peculiar
behaviors:
* Signature verification appears to be disabled, and
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1798863/+attachment/5204914/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1798863/+attachment/5204910/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1798863/+attachment/5204917/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798863
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1798863/+attachment/5204920/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798863
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1798863/+attachment/5204916/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798863
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1798863/+attachment/5204911/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798863
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1798863/+attachment/5204915/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1798863/+attachment/5204918/+files/RfKill.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798863
Title:
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1798863/+attachment/5204912/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798863
Title:
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1798863/+attachment/5204909/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798863
Title:
18.10
Public bug reported:
On a system with Ubuntu 18.10, with secure boot enabled, and a key
enrolled in the MOK database, I am observing the following peculiar
behaviors:
* Signature verification appears to be disabled, and cannot be enabled again.
It appeared to be enabled previously, as loading
Public bug reported:
The packages install the driver libraries, including symlinks intended
for the dynamic linker, to versioned directories (e.g.
/usr/lib/nvidia-390). The dynamic loader is configured to search these
directories via /etc/ld.so.conf.d; however, this configuration doesn't
affect
It's unlikely to be due a change in the NVIDIA driver, since we (NVIDIA)
have not yet identified a root cause for the touchpad freeze.
As this problem is highly sporadic, and can take several hours in some
cases to reproduce, if it reproduces at all, we should probably wait for
more confirmations
@Alberto:
Here's a patch that adds calls into pm_vt_switch_{required,unregister}()
to the NVIDIA driver. It resolves the corruption issue on my test
system. This change will be included with the next release of the 331
series drivers.
** Patch added: NVIDIA driver patch for
Moving this bug from nvidia-prime to nvidia-graphics-drivers-331, since
the fix goes in the NVIDIA driver, and not nvidia-prime.
FWIW, the attached patch has been formatted for use with the NVIDIA .run
installer's --apply-patch option, but it should be usable for DKMS,
since DKMS uses patchlevel
It looks like this is a consequence of recent changes in the kernel that
allow the system to optionally skip VT switches on suspend and resume:
24576d2 drm/i915: enable VT switchless resume v3
3cf2667 fb: add support for drivers not needing VT switch at suspend/resume
time
f43f627 PM: make VT
@Alberto: that's essentially the change which I tested successfully on a
laptop I have which reproduces the issue, but some of my colleagues have
suggested calling into pm_vt_switch_*() elsewhere in the driver. I would
prefer if you could wait for an official patch and/or driver update,
which
Public bug reported:
The BusID string created by prime-xconfig could be incorrect in any of
the following cases:
a) Any numeric component of the bus ID is greater than 9: prime-xconfig will
write a hexadecimal value, but X will parse it as decimal.
b) The system has more than one PCI domain:
Note that X can parse hexadecimal values in the BusID string if they're
prepended with 0x, since xf86ParsePciBusString() uses atoi(3) to parse
each field; however, the comment at the top of xf86ParsePciBusString()
explicitly states that a decimal value is expected.
--
You received this bug
Hi Alberto,
One of our GL driver engineers looked into this a bit, and it actually
seems to be a linker regression that is exposed when linking an
application against the Mesa libGL, and then running it against the
NVIDIA one. He is gathering some more information before filing a bug,
but in the
Hi Alberto,
One of our GL driver engineers looked into this a bit, and it actually
seems to be a linker regression that is exposed when linking an
application against the Mesa libGL, and then running it against the
NVIDIA one. He is gathering some more information before filing a bug,
but in the
Apologies for the duplicated post: I neglected to include the attachment
the first time around, and when I attempted to add it later, it resulted
in the text of my previous update being posted again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
The problem described in this bug is due to a confirmed regression in
the NVIDIA driver. If you are seeing a similar symptom on Intel, that
should probably be tracked in a separate bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Not to my knowledge: that changelog entry refers to adding an additional
interface via the NV-CONTROL API to the existing backlight
functionality. The problem is that the existing backlight functionality
is now broken on some laptops, so it doesn't make a difference whether
it's exposed through a
Sorry, I don't have any ideas. I don't think we've seen anything like
this either; we'd probably need a machine that uses the same touchpad or
touchpad driver.
If the Nouveau driver also supports the RandR 1.4 provider source
capability, it might be an interesting experiment to configure PRIME
Sorry, at the moment we don't have an ETA for a fix. It's not likely to
be fixed in the immediate future. I've added a note to the bug report on
the NVIDIA bug tracker as a reminder to update this Launchpad thread
when we have a fix in hand.
The only workaround I'm currently aware of is to use an
It's not explicitly stated anywhere in this bug report, but due to the
bug being assigned to nvidia-prime and the attached bug reports
apparently coming from systems with PRIME configured, can it be assumed
that this bug happens specifically on systems with RandR 1.4 display
offloading configured?
It looks like we're tracking a similar bug report about broken
brightness controls on HP EliteBook 8560w in the 319 and later drivers
in the NVIDIA internal bug tracker. That bug tracker is not visible to
the public, but in case you want to check with NVIDIA support on the
status of the bug, the
Public bug reported:
This bug is well described on the freedesktop.org bugzilla:
https://bugs.freedesktop.org/show_bug.cgi?id=54654
In short, the cursor can't move beyond one screen when a server is
running multiple X screens. The bug has been fixed upstream; the fix
should be applied to all
Hi Steve,
While the NVIDIA driver often happens to work with consoles other than
the standard VGA text mode console without any user-visible symptoms,
any console configuration besides VGA text mode is not supported by the
driver, and use of any alternative consoles is directly linked, in many
Public bug reported:
The NVIDIA driver does not interact well with consoles other than plain
VGA text consoles, such as vesafb. NVIDIA recommends that users run VGA
text consoles in conjunction with the NVIDIA driver.
Many distributions, such as Ubuntu, enable a framebuffer console by
default.
The current release 304 drivers should work fine with 1.13. I'll check
this out on my Quantal machine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1037896
Title:
Starting Firefox kills xserver
There was a change in the layout of an X server data structure, which
caused the NVIDIA OpenGL driver to call into invalid function pointers:
http://lists.x.org/archives/xorg-devel/2012-August/033307.html
This should be fixed in the next 304 release after 304.37. Thanks for
reporting this.
--
@tye3ow: In that case, you are probably experiencing a different issue,
as we have identified a specific problem that was introduced between the
290 and 295 series of drivers that we believe is responsible for many of
the reports here.
The next 304 release (the fix is not in 304.32) will contain
@joelm, thanks for providing that.
You provided three backtraces. You included a snippet from dmesg with
backtrace 1: can you confirm that you didn't see the same info from the
kernel when you captured backtraces 2 and 3?
Also, when did you generate that nvidia-bug-report.log file?
--
You
At an above linked forum thread, they were able to reproduce this bug
on a quadro fx4600. They are hoping to fix it this month, but I'd guess
it will be next month. The thread is now password protected.
Sorry if there is any confusion, but the issue I believe you are
referring to, which we do
@natew: NVIDIA does not have access to the nvnews.net forum at this
time, either. I was not directly involved in the attempts to reproduce
the issue described above, but as reported by the person who did
reproduce this issue, we did try several systems with chips that are
similar to the GeForce
@natew: I gave some basic guidance on how to get debug symbols for X
installed, and how to determine nvidia_drv.so's DSO load base in comment
#144 here: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-
drivers/+bug/973096/comments/144
Specifically, see (3a) and (3c). Let me know if you
Hi everybody,
Like I said earlier, I've personally been using Precise with Unity on
one of my main test machines since the alpha stage, and haven't seen any
X crashes that weren't due to bugs that have since been fixed, and I
certainly haven't seen random, frequent X crashes like what seems to be
Hi Alberto,
There seem to be a lot of reports here, and it's hard to tell whether
they're all related. We are currently investigating reports of a
regression with very recent versions of Flash where the X server can
crash when playing videos, which it sounds like many of the users here
are
Are the other affected users also running GeForce 6200 or similar
boards?
As an experiment, try reverting the security patch here:
ftp://download.nvidia.com/XFree86/patches/security/CVE-2012-0946/
You should be able to do this without reinstalling the whole driver by
manually reverting the patch
Effenberg, I think you're experiencing a different set of problems than
the original reporters, who have a regression in 295.40 compared to
295.33.
What's your display configuration? If you have multiple large displays,
or multiple displays with different resolutions, it is sometimes
necessary to
Okay, will they need any information from NVIDIA to populate the
database entry, or will they do their own research?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/959842
Title:
root escalation via
If it's true that similar issues show up in Nouveau, and on AMD boards
(radeon? fglrx?), then it probably makes the most sense to track down
the regression better first. There's still a chance that there could be
bugs in all of the affected drivers that are causing this, but it would
be great if
The 295 driver package will contain the control panel fix. However, the
original problem reported in this bug does not sound like the control
panel bug. It's not clear to me if the other comments on this bug are
actually reporting the same issue reported in this bug, or the control
panel issue as
I don't think it's related. I don't see any reports of X crashing here,
just inability to use external displays. Furthermore, the bug referenced
in that changelog entry was introduced in the 295 timeframe and this bug
is reported in 280.
The issue described here also doesn't seem to exactly match
What driver version is this reported on?
There is a known bug in the driver that resulted in momentary hangs
during modeswitch for some FBO applications. It was fixed in the 295
timeframe. The first public driver with the fix was the 295.17 beta.
--
You received this bug notification because
The next 295 driver version will contain a fix for this issue.
** Changed in: nvidia-graphics-drivers (Ubuntu)
Status: Triaged = Fix Committed
** Changed in: nvidia-graphics-drivers (Ubuntu)
Assignee: Alberto Milone (albertomilone) = Daniel Dadap (ddadap)
--
You received this bug
Hello all,
Thanks for reporting this bug. Since it seems to be quite active on
launchpad and users are writing in to linux-bugs about it, I just wanted
to mention that NVIDIA is aware of the issue. We've been tracking it for
a while under NVIDIA internal bug number 822418. It does appear to be
** Changed in: tightvnc (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/111039
Title:
xtightvncviewer scrolling doesn't work
--
ubuntu-bugs mailing list
Actually, this isn't a bug. The old-skool Xaw scrollbars need to be
right-clicked to scroll left or up.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/111039
Title:
xtightvncviewer scrolling doesn't
Just set the DISPLAY variable to your third display's X screen.
Example, if your third display is screen :0.1:
DISPLAY=:0.1 xterm
--
Launching QT apps such as SpeedCrunch, keepassX, Lucky Backup, Pencil,
Stellarium, skype, VLC crashes Xserver
https://bugs.launchpad.net/bugs/650539
You
TwinView is only supported when two displays are used on one GPU.
--
Launching QT apps such as SpeedCrunch, keepassX, Lucky Backup, Pencil,
Stellarium, skype, VLC crashes Xserver
https://bugs.launchpad.net/bugs/650539
You received this bug notification because you are a member of Kubuntu
Bugs,
The 260.19.04 driver doesn't have this fix yet. It will be a later
version that does.
--
nvidia 256.53 xorg-server 1.9.0 performance regression with antialiased text
https://bugs.launchpad.net/bugs/629910
You received this bug notification because you are a member of Ubuntu
Bugs, which is
The 256.xx driver should work fine with kernel 2.6.35. I just upgraded
my Maverick test machine to 2.6.35-14 and I'm not having any problems
with the NVIDIA driver.
The logs attached to this bug all appear to have been generated with
2.6.35-11. I'm assuming that the system was rebooted into the
The NVIDIA driver builds its list of available modes from several
sources. The most important of these are the display's EDID, and the X
server's list of VESA standard modes.
The ModeValidation NoXServerModes option removes the X server
provided modes from this pool. It seems that in this case,
Public bug reported:
Binary package hint: xorg
Steps to reproduce:
1. stop gdm
2. Run startx from a VT
3. Once the desktop is up, open a few windows.
4. Switch back to the VT that you ran startx on
5. Hit enter
6. Switch back to the VT that X is running on
With the nouveau and vesa drivers,
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/48237562/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/48237563/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/48237564/Dependencies.txt
**
The recent NVIDIA driver release does not fix this problem. This is a
problem with the X server.
The problem exists upstream and affects a number of other Linux
distributions as well, so it's not specific to Ubuntu.
--
Mouse movement corrupted with Xinerama enabled
The recent NVIDIA driver release does not fix this problem. This is a
problem with the X server.
The problem exists upstream and affects a number of other Linux
distributions as well, so it's not specific to Ubuntu.
--
Mouse movement corrupted with Xinerama enabled
Thanks for all the reports. We have tracked this down to a problem with
the kernel's VGA arbiter trying to move VGA ownership to a GPU that
hasn't POSTed. We're working with the developers of the VGA arbiter to
get this fixed in the kernel.
In the meantime, we have a patch which works around the
Thanks for all the reports. We have tracked this down to a problem with
the kernel's VGA arbiter trying to move VGA ownership to a GPU that
hasn't POSTed. We're working with the developers of the VGA arbiter to
get this fixed in the kernel.
In the meantime, we have a patch which works around the
This sounds like it might the same as this:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=563624
Could the affected people please try increasing the GDM timeout
(GdmXserverTimeout in /usr/share/gdm/defaults.conf) to see if it
alleviates the issue?
** Bug watch added: Debian Bug tracker
Hmm, I'll fire up my Ubuntu Lucid system and see if the setting for GDM
timeout has moved somewhere else. It might be in another file, or in
gconf, or who knows where...
--
nvidia driver sometime does not load at boot
https://bugs.launchpad.net/bugs/532436
You received this bug notification
Hi Mike, you're right; I can't seem to figure out where the GDM
configuration went...
Try creating a simple custom.conf file at /usr/share/gdm/custom.conf
containing the following two lines:
[daemon]
GdmXserverTimeout=60
If this doesn't work, it will tell us that either:
1) Your problem is not
This is a known bug in Xorg 1.7.
https://bugs.freedesktop.org/show_bug.cgi?id=24986
We did investigate this about a month ago, until we discovered that it
was a bug in X. At the time, it did reproduce in Debian unstable, though
the bug report here suggests that it currently does not. The
I haven't seen this happen during any of my recent testing with Lucid.
If it is a timing issue, it might be easiest to pursue a repro on the
same hardware. I'll try to get access to one of these notebook systems
(Dell Studio XPS 1340) for testing.
In the meantime, if anybody else is experiencing
Is the nvidia kernel module being rebuilt after the upgrade? It's
expected not to work after upgrading the kernel, if it's not rebuilt for
the new kernel.
--
[Test xpr-008] Lucid upgrade broke when upgrading from manually installed
nvidia proprietary drivers
This no longer happens for me after an aptitude update; aptitude upgrade
a few days ago. Please close this bug.
Thanks,
Daniel
--
System freeze when logging into GNOME on fresh Lucid install
https://bugs.launchpad.net/bugs/519538
You received this bug notification because you are a member of
Public bug reported:
This is happening on Toshiba Tecra M5 and Tecra M10 laptops.
Started with a fresh install of Karmic, which works normally. Did an
upgrade to Lucid. Upon booting into Lucid, the gdm login screen
displays. On the M5, this screen has scrambled video, which clears up if
I switch
94 matches
Mail list logo
