Bug 129954

Summary:	I started two jobs by accident but although I'd stopped one of them it in print manager jobs it still printed I then killed the other and that didnt stop printer printing Its a EPson 1290
Product:	[Unmaintained] kdeprint	Reporter:	michael Sansom <Michaelsansom>
Component:	kjobviewer	Assignee:	KDEPrint Devel Mailinglist <kde-print-devel>
Status:	CLOSED FIXED
Severity:	normal	CC:	jlayt
Priority:	NOR
Version:	0.1
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description michael Sansom 2006-06-28 11:42:29 UTC

Version:           0.1 (using KDE 3.5.2, Mandriva Linux i586)
Compiler:          Target: i586-mandriva-linux-gnu
OS:                Linux (i686) release 2.6.12-19mdk

As stated above I accidentally entered two Jobs for same document because of slow printer responce. If it had been quicker to respond I would not have started a new print job. But them I tried to stop surplus print job it did not do it so i tried to stop the second print job and that was a waste of time. I am used to the responce times in windows and forgot it takes for ever for the printer to set up in Mandriva but never the less for the print manager not be able to stop a print job could be expensive especially you using expensive inks and paper as one uses in Photography. I have experienced this before several times in Mandriva 2005 and 2006 and Christmas edition 2006 now the Kiosk version. PS my printer works OK in windows XP ( I know this hurts but its not my printer:-) )

Comment 1 michael Sansom 2006-06-28 11:51:04 UTC

I don't follow the comments below leave unconfirmed and resolved (if your the reporter) as the reporter how do I second guess its resolved by just reporting you may not have any success in curing it. Perception is obvious to those who know the language but when your an ordinary mortal it might just as well be from out of space. I suffer for Augsburg's syndrom please be patent.

Regards Mike Sansom

Comment 2 Kurt Pfeifle 2007-01-13 06:37:45 UTC

*** Bug has been marked as fixed ***.

Comment 3 John Layt 2008-12-31 20:11:12 UTC

Closing old Resolved status bug.