| Summary: | Crash when changing browser engine from WebKit to KHTML | ||
|---|---|---|---|
| Product: | [Frameworks and Libraries] kwebkitpart | Reporter: | Graeme Hewson <bugs> |
| Component: | general | Assignee: | webkit-devel |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | crash | CC: | adawit, christian_weilbach |
| Priority: | NOR | ||
| Version: | 1.1 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Graeme Hewson
2012-08-27 09:47:12 UTC
Could you please install all debugging symbols, including those for kwebkit and provide a better backtrace? See also techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports When I click on "Install Debug Symbols" in drkonqui, after a while I get a popup message saying "Could not find debug symbol packages for this application". I think this might have happened when I posted this bug. How should I proceed? It looks as though I already have the debug package for kwebkit: wajig list webkit ii kpart-webkit 1.1.0git80efcf77-1 WebKit KPart ii libkdewebkit5 4:4.9.0a-0ubuntu1~precise1~ppa1 KDE WebKit Library ii libqtwebkit4 2.2.1-1ubuntu4 Web content engine library for Qt ii libqtwebkit4-dbg 2.2.1-1ubuntu4 Web content engine library for Qt - debugging symbols ii libqtwebkit-dev 2.2.1-1ubuntu4 Web content engine library for Qt - development files ii libwebkitgtk-1.0-0 1.8.1-0ubuntu0.12.04.1 Web content engine library for GTK+ ii libwebkitgtk-1.0-0-dbg 1.8.1-0ubuntu0.12.04.1 Web content engine library for GTK+ - Debugging symbols ii libwebkitgtk-1.0-common 1.8.1-0ubuntu0.12.04.1 Web content engine library for GTK+ - data files ii libwebkitgtk-3.0-0 1.8.1-0ubuntu0.12.04.1 Web content engine library for GTK+ ii libwebkitgtk-3.0-0-dbg 1.8.1-0ubuntu0.12.04.1 Web content engine library for GTK+ - Debugging symbols ii libwebkitgtk-3.0-common 1.8.1-0ubuntu0.12.04.1 Web content engine library for GTK+ - data files rc libkwebkit1 0.9.6-0ubuntu3 KDE bindings for WebKit You apparently need to install the package called kpart-webkit-dbg, as kwebkitpart is the one not showing any debugging information in your backtrace:
> #8 0x00007fe96b6f66ff in ?? () from /usr/lib/kde4/kwebkitpart.so
> #9 0x00007fe96b6f2534 in ?? () from /usr/lib/kde4/kwebkitpart.so
> #10 0x00007fe96b6f259d in ?? () from /usr/lib/kde4/kwebkitpart.so
> #11 0x00007fe96b6e82d2 in ?? () from /usr/lib/kde4/kwebkitpart.so
> #12 0x00007fe96b6e834a in ?? () from /usr/lib/kde4/kwebkitpart.so
I guess that package isn't included in the Kubuntu 4.9.0 PPA. I'll see what I can do when the next release of Kubuntu is out. I have the package here, with exactly that name, check again :) Of course, it is probably the backports ppa if you use Kubuntu 12.04 $ dpkg-query -W 'kpart-webkit*' kpart-webkit 1.1.0git80efcf77-1 I followed the instructions at http://www.kubuntu.org/news/kde-sc-4.9 when installing 4.9.0, that is to add the repository ppa:kubuntu-ppa/backports. Apparently this is only available since Quantal then, sorry for the noise.. *** Bug 306684 has been marked as a duplicate of this bug. *** Confirmed by duplicate Raised bug for Kubuntu (https://bugs.launchpad.net/kubuntu-ppa/+bug/1051540). Followed the procedure in https://wiki.ubuntu.com/DebuggingProgramCrash, but can't find kpart-webkit-dbgsym either. First bug 306684 is really not a duplicate of this bug. See that bug report for the details. Secondly, the first thing I would do is remove the vestiages of the old kwebkitpart left over from the 0.9.6 era. Namely the following package from your system: > rc libkwebkit1 0.9.6-0ubuntu3 KDE bindings for WebKit And see if that resolves the issue for you. Unfortunately, there is nothing we can do if the distro won't provide a debug version of the package for you. All I can tell you is that I cannot reproduce this crash using kwebkitpart v1.3.0 which is the latest stable version. I still get the crash in 4.9.2, and I still can't get the debug symbols. Anyway, thanks for investigating. If you can't reproduce the crash with the latest stable version, that's good enough for me. Closing the ticket. *** Bug 306684 has been marked as a duplicate of this bug. *** |