Description of Problem:
Define a remote unix lpd printer.
After executing <File->Save Changes> look a /etc/printcap -- still the
Only after exiting printconf-gui are the changes saved.
Steps to Reproduce:
1. Using printconf-gui, define a remote unix lpd printer
2. File->Save Changes
3. less /etc/printcap (no changes)
4. exit printconf-gui
5. less /etc/printcap (changes not in place)
5. printsomething using a2ps
changes NOT saved
still does not work under printconf-0.3.6 from rawhide
When you quit, do you get the "You have made changes" dialog?
What do you tell it?
Saving changes explicitly, through the menu, does not restart lpd.
Changes are only applied to the queue when lpd is restarted.
The old 'Apply' button did both, but it confused people. So now I just track
changes, and ask the user if they want to save. If they say yes, I save /and/
But the menu items only do what they say. So, if you saved, and then quit
without letting it 'save', then lpd was not restarted, and you did not get the
This defect is considered MUST-FIX for Fairfax
save-changes I looked at /etc/printcap and it was not changed. I was prepared
to manually do the restart but since printcap had not changed, this was not done.
My understanding is that save changes should update /etc/printcap but not
restart -- but it did not seem to do that.
If you do a restart without a save then it should restart with the old version
of printcap, etc.
Yes, exiting did save the changes and restarted lpd thereafter everything was OK.
The version in rawhide is much better than the on in beta3.
I disagree. /etc/printcap needs to represent the current state of the server.
The changes are being saved through the alchemist, which one day will be a bit
more serious than just local changes.
Anyway, the thing in rawhide fixes many brown paper bag bugs.
Right now, Save changes does not seem to do anything.
I did save-changes (no change to printcap) and then I did restart LPD and the
changes were saved before restarting.
Then I tried adding a new definition and just did restart (NO save-changes) ---
printcap was not changed.
While I can see that there is some logic to the way things are working, I
believe that it makes more sense (is more intuitive) for save changes to update
Regardless, now that I understand what is happening, it is no big deal for me.
This only issue is how others (e.g., new users) will interpret things.
Perhaps this is an issue to be discussed on the testers-list for others to chime in.