Hi I upgraded to xfce-4.3.90.2 and I mentioned, that the kde runtime environment is not started properly. I cannot make use of programms like kcontrol or even korgac (Alarm daemon for Korganizer). I tested it with KDE 3.4.3, 3.5.2 and 3.5.3 and ist all the same. With XFCE 4.2.3.2 there are no problems with that. I'm using gentoo-Linux
Well, the KDE compat code in xfce4-session is exactly the same as in 4.2, so its unlikely a problem in xfce4-session (and thereby in Xfce). What does not work exactly? And which error messages do you get?
Created attachment 676 kcontrol in action
Unfortunately, I do not get any errormessages. Korgac does not respond to a mouscklick, and the KDE Controll-Center has no functions. I attached a screenshot. I can only solve this problem for about 15minutes, when I start kde-3.4 (does'nt work with kde-3.5) and start these Programms within. After switching back to xfce, these programms will work korrektly for about 15 minutes. Sometimes (doesn't happen very often) the KDE-Trayicons are opened in an own window instead of the tray.
Well, since it did not change, xfce4-session still does env DYLD_FORCE_FLAT_NAMESPACE= LD_BIND_NOW=true SESSION_MANAGER= kdeinit dcop klauncher klauncher setLaunchEnv SESSION_MANAGER <sm> on startup. So you have basicly two options: a) File a bug report to KDE, which makes most sense, since it's actually a KDE app that doesn't work. b) Check if gentoo applies special patches to 4.2, that are not applied to 4.4. I'll resolve this to INVALID for now. Reopen if it's really a bug in Xfce.
Ok, I found out, where this problem lies, and how to solve it. It's just a really little thing: The variable XDG_DATA_DIRS is set without the kdepath so kbuildsycoca scrambles the whole database in kdecache. I'm testing, if this was the only reason for this problem, but I think (and hope) it's done with that.
So this is a bug in KDE, and this report can be closed.
(In reply to comment #5) > Ok, I found out, where this problem lies, and how to solve it. It's just a > really little thing: > > The variable XDG_DATA_DIRS is set without the kdepath so kbuildsycoca scrambles > the whole database in kdecache. > I'm testing, if this was the only reason for this problem, but I think (and > hope) it's done with that. > what was the result of your testings? Have the same problem (http://bugzilla.xfce.org/show_bug.cgi?id=2177) and looking for the solution.
export XDG_CONFIG_DIRS=/etc/xdg:/usr/kde/3.5/etc/xdg export XDG_DATA_DIRS=/usr/kde/3.5/share:/usr/share worked for me :)
(In reply to comment #7) > what was the result of your testings? Have the same problem > (http://bugzilla.xfce.org/show_bug.cgi?id=2177) and looking for the solution. > This definitely solved my problem. I didn't need to set the XDG_CONFIG_DIRS, but I think, it doesn't harm ;)
I was running RC1 and RC2 and had a similar problem. Since the issue is apparently resolved by setting an environment variable, shouldn't we just add something like XDG_DATA_DIRS="$XDG_DATA_DIRS:$KDEDIR/share" to startxfce4 and make it work instead of calling it a KDE bug and leave KDE users with a broken kcontrol?
Well, it's a clearly bug in KDE. Dunno whether it's worth to add a work-around that comes at the risk of breaking other things.
What do the other devs think?
I think this is correctly INVALID. It's up to the distribution to set (or add to) XDG_DATA_DIRS properly. For example, on Gentoo, this whole thing could be solved by having each desktop environment's 'meta-ebuild' add a stub to /etc/env.d/ that specifies its XDG_* related variables. File a bug with your distro, and feel free to point them here for further explanation.