https://bugs.kde.org/show_bug.cgi?id=475562
--- Comment #22 from Halla Rempt ---
I guess we also need to figure out why KoResourcePaths::getApplicationRoot()
doesn't work on this distribution.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=475562
--- Comment #21 from Lynx3d ---
Git commit 737a640d6765424870f6df7ccec9db0b08d53e88 by Mathias Wein.
Committed on 21/10/2023 at 22:51.
Pushed by mwein into branch 'krita/5.2'.
Prevent a crash when a default profile is missing
KoColorSpaceRegistry::ins
https://bugs.kde.org/show_bug.cgi?id=475562
--- Comment #20 from Lynx3d ---
Git commit 01b70545968e1c0b01d738b8e32de69cacff89c1 by Mathias Wein.
Committed on 21/10/2023 at 22:41.
Pushed by mwein into branch 'master'.
Prevent a crash when a default profile is missing
KoColorSpaceRegistry::instan
https://bugs.kde.org/show_bug.cgi?id=475562
--- Comment #19 from Timo Gurr ---
I was able to workaround this downstream by applying:
diff -Naur krita-5.2.0/libs/resources/KoResourcePaths.cpp
krita-5.2.0.new/libs/resources/KoResourcePaths.cpp
--- krita-5.2.0/libs/resources/KoResourcePaths.cpp
https://bugs.kde.org/show_bug.cgi?id=475562
--- Comment #18 from Timo Gurr ---
(In reply to Lynx3d from comment #17)
> The file is 'ITUR_2100_PQ_FULL.ICC'
> It should be in: /share/color/icc/krita/
Thanks for the information, as you can see from my attached full list above I
do have the file in
https://bugs.kde.org/show_bug.cgi?id=475562
--- Comment #17 from Lynx3d ---
The file is 'ITUR_2100_PQ_FULL.ICC' and has the verbose descriptive name "High
Dynamic Range UHDTV Wide Color Gamut Display (Rec. 2020) - SMPTE ST 2084 PQ
EOTF"
It should be in: /share/color/icc/krita/
I don't have a comp
https://bugs.kde.org/show_bug.cgi?id=475562
--- Comment #16 from Timo Gurr ---
Created attachment 162374
--> https://bugs.kde.org/attachment.cgi?id=162374&action=edit
krita-5.2.0-installed-files.txt
(In reply to Lynx3d from comment #15)
> hm the crashing line is:
> > cs->profile()->uniqueId()
https://bugs.kde.org/show_bug.cgi?id=475562
Lynx3d changed:
What|Removed |Added
CC||lynx.mw+...@gmail.com
--- Comment #15 from Lynx3d ---
https://bugs.kde.org/show_bug.cgi?id=475562
--- Comment #14 from Timo Gurr ---
Created attachment 162343
--> https://bugs.kde.org/attachment.cgi?id=162343&action=edit
krita-20231016-085327.kcrash
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=475562
--- Comment #13 from Timo Gurr ---
(In reply to Halla Rempt from comment #12)
> That's dependent on the distribution... You probably need to configure
> something that prevents stripping out debug info.
Turns out that -DCMAKE_BUILD_TYPE:STRING=RelWithD
https://bugs.kde.org/show_bug.cgi?id=475562
--- Comment #12 from Halla Rempt ---
That's dependent on the distribution... You probably need to configure
something that prevents stripping out debug info.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=475562
--- Comment #11 from Timo Gurr ---
(In reply to Halla Rempt from comment #10)
> it would be helpful if the backtrace would include line numbers :)
Is it possible to automatically get them included in the debug output and if so
can you please advice how
https://bugs.kde.org/show_bug.cgi?id=475562
--- Comment #10 from Halla Rempt ---
it would be helpful if the backtrace would include line numbers :)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=475562
Bug Janitor Service changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
Resolution|WAITINGFORINF
https://bugs.kde.org/show_bug.cgi?id=475562
--- Comment #8 from Timo Gurr ---
Created attachment 162284
--> https://bugs.kde.org/attachment.cgi?id=162284&action=edit
krita-20231014-004649.kcrash
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=475562
--- Comment #7 from Timo Gurr ---
(In reply to Halla Rempt from comment #6)
> I know... But even so, there isn't much testing we can do, since it doesn't
> happen elsewhere. The only guess I can make is that this patch might help,
> but I cannot test it
https://bugs.kde.org/show_bug.cgi?id=475562
--- Comment #6 from Halla Rempt ---
I know... But even so, there isn't much testing we can do, since it doesn't
happen elsewhere. The only guess I can make is that this patch might help, but
I cannot test it:
diff --git a/libs/widgets/KisVisualColorMod
https://bugs.kde.org/show_bug.cgi?id=475562
--- Comment #5 from Timo Gurr ---
Thanks for your comments. Just for reference this pretty much happens to us
with every new krita version and usually the problems in the past have not
really been on our side:
https://bugs.kde.org/show_bug.cgi?id=44527
https://bugs.kde.org/show_bug.cgi?id=475562
--- Comment #4 from Halla Rempt ---
I'm afraid you'll have to investigate this yourself. It (obviously) doesn't
happen for any of us developers, so it's either a build problem, a problem with
dependencies or something else, even weirder.
--
You are re
https://bugs.kde.org/show_bug.cgi?id=475562
--- Comment #3 from Timo Gurr ---
Only one krita present on the system. Exherbo is a source-based distribution
like Gentoo.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=475562
Halla Rempt changed:
What|Removed |Added
Status|REPORTED|NEEDSINFO
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=475562
--- Comment #1 from Timo Gurr ---
Created attachment 162273
--> https://bugs.kde.org/attachment.cgi?id=162273&action=edit
krita-5.2.0-coredump.txt
--
You are receiving this mail because:
You are watching all bug changes.
22 matches
Mail list logo
