How do I submit an Xorg bug on HAL?

Reference: Since implementation of KMS technologies at Ubuntu version 10.04, transitions have occurred where the graphics is first set and how, via:
"Kernel mode-setting (KMS) shifts responsibility for selecting and setting up the graphics mode from X.org to the kernel. When X.org is started, it then detects and uses the mode without any further mode changes. This promises to make booting faster, more graphical, and less flickery. "

From what I can figure out, most of this started with 10.04 when they started implementing KMS technology:
(Simplistic explanation of graphical changes)
- 9.10 graphics modes were dealt with in xorg and the video drivers. Grub2 introduced.
- 10.04 introduces KMS, (kernel mode switching) where graphics modes were set in the kernel and passed to xorg.
- 10.10 has some more changes with this... Trying to find and set the graphics modes and pass it to Xorg.
- Natty and Grub 1.99 have ingrained changes tied to KMS. Grub tries to find and set the graphics using HAL from Xorg, which it then passes to the kernel, which then passes in it to Xorg. That's why we now have the graphics changes happening as soon as the Grub Menu...

Most of the people that I've helped correct their blank screen problems with Natty have been by Bypassing the GFXMODE=auto default, a process that starts and uses data returned by HAL. The main fix explicitely sets the GFXMODE=WIDTHxHEIGHTxDEPTH parameters of a mode that "their" graphics hardware supports. This fix "bypasses "HAL" and it's query/mode set functions. Other fixes are via setting the scan rate of a monitor, which is also sopposed to be a a function of HAL. (ETC.)

That first fix applies setting the "3" common parameters of GFXMODE. That third parameter is buried in the documentation I did find from GNU...

There have been a few other "instances" where there was some other things going on or the "current" kernel "did not support or lost" graphics support for... (The kernel in proposed fixes a lot of those) But the majority was just setting an initial mode.

I have asked around... and no-one wants to fix this, or to even talk about this "new" relationships between grub, the kernel and xorg. I've asked in many places at Ubuntu and Conical (where I thought I could get some answers) about any kind of documentations... but all have been ignored.

I know that kernel boot parameters are a part of it. I know that Grub 1.99's GFXMODE and GFXTERM are a part of it. I know thiat HAL and subsequently Xorg is a part of this.

What I put together so far is in this sticky, which is still evolving:
http://ubuntuforums.org/showthread.php?t=1743535

I know that the default of GFXMODE=auto is causing a lot of blank screens as it tries modes until it lands on one that deos not return an error code... even though that instance may be invalid or out-of-range.

On some people I've helped with this, rolling back the kerenl to 2.6.37.x makes their problems disappear. You say rolling the Grub version back to 1.98 works. I'm thinking that "maybe" those 2 items might be doing the same thing by not passing an invalid mode or parameter. Could it?

Along those line, the same fixes "happen" if they install the propose kernel 2.6.38.9 in the proposed repo or the 2.6.39.0 in the mainline. Which those might have fixed ported in for the bugs that have been filed on this(?)

In Natty Norwhahl 11.04, HAL affects Xorg and the xorg.conf:
"# commented out by update-manager, HAL is now used and auto-detects devices"

Querying video hardware:
"hal.1: read hal dataprocess 2951: arguments to dbus_move_error() were incorrect, assertion "(dest) == NULL || !dbus_error_is_set ((dest))" failed in file dbus-errors.c line 280.
This is normally a bug in some application using the D-Bus library.
libhal.c 3483 : Error unsubscribing to signals, error=The name org.freedesktop.Hal was not provided by any .service files"

HAL problems now affect GNU Grub 1.99, Linux kernel and Xorg. This really affect this new distribution of Ubuntu (11.04) which heavily relies on this and is cuaing may problems.

Summary:
Normal users should not have to be highly skilled "techies" to manually bypass a broken part of a system to make a released distribution work!

How do I submit a bug for this, that will probly be an upstream bug?