Sun Jul 19 12:31:25 EDT 2015

Went to bed a little late, but woke up at 7:30 AM.

Another very hot day. Staying inside.

Did a little drawing.

Working on getting my printer working.
I got it on the new wireless network, and installed through the CUPS web interface.
Applications (Gimp, Firefox) couldn't see it (although `lpstat -a` saw it, but was slow to return).
I thought it might be a firewall issue, but apps still couldn't see it after `sudo iptables -F`).
CUPS is suddenly super fucking fragile. It used to be solid.
Ah. After a considerable amount of fucking around with various inconsistent CUPS failures and weirdness, I realized it was IPv6. I had ip6tables blocking everything. Apparently, that breaks CUPS. Nice.

    $ sudo ip6tables -F
    $ sudo ip6tables --policy INPUT DROP
    $ sudo ip6tables -A INPUT -i lo -j ACCEPT
    $ sudo -s
    # ip6tables-save > /etc/iptables/rules.v6
    # exit

CUPS may have tried to use IPv6 because /etc/cups/cupsd.conf has this line:
    Listen localhost:631
...and /etc/hosts has this line:
    ::1     localhost ip6-localhost ip6-loopback
Possibly changing the CUPS config to use '127.0.0.1' instead of 'localhost' would have forced IPv6.
It sucks that this is not well document (or documented at all that I could find), it doesn't fall back to IPv4, and logs nothing useful to /var/log/cups/error_log.
"Boo" to the CUPS team.

https://bugzilla.redhat.com/show_bug.cgi?id=459610
Hmm. Maybe it's a GTK rather than CUPS bug. Not great in any case.

I suppose allowing IPv6 on lo will save me headaches down the road anyhow.