Package: quassel-client
Version: 0.4.2-1
Severity: normal

Not sure if this is a feature already present and expected to work, but
quassel-client does not autoconnect to the remote core.

quassel-client is designed to run on a moving machine (laptop) and keep
the irc sessions always on. When the laptop disconnecets and reconnects,
quassel-client doesn't auto-connect to the core.

Ritesh

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (101, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.30-custom (SMP w/1 CPU core; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages quassel-client depends on:
ii  libc6                         2.9-12     GNU C Library: Shared libraries
ii  libgcc1                       1:4.4.0-5  GCC support library
ii  libqt4-dbus                   4:4.5.2-1  Qt 4 D-Bus module
ii  libqt4-network                4:4.5.2-1  Qt 4 network module
ii  libqt4-webkit                 4:4.5.2-1  Qt 4 WebKit module
ii  libqtcore4                    4:4.5.2-1  Qt 4 core module
ii  libqtgui4                     4:4.5.2-1  Qt 4 GUI module
ii  libstdc++6                    4.4.0-5    The GNU Standard C++ Library v3
ii  quassel-data                  0.4.2-1    distributed IRC client using a cen

Versions of packages quassel-client recommends:
pn  quassel-core                  <none>     (no description available)

quassel-client suggests no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to