Description of problem: Konqueror crashed suddenly, this would be related to qtwebkit because I am having similar problems with rekonq that I compiled from git source. Version-Release number of selected component: kde-baseapps-4.9.2-2.fc17 Additional info: libreport version: 2.0.18 abrt_version: 2.0.18 backtrace_rating: 4 cmdline: /usr/bin/konqueror --silent crash_function: WebPluginFactory::create kernel: 3.6.5-1.fc17.x86_64 truncated backtrace: :Thread no. 1 (10 frames) : #0 WebPluginFactory::create at /usr/src/debug/kwebkitpart-1.3.0/src/webpluginfactory.cpp:208 : #1 WebCore::FrameLoaderClientQt::createPlugin at WebCoreSupport/FrameLoaderClientQt.cpp:1575 : #2 WebCore::SubframeLoader::loadPlugin at loader/SubframeLoader.cpp:363 : #3 WebCore::SubframeLoader::requestPlugin at loader/SubframeLoader.cpp:122 : #4 WebCore::SubframeLoader::requestObject at loader/SubframeLoader.cpp:142 : #5 WebCore::HTMLEmbedElement::updateWidget at html/HTMLEmbedElement.cpp:183 : #6 WebCore::FrameView::updateWidget at page/FrameView.cpp:1938 : #7 WebCore::FrameView::updateWidgets at page/FrameView.cpp:1970 : #8 WebCore::FrameView::performPostLayoutTasks at page/FrameView.cpp:2014 : #9 WebCore::ThreadTimers::sharedTimerFiredInternal at platform/ThreadTimers.cpp:112
Created attachment 641176 [details] File: core_backtrace
Created attachment 641178 [details] File: environ
Created attachment 641181 [details] File: backtrace
Created attachment 641183 [details] File: limits
Created attachment 641185 [details] File: cgroup
Created attachment 641187 [details] File: smolt_data
Created attachment 641189 [details] File: xsession_errors
Created attachment 641191 [details] File: executable
Created attachment 641192 [details] File: maps
Created attachment 641193 [details] File: dso_list
Created attachment 641194 [details] File: build_ids
Created attachment 641195 [details] File: proc_pid_status
Created attachment 641196 [details] File: var_log_messages
Created attachment 641197 [details] File: open_fds
OK, very likely qtwebkit then. What plugins do you happen to have installed in /usr/lib(64)/mozilla/plugins ?
I have flash, java and googletalk plugins installed in /usr/lib64/mozilla/plugins. Below is the output of ls -al /usr/lib64/mozilla/plugins command. libflashplayer.so libjavaplugin.so libnpgoogletalk.so libnpgtpo3dautoplugin.so I guess they are symbolic links to the plugins.
and any particular way to trigger the crash? Does it happen only when browsing certain sites or content?
I was visiting a turkish news website www.milliyet.com.tr to check the scores of a few soccer games before the crash happened. This website also causes rekonq to crash almost everytime. I sometimes have the crash with www.nytimes.com which is another news website. Initially I was suspecting that it may be related to adblock (I am using adblock with hide filtered elements option enabled, easy list+easy privacy checked). But it turns out that it is related to webkit. I am not sure if this would be related but I have another very strange problem with both rekonq and konqueror. When I visit www.tdcanadatrust.ca and try to check my bank account, I am being greeted with a message saying that I should enable cookies in order to login; the website does not allow me to login. I checked my settings and both in konqueror and rekonq cookies are enabled. I was able to login using bot rekonq and konqueror a few weeks ago. In any case I have no clue what makes konqueror behaving this way when I visit these websites.
mind testing this build? http://koji.fedoraproject.org/koji/taskinfo?taskID=4683534 (when it finishes)
OK, I will try it; let me know when it is ready. I will also need some brief instruction on how to install it, e.g. whether to compile from source or enable (testing) repos.
su -c "rpm -Uvh http://kojipkgs.fedoraproject.org//packages/qtwebkit/2.2.2/3.fc17/x86_64/qtwebkit-2.2.2-3.fc17.x86_64.rpm" (all in one line)
I installed both qtwebkit and qtwebkit-devel. I can readily confirm that rekonq that I compiled from git source is still crashing. Bad news is rekonq does not offer me to report a bug after it closes. All I can see regarding the crash in rekonq is when I start it from the konsole. I obtain the following information below: void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action "View Page S&ource" under id 24 libpng warning: Duplicate iCCP chunk loaded the Generic plugin QFont::setPixelSize: Pixel size <= 0 (0) No bp log location saved, using default. [000:000] Browser XEmbed support present: 1 [000:000] Browser toolkit is not Gtk2 (0). [000:011] Using Xt toolkit java version "1.7.0_09-icedtea" OpenJDK Runtime Environment (fedora-2.3.3.fc17.1-x86_64) OpenJDK 64-Bit Server VM (build 23.2-b09, mixed mode) (rekonq:1795): Gdk-ERROR **: The program 'rekonq' received an X Window System error. This probably reflects a bug in the program. The error was 'BadValue (integer parameter out of range for operation)'. (Details: serial 9781 error_code 2 request_code 53 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Konqueror didn't crash with the same websites I am testing yet. I will report again in case it crashes in the following 1-2 days. Otherwise I will confirm Konqueror is performing well.
I would like to add that with both konqueror and rekonq the error on cookies not enabled with some secure websites still appear. From the settings I see that cookies are enabled yet some websites reject accessing my personal account. I have another problem with Konqueror. After I close Konqueror, when I hit Ctrl+Esc to see the running applications I find running instances of konqueror stealth occasionally.
Just a few minutes ago I managed to crash konqueror as well. The abrt program prepared the crash report but it didn't send for some reason. All I see was a few of the debuginfo files including gstreamer, icedtea being downloaded. Was I supposed to install qtwebkit-debuginfo as well? In any case, I'm afraid konqueror still crashes with webkit.
Yes, qtwebkit-debuginfo is needed for a proper backtrace, but you need the one from the same Koji build as qtwebkit. ABRT wasn't able to find the correct debuginfo package in the repository, which is why it didn't install it automatically. (Mismatched debuginfo packages are useless, they have to be from the exact same build as the matching normal package.)
OK then, I reported the bug id 876818.
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.