On Sun, Apr 20, 2008 at 4:37 PM, dracon <picky2k@yahoo.com> wrote:

Hi. I'll try this off the launchpad bug forum since I'm not at all sure it will work for you and don't want to spread any nonsense further than required.
I'm dracon on the launchpad and I was able to get past my cups problem bu "forcing" a printer ID.

Here is what you might try. At least it's easy and worth a shot.
Go to System/Administration/Printing> click the New Printer button to add a new printer...Don't mess with your normal set up just leave well enough alone there.

When you get the available printers selection pane select "Other"
and in the URI field put the exact ID of your cable (copy/paste). From your note that would be:

hal:///org/freedesktop/Hal/devices/usb_device_4b8_5_M01P20511302159560_if0_printer_noserial

Click forward and select the appropriate device driver for your printer, and continue to set the "new" printer up normally..new name and human description, but leave the default location alone.

This should add a new printer presence named (Different-Name?) to your
printer list.

Try printing to that printer, make it default, see if it is able to reconnect.
This worked for me with a legacy HP4 that cups found about 50% of the time..Now it doesn't fail and I can recover print jobs if the printer is unplugged and re plugged.

If this works please let me know. Maybe we can point the Cups/Hal folks
to a particular problem or give some bypass suggestionto the bug forum.
(if it does not work le me know that too)

Bill

quixote <commer@greenglim.com> wrote: I'm suddenly having major issues with my USB-connected printer. I have

a Sharp MP30 laptop (from 2005), Epson Stylus Photo R220 printer, and
running Hardy 8.04 with all updates applied as of Apr 20. (As a user,
not a developer, I don't know what the problem really is or whether this
is the correct thread.)

Before I read this thread, this was the problem: after a cold start,
everything worked, but after suspend, the system thought the printer was
"unplugged." Other USB devices, like a thumbdrive, would not work
either. I have two USB ports, and either one would become nonfunctional
after trying to talk to the printer. Restarting cupsys, restarting X,
nothing worked. Only a complete shutdown and boot up made the USB ports
available again.

After I read this thread and tried some of the diagnostics after
suspending, it turned out that $lsusb or $lpinfo -v somehow woke the
port back up and it would print. So what's the deal?? Any command to
poll the printer or usb reminds the system of something and everything
works again??

Bizarre. I hope I'm not the only person with this problem and it's
something that can get sorted out. I've been using Ubuntu since Dapper,
and this is the first time anything like this has happened.

Some of the output from diagnostics:
-----------------------
Cold boot, printing via usb cable works:
-----------------------
$lsusb
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 002: ID 04b8:0005 Seiko Epson Corp. Stylus Printer
Bus 001 Device 001: ID 0000:0000

$sudo usb_printerid /dev/usb/lp0
GET_DEVICE_ID string:
MFG:EPSON;CMD:ESCPL2,BDC,D4;MDL:Stylus Photo R220;CLS:PRINTER;DES:EPSON Stylus Photo R220;

$lpinfo -v
network socket
network beh
direct hal:///org/freedesktop/Hal/devices/usb_device_4b8_5_M01P20511302159560_if0_printer_noserial
direct usb://EPSON/Stylus%20Photo%20R220
direct epson:/dev/usb/lp0
direct hpfax
direct hp
network http
network ipp
network lpd
file cups-pdf:/
direct scsi
network smb

------------------------
after suspend: printer and/or usb no longer works
------------------------
$lsusb
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000

HOWEVER: this time, after running lsusb, the printer woke up and started
printing the job I'd just given it. In the past, besides restarting X,
I'd also tried restarting cupsys service and everything else I could
think of.

Now the output is
$lsusb
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 003: ID 04b8:0005 Seiko Epson Corp. Stylus Printer
Bus 001 Device 001: ID 0000:0000

------------------------------
another suspend: printer not working at first
------------------------------
$lpinfo -v
network socket
network beh
direct hal:///org/freedesktop/Hal/devices/usb_device_4b8_5_M01P20511302159560_if0_printer_noserial
direct usb://EPSON/Stylus%20Photo%20R220
direct epson:/dev/usb/lp0
direct hpfax
direct hp
network http
network ipp
network lpd
file cups-pdf:/
direct scsi
network smb

and it started printing the job I'd just given it....

--
Printer is not detected properly over USB
https://bugs.launchpad.net/bugs/35638
You received this bug notification because you are a direct subscriber
of the bug.

Status in Source Package "cupsys" in Ubuntu: Confirmed
Status in Source Package "linux-source-2.6.15" in Ubuntu: Won't Fix
Status in Source Package "linux-source-2.6.17" in Ubuntu: Won't Fix
Status in Source Package "linux-source-2.6.20" in Ubuntu: Won't Fix
Status in cupsys in Ubuntu Hardy: Confirmed
Status in linux-source-2.6.15 in Ubuntu Hardy: Won't Fix
Status in linux-source-2.6.17 in Ubuntu Hardy: Won't Fix
Status in linux-source-2.6.20 in Ubuntu Hardy: Won't Fix

Bug description:
Description of the problem:
I have a Brother HL1050 that was detected properly in breezy but does not seem to be in dapper.

Steps to reproduce the problem:
1. Plug printer into usb slot and turn the printer on.
2. Run gnome-cups-add .

Expected results:
Printer to be detected and shown under "Use a detected printer:". Printer manufacturer to be displayed in Printer Port dropdown.

Actual rsults:
"No printer detected" is displayed under Use a detected printer. "USB Printer #1 (CANON)" "USB Printer #1 (EPSON)" are displayed in Printer Port dropdown.

---------------------------------
Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now.

** Attachment added: "unnamed"
http://launchpadlibrarian.net/13590102/unnamed

--
Printer is not detected properly over USB
https://bugs.launchpad.net/bugs/35638
You received this bug notification because you are a direct subscriber
of the bug.