Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#57018 - [qt5-webengine] Kontact Failed to load /usr/bin/ and crash in wayland

Attached to Project: Arch Linux
Opened by Munzir Taha (munzirtaha) - Tuesday, 09 January 2018, 04:38 GMT
Last edited by Antonio Rojas (arojas) - Wednesday, 17 January 2018, 17:53 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Antonio Rojas (arojas)
Felix Yan (felixonmars)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No


kontact and its family (kmail, akregator, ...) all crashes and segfaults upon start on wayland. I filed the bug upstream at and they say it's downstream

Additional info:
* package version(s): Attached is pacman -Q output
* config and/or log files etc.

Steps to reproduce:
@spectre~> kontact
Using Wayland-EGL
WebEngine compiled with X11 support, however qpa backend is not xcb. This may fail.
[0109/] Failed to open file: /home/munzir/#23471566 (deleted)
Error: No such file or directory
[2574:2596:0109/] Failed to load /usr/bin/ /usr/bin/ cannot open shared object file: No such file or directory
Using the 'wl-shell' shell integration
[2574:2596:0109/073154.498272:ERROR:gl_surface_qt.cpp(701)] Requested OpenGL implementation is not supported. Implementation: 0
*** stack smashing detected ***: <unknown> terminated
Received signal 6
#0 0x7f75a5bd8086 <unknown>
#1 0x7f75a48041cc <unknown>
#2 0x7f75a5bd83fc <unknown>
#3 0x7f75b4e3d8e0 <unknown>
#4 0x7f75b4e3d860 __GI_raise
#5 0x7f75b4e3eec9 __GI_abort
#6 0x7f75b4e80437 __libc_message
#7 0x7f75b4f1033f __GI___fortify_fail_abort
#8 0x7f75b4f10302 __stack_chk_fail_local
#9 0x7f75a485a77c <unknown>
#10 0x7f75a662dda7 <unknown>
#11 0x7f75a663ae1e <unknown>
#12 0x7f75a663d6ff <unknown>
#13 0x7f75a663e96f <unknown>
#14 0x7f75a66382cd <unknown>
#15 0x7f75a66389e8 <unknown>
#16 0x7f75a6637bde <unknown>
#17 0x7f75a663a095 <unknown>
#18 0x7f75a5c5dee2 <unknown>
#19 0x7f75a5bf5548 <unknown>
#20 0x7f75a5bf6528 <unknown>
#21 0x7f75a5bf6993 <unknown>
#22 0x7f75a5bf7cf1 <unknown>
#23 0x7f75a5c1622b <unknown>
#24 0x7f75a5c311f6 <unknown>
#25 0x7f75a5c2c3eb <unknown>
#26 0x7f75b0dfe08c start_thread
#27 0x7f75b4efee1f __GI___clone
r8: 0000000000000000 r9: 00007f7533ffd730 r10: 0000000000000008 r11: 0000000000000246
r12: 00007f7533ffd9d0 r13: 0000000000001000 r14: 0000000000000000 r15: 0000000000000030
di: 0000000000000002 si: 00007f7533ffd730 bp: 00007f7533ffdb60 bx: 0000000000000006
dx: 0000000000000000 ax: 0000000000000000 cx: 00007f75b4e3d860 sp: 00007f7533ffd730
ip: 00007f75b4e3d860 efl: 0000000000000246 cgf: 002b000000000033 erf: 0000000000000000
trp: 0000000000000000 msk: 0000000000000000 cr2: 0000000000000000
[end of stack trace]
Calling _exit(1). Core file will not be generated.
[2634:2634:0100/] Invalid node channel message

@spectre~> lspci | egrep 'VGA|3D'
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 620 (rev 02)
00:13.0 Non-VGA unclassified device: Intel Corporation Sunrise Point-LP Integrated Sensor Hub (rev 21)
01:00.0 3D controller: NVIDIA Corporation GM108M [GeForce 940MX] (rev ff)

Attached is glxinfo output
This task depends upon

Closed by  Antonio Rojas (arojas)
Wednesday, 17 January 2018, 17:53 GMT
Reason for closing:  Fixed
Additional comments about closing:  qt5-webengine 5.10.0-3
Comment by Antonio Rojas (arojas) - Thursday, 11 January 2018, 10:46 GMT
This is indeed unrelated to nvidia. It's an unfortunate coincidence that it was filed the same day that a nvidia bug with the same symptoms was introduced.
Comment by Munzir Taha (munzirtaha) - Thursday, 11 January 2018, 11:07 GMT
Thanks for reopening. I hope there is a policy or agreement to give us some time to explain and respond. With HIM shutting me up twice, I felt like my freedom to speak is stolen!
Comment by Antonio Rojas (arojas) - Wednesday, 17 January 2018, 17:53 GMT
I've disabled GPU rendering on Wayland until this is fixed (workaround courtesy of opensuse)