Solaar does not recognise unifying receiver (046d:c52b, K400r)

[paolocent]

Hello, I've installed Solaar in RaspBMC (a XBMC distribution for raspberry pi), I am using logitech K400r keyboard and i'd like to add another device, but Solaar does not recognise the receiver. I attach terminal responses. Thanks for help!

pi@raspbmc:~$ lsusb | grep Logitech
Bus 001 Device 005: ID 046d:c52b Logitech, Inc. Unifying Receiver

pi@raspbmc:~$ dmesg | grep Logitech
usb 1-1.2: Manufacturer: Logitech
usb 1-1.3: Manufacturer: Logitech
logitech-djreceiver 0003:046D:C52B.0005: hiddev0: USB HID v1.11 Device [Logitech USB Receiver] on usb-bcm2708_usb-1.3/input2
input: Logitech USB Receiver as /devices/platform/bcm2708_usb/usb1/1-1/1-1.2/1-1.2:1.0/input/input1
input: Logitech Unifying Device. Wireless PID:4024 as /devices/platform/bcm2708_usb/usb1/1-1/1-1.3/1-1.3:1.2/0003:046D:C52B.0005/input/input0
logitech 0003:046D:C50C.0001: input: USB HID v1.10 Keyboard [Logitech USB Receiver] on usb-bcm2708_usb-1.2/input0
logitech 0003:046D:C50C.0002: fixing up Logitech keyboard report descriptor
logitech-djdevice 0003:046D:C52B.0006: input: USB HID v1.11 Keyboard [Logitech Unifying Device. Wireless PID:4024] on usb-bcm2708_usb-1.3:1
input: Logitech USB Receiver as /devices/platform/bcm2708_usb/usb1/1-1/1-1.2/1-1.2:1.1/input/input2
logitech 0003:046D:C50C.0002: input,hiddev0: USB HID v1.10 Mouse [Logitech USB Receiver] on usb-bcm2708_usb-1.2/input1
usb 1-1.2: Manufacturer: Logitech
input: Logitech USB RECEIVER as /devices/platform/bcm2708_usb/usb1/1-1/1-1.2/1-1.2:1.0/input/input3
hid-generic 0003:046D:C50E.0007: input: USB HID v1.11 Mouse [Logitech USB RECEIVER] on usb-bcm2708_usb-1.2/input0

pi@raspbmc:~$ solaar-cli show
solaar-cli: error: Logitech receiver not found

[mikken]

Gentoo here.
Adapter isn't recognized:

$ solaar-cli show
solaar-cli: error: Logitech receiver not found

$ lsusb|grep Log
Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver

$ lsmod|grep log
hid_logitech_dj 9022 0

[Lekensteyn]

@mikken Can you try ltunify? If that bails out too, it should give a helpful message. Otherwise, please run solaar with debug (-d).

[mikken]

I figured out out CONFIG_HIDRAW had to be enabled in kernel.
Now it detects the adapter and mouse, but I have other problems, I'll bother the Gentoo package maintainer first.
On of them is that the main window is "always on top", but About window is behind the main window.

[mikken]

I was told to report upstream, copy-pasting here:

1. The icon in system tray looks like a sheet of paper with a red cross.
2. The icon near the mouse name also looks like that.
3. Nothing happens when I select a device in main window and there's no way to add new devices.
   Screenshot: https://494304.bugs.gentoo.org/attachment.cgi?id=365560

There's a Python exception when I start solaar from a terminal:

Traceback (most recent call last):
  File "/usr/lib64/python3.3/site-packages/solaar/ui/window.py", line 390, in _device_selected
    _update_info_panel(device, full=True)
  File "/usr/lib64/python3.3/site-packages/solaar/ui/window.py", line 695, in _update_info_panel
    _info._icon.set_from_icon_name(icon_name, _DEVICE_ICON_SIZE)
  File "/usr/lib64/python3.3/site-packages/gi/types.py", line 113, in function
    return info.invoke(*args, **kwargs)
TypeError: Argument 1 does not allow None as a value

[Lekensteyn]

The red cross icon problem occurs when you miss a theme package, do you have the required gnome themes installed?

(your bug is reported at https://bugs.gentoo.org/show_bug.cgi?id=494304)

[mikken]

Yes, it's me who reported it.
I don't know which themes to install, tried these packages (I'm a KDE user):
x11-themes/gnome-themes-2.32.1-r1
x11-themes/gnome-themes-extras-2.22.0-r1
x11-themes/gnome-themes-standard-3.8.4

Nothing changed.

installation.md only mentions GObject Introspection bindings and I have it (called dev-python/pygobject).

[mikken]

Sorry, I forgot to actually activate the theme after installing it. Now everything is fixed (icons, exceptions, selecting a device).

[Darkmagister]

hi i've a debian testing/sid with kernel 3.16.2 i've added the CONFIG_HIDRAW to it but
solaar-cli show
solaar-cli: error: Logitech receiver not found
but i have it connected:
Bus 002 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver

and i have the module for the receiver:
lsmod|grep log
hid_logitech_dj 9444 0

any idea? or news?
thanks

[Lekensteyn]

@Darkmagister Do the /dev/hidraw* devices exist (where * is a number)? Have you installed udev rules that grant you read/write access to them?

[Darkmagister]

ls /dev/hidraw
hidraw0 hidraw1 hidraw2

yes there are

no i haven't installed any rels for udev, but just for info, i've tried launching
sudo solaar-cli show
solaar-cli: error: Logitech receiver not found

so as root not work, i don't think it's a permission problem, but maybe i'm wrong

[Lekensteyn]

Please post the output of:
ls -l /dev/hidraw* /sys/bus/hid/drivers/logitech-dj*/*:*{/hidraw/hidraw*,}

Have you tried ltunify too?

[Darkmagister]

ls -l /dev/hidraw* /sys/bus/hid/drivers/logitech-dj_/_:_{/hidraw/hidraw_,}
ls: impossibile accedere a /sys/bus/hid/drivers/logitech-dj_/_:_/hidraw/hidraw_: File o directory non esistente
ls: impossibile accedere a /sys/bus/hid/drivers/logitech-dj_/_:*: File o directory non esistente
crw------- 1 root root 252, 0 set 15 10:57 /dev/hidraw0
crw------- 1 root root 252, 1 set 15 10:57 /dev/hidraw1
crw------- 1 root root 252, 2 set 15 10:57 /dev/hidraw2

the 2 line with the error are in italian and they just say for that 2 cases file or directory not found
and no, i haven't tried ltunify i don't know what it is, i go and try to find it

EDIT: i've found ltunify, compiled it but
./ltunify list
No Logitech Unifying Receiver device found

so no, it doesn't work

[Lekensteyn]

Who is responsible for those hidraw nodes? Could you run ls -ld /sys/class/hidraw/*/device/driver?

Where exactly did you get your kernel from? https://packages.debian.org/sid/linux-image-3.16-1-amd64?

[Darkmagister]

ls -ld /sys/class/hidraw/*/device/driver
lrwxrwxrwx 1 root root 0 set 18 15:29 /sys/class/hidraw/hidraw0/device/driver -> ../../../../../../../../bus/hid/drivers/hid-generic
lrwxrwxrwx 1 root root 0 set 18 15:29 /sys/class/hidraw/hidraw1/device/driver -> ../../../../../../../../bus/hid/drivers/hid-generic
lrwxrwxrwx 1 root root 0 set 18 15:29 /sys/class/hidraw/hidraw2/device/driver -> ../../../../../../../../bus/hid/drivers/hid-generic

I've also tried to run solaar-cli show with sudo... but got the same result.

The kernel is a vanilla one from kernel.org compiled by me.

[Lekensteyn]

Double-check that your config has CONFIG_HID_LOGITECH_DJ and CONFIG_USB_HID enabled.

[Darkmagister]

cat .config | grep CONFIG_HID_LOGITECH_DJ
CONFIG_HID_LOGITECH_DJ=m
cat .config | grep CONFIG_USB_HID
CONFIG_USB_HID=m
CONFIG_USB_HIDDEV=y

[Lekensteyn]

Do you have a /proc/config.gz that contains the same strings? Have you actually installed the modules in /lib/modules/ using make modules_install? Does lsmod show hid_logitech_dj? What if you remove/insert the receiver? Please provide a (short) dmesg from that case.

[darlanalves]

Just stumble upon this issue and I just changed the line 695 of solaar/ui/window.py into this:

if icon_name is not None:
                _info._icon.set_from_icon_name(icon_name, _DEVICE_ICON_SIZE)

... and the program ran just fine.

[ShyPixie]

I have same problem here.

[jpeter01]

...same problem:

user1@linux-home_pc:~/Solaar/Solaar-0.9.2/bin> ./solaar -d
22:41:28,497 INFO [MainThread] root: language hu_HU (UTF-8), translations path None
22:41:28,502 INFO [MainThread] solaar.ui: application /io/github/pwr/solaar, registered True
22:41:28,573 INFO [MainThread] solaar.ui.tray: using StatusIcon
22:41:28,573 INFO [MainThread] solaar.ui.notify: starting desktop notifications
22:41:28,636 INFO [MainThread] solaar.upower: connected to system dbus, watching for suspend/resume events
22:41:28,637 INFO [MainThread] solaar.listener: starting receiver listening threads
22:41:28,638 INFO [MainThread] solaar.listener: receiver event add DeviceInfo(path=u'/dev/hidraw6', vendor_id=u'046d', product_id=u'c52b', serial=None, release='1201', manufacturer='Logitech', product='USB Receiver', interface=2, driver=u'logitech-djreceiver')
22:41:28,642 ERROR [MainThread] logitech_receiver.receiver: open DeviceInfo(path=u'/dev/hidraw6', vendor_id=u'046d', product_id=u'c52b', serial=None, release='1201', manufacturer='Logitech', product='USB Receiver', interface=2, driver=u'logitech-djreceiver')
Traceback (most recent call last):
File "/home/user1/Solaar/Solaar-0.9.2/lib/logitech_receiver/receiver.py", line 525, in open
return Receiver(handle, device_info)
File "/home/user1/Solaar/Solaar-0.9.2/lib/logitech_receiver/receiver.py", line 340, in init
assert serial_reply
AssertionError
Exception AttributeError: "'Receiver' object has no attribute '_devices'" in ignored
22:41:28,643 WARNING [MainThread] solaar.listener: failed to open DeviceInfo(path=u'/dev/hidraw6', vendor_id=u'046d', product_id=u'c52b', serial=None, release='1201', manufacturer='Logitech', product='USB Receiver', interface=2, driver=u'logitech-djreceiver')
22:46:39,798 INFO [MainThread] solaar.ui.notify: stopping desktop notifications

#

user1@linux-home_pc:~/Solaar/Solaar-master/bin> ./solaar -d show
22:54:24,019 ERROR [MainThread] logitech_receiver.receiver: open DeviceInfo(path=u'/dev/hidraw6', vendor_id=u'046d', product_id=u'c52b', serial=None, release='1201', manufacturer='Logitech', product='USB Receiver', interface=2, driver=u'logitech-djreceiver')
Traceback (most recent call last):
File "/home/user1/Solaar/Solaar-master/lib/logitech_receiver/receiver.py", line 525, in open
return Receiver(handle, device_info)
File "/home/user1/Solaar/Solaar-master/lib/logitech_receiver/receiver.py", line 340, in init
assert serial_reply
AssertionError
Exception AttributeError: "'Receiver' object has no attribute '_devices'" in ignored
solaar: error: Logitech receiver not found

#

#

Update:
The version 0.7.4 is working fine on the same system, with the same hardware:

user1@linux-home_pc:~/Solaar/Solaar-0.7.4/bin> ./solaar -v
2016-06-23 23:39:25,468 INFO [MainThread] root: starting desktop notifications
2016-06-23 23:39:25,619 INFO [MainThread] Receiver[/dev/hidraw6]: initialized
2016-06-23 23:39:25,623 INFO [MainThread] Receiver[/dev/hidraw6]: reports 1 device(s) paired
2016-06-23 23:39:25,627 INFO [ReceiverListener] Receiver[/dev/hidraw6]: new device 2016-06-23 23:39:25,629 INFO [MainThread] Receiver[/dev/hidraw6]: triggered device events
2016-06-23 23:39:59,767 INFO [MainThread] root: stopping desktop notifications

...after using 0.7.4, I tried 0.9.2 again, and now it is working properly.
Addition:
If the receiver hasn't any paired devices, 0.9.2 does not recognizes the receiver, if it has at least one paired device, it is working properly. But 0.7.4 recognizes the receiver without a paired device.

OS Information:
OS: Linux 3.16.7-35-desktop x86_64
System: openSUSE 13.2 (x86_64)
KDE: 4.14.9

Device information (lsusb):
Bus 004 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver

[jrbenito]

The logic related to recognition device type is not reliable. We already saw issues with other receivers.

@jpeter01 are you able to gather some debug information if I send modifications to you?

[jpeter01]

I have only this one receiver, but I can help to get some information if
you send the modifications.

2016-11-22 17:17 keltezéssel, Josenivaldo Benito Junior írta:

The logic related to recognition device type is not reliable. We
already saw issues with other receivers.

@jpeter01 https://github.com/jpeter01 are you able to gather some
debug information if I send modifications to you?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/pwr/Solaar/issues/137#issuecomment-262286409, or
mute the thread
https://github.com/notifications/unsubscribe-auth/ATKsemB_HTfuxELY9Ogj2QKuCH-7s4ssks5rAxWtgaJpZM4BJ90K.

[jrbenito]

@jpeter01 ,

I tested with latest master, same receiver as yours, without devices paired to it and could not reproduce any errors:

bin/solaar show
Unifying Receiver
  Device path  : /dev/hidraw2
  USB id       : 046d:c52b
  Serial       : 8989B04C
    Firmware   : 12.03.B0025
    Bootloader : 02.15
    Other      : AA.AA
  Has 0 paired device(s) out of a maximum of 6.
  Notifications: wireless, software present (0x000900)
  Device activity counters: (empty)

Also, solaar does show the receiver in the GUI although it does not show a pairing button.

Are you able to reproduce the error?

[jpeter01]

I tested it under openSUSE 13.2 and 42.2 (this is a new installed system).

the results:

openSUSE 13.2:

./solaar show
Unifying Receiver
Device path : /dev/hidraw6
USB id : 046d:c52b
Serial : 1973948D
Firmware : 12.01.B0019
Bootloader : 02.14
Has 0 paired device(s) out of a maximum of 6.
Notifications: wireless, software present (0x000900)
Device activity counters: 1=147

openSuse 42.2:

unpaired, it gives the same output.

paired:

./solaar show
Unifying Receiver
Device path : /dev/hidraw6
USB id : 046d:c52b
Serial : 1973948D
Firmware : 12.01.B0019
Bootloader : 02.14
Has 1 paired device(s) out of a maximum of 6.
Notifications: wireless, software present (0x000900)
Device activity counters: 1=228

1: Wireless Mouse M175
Codename : M175
Kind : mouse
Wireless PID : 4008
Protocol : HID++ 2.0
Polling rate : 8 ms (125Hz)
Serial number: 51C17064
Firmware: RQM 27.02.B0028
The power switch is located on the base.
Supports 13 HID++ 2.0 features:
0: ROOT {0000}
1: FEATURE SET {0001}
2: DEVICE FW VERSION {0003}
3: DEVICE NAME {0005}
4: BATTERY STATUS {1000}
5: WIRELESS DEVICE STATUS {1D4B}
6: unknown:1DF3 {1DF3} hidden
7: REPROG CONTROLS {1B00}
8: unknown:1DF0 {1DF0} hidden
9: unknown:1F03 {1F03} hidden
10: VERTICAL SCROLLING {2100}
11: HI RES SCROLLING {2120}
12: MOUSE POINTER {2200}
Has 3 reprogrammable keys:
0: LEFT CLICK => LeftClick
mse, reprogrammable
1: RIGHT CLICK => RightClick
mse, reprogrammable
2: MIDDLE BUTTON => MiddleMouseButton
mse, reprogrammable
Battery: 90%, discharging.

The GUI works under 13.2 flawlessly (without any device, and with a
paired), but it don't works under 42.2. The tray icon does nothing on
the click (maybe some missing GTK dependencies, I will check this
later). With the CLI it is working properly in every situation, but to
get the Github master branch work under 42.2, I needed to install Solaar
from the OSS repository (before it had a hidraw privilege error).

installed Solaar:

i | solaar | package | 0.9.2-6.24 | noarch |
openSUSE-Leap-42.2-Oss
i | solaar-cli | package | 0.9.2-6.24 | noarch |
openSUSE-Leap-42.2-Oss
i | solaar-doc | package | 0.9.2-6.24 | noarch |
openSUSE-Leap-42.2-Oss

2016-11-23 13:57 keltezéssel, Josenivaldo Benito Junior írta:
>

@jpeter01 https://github.com/jpeter01 ,

I tested with latest master, same receiver as yours, without devices
paired to it and could not reproduce any errors:

|bin/solaar show Unifying Receiver Device path : /dev/hidraw2 USB id :
046d:c52b Serial : 8989B04C Firmware : 12.03.B0025 Bootloader : 02.15
Other : AA.AA Has 0 paired device(s) out of a maximum of 6.
Notifications: wireless, software present (0x000900) Device activity
counters: (empty) |

Also, solaar does show the receiver in the GUI although it does not
show a pairing button.

Are you able to reproduce the error?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/pwr/Solaar/issues/137#issuecomment-262505997, or
mute the thread
https://github.com/notifications/unsubscribe-auth/ATKsetzdVqywRK3XFoLqzp8zLxH318Wbks5rBDg7gaJpZM4BJ90K.

[jrbenito]

but to get the Github master branch work under 42.2, I needed to install Solaar
from the OSS repository (before it had a hidraw privilege error).

This is somehow expected. If you uninstall the official package you uninstall the udev rules that make every person logged to the system have permission to write on the device. You can put rules back by copying it from the cloned repository or installing official package.

Thanks for the investigation.

Is there any bug yet? Regarding the claim of this bug I believe it not reproducible anymore. Agree?

[jpeter01]

Thanks for fixing it.

I agree, I tried to reproduce it, but it is gone.

2016-11-30 01:18 keltezéssel, Josenivaldo Benito Junior írta:
>

but to get the Github master branch work under 42.2, I needed to
install Solaar
from the OSS repository (before it had a hidraw privilege error).

This is somehow expected. If you uninstall the official package you
uninstall the udev rules that make every person logged to the system
have permission to write on the device. You can put rules back by
copying it from the cloned repository or installing official package.

Thanks for the investigation.

Is there any bug yet? Regarding the claim of this bug I believe it not
reproducible anymore. Agree?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/pwr/Solaar/issues/137#issuecomment-263743439, or
mute the thread
https://github.com/notifications/unsubscribe-auth/ATKsemq3NGMKIF4nj9yJ2dTD66Ww6--Kks5rDMDsgaJpZM4BJ90K.

[jrbenito]

@jpeter01

thanks!

@Lekensteyn ,

We can close this one.

[Lekensteyn]

Thanks!

[oblitum]

I have the same issue, 0.9.2 grabbed from Archlinux AUR doesn't work for me. I have a MK220 combo.

[Lekensteyn]

@oblitum try solaar-git

[garrobo51]

I am running Ubuntu Mate 16.04 on several machines, just did an update and installed on a machine when I try to run it I get the following errors:

kp4djt@VideoSwitch:~$ sudo solaar
/usr/share/solaar/lib/solaar/gtk.py:33: PyGIWarning: Gtk was imported without specifying a version first. Use gi.require_version('Gtk', '3.0') before import to ensure that the right version gets loaded.
__import__(module)
/usr/share/solaar/lib/solaar/ui/notify.py:33: PyGIWarning: Notify was imported without specifying a version first. Use gi.require_version('Notify', '0.7') before import to ensure that the right version gets loaded.
from gi.repository import Notify
/usr/share/solaar/lib/solaar/ui/tray.py:72: PyGIWarning: AppIndicator3 was imported without specifying a version first. Use gi.require_version('AppIndicator3', '0.1') before import to ensure that the right version gets loaded.
from gi.repository import AppIndicator3

(solaar:3163): Gdk-CRITICAL **: gdk_window_thaw_toplevel_updates: assertion 'window->update_and_descendants_freeze_count > 0' failed

How do I correct this?

[garrobo51]

That should be a did an update and installed Solaar and got that series of errors. All of my other machines are running just fine.

[Lekensteyn]

@garrobo51 try installing the latest solaar version from git, 0.9.2 is missing a lot of fixes

[garrobo51]

That is where I pulled it from.

On Wed, Mar 22, 2017 at 3:43 PM, Peter Wu [e-mail] wrote:

@garrobo51 https://github.com/garrobo51 try installing the latest
solaar version from git, 0.9.2 is missing a lot of fixes

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/pwr/Solaar/issues/137#issuecomment-288562717, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AZYA5Mwu1QilxZDh2zD1KxapQknsGtM1ks5roaQhgaJpZM4BJ90K
.

--

Chuck Hast -- KP4DJT --
Glass, five thousand years of history and getting better.
The only container material that the USDA gives blanket approval on.

[Lekensteyn]

@garrobo51 the error messages suggest something else since these were fixed in the git version.

[doctor64]

@garrobo51 May be you start not updated version from git by ./bin/solaar, but version installed in system by just starting solaar without path?

[oblitum]

@Lekensteyn I have the same behaviour with solaar-git.

[garrobo51]

I will check it out when I can get back to that machine. I did do the
update from
github, so not sure what happened, just know that when I try to start it I
get that
error.

On Thu, Mar 23, 2017 at 10:21 PM, Francisco Lopes [e-mail]
wrote:

@Lekensteyn https://github.com/Lekensteyn I have the same behaviour
with solaar-git.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/pwr/Solaar/issues/137#issuecomment-288936084, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AZYA5HqgWMWtcMcfWAnlmPgL05cLimshks5ro1LfgaJpZM4BJ90K
.

--

Chuck Hast -- KP4DJT --
Glass, five thousand years of history and getting better.
The only container material that the USDA gives blanket approval on.

[Lekensteyn]

@oblitum which of the warnings/errors? the thaw_toplevel one? Can you post your output?

[oblitum]

@Lekensteyn I just get "error: Logitech receiver not found". Not a hint of detection.

[Lekensteyn]

@oblitum Can you try opening a new issue and add the output of solaar --debug?

[garrobo51]

I get the same thing
Logitech receiver not found

I removed and did a new install from git-hub. again I am attaching the
errors when run from a console:

kp4djt@VideoSwitch:~$ sudo solaar
[sudo] password for kp4djt:
Sorry, try again.
[sudo] password for kp4djt:
/usr/share/solaar/lib/solaar/gtk.py:33: PyGIWarning: Gtk was imported
without specifying a version first. Use gi.require_version('Gtk', '3.0')
before import to ensure that the right version gets loaded.
__import__(module)
/usr/share/solaar/lib/solaar/ui/notify.py:33: PyGIWarning: Notify was
imported without specifying a version first. Use
gi.require_version('Notify', '0.7') before import to ensure that the right
version gets loaded.
from gi.repository import Notify
/usr/share/solaar/lib/solaar/ui/tray.py:72: PyGIWarning: AppIndicator3 was
imported without specifying a version first. Use
gi.require_version('AppIndicator3',
'0.1') before import to ensure that the right version gets loaded.
from gi.repository import AppIndicator3

(solaar:6150): Gdk-CRITICAL **: gdk_window_thaw_toplevel_updates: assertion
'window->update_and_descendants_freeze_count > 0' failed

On Fri, Mar 24, 2017 at 5:40 PM, Peter Wu [e-mail] wrote:

@oblitum https://github.com/oblitum Can you try opening a new issue and
add the output of solaar --debug?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/pwr/Solaar/issues/137#issuecomment-289174490, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AZYA5AgI-73eROxU9dwFNUAOEoDCmypHks5rpGKCgaJpZM4BJ90K
.

--

Chuck Hast -- KP4DJT --
Glass, five thousand years of history and getting better.
The only container material that the USDA gives blanket approval on.

[Justin-Maxwell]

Thanks to those keeping our meeses healthy!