| Summary: | Rekonq crashes when selecting mail receiver from google contact list | ||
|---|---|---|---|
| Product: | [Applications] rekonq | Reporter: | Franklin Weng <franklin> |
| Component: | general | Assignee: | Andrea Diamantini <adjam7> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | CC: | adaptee, franklin |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Attachments: |
backtraces from kcrash (rekonq)
New crash information added by DrKonqi |
||
|
Description
Franklin Weng
2012-05-07 08:18:54 UTC
Any backtraces? Additional infos? versions? qtwebkit lib version? please provide all the information requested in comment #1 Created attachment 71485 [details]
backtraces from kcrash (rekonq)
Backtraces from rekonq crash
Sorry, I didn't notice the previous mail. My rekonq version: rekonq Version 0.9.2 Using KDE Development Platform 4.8.3 (4.8.3) optimized by the Chakra-Project qtwebkit 2.2.1-2 (from Chakra too) backtraces was attached. I tried on Kubuntu 12.04 this problem is there too. Created attachment 71486 [details]
New crash information added by DrKonqi
rekonq (0.9.1) on KDE Platform 4.8.3 (4.8.3) using Qt 4.8.1
- What I was doing when the application crashed:
The same bugs, running on Kubuntu 12.04. Backtraces from kcrash attached.
-- Backtrace (Reduced):
#8 0xb6159f06 in QWebPagePrivate::handleClipboard(QEvent*, Qt::MouseButton) () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4
#9 0xb615a0c9 in void QWebPagePrivate::mouseReleaseEvent<QMouseEvent>(QMouseEvent*) () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4
#10 0xb6163994 in QWebPage::event(QEvent*) () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4
#11 0xb61666c0 in QWebView::mouseReleaseEvent(QMouseEvent*) () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4
#12 0xb589ddca in KWebView::mouseReleaseEvent (this=0x91cef88, event=0xbfff0044) at ../../kdewebkit/kwebview.cpp:80
Thanks for your feedback. Looks like a duplicate of bug 299149 . *** This bug has been marked as a duplicate of bug 299149 *** |