Bug 405490 - crashes when trying to save
Summary: crashes when trying to save
Status: RESOLVED FIXED
Alias: None
Product: krita
Classification: Applications
Component: File formats (show other bugs)
Version: 4.1.7
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-03-15 08:51 UTC by sadeen
Modified: 2019-03-31 12:42 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
attachment-2520-0.html (1.69 KB, text/html)
2019-03-30 16:39 UTC, sadeen
Details

Note You need to log in before you can comment on or make changes to this bug.
Description sadeen 2019-03-15 08:51:45 UTC
SUMMARY


STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
MacOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 Halla Rempt 2019-03-15 08:59:13 UTC
Hi Sadeem,

Obviously, this problem is specific to something you are doing or to your system. If it would happen for everyone, we wouldn't have released Krita. But you're not giving us any information whatsoever, and without a lot more information, we cannot help you. 

Please give us:

* the output of help/system information for bug reports
* a crash log if available: see https://docs.krita.org/en/reference_manual/dr_minw_debugger.html#dr-minw
* information about the image you want to save (color model, channel depth, number of layers, memory consumption)
* which format you are trying to save to
* whether this crash happens no matter which format you are trying to save to, or only for a specific format
* whether you have any non-standard security software such as sandboxie installed -- anything other than Windows defender
* whether you have enabled any extra security features like described in https://docs.krita.org/en/KritaFAQ.html#windows-krita-cannot-save
Comment 2 Bug Janitor Service 2019-03-30 04:33:08 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 3 sadeen 2019-03-30 16:39:13 UTC
Created attachment 119160 [details]
attachment-2520-0.html

I apologize for my lack of response no worries the bug problem was fixed!

On Sat, Mar 30, 2019 at 7:33 AM Bug Janitor Service <
bugzilla_noreply@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=405490
>
> --- Comment #2 from Bug Janitor Service <bug-janitor@kde.org> ---
> 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!
>
> --
> You are receiving this mail because:
> You reported the bug.
Comment 4 Bug Janitor Service 2019-03-31 04:33:09 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.