#585646 konqueror: does not display html

Package:
konqueror
Source:
konqueror
Description:
advanced file manager, web browser and document viewer
Submitter:
Michal Suchanek
Date:
2010-08-04 15:27:06 UTC
Severity:
normal
#585646#5
Date:
2010-06-12 17:44:26 UTC
From:
To:
For me konquerror does not display HTML pages. It says this in
the window:

The requested operation could not be completed
Unexpected Program Termination
Details of the Request:
URL: http://www.debian.org
Protocol: http
Date and Time: Saturday 12 June 2010 19:41
Additional Information: http://www.debian.org
Description:
The program on your computer which provides access to the
http://www.debian.org protocol has unexpectedly terminated.
Possible Causes:
This is most likely to be caused by a bug in the program. Please
consider submitting a full bug report as detailed below.
Possible Solutions:
Update your software to the latest version. Your distribution should
provide tools to update your software.
When all else fails, please consider helping the KDE team or the third
party maintainer of this software by submitting a high quality bug
report. If the software is provided by a third party, please contact
them directly. Otherwise, first look to see if the same bug has been
submitted by someone else by searching at the KDE bug reporting website.
If not, take note of the details given above, and include them in your
bug report, along with as many other details as you think might help.


and logs this on the console:

$ konqueror http://www.debian.org
konqueror(30235)/kdecore (KLibrary) findLibraryInternal: plugins should
not have a 'lib' prefix: "libkhtmlpart.so"
konqueror(30235)/kdecore (KLibrary) findLibraryInternal: plugins should
not have a 'lib' prefix: "libkhtmlpart.so"
konqueror(30235)/kdecore (KLibrary) kde4Factory: The library
"/usr/lib/kde4/libkhtmlpart.so" does not offer a qt_plugin_instance
function.

I upgraded from 4.3 to 4.4 but the problem persists.

#585646#12
Date:
2010-06-14 18:22:27 UTC
From:
To:
Hello,

This probably means that /usr/lib/kde4/kio_http.so does not load.

These warnings are not critical at all and they should not be the reason of
the failures.

Your system is misconfigured and likely half-upgraded. You have "5.0.4" as
debian version but you seem to run some sort of stable/testing/unstable mix.
This is not supported. Please choose one flavour and dist-upgrade fully to it.
This is one of the reasons why severity of the bug was downgraded.

#585646#19
Date:
2010-06-16 18:32:17 UTC
From:
To:
AFAICT the konqueror dependencies are installed from testing (or
unstable in the case of kde libs which I tried to upgrade to 4.4 for
the test).

I don't see this as a misconfiguration.

Thanks

Michal

#585646#24
Date:
2010-06-16 21:06:38 UTC
From:
To:
severity 585646 normal
tags 585646 unreproducible
thanks

Hello,

At very least your base system is outdated. Failure is weird and points
towards problem with base installation. You are free to use whatever you
believe is OK, but we cannot support every weird mix out there. Sorry.

#585646#31
Date:
2010-08-04 15:23:51 UTC
From:
To:
Just FYI, I had the same sort if problem after upgrading konqueror
to unstable on a "mixed" system. It turned out that in my case, the
reason was that there were still old "kdeinit4: ..." processes
running, even though I had exited konqueror, and after killing those
processes manually everything worked fine.

Maybe that information helps someone else stuck with the same problem.

Two suggestions:

1) One the "Unexpected Program Termination" page, include information
that more information may be found in .xsession-errors. I found that
hinted at after some googling, and it contained the line

symbol lookup error: /usr/lib/kde4/kio_http.so:
undefined symbol: _ZN6KDebug13hasNullOutputE9QtMsgTypebib

which in turn lead me to the two versions of libkdecore.so, and
apparently the running kdeinit4 used the wrong one when launching
the http-process.

The information currently given on that page isn't particularly
helpful when trying to pin down the error.

2) Consider removing and/or restarting the kdeinit4-processes
as part of the upgrade process, if at all safely possible.