[krita] [Bug 369497] Crash when creating new large document directly after starting Krita

2016-10-14 Thread Miia Jalkanen via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=369497

--- Comment #9 from Miia Jalkanen  ---
No, I didn't change anything after downloading it and I checked the LUT docker,
OpenColorIO is not selected.

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


[krita] [Bug 369497] Crash when creating new large document directly after starting Krita

2016-10-13 Thread Miia Jalkanen via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=369497

--- Comment #7 from Miia Jalkanen  ---
On Windows 8.1 laptop it crashes also, but the module is different. Version
3.0.1.1, open, File > New, 1600×1200 px, Create, Crash.

krita.exe caused an Access Violation at location 7FFA838C631D in module
ig7icd64.dll Reading from location 1E21.

AddrPC   Params
7FFA838C631D 40794BD0   
ig7icd64.dll!DrvSetLayerPaletteEntries
7FFA837C5245 40913BC0 40794150 3E9ECB00 
ig7icd64.dll!RegisterProcTableCallback
7FFA837C53CE 3E9ECB00 40794150 0004 
ig7icd64.dll!RegisterProcTableCallback
7FFA837CA66A 3FE01010 3E9ECB00 40913BC0 
ig7icd64.dll!RegisterProcTableCallback
7FFA837BE5FA 00238BA0 0001 0001 
ig7icd64.dll!RegisterProcTableCallback
61BCAEC2    
Qt5Gui.dll!QOpenGLShaderProgram::bind
69B4924B 4000 00238E30 3C8B70B0 
libkritaui.dll! ??  
[C:/dev/krita-3.0.1.1/libs/ui/opengl/kis_opengl_canvas2.cpp @ 392]
69B4D0A5    
libkritaui.dll!renderCanvasGL 
[C:/dev/krita-3.0.1.1/libs/ui/opengl/kis_opengl_canvas2.cpp @ 372]
69B4D16C 3C8B70B0 0001 3D0539F0 
libkritaui.dll!paintGL 
[C:/dev/krita-3.0.1.1/libs/ui/opengl/kis_opengl_canvas2.cpp @ 252]
009D80E5 31C4ECF0 69BE3963  
Qt5Widgets.dll!QOpenGLWidget::resizeEvent
009BD828 00800080 01400140 01C00080 
Qt5Widgets.dll!QWidget::event
0097A33C   00260CC0 
Qt5Widgets.dll!QApplicationPrivate::notify_helper
0097F6A0 3C4D2558 3C8B70B0  
Qt5Widgets.dll!QApplication::notify
69C31746 00239520 3C81A598 3C8B70B0 
libkritaui.dll!notify  [C:/dev/krita-3.0.1.1/libs/ui/KisApplication.cpp @ 511]
68A0E9F2  61B20023 00239520 
Qt5Core.dll!QCoreApplication::notifyInternal2
009B5ECD 00239840  E4E4 
Qt5Widgets.dll!QWidgetPrivate::sendPaintEvent
009B66EB 53530001 8E8E7272 21CC3BA0 
Qt5Widgets.dll!QWidgetPrivate::drawWidget
009B71E6 3C59F4B0 3C81A598 3C59F4C8 
Qt5Widgets.dll!QWidgetPrivate::paintSiblingsRecursive
009B6035 3C59EC20 0097A33C  
Qt5Widgets.dll!QWidgetPrivate::drawWidget
009B71E6 3CAAB7A0 3C81A598 3CAAB7B8 
Qt5Widgets.dll!QWidgetPrivate::paintSiblingsRecursive
009B70DA 3CAAB7A0 3C81A598 3CAAB7B8 
Qt5Widgets.dll!QWidgetPrivate::paintSiblingsRecursive
009B70DA 3CAAB7A0 3C81A598 3CAAB7B8 
Qt5Widgets.dll!QWidgetPrivate::paintSiblingsRecursive
009B6035 3CC6E810 3C997E00 3C96AE00 
Qt5Widgets.dll!QWidgetPrivate::drawWidget
009B71E6 3C59F850 3C81A598 3C59F868 
Qt5Widgets.dll!QWidgetPrivate::paintSiblingsRecursive
009B6035 30CB7FC0 3C81A598 30CB7FD8 
Qt5Widgets.dll!QWidgetPrivate::drawWidget
009B71E6 30CB7FC0 3C81A598 30CB7FD8 
Qt5Widgets.dll!QWidgetPrivate::paintSiblingsRecursive
009B6035 61B5E070 61B65714 31FC4950 
Qt5Widgets.dll!QWidgetPrivate::drawWidget
009B71E6 31FC4880 3C81A598 31FC4898 
Qt5Widgets.dll!QWidgetPrivate::paintSiblingsRecursive
009B6035 2A3A4150 3C81A598 2A3A4168 
Qt5Widgets.dll!QWidgetPrivate::drawWidget
009B71E6 2A3A4150 3C81A598 2A3A4168 
Qt5Widgets.dll!QWidgetPrivate::paintSiblingsRecursive
009B70DA 2A3A4150 3C81A598 2A3A4168 
Qt5Widgets.dll!QWidgetPrivate::paintSiblingsRecursive
009B6035 31EB8A40 3C81A598 31EB8A58 
Qt5Widgets.dll!QWidgetPrivate::drawWidget
009B71E6 31EB8A40 3C81A598 31EB8A58 
Qt5Widgets.dll!QWidgetPrivate::paintSiblingsRecursive
009B70DA 31EB8A40 3C81A598 31EB8A58 
Qt5Widgets.dll!QWidgetPrivate::paintSiblingsRecursive
009B70DA 31EB8A40 3C81A598 31EB8A58 
Qt5Widgets.dll!QWidgetPrivate::paintSiblingsRecursive
009B70DA 31EB8A40 3C81A598 31EB8A58 
Qt5Widgets.dll!QWidgetPrivate::paintSiblingsRecursive
009B70DA 31EB8A40 3C81A598 31EB8A58 
Qt5Widgets.dll!QWidgetPrivate::paintSiblingsRecursive
009B70DA 31EB8A40 3C81A598 31EB8A58 
Qt5Widgets.dll!QWidgetPrivate::paintSiblingsRecursive
009B70DA 31EB8A40 

[krita] [Bug 370566] Larger documents do not get saved with Save as

2016-10-13 Thread Miia Jalkanen via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=370566

--- Comment #3 from Miia Jalkanen  ---
Looks like this a duplicate of this issue:
https://bugs.kde.org/show_bug.cgi?id=369368. 

Same behaviour with the saving dialog, menus and canvas, and also on Win 7.

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


[krita] [Bug 370566] Larger documents do not get saved with Save as

2016-10-13 Thread Miia Jalkanen via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=370566

--- Comment #2 from Miia Jalkanen  ---
Yes, every time. I have only Windows 7 on which I can test currently. Is there
anything else I could try, besides removing the kritarc file, or any other
information I could collect to help with this? Obviously, if both of these only
happen on my pc, there has to be something wrong with it.

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


[krita] [Bug 370566] New: Larger documents do not get saved with Save as

2016-10-12 Thread Miia Jalkanen via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=370566

Bug ID: 370566
   Summary: Larger documents do not get saved with Save as
   Product: krita
   Version: 3.0.1
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: jalmi...@gmail.com

When saving a file, a small Krita dialog with text "Saving document..." and a
progress bar is shown. This dialog remains there infinitely. Krita does not
respond to any mouse clicks, but it does not crash either. No file appears into
the selected location, but sometimes the name given to the file is displayed in
Krita window's top bar, along with the unsaved changes asterisk.

After 5 minutes or so, I clicked the top corner x to close the dialog. The
dialog disappears, mouse cursor remains on busy state but menus, settings
window, dockers etc. can now be opened. Painting on the canvas does not work.
Krita window's bottom info bar flashes every 15 seconds or so. 

Closing Krita from Taskbar finally crashes it, and "Krita has stopped working"
dialog is shown. Backtrace from there attached (from 3.0.1.90 beta version).

On the second time, after selecting Close all windows, "Document has been
modified, do you want to save?" dialog is shown. Answering Yes does nothing,
rigorous saving just seems to continue again. Answering No crashes Krita,
Backtrace attached (from 3.0.1.1 debug version).

Could this have something to do the same thing that causes bug 369497, since
saving small documents (e.g. 100 × 100 px) works, but saving larger ones does
not?


Reproducible: Always

Steps to Reproduce:
1. Create document (with small-one-first-workaround steps explained on bug
369497), 1920 × 1080 pixels.
2. Select File > Save as. 
3. Select location, fill in the name, click Save. 


Actual Results:  
Saving does not happen within multiple minutes time.

Expected Results:  
Document is saved within a reasonable period of time and Krita returns to
responsive state.

Backtrace from 3.0.1.90 beta version

krita.exe caused an Unknown [0xC374] Exception at location 77B2F262
in module ntdll.dll.

AddrPC   Params
77B2F262 0002 0023 C0482C30 
ntdll.dll!RtlReportCriticalFailure
77B2F846 0022ADC0 0022ADC0 C0482C30 
ntdll.dll!RtlpReportHeapFailure
77B30412 0183 0022ADC0  
ntdll.dll!RtlpHeapHandleError
77B32084 0022ADB0   
ntdll.dll!RtlpLogHeapFailure
77ACA162 A67F78C0 0180 001E 
ntdll.dll!RtlFreeHeap
07FEFF3910C8  AB385870 0180 
msvcrt.dll!free
68A35235 941437B8 AAD30190 AAD30190 
Qt5Core.dll!QObjectPrivate::deleteChildren
61E08D1F AAD30190 AAD30190 AAD30190 
Qt5Widgets.dll!QWidget::~QWidget
00DB05D4 C03BE780 AAD30190 00226680 
libkritawidgetutils.dll!KMainWindow::~KMainWindow
69C812B1 68D06830  AAD30190 
libkritaui.dll!KisMainWindow::~KisMainWindow
69C8131D AA196DC0 C03C2960 C03BE780 
libkritaui.dll!KisMainWindow::~KisMainWindow
68A2FC75 0030 03BA92D0 03BA92B0 
Qt5Core.dll!QObject::event
61E0DA2C C03EB6A0 C03EB6A0 C03BE780 
Qt5Widgets.dll!QWidget::event
61F0DEDB 0001 68A0E7BD AAD44A90 
Qt5Widgets.dll!QMainWindow::event
00DB270A 0022FDA0  0022FDA0 
libkritawidgetutils.dll!KMainWindow::event
61DCA33C AAD44A90 778688D4 C03C00C0 
Qt5Widgets.dll!QApplicationPrivate::notify_helper
61DCF6A0 00010003 AAD30190  
Qt5Widgets.dll!QApplication::notify
69C53D86  778578CC 0001 
libkritaui.dll!KisApplication::notify
68A0E9F2 00226D78   
Qt5Core.dll!QCoreApplication::notifyInternal2
68A13300 FFEB   
Qt5Core.dll!QCoreApplicationPrivate::sendPostedEvents
03E9AB1E 0102 00226E00 0002 
qwindows.dll!qt_plugin_instance
68A5577A  0038 00226F38 
Qt5Core.dll!QEventDispatcherWin32Private::sendTimerEvent
77869BDD 00227050 68A55450 00227050 
USER32.dll!UserCallWinProcCheckWow
778698E2 03885AB0 03885AB0 68A55450 
USER32.dll!DispatchMessageWorker
68A54EB3 039480D0  0022A350 
Qt5Core.dll!QEventDispatcherWin32::processEvents
03E9AB05 A36AB5E0 

[krita] [Bug 370562] New: Crash after removing a frame that has an active transform tool selection

2016-10-12 Thread Miia Jalkanen via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=370562

Bug ID: 370562
   Summary: Crash after removing a frame that has an active
transform tool selection
   Product: krita
   Version: 3.0.1
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: Animation
  Assignee: krita-bugs-n...@kde.org
  Reporter: jalmi...@gmail.com

Krita crashes, if a frame with transform tool active is removed and another
frame selected after that.

Reproducible: Always

Steps to Reproduce:
1. Create document (1920 × 1080, 3 layers, first one with fill)
2. Animation workspace opens by default
3. Draw something onto the canvas
4. In animation panel, click New frame to create frame there, on the timeline's
first slot
5. Right-click some other slot on timeline, select Copy frame
6. Select the Transform tool, which automatically selects the layer contents.
Notice, that you want some parts of the drawing to be on an another layer.
7. Right-click the most recent frame, select Remove frame. Frame is deleted
from timeline, the drawing and the transform tool's selection remain visible on
the canvas.
8. Click on the first frame on the timeline. Krita crashes. Looks like this is
caused only by the transformation tool, active selection with outline selection
etc. tools does not crash.

Actual Results:  
Krita crashes

Expected Results:  
The selected frame is activated, and either transform tool is deactivated, like
happens when selecting another frame without removing frames, or apply the
transform tool selection to the newly selected frame's contents directly.

Happens on both Krita 3.0 RC 1 and Beta 3.0.1.90. Cannot collect backtrace on
the debug version (3.0.1.1), because it goes to Not responding state already in
step 3, but does not crash.

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

[krita] [Bug 370562] Crash after removing a frame that has an active transform tool selection

2016-10-12 Thread Miia Jalkanen via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=370562

--- Comment #1 from Miia Jalkanen  ---
krita.exe caused an Access Violation at location 6F514B95 in module
libkritaimage.dll Writing to location 0090.

AddrPC   Params
6F514B95 A7F28980 6F532436 0001 
libkritaimage.dll!KisPaintDeviceFramesInterface::invalidateFrameCache
6F531EE6  6FCC1FF6  
libkritaimage.dll!KisTransactionData::startUpdates
6F533427 131AD6D0 0846FBB0  
libkritaimage.dll!KisTransactionData::undo
6F4B081D 027F   
libkritaimage.dll!KisStrokeStrategyUndoCommandBased::doStrokeCallback
1B09B691  07FEFE2713D2 0002 
kritatooltransform.dll!TransformStrokeStrategy::doStrokeCallback
6F60DCA3  0084BFCE  
libkritaimage.dll!KisUpdateJobItem::run
0084D7F5 0DF1F480 A2846A40 0A90C580 
Qt5Core.dll!QThreadPoolPrivate::enqueueTask
0084FD4C 0A90C580   
Qt5Core.dll!QThread::setTerminationEnabled
07FEFE27415F 07FEFE301EA0 0A90C580  
msvcrt.dll!_endthreadex
07FEFE276EBD    
msvcrt.dll!_endthreadex
772259CD    
kernel32.dll!BaseThreadInitThunk
7735A2E1    
ntdll.dll!RtlUserThreadStart

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


[krita] [Bug 369497] Crash when creating new large document directly after starting Krita

2016-10-07 Thread Miia Jalkanen via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=369497

--- Comment #6 from Miia Jalkanen  ---
No, no sandboxie or anything like that.

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


[krita] [Bug 369497] Crash when creating new large document directly after starting Krita

2016-10-04 Thread Miia Jalkanen via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=369497

--- Comment #4 from Miia Jalkanen  ---
Created attachment 101415
  --> https://bugs.kde.org/attachment.cgi?id=101415=edit
Backtrace from 3.0.1.1

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


[krita] [Bug 369497] Crash when creating new large document directly after starting Krita

2016-10-04 Thread Miia Jalkanen via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=369497

--- Comment #3 from Miia Jalkanen  ---
Created attachment 101414
  --> https://bugs.kde.org/attachment.cgi?id=101414=edit
Backtrace from 3.0.1.90

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


[krita] [Bug 369497] Crash when creating new large document directly after starting Krita

2016-10-04 Thread Miia Jalkanen via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=369497

--- Comment #2 from Miia Jalkanen  ---
Hi Boudewijn,

I removed kritarc from C:\Users\\AppData\Local\krita and tried again, and
it still happens. I added the backtraces produced by DrMingw as attachments.
First one is from Krita 3.0.1.90 (beta) and the other from latest version
available on the FAQ page (krita-3.0.1.1-x64-dbg).

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


[krita] [Bug 369497] New: Crash when creating new large document directly after starting Krita

2016-09-28 Thread Miia Jalkanen via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=369497

Bug ID: 369497
   Summary: Crash when creating new large document directly after
starting Krita
   Product: krita
   Version: 3.0.1
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: jalmi...@gmail.com

When creating a large document, for example predefined A4 300 ppi, after
opening Krita, it crashes. If however a small document, for example 100 × 100
px, is created first and closed, then creating the same large document
succeeds. 

Reproducible: Always

Steps to Reproduce:
1. Open Krita. 
2. Select File > New. On Custom Document page, select A4 or A3 (300 ppi) from
Predefined and click Create. 
3. Dialog "krita.exe has stopped working" appears immediately. 
4. Close the program.
5. Open Krita again.
6. Create 100×100 px document similarly.
7. Select File > Close.
8. Repeat step 2.



Actual Results:  
9. Large document is created and Krita does not crash

Expected Results:  
New document of desired size can be created without having to first create the
small one.

Krita 3.0.1.90

Debugger: An unhandled win32 exception occured in krita.exe.

Crash info:

Problem signature:
  Problem Event Name:APPCRASH
  Application Name:krita.exe
  Application Version:0.0.0.0
  Application Timestamp:
  Fault Module Name:libkritaimage.dll
  Fault Module Version:0.0.0.0
  Fault Module Timestamp:00010401
  Exception Code:c005
  Exception Offset:00261290
  OS Version:6.1.7601.2.1.0.256.48
  Locale ID:1035
  Additional Information 1:5c3f
  Additional Information 2:5c3f1e643c259668a63456693dcbae2e
  Additional Information 3:a8fe
  Additional Information 4:a8fe8993bd848dd565875a86b95a51ef


Windows 7 Professional SP 1 64-bit
Intel Core i7-4712MQ CPU @2.30GHz 
8,00 GB RAM
NVIDIA GeForce GT 740M
Driver: NVIDIA 9.18.13.4520

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

[krita] [Bug 364887] [WACOM] Pressure Sensitivity Not Working (only for Krita)

2016-08-20 Thread Miia Jalkanen via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364887

Miia Jalkanen  changed:

   What|Removed |Added

 CC||jalmi...@gmail.com

--- Comment #2 from Miia Jalkanen  ---
Losing Wacom pressure sensitivity happens to me quite often, too, and has been
there with Krita 2.8, 2.9 and 3.0. 

I haven't been able to precisely point out the reason for it, as it happens
really randomly: sometimes after pc waking from sleep with Krita open, or after
Krita just being open while using other software, or sometimes straight away
after Krita is started, but not nearly always in any of these cases. 

The driver I use is an old one, from something like 2013. Had to try every
driver version from newest 6.3.11 backwards to 6.3.6 make it work at all in the
first place. Maybe you could try with different driver version? The older
versions are all available on Wacom drivers download page.

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


[krita] [Bug 363755] Moving a Saturation layer crashes

2016-08-20 Thread Miia Jalkanen via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=363755

--- Comment #4 from Miia Jalkanen  ---
Hi Boudewijn, 
Glad to hear if this helped to fix something. I thought this too was related to
my mobile GPU like the other issue I reported. I did try it with every other
layer mode, but only Saturation caused crash. I tested it now (very briefly)
with krita-3.0.1-Alpha-ef558bb and it seems not occur any more. 

Sorry Scott, for some reason I had missed any notification about your question!
Unfortunately I can currently only test Krita on this pc (which is not Surface
Pro btw but Lenovo Thinkpad).

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


[krita] [Bug 364254] Whole Krita window is black after pc sleeping

2016-06-12 Thread Miia Jalkanen via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364254

--- Comment #1 from Miia Jalkanen  ---
Krita 3.0 (git f0cbffc)
Windows 7 Professional SP 1 64-bit
Intel Core i7-4712MQ CPU @2.30GHz 
8,00 GB RAM
NVIDIA GeForce GT 740M
Driver: NVIDIA 9.18.13.4520

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


[krita] [Bug 364254] New: Whole Krita window is black after pc sleeping

2016-06-12 Thread Miia Jalkanen via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364254

Bug ID: 364254
   Summary: Whole Krita window is black after pc sleeping
   Product: krita
   Version: 3.0
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: jalmi...@gmail.com

After waking computer from sleep, the whole Krita window remains black. Tooltip
texts and right click context menus are shown.

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


[krita] [Bug 362064] Saving as template creates only .desktop

2016-06-02 Thread Miia Jalkanen via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362064

Miia Jalkanen  changed:

   What|Removed |Added

 CC||jalmi...@gmail.com

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