Bug#1057477: /usr/bin/ld: /lib/x86_64-linux-gnu/libavfilter.so.9: undefined reference to `ass_track_set_feature'

2023-12-05 Thread Christian Montanari
Package: libavfilter-extra9 Version: 7:6.1-5 Severity: normal Tags: d-i ftbfs Justification: fails to build from source (but built successfully in the past) I try to build "kpipewireheadlesstest" from "g...@invent.kde.org:plasma/kpipewire.git" then the build fail at link time when object `ass_t

Bug#896446: gotcha (am-utils: segfaulting error 4 in libc-2.27.so with kernels 4.+)

2018-04-27 Thread Christian Montanari
this patch works better... diff --git a/amd/srvr_nfs.c b/amd/srvr_nfs.c index 99624311..7c1c2ea0 100644 --- a/amd/srvr_nfs.c +++ b/amd/srvr_nfs.c @@ -958,7 +958,7 @@ no_dns: ITER(fs, fserver, &nfs_srvr_list) { if (STREQ(host, fs->fs_host) && nfs_version == fs->fs_version && -

Bug#896446: gotcha (am-utils: segfaulting error 4 in libc-2.27.so with kernels 4.+)

2018-04-25 Thread Christian Montanari
nop... its my fault, yet again, not to use the standard am.config file. so it woz variable "nfs_proto" which is not deducted and null by default. so, maybe the following patch in amd/srvr_nfs.c will make it more robusts to crashes: @@ -956,11 +956,11 @@ no_dns: * chosen here (right now it a

Bug#896446: dbgsym backtrace (am-utils: segfaulting error 4 in libc-2.27.so with kernels 4.+)

2018-04-25 Thread Christian Montanari
well, I did made a -dbgsym package... and caught the same symptomatic error, now, "...segfault at 0 ip 7f5ac1e570f4 sp 7ffea6a75848 error 4 in libc-2.27.so[7f5ac1d22000+1b1000] ..." and found it ememnates in "... find_nfs_srvr (mf=0x557ff0586020) at ../../amd/srvr_nfs.c:961 ..."

Bug#896446: am-utils: segfaulting error 4 in libc-2.27.so with kernels 4.+

2018-04-21 Thread Christian Montanari
Package: am-utils Version: 6.2+rc20130922-1 Severity: normal Tags: upstream the last few eons I get many of those... amd[24631]: segfault at 0 ip 7f2a7445dd96 sp 7ffd7760ddb8 error 4 in libc-2.27.so[7f2a74329000+1b1000] this frequent libc crash is not going away (ie. https://bugs.d

Bug#867207: xdmx: crashes after (TimerForce+0x10)

2017-07-09 Thread Christian Montanari
On Wed, 5 Jul 2017 10:06:52 +0900 =?UTF-8?Q?Michel_D=c3=a4nzer?= wrote: > On 05/07/17 03:16 AM, ptizoom wrote: > > Package: xdmx > > Version: 2:1.19.3-1 > > Severity: normal > > > > Dear Maintainer, > > > > I have nothing better to try xdmx, but hey, this package seem to be > > obsolete. > >

Bug#832405: tex-common: fmtutil failed to build pdftex/cont-en xetex/cont-en as cont-en.mkii missing

2016-11-24 Thread Christian Montanari
On Mon, 25 Jul 2016 10:49:06 +0200 =?UTF-8?B?UHJldcOfZSwgSGlsbWFy?= wrote: > On 25.07.2016 09:11, cp.montan...@tiscali.co.uk wrote: > > Hi, > > > this tex-common does not install on my system, > > here is the end of the fmtutil log...: > > > > "... > > Running mktexlsr. This may take some time.

Bug#832405: tex-common: fmtutil failed to build pdftex/cont-en xetex/cont-en as cont-en.mkii missing

2016-11-24 Thread Christian Montanari
On Mon, 25 Jul 2016 08:11:54 +0100 cp.montan...@tiscali.co.uk wrote: > Package: tex-common > Version: 6.05 > Severity: normal > > Dear Maintainer, > > this tex-common does not install on my system, > here is the end of the fmtutil log...: > > "... > Running mktexlsr. This may take some time... d

Bug#832405: tex-common: fmtutil failed to build pdftex/cont-en xetex/cont-en as cont-en.mkii missing

2016-11-24 Thread Christian Montanari
. -- --- Christian Montanari FYI the trace indicates... > > fmtutil: fmtutil is using the following fmtutil.cnf file for writing > > changes: > > fmtutil: /etc/texmf/web2c/fmtutil.cnf so this '/etc/texmf/web2c/fmtutil.cnf' used for "writing" results indeed, is non ex

Bug#832405: tex-common: fmtutil failed to build pdftex/cont-en xetex/cont-en as cont-en.mkii missing

2016-11-24 Thread Christian Montanari
On Mon, 25 Jul 2016 10:49:06 +0200 =?UTF-8?B?UHJldcOfZSwgSGlsbWFy?= wrote: > On 25.07.2016 09:11, cp.montan...@tiscali.co.uk wrote: > > Hi, > > > this tex-common does not install on my system, > > here is the end of the fmtutil log...: > > > > "... > > Running mktexlsr. This may take some time.