similar to: Icecast 2.4 beta4 release

Hi, On 01/25/2014 11:47 PM, v_2e at ukr.net wrote: > I have tested the newly released IceCast 2.4beta4 and again found a > noticeable memory leak in it. Can you please run Icecast under Valgrind? I'm personally using: valgrind -v --time-stamp=yes --leak-check=full --show-reachable=yes icecast -c /etc/icecast2/icecast.xml With our experiments so far we were not able to see such

This is to announce the release of Icecast 2.4 beta5 (aka 2.3.99.5). We're looking forward to testing and feedback. As this is a beta release please discuss it on the icecast-dev mailing list. (Please do NOT cross-post to both lists, do NOT reply to the icecast mailing list, PLEASE reply to icecast-dev at xiph.org only). * Updated web interface to be fully XHTML compliant and mobile

This is to announce the release of Icecast 2.4 beta5 (aka 2.3.99.5). We're looking forward to testing and feedback. As this is a beta release please discuss it on the icecast-dev mailing list. (Please do NOT cross-post to both lists, do NOT reply to the icecast mailing list, PLEASE reply to icecast-dev at xiph.org only). * Updated web interface to be fully XHTML compliant and mobile

Hello! I started the IceCast using Valgrind, just like you suggested before. It started with ~37MB of residend memory used by the Valgrind process and then started to grow steadily after the IceS stream start. I waited till the memory used by Valgrind reached ~79MB and stopped the IceS stream. The Valgrind memory usage also stopped to grow. I waited for several hours and checked the memory

https://bugs.freedesktop.org/show_bug.cgi?id=60951 Priority: medium Bug ID: 60951 Assignee: nouveau at lists.freedesktop.org Summary: xf86-video-nouveau 1.0.6-1: Mouse cursor intermittently disappears, requiring reboot to resolve. QA Contact: xorg-team at lists.x.org Severity: major

http://bugs.freedesktop.org/show_bug.cgi?id=15758 Summary: Invisible mouse pointer on NV4E (C51) Product: xorg Version: unspecified Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org

https://bugs.freedesktop.org/show_bug.cgi?id=96460 Bug ID: 96460 Summary: NV43 [GeForce 6600 GT] shows many artifacts on a screen Product: Mesa Version: 11.2 Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: blocker Priority: medium Component:

Hi all, I try to join samba3 to NT4 domain: My smb.conf is following: [global] workgroup = MYDOM netbios name = LANSERVER server string = Samba Server security = domain hosts allow = 10. 127. log file = /var/log/samba/log.%m max log size = 50 password server = PDC #encrypt passwords = yes #winbind uid = 10000-20000 #winbind gid = 10000-20000 idmap uid = 15000-20000 idmap gid =

* |VALGRIND_DO_LEAK_CHECK|: does a full memory leak check (like |--leak-check=full|) right now. This is useful for incrementally checking for leaks between arbitrary places in the program's execution. It has no return value. * |VALGRIND_DO_ADDED_LEAK_CHECK|: same as |VALGRIND_DO_LEAK_CHECK| but only shows the entries for which there was an increase in leaked

http://dovecot.org/releases/1.2/beta/dovecot-1.2.beta4.tar.gz http://dovecot.org/releases/1.2/beta/dovecot-1.2.beta4.tar.gz.sig This release fixes a memory corruption bug related to MODSEQ handling in earlier v1.2 releases. Memory corruption means that it's a security bug and possibly exploitable. MODSEQ code is new in v1.2, so v1.1 and older releases are not affected. Other than that, there

http://dovecot.org/releases/1.2/beta/dovecot-1.2.beta4.tar.gz http://dovecot.org/releases/1.2/beta/dovecot-1.2.beta4.tar.gz.sig This release fixes a memory corruption bug related to MODSEQ handling in earlier v1.2 releases. Memory corruption means that it's a security bug and possibly exploitable. MODSEQ code is new in v1.2, so v1.1 and older releases are not affected. Other than that, there

http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta4.tar.gz http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta4.tar.gz.sig Lots of fixes since beta3, but apparently there are still a few bugs left: - Is SORT working? - APPEND seems to have problems in some setups. - Still some SEARCH TEXT problems? Or Squat indexing problems? -------------- next part -------------- A non-text attachment

I am unable to get 2.0.beta4 to compile. I get the following errors: /usr/lib64/gcc/x86_64-slackware-linux/4.3.3/../../../../lib64/libwrap.a(hosts_access.o): In function `host_match': hosts_access.c:(.text+0x625): undefined reference to `yp_get_default_domain' collect2: ld returned 1 exit status make[3]: *** [tcpwrap] Error 1 make[3]: Leaving directory

Does the 6.1-BETA4-i386-disc2.iso contain only usr/share/doc, or for some reason i am unable to see anything else? I was looking for usr/src (and for a odd chance to have usr/ports); i suppose those two trees would be available somewhere on some disc for RELENG_6_1. I mounted the image as ... mdconfig -a -t vnode -f /path/to/6.1-BETA4-i386-disc2.iso -u 0 mount -t cd9660 /dev/md0 /mnt ...

Hi, I tried to compile asterisk-1.8.0-beta4 but after ./configure && make I've got following error: [CC] res_fax.c -> res_fax.o [LD] res_fax.o -> res_fax.so [CC] res_fax_spandsp.c -> res_fax_spandsp.o res_fax_spandsp.c:117: error: field ?fax_state? has incomplete type res_fax_spandsp.c:118: error: field ?t38_state? has incomplete type res_fax_spandsp.c: In function

Hi all, Were there encoder differences between beta4 and 1.0rc1? A precompiled oggenc for Windows identifies itself as beta4, and from a certain mono file produces 53.3 kb/s files, whereas one I've compiled myself, identifying itself as 1.0rc1, produces 55.9 kb/s. Is this a feature or a bug? Also, all the links to images at the top of: http://www.vorbis.com/download_win.psp are broken.

Hi, Some of you may recall that I got the VP3 decoder working with the xine multimedia player some time ago and posted a patch for anyone else to try. I really messed up when I did that since I generated the patch against some random CVS snapshot of xine-lib. I did better this time and generated the patch against the latest release of xine-lib (1.0-beta4, released today). If you

Hello, I hope you won't mind if I give you mine opinion and suggestions about Vorbis audio encoder, especially new version. I was pretty satisfied with the quality of Beta4 encoder. For a bitrates around 112 to 128 kb/s I consider it better then any other audio compression formats (MP3, AAC, ...) at same bitrate. Sound quality that this version produces with bitrates below 112 kb/s was not

Hi! I would like to share with you an interesting test result. I re-encoded a song 10 times (the 2. made from the 1., the 3. made from the 2.,... the 10. made from the 9.), with a beta4 (CVS 20010620) and with an RC2 (CVS 20010817) library version, 256 kbit/s mode, channel coupling disabled at RC2. The beta4 is very good at the 10. encoding too, but the RC2 has some interesting quality bugs. So,

Using kmail with PLAIN authentication worked fine with beta3 but trying it with beta4 authentication fails. This is because kmail sends "username \0 username \0 password" in the authorization token and the new code to call auth_request_set_login_username() when supplied an authid must be returning failure (certainly commenting this code out returns to the beta3 behaviour of