[krita] [Bug 369125] New: Brushstroke offset compared to actual cursor

[Pierre via KDE Bugzilla]

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

Bug ID: 369125
   Summary: Brushstroke offset compared to actual cursor
   Product: krita
   Version: git master
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Brush engine
  Assignee: krita-bugs-n...@kde.org
  Reporter: bloodyw...@tastyespresso.de

Looks like a brush engine problem for me, since it doesn't happen with all
brushes. But Deevads 2B roller brush shows a nice example of this effect (In
deevads current krita brush kit) (pixel brush with texture)

This is not a problem between tablet and krita cursor, the offset here is fine
or not present at all.
But with some brushes it looks like the actual stroke is offset.

Found the problem which causes this: enabled dynamic size in brush editor. The
brush scales down because of low pressure but the scaled down stroke doesn't
get centered like one with max pressure.

Reproducible: Always

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

[krita] [Bug 368764] Crash when opening a .kra file in krita

[Pierre via KDE Bugzilla]

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

--- Comment #1 from Pierre  ---
Created attachment 101074
  --> https://bugs.kde.org/attachment.cgi?id=101074=edit
Backtrace

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

[krita] [Bug 368764] New: Crash when opening a .kra file in krita

[Pierre via KDE Bugzilla]

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

Bug ID: 368764
   Summary: Crash when opening a .kra file in krita
   Product: krita
   Version: git master
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: bloodyw...@tastyespresso.de

I was able to reproduce this multiple times now:

Starting Krita
Open a .kra file made with Krita Version from yesterday
SIGSEGV in __dynamic_cast()

Reproducible: Always

Steps to Reproduce:
See desciption

Actual Results:  
Makes krita crash

Expected Results:  
Should open the .kra file

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

[krita] [Bug 367901] Overview Dock causes freeze

[Pierre via KDE Bugzilla]

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

--- Comment #11 from Pierre  ---
Tested it and drew for multiple ours (Even finished my painting)
Looks like the build from your branch works. I got some minor slowdowns when I
change brushes shortly after doing a stroke, I guess that's the point when this
function triggers.

I'm going to test it within the next days more so that I can confirm for sure
that this fixes it.

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

[krita] [Bug 367901] Overview Dock causes freeze

[Pierre via KDE Bugzilla]

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

--- Comment #7 from Pierre  ---
Took me a while to got it to freeze, like a hour now I had 2 images open, one
reference and my drawing image and of course the overview. I was doing quick
brush strokes with a soft brush.

Going to attach the backtrace.

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

[krita] [Bug 367901] Overview Dock causes freeze

[Pierre via KDE Bugzilla]

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

--- Comment #8 from Pierre  ---
Created attachment 100853
  --> https://bugs.kde.org/attachment.cgi?id=100853=edit
GDB Backtrace right after the freeze

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

[krita] [Bug 367901] Overview Dock causes freeze

[Pierre via KDE Bugzilla]

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

--- Comment #4 from Pierre  ---
Freezes happen in docked mode too.

  totalusedfree  shared  buff/cache   available
Mem:   7.7G3.2G253M1.2G4.3G3.2G
Swap:  5.2G316K5.2G

Memory usage on krita looks good too: VIRT: 2843M RES: 985M SHR: 230M
I was using a liquify/move brush from Deevads 8.1 brush kit, but I doubt that
is the root of the problem.
What I'm going to do now is using my nvidia card, maybe it's a bug with the
intel module, which wouldn't surprise me.

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

[krita] [Bug 367901] Overview Dock causes freeze

[Pierre via KDE Bugzilla]

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

--- Comment #3 from Pierre  ---
Created attachment 100814
  --> https://bugs.kde.org/attachment.cgi?id=100814=edit
My Krita ebuild

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

[krita] [Bug 367901] Overview Dock causes freeze

[Pierre via KDE Bugzilla]

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

--- Comment #2 from Pierre  ---
Rev: 88a03cd3777a820db835f1e5eceb27346dd52d03

GCC:

COLLECT_GCC=/usr/x86_64-pc-linux-gnu/gcc-bin/4.9.3/gcc
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-pc-linux-gnu/4.9.3/lto-wrapper
Ziel: x86_64-pc-linux-gnu
Konfiguriert mit: ../gcc-4.9.3/configure --disable-libssp --enable-multilib
--enable-version-specific-runtime-libs --enable-libmudflap --prefix=/usr
--bindir=/usr/x86_64-pc-linux-gnu/gcc-bin/4.9.3
--includedir=/usr/lib/gcc/x86_64-pc-linux-gnu/4.9.3/include
--datadir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.9.3
--mandir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.9.3/man
--infodir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.9.3/info
--with-gxx-include-dir=/usr/lib/gcc/x86_64-pc-linux-gnu/4.9.3/include/g++-v4.9.3
--enable-libstdcxx-time --enable-__cxa_atexit --enable-clocale=gnu
--host=x86_64-pc-linux-gnu --build=x86_64-pc-linux-gnu --with-system-zlib
--enable-obsolete --disable-werror --enable-secureplt --enable-lto
--without-cloog --with-bugurl=http://bugs.funtoo.org --with-pkgversion='Funtoo
4.9.3-r3'
--with-mpfr-include=/var/tmp/portage/sys-devel/gcc-4.9.3-r3/work/gcc-4.9.3/mpfr/src
--with-mpfr-lib=/var/tmp/portage/sys-devel/gcc-4.9.3-r3/work/objdir/mpfr/src/.libs
--enable-libgomp --build=x86_64-pc-linux-gnu --enable-libgomp
--enable-languages=c,c++,fortran --disable-libgcj --disable-esp
--disable-libsanitizer
Thread-Modell: posix
gcc-Version 4.9.3 (Funtoo 4.9.3-r3)

QT: 5.6.1
Distro: Funtoo
Memory: Never checked it but when I run out of memory the systems cursor would
get slow very bad. 8GB RAM here but I'll check that next time.

6. Not tested yet
7. Nope could draw with it closed for multiple hours

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

[krita] [Bug 367901] New: Overview Dock causes freeze

[Pierre via KDE Bugzilla]

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

Bug ID: 367901
   Summary: Overview Dock causes freeze
   Product: krita
   Version: git master
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: Dockers
  Assignee: krita-bugs-n...@kde.org
  Reporter: bloodyw...@tastyespresso.de

After a around an hour with the overview dock floating krita freezses.

Steps to reproduce:

1. Overview Dock has to be visible and undocked from the toolbar just floating
around
2. Draw a while. I'm using canvas sizes with 16 bit and at least 3000px on the
longest side

Krita will freezes after a while now the brush cursor will remain at some paint
on canvas and the whole GUI will stop updating anything. Only exception your
actual cursor, if you hover edges that are resizeable within the program (like
the floating overview dock) it will change.

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

[krita] [Bug 361293] [WACOM] Airbrush wheel returning negative value and krita creates a negative brushsize

[Pierre via KDE Bugzilla]

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

--- Comment #6 from Pierre  ---
Update on this: The Brush wont get into a negative size now. But now only half
of the wheel is used. So middle state of the wheel is like 0 size.

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

[kmymoney4] [Bug 364777] The importer filtering accounts enhancement forget credit cards/liabilities accounts

[Pierre via KDE Bugzilla]

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

--- Comment #9 from Pierre  ---
Great ! Thank you for the workaround and your fast feedback.

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

[kmymoney4] [Bug 364777] The importer filtering accounts enhancement forget credit cards/liabilities accounts

[Pierre via KDE Bugzilla]

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

--- Comment #7 from Pierre  ---
I cannot select the version I am using as not available in the KMM versions
drop down list.
I'm using the official 4.8.0-2 version (installed from Manjaro community
repository).

I got these CSV and QIF from my credit card website provider. I do not use any
converters.
The OFX I used is for my Current accounts (different from Credit Card
provider).

Anonymized Credit Card CSV and QIF attached.

I indeed noticed in the Import Wizard, in the "Account Selection" step, the
"Account Type" defaults ALWAYS to "Current". Maybe this "defaulting" is the
root cause of the Liability Accounts disposition from the available accounts
list (located on the same step "Account Selection").

The unsolicited account types "filtering" behaviour seems again described as an
enhancement as per https://kmymoney.org/changelogs/ChangeLog-4.8.0.txt / commit
bfa7b5ac37d2203e4a88d9ac73b1ec43ce5211b4

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

[kmymoney4] [Bug 364777] The importer filtering accounts enhancement forget credit cards/liabilities accounts

[Pierre via KDE Bugzilla]

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

--- Comment #6 from Pierre  ---
Created attachment 99705
  --> https://bugs.kde.org/attachment.cgi?id=99705=edit
Anonymized Credit Card QIF

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

[kmymoney4] [Bug 364777] The importer filtering accounts enhancement forget credit cards/liabilities accounts

[Pierre via KDE Bugzilla]

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

--- Comment #5 from Pierre  ---
Created attachment 99704
  --> https://bugs.kde.org/attachment.cgi?id=99704=edit
Anonymized Credit Card CSV

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

[kmymoney4] [Bug 364777] The importer filtering accounts enhancement forget credit cards/liabilities accounts

[Pierre via KDE Bugzilla]

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

--- Comment #3 from Pierre  ---
(In reply to NSLW from comment #1)
> (In reply to Pierre from comment #0)
> > Hello,
> > 
> > Import QIF or CSV does not allow to select Credit Card account (set as
> > Liability account) in order to import to it. This seems to be due to below
> > enhancement.
> > 
> > Liability accounts should still be usable for imports, otherwise how we
> > import Credit Card transactions on a Liability account ?
> > 
> > 
> > (source: https://kmymoney.org/changelogs/ChangeLog-4.8.0.txt)
> > commit bfa7b5ac37d2203e4a88d9ac73b1ec43ce5211b4
> > Author: Åukasz WojniÅ‚owicz 
> > Date:   Sat May 28 19:59:22 2016 +0200
> > 
> > Present only right accounts during import of statements
> > 
> > During import of investment statement user is asked to select account
> > into which he wants to import. He should choose investment account, but
> > he is also presented with all other sorts of accounts. This patch makes
> > sure that user is presented only with the right account types.
> > 
> > FEATURE: 363069
> > REVIEW: 127915
> > 
> > Signed-off-by: Åukasz WojniÅ‚owicz 
> > 
> > Reproducible: Always
> > 
> > Steps to Reproduce:
> > 1. Select /
> > 2. Then  or 
> > 3. Select file to import
> > 4. Next screen shows only Current accounts (no liability accounts)
> > 
> > Actual Results:  
> > Only current accounts are available.
> > 
> > Expected Results:  
> > Liability accounts should be available too.
> 
> Hello,
> there is no problem with CSV imports of credit cards in KMM > 4.8. What do
> you try to import actually: CSV or QIF?

I added a screenshot showing that "Liability Account" is missing in the list of
available accounts.
The list is only showing "Current Accounts", the Credit Card account (in
"Liability Account" category) is not showing in the Import Wizard. (Import is
working fine with Current Accounts, tested with QIF and CSV and OFX)

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

[kmymoney4] [Bug 364777] The importer filtering accounts enhancement forget credit cards/liabilities accounts

[Pierre via KDE Bugzilla]

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

--- Comment #2 from Pierre  ---
Created attachment 99702
  --> https://bugs.kde.org/attachment.cgi?id=99702=edit
Missing Liability Account

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

[kmymoney4] [Bug 364777] The importer filtering accounts enhancement forget credit cards/liabilities accounts

[Pierre via KDE Bugzilla]

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

Pierre  changed:

   What|Removed |Added

   Keywords||regression, reproducible

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

[kmymoney4] [Bug 364777] New: The importer filtering accounts enhancement forget credit cards/liabilities accounts

[Pierre via KDE Bugzilla]

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

Bug ID: 364777
   Summary: The importer filtering accounts enhancement forget
credit cards/liabilities accounts
   Product: kmymoney4
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: kmymoney-de...@kde.org
  Reporter: pierre.gr...@gmail.com

Hello,

Import QIF or CSV does not allow to select Credit Card account (set as
Liability account) in order to import to it. This seems to be due to below
enhancement.

Liability accounts should still be usable for imports, otherwise how we import
Credit Card transactions on a Liability account ?


(source: https://kmymoney.org/changelogs/ChangeLog-4.8.0.txt)
commit bfa7b5ac37d2203e4a88d9ac73b1ec43ce5211b4
Author: Åukasz WojniÅ‚owicz 
Date:   Sat May 28 19:59:22 2016 +0200

Present only right accounts during import of statements

During import of investment statement user is asked to select account
into which he wants to import. He should choose investment account, but
he is also presented with all other sorts of accounts. This patch makes
sure that user is presented only with the right account types.

FEATURE: 363069
REVIEW: 127915

Signed-off-by: Åukasz WojniÅ‚owicz 

Reproducible: Always

Steps to Reproduce:
1. Select /
2. Then  or 
3. Select file to import
4. Next screen shows only Current accounts (no liability accounts)

Actual Results:  
Only current accounts are available.

Expected Results:  
Liability accounts should be available too.

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

[krita] [Bug 361293] [WACOM] Airbrush wheel returning negative value and krita creates a negative brushsize

[Pierre via KDE Bugzilla]

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

--- Comment #4 from Pierre  ---
The scroll wheel in Qt4 and 2.9.x had just the values 1, 0 and -1. Krita
handled the axis for that correct but qt4 messed up reporting the correct
values to krita.

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

[krita] [Bug 361293] New: Wacom Airbrush wheel returning negative value and krita creates a negative brushsize

[Pierre via KDE Bugzilla]

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

Bug ID: 361293
   Summary: Wacom Airbrush wheel returning negative value and
krita creates a negative brushsize
   Product: krita
   Version: git master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: tablet support
  Assignee: krita-bugs-n...@kde.org
  Reporter: bloodyw...@tastyespresso.de

The Wacom Airbush Pen returns a integer (or float?) range with can be negative
or positive

lowest value is -255 and highest +255.
The range 0 - 255 works just fine in krita but when I scroll further with the
airbrush wheel it returns a negative number and krita increases the brush size
according to the negative value.
But you can't draw with that negative brush size.

Reproducible: Always

Steps to Reproduce:
1. Map the airbush wheel to the brush size in the brush editor
2.
3.

Actual Results:  
Brush size is displayed the same as it's positive counterpart but. The result
is that only half of the brush wheel is usable.

Expected Results:  
the lowest negative size in tangential pressure should be the smallest brush
size in that case.

I'm not quite sure if the airbrush returns -1.0 and 1.0 or -255 and 255
Other devices could work with this since they return a range with 0 - 255

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

[krita] [Bug 360879] Crash when create new file with background color as canvas

[Pierre via KDE Bugzilla]

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

--- Comment #3 from Pierre  ---
I'm trying to reproduce it too now, I was testing some icc profiles before and
changed them. I was thinking an obscure profile was the reason first. But it
did crash with the default one as well.

You can close the bug report, if it happens again I try to get a strace log at
least.

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

[krita] [Bug 360879] Crash when create new file with background color as canvas

[Pierre via KDE Bugzilla]

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

--- Comment #1 from Pierre  ---
All the sudden it works now. I tested it multiple times before and it kept
crashing for me.

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

[krita] [Bug 360879] New: Crash when create new file with background color as canvas

[Pierre via KDE Bugzilla]

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

Bug ID: 360879
   Summary: Crash when create new file with background color as
canvas
   Product: krita
   Version: git master
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: bloodyw...@tastyespresso.de

Usually you create a new image with 1 layer and a backgroundcolor as filled
layer.
But when I change it to as canvas colour my krita crashes

I checked this with the git master of krita 3.

Reproducible: Always

Steps to Reproduce:
1. Open the new file dialog
2. go to the content tab
3. change it to as canvas colour
4. click create

Actual Results:  
A crash

Expected Results:  
Should create a new image

Work around: create a new image without changing it to canvas and change it
later from the menu.

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