Summary: | Duplicate Print Entries using Konqueror | ||
---|---|---|---|
Product: | [Unmaintained] kdeprint | Reporter: | Brat Wizard <bratwizard> |
Component: | general | Assignee: | KDEPrint Devel Mailinglist <kde-print-devel> |
Status: | CLOSED NOT A BUG | ||
Severity: | normal | CC: | jlayt |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Mandrake RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Brat Wizard
2003-02-25 11:08:14 UTC
I don't know exactly what can be the cause of such a problem. The strange thing is that this only happens with konqueror. However any KDE app should behave in the same way against the CUPS server. Did you try other KDE apps like kwrite, kword, kview....? When you start the KDE app in a terminal, can you see debug info on the standard output? If yes, could you send me the debug output when trying to print from konqueror? Michael. Subject: Re: Duplicate Print Entries using Konqueror >The strange > thing is that this only happens with konqueror. > However any KDE app should > behave in the same way against the CUPS server. Did > you try other KDE apps > like kwrite, kword, kview....? Hmm- not sure, I don't generally use those-- use Open Office instead... but I do occasionally have things open in kwrite-- so far no problems printing. However, I've noticed that the problem in Konqueror _seems_ to be related to whether or not there is a graphic on the page. Pages WITHOUT graphics print just fine. Pages WITH graphics have a problem every time. > When you start the > KDE app in a terminal, can > you see debug info on the standard output? If yes, > could you send me the > debug output when trying to print from konqueror? Konqueror does not seem to be reporting any errors that relate to the situation, but here is the output: Loading required GL library /usr/X11R6/lib/libGL.so.1.2 mcop warning: user defined signal handler found for SIG_PIPE, overriding bitBlt: Incompatible destination pixmap kio (KMimeType): WARNING: KServiceType::offers : servicetype application/x-activex-handler not found bitBlt: Incompatible destination pixmap kio (KMimeType): WARNING: KServiceType::offers : servicetype application/x-activex-handler not found kdecore (KAction): WARNING: KActionCollection::KActionCollection( QObject *parent, const char *name, KInstance *instance ) bitBlt: Incompatible destination pixmap kio (KMimeType): WARNING: KServiceType::offers : servicetype application/x-activex-handler not found bitBlt: Incompatible destination pixmap kio (KMimeType): WARNING: KServiceType::offers : servicetype application/x-activex-handler not found bitBlt: Incompatible destination pixmap kio (KMimeType): WARNING: KServiceType::offers : servicetype application/x-activex-handler not found bitBlt: Incompatible destination pixmap bitBlt: Incompatible destination pixmap bitBlt: Incompatible destination pixmap bitBlt: Incompatible destination pixmap kio (KMimeType): WARNING: KServiceType::offers : servicetype application/x-activex-handler not found bitBlt: Incompatible destination pixmap kio (KMimeType): WARNING: KServiceType::offers : servicetype application/x-activex-handler not found bitBlt: Incompatible destination pixmap kio (KMimeType): WARNING: KServiceType::offers : servicetype application/x-activex-handler not found bitBlt: Incompatible destination pixmap kio (KMimeType): WARNING: KServiceType::offers : servicetype application/x-activex-handler not found bitBlt: Incompatible destination pixmap kio (KMimeType): WARNING: KServiceType::offers : servicetype application/x-activex-handler not found Thanks for your time working on the problem. The one other thing-- and this may or may not be relevant-- is that sometimes, when the problem occurs the printer takes an ENORMOUS amount of time to render the page. Before the upgrade, these same pages used to render right away (example: maps.yahoo.com, now takes almost 20 minutes to spit out a page). But if I run it through the PDF filter first and print it from kpdf (or whatever the name of the pdf reader is that comes with konqueror) it prints it out almost immediately. I don't know if that's related or not. But there's definitely something wrong. __________________________________ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo. http://search.yahoo.com Subject: Re: Duplicate Print Entries using Konqueror
To KHTML developers: it seems that at least KHTML is involved. I don't
know why CUPS gets multiple job entries, but the fact that this only
happens with images included makes me think that html rendering has
a part of reponsability.
> However, I've noticed that the problem in Konqueror
> _seems_ to be related to whether or not there is a
> graphic on the page. Pages WITHOUT graphics print just
> fine. Pages WITH graphics have a problem every time.
Can you try to print a page with graphics to a postscript file,
then print it using the "lpr" utility. Do you have the same
problem?
To KHTML developers: is it possible that internally, more than one
KPrinter object is created for printing (this would explain why you
get more than one job: indeed, closing a KPrinter object triggers
the job creation)?
Michael.
Subject: Re: Duplicate Print Entries using Konqueror
On Wednesday 14 May 2003 13:35, Michael Goffioul wrote:
> To KHTML developers: is it possible that internally, more than one
> KPrinter object is created for printing (this would explain why you
> get more than one job: indeed, closing a KPrinter object triggers
> the job creation)?
Is it not rather on sites with frames, than on site with images?
It could be that the action is connected to each frame (KHTMLPart),
so printing the page starts N print jobs, one per frame (KHTMLPart).
Subject: Re: Duplicate Print Entries using Konqueror
> On Wednesday 14 May 2003 13:35, Michael Goffioul wrote:
> > To KHTML developers: is it possible that internally, more than one
> > KPrinter object is created for printing (this would explain why you
> > get more than one job: indeed, closing a KPrinter object triggers
> > the job creation)?
>
> Is it not rather on sites with frames, than on site with images?
> It could be that the action is connected to each frame (KHTMLPart),
> so printing the page starts N print jobs, one per frame (KHTMLPart).
I just tried to print a site with frames (java documentation, KDE-CVS
from last night): when you use the global print action, it only prints
a blank page, just the page title in the header, the content is
empty.
Michael.
Subject: Re: Duplicate Print Entries using Konqueror Not that I'm aware of-- at least I haven't specifically tried that-- in my case, the pages I was printing were all single page (no frame). --- David Faure <dfaure@trolltech.com> wrote: > ------- You are receiving this mail because: ------- > You reported the bug, or are watching the reporter. > > http://bugs.kde.org/show_bug.cgi?id=55146 > > > > > ------- Additional Comments From > dfaure@trolltech.com 2003-05-14 13:56 ------- > Subject: Re: Duplicate Print Entries using > Konqueror > > On Wednesday 14 May 2003 13:35, Michael Goffioul > wrote: > > To KHTML developers: is it possible that > internally, more than one > > KPrinter object is created for printing (this > would explain why you > > get more than one job: indeed, closing a KPrinter > object triggers > > the job creation)? > > Is it not rather on sites with frames, than on site > with images? > It could be that the action is connected to each > frame (KHTMLPart), > so printing the page starts N print jobs, one per > frame (KHTMLPart). __________________________________ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo. http://search.yahoo.com I have recently upgraded to Mandrake 9.1, stock version. And I am still having this problem.... takes forever to render html pages with images, and won't stop printing the page until the cups queue is manually emptied and cups restarted. Has any progress been made on this issue? Subject: Re: Duplicate Print Entries using Konqueror
> I have recently upgraded to Mandrake 9.1, stock version. And I am still having
> this problem.... takes forever to render html pages with images, and won't
> stop printing the page until the cups queue is manually emptied and cups
> restarted.
>
> Has any progress been made on this issue?
No because no-one seems able to reproduce it. Looking at the bug report,
the 'x-activex-handler' stuff triggered my attention. I wonder where
it comes from, but from the debug output, it seems related to image
rendering. Do you still have similar debug output? Can you do a
find $KDEDIR/share -name \*.desktop | xargs grep 'x-activex'
to see where it could come from.
Michael.
UNCONFIRMED (batch reassigning messed this) Two years old. Never reproduced. Original reporter didn't answer to last (May2003) question. Konqueror/KHTML changed a lot in the meantime. I close as invalid. If reproduced, ask for reopening. Closing old Resolved status bug. |