3/16/2023 0 Comments Qupzilla 64Jan 21 19:30:02 sdu3 kernel: pid 2023 (diligent), uid 1001: exited on signal 6 (core dumped) I'm just going to ask the reporter, Arto, to confirm if this was indeed resolved in the meantime? If so, we can close this.įor me qupzilla crashes upon startup with signal 6. As there's no patch here, the approval was never requested. In addition, you can set maintainer-approval+ to patches, which is related but not the same thing. Whenever you reply, like you did explaining that it was probably fixed upstream, and you think that's the appropriate answer / feedback given to the bug report, you flag it with maintainer-feedback+ (if it was requested with ?). The feedback requested was for the entire issue at hand. Just removing the feedback request (?) is inaccurate, so I'm setting it back to +. To address such a feedback, you set it to maintainer-feedback+, or else it would appear you never did which would lead to maintainer timeout. Your feedback was requested on the subject, it was set with maintainer-feedback? with your email address. The result was that just like So with this I would say that the problem is in webkit-qt5, not in webkit-qt4. Other than that, I can't sayīUT I did test www/otter-browser, which is another webkit-qt5 based software. And in that regard, the only desktop-related service I've enabled in both systems is D-Bus (because some apps misbehave or abort execution without it). If there is some meaningful difference, then it is in what services are enabled. Both install packages from the FreeBSD-latest repository. Both yield equal results Qupzilla (QT5) crashes after opening new tab w/ speed dial, or if you try opening eg. In regards to the difference in systems: I am testing these browser with both my laptop and server w/ VNC. I did notice that If they use different webkit, is there any point in testing and comparing ReKonq to Qupzilla (QT5)? Konqueror I could not find in repository, so could not test it. ReKonq works just fine, except that I cannot set search engine because of some arbitrary "desktop file missing" reason. Did you check it? It might provide useful clues on where this crash happens. I provided a crash dump for the speed dial crash. Trying to use gdb's gcore command on the browser (after forcing break to gdb with SIGINT) causes gdb itself to freeze after it's virtual memory footprint (supposedly) reaches 34 GB.Īlso, when I try to use the browser inside a VNC Server session, it will not accept any keyboard input while other applications work just fine. I could not make a core dump of the browser after it freezes. so the problem that causes the browser to freeze is not only the speed dial, but also some specific combination of HTML and Javascript. When the browser freezes, it can be killed with SIGTERM. This also means that if I use the location bar or start page to search, it will search via and freeze. However, I noticed another bug: some web pages cause the browser to freeze. Now I can open multiple tabs, and open pages in them via direct url or by using Google Search. Tried using the browser without speed dial on new tabs. I am using the FreeBSD-latest repository: If you need more information, please do ask. Core dump: įreeBSD leno 10.2-RELEASE-p7 FreeBSD 10.2-RELEASE-p7 #0: Mon Nov 2 14:19: amd64 Program termination was due to ABORT (probably triggered by program itself after it generated the crash log above). config/qupzilla/crashlog/Crash-T19:42:04.txt: Www/qupzilla-qt5 crashes after opening a new tab.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |