Voila. Unbuggered.
--
"Starting File Manager" windows open uncontrollably
https://bugs.launchpad.net/bugs/325973
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.ubun
Add the line:
AutostartCondition=GNOME /apps/nautilus/preferences/show_desktop
to /usr/share/applications/nautilus.desktop.
Then logout and login again.
--
"Starting File Manager" windows open uncontrollably
https://bugs.launchpad.net/bugs/325973
You received this bug notification because you
** Description changed:
I can't boot into 2.6.27-2 or -3 with my software raid setup. It's an
ASUS P5N-E SLI MoBo, and the disks look like this:
Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Public bug reported:
I can't boot into 2.6.27-2 or -3 with my software raid setup. It's an
ASUS P5N-E SLI MoBo, and the disks look like this:
Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier:
Confirming this problem still exists after today's kernel update
2.6.24-18-generic
--
dmraid not correctly detecting nforce raid
https://bugs.launchpad.net/bugs/136804
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs maili
Just to confirm, problem still exists in recently released 2.6.24-17
kernel.
Also, dmraid -ay occasionally returns:
"device-mapper: table 253:0: mirror: Device lookup failure"
at the command line on all failing kernels
--
dmraid not correctly detecting nforce raid
https://bugs.launchpad.net/bu
Good thinking, Batman - but it ain't that:
$ lsmod | grep dm
dm_crypt 15364 0
dm_mirror 24832 0
dm_mod 62660 2 dm_crypt,dm_mirror
Also, dmraid -tay returns:
$ sudo dmraid -tay
nvidia_acihdbbb: 0 976773166 mirror core 2 131072 nosync 2 /dev/sda 0 /d
I thought the UUID stuff was a red herring. Here's the output from
2.6.20-12, where everything works ok:
$ sudo dmraid -ay - -
WARN: locking /var/lock/dmraid/.lock
NOTICE: /dev/sda: asr discovering
NOTICE: /dev/sda: ddf1discovering
NOTICE: /dev/sda: hpt37x discovering
NOTICE: /dev
This has been driving me slightly nuts since Fiesty's release (and it's
persisted through Gutsy and doesn't seem to be fixed in Hardy beta's (up
to 2.6.24-16) either). And yes, I know I should have raised it as a bug
earlier, but I've just worked around it by booting into 2.6.20-12 which
was the la
It would appear that this bug still exists in kernel 2.6.20-14-generic
Apr 5 18:56:35 localhost kernel: [ 2880.464000] ata1.01: qc timeout (cmd 0xa0)
Apr 5 18:56:35 localhost kernel: [ 2880.464000] res
51/20:03:00:00:00/00:00:00:00:00/b0 Emask 0x5 (timeout)
Apr 5 18:56:42 localhost ke
Workaround is to kill the hald-addon-storage process
--
Hard disk I/O randomly freezes when hald is running and optical drive is empty
https://bugs.launchpad.net/bugs/84603
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu
11 matches
Mail list logo