Bug 455829

Summary:	Krita does not start on Centos Stream 9 / RHEL 9
Product:	[Applications] krita	Reporter:	Talis Pähn <talis.p2hn>
Component:	General	Assignee:	Krita Bugs <krita-bugs-null>
Status:	RESOLVED NOT A BUG
Severity:	crash	CC:	halla, krita-bugs-null, talis.p2hn
Priority:	NOR
Version First Reported In:	5.0.2
Target Milestone:	---
Platform:	Flatpak
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Bug Depends on:	455828
Bug Blocks:

Description Talis Pähn 2022-06-23 06:54:16 UTC

+++ This bug was initially created as a clone of Bug #455828 +++


SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. download appimage from krita.org
2. 580  cd Downloads/
3. 581  ls
4. 582  chmod a+x krita-5.0.2-x86_64.appimage
5. 583  ./krita-5.0.2-x86_64.appimage 


OBSERVED RESULT
[tpahn@magnesiumtoaster Downloads]$ ./krita-5.0.2-x86_64.appimage 
Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.
Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.
Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.
Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.
QObject::startTimer: Timers cannot have negative intervals
Could not find platform independent libraries <prefix>
Could not find platform dependent libraries <exec_prefix>
Consider setting $PYTHONHOME to <prefix>[:<exec_prefix>]
/tmp/.mount_krita-thDKow/usr/lib/krita-python-libs/krita added to PYTHONPATH
mprotect failed in ExecutableAllocator::makeExecutable: Permission denied
Segmentation fault (core dumped)
[tpahn@magnesiumtoaster Downloads]$ 


EXPECTED RESULT
krita would launch

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Centos Stream 9 (latest-fully updated)


ADDITIONAL INFORMATION
No difference in between root or personal user running it.
Splash screen pops up, crash right after that.

Comment 1 Talis Pähn 2022-06-23 07:01:54 UTC

SORRY!

This is an out-of-the-box SElinux issue

fix is:

$ sudo setsebool -P selinuxuser_execmod 1