Thanks You all ... after downgrading libusb driver, printer is running well.
However, when I need to access the system printers configuration applet and/or the printing queue panel, I detect often a crash from alternatively /usr/share/system-config-printer/config.py or /usr/share/system-config-printer/config.py
I tried to make a backtrace, but I'm not able to catch the PID of the process on-the-fly: when I open the panel I find the running pid with "pidof", but later the crash happens from a forked new process, and I'm not able to know its pid.
So it seems that the libusb downgrade is only part of the matter.
Thanks You all ... after downgrading libusb driver, printer is running well.
However, when I need to access the system printers configuration applet and/or the printing queue panel, I detect often a crash from alternatively /usr/share/ system- config- printer/ config. py or /usr/share/ system- config- printer/ config. py
I tried to make a backtrace, but I'm not able to catch the PID of the process on-the-fly: when I open the panel I find the running pid with "pidof", but later the crash happens from a forked new process, and I'm not able to know its pid.
So it seems that the libusb downgrade is only part of the matter.
Sorry for my English.
Ciao
CM