Bug#600522: Better solution
Hi again again.
A way better solution might be this:
OWNER=$(ls -l "$key" | sed
's/^[^[:space:]]\{10,12\}[[:space:]]\+[^[:space:]]\+[[:space:]]\+\([^[:space:]]\+\).*/\1/'
It's more future proof than the original method, cause it only
looks at space and non-space characters and at most counts them.
So any change in output which does not change space/non-space
pattern will not make sed notice the user.
Greets,
Raoul Bönisch
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#600522: finding workaround: SOLVED
Hi again!
This is a little workaround to make things going with SElinux
activated. Note that this does not check wether SElinux is
activated or not, nevertheless it works in both situation,
because the one seperating " " isn't screwing things up.
In /lib/cryptsetup/cryptdisks.functions replace line 252:
OWNER=$(ls -l "$key" | sed 's/^.\{10\}[+]\?.[^[:space:]]*
\([^[:space:]]*\).*/\1/')
with
OWNER=$(ls -l "$key" | sed 's/^.\{11\}[+]\?.[^[:space:]]*
\([^[:space:]]*\).*/\1/')
Note, the change is in \{10\} which becomes \{11\}
This will work with output like this:
$ ls -l /etc/keys/din-1.luks
-r. 1 root root 9 2010-01-13 13:01 /etc/keys/din-1.luks
and this:
$ ls -l /etc/keys/din-1.luks
-r 1 root root 9 2010-01-13 13:01 /etc/keys/din-1.luks
Note: I manually removed the '.' after permissions fields to show
the situation without SElinux enabled.
The package maintainer shall decide wether this should be
applied to official packages. My posting is ment as a hint for
reason and solution of this bug and as a quick workaround for
people desperately searching the bug trackers for help.
Greetings,
Raoul Bönisch
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#600522: Possible reason for this bug might be SElinux
Hi!
I have SElinux activated in permissive mode. This changes the
output of ls slightly:
$ ls -l "/etc/keys/din-1.luks"
-r. 1 root root 9 2010-01-13 13:01 /etc/keys/din-1.luks
This leads to returning wrong value for OWNER in
/lib/cryptsetup/cryptdisks.functions, line 262:
$ ls -l "/etc/keys/din-1.luks" | sed
's/^.\{10\}[+]\?.[^[:space:]]* \([^[:space:]]*\).*/\1/'
1
Returned is value 1, most likely "root" should have been
returned.
A possibly important difference from ls output when using SElnux
is the dot after the permissions letters. If so, the sed line
would have to be changed. I haven't checked the sed line so far.
Greetings,
Raoul Bönisch
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#316343: Same problem in Xmonad depending on hotkey sequence
Hello! Some people seem to hit this bug, some don't. For those who hit it, it's more or less frequent, that's why simply retrying the key combo they configured is a "workaround". I see a different in probability to hit the bug on keypress depending on the specific key combo. The combination Mod-Shift-L did only very rarely work for me (thenth of presses needed). The combination Mod-Pause and Mod-Shift-Pause work every time so far. So this is my workaround, simply use the so far always working key combination in Xmonad. Greetings, Raoul -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#326023: ifupdown sets $IFACE and $LOGICAL to same logical interface name for ppp
Hello!
Just to be sure you have the same issue as me: is the cause of your
problem the setting of $IFACE and $LOGICAL to the same $LOGICAL
interface name by ifupdown?
If so, this is my temporary workaround:
if test "$IFACE" == ""
then
echo "Crappy hack for ppp0, report bug"
IFACE=ppp0
fi
Replace with the logical interface name in
use. This goes to if-{up,down}.d scripts.
The remaining problem is lack of flexibility which physical
interface can be used. Here only ppp0 may be used.
I think $IFACE should be set properly for ppp connections by
ifupdown.
Greetings,
Raoul
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#547138: Solution
Hello again! Simply recompiling the libasound2-plugins package solves the problem. It then gets the proper verion number from /usr/include/alsa/pcm_rate.h of the libasound2-dev package. Do this to ged rid of the error message: apt-src install libasound2-plugins cd alsa-plugins-1.0.20/ fakeroot dpkg-buildpackage -us -uc cd .. ls *.deb sudo dpkg -i *.deb -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#547138: SND_PCM_RATE_PLUGIN_VERSION not defined
Hello! I seems to me SND_PCM_RATE_PLUGIN_VERSION isn't even defined anymore in the alsa-plugins source. Here is what I did: apt-src install libasound2-plugins cd alsa-plugins-1.0.20/ grep -r "Invalid rate plugin version" * grep -r SND_PCM_RATE_PLUGIN_VERSION * There is no hit but lines where SND_PCM_RATE_PLUGIN_VERSION is actually used, but never defined. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#532345: System freeze kernel log messages
* Tzafrir Cohen [2009-09-13 21:28]: > On Sun, Sep 13, 2009 at 08:45:08AM +0200, Raoul Bönisch wrote: > Hmmm... hfc_zap_chanconfig looks fishy . Try the following patch: > > The attached patch looks like the fix to me. Though I'm not sure if > there isn't any actual use in the code of the fact that sigchan is > reset. Yes, this patch seems to be the fix. I can now use the system.conf with dchan=3 and there is no system crash. I am not sure about wether then really no hardhdlc is used and what effects the options have. But there is no more freeze or reboot. Of course I will leave the system.conf as is here with the hardhdlc=3 option anyway. As far as I know this is the better option for the HFC cards. Anyway, thanks for killing this bug. Raoul -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#532345: System freeze kernel log messages
Hi again! * Tzafrir Cohen [2009-09-13 09:22]: > On Sun, Sep 13, 2009 at 08:45:08AM +0200, Raoul Bönisch wrote: > > hardhdlc=3 > > # dchan = 3 ### System freeze!!! ### > > With which driver? > > E.g., what is the output of: modinfo zaphfc This is the new driver I am using right now and it works fine with asterisk: $ modinfo zaphfc filename: /lib/modules/2.6.31-rc8/dahdi/zaphfc/zaphfc.ko license:GPL author: Jens Wilke , Daniele (Vihai) Orlandi , Jose A. Deniz description:HFC-S PCI A ISDN alias: pci:v182Dd3069sv*sd*bc*sc*i* alias: pci:v114Fd0073sv*sd*bc*sc*i* alias: pci:v114Fd0072sv*sd*bc*sc*i* alias: pci:v114Fd0071sv*sd*bc*sc*i* alias: pci:v114Fd0070sv*sd*bc*sc*i* alias: pci:v15B0d2BD0sv*sd*bc*sc*i* alias: pci:v1051d0100sv*sd*bc*sc*i* alias: pci:v0871dFFA1sv*sd*bc*sc*i* alias: pci:v0871dFFA2sv*sd*bc*sc*i* alias: pci:v1043d0675sv*sd*bc*sc*i* alias: pci:v13D1d2BD1sv*sd*bc*sc*i* alias: pci:v1397dB100sv*sd*bc*sc*i* alias: pci:v1397dB00Csv*sd*bc*sc*i* alias: pci:v1397dB00Bsv*sd*bc*sc*i* alias: pci:v1397dB00Asv*sd*bc*sc*i* alias: pci:v1397dB009sv*sd*bc*sc*i* alias: pci:v1397dB008sv*sd*bc*sc*i* alias: pci:v1397dB007sv*sd*bc*sc*i* alias: pci:v1397dB006sv*sd*bc*sc*i* alias: pci:v1397dB000sv*sd*bc*sc*i* alias: pci:v1397d2BD0sv*sd*bc*sc*i* depends:dahdi vermagic: 2.6.31-rc8 SMP mod_unload modversions parm: modes:[Deprecated] bit-mask to configure NT mode (int) parm: nt_modes:Comma-separated list of card IDs to configure in NT mode (array of int) parm: force_l1_up:Don't allow L1 to go down (int) I have successfully used this driver in official 2.6.30-1-amd64, too. The 2.6.31-r8 I have to use because of the Nouveau graphics driver of which I want the latest version and there were serious issues with it when compiled with older kernels. > > So, yes, it can be reproduced, but all in all the package works > > for me. This is still an issue to track, I am afraid. > > I've only recently replaced the old zaphfc with the newer one. > I'm actually surprised hardhdlc worked before. Sorry, I think I did not describe that clearly. With the old driver, I tried some different hfc patches, the option "dchan" lead to a system freeze, but the option hardhdlc did not. However, the old drivers never worked. There was an error with the hardhdlc option and I think it was because hardhdlc was never supported. So no phone calls possible with the old stuff. Only the zaptel driver worked for me in old days. But this is really long time ago. With the new driver, see modinfo zaphfc above, there is still the system freeze with the "dchan" option, but the hardhdlc option makes things work, at least with the recent asterisk packages. Calls in and out work ok and the sound is good most of the time. I experience persistent sound clutter on some calls occasionally, but that might not be the driver's or asterisk's fault. It might be my telco or my phone hardware installation locally. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#532345: System freeze kernel log messages
Hallo! Now I have to differentiate. There is the option "dchan" as opposed to "hardhdlc" in /etc/dahdi/system.conf. This is my current system.conf: $ cat /etc/dahdi/system.conf # If you edit this file and execute /usr/sbin/dahdi_genconf again, # your manual changes will be LOST. # Dahdi Configuration File # # This file is parsed by the Dahdi Configurator, dahdi_cfg # # Span 1: ZTHFC1 "HFC-S PCI A ISDN card 1 [TE]" (MASTER) span=1,1,3,ccs,ami bchan=1-2 hardhdlc=3 # dchan = 3 ### System freeze!!! ### echocanceller=mg2,1-2 loadzone= de defaultzone = de I have compiled current SVN with original mainstream DAHDI 2.2.0.2 and it works with this system.conf. However when using the dchan I still get the system freeze. With hardhdlc I can use the DAHDI driver and it works so far with the asterisk packages from Debian unstable. So, yes, it can be reproduced, but all in all the package works for me. This is still an issue to track, I am afraid. * Tzafrir Cohen [2009-09-13 08:37]: > On Fri, Jun 12, 2009 at 03:53:41PM +0200, Raoul Bönisch wrote: > > Hello! > > > > I noticed the kernel was still able to log messages. Even my > > SysRq keystroke were recognized, at least the help menu. > > > > The messages file is attached, stripped down to messages > > concerning the crash. > > > > Meanwhile I tried rc4 from debian testing which crashed, too. > > Sometimes the system immediately reboots, sometimes it freezes. > > Current SVN package replaces zaphfc with a new driver, based on vzaphfc, > but called zaphfc. Any chance you can test it and see if the problem is > can still be reproduced? > > -- >Tzafrir Cohen > icq#16849755 jabber:tzafrir.co...@xorcom.com > +972-50-7952406 mailto:tzafrir.co...@xorcom.com > http://www.xorcom.com iax:gu...@local.xorcom.com/tzafrir -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#528825: Graphical user interface for XMMS2
Hi! You can try gxmms2 as a graphical interface. It works with XMMS2 0.6DrMattDestruction-3. I can acknowledge the problem of the latest version of Esperanza depending on libxmmsclient4 and being uninstallable as of today. There is even a bug #531418 which I hit, too. Greetings, Raoul -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#467137: Error message about TLS packet with unexpected length due to usage of DNS alias name of mail server.
Hi again! Ok, then my guess was right. It is the canonical hostname you have to use. Nevertheless I think it is worth mentioning that the logging messages are misleading. They should be more verbose about this issue. In the debian package it might be enough to just put a hint in the config file passwd.client so that the user immediately sees the canonical name has to be used. Greetings and thanks for this quick reply, Raoul -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#467137: Error message about TLS packet with unexpected length due to usage of DNS alias name of mail server.
This email contains a simple workaround to this problem. Subject: exim4: Error message about TLS packet with unexpected length due to usage of DNS alias name of mail server. Package: exim4 Version: 4.69-11 Severity: normal This problem is similar to #467137, #482404, #467137, #478470. Note that I am using exim4-daemon-light though. I am using DSL-product Alice by HanseNet in germany. They advise to use smtp.alice-dsl.net as an smtp server. See https://www.alice-dsl.de/alicehelp/index.jsp?showContentNodeId=1291&type=6#1291 (german help page). With this setup I get this error: TLS recv error on connection to out.alice-dsl.net [88.44.60.16]: A TLS packet with unexpected length was received. TLS send error on connection to out.alice-dsl.net [88.44.60.16]: The specified session has been invalidated for some reason. R=smarthost_auto T=remote_smtp_smarthost defer (-45): SMTP error from remote mail server after MAIL FROM: SIZE=1517: host out.alice-dsl.net [88.44.60.16]: 454 5.7.3 Client does not have permission to submit mail to this server. I investigated the smtp server address: # host smtp.alice-dsl.net smtp.alice-dsl.net CNAME out.alice-dsl.net out.alice-dsl.net A 88.44.60.16 # nslookup smtp.alice-dsl.net Server: 127.0.0.1 Address:127.0.0.1#53 Non-authoritative answer: smtp.alice-dsl.net canonical name = out.alice-dsl.net. Name: out.alice-dsl.net Address: 88.44.60.16 Obviously smtp.alice-dsl.net is an alias dns name while out.alice-dsl.net is its canonical name. I put in the canonical smtp server name in the exim4 configuration and the problem was solved. The mail gets thru without the error message. The problem does not seem to be entropy related. It is never there with mail server out.alice-dsl.net and it is there every time with smtp.alice-dsl.net. Plus, there is enough entropy available: cat /proc/sys/kernel/random/entropy_avail 1305 I have tried removing ca-certificates which didn't solve the problem. My guess is that exim4 looks up the canonical name and tries to check it against the configuration file /etc/exim4/passwd.client to find login and password. When using the alias dns name in this file, exim4 doesn't find any login and password. I assume this is not the desired behaviour of exim4. Exim4 should lookup the canonical name as well as alias names, in case ISP's publish alias names of their DNS servers. At least there should be a hint to this problem in the documentation and the advice to check DNS names of mail servers and try them to get things working. Greetings, Raoul -- Package-specific info: Exim version 4.69 #1 built 10-May-2009 09:42:17 Copyright (c) University of Cambridge 2006 Berkeley DB: Berkeley DB 4.6.21: (September 27, 2007) Support for: crypteq iconv() IPv6 GnuTLS move_frozen_messages Lookups: lsearch wildlsearch nwildlsearch iplsearch cdb dbm dbmnz dnsdb dsearch nis nis0 passwd Authenticators: cram_md5 plaintext Routers: accept dnslookup ipliteral manualroute queryprogram redirect Transports: appendfile/maildir/mailstore autoreply lmtp pipe smtp Fixed never_users: 0 Size of off_t: 8 Configuration file is /var/lib/exim4/config.autogenerated # /etc/exim4/update-exim4.conf.conf # # Edit this file and /etc/mailname by hand and execute update-exim4.conf # yourself or use 'dpkg-reconfigure exim4-config' #;// Modified by Raoul B?ch :: `date` Mon Dec 1 16:28:26 UTC 2008 # # Please note that this is _not_ a dpkg-conffile and that automatic changes # to this file might happen. The code handling this will honor your local # changes, so this is usually fine, but will break local schemes that mess # around with multiple versions of the file. # # update-exim4.conf uses this file to determine variable values to generate # exim configuration macros for the configuration file. # # Most settings found in here do have corresponding questions in the # Debconf configuration, but not all of them. # # This is a Debian specific file dc_eximconfig_configtype='smarthost' dc_other_hostnames='res' dc_local_interfaces='127.0.0.1' dc_readhost='res' dc_relay_domains='' dc_minimaldns='false' dc_relay_nets='' dc_smarthost='mail.gmx.net;smtp.alice-dsl.net;smtp.cvmx.de' CFILEMODE='644' dc_use_split_config='true' dc_hide_mailname='true' dc_mailname_in_oh='true' dc_localdelivery='mail_spool' mailname:res.br.priv -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.29-2-amd64 (SMP w/1 CPU core) Locale: LANG=C, lc_ctype=de...@euro (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/bash Versions of packages exim4 depends on: ii debconf [debconf-2.0] 1.5.26 Debian configuration management sy ii exim4-base4.69-11support files for all Exim MTA (v4 ii exim4-daemon-light4.69-11lightweight Exim MTA (v4) daemon exim4 recommends no packages. exim4 suggests no packa
Bug#509405: Partial solution
> Can you please test that with the latest upstream svn trunk and branches/2.1 > ? It took me some time to compile this because I hit the UNICODE wxWidgets issue. Finally I could manage to compile testcall and iaxcomm. The problem basically still persists. One change was that the ALSA default device is now selectable in iaxcomm even if it was not explicitely defined in some asound.conf file. But I get stuttering sound and when selecting the hardware device I get the output "log-hw00.txt" attached to this email as soon as connecting a call. When selecting the default device I get "log-default.txt" output. I have uninstalled the Debian iaxcomm 2.0.2-3 and the iaxclient library shipped with Debian to make sure the newly compile program and library will be used. In Help/About of iaxcomm I get iaxComm version: 1.1.0final and libiaxclient version: 2.1-svn (as specified by me when installing. The ulimit output is the following: ulimit -a core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 30 file size (blocks, -f) unlimited pending signals (-i) 16382 max locked memory (kbytes, -l) 64 max memory size (kbytes, -m) unlimited open files (-n) 1024 pipe size(512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 60 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) unlimited virtual memory (kbytes, -v) unlimited file locks (-x) unlimited Greets, Raoul Expression 'SetApproximateSampleRate( pcm, hwParams, sr )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 1291 Expression 'PaAlsaStreamComponent_InitialConfigure( &self->capture, inParams, self->primeBuffers, hwParamsCapture, &realSr )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 1862 Expression 'PaAlsaStream_Configure( stream, inputParameters, outputParameters, sampleRate, framesPerBuffer, &inputLatency, &outputLatency, &hostBufferSizeMode )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 1986 PortAudio error at Unable to open streams: Invalid error code (value greater than zero) Expression 'SetApproximateSampleRate( pcm, hwParams, sr )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 1291 Expression 'PaAlsaStreamComponent_InitialConfigure( &self->capture, inParams, self->primeBuffers, hwParamsCapture, &realSr )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 1862 Expression 'PaAlsaStream_Configure( stream, inputParameters, outputParameters, sampleRate, framesPerBuffer, &inputLatency, &outputLatency, &hostBufferSizeMode )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 1986 PortAudio error at Unable to open streams: Invalid error code (value greater than zero) Expression 'SetApproximateSampleRate( pcm, hwParams, sr )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 1291 Expression 'PaAlsaStreamComponent_InitialConfigure( &self->capture, inParams, self->primeBuffers, hwParamsCapture, &realSr )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 1862 Expression 'PaAlsaStream_Configure( stream, inputParameters, outputParameters, sampleRate, framesPerBuffer, &inputLatency, &outputLatency, &hostBufferSizeMode )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 1986 PortAudio error at Unable to open streams: Invalid error code (value greater than zero) Expression 'SetApproximateSampleRate( pcm, hwParams, sr )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 1291 Expression 'PaAlsaStreamComponent_InitialConfigure( &self->capture, inParams, self->primeBuffers, hwParamsCapture, &realSr )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 1862 Expression 'PaAlsaStream_Configure( stream, inputParameters, outputParameters, sampleRate, framesPerBuffer, &inputLatency, &outputLatency, &hostBufferSizeMode )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 1986 PortAudio error at Unable to open streams: Invalid error code (value greater than zero) Expression 'SetApproximateSampleRate( pcm, hwParams, sr )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 1291 Expression 'PaAlsaStreamComponent_InitialConfigure( &self->capture, inParams, self->primeBuffers, hwParamsCapture, &realSr )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 1862 Expression 'PaAlsaStream_Configure( stream, inputParameters, outputParameters, sampleRate, framesPerBuffer, &inputLatency, &outputLatency, &hostBufferSizeMode )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 1986 PortAudio error at Unable to open streams: Invalid error code (value greater than zero) Expression 'SetApproximateSampleRate( pcm, hwParams, sr )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 1291 Expression 'PaAlsaStreamComponent_InitialConfigure( &self->capture, inParams, self->primeBuffers, hwParamsCapture, &realSr )' failed in 'src/hostapi/al
Bug#509405: Partial solution
Hello! I installed this file in ~/.asoundrc: defaults.pcm.card 1 defaults.ctl.card 1 Then in iaxcomm I use default as every sound device. Then connecting works and the sound sent is ok, but the incoming sound is stuttering very badly. This is the best result I could achieve so far. Greetings, Raoul Bönisch -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#509405: Strange behaviour after reboot
Hello! After one of the reboots on the machine all of the sudden without any change to the whole system the sound device /dev/dsp appeared in iaxcomm config menu. I chose this one for all sound devices and intermittently dialing works. Choosing the ALSA sound devices does not work at all, not one time. After dialing, hanging up results in different failures. Sometimes the messages Expression 'bytesWritten = write( component->fd, component->buffer, len )' failed in 'src/hostapi/oss/pa_unix_oss.c', line: 1096 Expression 'PaOssStreamComponent_Write( stream->playback, &frames )' failed in 'src/hostapi/oss/pa_unix_oss.c', line: 1665 appear and that's all. iaxcomm says ring out is running. Actually it seems to, though no sounds is there. But the loudness bar moves after a time as the answering machine picks up, so the application seems to receive the answering machine sound which I cannot hear on my headphones. Then the machine seems to record and clicking the connection bar on top of iaxcomm window does not give blue background. Clicking second connection bar and then the first gives the blue blackground. Only then can I hangup this connection. Sometimes I even get the sound again. Defocusing sound by clicking alternative connection bar and refocusing does not work though. I think there might be a problem in iaxcomm choosing which channel to play on the audio output. There is a 2.1 branch in the development source code and some bug reports fixed in latest releases sound quite similar to mine. Perhaps the problem is even fixed in latest release. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
