Version-Release number of selected component: qupzilla-2.0.1-1.fc24 Additional info: reporter: libreport-2.7.1 backtrace_rating: 3 cmdline: qupzilla executable: /usr/bin/qupzilla global_pid: 5750 kernel: 4.5.7-300.fc24.x86_64 pkg_fingerprint: 73BD E983 81B4 6521 pkg_vendor: Fedora Project reproducible: Not sure how to reproduce the problem runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 21 (10 frames) #0 ?? #1 (anonymous namespace)::ConvertTimespecToMicros at /usr/src/debug/qtwebengine-opensource-src-5.6.0/src/3rdparty/chromium/base/time/time_posix.cc:87 #2 (anonymous namespace)::ClockNow at /usr/src/debug/qtwebengine-opensource-src-5.6.0/src/3rdparty/chromium/base/time/time_posix.cc:103 #3 __clock_gettime at ../sysdeps/unix/clock_gettime.c:115 #4 gettime at event.c:370 #5 update_time_cache at event.c:428 #6 event_base_loop at event.c:1616 #7 base::MessagePumpLibevent::Run at /usr/src/debug/qtwebengine-opensource-src-5.6.0/src/3rdparty/chromium/base/message_loop/message_pump_libevent.cc:237 #8 base::RunLoop::Run at /usr/src/debug/qtwebengine-opensource-src-5.6.0/src/3rdparty/chromium/base/run_loop.cc:55 #9 base::MessageLoop::Run at /usr/src/debug/qtwebengine-opensource-src-5.6.0/src/3rdparty/chromium/base/message_loop/message_loop.cc:287
Created attachment 1172685 [details] File: backtrace
Created attachment 1172686 [details] File: cgroup
Created attachment 1172687 [details] File: core_backtrace
Created attachment 1172688 [details] File: dso_list
Created attachment 1172689 [details] File: environ
Created attachment 1172690 [details] File: limits
Created attachment 1172691 [details] File: maps
Created attachment 1172692 [details] File: mountinfo
Created attachment 1172693 [details] File: namespaces
Created attachment 1172694 [details] File: open_fds
Created attachment 1172695 [details] File: proc_pid_status
Created attachment 1172696 [details] File: var_log_messages
Created attachment 1172697 [details] File: exploitable
ABRT posted the backtrace of the wrong thread. The actual crashing thread is: Thread 20 (Thread 0x7fb98b9c2900 (LWP 5750)): … #10 <signal handler called> No locals. #11 0x0000000000000000 in ?? () No symbol table info available. #12 0x00007fb97a5bbd2f in nouveau_fence_trigger_work (fence=fence@entry=0x558fe7e714a0) at nouveau_fence.c:56 work = 0x558fe7d06800 tmp = 0x7fb999c51b58 <main_arena+88> #13 0x00007fb97a5bbf8e in nouveau_fence_update (screen=screen@entry=0x558fe3bcfa90, flushed=flushed@entry=false) at nouveau_fence.c:132 fence = 0x558fe7e714a0 next = 0x558f00000001 sequence = 0 #14 0x00007fb97a5bc292 in nouveau_fence_wait (fence=0x558fe7eabfe0, debug=0x0) at nouveau_fence.c:223 screen = 0x558fe3bcfa90 spins = 35191 start = 0 So this is a bug in the Nouveau graphics driver, i.e., in xorg-x11-drv-nouveau.
*** Bug 1352302 has been marked as a duplicate of this bug. ***
*** Bug 1370736 has been marked as a duplicate of this bug. ***
*** Bug 1399181 has been marked as a duplicate of this bug. ***
*** Bug 1414411 has been marked as a duplicate of this bug. ***
Try the patched Mesa build from: https://copr.fedorainfracloud.org/coprs/kkofler/qtwebengine/ which includes an experimental patch for this issue. We are still waiting for a fix that upstream will accept, Ben Skeggs wrote that he was working on one, but so far it has not landed.
*** Bug 1419797 has been marked as a duplicate of this bug. ***
(In reply to Kevin Kofler from comment #19) > We are still waiting for a fix that upstream will accept, Ben Skeggs wrote > that he was working on one, but so far it has not landed. ping, is there any progress? I started hitting this on one machine (not Fedora, can't use your copr :-/) and it is really big annoyance, I just can't use Konqueror or Qupzilla, they crash right after start btw, shouldn't this be assigned to mesa?
Why are you needinfoing me? Ask the mesa maintainers!
(In reply to Kevin Kofler from comment #22) > Why are you needinfoing me? because you've written "we are ..." and continued with the description who has done what which led me to impression that you're actively pursuing the issue - if by "we" you've meant some other group not including you then sorry for misunderstanding ;-) > Ask the mesa maintainers! I take this as "yes, it really belongs to mesa and not nouveau" then so ... ping, is there any progress?
(In reply to Karel Volný from comment #23) > (In reply to Kevin Kofler from comment #22) > > Why are you needinfoing me? > > because you've written "we are ..." and continued with the description who > has done what which led me to impression that you're actively pursuing the > issue - if by "we" you've meant some other group not including you then > sorry for misunderstanding ;-) > > > Ask the mesa maintainers! > > I take this as "yes, it really belongs to mesa and not nouveau" then > > so ... ping, is there any progress? It's an *extremely* large task to do fix these issues, and I'm working on them as fast as I'm able (while still working on all the other major issues that need to be solved). Yes there's progress, but no, it's not ready.
*** Bug 1454283 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 '24'. 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 24 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 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.
There are duplicates on F25 and F26. I think Rawhide is affected too, I am not aware of any fix having gone into mesa still.
*** Bug 1485203 has been marked as a duplicate of this bug. ***
Qt upstream got fed up of waiting for the driver to get fixed (after more than a year, with driver patches available!) and ended up adding a sledgehammer workaround to the QtWebEngine code (which completely blacklists Nouveau for OpenGL).
Confirmed that Qt upstreams approach works for me (testing for 5 hours) My system is stable again.. Thank you.
qt5-qtwebengine-5.10.0-1.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2018-763efd6d5c
Qt upstream have worked around this bug, its working well! F27.. https://bugzilla.redhat.com/show_bug.cgi?id=1350275#c30
Sorry, that comment was meant for bug #1376107
qt5-qtwebengine-5.10.0-1.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-763efd6d5c
qt5-qtwebengine-5.10.0-1.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-2c18cbf1fa
*** Bug 1539293 has been marked as a duplicate of this bug. ***
qt5-qtwebengine-5.10.0-1.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.
qt5-qtwebengine-5.10.0-1.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.