I do not know, as the system in question is still running Jaunty. I
can upgrade in the near future and respond.
On 7/30/2010 1:56 PM, Fabio Marconi wrote:
Thank you for taking the time to report this bug and helping to make Ubuntu
better.
Is this bug reproducible with the latest Lucid
When I upgraded to Karmic, I had to rebuild ffmpeg from source with aac
support. Ever since, it doesn't work correctly. The sound quality is
significantly degraded when encoding wav to aac, even on audio that
previously worked fine with the exact same settings.
So something is definitely wrong
This bug bites me all the time. Autofsck has another problem that's
even worse, though, so I had to remove it: If Autofsck prompts that a
disk needs checking, and I select OK on reboot, the system comes back
up, checks the disks, then shuts down!! I'd rather sit through the disk
checking with no
*** This bug is a duplicate of bug 65683 ***
https://bugs.launchpad.net/bugs/65683
Even though I'm hearing that this isn't a bug, but moreover a feature
that was intentionally removed, it's still an issue in Jaunty, and this
functionality never should have been removed. Also, please note
Public bug reported:
If you reboot and Autofsck prompts to tell you an fsck is needed, if you
ignore or click cancel, all is well... computer reboots, no fsck is run.
IF you click OK, all appears to work fine at first... the computer
reboots, fsck starts. But then when it's complete, the
To recreate the problem that I am seeing, you MUST use a password-
protected private key. Mine is 4096-bit RSA, but I've done a bit of
searching and see this is happening for users with 1024 and 2048 bit RSA
keys as well.
--
ssh are using ssh-userauth but ignores private key
To recreate the problem that I am seeing, you MUST use a password-
protected private key. Mine is 4096-bit RSA, but I've done a bit of
searching and see this is happening for users with 1024 and 2048 bit RSA
keys as well.
--
ssh are using ssh-userauth but ignores private key
@ Robert Ancell :
Curious, was this RSA key you used password-protected? Because I see the same
results as you saw with a non-protected key, but this problem still persists
with all users on my 9.04 system with a protected key.
--
ssh are using ssh-userauth but ignores private key
My experiences are as follows:
Ubuntu 9.04
Logged into GNOME as a user
copy existing id_rsa file to ~/.ssh/ and do a chmod 700 on it.
(Keyfile being used here is 4096 bit RSA)
open terminal and issue the following:
$ ssh-add
Returns: Enter passphrase for /home/me/.ssh/id_rsa: (or something to that
My experiences are as follows:
Ubuntu 9.04
Logged into GNOME as a user
copy existing id_rsa file to ~/.ssh/ and do a chmod 700 on it.
(Keyfile being used here is 4096 bit RSA)
open terminal and issue the following:
$ ssh-add
Returns: Enter passphrase for /home/me/.ssh/id_rsa: (or something to that
*** This bug is a duplicate of bug 348126 ***
https://bugs.launchpad.net/bugs/348126
Just upgraded to 9.04. Same problem here.
--
ubuntu 9.04 beta: ssh-agent doesn't work
https://bugs.launchpad.net/bugs/353759
You received this bug notification because you are a member of Ubuntu
Server
*** This bug is a duplicate of bug 348126 ***
https://bugs.launchpad.net/bugs/348126
Just upgraded to 9.04. Same problem here.
--
ubuntu 9.04 beta: ssh-agent doesn't work
https://bugs.launchpad.net/bugs/353759
You received this bug notification because you are a member of Ubuntu
Bugs,
So it would appear that this is, in fact a hardware issue (at least in
my case). Like I said, my mem, mobo, proc, and HDD's all were good.
The one thing I never considered: power supply.
It would appear that one of my drives was consistently receiving too
little power. It just occured to me out
So it would appear that this is, in fact a hardware issue (at least in
my case). Like I said, my mem, mobo, proc, and HDD's all were good.
The one thing I never considered: power supply.
It would appear that one of my drives was consistently receiving too
little power. It just occured to me out
So it would appear that this is, in fact a hardware issue (at least in
my case). Like I said, my mem, mobo, proc, and HDD's all were good.
The one thing I never considered: power supply.
It would appear that one of my drives was consistently receiving too
little power. It just occured to me out
I've read through this and countless other posts about this issue (which
I am also experiencing). It truly does render the computer useless.
The only big thing that jumps out at me in this thread is that everyone
is mentioning problems with their CD/DVD drives, and upgrading firmware,
etc.
I've seen this problem in Debian Etch and Lenny, as well as Ubuntu
Intrepid. All were running RAID1 with mdadm.
I can give more details. Once it starts, it's hard to get rid of.
Reboots, mdadm (remove, zero superblock, then add), fsck don't help.
Compatibility mode, configuring in BIOS... no
also I left some other details on my post here:
http://ubuntuforums.org/showthread.php?p=6358980
--
Jmicron AHCI controller probs...
https://bugs.launchpad.net/bugs/198871
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Also I didn't think about it until reading through this thread, but it
seems to most often happen after I try to do a large file copy (over
about 1GB) or after several days of system uptime. I would say that one
of those two situations occur just prior to me seeing this problem
almost every time.
I've seen this problem in Debian Etch and Lenny, as well as Ubuntu
Intrepid. All were running RAID1 with mdadm.
I can give more details. Once it starts, it's hard to get rid of.
Reboots, mdadm (remove, zero superblock, then add), fsck don't help.
Compatibility mode, configuring in BIOS... no
20 matches
Mail list logo
