Package: licq
Version: 1.3.2-6
Severity: minor
15:32:28: [ERR] Licq: Already running at pid 4793.
Kill process or remove /home/nemesis/.licq/licq.pid.
This is an annoyance because no error is reported in the GUI, so it appears
that licq is simply doing nothing. Even worse, there is no process 4793, so
the pidfile is obviously stale. licq should check for that. An even better
check would be to write /proc/self/cmdline also into the pidfile, and then see
if /proc/<pid>/cmdline matches that. Then even if a different process has
taken over the pid, licq can still start successfully.
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (990, 'testing')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-1-686-smp
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Versions of packages licq depends on:
ii libc6 2.3.6-13 GNU C Library: Shared libraries
ii libgcc1 1:4.1.0-4 GCC support library
ii libgpg-error0 1.2-1 library for common error values an
ii libgpgme11 1.1.2-2 GPGME - GnuPG Made Easy
ii libssl0.9.8 0.9.8b-2 SSL shared libraries
ii libstdc++6 4.1.0-4 The GNU Standard C++ Library v3
ii licq-plugin-qt [licq-plugin] 1.3.2-6 graphical user interface plug-in f
ii licq-plugin-rms [licq-plugin] 1.3.2-6 remote management server plug-in f
Versions of packages licq recommends:
ii sox 12.17.9-1 A universal sound sample translato
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
