(In reply to comment #16)
> I'd feel better if it were cross upstreamed to both kde and gnome, as it may
> well be a in bug either, or a simple incompatibility.
I do not think it is a bug (even partial) in GNOME.
The common case is that we try to use KDE/QT applications from a GNOME desktop, and most probably some services/libraries/settings that should be enabled, are not.
To take it a bit further. If a typical Fedora KDE desktop works just fine with dead keys, then the KDE/QT people may well say that the problem is a packaging problem. That is, when you hand-pick and install a KDE/QT application, the package manager should (hypothetically) enable some system settings so that dead keys are not affected in QT applications. For this scenario, we would need first someone from KDE/QT to tell us what's the source of the bug.
Thus, I think it was OK to change the bug to 'CLOSED UPSTREAM'.
(In reply to comment #16)
> I'd feel better if it were cross upstreamed to both kde and gnome, as it may
> well be a in bug either, or a simple incompatibility.
I do not think it is a bug (even partial) in GNOME. libraries/ settings that should be enabled, are not.
The common case is that we try to use KDE/QT applications from a GNOME desktop, and most probably some services/
To take it a bit further. If a typical Fedora KDE desktop works just fine with dead keys, then the KDE/QT people may well say that the problem is a packaging problem. That is, when you hand-pick and install a KDE/QT application, the package manager should (hypothetically) enable some system settings so that dead keys are not affected in QT applications. For this scenario, we would need first someone from KDE/QT to tell us what's the source of the bug.
Thus, I think it was OK to change the bug to 'CLOSED UPSTREAM'.