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_track_set_feature' is not 
found...

where is this object hiding nowadays ?



"...
[105/105] Linking CXX executable bin/kpipewireheadlesstest
FAILED: bin/kpipewireheadlesstest 
: && /usr/bin/c++ -pipe -fno-operator-names -fno-exceptions
-Wall -Wextra -Wcast-align -Wchar-subscripts -Wformat-security -Wno-long-long 
-Wpointer-arith -Wundef -Wnon-virtual-dtor -Woverloaded-virtual
-Werror=return-type -Werror=init-self -Werror=undef -Wvla -Wdate-time 
-Wsuggest-override -Wlogical-op -pedantic -Wzero-as-null-pointer-constant 
-Wmissing-include-dirs -fdiagnostics-color=always -g -Wl,--enable-new-dtags 
tests/CMakeFiles/kpipewireheadlesstest.dir/kpipewireheadlesstest_autogen/mocs_compilation.cpp.o
 tests/CMakeFiles/kpipewireheadlesstest.dir/HeadlessTest.cpp.o 
tests/CMakeFiles/kpipewireheadlesstest.dir/xdp_dbus_screencast_interface.cpp.o 
tests/CMakeFiles/kpipewireheadlesstest.dir/xdp_dbus_remotedesktop_interface.cpp.o
 -o bin/kpipewireheadlesstest  
-Wl,-rpath,/usr/src/kde/bld/plasma/kpipewire/bin:/usr/local/kde/lib:/usr/local/kde/usr/lib/x86_64-linux-gnu
  lib/libPipeWireScreencastingTest.a  bin/libKPipeWireRecord.so.5.90.0  
/usr/lib/x86_64-linux-gnu/libxkbcommon.so  
/usr/local/kde/lib/libQt6WaylandClient.so.6.6.2  
/usr/local/kde/usr/lib/x86_64-linux-gnu/libwayland-client.so  
/usr/local/kde/lib/libQt6Gui.so.6.6.2  /usr/lib/x86_64-linux-gnu/libGLX.so  
/usr/lib/x86_64-linux-gnu/libOpenGL.so  
/usr/local/kde/usr/lib/x86_64-linux-gnu/libwayland-cursor.so  
bin/libKPipeWireDmaBuf.so.5.90.0  bin/libKPipeWire.so.5.90.0  
/usr/local/kde/usr/lib/x86_64-linux-gnu/libKF6CoreAddons.so.5.246.0  
/usr/local/kde/lib/libQt6DBus.so.6.6.2  /usr/local/kde/lib/libQt6Core.so.6.6.2  
-Wl,-rpath-link,/usr/local/kde/usr/lib/x86_64-linux-gnu && :
/usr/bin/ld: /lib/x86_64-linux-gnu/libavfilter.so.9: undefined reference to 
`ass_track_set_feature'
collect2: error: ld returned 1 exit status
ninja: build stopped: subcommand failed.
..."

-- "bin/libKPipeWireRecord.so.5.90.0" is linked with "PkgConfig::AVFilter", so 
this is why libavfilter.so.9 appears.

here the cmake  inset...:
"...
target_link_libraries(KPipeWireRecord PUBLIC KPipeWire
PRIVATE Qt::Core Qt::Gui KF6::CoreAddons KPipeWireDmaBuf
PkgConfig::AVCodec PkgConfig::AVUtil PkgConfig::AVFormat 
PkgConfig::AVFilter PkgConfig::GBM PkgConfig::SWScale
epoxy::epoxy Libdrm::Libdrm Qt::GuiPrivate PkgConfig::LIBVA 
PkgConfig::LIBVA-drm
)
.."


-- I did also a bringing  package libavfilter-extra9 (but I have the same 
problem with libavfilter9) :
aptitude install libavfilter-extra9-dbgsym libavfilter-dev libav-dev 
libavfilter-extra


-- I must be missing the "so" containing this ''ass_track_set_feature'' 
object
or a dependenci not right...?



thx for any help.





-- System Information:
Debian Release: trixie/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 
'stable-security'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), 
(500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 
'experimental-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.5.0-3-amd64 (SMP w/2 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_DIE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libavfilter-extra9 depends on:
ii  libass9  2:0.14.0-dmo1
ii  libavcodec-extra60 [libavcodec60]7:6.1-5
ii  libavformat-extra60 [libavformat60]  7:6.1-5
ii  libavutil58  7:6.1-5
ii  libbs2b0 3.1.0+dfsg-7
ii  libc62.37-12
ii  libflite12.2-6
ii  libfontconfig1   2.14.2-6
ii  libfreetype6 2.13.0+dfsg-1
ii  libfribidi0  1.0.13-3
ii  libharfbuzz0b8.0.1-1
ii  liblilv-0-0  0.24.22-1
ii  libmysofa1   1.3.2+dfsg-2
ii  libplacebo3386.338.1-2
ii  libpocketsphinx3 0.8+5prealpha+1-15
ii  libpostproc577:6.1-5
ii  librubberband2   3.3.0+dfsg-2
ii  libsphinxbase3   0.8+5prealpha+1-16
ii  libstdc++6   13.2.0-7
ii  libswresample4   7:6.1-5
ii  libswscale7  7:6.1-5
ii  libtesseract55.3.3-1
ii  libva2  

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, _srvr_list) {
 if (STREQ(host, fs->fs_host) &&
nfs_version == fs->fs_version &&
-   STREQ(nfs_proto, fs->fs_proto)) {
+   (!nfs_proto || !fs->fs_proto || STREQ(nfs_proto, fs->fs_proto))) {
   /*
* fill in the IP address -- this is only needed
* if there is a chance an IP address will change

this nfs_proto, unset,  is being copied back into the "fs->fs_proto" structure 
and loops again.

-- 



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 always uses datagram sockets).
*/
   ITER(fs, fserver, _srvr_list) {
 if (STREQ(host, fs->fs_host) &&
nfs_version == fs->fs_version &&
-   STREQ(nfs_proto, fs->fs_proto)) {
+   (!nfs_proto || STREQ(nfs_proto, fs->fs_proto))) {
   /*
* fill in the IP address -- this is only needed
* if there is a chance an IP address will change
* between mounts.
* Mike Mitchell, m...@unx.sas.com, 09/08/93


still this global nfs_srvr_list queue is not protected,
although there are portmaper callback pinging function at work
this am-utils package makes you shiver !


thx for reading this, and long live user-space services.

PTZ.


signature.asc
Description: PGP signature


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 ..."

aye,

this "...  _srvr_list ... " must have references to stale
objects related to the fact my RPC is timing out bad... ?

tbc.



please note,
I could not stop myself modifing the darn am-utils-6.2 master baseline
https://salsa.debian.org/debian/am-utils.git,  and in the
process with a few changes related to the yalm wrapper flex/bison scanners made 
thread safe,
and gave setuid(), getuid() a more POSIX implementations ...
but those seem unrelated as the core "should" be identical...
anyway this is my prerogative since not being a deb-guy!



Program received signal SIGSEGV, Segmentation fault.
__strcmp_ssse3 () at ../sysdeps/x86_64/multiarch/../strcmp.S:572
572 ../sysdeps/x86_64/multiarch/../strcmp.S: No such file or directory.
(gdb) bt
#0  __strcmp_ssse3 () at ../sysdeps/x86_64/multiarch/../strcmp.S:572
#1  0x557ff02d0ebe in find_nfs_srvr (mf=0x557ff0586020) at 
../../amd/srvr_nfs.c:961
#2  0x557ff02c70c1 in init_mntfs (remopts=0x557ff0560980 "rw", 
mopts=0x557ff0560a60 "rw", auto_opts=0x557ff0576220 
"fs:=${autodir}/${rhost}/root/${rfs}", info=0x557ff05612a0 "rotan:/", 
mp=0x557ff0560ca0 "/amd/rotan/root", mo=0x557ff0575ab0, ops=0x557ff04efa00 
, mf=0x557ff0586020) at ../../amd/mntfs.c:98
#3  alloc_mntfs (ops=0x557ff04efa00 , ops@entry=0x557ff0575ab0, 
mo=mo@entry=0x557ff0575ab0, mp=0x557ff0560ca0 "/amd/rotan/root", 
info=0x557ff05612a0 "rotan:/", 
auto_opts=auto_opts@entry=0x557ff0576220 
"fs:=${autodir}/${rhost}/root/${rfs}", mopts=0x557ff0560a60 "rw", 
remopts=0x557ff0560980 "rw") at ../../amd/mntfs.c:109
#4  0x557ff02c7514 in find_mntfs (ops=0x557ff0575ab0, 
mo=mo@entry=0x557ff0575ab0, mp=, info=, 
auto_opts=auto_opts@entry=0x557ff0576220 
"fs:=${autodir}/${rhost}/root/${rfs}", mopts=, 
remopts=) at ../../amd/mntfs.c:207
#5  0x557ff02bd0aa in amfs_lookup_one_location (new_mp=0x557ff0573c00, 
new_mp=0x557ff0573c00, mf=0x557ff0576cb0, mf=0x557ff0576cb0, 
pfname=0x557ff0560d60 "rotan", 
def_opts=0x557ff0576220 "fs:=${autodir}/${rhost}/root/${rfs}", 
ivec=0x557ff05763c0 "rhost:=${key};type:=host;rfs:=/") at 
../../amd/amfs_generic.c:301
#6  amfs_lookup_loc (new_mp=new_mp@entry=0x557ff0573c00, 
error_return=error_return@entry=0x7ffd8cc54ee4) at ../../amd/amfs_generic.c:477
#7  0x557ff02bd5b1 in amfs_generic_lookup_child (mp=0x557ff056c320, 
fname=, error_return=0x7ffd8cc54ee4, op=1) at 
../../amd/amfs_generic.c:1183
#8  0x557ff02c9e0b in nfsproc_lookup_2_svc (argp=argp@entry=0x7ffd8cc54f10, 
rqstp=rqstp@entry=0x7ffd8cc54fb0) at ../../amd/nfs_subr.c:233
#9  0x557ff02c7af8 in nfs_program_2 (rqstp=0x7ffd8cc54fb0, 
transp=0x557ff0588b90) at ../../amd/nfs_prot_svc.c:293
#10 0x7f7d23c22a11 in __GI_svc_getreq_common (fd=fd@entry=9) at svc.c:525
#11 0x7f7d23c22a71 in __GI_svc_getreqset 
(readfds=readfds@entry=0x7ffd8cc556e0) at svc.c:430
#12 0x557ff02c85ec in run_rpc () at ../../amd/nfs_start.c:289
#13 mount_automounter (ppid=) at ../../amd/nfs_start.c:452
#14 0x557ff02b7e54 in main (argc=, argv=) at 
../../amd/amd.c:561
(



...
25/04/2018 07:44kaolo   amd[27726]  find_nfs_srvr: force NFS 
version to 3
25/04/2018 07:44kaolo   amd[27726]  check_pmap_up: failed to 
contact portmapper on host "rotan.ptizoom.co.uk": RPC: Timed out
25/04/2018 07:44kaolo   amd[27726]  portmapper service not running 
on rotan.ptizoom.co.uk
25/04/2018 07:44kaolo   amd[27726]  NFS service not running on 
rotan.ptizoom.co.uk
25/04/2018 07:44kaolo   amd[27726]  rotan:/homes/roland restarted 
fstype nfs on /homes/roland, flags 0x9
25/04/2018 07:44kaolo   amd[27726]  /usr/share/am-utils/amd.net 
referenced fstype toplvl on /net
25/04/2018 07:44kaolo   amd[27726]  /net set to never timeout
25/04/2018 07:44kaolo   amd[27726]  amd.home referenced fstype 
toplvl on /home
25/04/2018 07:44kaolo   amd[27726]  /home set to never timeout
25/04/2018 07:44kaolo   amd[27726]  file server 
rotan.ptizoom.co.uk, type nfs, state starts down
25/04/2018 07:44kaolo   amd[27726]  No fs type specified (key = 
"/defaults", map = ""root"")
25/04/2018 07:44kaolo   amd[27726]  find_nfs_srvr: force NFS 
version to 3
25/04/2018 07:44kaolo   amd[27726]  fileserver rotan.ptizoom.co.uk 
is already hung - not running NFS proto/version discovery
25/04/2018 07:44kaolo   amd[27726]  /etc/am-utils/amd.homes 
referenced fstype toplvl on /homes/kaolo
25/04/2018 07:44kaolo   amd[27726]  /homes/kaolo set to never 
timeout
25/04/2018 07:44kaolo   amd[27726]  file server 
rotan.ptizoom.co.uk, type nfs, state is up
25/04/2018 07:44 

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.debian.org/cgi-bin/bugreport.cgi?bug=727770
 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762071
);


but yet I am getting closer to pinpoint the bugger,  and here is a gdb 
backtrace:

Thread 1 "amd" received signal SIGSEGV, Segmentation fault.
__strcmp_ssse3 () at ../sysdeps/x86_64/multiarch/../strcmp.S:173
173 ../sysdeps/x86_64/multiarch/../strcmp.S: No such file or directory.
(gdb) bt
#0  __strcmp_ssse3 () at ../sysdeps/x86_64/multiarch/../strcmp.S:173
#1  0x004193ad in ?? ()
#2  0x00412a0c in ?? ()
#3  0x00412e2c in ?? ()
#4  0x00409137 in ?? ()
#5  0x00409878 in ?? ()
#6  0x00414c9e in ?? ()
#7  0x00413619 in ?? ()
#8  0x7f776127ea11 in __GI_svc_getreq_common (fd=fd@entry=5) at svc.c:525
#9  0x7f776127ea71 in __GI_svc_getreqset (readfds=) at 
svc.c:430
#10 0x00413e75 in ?? ()
#11 0x00405928 in ?? ()
#12 0x7f7761178a87 in __libc_start_main (main=0x405460, argc=5, 
argv=0x7ffd56495b78, init=, fini=, 
rtld_fini=, 
stack_end=0x7ffd56495b68) at ../csu/libc-start.c:310
#13 0x00405b06 in ?? ()



its frequency of occurence is hugely related when remote server machine (which 
is running NIS+NFS3 or 4? +RPC)
is not servicing RPC port-mapper (by processing this and other things) :
like...

13/04/2018 11:30loaka   amd[2627]   . is "${opts}"
13/04/2018 11:30loaka   amd[2627]   No fs type specified (key = 
"/defaults", map = ""root"")
13/04/2018 11:30loaka   amd[2627]   did not match defaults for 
"fs:=${autodir}/${rhost}/root/${rfs}"
13/04/2018 11:30loaka   amd[2627]   Expansion of 
"rhost:=${key};type:=host;rfs:=/"...
13/04/2018 11:30loaka   amd[2627]   . is 
"rhost:=rotan;type:=host;rfs:=/"
13/04/2018 11:30loaka   amd[2627]   Expansion of "/"...
13/04/2018 11:30loaka   amd[2627]   . is "/"
13/04/2018 11:30loaka   amd[2627]   . is "/amd/rotan/root/"
13/04/2018 11:30loaka   amd[2627]   NFS: mounting remote server 
"rotan", remote fs "/" on "/amd/rotan/root"
13/04/2018 11:30loaka   amd[2627]   Locating mntfs reference to 
(/amd/rotan/root,rotan:/)
13/04/2018 11:30loaka   amd[2627]   find_nfs_srvr: force NFS 
version to 3
13/04/2018 11:31loaka   amd[2627]   check_pmap_up: failed to 
contact portmapper on host "rotan.co.co": RPC: Timed out
13/04/2018 11:31loaka   amd[2627]   portmapper service not running 
on rotan.co.co
13/04/2018 11:31loaka   amd[2627]   NFS service not running on 
rotan.co.co
13/04/2018 11:31loaka   amd[2627]   find_nfs_srvr: using port 2049 
for nfs on rotan.co.co
...crash

it is a matter of trying to get an un-stripped version of amd now, and expose 
the nasty. 

but I also spotted some interresting improvement work on the original master...:

"
Author: zoulasc   2016-03-31 19:56:53
Committer: zoulasc   2016-03-31 19:56:53
Parent: c35699a16c2fd6f30be6ad7bee81a3bc0ee51828 (Today's RPC ping change.)
Child:  d324d2d30c49ac737fb147f0817881a35946b03d (Today's change)
Fix SEGV on amq entries that print times.
"

which could be beneficiary to incorporate ?

Thanks.

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 
'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.15.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages am-utils depends on:
ii  debconf1.5.66
ii  debianutils4.8.4
ii  libamu46.2+rc20130922-1
ii  libc6  2.27-2
ii  libgdbm3   1.8.3-14
ii  libhesiod0 3.2.1-3+b1
ii  libldap-2.4-2  2.4.45+dfsg-1
ii  libwrap0   7.6.q-27
ii  rpcbind [portmap]  0.2.3-0.6
ii  ucf3.0038

am-utils recommends no packages.

Versions of packages am-utils suggests:
ii  am-utils-doc  6.2+rc20110530-3.2
ii  nis   3.17.1-1+b2

-- Configuration Files:
/etc/am-utils/amd.conf changed [not included]
/etc/init.d/am-utils changed [not included]

-- no debconf information



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.
> > 
> > here I have produced 2 setups with same sort of crash...
> > 
> > 
> > -on a master machine in an kde desktop I create an Xnested window: 
> > 
> >  Xnest :14 &
> >  
> > -then on master still same kdeterminal I run:
> >  
> >   startx -- /usr/bin/Xdmx :10 -display :14
> > 
> > which crashes with ...
> >  (II) dmx: Generation: 1
> >  (II) dmx: DMX version:1.2.20070424 (DMX Project)
> >  (II) dmx: DMX Build OS:   Linux 3.16.0-4-amd64 x86_64 (Debian)
> >  (II) dmx: DMX Build Compiler: gcc 6.3.0
> >  (II) dmx: DMX Execution OS:   Linux 4.9.0-3-amd64 #1 SMP Debian 4.9.25-1 
> > (2017-05-02)
> >  (II) dmx: DMX Execution Host: master
> >  (II) dmx: MAXSCREENS: 16
> >  (II) dmx: Using configuration from command line
> >  (II) dmx: Added :14 at 0 0
> >  (II) dmx[o0/:14]: Name of display: :14
> >  (II) dmx[o0/:14]: Version number:  11.0
> >  (II) dmx[o0/:14]: Vendor string:   The X.Org Foundation
> >  (II) dmx[o0/:14]: Vendor release:  11903000
> >  (II) dmx[o0/:14]: Dimensions:  320x200 pixels
> >  (II) dmx[o0/:14]: 2 depths on screen 0:  1,24
> >  (II) dmx[o0/:14]: Depth of root window:  24 planes (24)
> >  (II) dmx[o0/:14]: Number of colormaps:   1 min, 1 max
> >  (II) dmx[o0/:14]: Options: backing-store no, save-unders no
> >  (II) dmx[o0/:14]: Window Manager running: no
> >  (II) dmx[o0/:14]: 320x200+0+0 on 320x200 at depth=24, bpp=32
> >  (II) dmx[o0/:14]: 0x20 TrueColor   24b 11b/rgb 256 0xff 0xff00 0x00ff *
> >  (II) dmx[o0/:14]: 0x21 DirectColor 24b 11b/rgb 256 0xff 0xff00 0x00ff
> >  (II) dmx[o0/:14]: DPMS not supported
> >  (EE) 
> >  (EE) Backtrace:
> >  (EE) 0: /usr/bin/Xdmx (xorg_backtrace+0x4a) [0x5619e528402a]
> >  (EE) 1: /usr/bin/Xdmx (0x5619e5118000+0x16fdd9) [0x5619e5287dd9]
> >  (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7ff65bb7+0x110c0) 
> > [0x7ff65bb810c0]
> >  (EE) 3: /usr/bin/Xdmx (TimerForce+0x10) [0x5619e5281ad0]
> >  (EE) 4: /usr/bin/Xdmx (0x5619e5118000+0x41be1) [0x5619e5159be1]
> >  (EE) 5: /usr/bin/Xdmx (0x5619e5118000+0x337a5) [0x5619e514b7a5]
> >  (EE) 6: /usr/bin/Xdmx (0x5619e5118000+0x40b07) [0x5619e5158b07]
> >  (EE) 7: /usr/bin/Xdmx (0x5619e5118000+0x40f75) [0x5619e5158f75]
> >  (EE) 8: /usr/bin/Xdmx (AddScreen+0xd7) [0x5619e524d787]
> >  (EE) 9: /usr/bin/Xdmx (InitOutput+0x40f) [0x5619e51534df]
> >  (EE) 10: /usr/bin/Xdmx (0x5619e5118000+0x1392e6) [0x5619e52512e6]
> >  (EE) 11: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf1) 
> > [0x7ff65b7f12b1]
> >  (EE) 12: /usr/bin/Xdmx (_start+0x2a) [0x5619e51471aa]
> >  (EE) 



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... done.
> > Running updmap-sys. This may take some time... done.
> > Running mktexlsr /var/lib/texmf ... done.
> > Building format(s) --all.
> > This may take some time...
> 
> 
> And this is the head:
> 
> > --- fmtutil full log...:
> >
> > *** /tmp/fmtutil.5xBG5aqo
> > fmtutil: fmtutil is using the following fmtutil.cnf files (in precedence 
> > order):
> > fmtutil:   /var/lib/texmf/web2c/fmtutil.cnf
> > fmtutil:   /usr/share/texmf/web2c/fmtutil.cnf
> > fmtutil:   /usr/share/texlive/texmf-dist/web2c/fmtutil.cnf
> > fmtutil: fmtutil is using the following fmtutil.cnf file for writing 
> > changes:
> > fmtutil:   /etc/texmf/web2c/fmtutil.cnf
> >
> That file /etc/texmf/web2c/fmtutil.cnf is not delivered w/ Debian, 
> instead normally the files in /var are used. I guess that file contains 
> a reference to the context formats, although context is not installed.
> 
> Try two things:
> 1. Does installing context solves your problem?
> 2. Please send a copy of the file /etc/texmf/web2c/fmtutil.cnf.
> 
> Hilmar
> -- 
> http://www.hilmar-preusse.de.vu/   #206401 http://counter.li.org
> 
> 



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... done.
> Running updmap-sys. This may take some time... done.
> Running mktexlsr /var/lib/texmf ... done.
> Building format(s) --all.
>   This may take some time... 
> fmtutil failed. Output has been stored in
> /tmp/fmtutil.5xBG5aqo
> Please include this file if you report a bug.
> "..."
> font\OMS/cmsy/m/n/5=cmsy5
> \font\OMS/cmsy/m/n/7=cmsy7
> \font\OMS/cmsy/m/n/10=cmsy10
> 14 preloaded fonts
> warning  (pdf backend): no pages of output.
> Transcript written on lualatex.log.
> fmtutil [INFO]: /var/lib/texmf/web2c/luatex/lualatex.fmt installed.
> fmtutil [WARNING]: inifile cont-en.mkii for cont-en/pdftex not found.
> fmtutil [WARNING]: inifile cont-en.mkii for cont-en/xetex not found.
> fmtutil [INFO]: Disabled formats: 3
> fmtutil [INFO]: Successfully rebuilt formats: 19
> fmtutil [INFO]: Failed to build: 2 (pdftex/cont-en xetex/cont-en)
> fmtutil [INFO]: Total formats: 24
> fmtutil [INFO]: exiting with status 2
> ..."
> 
> I wonder if this is the right problem? and how to generate this  
> "cont-en.mkii" file?
> 
> 
> PTZ.
> 
> 
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 4.6.0-1-amd64 (SMP w/2 CPU cores)
> Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: unable to detect
> 
> Versions of packages tex-common depends on:
> ii  dpkg  1.18.9
> ii  ucf   3.0036
> 
> tex-common recommends no packages.
> 
> Versions of packages tex-common suggests:



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
Hi Hilmar, thanks for pointing out this side of the problem.

I removed /var/lib/texmf/web2c/fmtutil.cnf and it resolved the issue.

altogether my /etc/texmf needs TLC, I have a lot of

remains from post year 2K!... I will cruft it.

-- 
--- 
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 existent on my system.

but found in the /var/lib/texmf/web2c/fmtutil.cnf:"...
# ## From file: /etc/texmf/fmt.d/10texlive-base.cnf
# 10texlive-base.cnf
# You can change/add entries to this file and changes will be preserved
# over upgrades, even if you have removed the main package prior
# (not if you purged it). You should leave the following pseudo comment
# present in the file!
# -_- DebPkgProvidedMaps -_-
# 
luatex luatex language.def,language.dat.lua luatex.ini
tex tex - tex.ini
pdfetex pdftex language.def -translate-file=cp227.tcx *pdfetex.ini
mf mf-nowin - -translate-file=cp227.tcx mf.ini
dviluatex luatex language.def,language.dat.lua dviluatex.ini
pdftex pdftex language.def -translate-file=cp227.tcx *pdfetex.ini
etex pdftex language.def -translate-file=cp227.tcx *etex.ini
#! luajittex luajittex language.def,language.dat.lua luatex.ini
# End of file: /etc/texmf/fmt.d/10texlive-base.cnf
..."

which is wrong since '/etc/texmf/fmt.d' disappeared from "my"
deb-system!

other relevant fmtutil.cnf are then from ...

texlive-base: /usr/share/texlive/texmf-dist/web2c/fmtutil.cnf
texlive-base: /usr/share/texmf/web2c/fmtutil.cnf

/usr/share/texlive/texmf-dist/web2c/fmtutil.cnf:"...
### This file was automatically generated by update-fmtutil.
#
# Any local change will be overwritten. Please see the documentation
# of updmap on how to override things from here.
#
###
#! mflua mflua-nowin - mf.ini
dvilualatex luatex language.dat,language.dat.lua dvilualatex.ini
latex pdftex language.dat -translate-file=cp227.tcx *latex.ini
#! luajitlatex luajittex language.dat,language.dat.lua lualatex.ini
lualatex luatex language.dat,language.dat.lua lualatex.ini
mptopdf pdftex - -translate-file=cp227.tcx mptopdf.tex
pdflatex pdftex language.dat -translate-file=cp227.tcx *pdflatex.ini
xelatex xetex language.dat -etex xelatex.ini
xetex xetex language.def -etex xetex.ini
amstex pdftex - -translate-file=cp227.tcx *amstex.ini
dviluatex luatex language.def,language.dat.lua dviluatex.ini
etex pdftex language.def -translate-file=cp227.tcx *etex.ini
#! luajittex luajittex language.def,language.dat.lua luatex.ini
luatex luatex language.def,language.dat.lua luatex.ini
mf mf-nowin - -translate-file=cp227.tcx mf.ini
pdfetex pdftex language.def -translate-file=cp227.tcx *pdfetex.ini
pdftex pdftex language.def -translate-file=cp227.tcx *pdfetex.ini
tex tex - tex.ini
jadetex pdftex language.dat *jadetex.ini
pdfjadetex pdftex language.dat *pdfjadetex.ini
pdfxmltex pdftex language.dat *pdfxmltex.ini
xmltex pdftex language.dat *xmltex.ini
..."

On Mon, Jul 25, 2016 at 10:49:06AM +0200, Preuße, Hilmar 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... done.
> > Running updmap-sys. This may take some time... done.
> > Running mktexlsr /var/lib/texmf ... done.
> > Building format(s) --all.
> > This may take some time...
> 
> 
> And this is the head:
> 
> > --- fmtutil full log...:
> > 
> > *** /tmp/fmtutil.5xBG5aqo
> > fmtutil: fmtutil is using the following fmtutil.cnf files (in precedence 
> > order):
> > fmtutil:   /var/lib/texmf/web2c/fmtutil.cnf
> > fmtutil:   /usr/share/texmf/web2c/fmtutil.cnf
> > fmtutil:   /usr/share/texlive/texmf-dist/web2c/fmtutil.cnf
> > fmtutil: fmtutil is using the following fmtutil.cnf file for writing 
> > changes:
> > fmtutil:   /etc/texmf/web2c/fmtutil.cnf
> > 
> That file /etc/texmf/web2c/fmtutil.cnf is not delivered w/ Debian, instead
> normally the files in /var are used. I guess that file contains a reference
> to the context formats, although context is not installed.
> 
> Try two things:
> 1. Does installing context solves your problem?
> 2. Please send a copy of the file /etc/texmf/web2c/fmtutil.cnf.
> 
> Hilmar



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... done.
> > Running updmap-sys. This may take some time... done.
> > Running mktexlsr /var/lib/texmf ... done.
> > Building format(s) --all.
> > This may take some time...
> 
> 
> And this is the head:
> 
> > --- fmtutil full log...:
> >
> > *** /tmp/fmtutil.5xBG5aqo
> > fmtutil: fmtutil is using the following fmtutil.cnf files (in precedence 
> > order):
> > fmtutil:   /var/lib/texmf/web2c/fmtutil.cnf
> > fmtutil:   /usr/share/texmf/web2c/fmtutil.cnf
> > fmtutil:   /usr/share/texlive/texmf-dist/web2c/fmtutil.cnf
> > fmtutil: fmtutil is using the following fmtutil.cnf file for writing 
> > changes:
> > fmtutil:   /etc/texmf/web2c/fmtutil.cnf
> >
> That file /etc/texmf/web2c/fmtutil.cnf is not delivered w/ Debian, 
> instead normally the files in /var are used. I guess that file contains 
> a reference to the context formats, although context is not installed.
> 
> Try two things:
> 1. Does installing context solves your problem?
> 2. Please send a copy of the file /etc/texmf/web2c/fmtutil.cnf.
> 
> Hilmar
> -- 
> http://www.hilmar-preusse.de.vu/   #206401 http://counter.li.org
> 
>