Preventing CUPS from scanning parport

[Dennis Grant]

Hello,

I have a new install of Ubuntu 9.04.

This machine has an LCD display connected to the parport. Whenever I attempt to add a new printer to CUPS (network printer in this case) it appears CUPS is attempting to scan the parport for printers, encounters the LCD display, and dies.

What I would like to do is configure CUPS to not scan the parport - ever. I tried moving the file "parallel" out of /usr/lib/cups/backends and backends-available and restarting CUPS, but that did not work.

Here is the output of /var/log/messages of attempting to add a new printer vi the CGI interface:

 Apr 28 17:09:21 karzai kernel: [264974.352726] Pid: 17570, comm: python Tainted: P           2.6.28-11-generic #42-Ubuntu
Apr 28 17:09:21 karzai kernel: [264974.352732] Call Trace:
Apr 28 17:09:21 karzai kernel: [264974.352751]  [<c0500ac6>] ? printk+0x18/0x1a
Apr 28 17:09:21 karzai kernel: [264974.352764]  [<c0155b74>] set_fail+0x54/0x60
Apr 28 17:09:21 karzai kernel: [264974.352773]  [<c0155e39>] sysctl_check_table+0x129/0x3b0
Apr 28 17:09:21 karzai kernel: [264974.352780]  [<c0155e48>] sysctl_check_table+0x138/0x3b0
Apr 28 17:09:21 karzai kernel: [264974.352788]  [<c0155e48>] sysctl_check_table+0x138/0x3b0
Apr 28 17:09:21 karzai kernel: [264974.352795]  [<c0155e48>] sysctl_check_table+0x138/0x3b0
Apr 28 17:09:21 karzai kernel: [264974.352802]  [<c0155e48>] sysctl_check_table+0x138/0x3b0
Apr 28 17:09:21 karzai kernel: [264974.352809]  [<c0155e48>] sysctl_check_table+0x138/0x3b0
Apr 28 17:09:21 karzai kernel: [264974.352817]  [<c0141c17>] __register_sysctl_paths+0xc7/0x2f0
Apr 28 17:09:21 karzai kernel: [264974.352848]  [<c0141e63>] register_sysctl_paths+0x23/0x30
Apr 28 17:09:21 karzai kernel: [264974.352855]  [<c0141e7f>] register_sysctl_table+0xf/0x20
Apr 28 17:09:21 karzai kernel: [264974.352875]  [<f81e49df>] parport_device_proc_register+0xaf/0xe0 [parport]
Apr 28 17:09:21 karzai kernel: [264974.352890]  [<f81e2909>] parport_register_device+0x149/0x230 [parport]
Apr 28 17:09:21 karzai kernel: [264974.352898]  [<c0502cf8>] ? _spin_lock+0x8/0x10
Apr 28 17:09:21 karzai kernel: [264974.352911]  [<f81e25c4>] ? parport_find_number+0x74/0x90 [parport]
Apr 28 17:09:21 karzai kernel: [264974.352921]  [<f8214356>] register_device+0x86/0xf0 [ppdev]
Apr 28 17:09:21 karzai kernel: [264974.352929]  [<f8214bb0>] ? pp_irq+0x0/0x50 [ppdev]
Apr 28 17:09:21 karzai kernel: [264974.352938]  [<f82147f1>] pp_do_ioctl+0x431/0x7b0 [ppdev]
Apr 28 17:09:21 karzai kernel: [264974.352947]  [<c01d387d>] ? mntput_no_expire+0x1d/0x120
Apr 28 17:09:21 karzai kernel: [264974.352955]  [<f8214b97>] pp_ioctl+0x27/0x40 [ppdev]
Apr 28 17:09:21 karzai kernel: [264974.352963]  [<f8214b70>] ? pp_ioctl+0x0/0x40 [ppdev]
Apr 28 17:09:21 karzai kernel: [264974.352972]  [<c01ca1b8>] vfs_ioctl+0x28/0x90
Apr 28 17:09:21 karzai kernel: [264974.352979]  [<c01ca69e>] do_vfs_ioctl+0x5e/0x200
Apr 28 17:09:21 karzai kernel: [264974.352986]  [<c01ca8a3>] sys_ioctl+0x63/0x70
Apr 28 17:09:21 karzai kernel: [264974.352993]  [<c0103f6b>] sysenter_do_call+0x12/0x2f

Thanks,

DG