Bug#769826: Acknowledgement (wodim: burning audio disc with duplicate audio tracks fails, creates unusable disc)

2014-11-16 Thread Tim Walberg
Original report erroneously stated that this has not been verified on "lenny/stable" - that should have been "wheezy/stable". -- twalb...@gmail.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.or

Bug#769826: wodim: burning audio disc with duplicate audio tracks fails, creates unusable disc

2014-11-16 Thread Tim Walberg
Package: wodim Version: 9:1.1.11-1 Severity: normal Attempting to create an audio disc that uses the same input file for more than one track fails and creates a bad disc. However, copying that input file and burning essentially the same disc, works as expected. It appears that wodim attempts to b

Bug#527867: cpio: broken option --owner (-R)

2009-05-08 Thread Tim Walberg
Package: cpio Version: 2.9-13 Severity: normal Using cpio as root to assign new ownership to files fails with "invalid user" error message. This is repeatable with either "-R ..." or "--owner=...", and with any of "user", "user:group", "user:", ":group" syntax. Example: # cd /tmp # touch x

Bug#517553: further info

2009-02-28 Thread Tim Walberg
Here's a dump of the first sector of the device in question. It's possible this issue is due to bug 473135, but I don't know which bits in the superblock to look at to verify that. 58 46 53 42 00 00 10 00 00 00 00 00 00 3f 69 f0 XFSB.?i. 0010 00 00 00 00 00 00 00 00 00 00 0

Bug#517553: further info

2009-02-28 Thread Tim Walberg
0 mmap(NULL, 2367488, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xf7a76000 mmap(NULL, 2367488, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xf7834000 close(3)= 0 _llseek(4, 0, [0], SEEK_SET)= 0 read(4, "XFSB\0\0\20\0\0\

Bug#517553: xfsprogs: xfs_db on sparc64 fails immediately with "Bus error"

2009-02-28 Thread Tim Walberg
Package: xfsprogs Version: 2.9.8-1lenny1 Severity: important Running xfs_db on a sparc64 system fails immediately with "Bus error". Probably either an endinness issue or a 32-bit userland vs 64-bit kernel issue. sparcy:~# xfs_db -r /dev/md0 Bus error sparcy:~# -- System Informatio