Bug 376006 - Crashed on new painting!
Summary: Crashed on new painting!
Status: RESOLVED DUPLICATE of bug 375901
Alias: None
Product: krita
Classification: Applications
Component: General (show other bugs)
Version: 3.1.1
Platform: Microsoft Windows Microsoft Windows
: NOR crash
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-02-04 15:42 UTC by gamedj2015
Modified: 2017-02-06 08:33 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
attachment-7930-0.html (2.81 KB, text/html)
2017-02-04 15:52 UTC, gamedj2015
Details
attachment-26373-0.html (1.30 KB, text/html)
2017-02-04 22:18 UTC, gamedj2015
Details
attachment-28558-0.html (2.98 KB, text/html)
2017-02-04 23:05 UTC, gamedj2015
Details

Note You need to log in before you can comment on or make changes to this bug.
Description gamedj2015 2017-02-04 15:42:13 UTC
Whenever I make a new file, it "loads" it, then crashes shortly after it happened!

I have a x64 Windows 8.1
Comment 1 Halla Rempt 2017-02-04 15:44:51 UTC
Hi,

Since Krita doesn't crash on any of my four windows test systems, this must be something specific to your system.

First check whether disabling opengl makes a difference. If that doesn't make a difference, please make a crash log (see https://docs.krita.org/Dr._Mingw_debugger) and attach it to this bug report.
Comment 2 gamedj2015 2017-02-04 15:52:37 UTC
Created attachment 103824 [details]
attachment-7930-0.html

Because I'm not very familiar with Krita, could you tell me how to disable OpenGL?
And the OpenGL reporting is disabled for me, so I can't tell if that's it, or you need something else. 

    Datuma 16:44 Subota, 4. Veljača 2017., Boudewijn Rempt <bugzilla_noreply@kde.org> je napisao:
 

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

Boudewijn Rempt <boud@valdyas.org> changed:

          What    |Removed                    |Added
----------------------------------------------------------------------------
                CC|                            |boud@valdyas.org
        Resolution|---                        |WAITINGFORINFO
            Status|UNCONFIRMED                |NEEDSINFO

--- Comment #1 from Boudewijn Rempt <boud@valdyas.org> ---
Hi,

Since Krita doesn't crash on any of my four windows test systems, this must be
something specific to your system.

First check whether disabling opengl makes a difference. If that doesn't make a
difference, please make a crash log (see
https://docs.krita.org/Dr._Mingw_debugger) and attach it to this bug report.
Comment 3 Halla Rempt 2017-02-04 16:22:17 UTC
Settings/Configure Krita/Display
Comment 4 gamedj2015 2017-02-04 22:18:29 UTC
Created attachment 103833 [details]
attachment-26373-0.html

Alright, that helped. Thanks for telling me and helping me! You're also very quick!! =D 

    Datuma 17:58 Subota, 4. Veljača 2017., Boudewijn Rempt <bugzilla_noreply@kde.org> je napisao:
 

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

--- Comment #3 from Boudewijn Rempt <boud@valdyas.org> ---
Settings/Configure Krita/Display
Comment 5 gamedj2015 2017-02-04 23:05:37 UTC
Created attachment 103834 [details]
attachment-28558-0.html

Hey, just if you don't mind, can you tell me this too?
I was messing with the Brushes, and I accidentally changed the "preset" of one I want to use alot, how do I reset back to default?
I used the F5 tactic. =( 

    Datuma 23:18 Subota, 4. Veljača 2017., Rony Ljevar <gamedj2015@yahoo.com> je napisao:
 

 Alright, that helped. Thanks for telling me and helping me! You're also very quick!! =D 

    Datuma 17:58 Subota, 4. Veljača 2017., Boudewijn Rempt <bugzilla_noreply@kde.org> je napisao:
 

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

--- Comment #3 from Boudewijn Rempt <boud@valdyas.org> ---
Settings/Configure Krita/Display
Comment 6 Halla Rempt 2017-02-06 08:28:44 UTC
If you overwrite a default brush, you can get the old one back by opening the resources folder (settings/manage resources/open resource folder) and removing the local copy.
Comment 7 Halla Rempt 2017-02-06 08:33:51 UTC
PLease check the bug I've marked as a duplicate -- that has some information on driver versions. With a correct driver, you probably won't have the problem even if opengl is enabled.

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