Bug 102338

Summary:	Editing the KMenu kills the screensaver list
Product:	[Applications] kmenuedit	Reporter:	metrol
Component:	general	Assignee:	Unassigned bugs mailing-list <unassigned-bugs>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	wstephenson
Priority:	NOR
Version:	0.7
Target Milestone:	---
Platform:	unspecified
OS:	FreeBSD
Latest Commit:		Version Fixed In:
Attachments:	Menu config that seems to kill the screensaver list

Description metrol 2005-03-24 03:42:24 UTC

Version:           0.7 (using KDE 3.4.0, compiled sources)
Compiler:          gcc version 3.4.2 [FreeBSD] 20040728
OS:                FreeBSD (i386) release 5.3-STABLE

Attempting to prep KDE for multiple users here which got me into some heavy editing of the KMenu.  I originally saw this problem with 3.3 and it seems to have carried over into 3.4.  Took a long while to figure this one out as there's no logical connection between the cause and the problem.

After several sessions of editing, the screensaver list is blank over in the Control Center.  The only way I've found to get the screensaver list back is to delete the $HOME/.config directory.

Comment 1 metrol 2005-03-24 03:43:56 UTC

Created attachment 10310 [details]
Menu config that seems to kill the screensaver list

Hopefully this helps in diagnosing the problem.

Comment 2 metrol 2005-03-25 11:26:13 UTC

I'm pretty sure the specific thing that killed the screensavers was putting the "Settings" folder under "Utilities".  Moving that folder around is dangerous stuff it would seem.

I'm now able to move all kinds of other stuff around without this problem, so long as "Settings" stays put.

Comment 3 Jens Rutschmann 2006-07-10 19:03:29 UTC

It seems that KControl looks in the wrong directory for screensaver if you put the "Settings" submenu into another submenu.

I opened a new bug report (130561) because:
- it is still present in KDE 3.5.2
- the real problem seems to be a bug in KControl or maybe even in the "KServiceGroup" component that looks up the screensaver path.
- it would also appear if you would configure your menu manually (not using KMenuEdit). I have no idea who would do such a thing, but who knows...

Comment 4 Philip Rodrigues 2006-08-07 21:33:51 UTC

Probably a dupe of bug 89434

Comment 5 Andrew Muhametshin 2007-02-16 06:54:47 UTC

FreeBSD-6.2, KDE 3.5.5 - The problem till now is not eliminated.

Comment 6 Will Stephenson 2009-11-23 15:16:03 UTC


*** This bug has been marked as a duplicate of bug 89434 ***