| Summary: | Problem with cups | ||
|---|---|---|---|
| Product: | [Unmaintained] kdelibs | Reporter: | dan <dan_blm> |
| Component: | print-dialog | Assignee: | KDEPrint Devel Mailinglist <kde-print-devel> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | andrew.crouthamel, cfeck, m.weghorn, matija |
| Priority: | NOR | Keywords: | triaged |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Gentoo Packages | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
dan
2010-06-16 02:25:26 UTC
Just to make sure I understand what you are doing. On KWord, you print to a file, on Firefox, you directly print to the printer? In both cases I print to the printer. When I print from kword and kwrite it provides the pdf error, from cups from firefox no. This all started when I printed one document to pdf from the kword dialog (choosing pdf) and now provides the indicated error, printing to the printer, and I do not know how to (readily) get around it. I have another kde system which works fine so no emergency so far; plus I think I can print to the printer from Okular but I did not try this. Where is the kword/kwrite set up file? Thanks for your interest Dan Blum --- On Mon, 6/21/10, Christoph Feck <christoph@maxiom.de> wrote: > From: Christoph Feck <christoph@maxiom.de> > Subject: [Bug 241873] Problem with cups > To: dan_blm@yahoo.com > Date: Monday, June 21, 2010, 12:51 PM > https://bugs.kde.org/show_bug.cgi?id=241873 > > > Christoph Feck <christoph@maxiom.de> > changed: > > What > |Removed > |Added > ---------------------------------------------------------------------------- > > CC| > > |christoph@maxiom.de > > > > > --- Comment #1 from Christoph Feck <christoph maxiom > de> 2010-06-21 19:51:24 --- > Just to make sure I understand what you are doing. On > KWord, you print to a > file, on Firefox, you directly print to the printer? > > -- > Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You reported the bug. > @dan: This bug report is quite old. Is this still a problem for you? (In reply to Michael Weghorn from comment #3) > @dan: This bug report is quite old. Is this still a problem for you? I'm setting the bug status to NEEDSINFO for now, since the question has not been answered yet. Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! I haven’t noticed this bug in a while now. I am not the original bug reporter though. Ok, I'll mark this resolved. If there is still an issue, please re-open. :) |