Package: zynaddsubfx
Version: 2.4.0-1.2
Followup-For: Bug #661887
Dear Maintainer,
I experience the same situation on my system.
To investigate the problem, I have run zynaddsubfx via strace:
strace -ff -o log zynaddsubfx
That's what I've found in one of the logs, after I tried to select one of banks
open("/usr/share/zynaddsubfx/banks/William_Godfrey_Collection//0045-Hard Stereo
Sweep Synth.xiz", O_RDONLY) = 7
fstat64(7, {st_mode=S_IFREG|0644, st_size=2860, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb0059000
fstat64(7, {st_mode=S_IFREG|0644, st_size=2860, ...}) = 0
_llseek(7, 0, [0], SEEK_SET) = 0
read(7,
"\37\213\10\0\0\0\0\0\0\3\355\\Qs\3338\16~\357\257\360\371\275\353\310\211c{\246\355\216/"...,
2860) = 2860
_llseek(7, 2860, [2860], SEEK_SET) = 0
close(7) = 0
munmap(0xb0059000, 4096) = 0
write(2, "mxml: Bad control character 0x1f"..., 62) = 62
When I opened the
/usr/share/zynaddsubfx/banks/William_Godfrey_Collection//0045-Hard Stereo Sweep
Synth.xiz
without decompression, I can see, that indeed the first byte is 0x1f
However if I rename it e.g. to test.gz and perform "gzip -d test.gz", I can see
correct XML file.
So the source of the problem is that zynaddsubfx does not recognize the ".xiz"
files as compressed, and attempts
to open them directly as XML.
*** End of the template - remove these lines ***
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (990, 'testing'), (50, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 3.2.11 (SMP w/2 CPU cores)
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages zynaddsubfx depends on:
ii libasound2 1.0.25-2
ii libc6 2.13-27
ii libfftw3-3 3.3-1
ii libfltk1.1 1.1.10-11
ii libgcc1 1:4.6.3-1
ii libjack-jackd2-0 [libjack-0.116] 1.9.8~dfsg.2-1
ii libmxml1 2.6-2
ii libstdc++6 4.6.3-1
ii zlib1g 1:1.2.6.dfsg-2
zynaddsubfx recommends no packages.
zynaddsubfx suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
