https://bugs.kde.org/show_bug.cgi?id=459490
amyspark changed:
What|Removed |Added
Latest Commit|https://invent.kde.org/grap |https://invent.kde.org/grap
|hics/
https://bugs.kde.org/show_bug.cgi?id=459490
amyspark changed:
What|Removed |Added
Resolution|--- |FIXED
Latest Commit|
https://bugs.kde.org/show_bug.cgi?id=459490
--- Comment #15 from amyspark ---
(In reply to Long Vu from comment #14)
> I attempted a build with the patches from the MR, getting this error
> currently.
>
> jsruntime/qv4function.cpp:49:10: fatal error: private/qv4functiontable_p.h:
> No such file
https://bugs.kde.org/show_bug.cgi?id=459490
--- Comment #14 from Long Vu ---
I attempted a build with the patches from the MR, getting this error currently.
jsruntime/qv4function.cpp:49:10: fatal error: private/qv4functiontable_p.h: No
such file or directory
49 | #include
| ^~
https://bugs.kde.org/show_bug.cgi?id=459490
--- Comment #13 from Timothée Ravier ---
I'm the one that asked for it to be reported here as Krita is not using the
same version of Qt as everyone else so we can not just update it without your
input.
Thanks for the investigation.
--
You are receivi
https://bugs.kde.org/show_bug.cgi?id=459490
--- Comment #12 from Halla Rempt ---
Okay, so someone needs to build and test this; I don't think any Krita
developer that uses Linux uses selinux.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=459490
--- Comment #11 from Bug Janitor Service ---
A possibly relevant merge request was started @
https://invent.kde.org/graphics/krita/-/merge_requests/1592
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=459490
amyspark changed:
What|Removed |Added
Ever confirmed|0 |1
Assignee|krita-bugs-n...@kde.org |a.
https://bugs.kde.org/show_bug.cgi?id=459490
--- Comment #9 from amyspark ---
There's no 5.15 AppImage as it's a Qt version we don't support it officially.
But I think I found the reason for this issue, Qt truly fixed their JIT much
later: https://codereview.qt-project.org/c/qt/qtdeclarative/+/329
https://bugs.kde.org/show_bug.cgi?id=459490
--- Comment #8 from Long Vu ---
(In reply to amyspark from comment #6)
> Does AlmaLinux also have SELinux enabled by default?
Yes, I spun up AlmaLinux 9 on a VM and can repo the issue mentioned there using
the AppImage. I can also verify SELinux is ena
https://bugs.kde.org/show_bug.cgi?id=459490
--- Comment #7 from amyspark ---
Hm, a better question is: if you run Krita under SELinux with Qt 5.15, does it
show the issue?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=459490
--- Comment #6 from amyspark ---
Does AlmaLinux also have SELinux enabled by default?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=459490
Long Vu changed:
What|Removed |Added
CC||h...@vulongm.com
--- Comment #5 from Long Vu ---
One
https://bugs.kde.org/show_bug.cgi?id=459490
--- Comment #4 from Halla Rempt ---
Yeah, I'm not sure either... Upstream (if it's an issue in Qt) or downstream
(if it's an issue in flatpak, but the flatpak people told Timothée to report
here). But I don't see what _we_ can do about this...
--
You
https://bugs.kde.org/show_bug.cgi?id=459490
amyspark changed:
What|Removed |Added
CC||a...@amyspark.me
--- Comment #3 from amyspark ---
A
https://bugs.kde.org/show_bug.cgi?id=459490
Halla Rempt changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
CC|
https://bugs.kde.org/show_bug.cgi?id=459490
--- Comment #1 from Timothée Ravier ---
Might be related to https://bugzilla.redhat.com/show_bug.cgi?id=1686675.
Might be related to the fact that Krita in Flathub uses an old Qt version.
--
You are receiving this mail because:
You are watching all bu
17 matches
Mail list logo