Version: 0.6.0 (using KDE 4.5.1) OS: Linux type in lists.kde.org in address bar and press enter. Rekonq crashes each and every time without showing contents of the page. :-( Reproducible: Always Steps to Reproduce: see above Actual Results: and see above. A lot of superfluous steps in the bug reporting tooling? Expected Results: guess... and guess again
> A lot of superfluous steps in the bug reporting tooling? It looks like you did not use the DrKonqi crash dialog, because then you would have added the backtrace. If the crash is reproducible, please add the backtrace. For more information, see http://techbase.kde.org/User:DarioAndres/How_to_provide_more_information_about_crash_reports
In all the many crashes I experience with kde4.5 and its applications, the backtrace tool claims it does not produce a useful backtrace and it is not worth filing a bug report. So perhaps it looks like I need to install more software, not like I did not use the crash dialog. I will see what libraries I need to install. But it would be useful to know if you could reproduce the crash. Can you try and report here? If you can reproduce it, I guess there is no need for me to install extra stuff. On Thursday 30 September 2010 14:31:07 Christoph Feck wrote: > https://bugs.kde.org/show_bug.cgi?id=252847 > > > Christoph Feck <christoph@maxiom.de> changed: > > What |Removed |Added > --------------------------------------------------------------------------- > - Status|NEW |NEEDSINFO > CC|john@van-spaandonk.nl |christoph@maxiom.de > Resolution| |BACKTRACE > > > > > --- Comment #1 from Christoph Feck <christoph maxiom de> 2010-09-30 > 14:31:06 --- > > > A lot of superfluous steps in the bug reporting tooling? > > It looks like you did not use the DrKonqi crash dialog, because then you > would have added the backtrace. > > If the crash is reproducible, please add the backtrace. For more > information, see > http://techbase.kde.org/User:DarioAndres/How_to_provide_more_information_ab > out_crash_reports
You don't need additional libraries, but "debug" packages. If unsure, ask in an Archlinux forum how to install them. Note that rekonq uses QtWebKit, and most distributions do not ship debug packages for QtWebKit, because of the large size, so don't expect a perfect backtrace. And I cannot reproduce. That's why a backtrace (even with some missing symbols) would be fine.
On 10/01/2010 01:09 PM, Christoph Feck wrote: > https://bugs.kde.org/show_bug.cgi?id=252847 > > > > > > --- Comment #3 from Christoph Feck<christoph maxiom de> 2010-10-01 13:09:58 --- > You don't need additional libraries, but "debug" packages. If unsure, ask in an > Archlinux forum how to install them. > > Note that rekonq uses QtWebKit, and most distributions do not ship debug > packages for QtWebKit, because of the large size, so don't expect a perfect > backtrace. > > And I cannot reproduce. That's why a backtrace (even with some missing symbols) > would be fine. > I cannot reproduce it, too.
let's see if the arch people can help me.
I removed .kde4/share/apps/rekonq directory as well as .kde4/share/config/rekonqrc This solved the crash Thanks for the quick reply, I guess it is now safe to close this bug. I gave it type invalid, hope this is ok.