Bugzilla – Bug 46495
can't type anything in (some) kde embedded yast2 modules
Last modified: 2005-10-12 10:15:19 UTC
The keyboard input in the dsl provider dialog doesn't work when it's embedded in the kde control center. Input in the sysconfig editor works.
this sounds more like a yast QXEmbed issue ..
It's a focus problem. Even I though I click on the entry the keyboard focus stays on the left where the modules are selected.
yes ... wasn't that the reason for the QXEmbed update ? going with <Tab> into that part will lead into working keyboard input, so there should be a way to solve this ....
[Tab] takes the keyboard focus away from kcontrol's module list at the left side, but then the keyboard focus seems to be nowhere. No amount of clicking or hitting [Tab] or whatever seems to move the keyboard focus to the YaST2 dialog. Just checked with RC1 - fails as reported by Arvin. Coolo, any idea?
Worked fine on Coolo's x86_64 machine. Worked sometimes on his i386 machine. Lubos, any idea?
Can't reproduce this any more after the first try. Logged out and back into KDE, rebooted - works flawlessly. Reducing severity to "normal" since this seems to occur randomly (and infrequently).
I can reproduce it reliably with the users YaST2 module, when adding new user (RC2). BTW, this is basically the same like #26494, which was closed only because QXEmbed was updated. I can give it a try, but it won't be that simple :(.
It looks like we'll do a proper kcmshell integration for the next release. This will hopefully make this issue obsolete for good.
*** Bug 48575 has been marked as a duplicate of this bug. ***
I reproduced it always, when I executed package manager. At home on fresh installation or here where are all updates. btw: When I start kcontrol in Window Maker, YaST modules do not open inside kcontrol but as new windows, but I guess this is not an issue, because kcontrol is usually not started without KDE.
I don't know if and how this is supposed to work with another window manager. I guess that KDE embedding magic relies on a KDE aware window manager (kwin).
I don't thing it is problem, I found it just when trying to reproduce it while I was using Window Maker...
No, I only meant the embedded windows that appear outside the kcontrol window. Typing should of course always work.
Adrian, Coolo, Lubos: Would that http://www.trolltech.com/products/solutions/catalog/Widgets/qtxembed/ be a reasonable approach to get around those problems? I didn't look into it yet to find out where exactly the difference is between that QtXEmbed and the version of QXEmbed we are using. It might easily be a simple renaming of QXEmbed -> QtXEmbed.
it is. however, as said before we want anyway native kcm/kpart solution for this, so this will become obsolete.
*** Bug 48977 has been marked as a duplicate of this bug. ***
A new KPart based Y2 KDE integration is on the way. This will fix this issue once and for all.
The new KDE integration didn't make it into 9.1, so this remains open. :-( LATER
*** Bug 53145 has been marked as a duplicate of this bug. ***
still happens occasionally with 9.2 and 9.3
This is deep within that nasty QxEmbed hack. All of our assembled X11 and Qt specialists could not do anything about this.
Maybe we should drop the KDE Control Center embedding instead of the YaST Control Center.
a way better approach is to create kcm modules to be able to do a real embedding.
Have you considered using the settings:/ ioslave instead of the control center? Drawback is, that you loose the hierarchical information of the modules, which is usability-wise a rather bad solution (actually the presetting in kcontrol right now to not show the tree is equally awkward). Advantage is, that each module has it's own window, so now embedding here.
settings:/ is no alternative due to the lack of the help texts and the search functionality which is badly needed for the number of modules.
Eva, for one thing, we have to use kdesu since most modules need root permissions - does "settings:/" support that? For another, embedding the YaST2 window into kcontrol is the core idea of this kcontrol integration.
no, don't use kdesu, it is a konq bug that it doesn't ask. A different bugreport does exist for this already.
*** Bug 74073 has been marked as a duplicate of this bug. ***
*** Bug 80236 has been marked as a duplicate of this bug. ***
*** Bug 103048 has been marked as a duplicate of this bug. ***
Still present in 10.0 beta1. I think this needs to be dealt with somehow rather than closing as WONTFIX. For a new user (especially perhaps coming from another operating system), this is very annoying and gives a bad out-of-box impression. Even as a seasoned SUSE user (seven years), I find it annoying.
Ok, where's my magic wand ... ?
I'm about to submit a kdelibs3 package with fixes for QXEmbed that should hopefully finally take care of this. However as yast2-qt includes its own copy of QXEmbed it needs updating too, see attached files.
Created attachment 46562 [details] qxembed.cc
Created attachment 46563 [details] qxembed.h
Now using that new QXEmbed, hoping that it will fix this issue finally. Thanks, Lubos!
*** Bug 105950 has been marked as a duplicate of this bug. ***
*** Bug 105952 has been marked as a duplicate of this bug. ***
Just for the record, I forgot to include a part of the fix that should be in the kdebase3-SuSE package, so this actually still doesn't work. A working package will be submitted today.
*** Bug 84592 has been marked as a duplicate of this bug. ***
*** Bug 127543 has been marked as a duplicate of this bug. ***
(this was discovered in SuSE Linux 8.x - changed version to 10.0 so it can be made visible to the public)