[Portland] Issues with 1.0beta2 and KDE

Bastian, Waldo waldo.bastian at intel.com
Thu Aug 3 13:01:01 PDT 2006


>[Čt srp  3 15:42:45 CEST 2006] test_plain_file_install: verify  is
>installed
>correctly on the desktop: FAIL
>Did not find 'xdgtestdata-08-03+7.txt' in '/home/llunak/Desktop'
>Test has already failed. Not bothering to ask 'Is there an icon on the
>desktop with name 'xdgtestdata-08-03+7.txt'?'
>
> The reason is simple, my desktop is not /home/llunak/Desktop,
>it's /home/llunak/.kde/Desktop - this is configurable in KDE
>(kcontrol->System Administration->Paths) and I don't like polluted ~/.
>
> The attached xdg-desktop-icon patch makes it read the proper config value,
>but it doesn't really work since it needs detection of the desktop which
>may not be running at the install time (so the patch is not ok). Also, I'm 
>not sure it should just work that way - perhaps it should first try to 
>install to $HOME/Desktop and if KDE is also installed and the desktop path 
> is different then try to install in this path as well?

That sounds like a usable heuristic. 

> The reason is that kfmclient exec/openURL can give bogus exit code because
>of a bug (access to deleted memory). I've already fixed this in KDE SVN. I
>suggest using the attached kfmclient.patch patch that checks KDE version
>and if it's older then KDE3.5.5 then kfmclient exec simply never fails.

Can you change it so that it runs kde-config once and stores the result?

>- The installed menu entries cause startup feedback. I see that's been
>already fixed in CVS, I've just changed it to generic StartupNotify= 
>without X-KDE- prefix.

Gnome didn't show notifications in the first place, seems they use a different default.

>- There are problems with focus stealing prevention if kfmclient opens a
>window for an application that has already some windows open - the new
>window is then open in background. Most visible when using xdg-email with 
> the mailer already open. It looks like nobody has ever run into this 
> scenario or nobody has ever used kfmclient at all (KDE apps use the 
> functionality directly and there the activation is handled properly).
>
> I'm unsure what to do with this. I'll fix kfmclient for KDE3.5.5 but I
>don't
>know about the scripts. Just ignoring this problem doesn't seem to be that
>good solution, I can probably add a hack for KMail but I have no idea how
>to
>handle the case when the user has some other mailer configured for use in
>KDE :-/.

Can't help you with that one.

> With these fixes I'm not getting any testsuite failures on SUSE10.1 +
>KDE3.5.4 except for those caused by the Desktop directory.

Nice.

Cheers,
Waldo


More information about the Portland mailing list