Bug 451533

Summary: Closed without any messenge
Product: [Applications] krita Reporter: Roberto Reis <roberto.santos.reis>
Component: G'Mic for KritaAssignee: Krita Bugs <krita-bugs-null>
Status: RESOLVED FIXED    
Severity: crash CC: amy, halla
Priority: NOR    
Version First Reported In: 5.0.2   
Target Milestone: ---   
Platform: Mint (Ubuntu based)   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: attachment-17236-0.html
krita.log
krita-sysinfo.log

Description Roberto Reis 2022-03-15 15:08:41 UTC
just Closed after try save. In the work, i use the plugin and a wacon tablet. The vertion is a flatpak
Comment 1 amyspark 2022-03-15 16:25:11 UTC
Hi! We need a crash log before we can act on Krita crashes; this is even more critical with outside components like G'MIC.

See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports and https://docs.krita.org/en/reference_manual/sharing_krita_logs.html?highlight=crash.
Comment 2 Roberto Reis 2022-03-15 16:46:37 UTC
Created attachment 147513 [details]
attachment-17236-0.html

The link refer the log file in$HOME/.local/share/krita.log

I'm using a flatpak version and can't find the log file. I´m looking for 
it on google to solve this and add file here.



Thanks


Em 15/03/2022 13:25, amyspark escreveu:

> https://bugs.kde.org/show_bug.cgi?id=451533
>
> amyspark<amy@amyspark.me>  changed:
>
>             What    |Removed                     |Added
> ----------------------------------------------------------------------------
>           Resolution|---                         |WAITINGFORINFO
>               Status|REPORTED                    |NEEDSINFO
>                   CC|                            |amy@amyspark.me
>
> --- Comment #1 from amyspark<amy@amyspark.me>  ---
> Hi! We need a crash log before we can act on Krita crashes; this is even more
> critical with outside components like G'MIC.
>
> See
> https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
> and
> https://docs.krita.org/en/reference_manual/sharing_krita_logs.html?highlight=crash.
>
Comment 3 Roberto Reis 2022-03-15 16:53:55 UTC
Created attachment 147514 [details]
krita.log

The file on flatpak path for site update : 
$HOME//.var/app/org.kde.krita/data




Em 15/03/2022 13:43, Halla Rempt escreveu:
> https://bugs.kde.org/show_bug.cgi?id=451533
>
> Halla Rempt <halla@valdyas.org> changed:
>
>             What    |Removed                     |Added
> ----------------------------------------------------------------------------
>             Severity|critical                    |crash
>                   CC|                            |halla@valdyas.org
>
Comment 4 Roberto Reis 2022-03-15 16:53:56 UTC
Created attachment 147515 [details]
krita-sysinfo.log
Comment 5 Bug Janitor Service 2022-03-16 04:35:29 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 amyspark 2022-03-17 16:45:48 UTC
Hi! we still need the backtrace of the crash in order to triage the bug.

Can you reproduce it with the latest nightly build?
Comment 7 Roberto Reis 2022-03-17 17:58:46 UTC
No. With the new installation using .appimage , appearance more stable. 
No crash, no screen bugs and not problem with manual selection tool.

The flathub mirrored the image and make the half black screen. Now, all 
things run smooth on appimage.


Thanks


Em 17/03/2022 13:45, amyspark escreveu:
> https://bugs.kde.org/show_bug.cgi?id=451533
>
> amyspark <amy@amyspark.me> changed:
>
>             What    |Removed                     |Added
> ----------------------------------------------------------------------------
>           Resolution|---                         |WAITINGFORINFO
>               Status|REPORTED                    |NEEDSINFO
>
> --- Comment #6 from amyspark <amy@amyspark.me> ---
> Hi! we still need the backtrace of the crash in order to triage the bug.
>
> Can you reproduce it with the latest nightly build?
>