[krita] [Bug 459252] Filter layers crashes on large files

2022-09-18 Thread Razvan Radulescu
https://bugs.kde.org/show_bug.cgi?id=459252

--- Comment #6 from Razvan Radulescu  ---
(In reply to Halla Rempt from comment #5)
> Could you type "thread apply 1 bt" in the gdb window to get more of the
> backtrace? I still cannot reproduce this, so it might be worth trying this
> with a clean config/share folder, too. (Make backups, though, of
> .config/krita* and .local/share/krita*.)

So this run is with fresh `~/.config/krita*` & `~/.local/share/krita` files and
folders.

❯ gdb ./krita-5.1.1-4126e6dde4-x86_64.appimage
GNU gdb (Ubuntu 12.0.90-0ubuntu1) 12.0.90
Copyright (C) 2022 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from ./krita-5.1.1-4126e6dde4-x86_64.appimage...
(No debugging symbols found in ./krita-5.1.1-4126e6dde4-x86_64.appimage)
(gdb) r
Starting program:
/home/razcore-rad/Downloads/krita-5.1.1-4126e6dde4-x86_64.appimage 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Detaching after fork from child process 141515]
process 141472 is executing new program: /tmp/.mount_krita-kF1Bf2/AppRun
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
process 141472 is executing new program: /tmp/.mount_krita-kF1Bf2/usr/bin/krita
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffe31ff640 (LWP 141522)]
[New Thread 0x7fffe29fe640 (LWP 141523)]
[Thread 0x7fffe31ff640 (LWP 141522) exited]
[New Thread 0x7fffe31ff640 (LWP 141525)]
[Thread 0x7fffe31ff640 (LWP 141525) exited]
[New Thread 0x7fffe31ff640 (LWP 141526)]
[Thread 0x7fffe31ff640 (LWP 141526) exited]
[New Thread 0x7fffe31ff640 (LWP 141527)]
krita.lib.resources: Created table "version_information"
krita.lib.resources: Created table "storage_types"
krita.lib.resources: Created table "resource_types"
krita.lib.resources: Created table "storages"
krita.lib.resources: Created table "tags"
krita.lib.resources: Created table "resources"
krita.lib.resources: Created table "versioned_resources"
krita.lib.resources: Created table "resource_tags"
krita.lib.resources: Created table "metadata"
krita.lib.resources: Created table "tags_storages"
krita.lib.resources: Created table "tag_translations"
krita.lib.resources: Created table "storages"
krita.lib.resources: Created table "versioned_resources"
krita.lib.resources: Created table "tags"
krita.lib.resources: Created table "resources"
krita.lib.resources: Created table "tag_translations"
krita.lib.resources: Created table "resource_tags"
krita.lib.resources: Created table "resources_signature"
krita.lib.resources: Filled lookup table storage_types
krita.lib.resources: Filled lookup table resource_types
krita.lib.resources: Filled version table
[New Thread 0x7fffb31ff640 (LWP 141531)]
QObject::startTimer: Timers cannot have negative intervals
[New Thread 0x7fffb29fe640 (LWP 141532)]
[New Thread 0x7fffb21fd640 (LWP 141533)]
[Thread 0x7fffb29fe640 (LWP 141532) exited]
Could not find platform independent libraries 
Could not find platform dependent libraries 
Consider setting $PYTHONHOME to [:]
/tmp/.mount_krita-kF1Bf2/usr/lib/krita-python-libs/krita added to PYTHONPATH
[New Thread 0x7fffb29fe640 (LWP 141536)]
[New Thread 0x7fff9a3ff640 (LWP 141537)]
qt.qpa.xkeyboard: QXcbKeyboard::handleKeyEvent: key pressed, but it is already
present in the registry code 64 qtcode 16777251 registered qtcode 16777251
[New Thread 0x7fff9948d640 (LWP 141552)]
[New Thread 0x7fff98c8c640 (LWP 141553)]
[New Thread 0x7fff8bfff640 (LWP 141554)]
[New Thread 0x7fff8b7fe640 (LWP 141555)]
[New Thread 0x7fff8affd640 (LWP 141556)]
[New Thread 0x7fff8a7fc640 (LWP 141557)]
[New Thread 0x7fff89ffb640 (LWP 141558)]
[New Thread 0x7fff897fa640 (LWP 141559)]
[New Thread 0x7fff88ff9640 (LWP 141560)]
[New Thread 0x7fff63fff640 (LWP 141561)]
[New Thread 0x7fff6bfff640 (LWP 141562)]
[New Thread 0x7fff6b7fe640 (LWP 141563)]
[New Thread 0x7fff4bffd640 (LWP 141577)]

Thread 1

[krita] [Bug 459252] Filter layers crashes on large files

2022-09-18 Thread Razvan Radulescu
https://bugs.kde.org/show_bug.cgi?id=459252

--- Comment #4 from Razvan Radulescu  ---
I don't know if this helps or not, but this is the run with GDB, I didn't know
it outputs more stuff even with the appimage...

❯ gdb ./krita-5.1.1-4126e6dde4-x86_64.appimage 
GNU gdb (Ubuntu 12.0.90-0ubuntu1) 12.0.90
Copyright (C) 2022 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from ./krita-5.1.1-4126e6dde4-x86_64.appimage...
(No debugging symbols found in ./krita-5.1.1-4126e6dde4-x86_64.appimage)
(gdb) r
Starting program:
/home/razcore-rad/Downloads/krita-5.1.1-4126e6dde4-x86_64.appimage 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Detaching after fork from child process 139098]
process 139056 is executing new program: /tmp/.mount_krita-eEYXdU/AppRun
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
process 139056 is executing new program: /tmp/.mount_krita-eEYXdU/usr/bin/krita
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffe31ff640 (LWP 139103)]
[New Thread 0x7fffe29fe640 (LWP 139104)]
[Thread 0x7fffe31ff640 (LWP 139103) exited]
[New Thread 0x7fffe31ff640 (LWP 139106)]
[Thread 0x7fffe31ff640 (LWP 139106) exited]
[New Thread 0x7fffe31ff640 (LWP 139107)]
[Thread 0x7fffe31ff640 (LWP 139107) exited]
[New Thread 0x7fffe31ff640 (LWP 139108)]
[New Thread 0x7fffb31ff640 (LWP 139109)]
QObject::startTimer: Timers cannot have negative intervals
[Detaching after fork from child process 139110]
[New Thread 0x7fffb29fe640 (LWP 139118)]
[New Thread 0x7fffb21fd640 (LWP 139119)]
[Thread 0x7fffb29fe640 (LWP 139118) exited]
Could not find platform independent libraries 
Could not find platform dependent libraries 
Consider setting $PYTHONHOME to [:]
/tmp/.mount_krita-eEYXdU/usr/lib/krita-python-libs/krita added to PYTHONPATH
[New Thread 0x7fffb29fe640 (LWP 139126)]
[New Thread 0x7fff9a3ff640 (LWP 139127)]
qt.svg: Cannot open file '/:16_dark_tab-close.svg', because: No such file or
directory
qt.svg: Cannot open file '/:16_dark_tab-close.svg', because: No such file or
directory
[New Thread 0x7fff99bfe640 (LWP 139128)]
[New Thread 0x7fff993fd640 (LWP 139129)]
[New Thread 0x7fff8bfff640 (LWP 139130)]
[New Thread 0x7fff8a999640 (LWP 139131)]
[New Thread 0x7fff8b7fe640 (LWP 139139)]
[New Thread 0x7fff8a198640 (LWP 139140)]
[New Thread 0x7fff89997640 (LWP 139141)]
[New Thread 0x7fff89196640 (LWP 139142)]
[New Thread 0x7fff88995640 (LWP 139143)]
[New Thread 0x7fff67fff640 (LWP 139144)]
[New Thread 0x7fff677fe640 (LWP 139145)]
[New Thread 0x7fff66ffd640 (LWP 139146)]
[New Thread 0x7fff667fc640 (LWP 139147)]
[New Thread 0x7fff65ffb640 (LWP 139148)]
[New Thread 0x7fff657fa640 (LWP 139149)]
[New Thread 0x7fff64ff9640 (LWP 139150)]
[New Thread 0x7fff47bff640 (LWP 139168)]

Thread 1 "krita" received signal SIGSEGV, Segmentation fault.
0x767e5220 in KisNode::graphListener() const () from
/tmp/.mount_krita-eEYXdU/usr/bin/../lib/libkritaimage.so.18

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

[krita] [Bug 459252] Filter layers crashes on large files

2022-09-18 Thread Razvan Radulescu
https://bugs.kde.org/show_bug.cgi?id=459252

--- Comment #3 from Razvan Radulescu  ---
(In reply to Halla Rempt from comment #1)
> I cannot reproduce a crash. Is this 100% reproducible for you? 
> 
> Do you see any interesting messages about asserts on the terminal if you
> start Krita from there? Do you get a backtrace if you run Krita in GDB?

I use the appimage so I can't get the backlog, it's a bit too much work to
compile it locally. I attached a video with the exact steps and maybe there's
other differences in the new file created by me. I'm not sure. Anyway, yes,
following these steps it crashes 100% of the time on my PC with SIGSEGV.

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

[krita] [Bug 459252] Filter layers crashes on large files

2022-09-18 Thread Razvan Radulescu
https://bugs.kde.org/show_bug.cgi?id=459252

--- Comment #2 from Razvan Radulescu  ---
Created attachment 152181
  --> https://bugs.kde.org/attachment.cgi?id=152181=edit
Video Steps to Crash

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

[krita] [Bug 459252] New: Filter layers crashes on large files

2022-09-17 Thread Razvan Radulescu
https://bugs.kde.org/show_bug.cgi?id=459252

Bug ID: 459252
   Summary: Filter layers crashes on large files
Classification: Unclassified
   Product: krita
   Version: git master (please specify the git hash!)
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Filter Layers
  Assignee: krita-bugs-n...@kde.org
  Reporter: razcore@gmail.com
  Target Milestone: ---

Created attachment 152139
  --> https://bugs.kde.org/attachment.cgi?id=152139=edit
Krita Sysinfo

SUMMARY
Crash on save with filer layers for large files (>4K)
git hash: 4126e6d

STEPS TO REPRODUCE
1. Create a 4K image (7680x4320)
2. Add Filter Layer, e.g. Color Adjustment
3. Save the file

OBSERVED RESULT

Instant crash.

EXPECTED RESULT
File gets saved without crash.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma:  Ubuntu 22.04.1 LTS
Qt Version: 5.12.12

ADDITIONAL INFORMATION
See attached file for full system info.

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

[krita] [Bug 442353] Brushes seemingly randomly fail to properly load their pattern

2021-09-29 Thread Razvan Radulescu
https://bugs.kde.org/show_bug.cgi?id=442353

Razvan Radulescu  changed:

   What|Removed |Added

 CC||razcore@gmail.com

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

[krita] [Bug 440138] New: Crash when picking paintoppreset

2021-07-21 Thread Razvan Radulescu
https://bugs.kde.org/show_bug.cgi?id=440138

Bug ID: 440138
   Summary: Crash when picking paintoppreset
   Product: krita
   Version: nightly build (please specify the git hash!)
  Platform: Appimage
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Brush engines
  Assignee: krita-bugs-n...@kde.org
  Reporter: razcore@gmail.com
  Target Milestone: ---

SUMMARY
Grab a problematic preset from the github repo, for example:
https://github.com/razcore-rad/krita-resources/blob/main/krita/paintoppresets/h)_Charcoal_RazcoreRad.kpp
This is also part of the bundle:
https://github.com/razcore-rad/krita-resources/releases/tag/0.4-alpha

Krita doesn't crash in the previous nightly build: 6f58e0c.


STEPS TO REPRODUCE
1. Open Krita
2. Pick a problematic paintoppreset
3. Crash

OBSERVED RESULT
Crash on picking new paintoppreset.

❯ krita.appimage   
   
  08:32:49
QObject::startTimer: Timers cannot have negative intervals
Could not find platform independent libraries 
Could not find platform dependent libraries 
Consider setting $PYTHONHOME to [:]
/tmp/.mount_krita.5tSMsJ/usr/lib/krita-python-libs/krita added to PYTHONPATH
qt.svg: Cannot open file '/:16_dark_tab-close.svg', because: No such file or
directory
qt.svg: Cannot open file '/:16_dark_tab-close.svg', because: No such file or
directory
qt.svg: Cannot open file '/:16_dark_tab-close.svg', because: No such file or
directory
qt.svg: Cannot open file '/:16_dark_tab-close.svg', because: No such file or
directory
SAFE ASSERT (krita): "brush" in file
/home/appimage/workspace/Krita_Nightly_Appimage_Build/krita/libs/brush/kis_predefined_brush_factory.cpp,
line 37
fish: Job 1, 'krita.appimage' terminated by signal SIGSEGV (Address boundary
error)



EXPECTED RESULT
Krita should pick new paintoppreset.


SOFTWARE/OS VERSIONS
Krita

 Version: 5.0.0-prealpha (git 63be085)
 Languages: en_US, en
 Hidpi: true

Qt

  Version (compiled): 5.12.11
  Version (loaded): 5.12.11

OS Information

  Build ABI: x86_64-little_endian-lp64
  Build CPU: x86_64
  CPU: x86_64
  Kernel Type: linux
  Kernel Version: 5.11.0-25-generic
  Pretty Productname: Ubuntu 21.04
  Product Type: ubuntu
  Product Version: 21.04
  Desktop: ubuntu:GNOME

OpenGL Info

  Vendor:  "NVIDIA Corporation" 
  Renderer:  "GeForce GT 750M/PCIe/SSE2" 
  Version:  "4.6.0 NVIDIA 390.144" 
  Shading language:  "4.60 NVIDIA" 
  Requested format:  QSurfaceFormat(version 3.0, options
QFlags(DeprecatedFunctions), depthBufferSize 24,
redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8,
stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer,
swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile 
QSurfaceFormat::CompatibilityProfile) 
  Current format:QSurfaceFormat(version 4.6, options
QFlags(DeprecatedFunctions), depthBufferSize 24,
redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8,
stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer,
swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile 
QSurfaceFormat::CompatibilityProfile) 
 Version: 4.6
 Supports deprecated functions true 
 is OpenGL ES: false 

QPA OpenGL Detection Info 
  supportsDesktopGL: true 
  supportsOpenGLES: true 
  isQtPreferOpenGLES: false 

Hardware Information

  GPU Acceleration: auto
  Memory: 15884 Mb
  Number of Cores: 8
  Swap Location: /tmp

Current Settings

  Current Swap Location: /tmp
  Current Swap Location writable: true
  Undo Enabled: true
  Undo Stack Limit: 100
  Use OpenGL: true
  Use OpenGL Texture Buffer: true
  Use AMD Vectorization Workaround: false
  Canvas State: OPENGL_SUCCESS
  Autosave Interval: 120
  Use Backup Files: true
  Number of Backups Kept: 1
  Backup File Suffix: ~
  Backup Location: Same Folder as the File
  Backup Location writable: false
  Use Win8 Pointer Input: false
  Use RightMiddleTabletButton Workaround: false
  Levels of Detail Enabled: false
  Use Zip64: false


Display Information
Number of screens: 3
Screen: 0
Name: eDP-1-1
Depth: 24
Scale: 1
Resolution in pixels: 1920x1080
Manufacturer: AU Optronics
Model: 
Refresh Rate: 60
Screen: 1
Name: DP-0
Depth: 24
Scale: 1
Resolution in pixels: 1920x1080
Manufacturer: UGD
Model: ID160F-
Refresh Rate: 60
Screen: 2
Name: HDMI-1-1
Depth: 24
Scale: 1
Resolution in pixels: 1920x1080
Manufacturer: Samsung Electric Company
Model: 

[krita] [Bug 405717] Numpad numbers won't work even when numlock is on

2019-03-22 Thread Razvan Radulescu
https://bugs.kde.org/show_bug.cgi?id=405717

--- Comment #2 from Razvan Radulescu  ---
(In reply to Boudewijn Rempt from comment #1)
> You can find the git hash in the about box, it's part of the version number.
> As for the issue: are you typing in things like the opacity slider or the
> size slider in toolbar, or in entry boxes in dockers or dialogs?

It's the same everywhere - dockers/dialogs/toolbar sliders etc. but not just
sliders, any input box really, like for example layer names, specific color
entry boxes. Krita just ignores keypad number keys/numlock altogether.

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

[krita] [Bug 405717] New: Numpad numbers won't work even when numlock is on

2019-03-21 Thread Razvan Radulescu
https://bugs.kde.org/show_bug.cgi?id=405717

Bug ID: 405717
   Summary: Numpad numbers won't work even when numlock is on
   Product: krita
   Version: nightly build (please specify the git hash!)
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: krita-bugs-n...@kde.org
  Reporter: razcore@gmail.com
  Target Milestone: ---

SUMMARY
Numpad number keys are ignored no matter the numlock state.

STEPS TO REPRODUCE
1. Try to input any number sequence in options like size/opacity/etc.
2. Observe that no numbers are typed, instead the numpad keys behave as if
numlock isn't active


KRITA VERSION:
krita-4.2.0-pre-alpha-9429230-x86_64.appimage - don't know how to get the git
hash from the nightly build site
Build #421 (Mar 20, 2019 4:09:00 PM)


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Ubuntu 18.10
Qt
  Version (compiled): 5.10.0
  Version (loaded): 5.10.0

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

[krita] [Bug 402382] Node::projectionPixelData returns 0s for grouplayer and wrong data for filelayer

2019-01-23 Thread Razvan Radulescu
https://bugs.kde.org/show_bug.cgi?id=402382

Razvan Radulescu  changed:

   What|Removed |Added

 Resolution|--- |NOT A BUG
 Status|REPORTED|RESOLVED

--- Comment #8 from Razvan Radulescu  ---
OK so I think we went through a lot in the IRC chat. I'll have to book mark
this for later, the script is really helpful.

At the end of the day it's because of Node.setColorProfile() and likewise I
tried Document.setColorProfile() with no luck.

As for the file layer I've tried another .kra file so that was the issue there.
I'm going to close this as pretty much all has been answered, as much as it
could have been :)

Thanks for all the help Wolthera

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

[krita] [Bug 402382] New: Node::projectionPixelData returns 0s for grouplayer and wrong data for filelayer

2018-12-20 Thread Razvan Radulescu
https://bugs.kde.org/show_bug.cgi?id=402382

Bug ID: 402382
   Summary: Node::projectionPixelData returns 0s for grouplayer
and wrong data for filelayer
   Product: krita
   Version: nightly build (please specify the git hash!)
  Platform: Appimage
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Scripting
  Assignee: krita-bugs-n...@kde.org
  Reporter: razcore@gmail.com
  Target Milestone: ---

Created attachment 117026
  --> https://bugs.kde.org/attachment.cgi?id=117026=edit
test kra and export files

SUMMARY
Node::projectionPixelData should return data even in case of grouplayer as per
libkis documentation: <>

It turns out Node::projectionPixelData for grouplayer returns all 0s and for
filelayer it looks to be screwed up.

STEPS TO REPRODUCE
This is very tricky because it's based on a script. One option would be to
clone/download https://github.com/razcore-art/Krita-designer-tools and place in
pykrita. Create a `Dependencies` folder inside the plugin folder
(gdquest_art_tools) and install a compatible Pillow version with your Krita
Python version with `pip install --target=Dependencies link_to_pillow`.
`link_to_pillow` can be found from https://pypi.org/project/Pillow/#files. Then
open up Krita with uploaded `test.kra` file. Be sure to have
`test_convertion.kra` in there as well since `test.kra` uses
`test_convertion.kra` as a file layer. Turn on the plugin (called GDquest Art
Tools), open the docker with the same name and press "All Layers". You can also
press "Selected Layers" while selecting some of them. Try the group/file
layers. See further info at this PR:
https://github.com/GDquest/Krita-designer-tools/pull/12#issue-240184606.

Another option is to just explore the attached files via Scripter.

I've included the export operation in the attachment as well.

OBSERVED RESULT
Open the files and see that group layer exports are completely transparent, no
data (all 0s) while file layer exports are all screwed up, it's as if the
column/row order in the bytearray is inverted.


EXPECTED RESULT
All layers should be exported as they appear in Krita.


SOFTWARE/OS VERSIONS
OS Information
  Build ABI: x86_64-little_endian-lp64
  Build CPU: x86_64
  CPU: x86_64
  Kernel Type: linux
  Kernel Version: 4.18.0-12-generic
  Pretty Productname: Ubuntu 18.10
  Product Type: ubuntu
  Product Version: 18.10

Qt
  Version (compiled): 5.10.0
  Version (loaded): 5.10.0

ADDITIONAL INFORMATION
Krita 4.2.0-pre-alpha (git c1b8345)

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