https://bugs.kde.org/show_bug.cgi?id=469645

--- Comment #5 from djdarius...@gmail.com ---
Here is the file
https://drive.google.com/file/d/1PWeE10XlcFdGWBU-Qz0bzZfnGWUfgXNW/view?usp=sharing
I believe it is crashing because after I finish the drawing and save it as
a png i go back to that same file and change it back to a kra file and draw
on it which then eventually crashes. but when i reopen krita it
doesnt crash again until i repeat what i just said.

On Mon, 22 May 2023 at 16:26, Tiar <bugzilla_nore...@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=469645
>
> Tiar <tamtamy.tym...@gmail.com> changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>              Status|REPORTED                    |NEEDSINFO
>          Resolution|---                         |WAITINGFORINFO
>                  CC|                            |tamtamy.tym...@gmail.com
>
> --- Comment #4 from Tiar <tamtamy.tym...@gmail.com> ---
> There are three ways how you can do it:
> 1) Easiest, but with size limit: you can visit
> https://bugs.kde.org/show_bug.cgi?id=469645 (this is the website for the
> bug
> report), there will be a list of Attachments. Underneath there is text
> "Add an
> attachment". Press it, then you'll see another page. There will be "Browse"
> button, click it, find the file that causes Krita to crash, add some text
> in
> Description field, and press "Submit".
> 2) You can share it on Google Drive (remember to add the viewing access for
> people having the link) or Dropbox or similar service.
> 3) If it's really private (or you can't show it to public because it's a
> commission for a client etc.), you can send an email from gmail to
> mentioned
> email address: vur...@gmail.com with the file as an attachment.
>
> It's best to use (1) or (2) so all developers have access to it.
>
> --
> You are receiving this mail because:
> You reported the bug.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to