Bug#500540: kdebase: automounting vfat (partialy) case sensitive due to utf8 is plain wrong and dangerous

> New version of "pmount" package was uploaded (and unblocked) recently. Sorry to say that, but upgrading to pmount 0.9.18 didn't fix the problem. > [EMAIL PROTECTED]:~$ pmount -V > 0.9.18 > [EMAIL PROTECTED]:~$ dmesg | tail > [64822.927396] sd 0:0:0:0: [sda] Write Protect is off > [64822.927402]

Bug#500540: automounting vfat as utf8

Hi Sune and thanks for taking up the issue. On Mon, Oct 06, 2008 at 07:38:15PM +0200, Sune Vuorela wrote: > > KDE uses the information from hal to decide what options to use when > mounting. > > On a vfat drive, hal gives the following: > hal-get-property --udi '/org/freedesktop/Hal/devices/volu

Bug#379610: (bacula-wxconsole: restore mode "dir" parsing error)

Seems to have been be patched upstream ... see http://bugs.bacula.org/bug_view_advanced_page.php?bug_id=338 I guess there's no point in hoping this will get fixed for stable. So you can probably close this bug. cheers -h -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of

Bug#379610: bacula-wxconsole: restore mode "dir" parsing error

Package: bacula-wxconsole Version: 1.36.2-2sarge1 In file-selection mode the parsing of "dir" output seems to assume fixed byte-position of filenames instead of word/field number. When switching to restore mode console shows the directory content like this. cwd is: / $ unmark * 218

Bug#379605: in file-selection mode bacula-console-wx issues ".dir" instead of "dir"

Package: bacula-console-wx Version: 1.38.9-10 Severity: important I'm trying to use the current testing/etch version of bacula-console-wx with a stable/sarge version of bacula-director. The bacula-director on sarge is version 1.36.2 (28 February 2005). So far everything seems to work. Only when