By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.

Bug 1174

Summary:	Changing theme moves panel
Product:	TDE	Reporter:	Kris <krisgamrat>
Component:	tdebase	Assignee:	Timothy Pearson <kb9vqf>
Status:	RESOLVED FIXED
Severity:	major	CC:	bugwatch, kb9vqf
Priority:	P5
Version:	R14.0.0 [Trinity]
Hardware:	All
OS:	Linux
Compiler Version:		TDE Version String:
Application Version:		Application Name:

Description Kris 2012-08-17 12:01:18 CDT

Every time I go to KControl -> Appearance & Themes -> Theme Manager and change the theme, after updating the configuration, it will refresh the screen so the new theme will take effect. When this happens, the panel will move to the left edge of the screen, regardless of whether it was originally on the bottom, right, or top. If the panel was already on the left edge of the screen, it doesn't move at all. It will only move to the left.

All other panel settings will remain the same (e.g. size, applet/application layout, etc. will not change, it's just the position).

Comment 1 Kris 2012-08-17 12:42:20 CDT

(In reply to comment #0)
> Every time I go to KControl -> Appearance & Themes -> Theme Manager and change
> the theme, after updating the configuration, it will refresh the screen so the
> new theme will take effect. When this happens, the panel will move to the left
> edge of the screen, regardless of whether it was originally on the bottom,
> right, or top. If the panel was already on the left edge of the screen, it
> doesn't move at all. It will only move to the left.
> 
> All other panel settings will remain the same (e.g. size, applet/application
> layout, etc. will not change, it's just the position).

This bug was present in 3.5.13, and is still there in R14.

Comment 2 Darrell 2012-09-13 22:32:40 CDT

Confirmed in R14. I'm bumping this to Major.

Comment 3 Timothy Pearson 2013-05-09 14:21:33 CDT

This was caused by the theme manager overwriting existing settings even if the selected theme did not explicitly set those settings.  This is fixed in GIT hash 77cbd6e9.

Thanks for reporting!