Red Hat Bugzilla – Bug 229378
server settings aren't saved when using "Apply changes" warning dialog
Last modified: 2007-11-30 17:11:57 EST
Description of problem:
Changed server settings aren't saved when using "Apply changes" warning dialog.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. in "Server settings" dialog change some setting (e.g. turn on "Allow users
2. don't click "Apply" and click some remote printer from the list
3. "Apply changes" dialog appears
4. click "Apply"
change is not saved, I'm sill in "Server settings" dialog
change is saved, I'm in printer config dialog (I clicked on the printer)
Fixed in CVS.
Moving to 'devel' as discussed on
I'm still getting this issue, and I noticed the following traceback when I run
it from a terminal window:
Traceback (most recent call last):
File "/usr/share/system-config-printer/system-config-printer.py", line 1099,
err = self.apply()
File "/usr/share/system-config-printer/system-config-printer.py", line 1110,
File "/usr/share/system-config-printer/system-config-printer.py", line 3109,
RuntimeError: Failed to set settings
The application continues to run, but nothing is actually changed.
Fixed in update: system-config-printer-0.7.52.1-2.fc6.
(In reply to comment #4)
> Fixed in update: system-config-printer-0.7.52.1-2.fc6.
Will a similar update hit Rawhide/Development soon?
Peter, this fix went into system-config-printer-0.7.53-1.fc7 so if you're still
seeing the problem it isn't completely fixed. Are you sure you're clicking on a
printer (and getting an apply dialog) rather than just clicking the 'Apply'
button on the settings screen?
If you're clicking the Apply button on the settings screen it's a different
problem, and I would greatly appreciate a separate bug report for it..
Thanks for your further inquiry. I looked into it a bit more and found out that
I couldn't even print at all! I double-checked my config files and - wouldn't
you know it - my earlier fiddling actually *was* saved...so I had accidentally
denied access to every user...How odd. Anyway, I retweaked the files to allow
access again and it seems to work as it should (from my brief testing).
Thanks for the fix!