Package: libpisock9
Version: 0.12.3-4+b1
Severity: important

libpisock9 seems to assume that visor module should no longer be loaded,
and instead of using its devices /dev/ttyUSB* one should now sync over
usb:.

However, as explained in #459500, it won't work for my Sony CLiƩ over
usb:

Thus, I think that the module shouldn't be blacklisted in
/etc/modprobe.d/libpisock9, allowing the autoloading of visor once
trying to sync, which renders /dev/ttyUSB* devices usable, as was
previously.

Hope this regression can be fixed.

Best regards,

P.S.: Similar report in Ubuntu :
https://bugs.launchpad.net/ubuntu/+source/gnome-pilot/+bug/108512 


-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.24-1-686 (SMP w/1 CPU core)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages libpisock9 depends on:
ii  libbluetooth2                3.30-1      Library to use the BlueZ Linux Blu
ii  libc6                        2.7-10      GNU C Library: Shared libraries
ii  libusb-0.1-4                 2:0.1.12-11 userspace USB programming library

libpisock9 recommends no packages.

-- no debconf information



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to