Bug 395678

Summary:	cannot start kmail in plasma-wayland
Product:	[Applications] kmail2	Reporter:	Martin Tlustos <martin.tlustos>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UPSTREAM
Severity:	crash	CC:	arojas, notuxius, shawn
Priority:	NOR
Version:	5.8.2
Target Milestone:	---
Platform:	Neon
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Martin Tlustos 2018-06-21 06:28:31 UTC

Whenever I try to start kmail (or korganizer, and of course kontact), it will crash in plasma wayland with the following konsole output:

martin@martin-laptop:~$ kmail
Using Wayland-EGL
No text-to-speech plug-ins were found.
WebEngine compiled with X11 support, however qpa backend is not xcb. This may fail.
[6760:6794:0621/092529.060601:ERROR:gl_surface_qt.cpp(230)] eglGetProcAddress not found.
Using the 'xdg-shell-v6' shell integration
[6760:6794:0621/092530.158388:ERROR:gl_surface_qt.cpp(299)] Requested OpenGL implementation is not supported. Implementation: 0
Received signal 11 SEGV_MAPERR 000000000000
#0 0x7fa60cbd81cf <unknown>
#1 0x7fa60b5fbe17 <unknown>
#2 0x7fa60cbd86de <unknown>
#3 0x7fa6222f64b0 <unknown>
#4 0x7fa60b666e42 <unknown>
#5 0x7fa60b6510e8 <unknown>
#6 0x7fa60d697a8d <unknown>
#7 0x7fa60f70c927 <unknown>
#8 0x7fa60f70f8f0 <unknown>
#9 0x7fa60f70ae16 <unknown>
#10 0x7fa60f708adf <unknown>
#11 0x7fa60f70a022 <unknown>
#12 0x7fa60f70bbbd <unknown>
#13 0x7fa60cbd88d9 <unknown>
#14 0x7fa60cbf9da0 <unknown>
#15 0x7fa60cbfa7fd <unknown>
#16 0x7fa60cbfaae7 <unknown>
#17 0x7fa60cbf6679 <unknown>
#18 0x7fa60cc1cbcf <unknown>
#19 0x7fa60cc3e71f <unknown>
#20 0x7fa60cc39d80 <unknown>
#21 0x7fa617c756ba start_thread
#22 0x7fa6223c841d clone
  r8: 0000000000000000  r9: 0000000000000001 r10: 0000000000000080 r11: 0000000000000000
 r12: 00007fa5bdff9a50 r13: 0000000000000000 r14: 00007fa55800b200 r15: 00007fa5bdff9c60
  di: 0000000000000000  si: 0000000000000000  bp: 00007fa5bdff9a30  bx: 00007fa558015470
  dx: 0000000000000000  ax: 00007fa611cd9138  cx: 00007fa5bdff9850  sp: 00007fa5bdff9850
  ip: 00007fa60b666e42 efl: 0000000000010246 cgf: 0000000000000033 erf: 0000000000000004
 trp: 000000000000000e msk: 0000000000000000 cr2: 0000000000000000
[end of stack trace]
Calling _exit(1). Core file will not be generated.

Comment 1 Alexander Mentyu 2018-06-21 12:44:53 UTC

KMail is starting on Wayland in:

Plasma: 5.13.1
Apps: 18.04.2
Frameworks: 5.47.0
Qt: 5.11.1
Kernel: 4.18.0-1-MANJARO
OS: Netrunner Rolling
Video: Intel 4400
Driver: xf86-video-intel 1:2.99.917+831+ge7bfc906-1
Mesa 3D: 18.1.2
Screen: 1600x900
Xorg: 1.20
Wayland: 1.15.0-1
Wayland Protocols: 1.14-1

but i can recall KMail wasn't starting on Wayland in Plasma ~5.12.5

Starting KMail in installed with updates neon Dev Unstable error:

Using Wayland-EGL
org.kde.pim.kidentitymanagement: IdentityManager: There was no default identity. Marking first one as default.
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
No text-to-speech plug-ins were found.
WebEngine compiled with X11 support, however qpa backend is not xcb. This may fail.
[2172:2212:0621/152306.366742:ERROR:gl_surface_qt.cpp(230)] eglGetProcAddress not found.
Using the 'xdg-shell-v6' shell integration
Received signal 11 SEGV_MAPERR 0000020f5000
#0 0x7f3b62fca1cf <unknown>
#1 0x7f3b619ede17 <unknown>
#2 0x7f3b62fca6de <unknown>
#3 0x7f3b784f44b0 <unknown>
#4 0x7f3b7860d1c2 <unknown>
#5 0x7f3b4e0004f6 <unknown>
#6 0x7f3b4e000700 <unknown>
#7 0x7f3b4b8a8ab6 <unknown>
#8 0x7f3b4b8a925e <unknown>
#9 0x7f3b4dffe186 <unknown>
#10 0x7f3b4dff1cf2 eglSwapBuffers
#11 0x7f3b4e2258c2 <unknown>
#12 0x7f3b79479f6c QOpenGLContext::swapBuffers()
#13 0x7f3b796f3d3b QPlatformBackingStore::composeAndFlush()
#14 0x7f3b79c509d2 <unknown>
#15 0x7f3b79c51f61 <unknown>
#16 0x7f3b79c53da5 <unknown>
#17 0x7f3b79c544e5 <unknown>
#18 0x7f3b79c9f81c <unknown>
#19 0x7f3b79ca029b <unknown>
#20 0x7f3b79c4429c QApplicationPrivate::notify_helper()
#21 0x7f3b79c4b917 QApplication::notify()
#22 0x7f3b78e7ae38 QCoreApplication::notifyInternal2()
#23 0x7f3b7943fded QGuiApplicationPrivate::processExposeEvent()
#24 0x7f3b79440a1d QGuiApplicationPrivate::processWindowSystemEvent()
#25 0x7f3b79418dfb QWindowSystemInterface::sendWindowSystemEvents()
#26 0x7f3b4f8dce6b <unknown>
#27 0x7f3b78e791ca QEventLoop::exec()
#28 0x7f3b78e822d4 QCoreApplication::exec()
#29 0x000000403713 <unknown>
#30 0x7f3b784df830 __libc_start_main
#31 0x0000004038c9 _start
  r8: 00007f3a65cb4000  r9: 0000000000000000 r10: 0000000000000020 r11: 00007f3a65cb4000
 r12: 0000000000000040 r13: fffffffffffffffc r14: 0000000000000001 r15: fffffffffffffffc
  di: 00007f3a662d92a0  si: 00000000020f4fe0  bp: 0000000001acfd40  bx: 0000000001ac9400
  dx: ffffffffff9dacdc  ax: 00007f3a65cb4000  cx: 00007f3a65cb3ffc  sp: 00007ffca9c3d248
  ip: 00007f3b7860d1c2 efl: 0000000000010283 cgf: 002b000000000033 erf: 0000000000000004
 trp: 000000000000000e msk: 0000000000000000 cr2: 00000000020f5000
[end of stack trace]
Calling _exit(1). Core file will not be generated.

Comment 2 Antonio Rojas 2018-06-21 13:14:37 UTC

Qt issue, will be fixed in 5.11.2
https://bugreports.qt.io/browse/QTBUG-68479

Comment 3 Christophe Marin 2018-06-22 11:43:24 UTC

*** Bug 395394 has been marked as a duplicate of this bug. ***