[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: What needs to improve in KDE 4?



I ccd you since you ccd me. Please do not cc me in the future. I read the 
list and that new thread grouping features of KMail are really handy ;).

Am Dienstag 11 Mai 2010 schrieb Dotan Cohen:
> On 11 May 2010 00:58, Martin Steigerwald <Martin@lichtvoll.de> wrote:
> > Am Montag 10 Mai 2010 schrieb Nate Bargmann:
> >> * On 2010 10 May 11:50 -0500, Dotan Cohen wrote:
> >> > Yes, 4.2 and now 4.4 seem to behave badly without a clean ~/.kde.
> >> > I find that very disturbing and unstable.
> >> 
> >> For the record, I had a clean ~/.kde for 4.2 when it hit Sid about a
> >> year ago and upgraded the offered KDE packages through 4.3.4, IIRC,
> >> and then started with a clean ~/.kde for Sid's new 4.4.3.
> >> 
> >> - Nate >>
> > 
> > IMHO when a config setting is not handled properly on upgrade of KDE
> > its a bug.
> 
> Agreed, but it's not one that is likely to be fixed. There seems to be
> no backwards-compatibility in KDE anymore. It's a problem, I know.

Well I got no reply to my detailed bug report yet.

> > I migrated configuration from KDE 3.5.10 and just pressed on "Reset
> > to defaults" for quite some appearance related settings in order to
> > switch them to Oxygen. There have been issues, but I mostly didn't
> > file them as bugs.
> > 
> > Only one I triaged and filed: The separator "58" for colon for web
> > shortcuts in kuriikwsrc or something like that it was is not
> > recognized by KRunner, only by Konqueror. ":" instead works with
> > both. Unfortunately Konqueror saved it as "58" not as ":".
> 
> It _should_ be escaped.

It doesn't work in krunner when it is. See here:

[Bug 218272] New: webshortcuts broken after upgrading KDE 3 to 4 due to 
decimal in keyword delimiter which krunner doesnt support

https://bugs.kde.org/218272
 
> > Anyway I suggest to file those issues as concrete as possible as bugs
> > as you manage to take time for it.

I did so really. This bug report contains quite some hints on testing with 
an empty configuration. Its as easy as that:

mkdir ~/.kde-test
export KDEHOME=~/.kde-test

Then start your KDE application you want to test with empty settings from 
this shell. You can also easily see what configuration files the application 
or the subsystems it uses create.

Ciao,
-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7

Attachment: signature.asc
Description: This is a digitally signed message part.


Reply to: