Bug#888377: karlyriceditor: diff for NMU version 1.11-2.1

Hi Sebastian, Thank you for your efforts! I am fine with the NMU you are suggesting, so if you want, you can let it go through immediately (no more delay necessary). Cheers, Martin On 11/07/18 22:29 Sebastian Ramacher wrote: Control: tags 888377 + pending Dear maintainer, I've prepared

Bug#899571: [Pkg-mpd-maintainers] mpd is marked for autoremoval from testing

Hi, I can take a look at migrating the list. However, I understand that there has to be a DD assigned as the owner, but I'm not a DD. Cheers, Martin On 11/07/18 13:50 Petter Reinholdtsen wrote: [Florian Schlichting] Hello libfishsound Maintainers/Uploaders, given that your package

Bug#821321: libvorbisfile: ov_pcm_seek wrongly returns OV_EOF or segfaults sometimes

Hi Frank, Thank you for your bug report! Judging from the code that reproduces the bug (two subsequent seeks to 0) and from the related vorbis code you are mentioning, this sounds a lot like #782831, which was fixed in 1.3.4-3. Could you confirm or refute that theory by testing your code (I

Bug#818037: vorbis-tools: vcut always(?) segfaults

Frank Heckenbach wrote: The patch is in the git repository. Where can I get it (just the patch, so I can try it against the jessie version)? https://git.xiph.org/ says: vorbis-tools.git ... Last change 5 months ago It's not yet in the upstream git repository (I submitted the patch through

Bug#818037: vorbis-tools: vcut always(?) segfaults

tags 818037 + pending thanks Frank Heckenbach wrote: Sorry for the brief description, but for what I can tell, that's really it. I tried various cases, and vcut always seems to just segfault. Here's one example: % head -c 50 /dev/zero | oggenc -Q -r -o 1.ogg - % vcut 1.ogg 2.ogg 3.ogg +1

Bug#803828: karlyriceditor: FTBFS with FFmpeg 2.9

Thanks Felipe for the upload, thanks Andreas for the patch! Martin

Bug#803828: karlyriceditor: FTBFS with FFmpeg 2.9

Felipe Sateler wrote: Thanks. I'm confused though: there are still deprecation warnings: ffmpegvideoencoder.cpp:264:24: warning: 'AVCodecContext::coded_frame' is deprecated [-Wdeprecated-declarations] if ( audioCodecCtx->coded_frame && audioCodecCtx->coded_frame->pts != AV_NOPTS_VALUE )

Bug#803828: karlyriceditor: FTBFS with FFmpeg 2.9

Felipe Sateler wrote: Please update the changelog fully to add the bug closure and upload distro (if you want, you can do it on a different branch that is only merged to master once the package is in the archive). Sorry. Please find the updated changelog in

Bug#803828: karlyriceditor: FTBFS with FFmpeg 2.9

Hi Andreas, Andreas Cadhalpun wrote: I think there is a misunderstanding here. The deprecation of the APIs this patch is about happened several years ago, so fixing the code is certainly not premature, rather the contrary. The goal is that all Debian packages are ready for the new upstream

Bug#803828: karlyriceditor: FTBFS with FFmpeg 2.9

severity 803828 minor thanks Hi Andreas, There was no update on this bug report because I found any upload on this matter premature. When this bug was reported, there was no transition yet [1] and the FFmpeg version you wanted to upgrade to hadn't even been release by upstream [2]. Nothing

Bug#798960: libvorbis: Please upgrade to 1.3.5

No technical reason, just not enough time to test is as well as the number of reverse dependencies would demand it for a new upstream release. My testing efforts so far: * Test compilation of vorbis-tools against the libvorbis-dev package * Perform very basic tests of the ogg-vorbis related

Bug#795708: /usr/bin/ogg123: ogg123: Metadata_block_picture comments spew base64 all over the screen

Note: A bug report about the same issue seems to be present upstream: https://trac.xiph.org/ticket/1570

Bug#802393: libvorbisfile3: ov_raw_total() ignores the size of the last page

Package: libvorbisfile3 Version: 1.3.4-3 Severity: normal Tags: confirmed The maintainers of the package "libogg-vorbis-decoder-perl" discovered that the return value of "ov_raw_total()" with i==-1 changed after the upgrade from libvorbisfile3 1.3.4-2 to 1.3.4-3, which breaks their test

Bug#801610: libogg-vorbis-decoder-perl: FTBFS: Failed test 'raw_total'

block 801610 by 802393 thanks Niko Tyni wrote: On Mon, Oct 12, 2015 at 04:52:37PM +0300, Niko Tyni wrote: # Failed test 'raw_total' # at t/basic.t line 20. # got: '4414398' # expected: '4418594' This test was broken by src:libvorbis (binary:libvorbisfile3 to be

Bug#772877: oggenc fails when using '--advanced-encode-option disable_coupling' switch and CBR encoding

reassign 772877 libvorbisenc2 retitle 772877 libvorbis: Segmentation fault when disabling channel coupling thanks Actually the oggenc code about setting the "disable_coupling" option seems to be fine, but the relevant libvorbis encoding code not so much. So I'm reassigning this to

Bug#775983: oggenc: Invalid memory access with low sampling rate

tags 775983 + confirmed retitle 775983 oggenc: Invalid memory access with low sampling rate thanks The problem seems to be independent of oggenc's resampler. It can be observed with any input file having a low sampling rate, e.g.: dd if=/dev/zero bs=1024 count=1000 | valgrind oggenc -r -R

Bug#263762: /usr/bin/oggdec: oggdec manpage error: oggdec - doesn't write to stdout

tags 263762 + pending thanks Dear Reuben, I've fixed this by adjusting oggdec's behavior to the one specified in the man page (instead of adjusting the information in the man page). I think that's the behavior that most users would expect. A trivial code change did the trick. New

Bug#694812: subtitlecomposer: Spellchecking aborts program when blank entry encountered

tags 694812 + pending thanks Apparently this is a general problem of Sonnet::Dialog, which cannot handle empty buffers. I was able to reproduce the crash outside of Subtitle Composer in an isolated example by passing an empty buffer to Sonnet::Dialog. Sonnet::Dialog's specification doesn't

Bug#797644: kdelibs5-dev: kopete FTBFS: No rule to make target '/usr/lib/libsoprano.so', needed by 'kopete/kopete'

Martin Steghöfer wrote: It's fine for "libkhtml.so" to request linking to libsoprano. But if it does so, IMHO its corresponding -dev package should make sure that the necessary dependencies are pulled in. Never mind, someone just re-added the missing dependency to kdelibs5-dev, j

Bug#797644: kdelibs5-dev: kopete FTBFS: No rule to make target '/usr/lib/libsoprano.so', needed by 'kopete/kopete'

Thank you for your comment, Scott! Let my clarify... Scott Kitterman wrote: If there's a warning not to link against it, isn't the solution not to do that? Yes, of course it would be a solution *not* to link against it, but "kdelibs5-dev" forces me to do so (that's why I blame it). That's

Bug#797644: kdelibs5-dev: kopete FTBFS: No rule to make target '/usr/lib/libsoprano.so', needed by 'kopete/kopete'

Dear kdelibs5-dev maintainers, One package I worked on is affected by this problem, too. That's why I started investigating this issue and found out that there is a whole bunch of packages that are currently (or were recently) FTBFS'ing because of this problem. Some maintainers employed the

Bug#775983: oggenc: low --resample rate -> double free or corruption

Petter Reinholdtsen wrote: [Jakub Wilk 2015-01-22] I tried to resample the input file to a very low rate, but oggenc crashed: This no longer happen with version 1.4.0-6 on my machine, at least. Now I get an error instead: No crash for me, either. But valgrind reports a whole bunch of invalid

Bug#799957: subtitlecomposer: Please upgrade to 0.5.7

n moved to Github [2]. Cheers, Martin Steghöfer [1] http://sourceforge.net/projects/subcomposer/ [2] https://github.com/maxrd2/subtitlecomposer/

Bug#798960: libvorbis: Please upgrade to 1.3.5

El 22-09-2015 a les 23:40, Petter Reinholdtsen ha escrit: Did you include all the patches in Debian into the 1.3.5 release? Knowing which to keep will make the update a bit easier for us. The complete set is available from https://sources.debian.net/src/libvorbis/1.3.4-3/debian/patches/ >.

Bug#777209: libkate1 is not Multi-Arch compatible

Petter Reinholdtsen wrote: E: libkate-tools: package-installs-python-bytecode usr/lib/python2.7/dist-packages/kdj/__init__.pyc E: libkate-tools: package-installs-python-bytecode usr/lib/python2.7/dist-packages/kdj/__init__.pyo E: libkate-tools: package-installs-python-bytecode

Bug#790442: FTBFS with new LaTeX: Unknown float option `H'.

tags 790442 + pending thanks Thanks for the fix, Ralph! I just backported it into the package. Cheers, Martin Ralph Giles wrote: On Mon, 29 Jun 2015 11:32:43 -0400 Martin Michlmayr wrote: You're using the "H" float option. According to

Bug#606224: oggvideotools: oggJoin fails on powerpc

Petter Reinholdtsen wrote: [...] PATH=`pwd`/debian/oggvideotools/usr/bin:$PATH ./debian/tests/test-oggjoin + cd /tmp/tmp.25t0237HSw + echo info: Running autopkgtest script ./debian/tests/test-oggjoin info: Running autopkgtest script ./debian/tests/test-oggjoin + echo info: Generating Ogg Theora

Bug#606224: oggvideotools: oggJoin fails on powerpc

I compiled the package from source in the mentioned QEMU-emulated big-endian MIPS machine, so I could debug it properly. This way I found the culprit for this specific error. However, only very little of the other file reading code seems to be ready for a big-endian environment. There seems to

Bug#606224: oggvideotools: oggJoin fails on powerpc

found 606224 0.8a-1 thanks Since there was no more feedback from the bug reporter, I tried to reproduce this on my own. I don't have access to a ppc machine, but managed to get a Debian Wheezy running in a QEMU-emulated big-endian MIPS machine, on which I could reproduce the problem with

Bug#782831: libvorbis: use of non-initialized variable leads to SIGSEV in dhewm3

Tobias Frost wrote: I'm currently considering to NMU the workaround. I hope that I get around to integrating the 1.3.4 patch or packaging 1.3.5 this weekend. Otherwise, please NMU the workaround. It may not be too nice to just have a workaround, but I consider it safe. Best, Martin

Bug#782831: libvorbis: use of non-initialized variable leads to SIGSEV in dhewm3

El 12-06-2015 a les 15:06, Tobias Frost ha escrit: Did you report this issue already upstream? Could not find it on their BTS... Not necessary because upstream doesn't have the problem. Martin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of

Bug#782831: libvorbis: use of non-initialized variable leads to SIGSEV in dhewm3 -- fixed in new upstream version

Hi Tobias! Thank you for the effort! I've already identified the problem. The upstream commit we imported in order to fix #762571 had some issues that were fixed later in the upstream repository (but never imported into the Debian package). I've identified the relevant commits and they seem

Bug#784075: subtitlecomposer: Missing Build-Conflicts entry qt5-qmake

Package: subtitlecomposer Version: 0.5.3-4 Severity: minor Dear maintainers of subtitlecomposer, The package subtitlecomposer doesn't build from source if the package qt5-qmake is installed. If this package is installed, the subtitlecomposer's build system will use the Qt5 QMake instead of

Bug#782831: libvorbis: use of non-initialized variable leads to SIGSEV in dhewm3

Update: This is related to the beginning-of-stream special case for seeking and to the fact that there is only one normal ogg page in the file. The first time this special case is used, it seems to advance the page pointer to a place where the same special case cannot find any page during the

Bug#782831: libvorbis: use of non-initialized variable leads to SIGSEV in dhewm3

Dear Tobi, Thank you for the bug report and your analysis of the problem. The error handling is one thing. A library should be robust to failures and not crash the whole product. The crashing doesn't happen on other distros because for bug #762571 we backported an upstream change that fixes

Bug#776086: vorbis-tools: CVE-2014-9638 CVE-2014-9639 CVE-2014-9640

Moritz Muehlenhoff wrote: Did you contact upstream, are fixes available for these? There are bug tracker items available for the two remaining issues [1] [2], but there has been no movement so far. I've looked into it and the security aspect is fairly easy to fix by just adding an

Bug#776326: subtitlecomposer breaks MIME type detection of some PNGs

Package: subtitlecomposer Version: 0.5.3-4 Severity: normal Dear maintainers of subtitlecomposer, the installation of the package subtitlecomposer breaks the MIME type detection of certain PNGs. Before installation of subtitlecomposer: | mast:~$ gvfs-info headset.png | grep content-type |

Bug#776086: vorbis-tools: CVE-2014-9638 CVE-2014-9639 CVE-2014-9640

retitle 776086 CVE-2014-9638 CVE-2014-9639 thanks Dear Salvatore, thank you for reporting this! Salvatore Bonaccorso wrote: CVE-2014-9638[0]: Oggenc division by zero issue Confirmed with 1.4.0-6 as well as with the current git head. There doesn't seem to be a fix yet, so I am going to

Bug#774516: vorbis-tools: null pointer dereference

Jakub Wilk wrote: AFL comes with comprehensive documentation, but if you had trouble setting it up, please let me know. :-) No real trouble, but some questions I'd like to ask you (seeing that you seem to have more experience with the tool). But that is better done off-list, this bug report

Bug#774516: vorbis-tools: null pointer dereference

Forgot to CC the bug report itself. Here comes the message: Martin Steghöfer wrote: reassign 774516 libvorbisfile3 tags 774516 confirmed thanks Hi Jakub, Thank you for the bug report! Jakub Wilk wrote: Both oggdec and ogg123 crash on the attached file, trying to dereference null pointer

Bug#728062: vorbis-tools: mailcap of ogginfo

tags 728062 + pending thanks Martin Steghöfer wrote: So for now I've uploaded the change only to the separate branch mime in our git repository. If nobody raises any concerns, I will integrate this into the master branch, so it can be uploaded to the archive eventually. No concerns raised

Bug#578720: vorbis-tools: Sends invalid argument to ALSA when playing some files

Hi Ron! Ron wrote: No, that's fine. Most of that was just me thinking out loud as I traced through the relevant code. That we agree on that just means we came to the same conclusion. I didn't mean to suggest you thought otherwise, I was just fleshing out the reasons I thought that was the

Bug#578720: vorbis-tools: Sends invalid argument to ALSA when playing some files

Hi Ron! I agree that implementing some magic to find out the real reason isn't a very good idea. I think the main point where we still disagree is how magic (according to you) or specified (according to me) the meaning of EINVAL really is in this situation. Ron write: The problem is, that

Bug#772976: oggdec internationalization is broken

Package: vorbis-tools Version: 1.4.0-6 Severity: minor File: /usr/bin/oggdec While trying to fix a different bug, I've discovered that the oggdec executable uses the _ (underscore) macro for internationalization and has translations of the relevant strings available in the .po files, but

Bug#772978: vorbis-tools: oggdec crashes with SIGFPE (was: oggdec goes into an infinite loop while processing file)

Package: vorbis-tools Version: 1.4.0-6 Severity: normal File: /usr/bin/oggdec Tags: confirmed I'm forwarding this bug report from Ubuntu bug 629135 [1]. Original description: / | Binary package hint: vorbis-tools | | oggdec goes into an infinite loop while processing the | file at

Bug#772981: libvorbis: Suspicion of SIGFPE with corrupt input file

Package: libvorbis Version: 1.3.4-2 Severity: normal While investigating the cause for #772978, the relevant libvorbis code gave me the impression that (with input files different from the referenced one) the division by zero may happen even if oggdec handled the reported errors correctly.

Bug#578720: vorbis-tools: Sends invalid argument to ALSA when playing some files

severity 578720 minor thanks Martin Steghöfer wrote: The error message here is a bit cryptic. What it tries to say is: Your output device doesn't support Mono playback and no software in the output pipeline [...] is willing to do the necessary upmixing [...] Doing the upmixing in ogg123

Bug#578720: vorbis-tools: Sends invalid argument to ALSA when playing some files

Hi Ron! Thank you for your quick and comprehensive answer! :-) Unfortunately, I think I should have pasted more information into my previous mail. Most of your answer tries to argue away a point that I actually already ruled out in a message I posted earlier to this bug report: It looks like

Bug#772877: oggenc fails when using '--advanced-encode-option disable_coupling' switch and CBR encoding

Package: vorbis-tools Version: 1.4.0-6 Severity: normal File: /usr/bin/oggenc Tags: confirmed I'm forwarding this bug report from Ubuntu bug 948459 [1]. Original description: | Running the following command line in a shell (with in.wav | being a commong 16bit 44,1KHz wave file): | | oggenc

Bug#312185: vorbis-tools: ogg123 plays speex files wrong: clicks, then silence.

Martin Steghöfer wrote: However, the issue happens even after transcoding the speex file to ogg vorbis (using audacity). This assessment was based and on a file mix-up in my testing process and is wrong. The issue is speex-specific. The problem occurs with speex files that declare 2

Bug#772766: vorbis-tools: ogg123 shows error message and aborts playback of speex files

Package: vorbis-tools Version: 1.4.0-6 Severity: normal File: /usr/bin/ogg123 Tags: pending While working on the fix for #312185, related to acoustic problems with playing stereo speex files in ogg123, I discovered additional unrelated issues with ogg123's ability to play speex files: The

Bug#739099: vorbis-tools: ogg123 manpage inadequately documents -d option

Hi Paul! Martin Steghöfer wrote: [documentation examples skipped] I'm not sure what else you'd expect here. Especially your doubt about the format of the name-value pairs seems to be explained in the very first paragraph of the man page (-o option:value). Is the information not structured

Bug#728062: vorbis-tools: mailcap of ogginfo

Hi Kevin! Thank you for the contribution! It sounds like a good idea to me. I've given your patch a try and, for what I can see, it works great. It seems to implement the cat action properly, while not disturbing the view action (thanks to the low priority). However, as I don't know much

Bug#239073: /usr/bin/ogg123: ogg123 status filling the console

tags 239073 + pending thanks Thanks for reporting the bug! A patch has been committed to our git repository and an updated version of the package will soon be uploaded to the Debian archives. Cheers, Martin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a

Bug#772137: unblock: vorbis-tools/1.4.0-6 (fixing crash and faulty parameter parsing)

Ivo De Decker wrote: Unblocked. Thanks! :-) Martin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#263762: /usr/bin/oggdec: oggdec manpage error: oggdec - doesn't write to stdout

Thanks for reporting this issue! I think it's the oggdec executable that needs fixing rather than the documentation. Writing to -.wav is probably a quite undesired behavior for most users. Will look into it... Cheers, Martin -- To UNSUBSCRIBE, email to

Bug#772137: unblock: vorbis-tools/1.4.0-6 (fixing crash and faulty parameter parsing)

tags 772137 - moreinfo thanks Ivo De Decker wrote: If the package is uploaded before Monday Dec 8th, it can still be unblocked. Otherwise, it's too late for jessie. Remove the moreinfo tag once it's in unstable. Thank you for your efforts! The package just got uploaded and will shortly

Bug#772391: vorbis-tools: bashism in /bin/sh script

tags 772391 confirmed pending thanks Thank you for reporting this! I've fixed this in git commit af56389cda. The current severity minor seems appropriate, given that the affected line is never actually executed in a properly installed system, and that even if it is executed using dash

Bug#772137: unblock: vorbis-tools/1.4.0-6 (fixing crash and faulty parameter parsing)

Ivo De Decker wrote: This package is not in unstable, so it can't be unblocked. Thanks for the reply! The changes are in our git repository, but I don't have upload permissions and the only member of our team who does hasn't gotten around to uploading it yet. So I tried to get the changes

Bug#763338: Bug#771363: Get #763338 and #771363 into Jessie

Forwarded message Subject: Re: Bug#772137: unblock: vorbis-tools/1.4.0-6 (fixing crash and faulty parameter parsing) Date: Sat, 6 Dec 2014 18:16:34 +0100 From: Ivo De Decker iv...@debian.org To: Martin Steghöfer mar...@steghoefer.eu, 772...@bugs.debian.org Control

Bug#772137: unblock: vorbis-tools/1.4.0-6 (fixing crash and faulty parameter parsing)

of input parameters in the script vorbistagedit, which makes it impossible to use the script with filenames containing spaces. The changlog entry for 1.4.0-6: [ Martin Steghöfer ] * Fix oggenc crash on closing raw input files by backporting r19117 from upstream (Closes: #771363

Bug#763338: Get #763338 and #771363 into Jessie

Petter Reinholdtsen wrote: Did you ask for pre-approval? No, I was hoping we would have something uploaded before I asked for unblock. Finally I sent in a debdiff this morning [1]. Let's see if someone attends to it in time. Cheers, Martin [1] https://bugs.debian.org/772137 -- To

Bug#763338: Get #763338 and #771363 into Jessie

If we want to get this into Jessie, we probably need to act now. Could you try getting this uploaded, Petter? Cheers, Martin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#771363: Fixed in git; severity important

severity 771363 important thanks Fixed in git. I'm changing the severity of this to important: Even though the crash happens *after* correctly encoding the file, it prevents posterior files from being encoded and makes batch encoding impossible. This severity probably qualifies the fix to

Bug#771448: vorbistagedit doesn't read filenames from stdin

Package: vorbis-tools Version: 1.4.0-5 Severity: normal File: /usr/bin/vorbistagedit While working on the fix for #763338, related to the vorbistagedit script, I discovered another issue with the same script: The documentation claims that without input files given as command-line arguments

Bug#763338: /usr/bin/vorbistagedit: Doesn't escape filenames properly

Thank you for reporting this problem, Roland! I tried to track the problem down. I'm certainly not a shell-script expert, but I think I fixed it. The patch that was applied earlier to fix this bug only fixed the quoting of the *input* to getopt. However, there was still a problem with the

Bug#771363: oggenc --raw segfaults

tags 771363 confirmed thanks Jakub Wilk wrote: Package: vorbis-tools Version: 1.4.0-5 oggenc --raw seems to always segfault: Thanks for the bug report, Jakub! I can reproduce this bug in 1.4.0-5 and several older versions, so this isn't something we broke recently. And it doesn't only

Bug#769479: unblock: libvorbis/1.3.4-2 (fix invalid memory access)

has the potential to crash applications that use libvorbis with a segfault, if the application doesn't have additional sanity checks in place that go beyond checking libvorbis' return values. The changlog entry for 1.3.4-2: [ Martin Steghöfer ] * Add sampling rate sanity check to avoid

Bug#768685: libtheora: FTBFS in jessie: ld: player_example-player_example.o: undefined reference to symbol 'rintf@@GLIBC_2.2.5'

tags 768685 + patch pending thanks Hi Simon! Thanks for your help! The patch works fine. It compiles in my unstable jail on amd64 and the player example binary still works as expected. Cheers, Martin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of

Bug#307325: ogg123 freeze when interrupting at End-Of-Stream

Hi Rémi! On Sat, 10 Apr 2010 12:02:40 +0300 Rémi Denis-Courmont r...@remlab.net wrote: reopen 307325 submitter 307325 ! found 307325 1.4.0-1 thanks This is still happening here. If I press Ctrl+C when ogg123 shows '(EOS)' at the end of the status line (after Output Buffer), it gets completely

Bug#739099: vorbis-tools: ogg123 manpage inadequately documents -d option

tags 739099 moreinfo thanks On Sat, 15 Feb 2014 19:57:36 + Paul LeoNerd Evans leon...@leonerd.org.uk wrote: The manpage briefly mentions the -d option, and says it takes such choices as 'alsa'. It further mentions that the 'alsa' option has some sub-parameters. However, the manpage

Bug#745857: ogg123 outputs corrupt sound when pulseaudio is installed

tags 745857 moreinfo thanks Hi Stefan! Thanks for reporting this bug. It would really help us, if you could contribute some more information about this. To get started, some questions: 1. Which output device (-d option) are you using with ogg123? Does the stuttering happen with all of

Bug#578720: vorbis-tools: Sends invalid argument to ALSA when playing some files

tags 578720 wontfix thanks Hi John! On Thu, 22 Apr 2010 07:44:50 +0100 John Talbut j...@dpets.co.uk wrote: Playing: /data/Sounds/Barbara_Allen.ogg Ogg Vorbis stream: 1 channel, 44100 Hz ALSA snd_pcm_hw_params_set_channels error: Invalid argument Error: Cannot open device alsa. The error

Bug#359948: vorbis-tools: ogg123 undocumentedly requires -d to preceed -f

On Wed, 29 Mar 2006 09:40:47 -0900 Britton Leo Kerin bkerin...@letterboxes.org wrote: Actually the man page doesn't really even say that -f is going to require -d, and the error message that you get when you try -f alone doesn't say that you need to have the -d preceed the -f, though this

Bug#538025: Still found in 1.4.0-4

found 538025 vorbis-tools/1.4.0-4 thanks This is still an issue in 1.4.0-4. Cheers, Martin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#510459: No luck reproducing this

I've tried to reproduce this issue on an installation with all the old library versions mentioned in the original bug report. No luck so far. In order to reproduce it I've tried several combinations of the following: * Play with inaccessible ALSA (original bug report) * Play with 2 instances in

Bug#716613: [Mayhem] Bug report on vorbis-tools: oggenc crashes with exit status 136

reassign 716613 libvorbisenc2 thanks This test case actually triggers 2 bugs that are both related to the sampling rate of the input file being 0: The first one being in libvorbis (including the most recent version 1.3.4-1): ==29485== Invalid read of size 4 ==29485==at 0x50F62C2:

Bug#312185: vorbis-tools: ogg123 plays speex files wrong: clicks, then silence.

Bug still reproducible with vorbis-tools 1.4.0-4. As this issue happens mostly with this specific file, a decoding issue would stand to reason. However, the issue happens even after transcoding the speex file to ogg vorbis (using audacity). As it's very unlikely that the actual waveform is

Bug#765341: Please don't let audacity freeze like this...

Martin Steghöfer wrote: Andoru Ekkusu wrote: Does anyone have any idea when this patch will be committed? Hopefully soon, otherwise the new package won't make it to testing in time before the freeze. Then getting the fix into jessie will become much more complicated. I think it's quite

Bug#765341: Maintainers, please make sure this makes it into testing in time :-)

Hopefully the maintainers pick up those fixes soon, otherwise the new package won't make it to testing in time before the freeze. Then getting the fixes into jessie will become much more complicated. I think it's quite important for the usability to have these remaining issues fixed. Cheers,

Bug#765779: Maintainers, please make sure this makes it into testing in time :-)

Andoru Ekkusu wrote: Does anyone have any idea when this patch will be committed? Hopefully soon, otherwise the new package won't make it to testing in time before the freeze. Then getting the fix into jessie will become much more complicated. I think it's quite important for the usability

Bug#765341: more information

Fabian Greffrath wrote: just because noone has done this so far (or I have read over it), I want to thank you for the massive amount of effort and time you invest in fixing these bugs, both in Audacity and in wxwidgets! So, thank you! ;) It's always nice to be appreciated, thanks! :-) Martin

Bug#765341: Patch available

Hi Manfred! Manfred wrote: I get the same error which Klaumi reported. I installed Audacity today using Synaptic, then I recorded both sides of a turntable without problems. First time that error occured after pressing ctrl-B, it always occurs when playing a .aup file, also those files

Bug#765341: more information

El 21/10/14 a les 14:13, Klaumi Klingsporn ha escrit: sorry for the late answer No need to apologize, you've been a great help so far! El 21/10/14 a les 16:10, Klaumi Klingsporn ha escrit: and I also added the configure flag '--with-lv2=system' to Debian/rules ...which I think is a good

Bug#765341: more information

tag 765341 patch thanks El 16/10/14 a les 20:19, Martin Steghöfer ha escrit: 2. Small buttons in the project recovery dialog [...] Regarding 2: I've observed this. It's a bug of wxWidgets 3.0.x. I've filed it in the wxWidget upstream tracker, but it doesn't seem to receive much attention

Bug#765341: more information

Hi Klaumi! Regarding (1): El 16/10/14 a les 23:53, Klaumi Klingsporn ha escrit: You find a sample-project at: https://www.dropbox.com/s/79d6p6sri6shlj5/sample-project.tgz?dl=0 Thanks, that sample project helped a lot to track down the problem! :-) I identified the problem as a bug in

Bug#765779: audacity: An assertion failed! when changing track volume or panning

Dear Andoru, thanks a lot for the bug report! :-) With the upgrade to 3.0, wxWidgets enforces the correct usage of its API a lot more with asserts. So now, many bugs that were in Audacity before become visible as error messages (which themselves may cause even more undesired behavior, if

Bug#753744: audacity does nothing when trying to load a ogg-file by passing its name as argument

Hi! Would you mind sharing that .ogg file? This way your problem can be reproduced. I couldn't reproduce it with any of the .ogg files I have. Cheers, Martin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact

Bug#739722: libvorbis: New upstream release

Hi Kurt! On Tue, 9 Sep 2014 17:21:18 +0200 Kurt Roeckx k...@roeckx.be wrote: Any news about this? Would you mind I did an NMU with the new upstream version? It seems that no one of the packaging group that maintains this package is active any more. So Petter Reinholdtsen and me have joined

Bug#765341: more information

Hi Klaumi! Thank you for reporting the issue(s)! I have to admit that I'm a bit lost in your tale. Am I right that what you are reporting are the following 3 issues? 1. assert !ms_clipboard failed in wxClipboardSync in various occasions: a) When opening a certain project (all project in

Bug#762571: Patch for libvorbis (Was: Debdiff)

Petter Reinholdtsen wrote: Thank you very much. I used it when uploading an NMU fixing this issue and a few others. I converted the source format to 3.0 (quilt) in the process, to make it easier to track changes done to the upstream source. Thanks for your effort, otherwise this patch would

Bug#749659: audacity: Systematic check for Printf/Format mismatches

El 09/10/14 a les 01:11, Benjamin Drung ha escrit: Your patch needs to be forward ported, We already have a patch that fixes 2.0.6 for wxWidgets 3.0. Back when you asked me to forward-port my patch to the current svn head (in order to get the changes into upstream), I did. Apart from the

Bug#749659: audacity: Systematic check for Printf/Format mismatches

Hi Benjamin! Martin Steghöfer wrote: And before we just upload stuff to upstream, I'd also like to discuss the upstream integration with the person that has been working on wx3.0 there Looking at the recent upstream activity, I've changed my mind about this: We should get

Bug#749136: jellyfish: FTBFS with clang instead of gcc

El 09/10/14 a les 13:16, Andreas Tille ha escrit: Thanks a lot for your work on this Always a pleasure working with you guys :-) Martin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#749136: jellyfish: FTBFS with clang instead of gcc

Hi Andreas! El 04/10/14 a les 19:41, Andreas Tille ha escrit: In the case of Jellyfish I guess the best thing is to migrate to latest upstream version. That sounds like a good idea in general. It won't solve the clang issue, though. I commited the packaging to Git - however, it needs

Bug#716353: biosquid: sreformat crash - Proposing patch

Hi there! :-) I've fixed the crash. It was a segmentation fault due to a faulty implementation of a command-line options parser. The command line parser accessed invalid memory when a given option matched several option definitions as a prefix, but none of them exactly (e.g. --s as option

Bug#749136: jellyfish: FTBFS with clang instead of gcc

Hi Andreas! El 08/10/14 a les 21:06, Andreas Tille ha escrit: Would you volunteer to check the current Git repository regarding the clang issue? It's not ready yet but the state is good enough to look into the clang build. The current state of the package in Debian-Med's git repository has

Bug#716540: Status of netcdf (Was: Bug#716540: [Mayhem] Bug report on minc-tools: minccopy crashes with exit status 139)

El 06/10/14 a les 09:57, Andreas Tille ha escrit: there exists a patch for an issue in netcdf and a changelog entry [...] in Git about a new version. Thanks for pointing out the work that has been started on packaging a new version! I'd like to add that there has just been a new upstream

Bug#763989: xdrawchem hangs when doing Undo

Package: xdrawchem Version: 2.0-2 Severity: normal Hi there! Under certain circumstances (which actually happen a lot) xdrawchem hangs when doing Undo (be it via the Menu or via Ctrl+Z, it doesn't matter) and has to be killed. It seems that the hang always happens when the Undo operation

Bug#749136: jellyfish: FTBFS with clang instead of gcc

Hi all, I can confirm that the build fails with clang 3.4 and that the patch sent by Alexander fixes the problem. The most recent version of clang (3.5), however, compiles the package fine without any patches. This is because Clang has extended its detection of constant values and is now

  1   2   >