Bug#292307: Theme does not contain a .themerc nor a .theme file.
Package: kdebase
Version: 4:2.2.2-14.8
I think the KDE Theme Manager (Preferences | Look & Feel | Theme Manager)
is still broken. It was reported in bug 203863 which is marked as fixed
and closed.
The error message is:
Theme does not contain a .themerc nor a .theme file.
To repeat the error:
>From the K menu select Preferences | Look & Feel | Theme Manager then click
on a theme, or from the K menu select Control Centre | Look & Feel | Theme
Manager then click on a theme. The bug might not appear on a fresh install.
What I was expecting:
Actually, this used to work, and a lot of people have reported the same. I
was expecting the theme to change when I clicked on a new theme name.
What I think is broken:
I think something is deleting the directory
.kde/share/apps/kthememgr/Work
You can see an error report if you run the theme manager in a shell and
select a theme:
user@host:~$ kcmshell kthememgr
Xlib: extension "RENDER" missing on display "host:1.0".
sh: cd: /home/user/.kde/share/apps/kthememgr/Work/: No such file or
directory
QDir::readDirEntries: Cannot read the directory:
/home/user/.kde/share/apps/kthememgr/Work
As an experiment, I created this directory and tried to select a theme.
The directory was deleted. I think something is deleting the directory
rather than the *contents* of the directory.
e.g:
user@host:~$ mkdir .kde/share/apps/kthememgr/Work
user@host:~$ ls .kde/share/apps/kthememgr/Work
user@host:~$
Now select a theme.
user@host:~$ ls .kde/share/apps/kthememgr/Work
ls: .kde/share/apps/kthememgr/Work: No such file or directory
user@host:~$
System configuration:
This happens on a server and a laptop I have installed. Both are running
Debian 3.0 r0 Woody (bf24 variant) with all security updates and various
(and different) packages.
uname -a output:
Linux host 2.4.18-bf2.4 #1 Son Apr 14 09:53:28 CEST 2002 i686 unknown
It originally worked, but because I use the feature so rarely I don't know
when it stopped working.
I don't think bug 203863 should have been closed yet. Or rather, it may
well have been fixed in KDE 3.2, but not in KDE 2.2.2, which is the version
in Debian 3.0 Woody.
Thank you.
Andrew Errington
Reply to: