Bug 449017 - Krita crashes with right click.
Summary: Krita crashes with right click.
Status: RESOLVED DUPLICATE of bug 447868
Alias: None
Product: krita
Classification: Applications
Component: General (show other bugs)
Version: 5.0.2
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-01-23 14:04 UTC by budd.chris71
Modified: 2022-01-23 16:35 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Krita log (40.43 KB, text/plain)
2022-01-23 14:05 UTC, budd.chris71
Details
attachment-32630-0.html (2.20 KB, text/html)
2022-01-23 15:48 UTC, budd.chris71
Details
KritaSystemInformation.txt (5.60 KB, text/plain)
2022-01-23 16:13 UTC, budd.chris71
Details

Note You need to log in before you can comment on or make changes to this bug.
Description budd.chris71 2022-01-23 14:04:00 UTC
SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. open Krita
2. select a project
3. Right click anywhere on workspace

OBSERVED RESULT
Krita goes into processing and then crashes. 

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 budd.chris71 2022-01-23 14:05:22 UTC
Created attachment 145803 [details]
Krita log
Comment 2 Alvin Wong 2022-01-23 15:31:27 UTC
Can you provide the information from "Help -> Show system information for bug reports"?

Also, the info you pasted here does not contain a crash backtrace, can you try finding it by following https://docs.krita.org/en/reference_manual/dr_minw_debugger.html#getting-a-backtrace ?
Comment 3 budd.chris71 2022-01-23 15:48:56 UTC
Created attachment 145805 [details]
attachment-32630-0.html

i cannot find a Kritacrash.log and all i could send you was what i already
sent.
the Krita program gets the little processing circle, which doesn't finish
and then the X n the top right corner turns red and shortly, Krita closes
on it's own.
That is all the help i can provide.
The trigger, and i have done this several times, is right clicking on the
workspace.
I would be happy to reinstall the rogram if that may help.
Chris

On Sun, Jan 23, 2022 at 9:31 AM Alvin Wong <bugzilla_noreply@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=449017
>
> Alvin Wong <alvin@alvinhc.com> changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>              Status|REPORTED                    |NEEDSINFO
>          Resolution|---                         |WAITINGFORINFO
>                  CC|                            |alvin@alvinhc.com
>
> --- Comment #2 from Alvin Wong <alvin@alvinhc.com> ---
> Can you provide the information from "Help -> Show system information for
> bug
> reports"?
>
> Also, the info you pasted here does not contain a crash backtrace, can you
> try
> finding it by following
>
> https://docs.krita.org/en/reference_manual/dr_minw_debugger.html#getting-a-backtrace
> ?
>
> --
> You are receiving this mail because:
> You reported the bug.
Comment 4 Alvin Wong 2022-01-23 16:09:24 UTC
How about the text from "Help -> Show system information for bug reports"? (Not "Show Krita log for bug report" which you already provided.)
Comment 5 budd.chris71 2022-01-23 16:13:12 UTC
Created attachment 145806 [details]
KritaSystemInformation.txt

Here is what came up. I hope this helps.

On Sun, Jan 23, 2022 at 10:09 AM Alvin Wong <bugzilla_noreply@kde.org>
wrote:

> https://bugs.kde.org/show_bug.cgi?id=449017
>
> --- Comment #4 from Alvin Wong <alvin@alvinhc.com> ---
> How about the text from "Help -> Show system information for bug reports"?
> (Not
> "Show Krita log for bug report" which you already provided.)
>
> --
> You are receiving this mail because:
> You reported the bug.
Comment 6 Alvin Wong 2022-01-23 16:35:41 UTC
Thanks, it is likely the same issue as bug 447868.

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