Your message dated Mon, 13 Feb 2012 19:38:34 +0100
with message-id <[email protected]>
and subject line Re: Bug#658928: moc crashes with FATAL_ERROR: Can't receive 
value from the server!
has caused the Debian Bug report #658928,
regarding moc crashes with FATAL_ERROR: Can't receive value from the server!
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
658928: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=658928
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: moc
Version: 1:2.5.0~alpha4+svn20111012-1
Severity: important

Dear Maintainer,

The issue seems to happen after playing several files in a directory,
not necessarily the first or for every file. I tried removing
~/.moc/cache and problem reoccured. I ran mocp -D and mocp_client_log
says:

Feb  6 13:11:29.291934: interface.c:292 send_tags_request(): Asking for tags 
for /home/ljholish/Downloads/JayLeboeuf44/hat4.wav
Feb  6 13:11:29.315049: protocol.c:63 get_int(): recv() failed when getting 
int: Connection reset by peer
Feb  6 13:11:29.315136: common.c:61 fatal(): FATAL ERROR: Can't receive value 
from the server!

# Jack output settings.
JackOutLeft             = "system:playback_1"
JackOutRight    = "system:playback_2"

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.39-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages moc depends on:
ii  libasound2                        1.0.24.1-4
ii  libc6                             2.13-26
ii  libcurl3-gnutls                   7.24.0-1
ii  libdb5.1                          5.1.29-1
ii  libfaad2                          2.7-7
ii  libflac8                          1.2.1-6
ii  libgcc1                           1:4.6.2-12
ii  libid3tag0                        0.15.1b-10
ii  libjack-jackd2-0 [libjack-0.116]  1.9.8~dfsg.1-1
ii  libltdl7                          2.4.2-1
ii  libmad0                           0.15.1b-7
ii  libmagic1                         5.09-2
ii  libmodplug1                       1:0.8.8.4-1
ii  libmpcdec6                        2:0.1~r459-1
ii  libncursesw5                      5.9-4
ii  libogg0                           1.2.2~dfsg-1
ii  librcc0                           0.2.9-3
ii  libresid-builder0c2a              2.1.1-11
ii  libsamplerate0                    0.1.8-2
ii  libsidplay2                       2.1.1-11
ii  libsidutils0                      2.1.1-11
ii  libsndfile1                       1.0.25-4
ii  libspeex1                         1.2~rc1-3
ii  libstdc++6                        4.6.2-12
ii  libtagc0                          1.7-1
ii  libtinfo5                         5.9-4
ii  libvorbis0a                       1.3.2-1.1
ii  libvorbisfile3                    1.3.2-1.1
ii  libwavpack1                       4.60.1-2
ii  zlib1g                            1:1.2.3.4.dfsg-3

moc recommends no packages.

Versions of packages moc suggests:
pn  moc-ffmpeg-plugin  <none>

-- no debconf information

-- 
Larry Holish
<[email protected]>



--- End Message ---
--- Begin Message ---
* Larry Holish [120213 11:32 -0600]:

> On Mon, Feb 13, 2012 at 08:49:24AM +0100, Elimar Riesebieter wrote:
> > Did you ever tried to use moc without jackd? Just stop the jack
> > daemon and run mocp -R ALSA just as a comparison.
> 
> moc is working perfectly using only the ALSA driver. No more crashes in
> any of the directories that previously caused trouble.
> 
> Further investigating my particular .asoundrc setup, I found this page
> which describes it:
> 
> http://jackaudio.org/routing_alsa
> 
[...]
> So I believe this is the source of the issue I reported, and not the moc
> package. I will find some other workaround. Thank you very much for your
> efforts on this issue Elimar and sorry for taking up your time.

Thanks for cooperation.
Bug closed hereby

Elimar

-- 
  You cannot propel yourself forward by
  patting yourself on the back.


--- End Message ---

Reply via email to