[kmail2] [Bug 395678] cannot start kmail in plasma-wayland

2018-06-22 Thread Christophe Giboudeaux
https://bugs.kde.org/show_bug.cgi?id=395678

Christophe Giboudeaux  changed:

   What|Removed |Added

 CC||sh...@sorbom.com

--- Comment #3 from Christophe Giboudeaux  ---
*** Bug 395394 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 395678] cannot start kmail in plasma-wayland

2018-06-21 Thread Christophe Giboudeaux
https://bugs.kde.org/show_bug.cgi?id=395678

Christophe Giboudeaux  changed:

   What|Removed |Added

 Resolution|--- |UPSTREAM
 Status|UNCONFIRMED |RESOLVED

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 395678] cannot start kmail in plasma-wayland

2018-06-21 Thread Antonio Rojas
https://bugs.kde.org/show_bug.cgi?id=395678

Antonio Rojas  changed:

   What|Removed |Added

 CC||aro...@archlinux.org

--- Comment #2 from Antonio Rojas  ---
Qt issue, will be fixed in 5.11.2
https://bugreports.qt.io/browse/QTBUG-68479

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 395678] cannot start kmail in plasma-wayland

2018-06-21 Thread Alexander Mentyu
https://bugs.kde.org/show_bug.cgi?id=395678

Alexander Mentyu  changed:

   What|Removed |Added

 CC||notux...@gmail.com

--- Comment #1 from Alexander Mentyu  ---
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 020f5000
#0 0x7f3b62fca1cf 
#1 0x7f3b619ede17 
#2 0x7f3b62fca6de 
#3 0x7f3b784f44b0 
#4 0x7f3b7860d1c2 
#5 0x7f3b4e0004f6 
#6 0x7f3b4e000700 
#7 0x7f3b4b8a8ab6 
#8 0x7f3b4b8a925e 
#9 0x7f3b4dffe186 
#10 0x7f3b4dff1cf2 eglSwapBuffers
#11 0x7f3b4e2258c2 
#12 0x7f3b79479f6c QOpenGLContext::swapBuffers()
#13 0x7f3b796f3d3b QPlatformBackingStore::composeAndFlush()
#14 0x7f3b79c509d2 
#15 0x7f3b79c51f61 
#16 0x7f3b79c53da5 
#17 0x7f3b79c544e5 
#18 0x7f3b79c9f81c 
#19 0x7f3b79ca029b 
#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 
#27 0x7f3b78e791ca QEventLoop::exec()
#28 0x7f3b78e822d4 QCoreApplication::exec()
#29 0x00403713 
#30 0x7f3b784df830 __libc_start_main
#31 0x004038c9 _start
  r8: 7f3a65cb4000  r9:  r10: 0020 r11:
7f3a65cb4000
 r12: 0040 r13: fffc r14: 0001 r15:
fffc
  di: 7f3a662d92a0  si: 020f4fe0  bp: 01acfd40  bx:
01ac9400
  dx: ff9dacdc  ax: 7f3a65cb4000  cx: 7f3a65cb3ffc  sp:
7ffca9c3d248
  ip: 7f3b7860d1c2 efl: 00010283 cgf: 002b0033 erf:
0004
 trp: 000e msk:  cr2: 020f5000
[end of stack trace]
Calling _exit(1). Core file will not be generated.

-- 
You are receiving this mail because:
You are the assignee for the bug.