Your message dated Fri, 2 Nov 2018 18:19:53 +0300
with message-id <20181102151953.ga13...@mitya57.me>
and subject line Re: Bug#910317: QtWebEngine in unstable is constantly crashing
has caused the Debian Bug report #910317,
regarding QtWebEngine in unstable is constantly crashing
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
910317: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910317
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-pyqt5.qtwebengine
Version: 5.11.2+dfsg-1
Severity: serious
X-Debbugs-CC: debian-qt-kde@lists.debian.org
Control: affects -1 + libqt5webengine5
Dear Debian Qt/KDE maintainers and pyqt5.qtwebengine maintainers,
Current QtWebEngine in Debian Unstable would easily crash. That
happens after recent upgrade of libkf5.
For example, run the following script under python3:
$ export LC_ALL=C.UTF-8
$ export LANG=C
$ cat ./test.py
import sys
from PyQt5.QtWidgets import QApplication
from PyQt5.QtWidgets import QMainWindow
from PyQt5.QtWebEngineWidgets import QWebEngineView
from PyQt5.QtCore import QUrl
def main():
app = QApplication(sys.argv)
window = QMainWindow()
window.setWindowTitle('PyQt Demo')
window.setGeometry(320, 180, 960, 540)
view = QWebEngineView()
view.load(QUrl('http://leafletjs.com/')) # error here
window.setCentralWidget(view)
window.show()
sys.exit(app.exec_())
if __name__ == '__main__':
main()
$ python3 ./test.py
[1004/140404.438632:WARNING:stack_trace_posix.cc(699)] Failed to open
file: /tmp/.glBfSxZo (deleted)
Error: No such file or directory
[8494:8515:1004/140404.647050:ERROR:nss_util.cc(727)] After loading
Root Certs, loaded==false: NSS error code: -8018
Received signal 11 SEGV_MAPERR 000000000010
#0 0x7fc98c03e76e <unknown>
#1 0x7fc98c03e880 <unknown>
#2 0x7fc98c03eeb7 <unknown>
#3 0x7fc9969db8e0 <unknown>
#4 0x7fc990771604 <unknown>
#5 0x7fc98aa8d660 <unknown>
#6 0x7fc98aabde3c <unknown>
#7 0x7fc98a0af500 QQuickWindowPrivate::updateDirtyNode()
#8 0x7fc98a0af963 QQuickWindowPrivate::updateDirtyNodes()
#9 0x7fc98a0b0e22 QQuickWindowPrivate::syncSceneGraph()
#10 0x7fc98a16ce49 QQuickRenderControl::sync()
#11 0x7fc989c7e0c6 <unknown>
#12 0x7fc989c7e2a6 <unknown>
#13 0x7fc994b0003b QObject::event()
#14 0x7fc99548ac6b QWidget::event()
#15 0x7fc989c81e2d QQuickWidget::event()
#16 0x7fc990771bf0 <unknown>
#17 0x7fc99544c4a1 QApplicationPrivate::notify_helper()
#18 0x7fc995453ae0 QApplication::notify()
#19 0x7fc995d1f11e <unknown>
#20 0x7fc994ad6589 QCoreApplication::notifyInternal2()
#21 0x7fc994b27648 QTimerInfoList::activateTimers()
#22 0x7fc994b27ea4 <unknown>
#23 0x7fc9939acc3e g_main_context_dispatch
#24 0x7fc9939aced8 <unknown>
#25 0x7fc9939acf6c g_main_context_iteration
#26 0x7fc994b28233 QEventDispatcherGlib::processEvents()
#27 0x7fc97df51ee1 <unknown>
#28 0x7fc994ad525b QEventLoop::exec()
#29 0x7fc994add3d2 QCoreApplication::exec()
#30 0x7fc995ce214b <unknown>
#31 0x0000005068bf <unknown>
#32 0x00000050a4e9 _PyEval_EvalFrameDefault
#33 0x000000505d58 <unknown>
#34 0x000000506a8d <unknown>
#35 0x00000050a4e9 _PyEval_EvalFrameDefault
#36 0x0000005088b8 <unknown>
#37 0x00000050a023 PyEval_EvalCode
#38 0x000000635f82 <unknown>
#39 0x00000063603a PyRun_FileExFlags
#40 0x0000006397f8 PyRun_SimpleFileExFlags
#41 0x00000063a38a Py_Main
#42 0x0000004ac090 main
#43 0x7fc996433b17 __libc_start_main
#44 0x0000005b35aa _start
r8: 0000000017281b04 r9: 00000000017ae3e0 r10: 0000000017281b04
r11: 0000000000000001
r12: 0000000000000000 r13: 00000000017651c0 r14: 00007fc994b91660
r15: 00000000017650e0
di: 0000000001728da0 si: 0000000000000000 bp: 00007ffc01652bc0
bx: 0000000001713dd0
dx: 00007fc994b91660 ax: 0000000001082000 cx: 00007fc994b91678
sp: 00007ffc016527e0
ip: 00007fc990771604 efl: 0000000000010202 cgf: 002b000000000033
erf: 0000000000000004
trp: 000000000000000e msk: 0000000000000000 cr2: 0000000000000010
[end of stack trace]
Calling _exit(1). Core file will not be generated.
$
--
Thanks,
Boyuan Yang
--- End Message ---
--- Begin Message ---
Version: 5.11.2+dfsg-1
On Thu, Oct 18, 2018 at 03:42:58PM +0300, Dmitry Shachnev wrote:
> I cannot reproduce this crash with 5.11.2 packages (now in unstable).
>
> Are you sure you are getting the same crash, maybe the stacktrace is a
> different one? Did you try to use the debugger to get stacktrace?
>
> In any case please paste the URL of page where Falkon is crashing, or
> attach the C++ example if you have it.
I just tried the original Python example with the latest packages from
unstable, and it does not crash anymore. So closing this bug.
If you still experience crashes then file a new bug with a fresh stacktrace.
--
Dmitry Shachnev
signature.asc
Description: PGP signature
--- End Message ---
