You are not logged in.

Dear visitor, welcome to KDE-Forum.org. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

PTrenholme

Beginner

  • "PTrenholme" started this thread

Posts: 5

Location: Boulder, Colorado, USA

Occupation: Retired

  • Send private message

1

Tuesday, December 13th 2005, 3:40pm

Upgraded to 3.5: Users lost "Panel" configuration

Hi,

I upgraded to 3.5 via the kde-redhat-stable repository (using Fedora Core 4).

Most things seem fine, except that users are presented with a blank panel when they attempt to configure their display panel. (I.e.: Settings -> Desktop -> Panels displays a window with no contents.)

Since this works as expected for "root," I suspect a permissions problem.

Can anyone suggest which components needs their permissions changed so users can configure their own panels? I did look a the "kicker" files, but they were all rwxr-xr-x, so that wasn't where the problem could be found.

2

Saturday, December 31st 2005, 12:31am

RE: Upgraded to 3.5: Users lost "Panel" configuration

same for me (fedora 4 / updated via kde-redhat/yum).
I cant resize the kicker-panel(s) (height)
Anyone seen this too?

Best regards
chrom

3

Monday, January 2nd 2006, 12:31pm

This was discussed on the kde-redhat-users list and the following worked for me:

Try running (as the affected user):
$ kbuildsycoca --noincremental

and

Undo/revert previous menu reconfig/customizations:
$ mv ~/.config ~/.config.BAK

Paul.

4

Sunday, January 15th 2006, 9:53pm

Quoted

Originally posted by Paul Scott
This was discussed on the kde-redhat-users list and the following worked for me:

Try running (as the affected user):
$ kbuildsycoca --noincremental

and

Undo/revert previous menu reconfig/customizations:
$ mv ~/.config ~/.config.BAK

Paul.


I had been struggling with the same bug after installing kde-redhat rpms, and your solution worked. Thanks!
Micha