Created attachment 130926 [details] Problem Report File SUMMARY When double clicking on .kra file, Krita 4.3.0 crashes repeatedly and consistently STEPS TO REPRODUCE 1. Double Click .kra file using 4.3.0 Krita 2. Finally when Krita opens, close the app without opening any file and it crashes 3. below you will find the error from the OS OBSERVED RESULT Process: krita [1799] Path: /private/var/folders/*/krita.app/Contents/MacOS/krita Identifier: org.krita Version: 4.3.0 (???) Code Type: X86-64 (Native) Parent Process: ??? [1] Responsible: krita [1799] User ID: 501 Date/Time: 2020-08-16 23:43:39.911 -0500 OS Version: Mac OS X 10.13.6 (17G14019) Report Version: 12 Anonymous UUID: 3BD0965A-86E6-7287-EB46-AAE7CE00265E Sleep/Wake UUID: 276DB2BA-A467-4D6A-B8E0-87176B361CE0 Time Awake Since Boot: 19000 seconds Time Since Wake: 13000 seconds System Integrity Protection: enabled Notes: Translocated Process Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000 Exception Note: EXC_CORPSE_NOTIFY Termination Signal: Segmentation fault: 11 Termination Reason: Namespace SIGNAL, Code 0xb Terminating Process: exc handler [0]
I cannot conirm this. However if your want to help some more, could you attach the missing part of the crash report after "Terrminating process:" There should be threads information.
Created attachment 130938 [details] attachment-12316-0.html Here is the file that I had hoped that was attached in the 1st email. It is in rich text format and as a Word document. I hope this helps you. Allen > On Aug 17, 2020, at 11:49 AM, vanyossi <bugzilla_noreply@kde.org> wrote: > > https://bugs.kde.org/show_bug.cgi?id=425442 > > vanyossi <ghevan@gmail.com> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Resolution|--- |WAITINGFORINFO > CC| |ghevan@gmail.com > Status|REPORTED |NEEDSINFO > > --- Comment #1 from vanyossi <ghevan@gmail.com> --- > I cannot conirm this. > > However if your want to help some more, could you attach the missing part of > the crash report after "Terrminating process:" There should be threads > information. > > -- > You are receiving this mail because: > You reported the bug.
Created attachment 130939 [details] attachment-12316-1.html
Created attachment 130940 [details] attachment-12316-2.html
Created attachment 130941 [details] Krita Problem Report.rtf
Created attachment 130942 [details] Krita Problem Report.docx
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.
Does this also happen if you disable "native file dialogs" in krita's setttings?
Created attachment 130955 [details] attachment-5682-0.html It already was disabled for me. I downloaded the latest version and installed it as is. I made no changes to that option after installation. I then changed the option and the same results happened. Here are the error report files again. Allen > On Aug 18, 2020, at 2:27 AM, Boudewijn Rempt <bugzilla_noreply@kde.org> wrote: > > https://bugs.kde.org/show_bug.cgi?id=425442 > > Boudewijn Rempt <boud@valdyas.org> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Resolution|--- |WAITINGFORINFO > CC| |boud@valdyas.org > Status|REPORTED |NEEDSINFO > > --- Comment #8 from Boudewijn Rempt <boud@valdyas.org> --- > Does this also happen if you disable "native file dialogs" in krita's > setttings? > > -- > You are receiving this mail because: > You reported the bug.
Created attachment 130956 [details] attachment-5682-1.html
Created attachment 130957 [details] attachment-5682-2.html
Created attachment 130958 [details] Krita Error Report.rtf
Created attachment 130959 [details] Krita Error Report.pdf
Hm... So, what happens if you _enable_ the option? And what happens if you run Krita as another user, i.e. with a completely clean installation?
I’ve no reason to execute Rita as another user. I have executed krita both with and without this option. I attacked the érrelo report files in my last email. -Allen "Whatever hasn't killed me...had better start running." :) From my iPad Air > On Aug 18, 2020, at 3:36 AM, Boudewijn Rempt <bugzilla_noreply@kde.org> wrote: > > https://bugs.kde.org/show_bug.cgi?id=425442 > > --- Comment #14 from Boudewijn Rempt <boud@valdyas.org> --- > Hm... So, what happens if you _enable_ the option? And what happens if you run > Krita as another user, i.e. with a completely clean installation? > > -- > You are receiving this mail because: > You reported the bug.
i know the reason of this bug and was working on a fix. it only happens if krita is not open before double clicking. This is a duplicate. Closing *** This bug has been marked as a duplicate of bug 421448 ***
Created attachment 130988 [details] attachment-6339-0.html Thx for finding this bug as a dup. The sis good!! That means it’s been found already and is known. It also means that you’re doing more testing to determine if it’s fixed or not. Looking forward to the fix 😄 😄 Allen > On Aug 18, 2020, at 4:41 PM, vanyossi <bugzilla_noreply@kde.org> wrote: > > https://bugs.kde.org/show_bug.cgi?id=425442 > > vanyossi <ghevan@gmail.com> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Status|NEEDSINFO |RESOLVED > Resolution|WAITINGFORINFO |DUPLICATE > > --- Comment #16 from vanyossi <ghevan@gmail.com> --- > i know the reason of this bug and was working on a fix. it only happens if > krita is not open before double clicking. This is a duplicate. > > Closing > > *** This bug has been marked as a duplicate of bug 421448 *** > > -- > You are receiving this mail because: > You reported the bug.