[krita] [Bug 443799] Warp transform mask makes layer content invisible for a short time after layer reorder
https://bugs.kde.org/show_bug.cgi?id=443799 Yu-Hsuan Lai changed: What|Removed |Added CC||rainco...@gmail.com --- Comment #3 from Yu-Hsuan Lai --- Still happens to me. On windows 10. Both 5.1.2 and 5.2.0-beta2. The transform mask is *extremely* unstable to a point it's unusable when Warp, Cage or Liquify is involved. The whole layer can just disappear after toggling the transform mask's visibility. It can also partially disappear, leaving the file in an weird state. I even renewed my PS license today for this... -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 460261] New: Font kerning just looks very off
https://bugs.kde.org/show_bug.cgi?id=460261 Bug ID: 460261 Summary: Font kerning just looks very off Classification: Applications Product: krita Version: 5.1.1 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Tool/Text Assignee: krita-bugs-n...@kde.org Reporter: rainco...@gmail.com Target Milestone: --- Created attachment 152715 --> https://bugs.kde.org/attachment.cgi?id=152715&action=edit font test SUMMARY Fonts rendered by Krita look very off, especially when font size is small. STEPS TO REPRODUCE 1. Choose text tool 2. Draw a text box and type "Lorem ipsum" 3. Set font size to 8pt, font to "Arial" OBSERVED RESULT Bad kerning EXPECTED RESULT Proper kerning SOFTWARE/OS VERSIONS Krita Version: 5.1.1 Installation type: installer / portable package Hidpi: true Qt Version (compiled): 5.12.12 Version (loaded): 5.12.12 OS Information Build ABI: x86_64-little_endian-llp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: winnt Kernel Version: 10.0.19044 Pretty Productname: Windows 10 (10.0) Product Type: windows Product Version: 10 Locale Languages: en_US C locale: C QLocale current: en QLocale system: en QTextCodec for locale: UTF-8 Process ACP: 65001 (UTF-8) System locale default ACP: 1252 (ANSI - Latin I) ADDITIONAL INFORMATION Please check the attachment. Photoshop and chrome also give similar results to Figma's. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 459683] New: "Toggle Layer Visiblity" doesn't work for multiple layers
https://bugs.kde.org/show_bug.cgi?id=459683 Bug ID: 459683 Summary: "Toggle Layer Visiblity" doesn't work for multiple layers Classification: Applications Product: krita Version: 5.1.1 Platform: Microsoft Windows OS: All Status: REPORTED Severity: normal Priority: NOR Component: Layer Stack Assignee: krita-bugs-n...@kde.org Reporter: rainco...@gmail.com Target Milestone: --- SUMMARY Not entirely sure if it's a bug, but its behavior is rather unexpected for me. STEPS TO REPRODUCE 1. Create a layer "A" 2. Create a layer "B" 3. Hide layer "B" (now "A" is visible and "B" is hidden) 4. Select both "A" and "B" 5. Excute the action "Toggle Layer Visibility" OBSERVED RESULT "A" and "B" are both visible EXPECTED RESULT "A" is hidden and "B" is visible NOTE I can see why it works like that, but I believe it shouldn't. It should've toggled all select layers' visiblity. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 459415] Krita exports weirdly huge pngs when colorspace conversion is involved
https://bugs.kde.org/show_bug.cgi?id=459415 --- Comment #3 from Yu-Hsuan Lai --- (In reply to Halla Rempt from comment #2) > Yes, well, Photos doesn't support 16 bit/channel PNG, which krita does > support. Converting to sRGB does not drop the channel depth to 8 bit/channel. Is there an option to drop it to 8bit at export? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 459415] Krita exports weirdly huge pngs when colorspace conversion is involed
https://bugs.kde.org/show_bug.cgi?id=459415 --- Comment #1 from Yu-Hsuan Lai --- test.kra is too large to be uploaded as an attachment. please download it here: https://drive.google.com/file/d/1g3wUlCMUCokH0O2qvt-y_YnB9WOmvyvJ/view?usp=sharing -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 459415] New: Krita exports weirdly huge pngs when colorspace conversion is involed
https://bugs.kde.org/show_bug.cgi?id=459415 Bug ID: 459415 Summary: Krita exports weirdly huge pngs when colorspace conversion is involed Classification: Unclassified Product: krita Version: 5.1.1 Platform: Microsoft Windows OS: All Status: REPORTED Severity: normal Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: rainco...@gmail.com Target Milestone: --- SUMMARY The pngs exported from Krita are really huge when the .kra is in a colorspace and .png is converted to sRGB during export. STEPS TO REPRODUCE 1. Open test.kra in Krita 2. File -> Export -> Save as Type: png 3. Export with default options OBSERVED RESULT The exported png is 2.39MB EXPECTED RESULT The exported png is much smaller than that. I opened the exported file in Windows' built-in Photos, save a copy of it, and it's only 767KB. If I converted the .kra in Krita and then exported it, it's about 400KB only. SOFTWARE/OS VERSIONS Krita Version: 5.1.1 Qt Version (compiled): 5.12.12 ADDITIONAL INFORMATION test.kra is attached -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 458115] Trying to Copy Vector Layers from one Project into another - will cause a Crash (100% Repro)
https://bugs.kde.org/show_bug.cgi?id=458115 --- Comment #20 from Yu-Hsuan Lai --- I confirm this problem doesn't happen in 5.1.1. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 458115] Trying to Copy Vector Layers from one Project into another - will cause a Crash (100% Repro)
https://bugs.kde.org/show_bug.cgi?id=458115 Yu-Hsuan Lai changed: What|Removed |Added CC||rainco...@gmail.com --- Comment #14 from Yu-Hsuan Lai --- I can confirm this bug happens to me too. 5.1.0 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 456787] Inconsistent behaviour while changing brush size with a shortcut
https://bugs.kde.org/show_bug.cgi?id=456787 Yu-Hsuan Lai changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- Assignee|krita-bugs-n...@kde.org |rainco...@gmail.com --- Comment #2 from Yu-Hsuan Lai --- Created attachment 151337 --> https://bugs.kde.org/attachment.cgi?id=151337&action=edit brush tip (In reply to Halla Rempt from comment #1) > I cannot reproduce this with basic-4 flow opacity. Which preset are you > using? Basic-3 Flow. But here is the catch: this bug only happens when I set the brush tip to "chisel_eroded" (I'm not sure if it's built-in one) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 456787] New: Inconsistent behaviour while changing brush size with a shortcut
https://bugs.kde.org/show_bug.cgi?id=456787 Bug ID: 456787 Summary: Inconsistent behaviour while changing brush size with a shortcut Product: krita Version: 5.0.6 Platform: Microsoft Windows OS: All Status: REPORTED Severity: normal Priority: NOR Component: Brush engines Assignee: krita-bugs-n...@kde.org Reporter: rainco...@gmail.com Target Milestone: --- SUMMARY It's a very small but annoying bug. You need to press ] twice to go from 1px to 3px, but pressing [ once will bring you back to 1px. STEPS TO REPRODUCE 1. Set the brush size to 1px 2. Press ] to increase brush size, now it's 2px 3. Press ] again, now it's 3px 4. Press [ to decrease brush size OBSERVED RESULT Brush size is 1px EXPECTED RESULT Brush size is 2px SOFTWARE/OS VERSIONS All ADDITIONAL INFORMATION It's a very small but annoying bug, especially while doing finer lineart. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 455106] New: Value (HSV) blend mode changes saturation unexpectedly
https://bugs.kde.org/show_bug.cgi?id=455106 Bug ID: 455106 Summary: Value (HSV) blend mode changes saturation unexpectedly Product: krita Version: 5.0.6 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Color models Assignee: krita-bugs-n...@kde.org Reporter: rainco...@gmail.com Target Milestone: --- SUMMARY "Value" blend mode (under HSV section) should only change value. STEPS TO REPRODUCE 1. Create a layer and fill it with hsv(0, 100, 50) (a dark red color) 2. Create another layer above it, fill it with hsv(0, 0, 100) (pure white) 3. Change the top layer's blend mode to "Value" OBSERVED RESULT The blended color is hsv(0, 49.8, 100) (pink) EXPECTED RESULT The blended color is hsv(0, 100, 100) (pure red) SOFTWARE/OS VERSIONS Krita 5.0.6 probably all platforms ADDITIONAL INFORMATION I know other software has similar behavior. However, I still consider it a bug. Krita's "Value" blend mode is explicitly under "HSV" section, which implies it should change the value and value only, according to HSV color model. It shouldn't change saturation somehow. If I'd like to change lightness, I'd use "Lightness" blend mode (under HSL section). "Value" shouldn't try to be smart like this. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 441350] Brushes works wrong, after selecting another pattern and reselecting the original one, they works like the should
https://bugs.kde.org/show_bug.cgi?id=441350 Yu-Hsuan Lai changed: What|Removed |Added CC||rainco...@gmail.com --- Comment #12 from Yu-Hsuan Lai --- Buggy for me too. 5.0.0-beta2 (git a642eb0). Video demo for the bug: https://krita-artists.org/t/color-smudge-brushs-ratio-setting-bug-with-video-evidence/32580/4 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 446073] wrong mouse position when scaled inside SPICE virtual machine
https://bugs.kde.org/show_bug.cgi?id=446073 Yu-Hsuan Lai changed: What|Removed |Added CC||rainco...@gmail.com --- Comment #1 from Yu-Hsuan Lai --- Similar problem with me. Not in virtual machine, but on a normal destkop environment with Global Scale set to 200%. The cursor position is wrong for all Qt apps, making them unusable. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 438426] Issue with copy-paste image from Chromium based browser (Chrome, Edge) on Nightly Build
https://bugs.kde.org/show_bug.cgi?id=438426 Yu-Hsuan Lai changed: What|Removed |Added CC||rainco...@gmail.com --- Comment #8 from Yu-Hsuan Lai --- Similar issue for me with 5.0.0-beta1. It seems to always try to download from the URL. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 441903] New: It's very difficult to refresh "Show Common Colors"s colors
https://bugs.kde.org/show_bug.cgi?id=441903 Bug ID: 441903 Summary: It's very difficult to refresh "Show Common Colors"s colors Product: krita Version: 5.0.0-beta1 Platform: Microsoft Windows OS: All Status: REPORTED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: rainco...@gmail.com Target Milestone: --- Created attachment 141240 --> https://bugs.kde.org/attachment.cgi?id=141240&action=edit video SUMMARY This is technically by design. But I still submit it as a bug report because its design is practically unusable. Please see the attachment. STEPS TO REPRODUCE 1. Execute "Show Common Colors" action 2. Try to click the refresh button OBSERVED RESULT It's extremely difficult to click the button without accidentally close common colors pop up. EXPECTED RESULT Such a simple operation shouldn't require such high precision. SOFTWARE/OS VERSIONS Krita Version: 5.0.0-beta1 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-llp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: winnt Kernel Version: 10.0.22000 Pretty Productname: Windows 10 (10.0) Product Type: windows Product Version: 10 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 441901] It's impossible to close a file in dual monitor setup
https://bugs.kde.org/show_bug.cgi?id=441901 Yu-Hsuan Lai changed: What|Removed |Added OS|All |Microsoft Windows Platform|Compiled Sources|Microsoft Windows -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 441901] New: It's impossible to close a file in dual monitor setup
https://bugs.kde.org/show_bug.cgi?id=441901 Bug ID: 441901 Summary: It's impossible to close a file in dual monitor setup Product: krita Version: 5.0.0-beta1 Platform: Compiled Sources OS: All Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: rainco...@gmail.com Target Milestone: --- SUMMARY This bug only happens in some specific conditions. See steps to reproduce. STEPS TO REPRODUCE 1. Create and save two .kra files, namely A.kra and B.kra. 2. Close Krita and reopen in a blank state. 3. Set Settings -> General -> Window -> Multiple Document Mode to "Subwindows" 4. Switch to windows layout "Dual screen editing". Now we have two Krita windows, namely "Win1" and "Win2". 5. Save a new windows layout, with "Show active image in all windows" checked. 6. Open A.kra in both Krita windows. 7. Open B.kra by double clicking it from file explorer. 8. Close A.kra in Win1. 9. Close A.kra in Win2. OBSERVED RESULT A.kra is re-opened in Win1. EXPECTED RESULT A.kra is completely closed. SOFTWARE/OS VERSIONS Krita Version: 5.0.0-beta1 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-llp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: winnt Kernel Version: 10.0.22000 Pretty Productname: Windows 10 (10.0) Product Type: windows Product Version: 10 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 441900] New: Color history on pop-up palette is out of order
https://bugs.kde.org/show_bug.cgi?id=441900 Bug ID: 441900 Summary: Color history on pop-up palette is out of order Product: krita Version: 5.0.0-beta1 Platform: Compiled Sources OS: All Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: rainco...@gmail.com Target Milestone: --- Created attachment 141238 --> https://bugs.kde.org/attachment.cgi?id=141238&action=edit In order vs out of order SUMMARY Please see the attachment. On Advanced Color Selector, the color history is in order. On pop-up palette, it's out of order. STEPS TO REPRODUCE 1. Paint with several colors 2. Open pop-up palette OBSERVED RESULT Color history is out of order EXPECTED RESULT Color history is in order SOFTWARE/OS VERSIONS Krita Version: 5.0.0-beta1 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-llp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: winnt Kernel Version: 10.0.22000 Pretty Productname: Windows 10 (10.0) Product Type: windows Product Version: 10 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 441899] New: Pop-up palette doesn't dismiss itself at right click
https://bugs.kde.org/show_bug.cgi?id=441899 Bug ID: 441899 Summary: Pop-up palette doesn't dismiss itself at right click Product: krita Version: 5.0.0-beta1 Platform: Compiled Sources OS: All Status: REPORTED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: rainco...@gmail.com Target Milestone: --- SUMMARY I need to press RMB *twice* to dismiss pop-up palette. The first click seems to do nothing. STEPS TO REPRODUCE 1. Click RMB to activate pop-up palette 2. Click RMB again OBSERVED RESULT Nothing happens. Pop-up palette is still shown (if I click RMB again, then it's dismissed) EXPECTED RESULT Pop-up palette is dismissed SOFTWARE/OS VERSIONS Krita Version: 5.0.0-beta1 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-llp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: winnt Kernel Version: 10.0.22000 Pretty Productname: Windows 10 (10.0) Product Type: windows Product Version: 10 ADDITIONAL INFORMATION Not sure if it's a bug, but I've never seen any other apps work like this so I just assume it is. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 441837] Middle click sometimes stop being registered on DirectX11 canvas
https://bugs.kde.org/show_bug.cgi?id=441837 --- Comment #1 from Yu-Hsuan Lai --- After further investigation, I found that DX11 or OpenGL is actually irrelevant. What actually fixed this issue is checking "Tablet Settings -> Use Mouse Events for Right and Middle clicks." -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 441838] Ten Brushes crashes: wrapped C/C++ object of type QWidgetAction has been deleted
https://bugs.kde.org/show_bug.cgi?id=441838 Yu-Hsuan Lai changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #3 from Yu-Hsuan Lai --- Ok, I pinpointed it. On my computer these steps reproduce it 100% of the time. 1. Start Krita 2. Select Windows layout "Dual screen editing" (I believe it's built-in) 3. Tools -> Scripts -> Ten Brushes -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 441838] Ten Brushes crashes: wrapped C/C++ object of type QWidgetAction has been deleted
https://bugs.kde.org/show_bug.cgi?id=441838 --- Comment #2 from Yu-Hsuan Lai --- (In reply to Halla Rempt from comment #1) > I'm sorry, but I cannot reproduce this issue. Did you build Krita yourself > like you indicated in the Platform field originally? What language is your > system set to? Uh no it's just official 5.0.0-beta1 build. My system is in English. I observed something else... when I restart Krita, Ten Brushes works. But after a while it shows this error (but I can still use its shortcuts to switch brushes, just can't open the panel to set which slot is which brush). And once it crashes, if I restart Krita it works again. Then after a while it crashes again. I haven't pinpointed which action causes it to start crashing. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 441865] New: "Switch to Previous Preset" changes brush's opacity accidentally
https://bugs.kde.org/show_bug.cgi?id=441865 Bug ID: 441865 Summary: "Switch to Previous Preset" changes brush's opacity accidentally Product: krita Version: 5.0.0-beta1 Platform: Compiled Sources OS: All Status: REPORTED Severity: normal Priority: NOR Component: Tools Assignee: krita-bugs-n...@kde.org Reporter: rainco...@gmail.com Target Milestone: --- SUMMARY "Switch to Previous Preset" changes brush's opacity accidentally if transform tool is activated. It can be reliably reproduced (see below). STEPS TO REPRODUCE 1. Activate freehand brush tool 2. Select built-in brush "c)_Pencil-3_Large_4B" 3. Select built-in brush "a)_Eraser_Small" 4. Select built-in brush "c)_Pencil-3_Large_4B" again 5. Activate transform tool 6. Execute "Switch to Previous Preset" action 7. Activate freehand brush tool OBSERVED RESULT "a)_Eraser_Small" is the active brush, and its opacity is changed from 100 to 15 EXPECTED RESULT "a)_Eraser_Small" is the active brush, and its opacity remains 100 SOFTWARE/OS VERSIONS Krita Version: 5.0.0-beta1 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-llp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: winnt Kernel Version: 10.0.22000 Pretty Productname: Windows 10 (10.0) Product Type: windows Product Version: 10 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 441841] New: Assignable shortcuts for dockers
https://bugs.kde.org/show_bug.cgi?id=441841 Bug ID: 441841 Summary: Assignable shortcuts for dockers Product: krita Version: 5.0.0-beta1 Platform: Other OS: Other Status: REPORTED Severity: wishlist Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: rainco...@gmail.com Target Milestone: --- SUMMARY Right now we can't assign a shortcut to a docker. I think it'd be very useful if it's possible. For example I want to open Layers only when I need it. Right now the only way is to enter/exit canvas only mode. But I'd like to toggle dockers separately, not as a whole. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 441838] New: Ten Brushes crashes: wrapped C/C++ object of type QWidgetAction has been deleted
https://bugs.kde.org/show_bug.cgi?id=441838
Bug ID: 441838
Summary: Ten Brushes crashes: wrapped C/C++ object of type
QWidgetAction has been deleted
Product: krita
Version: 5.0.0-beta1
Platform: Compiled Sources
OS: All
Status: REPORTED
Severity: normal
Priority: NOR
Component: Scripting
Assignee: krita-bugs-n...@kde.org
Reporter: rainco...@gmail.com
Target Milestone: ---
SUMMARY
Ten Brushes script crashes itself
STEPS TO REPRODUCE
1. Tools -> Scripts -> Ten Brushes
OBSERVED RESULT
The script (not the whole Krita) crashes with the following log:
RuntimeError
Python 3.8.1: C:\Program Files\Krita (x64)\bin\krita.exe
Wed Sep 1 09:06:55 2021
A problem occurred in a Python script. Here is the sequence of
function calls leading up to the error, in the order they occurred.
C:\Program Files\Krita (x64)\share\krita\pykrita\tenscripts\tenscripts.py in
initialize(self=)
31 def initialize(self):
32 self.uitenscripts = uitenscripts.UITenScripts()
33 self.uitenscripts.initialize(self)
34
35 def readSettings(self):
self =
self.uitenscripts =
self.uitenscripts.initialize = >
C:\Program Files\Krita (x64)\share\krita\pykrita\tenscripts\uitenscripts.py in
initialize(self=,
tenscripts=)
35 self.tenscripts = tenscripts
36
37 self._loadGridLayout()
38 self._fillScripts()
39
self =
self._loadGridLayout = >
C:\Program Files\Krita (x64)\share\krita\pykrita\tenscripts\uitenscripts.py in
_loadGridLayout(self=)
97 def _loadGridLayout(self):
98 for item in range(0, 10):
99 self.addNewRow(item)
100
101 def _fillScripts(self):
self =
self.addNewRow = >
item = 0
C:\Program Files\Krita (x64)\share\krita\pykrita\tenscripts\uitenscripts.py in
addNewRow(self=, key=0)
60
61 directoryTextField.setReadOnly(True)
62
label.setText(self.tenscripts.actions[key].shortcut().toString(QKeySequence.NativeText))
63 directoryTextField.setToolTip(i18n("Selected path"))
64 directoryDialogButton.setToolTip(i18n("Select the script"))
label =
label.setText =
self =
self.tenscripts =
self.tenscripts.actions = [,
, ,
, ,
, ,
, ,
, ,
, ,
, ,
, ,
, ,
, ...]
key = 0
].shortcut undefined
global QKeySequence =
QKeySequence.NativeText = 0
RuntimeError: wrapped C/C++ object of type QWidgetAction has been deleted
__cause__ = None
__class__ =
__context__ = None
__delattr__ =
__dict__ = {}
__dir__ =
__doc__ = 'Unspecified run-time error.'
__eq__ =
__format__ =
__ge__ =
__getattribute__ =
__gt__ =
__hash__ =
__init__ =
__init_subclass__ =
__le__ =
__lt__ =
__ne__ =
__new__ =
__reduce__ =
__reduce_ex__ =
__repr__ =
__setattr__ =
__setstate__ =
__sizeof__ =
__str__ =
__subclasshook__ =
__suppress_context__ = False
__traceback__ =
args = ('wrapped C/C++ object of type QWidgetAction has been deleted',)
with_traceback =
The above is a description of an error in a Python program. Here is
the original traceback:
Traceback (most recent call last):
File "C:\Program Files\Krita
(x64)\share\krita\pykrita\tenscripts\tenscripts.py", line 33, in initialize
self.uitenscripts.initialize(self)
File "C:\Program Files\Krita
(x64)\share\krita\pykrita\tenscripts\uitenscripts.py", line 37, in initialize
self._loadGridLayout()
File "C:\Program Files\Krita
(x64)\share\krita\pykrita\tenscripts\uitenscripts.py", line 99, in
_loadGridLayout
self.addNewRow(item)
File "C:\Program Files\Krita
(x64)\share\krita\pykrita\tenscripts\uitenscripts.py", line 62, in addNewRow
label.setText(self.tenscripts.actions[key].shortcut().toString(QKeySequence.NativeText))
RuntimeError: wrapped C/C++ object of type QWidgetAction has been deleted
---
EXPECTED RESULT
Shows Ten Brushes' panel
SOFTWARE/OS VERSIONS
Krita
Version: 5.0.0-beta1
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-llp64
Build CPU: x86_64
CPU: x86_64
Kernel Type: winnt
Kernel Version: 10.0.22000
Pretty Productname: Windows 10 (10.0)
Product Type: windows
Product Version: 10
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 419833] Color Smudge Brush treats the space outside of the canvas as transparency
https://bugs.kde.org/show_bug.cgi?id=419833 Yu-Hsuan Lai changed: What|Removed |Added Resolution|WORKSFORME |FIXED --- Comment #8 from Yu-Hsuan Lai --- On Krita 5.0 beta, color smudge brush no longer smudges the transparency in from the outside of canvas. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 441837] New: Middle click sometimes stop being registered on DirectX11 canvas
https://bugs.kde.org/show_bug.cgi?id=441837 Bug ID: 441837 Summary: Middle click sometimes stop being registered on DirectX11 canvas Product: krita Version: 5.0.0-beta1 Platform: Compiled Sources OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Shortcuts and Canvas Input Settings Assignee: krita-bugs-n...@kde.org Reporter: rainco...@gmail.com Target Milestone: --- SUMMARY Sometimes, middle mouse click stop being register on the canvas. It's an elusive bug that can't be reliably reproduced, but happens very often (10+ times per day in my case). STEPS TO REPRODUCE 1. Open an empty canvas in Krita 2. Switch to another program 3. Use the program *for a while* (1~2 min) 4. Switch back to Krita OBSERVED RESULT Can't use MMB to pan the canvas any more. But still can scroll in dockers via kinetic scrolling. EXPECTED RESULT Being able to pan the canvas as usual. SOFTWARE/OS VERSIONS Windows: Windows 11 Pro Version 21H2 ADDITIONAL INFORMATION It's a very elusive bug that happens *sometimes*. I submit this report just for the record. And more importantly, it seems to only happen on DirectX11 canvas. If anyone ran into this bug, you could try to switch to OpenGL canvas. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419794] Cursor appears after unlocking screen
https://bugs.kde.org/show_bug.cgi?id=419794 --- Comment #17 from Yu-Hsuan Lai --- This issue bothers me so much that I almost quitted Krita (the cursor makes it very hard to paint details). Again, just for the record, I found a free app called Cursorcerer that allows me to hide the cursor at will. It's not open-sourced so I won't post the link here. If anyone runs into this issue in the future and is looking for a workaround, use it at your own risk. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419794] Cursor appears after unlocking screen
https://bugs.kde.org/show_bug.cgi?id=419794 --- Comment #16 from Yu-Hsuan Lai --- Created attachment 129885 --> https://bugs.kde.org/attachment.cgi?id=129885&action=edit accessibility Just for the record, this is my accessibility settings. And this bug still happens to me as before. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 423587] New: Snapping to grid doesn't work at all
https://bugs.kde.org/show_bug.cgi?id=423587 Bug ID: 423587 Summary: Snapping to grid doesn't work at all Product: krita Version: 4.3.0 Platform: macOS Disk Images OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: Tools/Move Assignee: krita-bugs-n...@kde.org Reporter: rainco...@gmail.com Target Milestone: --- Created attachment 129723 --> https://bugs.kde.org/attachment.cgi?id=129723&action=edit Video of no snapping SUMMARY STEPS TO REPRODUCE 1. Open Grid and Guides Docker 2. Check "Show Grid" 3. Check "Snap to Grid" 4. Draw a line on the canvas 5. Use Move Tool to the line around the grid lines OBSERVED RESULT No snapping happens EXPECTED RESULT Snapping happens SOFTWARE/OS VERSIONS macOS: 10.14.6 Krita: 4.3.0 ADDITIONAL INFORMATION See attachment -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420032] Random crashes on Mac (with canvas acceleration off)
https://bugs.kde.org/show_bug.cgi?id=420032 --- Comment #36 from Yu-Hsuan Lai --- Created attachment 129593 --> https://bugs.kde.org/attachment.cgi?id=129593&action=edit crash log from lldb I got this crash while changing some shortcuts. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 423170] MacOS' color picker pops up instead of Krita's internal color selector
https://bugs.kde.org/show_bug.cgi?id=423170 Yu-Hsuan Lai changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |INTENTIONAL --- Comment #4 from Yu-Hsuan Lai --- (In reply to Boudewijn Rempt from comment #3) > Well... Because macos users asked for it. We spent quite a bit of time > making sure the macos native color selector would show because we got > complaints Krita had its own. Well okay... I don't get why they hate Krita's own color picker. With palette and other nice stuff. I think it's better to have an option to use Krita's coloer picker instead of MacOS' then. But it's more a feature request than a bug report. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420032] Random crashes on Mac (with canvas acceleration off)
https://bugs.kde.org/show_bug.cgi?id=420032 Yu-Hsuan Lai changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #34 from Yu-Hsuan Lai --- Unfortunately it happened again with 4.3.0. I'm not sure if it's regression from 4.3.0-beta1 though because it happens rather rarely (once since 4.3.0 release). Maybe I were just lucky to not get this with beta1. The system log is the same as before. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 423176] "Preferences" disappears from app menus after add text
https://bugs.kde.org/show_bug.cgi?id=423176 --- Comment #3 from Yu-Hsuan Lai --- Well this is again an elusive bug... after reproducing it several times now I can't reproduce it at all. There might be some missing steps I haven't figured out. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 423176] "Preferences" disappears from app menus after add text
https://bugs.kde.org/show_bug.cgi?id=423176 --- Comment #2 from Yu-Hsuan Lai --- Created attachment 129494 --> https://bugs.kde.org/attachment.cgi?id=129494&action=edit "Settings" menu There isn't "Configuration Options" either -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 423176] New: "Preferences" disappears from app menus after add text
https://bugs.kde.org/show_bug.cgi?id=423176 Bug ID: 423176 Summary: "Preferences" disappears from app menus after add text Product: krita Version: 4.3.0 Platform: macOS Disk Images OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: Tool/Text Assignee: krita-bugs-n...@kde.org Reporter: rainco...@gmail.com Target Milestone: --- Created attachment 129493 --> https://bugs.kde.org/attachment.cgi?id=129493&action=edit where "Preferences" should've been SUMMARY The "Preferences" item disappear from app menus after add any text with SVG text tool. STEPS TO REPRODUCE 1. Active SVG Text Tool 2. Drag a region on the canvas 3. Add some text and save the text OBSERVED RESULT "Preferences" disappear from app menus EXPECTED RESULT "Preferences" is still under "Krita" app menu SOFTWARE/OS VERSIONS macOS: 10.14.6 Krita: 4.3.0 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 423170] MacOS' color picker pops up instead of Krita's internal color selector
https://bugs.kde.org/show_bug.cgi?id=423170 --- Comment #2 from Yu-Hsuan Lai --- (In reply to wolthera from comment #1) > Hi, we can't because of https://bugs.kde.org/show_bug.cgi?id=378282 , so I > think we'll need to close this? But I'm not talking about picking color from other windows. I'm talking about the Krita internal color selector is completely unavailable on MacOS. Why do we discard the whole well-designed color selector just to be able to pick colors from other windows? If someone really needs to pick colors from other windows they can screenshot and paste to Krita (on Mac there is a default shortcut to screenshot into clipboard so it's rather convenient). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 378282] Filter Layer/Artistic/Index Color's Color Picker cannot pick colors outside oh its own window.
https://bugs.kde.org/show_bug.cgi?id=378282 Yu-Hsuan Lai changed: What|Removed |Added CC||rainco...@gmail.com --- Comment #6 from Yu-Hsuan Lai --- But Clip Studio Paint is able to pick color from other windows, even on MacOS? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419794] Cursor appears after unlocking screen
https://bugs.kde.org/show_bug.cgi?id=419794 --- Comment #14 from Yu-Hsuan Lai --- Still happens with 4.3.0. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422729] No action (assignable shortcut) for Magnetic Selection Tool
https://bugs.kde.org/show_bug.cgi?id=422729 --- Comment #8 from Yu-Hsuan Lai --- Was this fix supposed to be included in the 4.3.0 release? I just downloaded 4.3.0 (not 4.3.0-beta2) but Magnetic Selection Tool still has no assignable shortcut. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 423170] New: MacOS' color picker pops up instead of Krita's internal color selector
https://bugs.kde.org/show_bug.cgi?id=423170
Bug ID: 423170
Summary: MacOS' color picker pops up instead of Krita's
internal color selector
Product: krita
Version: 4.3.0
Platform: macOS Disk Images
OS: macOS
Status: REPORTED
Severity: normal
Priority: NOR
Component: Color Selectors
Assignee: krita-bugs-n...@kde.org
Reporter: rainco...@gmail.com
Target Milestone: ---
Created attachment 129491
--> https://bugs.kde.org/attachment.cgi?id=129491&action=edit
MacOS' color picker
SUMMARY
When picking a color, Krita's internal color selector ("Select a Color" dialog)
never shows up. Instead, MacOS' color picker is used. I believe this is a bug
STEPS TO REPRODUCE
1. Click the foreground color patch on the toolbar.
OBSERVED RESULT
MacOS' color picker pops up.
EXPECTED RESULT
Krita's internal color picker ("Select a Color") pops up.
SOFTWARE/OS VERSIONS
macOS: 10.14.6
Krita: 4.3.0
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 422907] New: Brush preset loses its tags after being overwritten
https://bugs.kde.org/show_bug.cgi?id=422907 Bug ID: 422907 Summary: Brush preset loses its tags after being overwritten Product: krita Version: 4.3.0-beta2 Platform: macOS Disk Images OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: Resource Management Assignee: krita-bugs-n...@kde.org Reporter: rainco...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Select a brush with tags 2. Open brush settings and change its size 3. Overwrite brush 4. Close Krita and relaunch it OBSERVED RESULT The brush loses all its tags. EXPECTED RESULT The brush's setting is overwritten, but the tags are unchanged. SOFTWARE/OS VERSIONS Krita: 4.3.0-beta2 macOS: 10.14.6 ADDITIONAL INFORMATION It's rather an elusive bug that doesn't happen every time. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422729] No action (assignable shortcut) for Magnetic Selection Tool
https://bugs.kde.org/show_bug.cgi?id=422729 --- Comment #2 from Yu-Hsuan Lai --- (In reply to Boudewijn Rempt from comment #1) > Looks like most of the .action files in the plugins/tools folder are broken, > which is why the actions are also present in krita/krita.action, which > shouldn't be necessary... Is it possible to workaround this without building my own Krita? Like manually creating this .actions file with Magnetic Selection Tool or something? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422729] New: No action (assignable shortcut) for Magnetic Selection Tool
https://bugs.kde.org/show_bug.cgi?id=422729 Bug ID: 422729 Summary: No action (assignable shortcut) for Magnetic Selection Tool Product: krita Version: 4.3.0-beta2 Platform: macOS Disk Images OS: All Status: REPORTED Severity: normal Priority: NOR Component: Tools/Selection Assignee: krita-bugs-n...@kde.org Reporter: rainco...@gmail.com Target Milestone: --- SUMMARY It seems that Magnetic Selection Tool isn't an action, and therefore it's impossible to assign a shortcut for it. STEPS TO REPRODUCE 1. Open Keyboard Shortcuts configuration OBSERVED RESULT Magnetic Selection Tool isn't there EXPECTED RESULT Being able to assign a shortcut for Magnetic Selection Tool SOFTWARE/OS VERSIONS Krita: 4.3.0-beta2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420738] Random crash when exiting "Canvas Input Settings" dialog on Mac
https://bugs.kde.org/show_bug.cgi?id=420738 Yu-Hsuan Lai changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #5 from Yu-Hsuan Lai --- (In reply to vanyossi from comment #4) > I can't make it crash at all. Are you still getting this. could you paste > the log in krita -> help -> show krita info for bug reports? > > Also please attach the backtrace from lldb. After it crashes type "bt all" > to get a backtrace from the crash. This hasn't happen since 4.3.0-beta1 so I'll close this. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419794] Cursor appears after unlocking screen
https://bugs.kde.org/show_bug.cgi?id=419794 --- Comment #12 from Yu-Hsuan Lai --- (In reply to vanyossi from comment #11) > I cannot reproduce it at all. It may be something in your configuration > –macos accesibility, or kritarc– that is preventing krita to change. > > Have you tried reseting your kritarc file? > https://docs.krita.org/en/KritaFAQ.html#resetting-krita-configuration I have reset the kritarc files but the bug still presents. I noticed one more thing tho: when I just launch Krita the cursor doesn't show up. It shows up after I switch to another app (any app) and switch back, and refuses to go away until I restart Krita. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 421448] New: Crash when opening PSD files from Finder
https://bugs.kde.org/show_bug.cgi?id=421448
Bug ID: 421448
Summary: Crash when opening PSD files from Finder
Product: krita
Version: 4.3.0-beta1
Platform: macOS Disk Images
OS: macOS
Status: REPORTED
Severity: normal
Priority: NOR
Component: File formats
Assignee: krita-bugs-n...@kde.org
Reporter: rainco...@gmail.com
Target Milestone: ---
Created attachment 128416
--> https://bugs.kde.org/attachment.cgi?id=128416&action=edit
system.log is the crash log shown by the OS.
SUMMARY
Krita crashes when I try to open a PSD file from Finder.
STEPS TO REPRODUCE
1. Make sure there is no a Krita instance running
2. Open Finder
3. Right click on a PSD file
4. "Open With" -> "Other..." -> select Krita
OBSERVED RESULT
The splash art shows up; then Krita crashes.
EXPECTED RESULT
Krita is launched with the given PSD opened.
SOFTWARE/OS VERSIONS
macOS: 10.14.6
Krita: 4.3.0-beta1
ADDITIONAL INFORMATION
If Krita is already opened when I do this, then nothing happens. The PSD won't
be opened and Krita won't crash.
If I open the PSD from Krita ("File" -> "Open...", instead of from Finder),
everything works as expected.
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 419794] Cursor appears after unlocking screen
https://bugs.kde.org/show_bug.cgi?id=419794 --- Comment #10 from Yu-Hsuan Lai --- Created attachment 128415 --> https://bugs.kde.org/attachment.cgi?id=128415&action=edit System information -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419794] Cursor appears after unlocking screen
https://bugs.kde.org/show_bug.cgi?id=419794 Yu-Hsuan Lai changed: What|Removed |Added Status|NEEDSINFO |REOPENED Resolution|WAITINGFORINFO |--- --- Comment #9 from Yu-Hsuan Lai --- See the new attachment -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419794] Cursor appears after unlocking screen
https://bugs.kde.org/show_bug.cgi?id=419794 --- Comment #8 from Yu-Hsuan Lai --- Created attachment 128413 --> https://bugs.kde.org/attachment.cgi?id=128413&action=edit screen recording -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419794] Cursor appears after unlocking screen
https://bugs.kde.org/show_bug.cgi?id=419794 --- Comment #7 from Yu-Hsuan Lai --- (In reply to vanyossi from comment #6) > Im sorry but I cannot reproduce the issue but going to krita, setting to > cursor to no cursor and brush outline. Getting the mac to "lock screen" > using the Apple menu. Typing password to unlock and coming back to the app. > Does not show the cursor as described. > > I could be doing something different from what you are doing. if recording > screen does not show the cursor, could you record using a cellphone? Does > this happen on another macos computer? (if you have another one available) well in my case, I don't need to do anything to "reproduce" it with 4.3.0-beta1... the cursor is always there and never gone after restarting Krita or even rebooting the system. I'll try a real screenrecording software instead of macos' builtin screenrecording. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420032] Random crashes on Mac (with canvas acceleration off)
https://bugs.kde.org/show_bug.cgi?id=420032 --- Comment #32 from Yu-Hsuan Lai --- I've been using 4.3.0-beta1 for a while (30+ hrs) and this hasn't happened. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419794] Cursor appears after unlocking screen
https://bugs.kde.org/show_bug.cgi?id=419794 --- Comment #5 from Yu-Hsuan Lai --- UPDATE: this is exacerbated with 4.3.0-beta1. Now the system cursor always shows up, no matter what the setting of "Cursor Shape" is. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420226] Random crashes on Mac while deselecting a selection
https://bugs.kde.org/show_bug.cgi?id=420226 Yu-Hsuan Lai changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #7 from Yu-Hsuan Lai --- I've been using 4.3.0-beta1 for a while (30+ hrs) and this hasn't happened. We could probably close this for now. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420956] New: KDE desktop didn't automatically change display size to fit remote XServer screen size
https://bugs.kde.org/show_bug.cgi?id=420956 Bug ID: 420956 Summary: KDE desktop didn't automatically change display size to fit remote XServer screen size Product: plasmashell Version: 5.18.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: a...@yylai.xyz CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 128113 --> https://bugs.kde.org/attachment.cgi?id=128113&action=edit Screenshot SUMMARY I am running KDE plasma with a remote X11 server. If I resize the remote screen window, expand it for example, desktop and panel will not adjust their size as expected, thus leave expanded area blank, but I am able to drag windows freely across whole screen. STEPS TO REPRODUCE 1. Set environment variable 'DISPLAY' to remote xserver 2. Start KDE plasma session by startplasma-x11 3. Resize remote xserver screen OBSERVED RESULT Windows running in KDE automatically adjusted their position and size, but panel and desktop background did not. EXPECTED RESULT All the components in KDE should automatically fit the new screen size. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.69.0 Qt Version: 5.14.2 XServer: X410-2.8.2 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420032] Random crashes on Mac (with canvas acceleration off)
https://bugs.kde.org/show_bug.cgi?id=420032 --- Comment #30 from Yu-Hsuan Lai --- This particular bug doesn't seem to happen with 4.3.0. It might just be a placebo effect though. Does 4.3.0(2bae978) uses a different Qt version than 4.2.9? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420738] Random crash when exiting "Canvas Input Settings" dialog on Mac
https://bugs.kde.org/show_bug.cgi?id=420738 --- Comment #2 from Yu-Hsuan Lai --- Created attachment 127973 --> https://bugs.kde.org/attachment.cgi?id=127973&action=edit macOS system log -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420738] Random crash when exiting "Canvas Input Settings" dialog on Mac
https://bugs.kde.org/show_bug.cgi?id=420738 --- Comment #1 from Yu-Hsuan Lai --- Created attachment 127972 --> https://bugs.kde.org/attachment.cgi?id=127972&action=edit lldb log -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420738] New: Random crash when exiting "Canvas Input Settings" dialog on Mac
https://bugs.kde.org/show_bug.cgi?id=420738 Bug ID: 420738 Summary: Random crash when exiting "Canvas Input Settings" dialog on Mac Product: krita Version: nightly build (please specify the git hash!) Platform: macOS Disk Images OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: rainco...@gmail.com Target Milestone: --- Created attachment 127971 --> https://bugs.kde.org/attachment.cgi?id=127971&action=edit this dialog SUMMARY Crash when exiting "Canvas Input Settings" dialog. It doesn't happen every time. STEPS TO REPRODUCE Unable to reliably reproduce it. But it seems to happen with this specific dialog the most. OBSERVED RESULT The UI freezes forever, but from the command line we can see the Krita process already crashed. EXPECTED RESULT Not crash. SOFTWARE/OS VERSIONS macOS: 10.14.6 Krita: 4.3.0 (2bae978) ADDITIONAL INFORMATION See attachment -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420231] The UI glitches while using Outline Selection Tool and holding Cmd
https://bugs.kde.org/show_bug.cgi?id=420231 --- Comment #17 from Yu-Hsuan Lai --- Ok, please follow up at Bug 420737 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420737] Modifier key conflicts with Outline Selection Tool on Mac
https://bugs.kde.org/show_bug.cgi?id=420737 --- Comment #1 from Yu-Hsuan Lai --- Created attachment 127970 --> https://bugs.kde.org/attachment.cgi?id=127970&action=edit screen recording -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420737] New: Modifier key conflicts with Outline Selection Tool on Mac
https://bugs.kde.org/show_bug.cgi?id=420737 Bug ID: 420737 Summary: Modifier key conflicts with Outline Selection Tool on Mac Product: krita Version: nightly build (please specify the git hash!) Platform: macOS Disk Images OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: Tools/Selection Assignee: krita-bugs-n...@kde.org Reporter: rainco...@gmail.com Target Milestone: --- SUMMARY On Mac, while using Outline Selection Tool, pressing "Command" does two things: 1) makes it work like Polygon Selection Tool temporarily 2) makes it work under subtract mode STEPS TO REPRODUCE 1. Switch to Outline Selection Tool. 2. Draw a curve, but don't close the outline 3. Holding Cmd. 4. Click on canvas. 5. Finish selection OBSERVED RESULT The "outside" of the intended region is selected EXPECTED RESULT The intended region is selected SOFTWARE/OS VERSIONS macOS: 10.14.6 Krita: 4.3.0 (2bae978) ADDITIONAL INFORMATION See attachment -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420231] The UI glitches while using Outline Selection Tool and holding Cmd
https://bugs.kde.org/show_bug.cgi?id=420231 --- Comment #16 from Yu-Hsuan Lai --- (In reply to vanyossi from comment #15) > Its normal if you press "alt" while releasing the selection action. Notice > how in the video you can see selection change to substract mode (the minus > sign). so instead of replacing the selection it substracts from your current > selection. > > Im closing this bug as you no longer can reproduce the behaviour in 4.3 > > If you have other problems with selection open a different bug to give every > issue a better follow up. Yeah but I were 100% not press "alt"... Anyway I'll submit another bug report for that. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420231] The UI glitches while using Outline Selection Tool and holding Cmd
https://bugs.kde.org/show_bug.cgi?id=420231 --- Comment #14 from Yu-Hsuan Lai --- In 4.3.0 (git 2bae978), the UI glitch doesn't happen. However it selects the "outside" of my intended region. Is this normal? (See the latest attachment) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420231] The UI glitches while using Outline Selection Tool and holding Cmd
https://bugs.kde.org/show_bug.cgi?id=420231 --- Comment #13 from Yu-Hsuan Lai --- Created attachment 127936 --> https://bugs.kde.org/attachment.cgi?id=127936&action=edit the selection is inverted -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420231] The UI glitches while using Outline Selection Tool and holding Cmd
https://bugs.kde.org/show_bug.cgi?id=420231 --- Comment #11 from Yu-Hsuan Lai --- It happens to me with any combination of (4.9.2, nightly) and (canvas acceleration on, canvas acceleration off). No discernible difference. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420231] The UI glitches while using Outline Selection Tool and holding Cmd
https://bugs.kde.org/show_bug.cgi?id=420231 --- Comment #10 from Yu-Hsuan Lai --- Created attachment 127891 --> https://bugs.kde.org/attachment.cgi?id=127891&action=edit system log 2 (nightly build) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420231] The UI glitches while using Outline Selection Tool and holding Cmd
https://bugs.kde.org/show_bug.cgi?id=420231 --- Comment #9 from Yu-Hsuan Lai --- Created attachment 127890 --> https://bugs.kde.org/attachment.cgi?id=127890&action=edit system log 1 (4.9.2) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419794] Cursor appears after unlocking screen
https://bugs.kde.org/show_bug.cgi?id=419794 Yu-Hsuan Lai changed: What|Removed |Added Ever confirmed|0 |1 Resolution|DUPLICATE |--- Status|RESOLVED|REOPENED --- Comment #4 from Yu-Hsuan Lai --- (In reply to wolthera from comment #3) > Same issue as the other cursor bug. Given that that has more discussion I'll > mark this as a duplicate. > > *** This bug has been marked as a duplicate of bug 419921 *** Sorry, but are you sure it's the same bug? Bug 419921 looks almost like the opposite of this issue. This issue is that the cursor (arrow) appears when it shouldn't, and Bug 419921 is about the cursor disappearing, if I read it correctly. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420231] The UI glitches while using Outline Selection Tool and holding Cmd
https://bugs.kde.org/show_bug.cgi?id=420231 Yu-Hsuan Lai changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|UNMAINTAINED|--- Ever confirmed|0 |1 --- Comment #7 from Yu-Hsuan Lai --- Uh, actually this issue still happens to me with canvas acceleration on. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420231] The UI glitches while using Outline Selection Tool and holding Cmd
https://bugs.kde.org/show_bug.cgi?id=420231 --- Comment #6 from Yu-Hsuan Lai --- (In reply to wolthera from comment #5) > This is a problem caused by the fact that the canvas isn't using graphics > acceleration. We implemented graphics acceleration via opengl to resolve > issues like these, though it can be turned off when your device's opengl > support is terrible. I recommend turning on graphics acceleration in the > preferences, or just living with the glitch. Well canvas acceleration is practically unusable on som3 Mac (see Bug 419783). And it's not a visual glitch only, but functionality issue too. So I think at least one of these two should be considered a confirmed bug. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420226] Random crashes on Mac while deselecting a selection
https://bugs.kde.org/show_bug.cgi?id=420226 --- Comment #3 from Yu-Hsuan Lai --- (In reply to vanyossi from comment #2) > I cannot reproduce this issue, i suppose because its random its not that > easy to reproduce. Looking at the log provided I can only tell the crash > ocurred somewhere at KisSelection::pixelSelection() > > Are you generate lldb backtraces? Frankly I don't know how to do that. I tried something like this: > ❯ lldb /Applications/krita.app/Contents/MacOS/krita > (lldb) target create "/Applications/krita.app/Contents/MacOS/krita" > runCurrent executable set to '/Applications/krita.app/Contents/MacOS/krita' > (x86_64). > (lldb) run > error: process exited with status -1 (Error 1) But as you can see it doesn't work. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420231] The UI glitches while using Outline Selection Tool and holding Cmd
https://bugs.kde.org/show_bug.cgi?id=420231 --- Comment #3 from Yu-Hsuan Lai --- (In reply to vanyossi from comment #1) > Im sorry but I couldn't reproduce the issue with the instructions given. If > I make a curve and lift the pen the selection is created. Then pressing and > Hold Cmd and click on canvas creates a new selection. > > Could you explain some more or post a video that shows the issue? > > Tested on macos 10.14.6 krita (94a83a7) Sure. I attached a video. Hope it makes things clearer! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420231] The UI glitches while using Outline Selection Tool and holding Cmd
https://bugs.kde.org/show_bug.cgi?id=420231 --- Comment #2 from Yu-Hsuan Lai --- Created attachment 127769 --> https://bugs.kde.org/attachment.cgi?id=127769&action=edit the video showing the buggy operation -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420230] The background color "square" doesn't update correctly in Artistic Color Selector
https://bugs.kde.org/show_bug.cgi?id=420230 --- Comment #3 from Yu-Hsuan Lai --- (In reply to vanyossi from comment #2) > This is intentional as described by de documentation: "The blip shows the > position of current foreground color on the wheel (black&white circle) and > on the value scale (black&white line). Last selected swatches are outlined." > from > "https://docs.krita.org/en/reference_manual/dockers/artistic_color_selector. > html#usage" > > If you believe the oulined square should correspond to the backgroundcolor > and the blip to the foreground could you open the topic for discussion in > the forum where other users can add input. (https://krita-artists.org/) Thanks. I missed the "Last selected swatched are outlined" part. Sorry for mis-report. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420230] The background color "square" doesn't update correctly in Artistic Color Selector
https://bugs.kde.org/show_bug.cgi?id=420230 --- Comment #4 from Yu-Hsuan Lai --- (In reply to vanyossi from comment #2) > This is intentional as described by de documentation: "The blip shows the > position of current foreground color on the wheel (black&white circle) and > on the value scale (black&white line). Last selected swatches are outlined." > from > "https://docs.krita.org/en/reference_manual/dockers/artistic_color_selector. > html#usage" > > If you believe the oulined square should correspond to the backgroundcolor > and the blip to the foreground could you open the topic for discussion in > the forum where other users can add input. (https://krita-artists.org/) Thanks. I missed the "Last selected swatched are outlined" part. Sorry for mis-report. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420231] New: The UI glitches while using Outline Selection Tool and holding Cmd
https://bugs.kde.org/show_bug.cgi?id=420231 Bug ID: 420231 Summary: The UI glitches while using Outline Selection Tool and holding Cmd Product: krita Version: nightly build (please specify the git hash!) Platform: macOS Disk Images OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: Tools/Selection Assignee: krita-bugs-n...@kde.org Reporter: rainco...@gmail.com Target Milestone: --- Created attachment 127630 --> https://bugs.kde.org/attachment.cgi?id=127630&action=edit the glitch SUMMARY Holding Cmd seems to allow Outline Selection Tool to draw straight lines, similar to Polygon Selection Tool. But instead it causes UI glitches. STEPS TO REPRODUCE 1. Switch to Outline Selection Tool. 2. Draw a curve, but don't close the outline 3. Holding Cmd. 4. Click on canvas. OBSERVED RESULT It does nothing but glitches the UI. See attachment. EXPECTED RESULT A straight segment should be added to the current unfinished selection outline. SOFTWARE/OS VERSIONS macOS: 10.14.6 Krita: Nightly build (44e3f62) ADDITIONAL INFORMATION Same with 4.2.9. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420230] The background color "square" doesn't update correctly in Artistic Color Selector
https://bugs.kde.org/show_bug.cgi?id=420230 --- Comment #1 from Yu-Hsuan Lai --- Created attachment 127629 --> https://bugs.kde.org/attachment.cgi?id=127629&action=edit expected result -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420230] New: The background color "square" doesn't update correctly in Artistic Color Selector
https://bugs.kde.org/show_bug.cgi?id=420230 Bug ID: 420230 Summary: The background color "square" doesn't update correctly in Artistic Color Selector Product: krita Version: nightly build (please specify the git hash!) Platform: macOS Disk Images OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: Color Selectors Assignee: krita-bugs-n...@kde.org Reporter: rainco...@gmail.com Target Milestone: --- Created attachment 127628 --> https://bugs.kde.org/attachment.cgi?id=127628&action=edit observed result SUMMARY By "background color square" I mean the little square in Artistic Color Selector on the background color selected. Not the "background color indicator" in the lower right corner. Similar to Bug 324121, but only the background color square is wrong. STEPS TO REPRODUCE 1. Select a background color, say blue, by right-clicking blue on Artistic Color Selector. 2. Select a different foreground color, say red, by left-clicking red on Artistic Color Selector. OBSERVED RESULT Both the "circle" and "square" are on red. See observed.png EXPECTED RESULT "Circle" is on red and "square" is on blue. See expected.png SOFTWARE/OS VERSIONS macOS: 10.14.6 Krita: Nightly build (44e3f62) ADDITIONAL INFORMATION Same with 4.2.9 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420229] New: Unable to overwrite existing workspace
https://bugs.kde.org/show_bug.cgi?id=420229 Bug ID: 420229 Summary: Unable to overwrite existing workspace Product: krita Version: nightly build (please specify the git hash!) Platform: macOS Disk Images OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: Resource Management Assignee: krita-bugs-n...@kde.org Reporter: rainco...@gmail.com Target Milestone: --- Created attachment 127627 --> https://bugs.kde.org/attachment.cgi?id=127627&action=edit The warning sign SUMMARY It seems impossible to make changes to an existing workspace. STEPS TO REPRODUCE 1. Save the workspace with a unique name, e.g. "Painting" 2. Resize a docker 3. Save the workspace with the same name OBSERVED RESULT It shows a warning "Saving will overwrite the original workspace". But after pressing the save button, nothing happens. EXPECTED RESULT The original workspace should be overwritten. SOFTWARE/OS VERSIONS macOS: 10.14.6 Krita: Nightly build (git 44e3f62) ADDITIONAL INFORMATION In 4.2.9, it doesn't work either, but with a different result: it saves a new workspace named "Painting2". -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420226] Random crashes on Mac while deselecting a selection
https://bugs.kde.org/show_bug.cgi?id=420226 --- Comment #1 from Yu-Hsuan Lai --- Created attachment 127626 --> https://bugs.kde.org/attachment.cgi?id=127626&action=edit Krita Usage Log, if it matters -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420226] New: Random crashes on Mac while deselecting a selection
https://bugs.kde.org/show_bug.cgi?id=420226 Bug ID: 420226 Summary: Random crashes on Mac while deselecting a selection Product: krita Version: 4.2.9 Platform: macOS Disk Images OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: Tools/Selection Assignee: krita-bugs-n...@kde.org Reporter: rainco...@gmail.com Target Milestone: --- Created attachment 127625 --> https://bugs.kde.org/attachment.cgi?id=127625&action=edit system.log is the crash log shown by the OS. SUMMARY This crash looks very different from https://bugs.kde.org/show_bug.cgi?id=420032 so I'm filing a separate report. It happened when I have a selection on the canvas and pressed Cmd+D to deselect it. Krita semi-froze for several seconds. During the period I can select a different layer or switch tools, but the canvas was completely frozen. Then Krita crashed. The stack trace looks different from Bug 420032 too. STEPS TO REPRODUCE Unable to consistently reproduce. OBSERVED RESULT Crash EXPECTED RESULT Not crash, and selection should be deselected. SOFTWARE/OS VERSIONS macOS: 10.14.6 Krita: 4.9.2 ADDITIONAL INFORMATION See attachment -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420032] Random crashes on Mac (with canvas acceleration off)
https://bugs.kde.org/show_bug.cgi?id=420032 --- Comment #29 from Yu-Hsuan Lai --- (In reply to vanyossi from comment #28) > Hi! going trouhgh the logs and the info provided I did not find anything > conclusive, but I have some ideas. Another contributor helped set a better > isolation environment from homebrew compiles, but apparently it did not work > ery well. > > I recommend you check all libraries in the build. i/lib using otool -L (for > all linked libraries) and/or otool -l (for global rpath of that library), im > suspecting some libraries are linked to the homebrew compiled sources > instead of krita 3rdparty Qt. But these crashes happened with official stable 4.2.9, not my home-built Krita. At the bottom of the system log, it dumps the libraries used, and it seems to link to its own Qt: > 0x11e8ca000 -0x11e8ddffb +sip.so (0) > > /Applications/krita.app/Contents/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/PyQt5/sip.so > 0x11e96d000 -0x11e9befff +krita.so (0) > <6AFF8C97-AD49-3E75-A378-004D53FE08A4> > /Applications/krita.app/Contents/Frameworks/krita-python-libs/PyKrita/krita.so > 0x11ea39000 -0x11eba8ff3 +QtCore.so (0) > > /Applications/krita.app/Contents/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/PyQt5/QtCore.so > 0x11ed7c000 -0x11ef0efff +QtGui.so (0) > <767C40B2-F3AD-3260-8EFC-CF6672F2CEF4> > /Applications/krita.app/Contents/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/PyQt5/QtGui.so > 0x11f0fe000 -0x11f392ffb +QtWidgets.so (0) > <1CCA3B9B-D531-3AA8-A9CE-E1B1D1AC98D3> > /Applications/krita.app/Contents/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/PyQt5/QtWidgets.so > 0x11f6c5000 -0x11f6ecff3 +QtXml.so (0) > > /Applications/krita.app/Contents/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/PyQt5/QtXml.so -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420032] Random crashes on Mac (with canvas acceleration off)
https://bugs.kde.org/show_bug.cgi?id=420032 --- Comment #26 from Yu-Hsuan Lai --- (In reply to Boudewijn Rempt from comment #25) > Yes... It's pretty similar. Qt wants to put a dialog on screen, and then > there's a crash deep in cocoa. Oh wait, I have "Enable native file dialogs" enabled. Do you think it's the potential problem? Should I disabled it and keep using for a while? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420032] Random crashes on Mac (with canvas acceleration off)
https://bugs.kde.org/show_bug.cgi?id=420032 --- Comment #24 from Yu-Hsuan Lai --- Created attachment 127603 --> https://bugs.kde.org/attachment.cgi?id=127603&action=edit system.log is the crash log shown by the OS. Another similar crash. It happened when I pressed shift+Cmd+S to save a file under another name. But I tried to do it again and couldn't reproduce the crash. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420032] Random crashes on Mac (with canvas acceleration off)
https://bugs.kde.org/show_bug.cgi?id=420032 --- Comment #22 from Yu-Hsuan Lai --- (In reply to Boudewijn Rempt from comment #21) > It might be worth it to investiage libqcocoa, since that's where the crash > happens. https://forum.qt.io/topic/34280/solved-qt5-and-mac-libqcocoa/3 > suggests running otool -L on libqcocoa.dylib . Maybe that has some > unresolved dependencies? > ❯ otool -L ./Contents/PlugIns/platforms/libqcocoa.dylib > ./Contents/PlugIns/platforms/libqcocoa.dylib: > libqcocoa.dylib (compatibility version 0.0.0, current version 0.0.0) > > /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices > (compatibility version 1.0.0, current version 1069.11.0) > /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon > (compatibility version 2.0.0, current version 162.0.0) > /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore > (compatibility version 1.2.0, current version 1.11.0) > /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo > (compatibility version 1.2.0, current version 1.5.0) > /System/Library/Frameworks/Metal.framework/Versions/A/Metal > (compatibility version 1.0.0, current version 212.2.3) > /System/Library/Frameworks/IOSurface.framework/Versions/A/IOSurface > (compatibility version 1.0.0, current version 1.0.0) > /usr/lib/libcups.2.dylib (compatibility version 2.0.0, current version > 2.14.0) >. /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation (compatibility version 150.0.0, current version 1673.126.0) > > /System/Library/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics > (compatibility version 64.0.0, current version 1348.12.4) > /System/Library/Frameworks/CoreText.framework/Versions/A/CoreText > (compatibility version 1.0.0, current version 1.0.0) > /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation > (compatibility version 300.0.0, current version 1673.126.0) > /usr/lib/libz.1.dylib (compatibility version 1.0.0, current version > 1.2.11) > /System/Library/Frameworks/ImageIO.framework/Versions/A/ImageIO > (compatibility version 1.0.0, current version 1.0.0) > /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit > (compatibility version 45.0.0, current version 1894.10.126) > @loader_path/../../Frameworks/QtPrintSupport.framework/Versions/5/QtPrintSupport (compatibility version 5.12.0, current version 5.12.7) > @loader_path/../../Frameworks/QtWidgets.framework/Versions/5/QtWidgets > (compatibility version 5.12.0, current version 5.12.7) > @loader_path/../../Frameworks/QtGui.framework/Versions/5/QtGui > (compatibility version 5.12.0, current version 5.12.7) > @loader_path/../../Frameworks/QtCore.framework/Versions/5/QtCore > (compatibility version 5.12.0, current version 5.12.7) > /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration (compatibility version 1.0.0, current version 1.0.0) > /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit > (compatibility version 1.0.0, current version 275.0.0) > /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL > (compatibility version 1.0.0, current version 1.0.0) > /System/Library/Frameworks/AGL.framework/Versions/A/AGL (compatibility > version 1.0.0, current version 1.0.0) > /usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version > 800.7.0) > /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current > version 1281.0.0) > /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices (compatibility version 1.0.0, current version 52.0.0) > /usr/lib/libobjc.A.dylib (compatibility version 1.0.0, current version > 228.0.0) I'm not sure if there is anything abnormal here. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420032] Random crashes on Mac (with canvas acceleration off)
https://bugs.kde.org/show_bug.cgi?id=420032 --- Comment #20 from Yu-Hsuan Lai --- Created attachment 127561 --> https://bugs.kde.org/attachment.cgi?id=127561&action=edit Krita Usage Log 2 Krita usage log. There isn't much to see tho, except this time it correctly reports Krita version of 4.2.9 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420032] Random crashes on Mac (with canvas acceleration off)
https://bugs.kde.org/show_bug.cgi?id=420032 --- Comment #19 from Yu-Hsuan Lai --- Well... the same kind of crash (same stack dump in system log) still happens even without home-built Krita. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420032] Random crashes on Mac (with canvas acceleration off)
https://bugs.kde.org/show_bug.cgi?id=420032 --- Comment #18 from Yu-Hsuan Lai --- (In reply to Boudewijn Rempt from comment #17) > And is it more stable? No crash yet, but it's hard to tell for now because it only crashed one or two times a day before. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420032] Random crashes on Mac (with canvas acceleration off)
https://bugs.kde.org/show_bug.cgi?id=420032 --- Comment #16 from Yu-Hsuan Lai --- After removing the half-ass-home-built Krita, now both the "About Krita" and "Show system information" windows report Krita version 4.2.9. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420032] Random crashes on Mac (with canvas acceleration off)
https://bugs.kde.org/show_bug.cgi?id=420032 --- Comment #14 from Yu-Hsuan Lai --- (In reply to Boudewijn Rempt from comment #13) > Yes, it should correctly build all dependencies in the framework. I haven't > managed to talk to Ivan for some days (he's in mexico, and his internet > connection was flaky) and I'm in the Netherlands and was sick... And I don't > know where the reference to Qt 5.14 comes from; that's not built by any of > our scripts. Do you have Qt 5.14 on your mac for some other project? Yeah no hurry. I understand it's a bug tracker of open source project, not a customer support line. I do have Qt 5.14 installed via Homebrew (to develop an Anki plugin IIRC). Would It be relevant tho if Krita uses its own external dependencies tho? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420032] Random crashes on Mac (with canvas acceleration off)
https://bugs.kde.org/show_bug.cgi?id=420032 --- Comment #12 from Yu-Hsuan Lai --- (In reply to Boudewijn Rempt from comment #11) > Yes, something is definitely too weird for words there. I'd make the > home-built Krita inaccessible to start with, and maybe test with a clean > test user. The home-built Krita never runs actually (as I stated in https://krita-artists.org/t/improve-mac-build-instructions/5250/29, it keeps saying libKF5I18n needs Qt 5.14... but shouldn't osxbuild.sh build its own KDF framework? Why is there such a dependency conflict?). Anyway I'd remove the home-built Krita as clean as I can and see if the problem goes away, or at least gets more exposed. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420032] Random crashes on Mac (with canvas acceleration off)
https://bugs.kde.org/show_bug.cgi?id=420032 --- Comment #9 from Yu-Hsuan Lai --- Created attachment 127540 --> https://bugs.kde.org/attachment.cgi?id=127540&action=edit same krita instance, contradict info -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420032] Random crashes on Mac (with canvas acceleration off)
https://bugs.kde.org/show_bug.cgi?id=420032 --- Comment #10 from Yu-Hsuan Lai --- Created attachment 127541 --> https://bugs.kde.org/attachment.cgi?id=127541&action=edit same krita instance, contradict info -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420032] Random crashes on Mac (with canvas acceleration off)
https://bugs.kde.org/show_bug.cgi?id=420032 --- Comment #8 from Yu-Hsuan Lai --- (In reply to Boudewijn Rempt from comment #7) > Hm, could it be that there are bits and pieces of your self-compiled Krita > in > /Users/raincole/github/krita_buildroot/i/bin/krita.app/Contents/MacOS/krita > in the path? What we're seeing are crashes deep in Qt itself, when it talks > to its platform plugin. It sounds... likely?! Take a look at these two screenshots. One says my Krita version is 4.2.9, and one says it's 5.0.0-prealpha...! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420032] Random crashes on Mac (with canvas acceleration off)
https://bugs.kde.org/show_bug.cgi?id=420032 --- Comment #6 from Yu-Hsuan Lai --- Attached. I'm not sure if this usage log covers the random crash shown in system.log tho. It might be two different crashes. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420032] Random crashes on Mac (with canvas acceleration off)
https://bugs.kde.org/show_bug.cgi?id=420032 --- Comment #5 from Yu-Hsuan Lai --- Created attachment 127537 --> https://bugs.kde.org/attachment.cgi?id=127537&action=edit System information -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420032] Random crashes on Mac (with canvas acceleration off)
https://bugs.kde.org/show_bug.cgi?id=420032 --- Comment #4 from Yu-Hsuan Lai --- Created attachment 127536 --> https://bugs.kde.org/attachment.cgi?id=127536&action=edit Krita Usage Log This is my Krita Usage Log, but I'm not sure where the useful information is. It crashed once at: KRITA DID NOT CLOSE CORRECTLY SESSION: 14 Apr 2020 12:43:14 +0800. Executing /Applications/krita.app/Contents/MacOS/krita -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420033] New layer number always starts from 1 when editing present PSD files
https://bugs.kde.org/show_bug.cgi?id=420033 --- Comment #3 from Yu-Hsuan Lai --- (In reply to tusooa from comment #2) > (In reply to Yu-Hsuan Lai from comment #0) > > SOFTWARE/OS VERSIONS > > SUMMARY > > I still got random crashes on my Mac, even with canvas acceleration > > disabled. It happens about once a day. > > > > STEPS TO REPRODUCE > > Can't figure out the consistent reproducing steps. It seems pretty random. > > > > > > OBSERVED RESULT > > Crash > > > > EXPECTED RESULT > > Not crash > > > > Also, for the crash thing, I suggest you making a separate bug report for > it. It would be nice if you can also send a crash log. The way to generate > one can be seen at > https://docs.krita.org/en/reference_manual/sharing_krita_logs. > html?highlight=crash#getting-backtrace . Oh I made a separate report: https://bugs.kde.org/show_bug.cgi?id=420032 I just copied paste from it and forget to delete the extra characters. Sorry for the confusion. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420033] New: New layer number always starts from 1 when editing present PSD files
https://bugs.kde.org/show_bug.cgi?id=420033 Bug ID: 420033 Summary: New layer number always starts from 1 when editing present PSD files Product: krita Version: 4.2.9 Platform: macOS Disk Images OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: Layer Stack Assignee: krita-bugs-n...@kde.org Reporter: rainco...@gmail.com Target Milestone: --- Created attachment 127508 --> https://bugs.kde.org/attachment.cgi?id=127508&action=edit When there are more existing layers SUMMARY When editing a PSD file, even with a layer named "Layer 1" presents, the newly added layer is still named "Layer 1" instead of "Layer 2. STEPS TO REPRODUCE 1. Create a PSD file in Photoshop with a layer named "Layer 1" 2. Open said PSD file in Krita 3. Create a new layer OBSERVED RESULT The new layer is named "Layer 1" too. EXPECTED RESULT The new layer should be named "Layer 2". SOFTWARE/OS VERSIONS SUMMARY I still got random crashes on my Mac, even with canvas acceleration disabled. It happens about once a day. STEPS TO REPRODUCE Can't figure out the consistent reproducing steps. It seems pretty random. OBSERVED RESULT Crash EXPECTED RESULT Not crash SOFTWARE/OS VERSIONS macOS: 10.14.6 Krita: 4.9.2 ADDITIONAL INFORMATION See attachment -- You are receiving this mail because: You are watching all bug changes.
