[krita] [Bug 365142] Clone_tool crash ctrl+LMB

[1DrawingPerDay via KDE Bugzilla]

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

1DrawingPerDay  changed:

   What|Removed |Added

 CC|onedrawingper...@yahoo.com  |

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

[krita] [Bug 363124] Light green brush cursor border hard to see

[1DrawingPerDay via KDE Bugzilla]

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

--- Comment #8 from 1DrawingPerDay  ---
@Boudewijn Rempt 
ATI Mobility Radeon HD 3650 with the legacy AMD Catalyst driver.

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

[krita] [Bug 363124] Light green brush cursor border hard to see

[1DrawingPerDay via KDE Bugzilla]

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

--- Comment #4 from 1DrawingPerDay  ---
I just sent a couple of screenshots of what the cursor looks like in Krita 3.0
Beta.

Also please note the garbled text on the upper left corner of the canvas in the
screenshot with OpenGL enabled. Don't know what's that supposed to be it's
unreadable and it changes all the time (some kind of coordinates?)

No the brush cursor wasn't like that in 2.9.11

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

[krita] [Bug 363124] Light green brush cursor border hard to see

[1DrawingPerDay via KDE Bugzilla]

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

--- Comment #3 from 1DrawingPerDay  ---
Created attachment 99016
  --> https://bugs.kde.org/attachment.cgi?id=99016=edit
Open GL Disabled

This is what the cursor looks like in Krita 3.0 Beta with OpenGL disabled

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

[krita] [Bug 363124] Light green brush cursor border hard to see

[1DrawingPerDay via KDE Bugzilla]

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

--- Comment #2 from 1DrawingPerDay  ---
Created attachment 99015
  --> https://bugs.kde.org/attachment.cgi?id=99015=edit
Open GL Enabled

This is what the cursor looks in Krita 3.0 Beta with OpenGL enabled

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

[krita] [Bug 363127] New: Dragging 3 filter layers from one file to the other causes crash

[1DrawingPerDay via KDE Bugzilla]

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

Bug ID: 363127
   Summary: Dragging 3 filter layers from one file to the other
causes crash
   Product: krita
   Version: 3.0 Beta
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: adjustment layers
  Assignee: krita-bugs-n...@kde.org
  Reporter: onedrawingper...@yahoo.com

First of all I would like to say that currently I am testing Krita for
different projects of mine (painting animation frames, image editing etc) as
I'm thinking about switching to Linux for my main work computer. Currently I'm
in Windows and my system specs are:

Windows 7 SP1
32 bit system
Intel Core Duo 2.26 GH
3GB Ram
ATI Radeon GPU

Here is the link to download a ZIP with a typical .kra file that I'm working
with (please note that it's 34.4 MB)
https://dl.dropboxusercontent.com/u/55690400/DSC05434.zip

In the file there are 3 filter layers that I drag to other images so that I
have the same color adjustments in a group of pack-shots.

The images I work with are high resolution (2048 X 3072 pixels)

First I hide the visibility of said layers and then I drag them (while holding
down Shift) to another file. This usually causes Krita to become unresponsive
for about 15 seconds and then the layers are in the other file. However other
times (and that's often) Krita simply crashes. Note that I always have instant
preview turned off (since it causes an outright crash). I have tested this with
both OpenGL enabled and disabled and it happens anyway.

Also I have enabled the option in the settings for Krita to capture a log file
but when I look in said directory there is nothing there (that's why I'm
sending you the .kra file)

This is a typical workflow for me when I am editing pack-shots and when I work
with files like the one I am sending you sometimes things generally get very
slow and I get frequent crashes. I do not have these problems when a file does
not have Filter layers or when I am just painting.

I know that Krita is positioned as a drawing app but since it has image editing
features perhaps they should work a bit better, especially since the UI is so
much better than Gimp 2.8.

Also I've been looking for Krita's system requirements and I couldn't find any.
My system is old (obviously) and I don't know how Krita performs with Filter
layers in Linux (I hope that it's better than what I experience currently).

Maybe an improvement of Filter layers or dragging layers between files should
be a future feature...

Reproducible: Sometimes

Steps to Reproduce:
1.Hide visibility of 3 Filter layers
2.Select them
3.Drag them to another file

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

[krita] [Bug 363124] New: Light green brush cursor border hard to see

[1DrawingPerDay via KDE Bugzilla]

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

Bug ID: 363124
   Summary: Light green brush cursor border hard to see
   Product: krita
   Version: 3.0 Beta
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Tools
  Assignee: krita-bugs-n...@kde.org
  Reporter: onedrawingper...@yahoo.com

As per Wolthera's request at comment #6 of 
https://bugs.kde.org/show_bug.cgi?id=340085 here is a separate bug report for
the light green cursor. It's tough on the eyes sometimes like on a light grey
background. Also for me it's always the same color.

Like I commented in the other bug report maybe there should be an option to
change the cursor's color in Krita settings. As a workaround currently I create
a new layer above the background I'm working with filled with black and 30%
opacity. This makes the light green cursor more comfortable to work with on
light backgrounds.

My system details are:
Windows 7 SP1
32 bit system
Intel Core Duo 2.26 GH
3GB Ram
ATI Radeon GPU

Reproducible: Always

Steps to Reproduce:
1.Use the brush tool
2.
3.

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

[krita] [Bug 340085] Brush cursor border hard to see over specific color

[1DrawingPerDay via KDE Bugzilla]

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

1DrawingPerDay  changed:

   What|Removed |Added

 CC||onedrawingper...@yahoo.com

--- Comment #5 from 1DrawingPerDay  ---
Maybe there should be an option to choose cursor color in Krita's settings?

The green cursor is tough on the eyes on certain backgrounds (e.g. a light
grey)

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

[krita] [Bug 362793] 3.0 Beta (git 962bfe1) Krita buggy tools performance, crashes on save and OpenGL Error on Restart

[1DrawingPerDay via KDE Bugzilla]

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

--- Comment #2 from 1DrawingPerDay  ---
Hi! 

It seems that disabling OpenGL fixes overall Krita performance for me.

Will file separate bug reports in the future.

Thanks for taking the time to respond.

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

[krita] [Bug 362793] New: 3.0 Beta (git 962bfe1) Krita buggy tools performance, crashes on save and OpenGL Error on Restart

[1DrawingPerDay via KDE Bugzilla]

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

Bug ID: 362793
   Summary: 3.0 Beta (git 962bfe1) Krita buggy tools performance,
crashes on save and OpenGL Error on Restart
   Product: krita
   Version: 3.0 Beta
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: onedrawingper...@yahoo.com

The Version: 3.0 Beta (git 962bfe1) build has been giving me a rough time
performance wise today (filed another bug report about it today). 

I've been using it for the past five hours and during the last two it has
basically become unusable.

Changing the visibility of 3 Adjustment  Layers takes about a minute. Changing
the order of layers is also very slow and sometimes crashes Krita. I have found
a partial workaround to this by hiding the visibility of layers before changing
their order.

The Polygon and Brush tools get stuck often.The brush tool "chooses" to paint
on its own after I end a stroke and the polygon tool jumps around or does not
register a click making it almost unusable. 

Then Krita becomes unresponsive on file save. On program restart it threw me
this error:
Krita could not initialize the OpenGL canvas:
Checker vertex shader
Vertex shader failed to compile with the following errors:
 Krita will disable OpenGL and close now.

I think that I'm done testing this build and going back to the previous one. 

I'm on an old Toshiba Satellite laptop running Windows 7 32bit and using a
Wacom Intuos. I am aware that it's not the fastest system around but I never
had these kind of problems  with the previous builds of Krita 3.0 and I've
spent quite a bit of time testing them. 

Reproducible: Sometimes

Steps to Reproduce:
1
2.
3.

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

[krita] [Bug 362785] New: Undoing layer opacity change not working sometimes

[1DrawingPerDay via KDE Bugzilla]

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

Bug ID: 362785
   Summary: Undoing layer opacity change not working sometimes
   Product: krita
   Version: 3.0 Beta
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: usability
  Assignee: krita-bugs-n...@kde.org
  Reporter: onedrawingper...@yahoo.com

This happens in Version: 3.0 Beta (git 962bfe1)

It's a bit bizarre. 

Sometimes  pressing Ctrl+Z (or clicking the Undo option from the top Edit menu)
after changing the opacity of a layer will not undo it. Instead it will undo
the step before the Opacity Change. Also Opacity Change doesn't show up in the
History list. 

And then after a while Opacity Change re-appears as an option and undoing it
works... 

Reproducible: Sometimes

Steps to Reproduce:
1.Change layer opacity
2.Try to undo it (either Ctrl+Z or from the Edit Menu
3. Sometimes it will not undo the Opacity Change but the step before.

Actual Results:  
Undoing layer opacity does not work sometimes

Expected Results:  
Undoing Opacity change should work.

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

[krita] [Bug 362746] New: PNG File format export missing in 3.0 Beta (git 962bfe1)

[1DrawingPerDay via KDE Bugzilla]

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

Bug ID: 362746
   Summary: PNG File format export missing in 3.0 Beta (git
962bfe1)
   Product: krita
   Version: 3.0 Beta
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: File formats
  Assignee: krita-bugs-n...@kde.org
  Reporter: onedrawingper...@yahoo.com

There is no PNG format in the Save As or Export dropdown options in the 3.0
Beta (git 962bfe1).

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

[krita] [Bug 362740] G'MIC Filter Black & White Interactive Colorize

[1DrawingPerDay via KDE Bugzilla]

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

--- Comment #1 from 1DrawingPerDay  ---
EDIT

Also the filter in Krita does not remember the first image's control points for
subsequent images in a session.

That is also a crucial bug that makes coloring several images in a sequence not
practical in G'Mic for Krita.

It should remember the control points like G'Mic in Gimp.

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

[krita] [Bug 362740] New: G'MIC Filter Black & White Interactive Colorize

[1DrawingPerDay via KDE Bugzilla]

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

Bug ID: 362740
   Summary: G'MIC Filter Black & White Interactive Colorize
   Product: krita
   Version: 3.0 Alpha
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: G'Mic for Krita
  Assignee: krita-bugs-n...@kde.org
  Reporter: onedrawingper...@yahoo.com

Currently I am coloring some animation frames using G'Mic for Krita > Black &
White > Interactive Colorize

For every new frame I have to manually load the same .gpl file palette. G'Mic
for Krita does not remember the palette file that was loaded in the first image
for subsequent images in one session (like it happens in G'Mic for Gimp).

Also the Output Type when specified to Image + Colors (2 layers) or Image +
Colors (multi layer) should always have the original image layer on top (like
in Gimp 2.8) and not at the bottom like it is outputted now in Krita.

These bugs really break my G'Mic coloring workflow in Krita to the point that I
have to use G'Mic in Gimp instead.

Reproducible: Always

Steps to Reproduce:
1.G'Mic for Krita > Black & White > Interactive Colorize
2. Load .gpl file
3.Output Type

Actual Results:  
Have to load .gpl file everytime.

Original image is at the bottom of the layers stack and colored layers on top
when G'Mic is outputted in Krita.

Expected Results:  
Should remember .gpl file after it's loaded in the first image.

Original image should always be on top of colored layers when G'Mic is
outputted in Krita

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

[krita] [Bug 352205] shortcuc ctrl+w cannot be reassigned from default action

[1DrawingPerDay via KDE Bugzilla]

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

1DrawingPerDay  changed:

   What|Removed |Added

 CC||onedrawingper...@yahoo.com

--- Comment #3 from 1DrawingPerDay  ---
Something similar happens with this shortcut in Krita 3.0 Beta (git 4a58260)

I get the message: 
"The key sequence 'Ctrl+W' is ambiguous. Use 'Configure Shortcuts' from the
'Settings' menu to solve the ambiguity. No action will be triggered."

There is no other action triggered by this shortcut and if I change it to
something else like Ctrl+1 it works but if revert it to Ctrl+W Krita throws the
same message again.

Kind of bizarre...

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

[krita] [Bug 362343] Unable to load palette .gpl file in G'Mic for Krita

[1DrawingPerDay via KDE Bugzilla]

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

--- Comment #6 from 1DrawingPerDay  ---
My bad! I stand corrected! It the file dialog button is there when the window
is resized.

Thanks!

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

[krita] [Bug 362343] Unable to load palette .gpl file in G'Mic for Krita

[1DrawingPerDay via KDE Bugzilla]

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

--- Comment #4 from 1DrawingPerDay  ---
No I do not get the file dialog at all.

I also tried typing the location of the .gpl file and still it doesn't load.

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

[krita] [Bug 362343] Unable to load palette .gpl file in G'Mic for Krita

[1DrawingPerDay via KDE Bugzilla]

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

--- Comment #2 from 1DrawingPerDay  ---
Doesn't work for me with the new Beta Release either...

Would have selected the new Beta Release, when I filled the bug report, but it
wasn't available in the dropdown menu.

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

[krita] [Bug 362343] New: Unable to load palette .gpl file in G'Mic for Krita

[1DrawingPerDay via KDE Bugzilla]

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

Bug ID: 362343
   Summary: Unable to load palette .gpl file in G'Mic for Krita
   Product: krita
   Version: 3.0 Alpha
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: G'Mic for Krita
  Assignee: krita-bugs-n...@kde.org
  Reporter: onedrawingper...@yahoo.com

There is no way to select an existing .gpl file from the hard drive in
G'Mic>Black & White Interactive> Colorize filter. The selection to the path of
the .gpl file does not work.

Operating system: Windows 7 32 bit

Reproducible: Always

Steps to Reproduce:
1.Open G'Mic
2.Select Black & White then Colorize Interactive
3. Click in the box "Select 1st additional palette (.gpl file)" 

Actual Results:  
Unable to select .gpl file

Expected Results:  
Should be able to select .gpl file

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