Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 455329 - Notification theme is reset to standard when theme is customized
Summary: Notification theme is reset to standard when theme is customized
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: control-center
Version: rawhide
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Control Center Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-07-14 20:23 UTC by Martin Sourada
Modified: 2008-07-15 21:18 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-07-14 21:25:27 UTC


Attachments (Terms of Use)

Description Martin Sourada 2008-07-14 20:23:42 UTC
Description of problem:
Notification theme is always reset to 'standard' when customizing the theme
settings - i.e. changing controls, colours, window border, icons or pointer to a
combination that does not fit a theme that has set notification theme changes
the theme to 'standard', even if different was set before.

Version-Release number of selected component (if applicable):
control-center-2.23.4-3.fc10

How reproducible:
always

Steps to Reproduce:
1. install nodoka-gnome-theme >= 0.3.90-2.fc10
2. install gconf-editor
3. open gconf-editor and watch '/apps/notification-daemon/theme' key
4. open appearances caplet and select Nodoka theme
5. click Customize and change whatever
  
Actual results:
'/apps/notification-daemon/theme' key reverts back to standard

Expected results:
'/apps/notification-daemon/theme' key stays set to nodoka

Comment 1 Matthias Clasen 2008-07-14 21:25:27 UTC
I hope this is fixed in 2.23.4-4  

Comment 2 Martin Sourada 2008-07-15 21:18:59 UTC
Yup, works now as expected :-)


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