cups does not see usb printer

[Martina]

Binary package hint: cupsys

Even though i have read all bugs reports that are related i did not find any solution in any of them (16339, 83933, 65794, 26657 and others that were linked).
So, I would like to report that my USB Dymo Labelwriter 310 that is connected to a USB port of my PC is not "seen" by Cups although the printer is clearly visible in lsusb (Bus 003 Device 002: ID 0922:0009 Dymo-CoStar Corp. LabelWriter 310).
I have tried all "solutions" regarding adding cupsys, lp etc to different groups and looking at permissions but nothing helped as yet.
By the way: other 2 (HP) USB-printers were seen immediately and can be used.
Please help; I like to use the label printer!
My configuration: ubuntu feisty 704 including all updates that were presented.

[Patrice Vetsel (vetsel-patrice)]

"cups does not see" could be more specific ? Not see printer in usb or driver of this printer ?
Do you use gnome-cups-manager to add printer or cupsys web interface ?

Could you make a step by step showing what it's wrong and when ?!

[Pascal De Vuyst (pascal-devuyst)]

Please provide the output of the printer detection steps described here and attach the output of the printingbuginfo script: https://wiki.ubuntu.com/DebuggingPrintingProblems.

[Martina (m-divertacollini)]

Hi,
Output is attached: lsmod and log+lpinfo
The printer cannot be installed so no output from debug of cups when
trying to print.
Regards,
Martine

Pascal De Vuyst schreef:
> Please provide the output of the printer detection steps described here
> and attach the output of the printingbuginfo script:
> https://wiki.ubuntu.com/DebuggingPrintingProblems.
>
> ** Changed in: cupsys (Ubuntu)
> Assignee: (unassigned) => Pascal De Vuyst
>
>

usb_storage 72256 1
snd_usb_audio 79744 0
snd_pcm 79876 4 snd_intel8x0,snd_ac97_codec,snd_usb_audio,snd_pcm_oss
snd_usb_lib 17280 1 snd_usb_audio
snd_hwdep 9988 1 snd_usb_audio
snd_rawmidi 25472 2 snd_usb_lib,snd_seq_midi
libusual 17936 1 usb_storage
usblp 14848 0
snd 54020 14 snd_intel8x0,snd_ac97_codec,snd_seq_oss,snd_usb_audio,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_hwdep,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
scsi_mod 142348 6 sbp2,usb_storage,sg,sr_mod,sd_mod,libata
usbcore 134280 9 usb_storage,snd_usb_audio,snd_usb_lib,libusual,usblp,pwc,ehci_hcd,uhci_hcd

martine@ubuntu:~$ tail -f /var/log/messages
Aug 27 20:02:51 ubuntu -- MARK --
Aug 27 20:22:51 ubuntu -- MARK --
Aug 27 20:42:51 ubuntu -- MARK --
Aug 27 21:02:52 ubuntu -- MARK --
Aug 27 21:22:52 ubuntu -- MARK --
Aug 27 21:42:52 ubuntu -- MARK --
Aug 27 22:02:52 ubuntu -- MARK --
Aug 27 22:22:53 ubuntu -- MARK --
Aug 27 22:42:53 ubuntu -- MARK --
Aug 27 22:50:18 ubuntu kernel: [32827.152097] usb 3-1: USB disconnect, address 2
Aug 27 22:50:52 ubuntu kernel: [32861.229977] usb 3-1: new low speed USB device using uhci_hcd and address 3
Aug 27 22:50:52 ubuntu kernel: [32861.421585] usb 3-1: configuration #1 chosen from 1 choice

martine@ubuntu:~$ lpinfo -v
network socket
network beh
network bluetooth
direct usb://hp/deskjet%203600?serial=TH3811311W6B
direct hp:/usb/deskjet_3600?serial=TH3811311W6B
direct hpfax
direct usb://HP/LaserJet%202200
direct hp:/usb/HP_LaserJet_2200?serial=00CNHRG48352
network http
network ipp
network lpd
direct parallel:/dev/lp0
direct canon:/dev/lp0
direct epson:/dev/lp0
direct scsi
serial serial:/dev/ttyS0?baud=115200
network smb
martine@ubuntu:~$

[Pascal De Vuyst (pascal-devuyst)]

Could you also attach the output of the printingbug info script.
Note that e-mail attachments don't work, you have to go to the launchpad url and click "Add a comment/attachment".

[Martina (m-divertacollini)]

Thanks, Patrice, for replying so soon.

When using system/maintenance/printers (which would be gnome-cups-manager) only the two usb printers that function corectly come up (HPDeskjet & HPLaserprinter), even twice, one time normal usb and one time in HPLIP. I add add the other printer choosing "use another port" because the Dymo is not found automatically; then i get several options, but no USB printer-port.
see screenshot attached.

When i use the web-interface with localhost:631 it is no different although i get more options ;second screenshot. No USB printer ports that i can use.
What to do?
Regards,
Martine

[Martina (m-divertacollini)]

Hi,
Output is attached: lsmod and log+lpinfo
The printer cannot be installed so no output from debug of cups when
trying to print.
Regards,
Martine

[Patrice Vetsel (vetsel-patrice)]

Have you, or could you tried to remove all printers configuration. Unplug all printers.And just plugin your Dymo and see if it's available in gnome-cups-manager ? I suggest this manipulation to remove a conflict problem with your others printers.

[Martina (m-divertacollini)]

I removed all printers, restarted to be sure, connected the Dymo usb printer and tried to add the printer but no usb printerport was to be seen in either gnome-cups-manager or cupsys web interface. When i reconnected the other 2 printers (that are on a hub) the gnome-cups-manager came up by itself, so they were recognized immediately.
Unfortunately no success an also no conflict problem.

[Martina (m-divertacollini)]

I got a reply from Dymo Support where i put my printing problem as well; they send me the SDK for dymo on linux (if you want it I can att it for other ubuntu users); many different ppd files were included.
I encountered a document in the Zip file that said:
******************************
DYMO Products Supported

The following products are supported:
LabelWriter 400
LabelWriter 400 Turbo
LabelWriter DUO
LabelWriter Twin Turbo
LabelWriter 300
LabelWriter 330
LabelWriter 330 Turbo
LabelMANAGER 450
LabelPOINT 350
These products should work with direct USB or serial port connections as well as shared over the network from other Linux or Windows machine.

The following products can work only when shared over the network from a Windows machine. This is due to limitations in the USB support in these printers – Linux USB support only recognizes fully compliant USB devices.
LabelWriter 310
LabelWriter 315
LabelWriter 320
LabelMANAGER 400
LabelMANAGER PC
******************************

So maybe it is just the printer that does not do the proper usb things.
Would it be possible to "trick" ubuntu in believing it is a usb printer after all?

[Patrice Vetsel (vetsel-patrice)]

As said by manufacturer : "This is due to limitations in the USB support in these printers – Linux USB support only recognizes fully compliant USB devices.". So it's the printer fault if you can not see it under gnome-cups-manager. Sorry :(

[Patrice Vetsel (vetsel-patrice)]

Thank you for your bug report and feel free to do it again :)
Regards

[Till Kamppeter (till-kamppeter)]

I have now packaged CUPS with an alternative USB backend which does not use the usblp kernel module. You can download it here:

http://www.linux-foundation.org/~till/tmp/ubuntu/gutsy/cupsys/

Install all packages in the binary/ subdirectory using "sudo dpkg -i ...". Then do

sudo rmmod usblp

Does CUPS/system-config-printer/gnome-cups-manager see your Dymo now?

Note that the binary packages are for Ubuntu Gutsy.

[Martina (m-divertacollini)]

THX. Especially for taking this up further.

Unfortunately, all but one of the packages cannot be installed as libc6
or realated (libcupsys2) are a prerequisite and "not installed" altough
I can see libc6 installed in synaptic .....
Probably not the right version of the one your software needs.
What to do?
Regards,
Martine

Till Kamppeter schreef:
> I have now packaged CUPS with an alternative USB backend which does not
> use the usblp kernel module. You can download it here:
>
> http://www.linux-foundation.org/~till/tmp/ubuntu/gutsy/cupsys/
>
> Install all packages in the binary/ subdirectory using "sudo dpkg -i
> ...". Then do
>
> sudo rmmod usblp
>
> Does CUPS/system-config-printer/gnome-cups-manager see your Dymo now?
>
> Note that the binary packages are for Ubuntu Gutsy.
>
>

[Martina (m-divertacollini)]

THX. Especially for taking this up further.

Unfortunately, all but one of the packages cannot be installed as libc6 or realated (libcupsys2) are a prerequisite and "not installed" altough I can see libc6 installed in synaptic .....
Probably not the right version of the one your software needs.
What to do?
Regards,
Martine

[Till Kamppeter (till-kamppeter)]

Note that the binary packages are for Gutsy. For tests on Feisty you have to rebuild the source packages.

[Martina (m-divertacollini)]

Well, I'am not (yet) up to that sort of thing. Better wait and see if this is included in the next release of Ubuntu (Feisty).
Thanks anyway.
Martine

[Till Kamppeter (till-kamppeter)]

Do not worry about rebuilding a package. Here are the steps. Ask here if you have problems.

Download the three files which are directly in the

http://www.linux-foundation.org/~till/tmp/ubuntu/gutsy/cupsys/

into a new empty directory. Change into that directory and do

sudo apt-get install build-essential fakeroot
sudo apt-get build-dep cupsys
sudo apt-get install libkrb5-dev libavahi-compat-libdnssd-dev linux-libc-dev
dpkg-source -x *.dsc
cd cupsys-*
dpkg-buildpackage -rfakeroot
cd ..
sudo dpkg -i *.deb
sudo rmmod usblp

If AppArmor is installed on your box (you have a file /etc/init.d/apparmor) do in addition:

sudo apt-get install apparmor-utils
sudo aa-complain cupsd

Now try again and tell whether CUPS recognizes your Dymo printer now.

[Martina (m-divertacollini)]

Hi,
It stops when trying to buildpackages: many errors. See errors.txt.
also the nex command dpkg -i *.deb cannot be done because there is no .deb

Please help.
THX

[Till Kamppeter (till-kamppeter)]

Seems that the file

/usr/include/linux/usb/ch9.h

is not on your system.

Do the following:

sudo mkdir -p /usr/include/linux/usb/
ln -s /usr/include/linux/usb_ch9.h /usr/include/linux/usb/ch9.h

Then in the directory with the source packages do

rm -rf cupsys-1.3.0
dpkg-source -x *.dsc
cd cupsys-*
dpkg-buildpackage -rfakeroot
cd ..
sudo dpkg -i *.deb
sudo rmmod usblp

and in case of AppArmor being on your system also

sudo apt-get install apparmor-utils
sudo aa-complain cupsd

Now everything should work.

[Till Kamppeter (till-kamppeter)]

Forgot the "sudo" at the "ln" command, must be

sudo mkdir -p /usr/include/linux/usb/
sudo ln -s /usr/include/linux/usb_ch9.h /usr/include/linux/usb/ch9.h

[Martina (m-divertacollini)]

After adding the ch9.h to my system, i ran into some warnings but sudi dpkp -i *.deb didn't work because ghostscript is missng (?); These were the messages:
martine@ubuntu:~/cupsys$ sudo dpkg -i *.deb
(Database inlezen ... 120391 bestanden en mappen geïnstalleerd.)
Voorbereiden om cupsys 1.2.8-0ubuntu8 te vervangen (door cupsys_1.3.0-3ubuntu2_i386.deb) ...
 * Stopping Common Unix Printing System: cupsd [ OK ]
Uitpakken van vervangende cupsys ...
Voorbereiden om cupsys-bsd 1.2.8-0ubuntu8 te vervangen (door cupsys-bsd_1.3.0-3ubuntu2_i386.deb) ...
Uitpakken van vervangende cupsys-bsd ...
Voorbereiden om cupsys-client 1.2.8-0ubuntu8 te vervangen (door cupsys-client_1.3.0-3ubuntu2_i386.deb) ...
Uitpakken van vervangende cupsys-client ...
Voorbereiden om cupsys-common 1.3.0-3ubuntu2 te vervangen (door cupsys-common_1.3.0-3ubuntu2_all.deb) ...
Uitpakken van vervangende cupsys-common ...
Voorbereiden om libcupsimage2 1.2.8-0ubuntu8 te vervangen (door libcupsimage2_1.3.0-3ubuntu2_i386.deb) ...
Uitpakken van vervangende libcupsimage2 ...
Selecteren van voorheen niet geselecteerd pakket libcupsimage2-dev.
Uitpakken van libcupsimage2-dev (uit libcupsimage2-dev_1.3.0-3ubuntu2_i386.deb) ...
Voorbereiden om libcupsys2 1.2.8-0ubuntu8 te vervangen (door libcupsys2_1.3.0-3ubuntu2_i386.deb) ...
Uitpakken van vervangende libcupsys2 ...
Voorbereiden om libcupsys2-dev 1.2.8-0ubuntu8 te vervangen (door libcupsys2-dev_1.3.0-3ubuntu2_i386.deb) ...
Uitpakken van vervangende libcupsys2-dev ...
dpkg: vereistenproblemen verhinderen de configuratie van cupsys:
 cupsys is afhankelijk van ghostscript; maar:
  Pakket `ghostscript' is niet geïnstalleerd.
dpkg: fout bij afhandelen van cupsys (--install):
 vereistenproblemen - blijft ongeconfigureerd
Instellen van cupsys-common (1.3.0-3ubuntu2) ...
Instellen van libcupsys2 (1.3.0-3ubuntu2) ...

Instellen van libcupsys2-dev (1.3.0-3ubuntu2) ...
Instellen van libcupsimage2 (1.3.0-3ubuntu2) ...

Instellen van libcupsimage2-dev (1.3.0-3ubuntu2) ...
Instellen van cupsys-client (1.3.0-3ubuntu2) ...

Instellen van cupsys-bsd (1.3.0-3ubuntu2) ...

Fouten gevonden tijdens behandelen van:
 cupsys
I DO HAVE gs INSTALLED ON THE SYSTEM (DEFAULT IN UBUNTU). I couldn't find ghostscript in synaptic but i did finf gs interpreters but they want to remove cupsys completely, so i think that is not an option.

[Patrice Vetsel (vetsel-patrice)]

@Till , may be tests can be done under a Gutsy live session ?!

[Martina (m-divertacollini)]

good idea, because cupsys became wrecked (had to be removed and reinstalled, the original one). I am downloading gutsy-desktop-i386.iso and will see what it does when running the live cd session later today.

[Martina (m-divertacollini)]

I used the lice cd but there is no solution yet: the cupsys is "old" and the Dymo was not recognized. The iso was grabbed from http://cdimage.ubuntu.com/releases/gutsy/tribe-3/ Maybe that is not the one with cupsys 1.3.0
Any other options?

[Patrice Vetsel (vetsel-patrice)]

Martina : the latest release is Tribe 5, that you can find here -> http://cdimage.ubuntu.com/releases/gutsy/tribe-5/
Announce -> http://www.ubuntu.com/testing/tribe5

[Till Kamppeter (till-kamppeter)]

Once having booted or installed Tribe 5 you need to install the binary packages from

http://www.linux-foundation.org/~till/tmp/ubuntu/gutsy/cupsys/binary/

Under Tribe 5 (which is a recent development snapshot of Gutsy) these binaries work.

[Till Kamppeter (till-kamppeter)]

Another possibility to install the rebuilt CUPS on Feisty is to do

dpkg -i --force-depends *.deb

This makes the missing "ghostscript" dependency being ignored.

This problem was caused because the former "gs-esp" package from Feisty is replaced by a new "ghostscript" package in Gutsy. CUPS 1.3.0 works also with the old "gs-esp" without any problems.

[Martina (m-divertacollini)]

Hi,
I tried everything once more again but unfortunately:
1 the Dymo printer is not recognized as printer, just as USB device;
2 i thought i found another USB port when i had run the cupsys upgrade to 1.3.0. again, but after installing the Dymo on that port the (garbled) output ended up on the Laserjet and after removing the HP printers, nothing at all happened;
3 i tried live running Gutsy tribe 5 and installing the binary packages as you decribed on 29/8 but there were many error-msgs mostly the not-allowed kind when installing cupsys; i could not get it working and the (live) printer sw was wrecked. The second trial did not succeed as well.
So, back to Feisty and still no Dymo printer. Dymo offered me a brand new trade-in Labelwriter 400 for half price (still expensive when you only use it twice a month or so), which should run with Linux (and Vista and XP; I also have a Vista notebook but not for long because i go back to Xp with that, or maybe Ubuntu).
Bye and thanks for the help.

[Till Kamppeter (till-kamppeter)]

Lets try another thing. A probable problem can be that the printer does not return a device ID and so CUPS cannot create a URI.

So try the following:

Install the original CUPS package to get back to the backend based on the "usblp" kernel module:

sudo dpkg -r --force-depends cupsys
sudo apt-get install cupsys
sudo rm -f /etc/apparmor.d/usr.sbin.cupsd
sudo /etc/init.d/apparmor restart
sudo /etc/init.d/cupsys restart

Load the "usblp" kernel module:

sudo modprobe

With your Dymo printer connected and turned on do

ls -l /dev/usblp*

How many /dev/usblp* files do you get? One per connected printer, including one for the Dymo? Or one less (only for the HPs)?

Do (for each /dev/usblp* file):

cat ~/.bashrc > /dev/usblp0

Do you get page output/blinking lights on your printers? Also on the Dymo?

If one of the files led to a reaction on the Dymo, you will probably be able to print on your Dymo, if not, there is no /dev/usblp* file for the Dymo, which means that the kernel does not identify it as a printer.

If you have found the /dev/usblp* file, you should be able to make your Dymo printing by the following steps:

Edit /etc/cups/cupsd.conf, adding a line "FileDevice Yes".

Restart CUPS:

sudo /etc/init.d/cupsys restart

Set up the print queue:

lpadmin -p Dymo -E -v file:/dev/usblp0 -m lsb/usr/cups-included/Dymo/dymo.ppd

Note that in the "-v" option you have to put the /dev/usblp* file for your Dymo and in the "-m" option an appropriate PPD for your Dymo. Get a list of possible PPDs by

lpinfo -m | grep -i dymo

Now adjust the paper size to your labels with any printer setup tool and you should be able to print.

[Martina (m-divertacollini)]

Remark 1: i do not have apparmor. Should i install it? Output:
martine@ubuntu:~$ sudo rm -f /etc/apparmor.d/usr.sbin.cupsd
martine@ubuntu:~$ sudo /etc/init.d/apparmor restart
sudo: /etc/init.d/apparmor: command not found

2. sudo modprobe only gives hint on how to use it.

3. When looking in Synaptic i see most cupsys packages back to 1.2.8, cupsys-pt is on 1.2.4 but libcupsys2 is version 1.3.0 and libcupsys2-dev is on 1,2,8; this seems a strange mixture to me, but i don't know if it is a problem.

4. there is only one usblp0 and sending something to it results in printing a page on the HP laserjet (i don't see the other HP printer deskjet); so, no dymo.

5. For reference, output of lsusb:
Bus 004 Device 007: ID 03f0:7204 Hewlett-Packard DeskJet 36xx
Bus 004 Device 006: ID 0409:006a NEC Corp. Conceptronic USB Harddisk Box
Bus 004 Device 005: ID 03f0:0217 Hewlett-Packard
Bus 004 Device 003: ID 04b4:6560 Cypress Semiconductor Corp. CY7C65640 USB-2.0 "TetraHub"
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 002: ID 046d:08b2 Logitech, Inc. QuickCam Pro 4000
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 003: ID 0922:0009 Dymo-CoStar Corp. LabelWriter 310
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000

I indeed think that the kernel does not identify the Dymo LW310 as a printer; maybe because the usb is not fully compliant, as Dymo support tells me.
Know anything else to trick the system into believing that there is another printer?