Summary: | konqueror crashes after clinking the link on page | ||
---|---|---|---|
Product: | [Applications] konqueror | Reporter: | Anton <selecter> |
Component: | khtml | Assignee: | Konqueror Developers <konq-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | ||
Priority: | NOR | ||
Version First Reported In: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Gentoo Packages | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Anton
2004-02-04 23:43:47 UTC
Please help us: http://konqueror.kde.org/investigatebug/ I did everyting that you asked already... <from investigate bug> Konqueror crashes The most useful information you can provide in that case is a backtrace, but you need to compile KDE yourself (preferrably with --enable-debug) so the backtrace is useful, or to use development packages. Official binary packages are "stripped", so they don't contain any useful information for a backtrace. Simply paste the backtrace from DrKonqi, into the bugreport. Very important: a backtrace is good, but it's not enough. You must also describe on which site it happened, and which steps one should follow to reproduce the crash. </from investigate bug> Your back trace is still with stripped debug infos. And your clickery works for me. Ok. Then it must be Gentoo problem... check out #73311 My friend confirms the crash on slackware 9.1 with 2.4.24 kernel, gcc 3.2.3, using binary packages. I will recompile konq later... I recompiled kdelibs and kdebase with --enable-debug... What else should I compile to get full backtrace? I don't want to recompile whole kde... It's too long. *** This bug has been marked as a duplicate of 73311 *** Ok. Help yourself then! for the next crash your recompilations will be worth it |