Daniel, are you able to print the first job after turning on the printer (as it happens to the original poster of this bug report)? Or does the first job already behave as in your attached error_log files?
The job's behaviour in the two error_log files seems to be exactly the same, so it looks like that the activating or deactivating /lib/udev/udev-configure-printer has no influence for you.
Daniel, are you able to print the first job after turning on the printer (as it happens to the original poster of this bug report)? Or does the first job already behave as in your attached error_log files?
The job's behaviour in the two error_log files seems to be exactly the same, so it looks like that the activating or deactivating /lib/udev/ udev-configure- printer has no influence for you.