Bug 449723 - Layer Style on File Layer causes Krita to crash on Windows 10
Summary: Layer Style on File Layer causes Krita to crash on Windows 10
Status: RESOLVED DUPLICATE of bug 449122
Alias: None
Product: krita
Classification: Applications
Component: layer styles (show other bugs)
Version: git master (please specify the git hash!)
Platform: Compiled Sources Microsoft Windows
: NOR crash
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-02-07 00:04 UTC by ianmcclintock
Modified: 2022-02-14 12:21 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Backtrace Log (476.97 KB, text/plain)
2022-02-07 00:04 UTC, ianmcclintock
Details

Note You need to log in before you can comment on or make changes to this bug.
Description ianmcclintock 2022-02-07 00:04:20 UTC
Created attachment 146363 [details]
Backtrace Log

SUMMARY
***
Creating a File Layer in Krita and then attempting to apply a Layer Style to it will bring up the Layer Style dialog, at which point Krita hangs for a moment and then force-closes.
***


STEPS TO REPRODUCE
1. Add a file layer (tested with multiple different files of different types, all with the same result on my system)
2. Either by right-clicking on the layer or from the Layer menu, invoke adding a Layer Style

OBSERVED RESULT
The Layer Styles dialog appears, Krita hangs before any options can be selected.  After a moment the program closes.

EXPECTED RESULT
Selecting options and applying a layer style to the file layer.

SOFTWARE/OS VERSIONS
Windows: 10

ADDITIONAL INFORMATION
Trace log attached.  The two most recent crashes on 2/6/2022 are the relevant ones to this particular crash.
Comment 1 Ahab Greybeard 2022-02-07 15:22:22 UTC
With the latest Feb 05 5.1.0-prealpha appimage on Debian 10 and the latest Feb 07 5.1.0-prealpha .zip package on Windows 10, I have no problem applying Layer Styles onto a File layer.

This situation has some similarity with the following bug report:
https://bugs.kde.org/show_bug.cgi?id=445922

@ianmcclintock: Can you consider the comments on that bug report, especially towards the end, then investigate those observations for your situation?
Comment 2 ianmcclintock 2022-02-07 19:14:44 UTC
(In reply to Ahab Greybeard from comment #1)

> This situation has some similarity with the following bug report:
> https://bugs.kde.org/show_bug.cgi?id=445922
> 
> @ianmcclintock: Can you consider the comments on that bug report, especially
> towards the end, then investigate those observations for your situation?

Thank you for the link, and I apologize for the similar/duplicate report - the above didn't appear in the search results for some reason.

I can confirm that removing all custom content and reinstalling Krita has fixed this behavior.  It must be an issue with something in my add-ons or custom brushes, so I'll investigate that on my own further.  Thanks so much for the suggestion.
Comment 3 Ahab Greybeard 2022-02-07 19:36:10 UTC
No problem. Please note that reinstalling krita will have no effect (except in the unlikely event that the installation itself was corrupted, in which case it's behaviour would be very strange even if it could run at all).

The behaviour of krita is determined by the configuration files and the contents of the resources folder, which are recreated 'as new/default' when krita starts if you ever delete (or rename) them.
Comment 4 Bug Janitor Service 2022-02-08 04:37:21 UTC
Thanks for your comment!

Automatically switching the status of this bug to REPORTED so that the KDE team
knows that the bug is ready to get confirmed.

In the future you may also do this yourself when providing needed information.
Comment 5 Halla Rempt 2022-02-14 12:21:18 UTC

*** This bug has been marked as a duplicate of bug 449122 ***