Description of problem: USB printer isn't added automatically Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1.just connect USB printer 2. 3. Actual results: No printer detected Expected results: Printer added Additional info: Fresh F16 Install but fully updated Printer can be added by system-config-printer
What does su -c "lpinfo -l -v" show when the printer is connected and on ?
Device: uri = usb://Samsung/ML-1610 class = direct info = Samsung ML-1610 make-and-model = Samsung ML-1610 device-id = MFG:Samsung;CMD:GDI;MDL:ML-1610;CLS:PRINTER;MODE:GDI;STATUS:IDLE; It doesn't show up
Please edit /etc/rsyslog.conf and find this line: # Log anything (except mail) of level info or higher. # Don't log private authentication messages! *.info;mail.none;authpriv.none;cron.none /var/log/messages Add '*.debug;' to it, so that it looks like: *.debug;*.info;mail.none;authpriv.none;cron.none /var/log/messages Now restart rsyslog: systemctl restart rsyslog.service Now when you plug in your printer we should see some useful information about it in /var/log/messages. Could you please paste in any lines that are added to /var/log/messages when you plug in your printer?
Nov 15 20:05:07 localhost kernel: [ 748.456040] usb 3-1: new full speed USB device number 4 using uhci_hcd Nov 15 20:05:07 localhost kernel: [ 748.616459] usb 3-1: New USB device found, idVendor=04e8, idProduct=3268 Nov 15 20:05:07 localhost kernel: [ 748.616465] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Nov 15 20:05:07 localhost kernel: [ 748.616470] usb 3-1: Product: Samsung ML-1610 Series Nov 15 20:05:07 localhost kernel: [ 748.616473] usb 3-1: Manufacturer: Samsung Electronics Co., Ltd. Nov 15 20:05:07 localhost kernel: [ 748.616477] usb 3-1: SerialNumber: 3921BRJL304582.. Nov 15 20:05:07 localhost kernel: [ 748.624788] usblp0: USB Bidirectional printer dev 4 if 0 alt 0 proto 2 vid 0x04E8 pid 0x3268 Nov 15 20:05:07 localhost mtp-probe: checking bus 3, device 4: "/sys/devices/pci0000:00/0000:00:1d.1/usb3/3-1" Nov 15 20:05:07 localhost mtp-probe: bus: 3, device: 4 was not an MTP device Nov 15 20:05:07 localhost udev-configure-printer: add /devices/pci0000:00/0000:00:1d.1/usb3/3-1/3-1:1.0 Nov 15 20:05:07 localhost udev-configure-printer: device devpath is /devices/pci0000:00/0000:00:1d.1/usb3/3-1 Nov 15 20:05:07 localhost udev-configure-printer: Device vendor/product is 04E8:3268 Nov 15 20:05:07 localhost udev-configure-printer: failed to claim interface Nov 15 20:05:07 localhost udev-configure-printer: add /devices/pci0000:00/0000:00:1d.1/usb3/3-1/3-1:1.0/usb/lp0 Nov 15 20:05:07 localhost udev-configure-printer: device devpath is /devices/pci0000:00/0000:00:1d.1/usb3/3-1 Nov 15 20:05:07 localhost udev-configure-printer: MFG:Samsung MDL:ML-1610 SERN:- serial:3921BRJL304582.. Nov 15 20:05:08 localhost hp[1969]: io/hpmud/pp.c 627: unable to read device-id ret=-1 Nov 15 20:05:09 localhost python: io/hpmud/pp.c 627: unable to read device-id ret=-1 Nov 15 20:05:09 localhost udev-configure-printer: URI matches without serial number: usb://Samsung/ML-1610 Nov 15 20:05:09 localhost udev-configure-printer: No serial number URI matches so using those without Nov 15 20:05:09 localhost udev-configure-printer: About to add queue for usb://Samsung/ML-1610 Nov 15 20:05:09 localhost udev-add-printer: add_queue: URIs=['usb://Samsung/ML-1610'] Nov 15 20:05:10 localhost dbus[853]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper) Nov 15 20:05:10 localhost dbus-daemon[853]: dbus[853]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper) Nov 15 20:05:10 localhost dbus[853]: [system] Successfully activated service 'org.freedesktop.PackageKit' Nov 15 20:05:10 localhost dbus-daemon[853]: dbus[853]: [system] Successfully activated service 'org.freedesktop.PackageKit'
funny but now printer shows up!!!! System has been updated also tonight
I have a very similar issue with a Samsung scx-4500w printer - it seems to be able to be defined from the KDE desktop - I added the rastertosamsungspl file to /usr/lib/cups/filter as needed - and also the ppd file in the KDE setup dialog. The printer seems to be set up but sending a print to it gives an error: Under state it is: stopped "/usr/lib/cups/filter/rastertosamsungspl failed" Making a Samsung directory in /usr/share/cups/model/foomatic-db-ppds and putting the ppd file as a gzipped file in the Samsung directory gives the same error. I will attach the cups error log to this report shortly. I know that the rastertosamsungspl file is proprietary but until f14 on this machine I was able to use the printer with this file - with f16 I have failed to get the printer to work (scanner functions are also usually fine but I have not yet tested that with f16 - separate issue!)
Created attachment 533845 [details] Samsung scx-4500w error log This log shows a number of attempts to get the printer to print a file.... All unsuccessful and all ended with a fail for the rastertosamsungspl file
If I run the command lpinfo -l -v The output is a load of stanzas which appear not relevant but one has: Device: uri = usb://Samsung/SCX-4500W%20Series class = direct info = Samsung SCX-4500W Series make-and-model = Samsung SCX-4500W Series device-id = MFG:Samsung;CMD:GDI,FWV;MDL:SCX-4500W Series;CLS:PRINTER;STATUS:IDLE; So it looks like it is detected. Is there anything I can do to work around this problem?
Further information - not sure if relevant but this is a 64 bit f16 system with all updates in as of earlier today. uname -r 3.1.1-1.fc16.x86_64 rpm -q cups cups-1.5.0-16.fc16.x86_64
Mike, as you already know, we can't help you with the rastertosamsungspl filter. But Samsung SCX-4500 seems to be supported in SpliX (http://splix.ap2c.org/). Follow the intructions on http://www.linuxfoundation.org/collaborate/workgroups/openprinting/databasedriverpackages to setup yum repository for openprinting drivers and then install openprinting-splix package.
Oh, I've just tested it and the repository on openprinting.org is empty (Linux Foundation infrastructure was down recently for maintenance due to a security breach).
Thank you Jiri - and I was thinking of doing exactly as you describe as my preferred option is open source drivers - however in the middle of last night I woke up and wondered if there was a separate 64 bit rastertosamsungspl file - my system has just been upgraded from 32 bit F14 to 64 bit F16 - this morning I found that in the original Samsung unified driver file set there was indeed a separate directory for x86_64 - so I pulled the 64 bit rastertosamsungspl file and followed my original setup procedure using the same ppd file as I had used for 32 bit - it works fine! So my issue is resolved with the "correct" x86_64 raster file! However in the future I would really prefer to change over to the SpliX driver when the openprinting repo gets back online. In the meantime if the original author of this bug is happy then it can be closed. Thanks
(In reply to comment #6) > funny but now printer shows up!!!! System has been updated also tonight Closing then.
(In reply to comment #13) > However in the future I would really prefer to change over to the SpliX driver I've created a splix package. It's been in updates-testing repository. There's driver for Samsung SCX-4500. Give it a try, test whether it'll work with your SCX-4500W and possibly leave a note in https://admin.fedoraproject.org/updates/splix-2.0.1-0.3.20111121svn.fc16 Install it with: yum --enablerepo=updates-testing install splix
Jiri - thank you - it works a treat and I have added karma to the bodhi entry.