Bug 363207

Summary:	Krita crashes on Wayland
Product:	[Applications] krita	Reporter:	miku84 <miku84>
Component:	General	Assignee:	Krita Bugs <krita-bugs-null>
Status:	RESOLVED LATER
Severity:	grave	CC:	halla, munzirtaha
Priority:	NOR
Version:	3.0 Beta
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed In:

Description miku84 2016-05-18 09:29:11 UTC

Start Krita 3 beta in wayland, it crashes.

Reproducible: Always

Steps to Reproduce:
1.Start Krita on Wayland


Actual Results:  
Crash

Expected Results:  
No crash

AUR package: https://aur.archlinux.org/packages/krita-git

Comment 1 Halla Rempt 2016-05-18 10:29:35 UTC

Sorry, that's just not supported at all at the moment. Krita on Linux needs xcb for handling the graphics tablets, and we're not even beginning to think of supporting Wayland.

Comment 2 miku84 2016-05-18 10:40:59 UTC

I see, thanks for the info,

Comment 3 Munzir Taha 2016-08-22 05:34:56 UTC

For me krita 3.0 works in wayland if I launched it from command line, but if I launched if from GUI it crashes with:

Application: krita (krita), signal: Aborted
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fbaea8cb7c0 (LWP 7823))]

Thread 2 (Thread 0x7fbace999700 (LWP 7824)):
#0  0x00007fbae774048d in poll () from /usr/lib/libc.so.6
#1  0x00007fbae03e5066 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x00007fbae03e517c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#3  0x00007fbae827959b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5
#4  0x00007fbae82230da in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5
#5  0x00007fbae80460f3 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6  0x00007fbae1c71e75 in ?? () from /usr/lib/libQt5DBus.so.5
#7  0x00007fbae804ad78 in ?? () from /usr/lib/libQt5Core.so.5
#8  0x00007fbae1a46454 in start_thread () from /usr/lib/libpthread.so.0
#9  0x00007fbae77497df in clone () from /usr/lib/libc.so.6

Thread 1 (Thread 0x7fbaea8cb7c0 (LWP 7823)):
[KCrash Handler]
#5  0x00007fbae769404f in raise () from /usr/lib/libc.so.6
#6  0x00007fbae769547a in abort () from /usr/lib/libc.so.6
#7  0x00007fbae80314a1 in QMessageLogger::fatal(char const*, ...) const () from /usr/lib/libQt5Core.so.5
#8  0x00007fbaea3694de in ?? () from /usr/lib/libkritaui.so.15
#9  0x00007fbaea36b296 in KisXi2EventFilter::KisXi2EventFilter() () from /usr/lib/libkritaui.so.15
#10 0x00007fbaea36b37c in KisXi2EventFilter::instance() () from /usr/lib/libkritaui.so.15
#11 0x0000000000404973 in main ()

Comment 4 Halla Rempt 2016-08-22 06:50:16 UTC

That's not a bug in Krita; I suspect that's because when you launch krita from the gui, it cannot connect to X11-on-Wayland. But, as I said, Wayland is not supported, and I have no plans to start supporting it any time soon.