Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?

I have this testing box for test any changes in the future release of Debian.
In the last update it comes with a new darkice package (v 1.5-1). As I have
another server in stable with darkice working, I test this new version in this
box in a local setup, in the LAN.

   * What exactly did you do (or not do) that was effective (or
     ineffective)?

For the test I start icecast2 service, stop the firewall (ufw) only for the
test, and start darkice as root. Both the icecast and the darkice configs are
configured for one to talk with the other without problem... But in all my
probes, darkice 1.5 is not connecting with icecast...

That is the output of darkice v 1.5-1 in the console, with some debug info:

$ sudo darkice -v 5
DarkIce 1.5 live audio streamer, http://code.google.com/p/darkice/
Copyright (c) 2000-2007, Tyrell Hungary, http://tyrell.hu/
Copyright (c) 2008-2013, Akos Maroy and Rafael Diniz
This is free software, and you are welcome to redistribute it
under the terms of The GNU General Public License version 3 or
any later version.

Using config file: /etc/darkice.cfg
26-Feb-2025 20:02:04 Using ALSA DSP input device: hw:0,1
26-Feb-2025 20:02:04 buffer size:  882000
26-Feb-2025 20:02:04 buffer size:  882000
26-Feb-2025 20:02:04 encoding
26-Feb-2025 20:02:04 Using POSIX real-time scheduling, priority 3
DarkIce: TcpSocket.cpp:264: connect error [111]

But if I download the darkice version in stable (1.3-0.3+b1) from
packages.debian.org, uncompress the package and start the binary, it is working
well. This is the same output but with 1.3 version:

$ sudo ./darkice -v 5
DarkIce 1.3 live audio streamer, http://code.google.com/p/darkice/
Copyright (c) 2000-2007, Tyrell Hungary, http://tyrell.hu/
Copyright (c) 2008-2013, Akos Maroy and Rafael Diniz
This is free software, and you are welcome to redistribute it
under the terms of The GNU General Public License version 3 or
any later version.

Using config file: /etc/darkice.cfg
26-Feb-2025 20:06:53 Using ALSA DSP input device: hw:0,1
26-Feb-2025 20:06:53 buffer size:  882000
26-Feb-2025 20:06:53 buffer size:  882000
26-Feb-2025 20:06:53 encoding
26-Feb-2025 20:06:53 Using POSIX real-time scheduling, priority 3
26-Feb-2025 20:06:53 HTTP/1.0 200
26-Feb-2025 20:06:53 HTTP/1.0 200
26-Feb-2025 20:06:53 set lame mode 1
26-Feb-2025 20:06:53 set lame channels 2
26-Feb-2025 20:06:53 set lame in sample rate 44100
26-Feb-2025 20:06:53 set lame out sample rate 44100
26-Feb-2025 20:06:53 set lame bit rate 96
26-Feb-2025 20:06:53 set lame quality 9
26-Feb-2025 20:06:53 set lame lowpass frequency 0
26-Feb-2025 20:06:53 set lame highpass frequency 0
26-Feb-2025 20:06:53 set lame psycho acoustic model 1
26-Feb-2025 20:06:53 set lame error protection 1
LAME 3.100 64bits (http://lame.sf.net)
Using polyphase lowpass filter, transition band: 15115 Hz - 15648 Hz
26-Feb-2025 20:06:53 MultiThreadedConnector :: ThreadData :: threadFunction,
was (thread, priority, type):  0x559f457023f0 3 SCHED_FIFO
26-Feb-2025 20:06:53 MultiThreadedConnector :: ThreadData :: threadFunction,
was (thread, priority, type):  0x559f45702410 3 SCHED_FIFO
26-Feb-2025 20:06:53 MultiThreadedConnector :: ThreadData :: threadFunction,
now is (thread, priority, type):  0x559f457023f0 1 SCHED_FIFO
26-Feb-2025 20:06:53 MultiThreadedConnector :: ThreadData :: threadFunction,
now is (thread, priority, type):  0x559f45702410 1 SCHED_FIFO

   * What was the outcome of this action?

This is a test only, not in production. But if this is not fixed for the next
stable version, I will can not use darkice in my server...

I know nothing about programing, but can make some other basic test, so if you
need that I make other probes, instruct me and I will make them.

Many thanks for your work in Debian. Excuse my poor english. Greetings.
Martintxo.

   * What outcome did you expect instead?

*** End of the template - remove these template lines ***

I recently upgraded one of my encoders to Trixie and can confirm darkice
is unable to connect to my Icecast2 server. The error I'm getting is

DarkIce: IceCast2.cpp:258: Icecast2 - wrong password [0]

I've verified the source password is correct.

I've downgraded to the darkice version in oldstable for the meantime and
functionality has resumed.

Hello

I see than now we have icecast 2.5.0-1 in Testing. So I made some more test,
both in testing and in stable (this in our production server). I made all test
with the versions that I can install in Debian.

But first I can put here some subjects:

The darkice config that I was using is similar to this (look at the password
line):
  [icecast2-0]
  bitrateMode     = cbr       # average bit rate
  format          = mp3    # format of the stream: mp3
  bitrate         = 96        # bitrate of the stream sent to the server
  server          = localhost
                                  # host name of the server
  port            = 8000      # port of the IceCast2 server, usually 8000
  password        = xxxxxx    # source password to the IceCast2 server
  mountPoint      = xxxxxx  # mount point of this stream on the IceCast2
  ...

I see now that it is not good. The file
/usr/share/doc/darkice/examples/darkice.cfg states that the password line for
an icecast server need to be:
  # source password to the IceCast2 server
  password        = hackme
  # there must not be a comment following the password
This is my fault. But this may be soo comun...

In this bugreport from upstream they talk about the same problem:
https://github.com/rafael2k/darkice/issues/187

Well, the test that I made are:

1. Our current situation that works (see my first email in this bug report):
icecast 2.4.4-4+b2 from stable (trixie) and darkice 1.3-0.3+b1 from oldstable
(bookworm): Darkice connects wiht icecast whith any pasword config format.
Good!!

2. The situation that is not working: icecast 2.4.4-4+b2 from stable (trixie)
and darkice 1.5-1 from stable (trixie): It can not connect with icecast in any
form, is the same if the password line is:
  password        = xxxxxx    # source password to the IceCast2 server
or:
  password        = xxxxxx
or:
  password=xxxxxx

In all cases the error of darkice in console is:
  DarkIce: TcpSocket.cpp:264: connect error [111]

3. Another situation that IS WORKING: the new icecast 2.5.0-1 that is now
in testing, but installed from the upstream repository, see:
https://download.opensuse.org/repositories/multimedia:/xiph/
and darkice 1.5-1 from stable (trixie):
Whith this and the config:
  password        = xxxxxx    # source password to the IceCast2 server
not connects and the error is:
  DarkIce: IceCast2.cpp:258: Icecast2 - wrong password [0]

But if the config is (like stated in the example config file):
  password        = xxxxxx
or:
  password=xxxxxx
it connects well!!

Sooo, a workarround for this in stable (trixie) whould be to install the
upstream icecast packages, or to made a backport for the icecast testing
package for stable and put this in the Debian backports respository (this
is the best)....

By the way, there is a new version of darkice (1.6) in the upstream repository
at: https://github.com/rafael2k/darkice/releases
I don`t test it as it is source only. The changelog 1.5 - 1.6:
https://github.com/rafael2k/darkice/compare/v1.5...v1.6
seems to not talk anything about this...

Many thanks for maintaining these pieces of code. I think that darkice in stable
need to be restore to be funtional, I don't know if is best to change the
icecast code (changing the version), or to made modifications to the darkice
code. Greetings. Martintxo.

https://www.fundacionsustrai.org
https://www.sustraierakuntza.org