** Changed in: gtk
Importance: Unknown = Low
--
GTK's compose map is different to X's
https://bugs.launchpad.net/bugs/116183
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
** Changed in: gtk (upstream)
Status: Invalid = Won't Fix
--
GTK's compose map is different to X's
https://bugs.launchpad.net/bugs/116183
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
** Changed in: gtk (upstream)
Status: Unknown = Rejected
--
GTK's compose map is different to X's
https://bugs.launchpad.net/bugs/116183
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
** Bug watch added: GNOME Bug Tracker #440860
http://bugzilla.gnome.org/show_bug.cgi?id=440860
** Also affects: gtk (upstream) via
http://bugzilla.gnome.org/show_bug.cgi?id=440860
Importance: Unknown
Status: Unknown
--
GTK's compose map is different to X's
it has its own keymap, better to open upstream if we want to argue about
that, we distribute the software, don't write it
--
GTK's compose map is different to X's
https://bugs.launchpad.net/bugs/116183
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a
Sebastien Bacher wrote:
it has its own keymap, better to open upstream if we want to argue about
that, we distribute the software, don't write it
And there I have taken it.
http://bugzilla.gnome.org/show_activity.cgi?id=440860
Thanks for your help,
Sam.
--
GTK's compose map is different
Thanks for your comments. This does not appear to be a bug report and we
are closing it. We appreciate the difficulties you are facing, but it
would make more sense to raise your question in the support tracker.
https://answers.launchpad.net/questions
** Changed in: gtk+2.0 (Ubuntu)
gtk is ignoring the X key map. how is that not a bug.
Sam.
Sebastien Bacher wrote:
Thanks for your comments. This does not appear to be a bug report and we
are closing it. We appreciate the difficulties you are facing, but it
would make more sense to raise your question in the support