Quick status update on el6 kde builds hosted @ kde-redhat repos...
* I moved the kde-4.10.x stuff from kde-unstable to kde-testing, finally.
* Over the past couple of says, started working on kde-4.11.x builds,
should be showing up in kde-unstable real soon, as soon as I work my way
through the last batch of stuff that doesn't build cleanly:
Heard a lot of user feedback (complaints, requests) for being able to remove
konqueror, and I've implemented a first step in that direction beginning
with kde-baseapps-4.12.0-2 now in rawhide, and f19/f20 kde-unstable repos.
There continue to be kde-baseapps (metapackage), kde-baseapps-libs
(metapackage), kde-baseapps-devel. In addition to those we have new
kde-baseapps-common.noarch (includes licenses mostly)
this ended up being more work that I anticipated, ended up spending a lot of
yesterday working on it, but am happy with the result.
Please test, and offer feedback, especially regarding subpackage
Next steps include adding some/all of these to rawhide comps, and adjusting
dependencies in other packages that currently use stuff like:
I'm trying to establish an F20 x2go kde session with the correct
keyboard type and mapping for my clients' keyboards (pc105/gb, and mac).
What I get when I log in is always a us keyboard map for a pc105 keyboard.
I've tried starting the x2go session with a simple xterm, and found that
I can get the correct keyboard mapping as set by the x2go windows
client. (I had to touch a file /usr/share/X11/xkb/keymap.dir to get this
to work though.)
Since the keyboard map is correct in the Xterm session but wrong in the
kde session it looks like x2go is setting the keyboard/map ok but that
kde is somehow overriding what is being set by x2go. (I've tried with
Keyboard daemon both checked and unchecked in System Settings ->
Startup and Shutdown -> Service manager. I'm running with kscreen2
unchecked as that causes other problems with resizing the session window).
Does kde try to set the keyboard type and layout on login?
If so, how can I stop it doing that and accept whatever was set before
startkde was run?
PS I thought I had this working robustly from different clients in
F20-beta, but I'm back to square one now.
The crash on connect bug is fixed. Now I can connect to my audio sink. But I
can't disconnect. Even after connecting, there is no 'disconnect' option shown
- only 'connect'.
Clicking on 'configure bluetooth', I can then select my headset, and then
On login now I'm often prompted for my wireless password before I'm
prompted for my kwallet password (which contains the wireless password).
Is this a known issue?
Currently running 4.11.4 on F20.
Technical Manager 303-415-9701 x222
NWRA/CoRA Division FAX: 303-415-9702
3380 Mitchell Lane orion(a)cora.nwra.com
Boulder, CO 80301 http://www.cora.nwra.com
Thanks partly to my being home sick a couple of days, and having nothing
better to do... :)
Just pushed an initial batch of kde-4.12.0 rpms for f19 to our
kde-unstable (footnote) repo. I similarly updated kde-unstable/f20 a
couple of days ago too.
we'd very much appreciate any feedback/testing from the community to
help facilitate bringing kde-4.12.x to f20 officially at some point in
the (hopefully) near future.
footnote: see https://fedoraproject.org/wiki/SIGs/KDE/Testing for
details on how to use/access our 3rd party kde repos.
I have noticed that...
...never got updated to 4.11.95, 4.11.97 or 4.12.
Have they been discontinued?