Kubuntu Karmic: OK, but sometimes like uncontrolled horse (Was: Switching a friend to Ubuntu)
basroufs at gmail.com
Tue Jan 26 15:56:59 UTC 2010
Hello Dotan and Everybody
2010/1/26 Dotan Cohen <dotancohen at gmail.com>:
>> For a proper summary on how this mess looks like, I would need to
>> discover some 'chaos patterns' ....
> Are you sure that you are on a recent version of KDE 4?
Yes - in November I upgraded to Karmic along with the KDE version
coming with it. In December I upgraded KDE to version I am working
with now: KDE 4.3.3.
>.....KDE <= 4.2 would move the icons around the panel if they are unlocked.
This I can confirm by my own experience. But it is getting better
already. It is quite probable that I have summarised in my previous
mails in this thread my experiences ever since Jaunty and the KDE
version coming with that one. This afternoon I discovered that my
widgets were 'unlocked' - however, no problems occurred. But I
preferred to lock them again, in order to prevent complications during
my working sessions.
> Please test with 4.4 (the RC is available now) as I think that issue is resolved.
Is it possible to test a KDE 'release candidate' without seriously
messing up the system? I dared to upgrade to 4.3., because it was a
'stable' release. On the other hand, I am willing to test and report
my experiences, if it helps to contribute like this to the development
> That icon is called the "Cashew" and the mess you see is the
> "activities". It is a half-baked feature and the main dev refuses to
> remove the UI for it even though the feature is not ready.
Good that you mention this.
> Pressing the (+) magnifier near the center of the screen should bring you back
> to the desktop that you know.
? Pls. explain.
> I hate this feature too, and I suggest installing the Plasmoid that
> hides the Cashew:
> Here'a another one if there is a problem with the first:
Thx. I will try them and get back with experience about them.
>> lines or squares throughout the whole screen .....
> That was a Kubuntu-ATI bug and it has long since been fixed with the FOSS drivers.
It is quite possible that I had that experience before this bug-fix
had been distributed and installed.
More information about the ubuntu-users