Bug 151999 - printer hp 1320 will not print under suse 10.3
Summary: printer hp 1320 will not print under suse 10.3
Status: CLOSED NOT A BUG
Alias: None
Product: kdeprint
Classification: Applications
Component: kjobviewer (show other bugs)
Version: 0.1
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: KDEPrint Devel Mailinglist
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-11-08 01:51 UTC by boonzajer
Modified: 2008-12-31 20:57 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description boonzajer 2007-11-08 01:51:14 UTC 
Version:           0.1 (using KDE 3.5.7 "release 72.2" , openSUSE 10.3)
Compiler:          Target: i586-suse-linux
OS:                Linux (i686) release 2.6.22.9-0.4-default

The usb connected HP 1320 printer will not output. It is connected, can print a 'hello world' page, and no matter how I install it - nothing moves. The print job viewer shows the print job as 'under process.' The printer worked fine under suse 10.2, and has developed this bug some time after upgrading tot 10.3. Printer will work when I redirect the print job via a networked windows computer. I then have to manually start the printer for each job.
Comment 1 Cristian Tibirna 2007-11-08 12:30:42 UTC 
Does it print from other applications, like OpenOffice, Firefox or Gnome?
Comment 2 boonzajer 2007-11-08 16:54:53 UTC 
It does not print from any program. Tried OpenOffice, Thunderbird,
Firefox and YaST directly as a print test. Nothing, Does not print from
Gnome either. Worked fine under Suse 10.2 (both KDE and Gnome), worked
for a short time under 10.3, then stopped. Got the most recent CUPS
drivers installed yesterday - no avail.

Hoping for help,

Sincerely,

Robert

Cristian Tibirna wrote:
[bugs.kde.org quoted mail]
Comment 3 Tommi Tervo 2007-11-08 17:27:19 UTC 
Then this is not KDE problem, please report to OpenSuse bug tracking system.
Comment 4 John Layt 2008-12-31 20:57:12 UTC 
Closing old Resolved status bug.