[Bug 238954] Re: unable to paste passwords into seahorse passphrase windows
Hi, I just wanted to add that this behaviour is bugging me a lot as well. Using KeePassX for cross platform password db support with long random pass phrases for gpg keys is out of the question when you have to manually copy and paste. Even more so if you happen to use a lot of special chars and dead keys (accents) where you actually have to type an extra blank to make sure you don't get the wrong letter. Not to mention font problems when using chars like O vs. 0 or 1, l (small L) and I (capital i). I also do not understand, why keeping a pass phrase in memory indefinitely, as suggested by upstream, is considered more secure as storing it temporarily (default: 20 sec) in clipboard memory. For what it's worth, I will try and bring this to the seahorse maintainers attention. I understand that this bug will not be reopened, just wanted to add my opinion. Cheers Jens -- unable to paste passwords into seahorse passphrase windows https://bugs.launchpad.net/bugs/238954 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 156669] Re: SATA drive freezes when using LVM over dm-crypt
On Mon, 23 Feb 2009 05:07:24 - duanedesign duanedes...@gmail.com wrote: Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance. Thank you for the reminder. As far as I can tell, the bug has been fixed in all current versions of *buntu. Cheers Jens Prüfer -- SATA drive freezes when using LVM over dm-crypt https://bugs.launchpad.net/bugs/156669 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 135911] Re: [gutsy] request for Tex Gyre fonts to be added to texlive-fonts-extra
Dear Dr. Preining, Hello Norbert! First of all, thank you for keeping a debian package ready. While it is not exactly rocket science to add the fonts manually, it is a nicer and cleaner solution to do it the Debian way. While we are all patiently waiting for the license issues to be resolved, could you update your .deb package to a newer version? It looks like it has not been touched since October 2007. However, the newest release of the tex-gyre fonts is February 2008. Cheers Jens Prüfer -- [gutsy] request for Tex Gyre fonts to be added to texlive-fonts-extra https://bugs.launchpad.net/bugs/135911 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 156669] Re: SATA drive freezes when using LVM over dm-crypt
The problem *is* related to NCQ, however, I believe it is *not* the drive. I am running into the same problems on a different machine with a SAMSUNG SP2504C SATA drive. --- snip --- [0.00] Linux version 2.6.22-14-generic ([EMAIL PROTECTED]) (gcc version 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)) #1 SMP Sun Oct 14 23:05:12 GMT 2007 (Ubuntu 2.6.22-14.46-generic) ... [4.936000] sata_nv :00:08.0: version 3.4 [4.936000] sata_nv :00:08.0: Using ADMA mode ... [ 800.196000] ata1: timeout waiting for ADMA IDLE, stat=0x400 [ 800.196000] ata1: timeout waiting for ADMA LEGACY, stat=0x400 [ 800.196000] ata1.00: exception Emask 0x0 SAct 0x7 SErr 0x20 action 0x2 frozen [ 800.196000] ata1.00: cmd 61/00:00:1c:03:3c/04:00:1b:00:00/40 tag 0 cdb 0x0 data 524288 out [ 800.196000] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) [ 800.196000] ata1.00: cmd 61/00:08:1c:ff:3b/02:00:1b:00:00/40 tag 1 cdb 0x0 data 262144 out [ 800.196000] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) [ 800.196000] ata1.00: cmd 61/00:10:1c:01:3c/02:00:1b:00:00/40 tag 2 cdb 0x0 data 262144 out ... [ 918.972000] ata1: timeout waiting for ADMA IDLE, stat=0x400 [ 918.972000] ata1: timeout waiting for ADMA LEGACY, stat=0x400 [ 918.972000] ata1.00: NCQ disabled due to excessive errors [ 918.972000] ata1.00: exception Emask 0x0 SAct 0x1f SErr 0x0 action 0x2 frozen [ 918.972000] ata1.00: cmd 60/08:00:f4:75:14/00:00:1b:00:00/40 tag 0 cdb 0x0 data 4096 in [ 918.972000] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) [ 918.972000] ata1.00: cmd 61/08:08:bc:1e:fe/00:00:1a:00:00/40 tag 1 cdb 0x0 data 4096 out [ 918.972000] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) [ 918.972000] ata1.00: cmd 61/40:10:ac:1d:4a/00:00:1a:00:00/40 tag 2 cdb 0x0 data 32768 out [ 918.972000] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) ... [ 919.284000] ata1: soft resetting port [ 919.44] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 919.96] ata1.00: configured for UDMA/133 [ 919.96] ata1: EH complete [ 920.056000] sd 0:0:0:0: [sda] 488397168 512-byte hardware sectors (250059 MB) [ 920.056000] sd 0:0:0:0: [sda] Write Protect is off [ 920.056000] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [ 920.056000] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA ... and the drive is working again. The common denominator here is: both machines use the NForce4 chipset, both use the sata_nv driver and both are trying to use LVM over dm-crypt. I am of course not sure, but it is possible that there might be a bug combining sata_nv, NCQ and LVM mapped devices. I wish someone else would look into this issue. The drive does make funky noises during the error phase, but I am not sure if that is healthy at all. Cheers Jens -- SATA drive freezes when using LVM over dm-crypt https://bugs.launchpad.net/bugs/156669 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 156669] SATA drive freezes when using LVM over dm-crypt
Public bug reported: Hi, I can reproduce this bug on various kernels/systems (including Debian stable, Debian testing and Kubuntu 7.10) and I am a bit unsure, if this is a SATA driver, a dm-crypt devicemapper or a LVM problem. After initial booting and with complete (non-network) based installation of Kubuntu 7.10 drive access works normal. After a few minutes, the system freezes up completely, showing heaps of SATA errors in the logfile (see below). After a few extra rounds producing errors, the drive then reactivates and works normal for as long as I have been using the system (a few hours). As I said before, this behavior is reproducible over several kernel versions and Distributions. I am using a LVM over dm-crypt installation with the following layout: SCSI1 (0,0,0) #1 primary 67.1 GB ntfs #2 primary 510 MB ext2 /boot #3 primary 182.4 GB crypto (sda3_crypt) Encrypted Volume (sda3_crypt) 182.4 GB Linux device mapper #1 182.4 GB lvm LVM VG disk1, LV home 107.4 GB Linux device mapper #1 107.4 GBext2/home LVM VG disk1, LV swap 2.1 GB Linux device mapper #1 2.1GBswapswap LVM VG disk1, LV system 72.9 GB Linux device mapper #1 72.9 GBext2/ Error messages as reported by dmesg: [0.00] Linux version 2.6.22-14-generic ([EMAIL PROTECTED]) (gcc version 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)) ... cont. [ 22.606745] ata1: SATA max UDMA/133 cmd 0xf8860480 ctl 0xf88604a0 bmdma 0x0001d400 irq 18 [ 22.606748] ata2: SATA max UDMA/133 cmd 0xf8860580 ctl 0xf88605a0 bmdma 0x0001d408 irq 18 [ 23.071589] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 23.116317] ata1.00: ATA-7: ST3250620NS, 3.AEG, max UDMA/133 [ 23.116319] ata1.00: 488397168 sectors, multi 1: LBA48 NCQ (depth 31/32) [ 23.182879] ata1.00: configured for UDMA/133 [ 23.491089] ata2: SATA link down (SStatus 0 SControl 300) [ 23.491170] scsi 0:0:0:0: Direct-Access ATA ST3250620NS 3.AE PQ: 0 ANSI: 5 [ 23.491177] ata1: bounce limit 0x, segment boundary 0x, hw segs 61 ... cont. [ 23.499267] sd 0:0:0:0: [sda] 488397168 512-byte hardware sectors (250059 MB) [ 23.499277] sd 0:0:0:0: [sda] Write Protect is off [ 23.499279] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [ 23.499289] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 23.499322] sd 0:0:0:0: [sda] 488397168 512-byte hardware sectors (250059 MB) [ 23.499328] sd 0:0:0:0: [sda] Write Protect is off [ 23.499329] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [ 23.499337] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 23.499341] sda: sda1 sda2 sda3 [ 23.514090] sd 0:0:0:0: [sda] Attached SCSI disk [ 23.517291] sd 0:0:0:0: Attached scsi generic sg0 type 0 ... cont. [ 113.972000] ata1: EH in ADMA mode, notifier 0x0 notifier_error 0x0 gen_ctl 0x1501000 status 0x400 next cpb count 0x0 next cpb idx 0x0 [ 113.972000] ata1: CPB 1: ctl_flags 0x1f, resp_flags 0x2 [ 113.972000] ata1: CPB 2: ctl_flags 0x1f, resp_flags 0x2 [ 113.972000] ata1: CPB 3: ctl_flags 0x1f, resp_flags 0x2 [ 113.972000] ata1: CPB 4: ctl_flags 0x1f, resp_flags 0x2 [ 113.972000] ata1: timeout waiting for ADMA IDLE, stat=0x400 [ 113.972000] ata1: timeout waiting for ADMA LEGACY, stat=0x400 [ 113.972000] ata1.00: exception Emask 0x0 SAct 0x1e SErr 0x20 action 0x2 frozen [ 113.972000] ata1.00: cmd 61/00:08:b5:d1:28/02:00:17:00:00/40 tag 1 cdb 0x0 data 262144 out [ 113.972000] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) [ 113.972000] ata1.00: cmd 61/78:10:b5:d3:28/01:00:17:00:00/40 tag 2 cdb 0x0 data 192512 out [ 113.972000] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) [ 113.972000] ata1.00: cmd 61/08:18:a5:45:27/00:00:17:00:00/40 tag 3 cdb 0x0 data 4096 out [ 113.972000] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) [ 113.972000] ata1.00: cmd 60/10:20:15:4e:b9/00:00:1a:00:00/40 tag 4 cdb 0x0 data 8192 in [ 113.972000] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) [ 114.284000] ata1: soft resetting port [ 114.44] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 114.572000] ata1.00: configured for UDMA/133 [ 114.576000] ata1: EH complete [ 114.576000] sd 0:0:0:0: [sda] 488397168 512-byte hardware sectors (250059 MB) [ 114.576000] sd 0:0:0:0: [sda] Write Protect is off [ 114.576000] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [ 114.576000] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA ... cont. [ 233.248000] ata1: EH in ADMA mode, notifier 0x0 notifier_error 0x0 gen_ctl 0x1501000 status 0x400 next cpb count 0x4 next cpb idx 0x0 [ 233.248000] ata1: CPB 0: ctl_flags 0x1f, resp_flags 0x0 [ 233.248000] ata1: CPB 1: ctl_flags 0x1f, resp_flags 0x0 [ 233.248000] ata1: CPB 2: ctl_flags 0x1f,
[Bug 156669] Re: SATA drive freezes when using LVM over dm-crypt
** Description changed: Hi, I can reproduce this bug on various kernels/systems (including Debian stable, Debian testing and Kubuntu 7.10) and I am a bit unsure, if this is a SATA driver, a dm-crypt devicemapper or a LVM problem. After initial booting and with complete (non-network) based installation of Kubuntu 7.10 drive access works normal. After a few minutes, the system freezes up completely, showing heaps of SATA errors in the logfile (see below). After a few extra rounds producing errors, the drive then reactivates and works normal for as long as I have been using the system (a few hours). As I said before, this behavior is reproducible over several kernel versions and Distributions. I am using a LVM over dm-crypt installation with the following layout: SCSI1 (0,0,0) #1 primary 67.1 GB ntfs #2 primary 510 MB ext2 /boot #3 primary 182.4 GB crypto (sda3_crypt) Encrypted Volume (sda3_crypt) 182.4 GB Linux device mapper #1 182.4 GB lvm LVM VG disk1, LV home 107.4 GB Linux device mapper #1 107.4 GBext2/home LVM VG disk1, LV swap 2.1 GB Linux device mapper #1 2.1GBswapswap LVM VG disk1, LV system 72.9 GB Linux device mapper #1 72.9 GBext2/ Error messages as reported by dmesg: [0.00] Linux version 2.6.22-14-generic ([EMAIL PROTECTED]) (gcc version 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)) ... cont. [ 22.606745] ata1: SATA max UDMA/133 cmd 0xf8860480 ctl 0xf88604a0 bmdma 0x0001d400 irq 18 [ 22.606748] ata2: SATA max UDMA/133 cmd 0xf8860580 ctl 0xf88605a0 bmdma 0x0001d408 irq 18 [ 23.071589] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 23.116317] ata1.00: ATA-7: ST3250620NS, 3.AEG, max UDMA/133 [ 23.116319] ata1.00: 488397168 sectors, multi 1: LBA48 NCQ (depth 31/32) [ 23.182879] ata1.00: configured for UDMA/133 [ 23.491089] ata2: SATA link down (SStatus 0 SControl 300) [ 23.491170] scsi 0:0:0:0: Direct-Access ATA ST3250620NS 3.AE PQ: 0 ANSI: 5 [ 23.491177] ata1: bounce limit 0x, segment boundary 0x, hw segs 61 ... cont. [ 23.499267] sd 0:0:0:0: [sda] 488397168 512-byte hardware sectors (250059 MB) [ 23.499277] sd 0:0:0:0: [sda] Write Protect is off [ 23.499279] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [ 23.499289] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 23.499322] sd 0:0:0:0: [sda] 488397168 512-byte hardware sectors (250059 MB) [ 23.499328] sd 0:0:0:0: [sda] Write Protect is off [ 23.499329] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [ 23.499337] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 23.499341] sda: sda1 sda2 sda3 [ 23.514090] sd 0:0:0:0: [sda] Attached SCSI disk [ 23.517291] sd 0:0:0:0: Attached scsi generic sg0 type 0 ... cont. [ 113.972000] ata1: EH in ADMA mode, notifier 0x0 notifier_error 0x0 gen_ctl 0x1501000 status 0x400 next cpb count 0x0 next cpb idx 0x0 [ 113.972000] ata1: CPB 1: ctl_flags 0x1f, resp_flags 0x2 [ 113.972000] ata1: CPB 2: ctl_flags 0x1f, resp_flags 0x2 [ 113.972000] ata1: CPB 3: ctl_flags 0x1f, resp_flags 0x2 [ 113.972000] ata1: CPB 4: ctl_flags 0x1f, resp_flags 0x2 [ 113.972000] ata1: timeout waiting for ADMA IDLE, stat=0x400 [ 113.972000] ata1: timeout waiting for ADMA LEGACY, stat=0x400 [ 113.972000] ata1.00: exception Emask 0x0 SAct 0x1e SErr 0x20 action 0x2 frozen [ 113.972000] ata1.00: cmd 61/00:08:b5:d1:28/02:00:17:00:00/40 tag 1 cdb 0x0 data 262144 out [ 113.972000] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) [ 113.972000] ata1.00: cmd 61/78:10:b5:d3:28/01:00:17:00:00/40 tag 2 cdb 0x0 data 192512 out [ 113.972000] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) [ 113.972000] ata1.00: cmd 61/08:18:a5:45:27/00:00:17:00:00/40 tag 3 cdb 0x0 data 4096 out [ 113.972000] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) [ 113.972000] ata1.00: cmd 60/10:20:15:4e:b9/00:00:1a:00:00/40 tag 4 cdb 0x0 data 8192 in [ 113.972000] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) [ 114.284000] ata1: soft resetting port [ 114.44] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 114.572000] ata1.00: configured for UDMA/133 [ 114.576000] ata1: EH complete [ 114.576000] sd 0:0:0:0: [sda] 488397168 512-byte hardware sectors (250059 MB) [ 114.576000] sd 0:0:0:0: [sda] Write Protect is off [ 114.576000] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [ 114.576000] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA ... cont. [ 233.248000] ata1: EH in ADMA mode, notifier 0x0 notifier_error 0x0 gen_ctl 0x1501000 status 0x400 next cpb count 0x4 next cpb idx
[Bug 149193] Re: [Gutsy] Update-Manager cupsys update failed to install
*** This bug is a duplicate of bug 149106 *** https://bugs.launchpad.net/bugs/149106 I am also experiencing the same problem. Here is the complete apt-log: Preparing to replace cupsys 1.3.2-1ubuntu1 (using .../cupsys_1.3.2-1ubuntu4_i386.deb) ... Ignoring nonregistered document cupsys * Stopping Common Unix Printing System: cupsd [ OK ] Unpacking replacement cupsys ... pkg: error processing /var/cache/apt/archives/cupsys_1.3.2-1ubuntu4_i386.deb (--unpack): trying to overwrite `/usr/share/doc/libcupsys2/CREDITS.txt', which is also in package libcupsys2 dpkg-deb: subprocess paste killed by signal (Broken pipe) * Starting Common Unix Printing System: cupsd [ OK ] Errors were encountered while processing: /var/cache/apt/archives/cupsys_1.3.2-1ubuntu4_i386.deb There seems to be a deadlock between the libcupsys2 and cupsys packages. I'd give this bug a high priority, since it breaks further upgrades. Cheers Jens -- [Gutsy] Update-Manager cupsys update failed to install https://bugs.launchpad.net/bugs/149193 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
