| Summary: | Konqueror and Kmail hang on printing | ||
|---|---|---|---|
| Product: | [Unmaintained] kdeprint | Reporter: | mal <malcolm> |
| Component: | general | Assignee: | Michael Goffioul <kdeprint_bugs> |
| Status: | CLOSED FIXED | ||
| Severity: | normal | CC: | Dieter, grueni75, jlayt, patrakov, sean.clarke, sombragris, term |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
mal
2004-01-20 17:51:37 UTC
it's hanging in Qt and you're using a pre 3.3 Qt. Subject: Re: Komqueror and Kmail hang on printing I just installed Suse 9.0 from the DVD and then downloaded all of the rpms and did a rpm -ivh --force -nodeps * How has it gone wrong ? best wishes mal On Tuesday 20 January 2004 19:17, Stephan Kulow wrote: > ------- You are receiving this mail because: ------- > You reported the bug, or are watching the reporter. > > http://bugs.kde.org/show_bug.cgi?id=73041 > coolo@kde.org changed: > > What |Removed |Added > --------------------------------------------------------------------------- >- AssignedTo|konq-bugs@kde.org |null@kde.org > Severity|crash |normal > Component|general |qt > Product|konqueror |kdelibs > > > > ------- Additional Comments From coolo@kde.org 2004-01-20 20:17 ------- > it's hanging in Qt and you're using a pre 3.3 Qt. "--force -nodeps" and you expect it to works!? *** Bug 73279 has been marked as a duplicate of this bug. *** No, it's not hanging in Qt. This Bug is also present if Qt 3.3 is installed. If you start kmail or konqueror from console and try to print, you get the following error message: WARNING: KFilterBase::findFilterByExtension : no filter found for text/plain *** Bug 73317 has been marked as a duplicate of this bug. *** *** Bug 73350 has been marked as a duplicate of this bug. *** I am having this same bug on a system with a fresh install of Suse 9.0. I installed by removing conflicting rpm packages and doing an rpm -Uvh * I've seen the issue in both kmail and konqueror. The problem only occurs when attempting to print to a printer, printing to a pdf or a postscript file work fine. Can we raise the priority of this? The ability to print must surely be critical to any release. I notice that we all are SUSE based, could it be a package/library incompatibility/issue? Anyone seen this on a non SUSE system? various people see it on debian system (both the muesli CVS packages and self built) greetings, frank all with qt 3.3 development versions, right? Because for the suse packages reverting part of the 3.3 development back to 3.2 fixed the problem. Not sure... however your comments has highlighted something.... On my SUSE 9.0 installation I have:- qt3-3.3.0-24 qt3-devel-3.3.0-24 qt3-devel-doc-3.3.0-24 qt3-devel-tools-3.3.0-24 qt3-examples-3.2.3-1 qt3-extensions-3.3.0-24 qt3-man-3.3.0-24 qt3-mysql-3.3.0-24 qt3-non-mt-3.3.0-25 qt3-postgresql-3.3.0-24 qt3-static-3.2.3-6 qt3-unixODBC-3.3.0-24 and on my SUSE 8.2 installation I have :- qt3-3.3.0-24 qt3-devel-3.3.0-24 qt3-devel-doc-3.3.0-24 qt3-devel-tools-3.2.3-1 qt3-examples-3.2.3-1 qt3-extensions-3.2.3-1 qt3-man-3.2.3-1 qt3-mysql-3.2.3-1 qt3-non-mt-3.3.0-24 qt3-postgresql-3.2.3-1 qt3-static-3.3.0-23 qt3-unixODBC-3.2.3-1 Strange mix of 3.3.0 and 3.2.3. I also reported #bug 73096 (kdevelop fails on startup). could this inconsistency in library versions also be the cause? I'm going to give the Fedora version a go - I'll let you know later today BTW and interesting thing happend last night - I shut the machine down which I haven't done since I originally reported the problem and the as the machine shut down the missing pages came out of the printer - which is even odder because I've printed lots of other stuff since then - where was it hiding :-) Subject: Re: Konqueror and Kmail hang on printing On Tuesday 27 January 2004 4:46 am, Sean Clarke wrote: > ------- You are receiving this mail because: ------- > You are on the CC list for the bug, or are watching someone who is. > You are a voter for the bug, or are watching someone who is. > > http://bugs.kde.org/show_bug.cgi?id=73041 > > > > > ------- Additional Comments From sean.e.clarke@ntlworld.com 2004-01-27 > 13:46 ------- Can we raise the priority of this? The ability to print must > surely be critical to any release. > > I notice that we all are SUSE based, could it be a package/library > incompatibility/issue? > > Anyone seen this on a non SUSE system? I am on Debian Unstable using third-party KDE CVS debs. Michael, I commited a fix to HEAD. Please backport if it's fine and close the bug report Can you give a brief explanation of the problem Stephan? Subject: kdelibs/kdeprint
CVS commit by coolo:
This little test case gives 756.0 with qt 3.2 and 0 with qt-copy
QString f("756\"");
qDebug("f %f", f.toFloat());
This leads to the unfortunate suprise that cups printers are labeled
to have 0 points high pages - which gives khtml a hard time trying to
find the right number of pages
CCMAIL: 73041@bugs.kde.org
M +2 -1 ppdloader.cpp 1.4
--- kdelibs/kdeprint/ppdloader.cpp #1.3:1.4
@@ -84,5 +84,6 @@ static QValueList<float> splitNumberStri
else
{
- l.append( s.mid( p1 ).toFloat() );
+ // ignore the final quote
+ l.append( s.mid( p1, s.length() - p1 - 1 ).toFloat() );
break;
}
Tried Fedora - Konqueror crashes - though it sound like you are on to this already but I have attached the backtrace in case it helps bests wishes mal (no debugging symbols found)...Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...[Thread debugging using libthread_db enabled] [New Thread -1084521120 (LWP 4120)] (no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...0x00670c32 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2 #0 0x00670c32 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2 #1 0x0091c963 in __waitpid_nocancel () from /lib/tls/libpthread.so.0 #2 0x004e44e1 in KCrash::defaultCrashHandler(int) () from /usr/lib/libkdecore.so.4 Subject: KDE_3_2_BRANCH: kdelibs/kdeprint CVS commit by coolo: fixing problem that shows up when using Qt 3.3 CCMAIL: 73041-done@bugs.kde.org M +2 -1 ppdloader.cpp 1.3.2.1 --- kdelibs/kdeprint/ppdloader.cpp #1.3:1.3.2.1 @@ -84,5 +84,6 @@ static QValueList<float> splitNumberStri else { - l.append( s.mid( p1 ).toFloat() ); + // ignore the final quote + l.append( s.mid( p1, s.length() - p1 - 1 ).toFloat() ); break; } *** Bug 73683 has been marked as a duplicate of this bug. *** *** Bug 74809 has been marked as a duplicate of this bug. *** Can confirm fix in KDE 3.2. Verified using SuSE 9.0 and 8.2 RPMs. *** Bug 76069 has been marked as a duplicate of this bug. *** I am the reporter for bug 76069 -- sorry for the dupe and thanks for taking care of this. Eduardo Closing old Resolved status bug. |