Am Wed, 03 Apr 2024 20:46:29 +0200
schrieb Simon Chopin :
> I just uploaded the attached debdiff to Ubuntu to both fix the FTBFS and
> start the t64 transition for this package, based on the following
> comment:
Are you able to test this for the dev snapshot of mpg123 before I do
the next releas
Am Sat, 23 Mar 2024 21:59:54 +0500
schrieb Andrey Rakhmatullin :
> Source: mpg123
> Version: 1.32.5-1
> Severity: serious
> Tags: ftbfs
>
> https://buildd.debian.org/status/fetch.php?pkg=mpg123&arch=armel&ver=1.32.5-1%2Bb1&stamp=1711185338&raw=0
This is being discussued in
https://bugs
Am Mon, 05 Feb 2024 08:36:28 +
schrieb Steve Langasek :
> we have identified
> mpg123 as a source package shipping runtime libraries whose ABI
> either is affected by the change in size of time_t, or could not be
> analyzed via abi-compliance-checker (and therefore to be on the safe
> side we
Am Sat, 05 Nov 2022 12:07:57 +
schrieb Witold Baryluk :
> trying to overwrite shared '/usr/include/mpg123.h', which is
> different from other instances of package libmpg123-dev:i386
Oh, dear. I broke multiarch headers again. By trying to fix BSDs that
don't react to _FILE_OFFSET_BITS at all
Are you using the alsa output plugin with routing to pulseaudio? I remember this
from Ubuntu systems. Running mpg123 -o pulse works, -o alsa plays static noise.
Maybe some byte offset not aligned to the data type ...
I suspect the link from alsa to pulse is faulty, as mpg123's alsa output module
ha
Am Wed, 5 Oct 2016 21:34:49 +0200
schrieb Salvatore Bonaccorso :
> Any news from the DWF project on the assigned CVE?
Nothing. I got the initial request to accept the MITRE Terms of Use for
CVE from the person handling my case (I assume). I replied to the mail
at 2016-09-30. Nothing came back. I
Am Tue, 04 Oct 2016 10:03:10 +
schrieb ow...@bugs.debian.org (Debian Bug Tracking System):
> This is an automatic notification regarding your Bug report
> which was filed against the mpg123 package:
>
> #838960: denial of service with crafted id3v2 tags in all mpg123 versions
> since 0.60
>
Am Thu, 29 Sep 2016 01:20:05 +0200
schrieb Thomas Orgis :
> Still nothing. I don't expect anything to arrive anymore. Perhaps that
> Google Docs form was a joke anyway. So, please let's just get a number
> via Debian and get on with it.
Nope, eh … yes. I got a reply now f
Am Tue, 27 Sep 2016 22:39:21 +0200
schrieb Thomas Orgis :
> Well, so far I did not get a response from http://iwantacve.org/
Still nothing. I don't expect anything to arrive anymore. Perhaps that
Google Docs form was a joke anyway. So, please let's just get a number
via Debian an
Am Tue, 27 Sep 2016 18:50:35 +0200
schrieb Florian Weimer :
> Debian is a CNA-covered product, mpg123 is part of Debian,
> so it is unclear what to do here. I'll ask around.
Well, so far I did not get a response from http://iwantacve.org/
(linked from
http://cve.mitre.org/cve/data_sources_produ
Am Tue, 27 Sep 2016 10:27:04 +0100
schrieb James Cowgill :
> Does this have a CVE ID? If not it should get one.
I wondered about that. At the moment I just acted on the bug report and
pushed the fix. I have to personal experience with the CVE procedure.
In the past, just "someone" made them appe
Am Sat, 31 Aug 2013 16:02:45 +0200
schrieb Reinhard Tartler :
> The attached patch seems to do the right thing on Debian
> kFreeBSD/i386, i386 and amd64. I've therefore uploadedit to Debian
> unstable.
Sadly, that patch still is not quite right. Now Linux/i386 mixes long
and off_t with 64 bit. T
(I'm also CCing the FreeBSD port maintainer, as I imagine they want that
handled, too.)
Am Sat, 31 Aug 2013 10:03:46 +0200
schrieb Reinhard Tartler :
> Thomas, may I have your opinion on this patch? If you are d'accord,
> I'd upload it to debian/unstable for further testing.
OK, I see that I ne
Am Wed, 28 Aug 2013 01:33:08 +0200
schrieb Thomas Orgis :
> But let me try to get my own logic straight again.
Damn, I shouldn't write such stuff late at night, the brain torn
between wildly differing problems and the urge to fall into hibernation.
> Current lfs_wrap.c is hardc
Am Tue, 27 Aug 2013 23:49:08 +0200
schrieb Reinhard Tartler :
> +if test
> ".$ac_cv_sizeof_int32_t$ac_cv_sys_file_offset_bits$ac_cv_sizeof_off_t"
> = ".4no8"; then
> + # Add dual-mode wrapper code.anyways
> + LFS_LOBJ=lfs_wrap.lo
> + ac_cv_sys_wide_off_t="yes"
> + AC_DEFI
Am Sun, 23 May 2010 02:41:04 +0400 (MSD)
schrieb William Pitcock :
> Both. I believe this is caused by a bug where the pointers appear to
> become realigned twice (e.g. to the next 16 bytes.) So I believe the
> second realignment is a bug that has always been there.
Though that assumption prove
Am Sat, 22 May 2010 03:43:28 +0400 (MSD)
schrieb William Pitcock :
> This is due to a memory alignment issue in the way that the struct is packed.
> With some help from an affected user, we bisected it to mpg123 SVN r2491.
OK, that revision replaced aligned memory blocks that relied on special
c
Am Wed, 19 May 2010 22:40:08 +0200
schrieb gregor herrmann :
> The minimal change to make the crash go away is to remove "-pie" from
> LDFLAGS.
So, we have some textrel issues, I suppose. I fail to see how mpg123 triggers
that, though. One observation I have, again in a VM with debian unstable.
Poke, poke.
Am Mon, 10 May 2010 22:54:15 +0200
schrieb gregor herrmann :
> Yup, my test results with the current (vanilla|debian) binary+lib are
> the same as yours but they are not necessarily the same as my
> original crashes, and yesterday I haven't systematically tested
> against the lib fro
Am Mon, 10 May 2010 21:23:59 +0200
schrieb Daniel Kobras :
> With drum.mp3, I'm now also seeing the segfault in an i386 chroot. amd64 is
> still fine. Building the Debian package with DEB_BUILD_OPTIONS=noharden (ie.
> without CFLAGS "-Wformat -D_FORTIFY_SOURCE=2 -fstack-protector -fPIE" and
> LDF
I just added this to the mpg123 tracker item:
I managed to reproduce a crash
(no report of double free(), but a segfault during free()) on a VM install
of debian testing, with mpg123 from unstable.
The funny thing is that I observe the debian mpg123 binary crashing with
the debian libmpg123 and a
Am Sat, 8 May 2010 00:12:09 +0200
schrieb gregor herrmann :
> Summary:
> - pulse, arts, esd, jack, nas: I have no pulse audio/artsd/esd/jackd/nas
> daemon installed
> - dummy: fails
> - alsa: still fails
> - oss: hm, somethings blocking my sound device; ah. found it later.
> no visible effects
Hi, this is mpg123 upstream.
I asked for some confirmation of the confinedness of the issue to the ALSA
output on
http://sourceforge.net/tracker/?func=detail&aid=2996045&group_id=135704&atid=733194
...
Actually, this concerns both issues: The crash and the high CPU usage. Can you
try another
23 matches
Mail list logo
