[Bug 1827859] Re: Cura 3.3.1 not working correctly

2019-06-01 Thread mibus
Affected me after my upgrade to 19.04 too -- looks the same as https://bugzilla.redhat.com/show_bug.cgi?id=1708956 ** Bug watch added: Red Hat Bugzilla #1708956 https://bugzilla.redhat.com/show_bug.cgi?id=1708956 -- You received this bug notification because you are a member of Ubuntu Bugs, w

[Bug 807324] Re: BIND 9.7.0 (ie., lucid) is overly strict on authoritative responses missing the "aa" flag

2011-07-15 Thread mibus
It means that a small number of domains that used to resolve perfectly fine prior to Lucid, no longer work (due to the stricter handling of the 'aa' flag). I run caching resolvers for an ISP; all the time we're on an affected version of BIND, our customers can't access specific domains. Very few sp

[Bug 807324] [NEW] BIND 9.7.0 (ie., lucid) is overly strict on authoritative responses missing the "aa" flag

2011-07-07 Thread mibus
Public bug reported: See: http://www.isc.org/community/blog/201007/compatibility-issues- bind-970-and-971 Best done by quoting: "9.6 and earlier would allow messages without the AA bit (authoritative data) set to be accepted as answers if the rest of the message appeared to be an answer." & "othe

[Bug 510587] Re: Bind/named does not initialize on boot due to missing IPv6 address

2011-06-20 Thread mibus
I have a near-identical issue. During boot, this gets logged: named[770]: could not get query source dispatcher (2001:::::xxx#0) named[770]: loading configuration: address not available named[770]: exiting (due to fatal error) Manually starting BIND fixes the issue. This is the named

[Bug 560656] Re: The mysql add-on module is out of sync with asterisk

2010-06-12 Thread mibus
I can confirm that this also worked for me: apt-get build-dep asterisk-mysql apt-get -b source asterisk-mysql dpkg -i asterisk-mysql_1.6.2.0-1_i386.deb -- The mysql add-on module is out of sync with asterisk https://bugs.launchpad.net/bugs/560656 You received this bug notification because you ar

[Bug 66239] Re: Patch to add HAL FDI info for MPMan MP-Ki 128

2006-11-07 Thread mibus
1. I think so. I didn't have one, I probably had an old fdi file? My device was also 512MB, the '128' is just from the USB ident string. 2. Mine is the same. I didn't see that option - if there is one, it would be good to add it in. (FWIW, mine won't actually work as an MP3 player any more - eith

[Bug 66239] Patch to add HAL FDI info for MPMan MP-Ki 128

2006-10-15 Thread mibus
Public bug reported: Binary package hint: hal This patch (from instructions at http://blog.pcode.nl/?p=176 ) adds detection for a 'Actions Semiconductor Co., Ltd MPMan MP-Ki 128 MP3 Player/Recorder'). [EMAIL PROTECTED]:~$ lsusb Bus 002 Device 001: ID : Bus 001 Device 002: ID 10d6:1100 Ac