Bug 84043 - the printer Lexmark X 1160 does not print
Summary: the printer Lexmark X 1160 does not print
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: 2004-06-26 20:13 UTC by Marco
Modified: 2008-12-31 17:28 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marco 2004-06-26 20:13:15 UTC
Version:           0.1 (using KDE 3.2.1, SuSE)
Compiler:          gcc version 3.3.3 (SuSE Linux)
OS:                Linux (i686) release 2.6.5-7.75-default

when I give the command to print with openoffice, Kword or even the KDE program the printer does not respond (does not event switch on!!!).
Comment 1 Michael Goffioul 2004-06-27 20:07:04 UTC
You should make sure that a non-KDE program can print. For example try to test your printer from the CUPS web interface at http://localhost:631. Otherwise your problem is more general than a kdeprint problem.

Michael.
Comment 2 Cristian Tibirna 2005-09-24 06:29:19 UTC
waiting for the answer. Can the printer print other than with KDE?
Comment 3 Marco 2005-10-09 23:06:45 UTC
---------- Initial Header -----------

From      : owner@bugs.kde.org
To          : attela@libero.it
Cc          :
Date      : 24 Sep 2005 04:29:23 -0000
Subject : [Bug 84043] the printer Lexmark X 1160 does not print







[bugs.kde.org quoted mail]
obviously it works with winxp. I recently changed the system with Debian, and I have not yet tested the printer. once I will do it I will report the result.
Comment 4 Chris Howells 2006-05-30 02:37:15 UTC
Did you have a chance to try the printer?
Comment 5 Kurt Pfeifle 2007-01-13 06:45:17 UTC
Timeout now, reporter didn't respond to Chris' question for more than half a year [006-05-30 02:37].
Comment 6 John Layt 2008-12-31 17:28:21 UTC
Closing old Resolved status bug.