Bug 216283 - KDE screensaver cannot be configured on x86_64 for *some* (not all) users
Summary: KDE screensaver cannot be configured on x86_64 for *some* (not all) users
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: kdebase
Version: 6
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-11-18 19:04 UTC by William W. Austin
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-12-06 11:06:51 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description William W. Austin 2006-11-18 19:04:28 UTC
Description of problem:
kcontrol (FOR ONE USER ONLY) cannot obtain a list of screensavers and
screensaver cannot therefore be configured.


Version-Release number of selected component (if applicable):
kdebase-3.5.5-0.4.fc6


How reproducible:
Always


Steps to Reproduce:
1.startx
2.wait until desktop is ready (sys initdefault is 3) and right-click on the
"lock" symbol.
3.select "Configure Screen Saver"

  
Actual results:
The "Configure - KDE Control Module" window will appear, but it cannot find ANY
screen savers.

Expected results:
The "Configure - KDE Control Module" window will appear, and it will display a
list of installed screen savers to choose from.



Additional info:
I am pretty sure this an environment issue - but after RTFM'ing for weeks (this
started under late fc5), I'm still stuck.
This works correctly for most other non-priv. users and for root, so I suspect
an environment issue but have spent 3-5 weeks chasing it down with no luck.
I know it's a small thing but trying to find it is driving me batty.

Comment 1 Than Ngo 2006-11-20 10:20:53 UTC
could you please try following steps:

- login into KDE with login name which has this issue
- mv $HOME/.config HOME/.config.orig
- kbuildsycoca --noincremental

Does it fix the problem?


Note You need to log in before you can comment on or make changes to this bug.