Package: jpilot Version: 1.8.0.1-1 Severity: wishlist
It seems that the only way to abort a hotsync after telling jpilot to begin one is to follow jpilot's instructions to kill a process by typing 'kill nnnn' on the command line. This seems pretty kludgy, even though it's straightforward enough via copy and paste; shouldn't jpilot have an option to do this automatically from within the application? -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.35-rc5-lizzie-00064-ga9f7f2e 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 jpilot depends on: ii libatk1.0-0 1.30.0-1 The ATK accessibility toolkit ii libc6 2.11.2-2 Embedded GNU C Library: Shared lib ii libcairo2 1.8.10-4 The Cairo 2D vector graphics libra ii libfontconfig1 2.8.0-2.1 generic font configuration library ii libfreetype6 2.4.0-2 FreeType 2 font engine, shared lib ii libglib2.0-0 2.24.1-1 The GLib library of C routines ii libgtk2.0-0 2.20.1-1 The GTK+ graphical user interface ii libpango1.0-0 1.28.1-1 Layout and rendering of internatio ii libpisock9 0.12.5-2 library for communicating with a P Versions of packages jpilot recommends: pn jpilot-plugins <none> (no description available) Versions of packages jpilot suggests: pn jpilot-backup <none> (no description available) -- 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