On October 10, 2007, Rishi Oberoi wrote:

Hi Dennis,

Please send me the bug file so as to isolate the issue.

Regards,   Rishi

I am also having the problem that pdf printing stops when graphics are present. I am experiencing this since I upgraded to 10.3, 64bit kernel, and new 64 bit AMD 64x2 CPU and ASUS mainboard. Under 10.2, a 32 bit kernel, Pentium 4 CPU and Acer MB, the same printer (a samsung CLP-510) worked flawlessly. In my case, I am not convinced that the problem is stemming from Adobe Reader, as HTML pages also have this problem of stopping printing on pages with graphics. I have been able to effect a work-around, using KPDF, and in it's print dialog PDF Options tab selecting Force rasterization. When I do this, I am able to print complete documents containing graphics. No other PDF viewer (and I've installed most of the ones available in the various repositories were able to print graphics pages. The one issue that seems most significant to this user is that when printing was working under 10.2, it was working in conjunction with Samsung's unified driver. At that time, the CLP-510 was recognized by the samsung driver to be on the USB port /dev/mfp4. YAST and CUPS seemed to be getting their printer config info from the Samsung driver, as they were set-up in those services after the samsung driver was installed. With 10.3, the Samsung driver is unable to detect the samsung printer on any USB port. Yast, on the other hand, detects and configures the printer on usb://Samsung/CLP-510, and limited printing functionality is then established. Afterward, when I invoke samsung's unified driver configurator, I can see the clp-510 available to the driver on the URI: usb://Samsung/CLP-510. However, the unified driver fails when attempting to test the printer, by failing to detect the printer on the specified usb port. In fact, the unified driver only displays (for configuration) usb ports /dev/mfp0 through /dev/mfp11. It seems that the printer's own driver being unable to see the printer is a bit of a smoking gun. I'm not having much luck trying to troubleshoot the printer configuration in YAST. I'm guessing that usb://Samsung/CLP-510 is some kind of alias? I can't find any hint of it in the filesystem. Here is the output from 'hwinfo --printer' 17: USB 00.0: 10900 Printer [Created at usb.122] UDI: /org/freedesktop/Hal/devices/usb_device_4e8_3260_3761B1BY101171T__if0_printer_noserial Unique ID: Uc5H.oWh6z2eVUF3 Parent ID: k4bc.qorKZhhfFO6 SysFS ID: /devices/pci0000:00/0000:00:0b.1/usb1/1-4/1-4:1.0 SysFS BusID: 1-4:1.0 Hardware Class: printer Model: "Samsung CLP-510" Hotplug: USB Vendor: usb 0x04e8 "Samsung Electronics Co., Ltd" Device: usb 0x3260 "CLP-510 Color Laser Printer" SubVendor: "Samsung" SubDevice: "CLP-510" Revision: "1.00" Serial ID: "3761B1BY101171T." Driver: "usblp" Driver Modules: "usblp" Device File: /dev/usb/lp0 Device Files: /dev/usb/lp0, /dev/usblp0 Device Number: char 180:0 Speed: 480 Mbps Module Alias: "usb:v04E8p3260d0100dc00dsc00dp00ic07isc01ip02" Driver Info #0: Driver Status: usblp is active Driver Activation Cmd: "modprobe usblp" Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #14 (Hub) According to this bug: https://bugzilla.novell.com/show_bug.cgi?id=326319 ( listed as resolved) the use of /dev/usb/lp0 is "outdated since CUPS 1.2 and does no longer work". -- Timothy Cahill 301 Fulford-Ganges Rd. Salt Spring Island, BC, V8K 2K6 250-537-8409 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org