Bug 454171 - Krita Crashes when making a new file/opening existing file
Summary: Krita Crashes when making a new file/opening existing file
Status: RESOLVED WORKSFORME
Alias: None
Product: krita
Classification: Applications
Component: * Unknown (show other bugs)
Version: 5.0.6
Platform: Appimage Linux
: NOR crash
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-05-21 16:52 UTC by mjarvihaavisto
Modified: 2022-08-17 04:35 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Text that Krita advised to paste (33.48 KB, text/plain)
2022-05-21 16:52 UTC, mjarvihaavisto
Details

Note You need to log in before you can comment on or make changes to this bug.
Description mjarvihaavisto 2022-05-21 16:52:49 UTC
Created attachment 149086 [details]
Text that Krita advised to paste

SUMMARY
I was trying to make a new file with Krita on Flathub, which is version 5.0.2, but the canvas didn't appear. I then tried opening an exisisting file, but that resulted in the same thing happening. I could move the docks, but they appeared to updated only when I closed and re-opened Krita. I could also select tools and open menus, but they weren't much help as I couldn't see the canvas. I tried doing the same on the newest version, 5.0.6, which resulted in a crash.

STEPS TO REPRODUCE
1. Make a new file or open an existing one
2. Crash

OBSERVED RESULT
Krita Crashes

EXPECTED RESULT
Krita does not crash

SOFTWARE/OS VERSIONS
Krita: 5.0.6
OS: Fedora Linux 36 Workstation edition
Kernel: 5.17.8-300.fc36.x86_64
Comment 1 Halla Rempt 2022-05-21 16:54:51 UTC
So, you're not, actually, using the appimage?
Comment 2 mjarvihaavisto 2022-05-21 17:04:41 UTC
(In reply to Halla Rempt from comment #1)
> So, you're not, actually, using the appimage?

I am using the appimage. I saw that the documentation on reporting bugs advices to try replicating the bug on the latest version of Krita, which I did, and it resulted in Krita crashing! My apologies for the confusion.
Comment 3 Halla Rempt 2022-05-21 17:46:07 UTC
That's pretty strange, since we've got a bunch of reports about crashes recently that center on the file dialog that are all about platform integration -- which the appimage doesn't support. You also mention flathub?
Comment 4 mjarvihaavisto 2022-05-21 18:23:56 UTC
(In reply to Halla Rempt from comment #3)
> That's pretty strange, since we've got a bunch of reports about crashes
> recently that center on the file dialog that are all about platform
> integration -- which the appimage doesn't support. You also mention flathub?

I did mention flathub, yes. I apologise if I was not clear enough on this, but before I downloaded the newest appimage of Krita to test if my issue was present on the newest version, I had Krita already downloaded from flathub. It was working just fine before, but when I tried making a new file with it today, it didn't work as I was expecting it to. When I make a new file or open an existing one with the version on flathub, the welcome screen is still there. I can still resize docks and use the menus, like file, layers and the settings menu, but I could not see the canvas. That's when I tried the newest version, which I downloaded from the Krita website, and it simply crashes when I make or open a file. I wonder if this happened because I upgraded from Fedora 35 to Fedora 36? That's about the only thing I remember changing from the last time I tried Krita.
Comment 5 Bug Janitor Service 2022-05-22 04:35:40 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 6 Alvin Wong 2022-06-02 15:34:04 UTC
This is probably just another case of NVIDIA driver and/or (x)wayland striking again, like bug 454750 and bug 452880...
Comment 7 Dmitry Kazakov 2022-07-18 07:02:37 UTC
Hi, mjarvihaavisto!

The problem looks like an NVIDIA driver update issue. The reporter of the other bug 452880 said that the problem has been solved for him/her by updating driver to "nvidia prime". Could you also try that?

The source link: https://bugs.kde.org/show_bug.cgi?id=452880#c10
Comment 8 Bug Janitor Service 2022-08-02 04:35:43 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 9 Bug Janitor Service 2022-08-17 04:35:45 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!