[Bug 1290084] [NEW] [To Be Filled By O.E.M. To Be Filled By O.E.M.] suspend/resume failure

2014-03-09 Thread RandomInsano
Public bug reported: Happened during boot from a USB thumb drive. I'm unsure exactly what went wrong because I haven't investigated. ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-15-generic 3.13.0-15.35 ProcVersionSignature: Ubuntu 3.13.0-15.35-generic 3.13.5

[Bug 1288476] [NEW] [Apple Inc. MacBookPro9, 1] suspend/resume failure

2014-03-05 Thread RandomInsano
Public bug reported: This wasn't a suspend/resume problem. It was during a fresh boot from a forced power off. ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-14-generic 3.13.0-14.34 ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5 Uname: Linux

[Bug 1132249] Re: squid-deb-proxy-client cannot initiate connection - 22 invalid argument

2013-05-06 Thread RandomInsano
I submitted a patch that removed fe80 addresses since Linux can't easily route through those interfaces anyway. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1132249 Title: squid-deb-proxy-client

[Bug 1132249] Re: squid-deb-proxy-client cannot initiate connection - 22 invalid argument

2013-03-30 Thread RandomInsano
I'll be honest, this feels like a bug in Squid or apt itself. It's working great with IPv6 from other hosts. Interestingly, the problem host (which is also the squid-deb-proxy server) doesn't create any entries at all in access.log, presumably because of the failed connection. I've tried from a