Bug 62801 - Theme Manager totally destroyed my KDE
Summary: Theme Manager totally destroyed my KDE
Status: RESOLVED NOT A BUG
Alias: None
Product: kcontrol
Classification: Unmaintained
Component: kthememgr (show other bugs)
Version: 3.1.3
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
: 62293 (view as bug list)
Depends on:
Blocks:
 
Reported: 2003-08-17 00:33 UTC by Alex Radu
Modified: 2003-09-23 08:01 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alex Radu 2003-08-17 00:33:19 UTC
Version:           3.1.3 (using KDE KDE 3.1.1)
Installed from:    SuSE RPMs
OS:          Linux

I had the ThinKeramik style as default and then I went to the theme manager and clicked the first item the "Default" item (which really shouldn't be called default since it shows the hicolor style) than I clicked apply. My panel became inacessible and it became jsut a gray because my mouse was skipping slowly and ther est of the desktop was gray too, moving windows left many redaws behind and skipped slowly too. 

I rebooted the computer. Now it said ksplashscren had a segfault and all I could see was the panel in KDE, the rest was gray, my mouse still skipping and I couldn't click anything. I also couldn't go into GNOME to try to fix KDE because I had automatic login so I didn't even go to KDM.

I don't know what happened, but I hope all ANCIENT THEME MANAGER THEMES ARE REMOVED because they may cause the same problem that happened to me. I am too scared to even test another theme.

Hopefully this was just a SuSE 8.2 bug or something else triggered it.

BTW: The theme manager is pretty useless because it can't handle C++ styles. Everything in the Look n Feel section of the control center should be able to be changed with a Theme Manager theme.
Comment 1 Alex Radu 2003-08-17 11:49:53 UTC
I did another install and well I know I said I wouldn't, but I tried the same thing, but this 
time I didn't alter the system, it was a completely default SuSE 8.2 with almost everything 
on the DVD installed. 
 
Same result. 
Comment 2 Maksim Orlovich 2003-08-17 22:58:11 UTC
Sounds like the same bug as #62293. 
 
Comment 3 Alex Radu 2003-08-23 10:31:49 UTC
Yes, but its more general than the bug link you gave me. It does this crap on any theme in 
teh theme manager, this si a very serious bug IMO, but yeah I guess this is a duplicate. 
Comment 4 Aaron J. Seigo 2003-08-26 20:49:12 UTC
*** Bug 62293 has been marked as a duplicate of this bug. ***
Comment 5 Alex Radu 2003-08-26 20:56:57 UTC
Okay what's going on!!!

It says my bug is a duplicate of Bug 62293 and Bug 62293 says its a duplicate of
my  bug!

Comment 6 Alex Radu 2003-08-26 20:58:47 UTC
NM, I was looking at the wrong thing. Sorry.
Comment 7 Daniel Molkentin 2003-09-22 19:30:27 UTC
The Theme Manager is no more. It was removed so I will close this bug. 
Comment 8 Alex Radu 2003-09-23 00:32:58 UTC
Very well ;) I do hope that a far better theme manager that will be able to
support everything in teh Look n Feel and Destktop section of the control center
willa rise, because the idea of a theme manager is fantastic. 
Comment 9 Ian Wadham 2003-09-23 04:42:25 UTC
Subject: Re:  Theme Manager totally destroyed my KDE         

All I wanted to do was find out what a "theme" is, but the Theme
Manager wiped my desktop.  So now you are wiping the Theme
Manager ... great solution, guys ...

I still don't know what a theme is and cannot find out!  So why
not get rid of themes too?

Comment 10 Alex Radu 2003-09-23 08:01:54 UTC
Cool down! The theme manager can manage differnet package swhich can alter KDE's
look and feel, for example a theme pacakge might include a different wallpaper,
color scheme and style.  A theme is the definition of a theme package.

Ina ddition, I'm srue this si not a solution, it is temporary, there is not
enough time to implement a very good theme manager in 3.2 without big delays.
Remember 3.2 is a point release after all.