Giuseppe Sacco <[EMAIL PROTECTED]> wrote: Hi,
> is there any news on this bugs? I wonder if it could be possibile to > activate pthread to solve this problem. Sadly no, not much is happening on this front. Activating pthread is guaranteed to have side effects on the frontends, and such side effects won't be detected and fixed in time for the release, I'm afraid. I can't do that. I have the best part of a patch in the works to get back the device path and use that, fortunately this is only needed on Unix-like platforms, and I can certainly cover Linux & FreeBSD without any issue as far as Debian is concerned. I need to get back at that patch, not that I like it very much as it's quite a hack (unfortunately libusb doesn't keep track of the device node it's used, so it's not possible to get it back from libusb). JB. -- Julien BLACHE <[EMAIL PROTECTED]> | Debian, because code matters more Debian & GNU/Linux Developer | <http://www.debian.org> Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
