File Dialog HD Partition "Sort Order" randomizes on every boot

[I'M YourOnly.One 🔏]

Binary package hint: nautilus

I setup my fstab to mount partition in this order: "C-D-F-G". (Using UUID.)
When I open Nautilus itself, it shows up as "C-D-F-G", which is correct.

But when I "Open" or "Save" a file, and the File Dialog shows up, the Sort Order is different, example: D-C-G-F.
After a reboot, it may become "D-G-F-C"; or "D-F-C-G"; and so on.

Partitions C and D are SATA HDD.
Partitions F and G are PATA HDD.

My BIOS is setup to load my SATA HDD first.
But Karmic doesn't follow my BIOS setup, instead it follows the "cable" setup which is "PATA" first, then "SATA".

I attached my fstab here as well as 3 screenshots.

ProblemType: Bug
Architecture: amd64
Date: Sat Oct 17 23:33:06 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: nvidia
Package: nautilus 1:2.28.0-0ubuntu7
ProcEnviron:
 LANG=en_PH.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: nautilus
Uname: Linux 2.6.31-14-generic x86_64

[I'M YourOnly.One 🔏 (techmagus)]

Nautilus "Tree" randomized today as well, but different sort order as compared to "Places".

This is the same session as the previous screenshot above. Nautlius "Place" and "Tree" shows different sort order.

[Sebastien Bacher (seb128)]

Thank you for your bug report. The issue is an upstream one and it would be nice if somebody having it could send the bug the to the people writting the software (https://wiki.ubuntu.com/Bugs/Upstream/GNOME)

[A. Walton (awalton)]

This is a bug in both Nautilus and Gtk+; neither sidebar sorts volumes by name, we just append to the list of volumes, usually by order that the drives are mounted. I have a patch in my sidebar rework branch for nautilus, bug #508404 on GNOME's tracker, but it still needs some work before it goes upstream and of course we'd probably want to patch gtk+ similarly to match.

[Yazen Ghannam (yghannam-deactivatedaccount-deactivatedaccount)]

According to A. Walton's comment, it seems that a number of people are working on this issue upstream. I've added a link to the upstream discussion.

[Sebastien Bacher (seb128)]

the bug has been fixed upstream now