https://bugzilla.novell.com/show_bug.cgi?id=388575
User jsmeix@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=388575#c2
Johannes Meixner changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|Normal |Critical
--- Comment #2 from Johannes Meixner 2008-05-09 02:40:38 MST ---
Now a critical bug because of "corruption of data"
(corruption of config data in this particular case), see
https://bugzilla.novell.com/page.cgi?id=fields.html#bug_severity
The [Change Connection] stuff it broken to the core!
Have two locally connected printers to have
two DeviceURIs avialable so that you can
actually change the DeviceURI via [Change Connection].
Perhaps it works also with one real USB printer
and then change its DeviceURI to "parallel...".
Initially have no queues.
Start yast2-printer.
Set up a new queue only for one printer with yast2-printer.
Finish yast2-printer.
Start yast2-printer.
Select the queue to change it.
Select [Change Connection].
Choose another DeviceURI (e.g. the one for the other printer).
Normal bug:
yast2-printer automatically changes also the driver
without any user notification.
But this is not what I did.
I did only [Change Connection].
I didn't do [Change Driver].
If the model for the new DeviceURI looks different,
a user information that probably the driver should
also be changed is of course nice to have.
But a silent change is a bug.
If I replace a model completely, I would usually
just remove to old queue and set up a new one
(in particular to get a new matching queue name).
To reproduce the next bug, leave it as is
and just finish yast2-printer.
Critical bug:
Now there is a new queue with a meaningless
autogenerated name "printer" which has the
new DeviceUri and the new driver (PPD file)
but the original queue was not changed at all.
This is plain totally broken to the core.
Did you ever test it on your own?
If there is no time to fix it for 11.0
remove the [Change Connection] stuff completely
to avoid its descructive results.
Under the current circumstances it would be much better
to let the user delete and re-create the queue if the
connevtion is to be changed than the current mess.
I do not want to know what happens if I try to do
a lot of changes for a lot of different queues
in one single yast2-printer run...
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.