https://bugs.kde.org/show_bug.cgi?id=445502
M changed:
What|Removed |Added
CC||manuel.snudl.zeidler@gmail
https://bugs.kde.org/show_bug.cgi?id=445502
--- Comment #9 from M ---
Ah okay, thanks for the quick info. You don't need an extra bug report I take
it?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=455531
Bug ID: 455531
Summary: Special Window Settings & Virtual Desktops
Product: kwin
Version: 5.25.0
Platform: Archlinux Packages
OS: Linux
Status: REPORTED
Severity
https://bugs.kde.org/show_bug.cgi?id=485276
Bug ID: 485276
Summary: std::optional use: "Conditional jump or move depends
on uninitialised value(s)" (clang)
Classification: Developer tools
Product: valgrind
Version: unspecified
https://bugs.kde.org/show_bug.cgi?id=472329
m changed:
What|Removed |Added
Version|3.21.0 |3.22.0
Summary|std::optional use: |std
https://bugs.kde.org/show_bug.cgi?id=485276
m changed:
What|Removed |Added
Summary|std::optional use: |std::optional use:
|"Conditional ju
https://bugs.kde.org/show_bug.cgi?id=485276
--- Comment #1 from m ---
Forgot to mention that O1 can be used instead of O2 as a workaround, or
clang-16 or earlier should also work as a workaround.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=486764
Bug ID: 486764
Summary: Thai numerical instead of Arabic. We don't normally
use this number in daily use. I tried change the
Windows format and Location and Region already.
Classification
https://bugs.kde.org/show_bug.cgi?id=482365
M changed:
What|Removed |Added
CC||matias...@gmail.com
--- Comment #4 from M ---
I can
https://bugs.kde.org/show_bug.cgi?id=437429
--- Comment #4 from M ---
Created attachment 141363
--> https://bugs.kde.org/attachment.cgi?id=141363&action=edit
palette display mismatch
That is odd. I'm using a nightly build for Windows now from a few days ago (git
6ca8117) and s
https://bugs.kde.org/show_bug.cgi?id=445502
--- Comment #10 from M ---
I can confirm the bug I had is resolved now as well, thank you.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=39
Bug ID: 39
Summary: Floating-point HDR colors get clipped from painting,
layer blending or color space conversion
Product: krita
Version: git master (please specify the git hash!)
https://bugs.kde.org/show_bug.cgi?id=437429
M changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|FIXED
https://bugs.kde.org/show_bug.cgi?id=39
--- Comment #3 from M ---
Right, so I did some more testing. First, I could not reproduce the problem
that basic blending operation I know can algorithmically handle HDR color
values would clip them, such as Addition, or Multiply and Normal with values
https://bugs.kde.org/show_bug.cgi?id=373897
M changed:
What|Removed |Added
CC||manuel.snudl.zeidler@gmail
https://bugs.kde.org/show_bug.cgi?id=479593
Bug ID: 479593
Summary: Smart Patch
Classification: Applications
Product: krita
Version: 5.1.5
Platform: Other
OS: Other
Status: REPORTED
Severity: normal
https://bugs.kde.org/show_bug.cgi?id=472329
--- Comment #3 from m ---
I can reduce the test-case further, replacing the map with set, and dropping
the lambda wrapper. However, further reductions easily cause the optimizer to
eat all code before it gets compiled into the binary. Currently I have
https://bugs.kde.org/show_bug.cgi?id=472329
--- Comment #4 from m ---
Ok, the pair can be replaced by int64_t, but that is it so far:
```cpp
#include
#include
#include
#include
#include
void foo(std::optional f) {
std::cout << (f ? *f : 0) << std::endl;
std::set test;
te
https://bugs.kde.org/show_bug.cgi?id=463514
m changed:
What|Removed |Added
CC||kde.si...@dralias.com
--- Comment #8 from m ---
Is this
https://bugs.kde.org/show_bug.cgi?id=362680
m changed:
What|Removed |Added
Version|3.10.0 |3.21.0
CC
https://bugs.kde.org/show_bug.cgi?id=463514
m changed:
What|Removed |Added
Status|REPORTED|NEEDSINFO
Resolution
https://bugs.kde.org/show_bug.cgi?id=472219
m changed:
What|Removed |Added
CC||kde.si...@dralias.com
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=472329
Bug ID: 472329
Summary: std::optional use: "Conditional jump or move depends
on uninitialised value(s)"
Classification: Developer tools
Product: valgrind
Version: 3.21.0
Platf
https://bugs.kde.org/show_bug.cgi?id=472329
--- Comment #1 from m ---
Apologies, the cpp was missing the last line:
int main() { foo(std::nullopt); }
```
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=447464
Bug ID: 447464
Summary: Gradient stops in vector tool don't work
Product: krita
Version: 5.0.0
Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=408099
M changed:
What|Removed |Added
CC||manuel.snudl.zeidler@gmail
https://bugs.kde.org/show_bug.cgi?id=417792
M changed:
What|Removed |Added
CC||manuel.snudl.zeidler@gmail
https://bugs.kde.org/show_bug.cgi?id=437415
Bug ID: 437415
Summary: 2 Point Perspective assistant can't be hidden through
View > Show Painting Assistants
Product: krita
Version: nightly build (please specify the git hash!)
https://bugs.kde.org/show_bug.cgi?id=437429
Bug ID: 437429
Summary: Broken color display in the Palette docker with an
active OCIO config
Product: krita
Version: nightly build (please specify the git hash!)
Platform: Other
https://bugs.kde.org/show_bug.cgi?id=437429
--- Comment #1 from M ---
Created attachment 138627
--> https://bugs.kde.org/attachment.cgi?id=138627&action=edit
palette display comparison
And a screenshot comparison.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=405691
--- Comment #11 from M ---
As an update, I changed to a PRIME config for GPU switching on this same
hardware over a year ago, as that is now the much more officially supported and
less hacky way to switch between GPUs. I set Krita to start with prime
https://bugs.kde.org/show_bug.cgi?id=489404
M changed:
What|Removed |Added
CC||matias...@gmail.com
--- Comment #2 from M ---
I can
https://bugs.kde.org/show_bug.cgi?id=407665
M changed:
What|Removed |Added
CC||manuel.snudl.zeidler@gmail
https://bugs.kde.org/show_bug.cgi?id=407877
M changed:
What|Removed |Added
CC||manuel.snudl.zeidler@gmail
https://bugs.kde.org/show_bug.cgi?id=407877
--- Comment #2 from M ---
Sorry, wrong git hash. Correct is (git 45bdec0).
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=408427
M changed:
What|Removed |Added
CC||manuel.snudl.zeidler@gmail
https://bugs.kde.org/show_bug.cgi?id=408032
M changed:
What|Removed |Added
CC||manuel.snudl.zeidler@gmail
https://bugs.kde.org/show_bug.cgi?id=408856
M changed:
What|Removed |Added
CC||manuel.snudl.zeidler@gmail
https://bugs.kde.org/show_bug.cgi?id=408927
Bug ID: 408927
Summary: Segmentation fault when opening this file - with
backtrace
Product: krita
Version: git master
Platform: Manjaro
OS: Linux
Statu
https://bugs.kde.org/show_bug.cgi?id=408927
--- Comment #1 from M ---
Created attachment 121015
--> https://bugs.kde.org/attachment.cgi?id=121015&action=edit
gdb backtrace
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=408938
M changed:
What|Removed |Added
CC||manuel.snudl.zeidler@gmail
https://bugs.kde.org/show_bug.cgi?id=408927
--- Comment #2 from M ---
Reference images seem to be the culprit, when all are removed it loads fine.
Afterwards I can readd a reference image to the document, but when I close it
and try to open again the same crash occurs.
Same result also with the
https://bugs.kde.org/show_bug.cgi?id=409543
M changed:
What|Removed |Added
CC||manuel.snudl.zeidler@gmail
https://bugs.kde.org/show_bug.cgi?id=412761
M changed:
What|Removed |Added
Status|REPORTED|RESOLVED
CC
https://bugs.kde.org/show_bug.cgi?id=402831
M changed:
What|Removed |Added
CC||acc4commissi...@gmail.com
--- Comment #8 from M
https://bugs.kde.org/show_bug.cgi?id=412804
Bug ID: 412804
Summary: Crash when using the Magnetic Selection Tool
Product: krita
Version: git master
Platform: Other
OS: Linux
Status: REPORTED
Severity: norm
https://bugs.kde.org/show_bug.cgi?id=412804
--- Comment #1 from M ---
Created attachment 123120
--> https://bugs.kde.org/attachment.cgi?id=123120&action=edit
gdb backtrace
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=412804
--- Comment #2 from M ---
Oh, I should add I left all the default values in the tool options.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=412982
Bug ID: 412982
Summary: Crash when opening attached document
Product: krita
Version: nightly build (please specify the git hash!)
Platform: Other
OS: Linux
Status: REPORTE
https://bugs.kde.org/show_bug.cgi?id=412982
--- Comment #1 from M ---
Created attachment 123211
--> https://bugs.kde.org/attachment.cgi?id=123211&action=edit
GDB backtrace
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=412896
M changed:
What|Removed |Added
CC||manuel.snudl.zeidler@gmail
https://bugs.kde.org/show_bug.cgi?id=412896
--- Comment #4 from M ---
No, I didn't. This can happen on the first or second anchor, before the loop is
closable.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=413668
M changed:
What|Removed |Added
Ever confirmed|0 |1
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=413668
--- Comment #3 from M ---
It looks like there is a mismatch in the active preview of the Transform Tool.
I can click and press ESC repeatedly on the previous 1-pixel-off transform
result and see that the corner handles and image preview align exactly
https://bugs.kde.org/show_bug.cgi?id=406373
M changed:
What|Removed |Added
CC||manuel.snudl.zeidler@gmail
https://bugs.kde.org/show_bug.cgi?id=406250
--- Comment #5 from M ---
Created attachment 119321
--> https://bugs.kde.org/attachment.cgi?id=119321&action=edit
file:///home/snu/gdb output.txt
Here you go, this is everything from the beginning. The backtrace starts at
line 703.
--
https://bugs.kde.org/show_bug.cgi?id=404597
--- Comment #6 from M ---
If I remember correctly I was updating the appimage every few days before I
reported this on February 20, shortly after I first noticed it.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=411917
Bug ID: 411917
Summary: Filter brush with Color Adjustment freezes Krita
Product: krita
Version: git master
Platform: Manjaro
OS: Linux
Status: REPORTED
Severity
https://bugs.kde.org/show_bug.cgi?id=411932
Bug ID: 411932
Summary: Instant preview can turn off permanently
Product: krita
Version: git master
Platform: Manjaro
OS: Linux
Status: REPORTED
Severity: minor
https://bugs.kde.org/show_bug.cgi?id=410158
--- Comment #15 from M ---
I finished bisecting when the slowdown first started, the result is:
commit bbc0f80732afbf0cb36ccdf5fd6b672dd15712a6
Author: Dmitry Kazakov
Date: Fri Jul 12 20:02:22 2019 +0300
Refactor signal compressor to have
https://bugs.kde.org/show_bug.cgi?id=411971
Bug ID: 411971
Summary: Linked perspective assistants distort after image
transformation
Product: krita
Version: git master
Platform: Manjaro
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=411917
--- Comment #2 from M ---
That's strange, it still happens on my system with master (git 59d8e62) and the
newest Next AppImage (git a76f4c3). I checked multiple times, it was
reproducible every try.
--
You are receiving this mail because:
Yo
https://bugs.kde.org/show_bug.cgi?id=411917
--- Comment #4 from M ---
For the GDB backtrace above I had use DISPLAY=:0 gdb krita (thanks to Dmitry
for trick) from a virtual terminal, otherwise the whole session would stay
frozen, correct. Same output from the build directory executable. What
https://bugs.kde.org/show_bug.cgi?id=411917
--- Comment #6 from M ---
Created attachment 122790
--> https://bugs.kde.org/attachment.cgi?id=122790&action=edit
Backtrace from debug build
My mistake, that was a backtrace from the distro package. Here's the output
from the actua
https://bugs.kde.org/show_bug.cgi?id=412323
Bug ID: 412323
Summary: Still-frame of last used brush shown instead of "No
Preview for this engine"
Product: krita
Version: git master
Platform: Manjaro
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=402831
M changed:
What|Removed |Added
CC||manuel.snudl.zeidler@gmail
https://bugs.kde.org/show_bug.cgi?id=402831
--- Comment #7 from M ---
Comparing the 4.2.5 appimage to master - Auto tips have really regressed in
performance but that bitmap brush tip with the complex outline is similarly
sluggish to move, so the latter is probably not relevant to this bug
https://bugs.kde.org/show_bug.cgi?id=412491
Bug ID: 412491
Summary: Color Adjustment curves can give incorrect result
Product: krita
Version: git master
Platform: Manjaro
OS: Linux
Status: REPORTED
Severit
https://bugs.kde.org/show_bug.cgi?id=412492
Bug ID: 412492
Summary: Visible tiling artifacts with Mean Removal and Sharpen
as Filter Layer or Mask
Product: krita
Version: git master
Platform: Manjaro
OS: Lin
https://bugs.kde.org/show_bug.cgi?id=412491
--- Comment #2 from M ---
Created attachment 122970
--> https://bugs.kde.org/attachment.cgi?id=122970&action=edit
Test file with buggy filter
Here you go. The top layer is the Color Adjustment, and despite having crushed
RGBA towards the mid
https://bugs.kde.org/show_bug.cgi?id=412651
Bug ID: 412651
Summary: File overwrite warning can be skipped
Product: krita
Version: git master
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
https://bugs.kde.org/show_bug.cgi?id=412656
M changed:
What|Removed |Added
CC||manuel.snudl.zeidler@gmail
https://bugs.kde.org/show_bug.cgi?id=410158
M changed:
What|Removed |Added
CC||manuel.snudl.zeidler@gmail
https://bugs.kde.org/show_bug.cgi?id=405691
--- Comment #9 from M ---
Good reminder, optirun doesn't bypass the issue anymore for me either since an
update several months ago.
My workaround is to start a separate X session with the nvidia-xrun script, in
case I need the Nvidia GPU.
--
Yo
https://bugs.kde.org/show_bug.cgi?id=408015
M changed:
What|Removed |Added
CC||manuel.snudl.zeidler@gmail
https://bugs.kde.org/show_bug.cgi?id=410583
M changed:
What|Removed |Added
Ever confirmed|0 |1
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=404597
Bug ID: 404597
Summary: Jumpy, unpredictable zoom behavior right after canvas
rotation
Product: krita
Version: nightly build (please specify the git hash!)
Platform: Other
https://bugs.kde.org/show_bug.cgi?id=404597
M changed:
What|Removed |Added
Platform|Other |Manjaro
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=404601
Bug ID: 404601
Summary: Tilt input on rotation reverses on mirrored canvas
Product: krita
Version: nightly build (please specify the git hash!)
Platform: Manjaro
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=408015
--- Comment #24 from M ---
Hmm, I'm on Manjaro too and like I said ever since the commit I can use the
global menu again without issues.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=410583
M changed:
What|Removed |Added
Resolution|--- |FIXED
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=397559
M changed:
What|Removed |Added
CC||manuel.snudl.zeidler@gmail
https://bugs.kde.org/show_bug.cgi?id=389022
M changed:
What|Removed |Added
CC||manuel.snudl.zeidler@gmail
https://bugs.kde.org/show_bug.cgi?id=405691
Bug ID: 405691
Summary: Screen flickering in newest 4.2.0 when running through
primusrun
Product: krita
Version: nightly build (please specify the git hash!)
Platform: Manjaro
https://bugs.kde.org/show_bug.cgi?id=405693
Bug ID: 405693
Summary: PNG Brush tips are suddenly being recognized as GBR
format instead of masks
Product: krita
Version: nightly build (please specify the git hash!)
Platform:
https://bugs.kde.org/show_bug.cgi?id=405693
--- Comment #2 from M ---
Created attachment 118948
--> https://bugs.kde.org/attachment.cgi?id=118948&action=edit
Converted from SVG to PNG in Inkscape
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=405693
--- Comment #3 from M ---
Created attachment 118949
--> https://bugs.kde.org/attachment.cgi?id=118949&action=edit
Extracted from PSD layer
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=405693
--- Comment #4 from M ---
I added 2 more affected examples, that previously worked. The triangles one was
converted from an SVG in Inkscape, the scale was extracted from a multi layer
PSD with ImageMagick. Maybe it helps spot some pattern.
--
You are
https://bugs.kde.org/show_bug.cgi?id=405693
M changed:
What|Removed |Added
Attachment #118948|Converted from SVG to PNG |Converted from SVG to PNG
description|in Inkscape
https://bugs.kde.org/show_bug.cgi?id=404935
M changed:
What|Removed |Added
CC||manuel.snudl.zeidler@gmail
https://bugs.kde.org/show_bug.cgi?id=404935
--- Comment #4 from M ---
Here is the info for the integrated Intel GPU on the same laptop.
Again, the see-through issue remains.
OpenGL Info
Vendor: "Intel Open Source Technology Center"
Renderer: "Mesa DRI Intel(R)
https://bugs.kde.org/show_bug.cgi?id=405540
M changed:
What|Removed |Added
CC||manuel.snudl.zeidler@gmail
https://bugs.kde.org/show_bug.cgi?id=405691
--- Comment #2 from M ---
Yes, unfortunately it still is (git f3858d1), with optirun as well as
primusrun. The flickers only become apparent once a document is opened or
created, and only when there is any movement on screen. No issues with 4.1.8
https://bugs.kde.org/show_bug.cgi?id=405691
--- Comment #6 from M ---
No, the stable appimage seems to be unaffected (4.1.8-9347112). It also doesn't
produce those messages in the terminal.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=406250
Bug ID: 406250
Summary: Color space conversion with clone layer crashes - only
in specific circumstances
Product: krita
Version: unspecified
Platform: Manjaro
OS:
https://bugs.kde.org/show_bug.cgi?id=406250
--- Comment #1 from M ---
And this the last terminal output for 4.1.8:
ASSERT (krita): "0 && "sanity check failed: the tile has already been
removed!"" in file
/build/krita/src/krita-4.1.8/libs/image/tiles3/KisTiledExtent
https://bugs.kde.org/show_bug.cgi?id=406250
--- Comment #3 from M ---
If you can try the same steps in the pre-alpha with a filter layer instead of a
clone layer (for example color adjustment curves). That seems to hang and crash
for me almost always, too. In 4.1.8 I wasn't able to prov
https://bugs.kde.org/show_bug.cgi?id=420260
--- Comment #8 from M ---
Yes, thank you. I wanted to add that this crash was still happening a few weeks
ago, but with my most recent build and AppImage from yesterday I can open
documents without issue. It had vanished and reappeared before, so I&#
https://bugs.kde.org/show_bug.cgi?id=420260
--- Comment #9 from M ---
Never mind, updated my build and the crash on opening documents returned. :D
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=417667
M changed:
What|Removed |Added
Resolution|WORKSFORME |---
Status|RESOLVED
1 - 100 of 1788 matches
Mail list logo
