Bug 457032 - "systemsettings" crashes when changing from Klearlooks to GTK
Summary: "systemsettings" crashes when changing from Klearlooks to GTK
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kdebase-workspace
Version: 10
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-07-29 10:31 UTC by Paul Smith
Modified: 2009-02-04 18:15 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-02-04 18:15:11 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Paul Smith 2008-07-29 10:31:02 UTC 
When I run "systemsettings" of KDE to change the style  from Klearlooks to GTK,
"systemsettings" crashes. So, I cannot have the GTK style.

I am running XFCE and

$ rpm -q qgtkstyle
qgtkstyle-0.0-0.2.20080719svn693.fc9.i386
$ 

Paul
Comment 1 Rex Dieter 2008-07-29 12:15:20 UTC 
Reassigning -> kdebase-workspace (for systemsettings crash).
Comment 2 Bug Zapper 2008-11-26 02:36:57 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Comment 3 Steven M. Parrish 2009-01-10 15:08:10 UTC 
Is this still an issue?
Comment 4 Steven M. Parrish 2009-02-04 17:26:16 UTC 
Reporter, could you please reply to the previous request? If you don't reply in within one month of the original request , we will have to close this bug as INSUFFICIENT_DATA. Thank you.
Comment 5 Paul Smith 2009-02-04 18:08:45 UTC 
(In reply to comment #4)
> Reporter, could you please reply to the previous request? If you don't reply in
> within one month of the original request , we will have to close this bug as
> INSUFFICIENT_DATA. Thank you.

I am sorry, Steven, for not having replied promptly to your previous request, but I have been so busy that I forgot it.

I can now report that the problem seems now to be solved. Thus, I would suggest you to close this bug.

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