Your message dated Mon, 23 Sep 2013 19:40:37 +0100
with message-id 
<CAPQ4b8mWSuQ4YuMw_nwpDUJZESMBV_=5ctihyzgpb0p6jh-...@mail.gmail.com>
and subject line Re: Bug#705153: libsdl-mixer1.2: In scummvm I get this 
WARNING: SDL mixer output buffer size: 1024 differs from desired: 2048!
has caused the Debian Bug report #705153,
regarding libsdl-mixer1.2: In scummvm I get this WARNING: SDL mixer output 
buffer size: 1024 differs from desired: 2048!
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.)


-- 
705153: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=705153
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libsdl-mixer1.2
Version: 1.2.12-3
Severity: normal

Dear Maintainer,
I get the following whenever I try to play any games in scummvm which
use music.

$ scummvm
WARNING: SDL mixer output buffer size: 1024 differs from desired: 2048!
User picked target 'draci' (gameid 'draci')...
  Looking for a plugin supporting this gameid... Draci
  Starting 'Draci Historie'
Killed

$ drascula
WARNING: SDL mixer output buffer size: 1024 differs from desired: 2048!
User picked target 'drascula' (gameid 'drascula')...
  Looking for a plugin supporting this gameid... Drascula
  Starting 'Drascula: The Vampire Strikes Back'
Killed

$ ps ux | grep drascula
shirish  22722  0.0  0.0   4324   616 pts/2    S+   21:59   0:00
/bin/sh -e /usr/games/drascula
shirish  22724 14.6  1.0 386452 20596 pts/2    Sl+  21:59   0:03
/usr/games/scummvm -m 128 -p /usr/share/scummvm/drascula drascula
shirish  22729  0.0  0.0   8048   900 pts/1    S+   21:59   0:00 grep drascula

I have no idea whether it's scummvm, pulseaudio or scummvm at fault.

Please lemme know what the issue is.

-- System Information:
Debian Release: 7.0
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable'), (10, 'unstable'), (1,
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.8-trunk-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_IN.utf8, LC_CTYPE=en_IN.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libsdl-mixer1.2 depends on:
ii  libc6              2.17-0experimental2
ii  libflac8           1.2.1-6
ii  libmad0            0.15.1b-7
ii  libmikmod2         3.1.12-5
ii  libsdl1.2debian    1.2.15-5
ii  libvorbis0a        1.3.2-1.3
ii  libvorbisfile3     1.3.2-1.3
ii  multiarch-support  2.17-0experimental2

libsdl-mixer1.2 recommends no packages.

libsdl-mixer1.2 suggests no packages.

-- no debconf information

-- 
          Regards,
          Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
065C 6D79 A68C E7EA 52B3  8D70 950D 53FB 729A 8B17

--- End Message ---
--- Begin Message ---
2013/7/25 Manuel A. Fernandez Montecelo <[email protected]>:
> 2013/7/25 shirish शिरीष <[email protected]>:
>> Dear Manuel,
>> Due to unforseen circumstances, my system was down. I am now on a new
>> system which has just got Debian installed on it. It would take me
>> couple of days to check this out and see if the issue is still there
>> or not.
>>
>> Sorry for the lateness in reply.
>
> No problem, it's just that I want to see if something can be done
> early in the development cycle, rather than close to the next freeze.
>
> Also, I want to keep SDL-1.2 packages as clean as possible so things
> get fixed in version 2.
>
> So it's not urgent, but please remember to try this when you have the
> opportunity.

Nobody else complained about the issue during these months; and
meanwhile SDL2 version has been released a few months back already, so
1.2 branch is discontinued (upstream does not backport fixes to 1.2
versions, AFAIK).

So I think that it's better to close this bug report now, and reopen
it with new information if needed.


Cheers.
-- 
Manuel A. Fernandez Montecelo <[email protected]>

--- End Message ---

Reply via email to