This seems to have been fixed in Karmic. Closing the issue as fixed.
** Changed in: gtk+2.0 (Ubuntu)
Status: Invalid = Fix Released
--
Compose sequence for aring changed after upgrade
https://bugs.launchpad.net/bugs/284658
You received this bug notification because you are a member of
We are closing this bug report as it lacks the information, described in
the previous comments, we need to investigate the problem further.
However, please reopen it if you can give us the missing information and
don't hesitate to submit bug reports in the future.
** Changed in: gtk+2.0 (Ubuntu)
thank you for your bug report, what keymap do you use? could you try on
jaunty? the issue should be sent to bugzilla.gnome.org by somebody who
has a clue about how that should be working
** Changed in: gtk+2.0 (Ubuntu)
Importance: Undecided = Low
** Changed in: gtk+2.0 (Ubuntu)
Status:
This bug affects me as well.
http://ubuntuforums.org/showthread.php?p=6085358
--
Compose sequence for aring changed after upgrade
https://bugs.launchpad.net/bugs/284658
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Sorry, I should have noted that this affects more than just the aring
order, but the function of the compose key overall.
--
Compose sequence for aring changed after upgrade
https://bugs.launchpad.net/bugs/284658
You received this bug notification because you are a member of Ubuntu
Bugs, which
A workaround would be to replace the Gnome hard coding with XIM by
following the how-to under https://help.ubuntu.com/community/ComposeKey
and then add the following to lines to your .XCompose file:
Multi_key A A : Å Aring # LATIN CAPITAL LETTER A
WITH RING ABOVE
Multi_key
