Bug 761184

Summary: digiKam theme configuration doesn't open
Product: [Fedora] Fedora Reporter: Russell Harrison <fedora>
Component: digikamAssignee: Steven M. Parrish <smparrish>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: alekcejk, ltinkl, rdieter, rharriso, smparrish
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-12-26 04:49:35 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
The default tooltips when digiKam is installed on F16 are unreadable. none

Description Russell Harrison 2011-12-07 20:28:17 UTC
Description of problem:
The digiKam theme configuration dialog doesn't open unless kdebase-workspace is also installed.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Open digiKam on a machine where kdebase-workspace and its dependencies have not yet been installed.
2. Click on the "Settings" Menu and select "Themes -> Configuration..." 
  
Actual results:

Nothing happens...

Expected results:

The Theme Configuration dialog opens and the user is able to modify or select a theme

Additional info:

Installing the kdebase-workspace package resolves the issue.

Comment 1 Rex Dieter 2011-12-07 20:47:07 UTC
kcm_colors is indeed part of kdebase-workspace, not sure if it's worth adding a dep to it, to have it pull in for all users though.

Comment 2 Russell Harrison 2012-01-23 18:43:18 UTC
Created attachment 557025 [details]
The default tooltips when digiKam is installed on F16 are unreadable.

Comment 3 Rex Dieter 2012-01-23 18:47:39 UTC
Russell, what version of digikam are you using?  That was supposed to be fixed in a recent update...

https://admin.fedoraproject.org/updates/FEDORA-2011-16291/digikam-2.3.0-4.fc16

Comment 4 Russell Harrison 2012-01-23 20:16:00 UTC
$ rpm -q digikam
digikam-2.5.0-1.fc16.x86_64

I installed digiKam on this machine (fresh install) after that update was released.

Comment 5 Fedora Update System 2012-12-13 23:49:03 UTC
digikam-2.5.0-4.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/digikam-2.5.0-4.fc16

Comment 6 Fedora Update System 2012-12-15 17:58:29 UTC
Package digikam-2.5.0-4.fc16:
* should fix your issue,
* was pushed to the Fedora 16 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing digikam-2.5.0-4.fc16'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-20420/digikam-2.5.0-4.fc16
then log in and leave karma (feedback).

Comment 7 Fedora Update System 2012-12-26 04:49:37 UTC
digikam-2.5.0-4.fc16 has been pushed to the Fedora 16 stable repository.  If problems still persist, please make note of it in this bug report.