"John (J5) Palmieri" johnp@redhat.com wrote:
On Mon, 2004-12-06 at 13:30, Nicolas Mailhot wrote:
Le lundi 06 décembre 2004 à 12:38 -0500, John (J5) Palmieri a écrit :
I don't see a bug on this in bugzilla. Rule of thumb is if it is not filed in bugzilla it is not going to get fixed. This is why we have the test releases and rawhide. Please file a bug on hal-cups-utils.
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=119970
And yes the problem evolved somewhat since the bug was filled. The number of steps to perform to get the printer operational after power-up has shrunk a bit. But the autodetected hal printer is still pretty useless - if I hadn't created my own printer setup (with a different name than the HAL one else HAL would just nuke it) I couldn't print without going into system-config-printer every single time the printer is powered up.
That bug is before my time.
Then this one will be even more before your time:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=58901
Things do seem to have got better since then, but it's clearly still an issue in some cases. My solution to 58901 was a patch to kudzu which allowed the user to specify that a device was expected to be connected intermittently. In that case kudzu would retain the configuration and not pester the user about it as the device came and went.
Ron