dell 1100 laser printer worked in dapper but not in edgy or feisty

Bug #92790 reported by photek
4
Affects Status Importance Assigned to Milestone
udev (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Hi, i have a dell 1100 laser printer that used to work in ubuntu dapper without problems, using the samsung ml-1000 driver. The problem is since edgy the printer usb connection doesn't appear at all in the listing so i can't add it, and the previously added printer from dapper doesn't work anymore.

If i use foomatic it shows the connection but when installing the printer and trying to print test page, the printer appears as not connected.

Thanks in advance for your help.

Regards.

Tags: regression
Revision history for this message
photek (jccelaya) wrote :

tito@tito:~$ uname -a
Linux tito 2.6.20-11-generic #2 SMP Thu Mar 15 03:43:56 UTC 2007 x86_64 GNU/Linux

Tell me if you need more details. I'm using feisty with all the latest updates.

Revision history for this message
Pascal De Vuyst (pascal-devuyst) wrote :

Thanks for your bug report, more information is needed.
Please provide the information described here: https://wiki.ubuntu.com/DebuggingPrintingProblems.

Changed in cupsys:
assignee: nobody → pascal-devuyst
status: Unconfirmed → Needs Info
Revision history for this message
photek (jccelaya) wrote :

Here is the info you requested, take into account that i powered on the printer after booting the system, not before, as i'm not using it usually as it doesn't work. I say that for the message log in case you find it weird.

-------------------------------------------------------------------------------------------------------
tito@tito:~$ lsmod | grep usb
usblp 16768 0
usbhid 29088 0
hid 34048 1 usbhid
usbcore 154416 5 usblp,usbhid,ehci_hcd,ohci_hcd

-------------------------------------------------------------------------------------------------------
tito@tito:~$ tail -f /var/log/messages
Mar 20 10:49:45 localhost hpijs: WARNING: black pen has low ink
Mar 20 10:59:08 localhost kernel: [ 4688.812083] usb 1-3: new full speed USB device using ohci_hcd and address 10
Mar 20 10:59:09 localhost kernel: [ 4688.920017] usb 1-3: configuration #1 chosen from 1 choice
Mar 20 10:59:09 localhost kernel: [ 4688.924465] drivers/usb/class/usblp.c: usblp0: USB Bidirectional printer dev 10 if 0 alt 0 proto 2 vid 0x413C pid 0x5210
Mar 20 10:59:29 localhost kernel: [ 4708.046503] usb 2-5: new high speed USB device using ehci_hcd and address 10
Mar 20 10:59:29 localhost kernel: [ 4708.178775] usb 2-5: configuration #1 chosen from 1 choice
Mar 20 10:59:29 localhost kernel: [ 4708.178939] hub 2-5:1.0: USB hub found
Mar 20 10:59:29 localhost kernel: [ 4708.179125] hub 2-5:1.0: 4 ports detected
Mar 20 11:01:02 localhost kernel: [ 4774.581583] usb 1-3: USB disconnect, address 10
Mar 20 11:01:02 localhost kernel: [ 4774.581659] drivers/usb/class/usblp.c: usblp0: removed
Mar 20 11:02:27 localhost kernel: [ 4839.045319] usb 1-3: new full speed USB device using ohci_hcd and address 11
Mar 20 11:02:27 localhost kernel: [ 4839.260338] usb 1-3: configuration #1 chosen from 1 choice
Mar 20 11:02:27 localhost kernel: [ 4839.269268] drivers/usb/class/usblp.c: usblp0: USB Bidirectional printer dev 11 if 0 alt 0 proto 2 vid 0x413C pid 0x5210

-------------------------------------------------------------------------------------------------------
tito@tito:~$ lpinfo -v
network socket
network beh
network bluetooth
direct hp:/usb/officejet_5500_series?serial=MY418F12PM96
network http
network ipp
network lpd
direct hpfax:/usb/officejet_5500_series?serial=MY418F12PM96
file cups-pdf:/
network smb

Revision history for this message
photek (jccelaya) wrote :

printingbuginfo attached

Revision history for this message
photek (jccelaya) wrote :

I can't post cups error log as i'm not able to use foomatic-gui, it doesn't boot, and that was the only interface that allowed me to add the printer (i deleted it as it didn't work even if detected). I'll try if rebooting does the trick.

Revision history for this message
photek (jccelaya) wrote :

well, even rebooting foomatic-gui doesn't start, it asks me for the admin password but nothing appears. Let me know if i can help you in any other way.

Thanks in advance for your help.

Regards.

Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

Can you please post the output of the commands

ls -l /usr/share/cups/backend
sudo usb_printerid /dev/usblp0
sudo usb_printerid /dev/usblp1
grep -A4 cupsys/backend /var/cache/debconf/config.dat
ls -l /dev/usblp*

and the file

/proc/bus/usb/devices

Revision history for this message
photek (jccelaya) wrote :

Here we go:

---------------------------------------------------------------
tito@tito:~$ ls -l /usr/share/cups/backend
ls: /usr/share/cups/backend: No existe el fichero ó directorio<-- This means file not found.
---------------------------------------------------------------
tito@tito:~$ sudo usb_printerid /dev/usblp0
GET_DEVICE_ID string:
MFG:Dell;CMD:GDI;MDL:Laser Printer 1100;CLS:PRINTER;MODE:GDI;STATUS:IDLE;
---------------------------------------------------------------
tito@tito:~$ sudo usb_printerid /dev/usblp1
GET_DEVICE_ID string:
MFG:hp;MDL:officejet 5500 series;CMD:LDL,MLC,PML,DYN;CLS:PRINTER;1284.4DL:4d,4e,1;SN:MY418F12PM96;S:0380008000020020002c14d0000c2500043;Z:007;
---------------------------------------------------------------
tito@tito:~$ grep -A4 cupsys/backend /var/cache/debconf/config.dat
Name: cupsys/backend
Template: cupsys/backend
Value: ipp, lpd, parallel, socket, usb
Owners: cupsys
Flags: seen
---------------------------------------------------------------
tito@tito:~$ ls -l /dev/usblp*
crw-rw---- 1 root root 180, 0 2007-03-20 11:21 /dev/usblp0
crw-rw---- 1 root root 180, 1 2007-03-20 11:21 /dev/usblp1
---------------------------------------------------------------

Revision history for this message
photek (jccelaya) wrote :

For some reason i can't attach the devices file

Revision history for this message
photek (jccelaya) wrote :

devices files attached.

Revision history for this message
photek (jccelaya) wrote :

By the way, many dell printers are samsung printers repackaged. The Dell 1100 is a Samsung ML-1600, the Dell 1110 is the Samsung ML-1610, etc. Maybe the issue is affecting Samsung printers too.

Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

/usr/share/cups/backend was wrong, I meant

ls -l /usr/lib/cups/backend

Can you post the output of this command?

The ownerships of your /dev/usblp* device files are wrong, the group must be "lp". This affects only the Dell, as the HP is connected via HP's special CUPS backend which does not use the /dev/usblp* device files.

This looks like a problem in UDEV.

Changed in cupsys:
importance: Undecided → Medium
Revision history for this message
photek (jccelaya) wrote :

Here we go:

tito@tito:~$ ls -l /usr/lib/cups/backend
total 240
-rwxr-xr-x 1 root root 7200 2007-03-14 13:57 beh
-rwxr-xr-x 1 root root 12536 2007-02-19 13:41 bluetooth
-rwxr-xr-x 1 root root 15360 2007-03-07 16:13 canon
-rwsr-xr-- 1 root lp 25664 2007-03-02 16:58 cups-pdf
-rwxr-xr-x 1 root root 15352 2007-03-07 16:13 epson
-rwxr-xr-x 1 root root 27832 2007-02-20 21:22 hp
-rwxr-xr-x 1 root root 7612 2007-02-20 21:21 hpfax
-rwxr-xr-x 3 root root 25560 2007-03-15 02:47 http
-rwxr-xr-x 3 root root 25560 2007-03-15 02:47 ipp
-rwsr-xr-- 2 root lp 20464 2007-03-15 02:47 lpd
-rwxr-xr-x 2 root root 15240 2007-03-15 02:47 parallel
lrwxrwxrwx 1 root root 21 2007-03-04 19:14 smb -> ../../../bin/smbspool
-rwxr-xr-x 2 root root 12096 2007-03-15 02:47 socket
-rwxr-xr-x 2 root root 15936 2007-03-15 02:47 usb

So if i change onwership manually (chown...) from root to lp it should work? or it's something that has to be done from udev?

Regards.

Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote :

Please attach /var/log/udev

Revision history for this message
photek (jccelaya) wrote :

sure, here it is. I just powered the printer on again as it was powered off because it doesn't work. powered on when the computer was already working, don't know if it matters.

Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote :

Could you run the following with the printer plugged in, and provide the output

   sudo udevtest /class/usb/lp0

Revision history for this message
photek (jccelaya) wrote :

Hi, with the latest batch of updates i plugged in the printer, it was detected and i could add it as Dell Laser with the gdi driver. And it works!

Here is the output of the command anyway:

tito@tito:~$ sudo udevtest /class/usb/lp0
Password:
parse_file: reading '/etc/udev/rules.d/00-init.rules' as rules file
parse_file: reading '/etc/udev/rules.d/05-options.rules' as rules file
parse_file: reading '/etc/udev/rules.d/20-names.rules' as rules file
parse_file: reading '/etc/udev/rules.d/25-dmsetup.rules' as rules file
parse_file: reading '/etc/udev/rules.d/25-iftab.rules' as rules file
parse_file: reading '/etc/udev/rules.d/30-cdrom_id.rules' as rules file
parse_file: reading '/etc/udev/rules.d/40-permissions.rules' as rules file
parse_file: reading '/etc/udev/rules.d/45-hplip.rules' as rules file
parse_file: reading '/etc/udev/rules.d/45-libgphoto2.rules' as rules file
parse_file: reading '/etc/udev/rules.d/45-libnjb.rules' as rules file
parse_file: reading '/etc/udev/rules.d/45-libsane.rules' as rules file
parse_file: reading '/etc/udev/rules.d/50-xserver-xorg-input-wacom.rules' as rules file
parse_file: reading '/etc/udev/rules.d/60-libpisock.rules' as rules file
parse_file: reading '/etc/udev/rules.d/60-symlinks.rules' as rules file
parse_file: reading '/etc/udev/rules.d/65-libmtp.rules' as rules file
parse_file: reading '/etc/udev/rules.d/65-persistent-input.rules' as rules file
parse_file: reading '/etc/udev/rules.d/65-persistent-storage.rules' as rules file
parse_file: reading '/etc/udev/rules.d/65-wacom.rules' as rules file
parse_file: reading '/etc/udev/rules.d/80-programs.rules' as rules file
parse_file: reading '/etc/udev/rules.d/85-alsa.rules' as rules file
parse_file: reading '/etc/udev/rules.d/85-brltty.rules' as rules file
parse_file: reading '/etc/udev/rules.d/85-hdparm.rules' as rules file
parse_file: reading '/etc/udev/rules.d/85-hplj10xx.rules' as rules file
parse_file: reading '/etc/udev/rules.d/85-hwclock.rules' as rules file
parse_file: reading '/etc/udev/rules.d/85-ifupdown.rules' as rules file
parse_file: reading '/etc/udev/rules.d/85-pcmcia.rules' as rules file
parse_file: reading '/etc/udev/rules.d/90-modprobe.rules' as rules file
parse_file: reading '/etc/udev/rules.d/95-hal.rules' as rules file
parse_file: reading '/etc/udev/rules.d/99-udevmonitor.rules' as rules file
This program is for debugging only, it does not run any program,
specified by a RUN key. It may show incorrect results, if rules
match against subsystem specfic kernel event variables.

main: looking at device '/class/usb/lp0' from subsystem 'usb'
udev_rules_get_name: rule applied, 'lp0' becomes 'usblp0'
run_program: 'check_ptp_camera 06/01/01'
run_program: '/lib/udev/check_ptp_camera' returned with status 1
udev_db_get_device: found a symlink as db file
udev_device_event: device '/class/usb/lp0' already in database, cleanup
udev_node_add: creating device node '/dev/usblp0', major = '180', minor = '0', mode = '0660', uid = '0', gid = '7'
main: run: 'socket:/org/freedesktop/hal/udev_event'
main: run: 'socket:/org/kernel/udev/monitor'
tito@tito:~$

Changed in udev:
assignee: pascal-devuyst → nobody
status: Needs Info → Unconfirmed
Changed in udev:
status: Unconfirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.