[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#301878: Just exits; does not appear to do anything



Package: xitalk
Version: 1.1.11-13
Severity: grave

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

anthony@bohr:tmp$ xitalk 
anthony@bohr:tmp$ 
anthony@bohr:tmp$ ps xa | grep xita
 5652 pts/21   S+     0:03 /usr/bin/python2.3 -S /usr/bin/reportbug xitalk
 5716 pts/21   S+     0:01 gvim -f -c :6 /tmp/reportbug-xitalk-20050328-5652-94dwXk
 5728 pts/22   S+     0:00 grep xita

It just exits; no messages, nothing.

anthony@bohr:tmp$ xitalk ; echo $?
0

No error code, either. I don't see anything in README.gz, README.Debian,
or the manpage saying whats going on.

- -- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (500, 'testing'), (130, 'unstable'), (120, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.10-bohr
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages xitalk depends on:
ii  bsdmainutils             6.0.17          collection of more utilities from 
ii  libc6                    2.3.2.ds1-20    GNU C Library: Shared libraries an
ii  libice6                  4.3.0.dfsg.1-10 Inter-Client Exchange library
ii  libsm6                   4.3.0.dfsg.1-10 X Window System Session Management
ii  libx11-6                 4.3.0.dfsg.1-10 X Window System protocol client li
ii  libxaw7                  4.3.0.dfsg.1-10 X Athena widget set library
ii  libxext6                 4.3.0.dfsg.1-10 X Window System miscellaneous exte
ii  libxmu6                  4.3.0.dfsg.1-10 X Window System miscellaneous util
ii  libxpm4                  4.3.0.dfsg.1-10 X pixmap library
ii  libxt6                   4.3.0.dfsg.1-10 X Toolkit Intrinsics
ii  xlibs                    4.3.0.dfsg.1-10 X Keyboard Extension (XKB) configu

- -- no debconf information

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFCSIO2+z+IwlXqWf4RAmoHAKCFJ/Sb9bRIE9e+ctdf911e8KtHewCfW8vU
Id78Ua/Gz2ouYwDfYliE+Ew=
=W7nV
-----END PGP SIGNATURE-----



Reply to: