Version-Release number of selected component: qupzilla-2.0.1-7.fc25 Additional info: reporter: libreport-2.8.0 backtrace_rating: 4 cmdline: /usr/bin/qupzilla executable: /usr/bin/qupzilla global_pid: 11241 kernel: 4.8.0-0.rc8.git0.1.fc25.x86_64 pkg_fingerprint: 4089 D8F2 FDB1 9C98 pkg_vendor: Fedora Project runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #4 gfx::GLSurfaceQtEGL::Initialize at /usr/src/debug/qtwebengine-opensource-src-5.7.0/src/core/gl_surface_qt.cpp:427 #5 gfx::GLSurface::CreateOffscreenGLSurface at /usr/src/debug/qtwebengine-opensource-src-5.7.0/src/core/gl_surface_qt.cpp:529 #6 content::GpuChannelManager::GetDefaultOffscreenSurface at /usr/src/debug/qtwebengine-opensource-src-5.7.0/src/3rdparty/chromium/content/common/gpu/gpu_channel_manager.cc:338 #7 content::GpuCommandBufferStub::OnInitialize at /usr/src/debug/qtwebengine-opensource-src-5.7.0/src/3rdparty/chromium/content/common/gpu/gpu_command_buffer_stub.cc:554 #8 base::DispatchToMethodImpl<content::GpuCommandBufferStub, void (content::GpuCommandBufferStub::*)(base::FileDescriptor, IPC::Message*), base::FileDescriptor, IPC::Message&, 0ul, 0ul> at /usr/src/debug/qtwebengine-opensource-src-5.7.0/src/3rdparty/chromium/base/tuple.h:290 #9 base::DispatchToMethod<content::GpuCommandBufferStub, void (content::GpuCommandBufferStub::*)(base::FileDescriptor, IPC::Message*), base::FileDescriptor, IPC::Message&> at /usr/src/debug/qtwebengine-opensource-src-5.7.0/src/3rdparty/chromium/base/tuple.h:299 #10 IPC::SyncMessageSchema<base::Tuple<base::FileDescriptor>, base::Tuple<bool&, gpu::Capabilities&> >::DispatchDelayReplyWithSendParams<content::GpuCommandBufferStub, void (content::GpuCommandBufferStub::*)(base::FileDescriptor, IPC::Message*)> at /usr/src/debug/qtwebengine-opensource-src-5.7.0/src/3rdparty/chromium/ipc/ipc_message_utils.h:1049 #11 GpuCommandBufferMsg_Initialize::DispatchDelayReply<content::GpuCommandBufferStub, void, void (content::GpuCommandBufferStub::*)(base::FileDescriptor, IPC::Message*)> at /usr/src/debug/qtwebengine-opensource-src-5.7.0/src/3rdparty/chromium/content/common/gpu/gpu_messages.h:572 #12 content::GpuCommandBufferStub::OnMessageReceived at /usr/src/debug/qtwebengine-opensource-src-5.7.0/src/3rdparty/chromium/content/common/gpu/gpu_command_buffer_stub.cc:293 #13 content::GpuChannel::HandleMessage at /usr/src/debug/qtwebengine-opensource-src-5.7.0/src/3rdparty/chromium/content/common/gpu/gpu_channel.cc:851
Created attachment 1207075 [details] File: backtrace
Created attachment 1207076 [details] File: cgroup
Created attachment 1207077 [details] File: core_backtrace
Created attachment 1207078 [details] File: dso_list
Created attachment 1207079 [details] File: environ
Created attachment 1207080 [details] File: limits
Created attachment 1207081 [details] File: maps
Created attachment 1207082 [details] File: mountinfo
Created attachment 1207083 [details] File: namespaces
Created attachment 1207084 [details] File: open_fds
Created attachment 1207085 [details] File: proc_pid_status
Created attachment 1207086 [details] File: var_log_messages
According to environ, this is a crash with QtWebEngine on Wayland. (Try: QT_QPA_PLATFORM=xcb qupzilla to force it to use XWayland for now.) (ABRT has a text input field where you can give some information, please fill it in next time so that I do not have to scan through all the files to guess the relevant information from!)
QtWebEngine does not support Wayland at this time, see the upstream bug report.
This is unfortunately blocking on Chromium. I posted my findings to the upstream bug: https://bugreports.qt.io/browse/QTBUG-54038?focusedCommentId=333237&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-333237
(In reply to Kevin Kofler from comment #13) > According to environ, this is a crash with QtWebEngine on Wayland. (Try: > QT_QPA_PLATFORM=xcb qupzilla > to force it to use XWayland for now.) I confirm "QT_QPA_PLATFORM=xcb qupzilla" works, thanks. > > (ABRT has a text input field where you can give some information, please > fill it in next time so that I do not have to scan through all the files to > guess the relevant information from!) I usually fill it when I know where the problem is, but I didn't know what was it.
(In reply to Kevin Kofler from comment #15) > This is unfortunately blocking on Chromium. I posted my findings to the > upstream bug: > https://bugreports.qt.io/browse/QTBUG-54038?focusedCommentId=333237&page=com. > atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-333237 Chromium runs fine here, on the same wayland session. Also, until it is supported, QupZilla menu entry can contain the QT_QPA_PLATFORM=xcb to force xcb mode.