Description of problem: I did just this: $ wkhtmltopdf http://www.cnn.com cnn.pdf loaded the Generic plugin Loading page (1/2) No bp log location saved, using default.========> ] 79% [000:000] Cpu: 6.37.5, x4, 2667Mhz, 3751MB [000:000] Computer model: Not available [000:000] Browser XEmbed support present: 1 [000:000] Browser toolkit is not Gtk2 (0). [000:012] Using Xt toolkit No bp log location saved, using default. [000:000] Cpu: 6.37.5, x4, 2667Mhz, 3751MB [000:000] Computer model: Not available java version "1.7.0_55"==============================> ] 87% OpenJDK Runtime Environment (fedora-2.4.7.0.fc20-x86_64 u55-b13) OpenJDK 64-Bit Server VM (build 24.51-b03, mixed mode) Printing pages (2/2) Error: Failed loading page http://www.cnn.com (sometimes it will work just to ignore this error with --load-error-handling ignore) Segmentation fault (core dumped)=============================] 100% Resulting cnn.pdf seems OK. Version-Release number of selected component: wkhtmltopdf-0.11.0-0.2.rc1.fc20.1 Additional info: reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: wkhtmltopdf http://www.cnn.com cnn.pdf crash_function: node_copy executable: /usr/bin/wkhtmltopdf kernel: 3.14.4-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 node_copy at /usr/include/QtCore/qlist.h:399 #1 QList<QPair<QString, QString> >::detach_helper at /usr/include/QtCore/qlist.h:711 #2 detach_helper at /usr/include/QtCore/qlist.h:725 #3 QList at /usr/include/QtCore/qlist.h:122 #4 QForeachContainer at /usr/include/QtCore/qglobal.h:2367 #5 wkhtmltopdf::MyNetworkAccessManager::createRequest at ../lib/multipageloader.cc:79 #6 QNetworkAccessManager::get at access/qnetworkaccessmanager.cpp:598 #7 WebCore::QNetworkReplyHandler::sendNetworkRequest at /lib64/libQtWebKit.so.4 #8 WebCore::QNetworkReplyHandler::start at /lib64/libQtWebKit.so.4 #9 flush at /lib64/libQtWebKit.so.4
Created attachment 899676 [details] File: backtrace
Created attachment 899677 [details] File: cgroup
Created attachment 899678 [details] File: core_backtrace
Created attachment 899679 [details] File: dso_list
Created attachment 899680 [details] File: environ
Created attachment 899681 [details] File: exploitable
Created attachment 899682 [details] File: limits
Created attachment 899683 [details] File: maps
Created attachment 899684 [details] File: open_fds
Created attachment 899685 [details] File: proc_pid_status
Created attachment 899686 [details] File: var_log_messages
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora 'version' of '20'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 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 this bug is closed as described in the policy above. 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.