[Bug 746699] Re: failure trying to install from Debian 4.0 (kernel 2.6.18-5)

2021-10-28 Thread Brian Morris
I had forgotten I even filed this a decade ago. I don't really have such a system to test with anymore, and it's not clear what more recent versions of things would be worth testing with. I suspect this can just be closed. -- You received this bug notification because you are a member of Ubuntu

[Bug 1923416] [NEW] Installer crash in 20.10 in new VirtualBox VM on OS-X

2021-04-12 Thread Brian Morris
Public bug reported: Installing 20.10 in new VirtualBox VM on OS-X, zfs selected ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubiquity 20.10.13 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp

[Bug 1612517] Re: Server fails to start after upgrade because of customized config and obsolete/renamed directives

2017-08-15 Thread Brian Morris
This failure also occurs because "log_slow_queries" has become "slow_query_log", but the installer does not handle this change automagically. Like the OP's error, nothing specific to it is mentioned in the installation failure message. -- You received this bug notification because you are a

[Bug 1339607] Re: Unencrypted private keys are insecure message is vague and unhelpful

2015-04-08 Thread Brian Morris
I confirm the same behavior that Dmitri sees. I have an encrypted private key configured with its password within the Network Manager which belongs to a wifi connection. When that connection is found at boot time, I receive this warning message regardless of whether the key is encrypted, or not.

[Bug 1163513] [NEW] dbus/udev send NFS client connection out out the wrong interface

2013-04-02 Thread Brian Morris
Public bug reported: I apologize for being vague , but I am not certain which package is responsible for this bug. Both dbus and udev are the most likely candidates as both contain recent change logs that mention Interface 00 binding. Both were upgraded during the application of all waiting

[Bug 361992] Re: HostAliases ignored

2009-07-17 Thread Brian Morris
Hello, This issue has been resolved thanks to the help of Jean-Luc of the awstats team. Some changes that came in v6.5.x broke the way that we were using awstats. To make our configurations compatible with v6.5.x we had to change the following: 1) LogSeparator= became \s+ as one of our log

[Bug 361992] Re: HostAliases ignored

2009-07-13 Thread Brian Morris
Hello, I apologize for my delay but I stopped watching this after it didn't get answered for a few weeks. This is on the server edition of Ubuntu 6.06.x LTS (Dapper), but it is important to note that this issue persists in all versions of awstats from 6.54.x onward. -- HostAliases ignored

[Bug 361992] Re: HostAliases ignored

2009-07-13 Thread Brian Morris
Typo: The version in my last comment should have been 6.5.x. -- HostAliases ignored https://bugs.launchpad.net/bugs/361992 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com

[Bug 361992] [NEW] HostAliases ignored

2009-04-15 Thread Brian Morris
Public bug reported: Ubuntu 6.06.2 LTS (Dapper) Upgrading to any awstats version from 6.5-1 onward (I have tried both awstats_6.5-1ubuntu1.3_all.deb from dapper and awstats_6.6+dfsg- 1ubuntu0.1_all.deb from gutsy) breaks the HostAliases directive. Prior to this upgrade our awstats installation

[Bug 361992] Re: HostAliases ignored

2009-04-15 Thread Brian Morris
Here is the output of updating against myconf. You can see that every parsed record is counted as a new qualified record when only about 40% of the actual log lines pertain to the HostAliases in the coinfiguration. # /usr/lib/cgi-bin/awstats.pl -update -config=myconf Create/Update database for