affects 846570 apt
thanks
I was able to continue by running "dpkg --configure --pending", which
set up the "apt" package without further issues, then re-running
"aptitude safe-upgrade" to upgrade the remaining packages.
Ulrich
Package: aptitude
Version: 0.8.3-1+b2
Severity: important
When running an "aptitude safe-upgrade" on a Debian testing system that,
among other things, was meant to upgrade the apt package (from 1.3.1 to
1.4~beta1), I got this output:
> ...
> Vorbereitung zum Entpacken von
retitle 839112 Please revert to previous default settings
thanks
I also consider this change of defaults (the "mouse=a" change, at
least) a bug and would like to have it reverted. It is a very
disruptive change; to me, it was a sudden "WTF?! Pasting text from
another terminal no longer
tags 800576 + upstream fixed-upstream
thanks
I can confirm that the (trivial) upstream change mentioned by Jerome
above fixes this issue.
Ulrich
Package: firmware-realtek
Version: 0.44
Severity: wishlist
There is an rtl_bt/rtl8821a_fw.bin file in the upstream linux-firmware
repository (added in commit 8e181320b11de501046cf75c8c30915cd09a1e39),
but it is not yet included in the firmware-realtek Debian package. On
the other hand, the newest
I had a similar segfault issue in version 1.0.9.5, though in a
different place:
#0 0xb7f604e7 in debStatusIndex::Merge(pkgCacheGenerator,
OpProgress*) const () from /usr/lib/i386-linux-gnu/libapt-pkg.so.4.12
#1 0xb7ebddb4 in ?? () from /usr/lib/i386-linux-gnu/libapt-pkg.so.4.12
#2
Package: libdb5.3-java
Version: 5.3.28-7~deb8u1
Severity: grave
Justification: prevents package from being installed/upgraded
Unfortunately, there is another[1] bug in libdb5.3-java.maintscript which
means that the package still can't be installed or, if an earlier version
is present, can't be
Tangui, Jan: It is a different (though closely related) bug for which
I opened bug #773806 [1]. As soon as that bug is fixed in a new
version, it should be possible to upgrade normally.
Ulrich
[1] http://bugs.debian.org/773806
--
To UNSUBSCRIBE, email to
Package: picard
Version: 1.2-2+b1
Severity: wishlist
Upstream has released Picard 1.3:
http://blog.musicbrainz.org/2014/10/21/picard-1-3-released/
In light of the imminent Jessie freeze, it'd be great if this could
be packaged quickly. :-)
Ulrich
--
To UNSUBSCRIBE, email to
found 68 8:6.7.7.10+dfsg-1
thanks
After two years, this trivial fix has still not found its way into
unstable, meaning that the fft effect doesn't work. Any chance this
could be considered for inclusion in the near future?
Ulrich
--
To UNSUBSCRIBE, email to
Source: liblist-allutils-perl
Version: 0.03-1
Severity: wishlist
The current version on CPAN is 0.08. Please update the package.
Ulrich
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (990, 'testing'), (800, 'unstable'), (100, 'experimental')
Architecture:
Package: xul-ext-greasemonkey
Version: 1.12-1
Severity: important
Version 1.12-1 of the Greasemonkey package has successfully migrated to
testing even though it is not compatible with the Iceweasel version
there. This means that it is currently not possible to use Greasemonkey
on testing.
--
reassign 711747 libasound2-plugins
forcemerge 709855 711747
affects 709855 sox
thanks
Victor Porton wrote:
$ rec ~/t/x.wav
ALSA lib pcm_ioplug.c:920:(snd_pcm_ioplug_create) ioplug: Plugin
version mismatch
rec FAIL formats: can't open input `default': snd_pcm_open error:
No such device or
Fabian Greffrath wrote:
Do you know if the library interface/ABI has been changed in this release?
API-wise, there are a few added functions in libFLAC and libFLAC++,
but no existing functions have been removed or changed. Regarding the
ABI, I am not sure; but if the SHLIBS version is to
Source: flac
Version: 1.2.1-6
Severity: wishlist
After several years, a new upstream version of FLAC (1.3.0) has been
released by the Xiph.Org Foundation:
http://lists.xiph.org/pipermail/flac-dev/2013-May/004191.html
https://www.xiph.org/flac/changelog.html#flac_1_3_0
reassign 581201 libsox-fmt-ffmpeg 14.3.1-1
fixed 581201 14.3.1-1+b1
fixed 581201 14.3.1-2
thanks
Didier 'OdyX' Raboud wrote on 2010-05-17 [yes, that's three years ago]:
sox (14.3.1-1+b1) unstable; urgency=low
* Recompile against Debian official ffmpeg library (closes: #581201).
Closing…
unarchive 676167
thanks
Bohdan Linda wrote:
After an upgrade from Squeeze to Wheezy, `play` command starts issuing
segmentation fault. Bellow attached last part of strace.
Most probably, this is bug 676167.
Could you try one of the workarounds mentioned there (specifying the
audio driver
Fabian Greffrath wrote:
That should at least fix the symtom. However, I think it is still much
too easy to trigger this bug by accident. IMHO, there should not be
another header file called assert.h in a name space just one directory
level beneath /usr/include.
You are probably right. I doubt
This should be fixed in 1.3.0, which is due any day now. :)
https://git.xiph.org/?p=flac.git;a=commitdiff;h=b76d4f817c54c6fcfcb82fe72e38660c1b480774
Josh Coalson jcoal...@users.sourceforce.net
Sat, 29 Nov 2008 20:55:52 + (20:55 +)
Ulrich
--
To UNSUBSCRIBE, email to
I can't reproduce this with 1.2.1-6, although there weren't any
apparently related changes since 1.2.1-3.
I created a test file with the same name and also removed the MD5
hash, such that I got the same warning as in the original report. I
also varied the terminal width a bit. Still, there
fixed 537803 1.2.1-6
thanks
Christoph Anton Mitterer wrote:
Version: 1.2.1-1.2
It seems that flac cannot decode flac files, that have no known
extension (ogg/oga/flac).
One gets an error like:
filename: *** Got error code 0:FLAC__STREAM_DECODER_ERROR_STATUS_LOST_SYNC
I can't reproduce
The fix for this is in flac 1.3.0 that is going to be released soon.
Ulrich
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: file
Version: 5.11-2
Severity: normal
The debian/copyright file lists the file magic/Magdir/os9 as being
licensed under 4-clause BSD. However, this file has been relicensed to
2-clause BSD in the meantime, the same as the rest of the code.
-- System Information:
Debian Release: 7.0
Pascal Giard evily...@gmail.com:
I'll probably just push a 14.4.0-5 with it (14.4.0-4 went to
experimental).
The change is also in 14.4.1 (which will be out in two weeks' time), so a
14.4.0-5 isn't really necessary. Won't hurt either, of course.
Ulrich
--
To UNSUBSCRIBE, email to
Reinhard Tartler siret...@tauware.de:
Your package currently FTBFS against libav9 in experimental. The reason
is that the configure script checks the function 'av_open_input_file',
which has been replaced a long time ago by 'avformat_open_input':
It seems that the file
forcemerge 676167 687035
thanks
Torbjörn Andersson eriknos...@telia.com:
(All this seems familiar somehow... probably because I commented on
bug #664301 earlier this year. ...)
Yes, they are related: This problem is caused by the fix to #664301.
:) You'll find more information in bug
tags 672567 + fixed-upstream
thanks
Committed a fix to the Ogg Vorbis problem identified above.
Ubuntu6226: Could you confirm whether your problem only occurred with
files having 3, 5, 6, 7 etc. channels?
Ulrich
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a
tags 676167 + patch
thanks
It'd be interesting to know which driver causes the segfault on
platforms without ALSA support; it might be alsa there too, or one
of the following.
Apparently it is the oss format itself, which passes NULL to fileno().
I've attached a patch to replace the
tags 676143 + fixed-upstream
thanks
Frank Heckenbach f.heckenb...@fh-soft.de:
The following error message is misleading:
%sox -r441000 -s foo.raw foo.wav
sox FAIL formats: bad input format for file `foo.raw': data encoding
was not specified
since the encoding (-s) was actually specified.
retitle 672567 sox: terminates early on certain Ogg Vorbis files
found 672567 14.4.0-3
tags 672567 + upstream
thanks
Ubuntu 6226 ubuntu6...@yahoo.com:
It cannot play any OGG or it is very very choppy. It is
unfortuneltealy of no use..
any ogg playing is not working
I created a test file
Bob Proulx b...@proulx.com:
Is there any clue as to the root cause of the problem?
Yes. If an audio driver is explicitly specified by the user (via the
AUDIODRIVER environment variable or the -t option), SoX will use this
and there's no problem. Otherwise, SoX will try possible drivers in
Bob Proulx b...@proulx.com:
Although I don't know about
coreaudio it probably doesn't hurt. (shrug)
No, it isn't supposed to be compiled in at all on platforms other than MacOS.
Opening what driver produces the WARN alsa: can't encode 0-bit
Unknown or not applicable message? By the above
fixed 662830 2.91.3+git20120514.b9fec3e1-1
thanks
The problem has disappeared in current testing (hamster-applet
2.91.3+git20120514.b9fec3e1-1).
Ulrich
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
It simply does not work if one try to :
play -t alsa with hw:2,0 and some files files.mp3
It cannot play on another sound device else than the default one :
hw:0,0 (playing not sox converting).
What soundcards do you use (cat /proc/asound/cards shows a list)? Is
card 2 by any chance a USB
I've encountered the same bug, also in 2.7.3~rc2-1. I went through
versions 2.7.2-8, 2.7.2-13, and 2.7.3~rc1-1 previously, and none of
them exhibited this problem.
Ulrich
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
retitle 664301 sox: insists on using pulseaudio even when not available
tags 664301 + upstream
thanks
So the problem appears to be that SoX only checks whether its
PulseAudio format handler is present and, if so, decides to use it,
even if PulseAudio isn't running or not installed at all.
Hi,
a) what is your default audio device? Pulseaudio, or do you use JACK via ALSA?
b) You have a version mismatch between sox and its format handlers:
Package: sox
Version: 14.4.0-2
ii libsox-fmt-alsa 14.3.2-3
ii libsox-fmt-ao 14.3.2-3
ii libsox-fmt-base 14.3.2-3
ii libsox-fmt-oss
Package: hamster-applet
Version: 2.91.3+git20120211.9ebb889-2
Severity: normal
I'm using hamster in standalone mode, i.e. I run it as hamster-time-tracker
from a terminal.
Adding a previous activity only works once. When trying to use this function
a second time, only a small window without any
fixed 640482 8:6.7.4.0-1
thanks
I tried version 8:6.7.4.0-1 from experimental, and the bug is not
present there.
Ulrich
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Jonathan Nieder jrnie...@gmail.com:
Sorry for the slow reply. What kernel do you use nowadays? Does this
still happen?
Thank you for looking into this. The problem persisted for several
months, I think, but then disappeared. I don't think I have
experienced such a deadlock in the last
I'd like to add to this bug report that a very similar (the same?)
problem occurs when using the -update option to display. The image
will not be updated every time the file changes, and there are the
same messages about scenes.
On 2011-09-20, site admin magick wrote in the forum thread
severity 627321 grave
tags 627321 + fixed-upstream
thanks
The older upstream fix has now been released as a new upstream version
(2.25.0), could you please package it?
Changing severity to grave since a bidding program that can't bid is
unusable or mostly so, in my opinion.
Ulrich
Package: cups
Version: 1.4.6-1
Severity: important
With cups 1.4.6-1, I can't print some postscripts files anymore that used to
work before. (All the affected files are made with TeX and dvips, which may
or may not be a coincidence; not all dvips postscript files are affected.)
The error_log
It seems this is a bug in libpoppler that has already been fixed upstream:
https://bugs.freedesktop.org/show_bug.cgi?id=27728
However, it is still present in current testing (evince 2.30.3-1).
Ulrich
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of
Package: cron
Version: 3.0pl1-115
Severity: minor
In the EXAMPLE CRON FILE section of crontab(5), there is this example:
# Run on every second Saturday of the month
0 4 8-15 * *test $(date +\%u) -eq 6 echo 2nd Saturday
The range of days (8-15) in this example is one day too
Package: network-manager-gnome
Version: 0.8-1
Severity: normal
When editing a Wi-Fi connection (applet context menu - edit connections -
Wi-Fi - edit; or similar wording, as I am using the German localization),
the Apply button is always greyed out, even after doing changes. It is
therefore not
output 'ok_nocairo.png'
plot sin(x)
set terminal pngcairo size 1280,960
set output 'ok_cairo.png'
plot sin(x)
Ulrich Klauer
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: openoffice.org-core
Version: 1:3.1.1-16
Severity: normal
I tried to open a Word document. After calling
ooffice x.doc
the OOo splash appeared and disappeared again, then nothing happened. ps
showed a sleeping OOo instance. I tried again calling only
ooffice
and the welcome screen
48 matches
Mail list logo
