On Tuesday 11 May 2010 19:52:14 David C. Rankin wrote:

On 05/10/2010 11:23 PM, David C. Rankin wrote:

...

Guys,

Something is fubar with kde4, it seems to have possessed my box. I'm happily

working along in gnome, and suddenly drkonqi appears because of a knotify crash. WTF? knotify? That shouldn't even be running in gnome.

Next, in gedit, I click on the help button and the kde4 help appears with the

error that it can't find the subject 'blah blah blah'. No shit, I doubt very seriously the yelp information has been indexed in khelpcenter.

Let me re-ask the question in a different way in hope of stimulating some discussion which might start me off in the right direction.

"How is it possible for khelpcenter or knotify to be triggered when running gnome?"

Both KDE and GNOME apps start susehelp instead of invoking their native help tools directly for better integration in the native session. /usr/bin/susehelp is a bash script which tries to start khelpcenter in a KDE login and yelp in a GNOME session. For some reason susehelp thinks you're in a KDE session when you are in GNOME and launches khelpcenter. I would try debugging susehelp. knotify was probably started by some KDE app, either one started manually or restored with your session. Looking at your process list will probably make you wiser. Will -- Will Stephenson, openSUSE Team SUSE LINUX Products GmbH - Nürnberg - AG Nürnberg - HRB 16746 - GF: Markus Rex -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org