[krita] [Bug 445502] KPL palettes fail to open or import
https://bugs.kde.org/show_bug.cgi?id=445502 M changed: What|Removed |Added CC||manuel.snudl.zeidler@gmail. ||com --- Comment #7 from M --- Created attachment 146631 --> https://bugs.kde.org/attachment.cgi?id=146631&action=edit KPL palette failing to load This bug may need to be reopened. I am currently running into the issue with this sceneLinear KPL, I'll add it as an attachment here. I'm using the newest Next Nightly (git e2673ac) on Windows and don't remember encountering this problem on the previous installed build I had from about 2 months ago. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 445502] KPL palettes fail to open or import
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.
[kwin] [Bug 455531] New: Special Window Settings & Virtual Desktops
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: normal Priority: NOR Component: rules Assignee: kwin-bugs-n...@kde.org Reporter: butmon...@gmail.com CC: isma...@gmail.com Target Milestone: --- SUMMARY I have 6 Virtual Desktops, with 1 or more Auto-Start apps on each, some have No Border, all have Size, Position, Virtual Desktop set in Special Window Settings. Prior to 5.25.0 they would all load in their correct positions on boot, but now 1 window (usually Konsole, but not exclusive) will appear on every Virtual Desktop with a lag of ~1 second when switching Virtual Desktops, until the app is closed and restarted. STEPS TO REPRODUCE 1. Set up windows as above. 2. Reboot. 3. Close rogue app. OBSERVED RESULT 1 App will appear on all desktops after ~1sec of switching, despite being set to 1 desktop. EXPECTED RESULT Apps should only be on Virtual Desktop they are set to, as prior to 5.25.0 SOFTWARE/OS VERSIONS Windows: No macOS: No Linux/KDE Plasma: Garuda KDE Lite (Arch) (available in About System) KDE Plasma Version: Plasma 5.25.0 (Wayland) KDE Frameworks Version: 5.95.0 Qt Version: 5.15.4 ADDITIONAL INFORMATION Kernel - Linux 5.18.3-arch1-1 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 485276] New: std::optional use: "Conditional jump or move depends on uninitialised value(s)" (clang)
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
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: memcheck
Assignee: jsew...@acm.org
Reporter: kde.si...@dralias.com
Target Milestone: ---
Similar to https://bugs.kde.org/show_bug.cgi?id=472329
Steps to reproduce with clang-18:
# batcat main.cpp dummy.* && clang++-18 -std=c++17 -g -O2 -I. main.cpp
dummy.cpp -o /tmp/exe && valgrind /tmp/exe
│ File: main.cpp
1 │ #include
2 │
3 │ #include
4 │ #include
5 │
6 │ static std::set empty_set;
7 │
8 │ std::optional static none()
9 │ {
10 │ std::optional maybe;
11 │ {
12 │ for (const auto& a : empty_set) {
13 │ if (empty_set.size() > 10) {
14 │ maybe.emplace(dummy{});
15 │ }
16 │ }
17 │ }
18 │ return maybe;
19 │ }
20 │
21 │ dummy dummy_or_default()
22 │ {
23 │ return none().value_or(dummy{});
24 │ }
25 │
26 │ int main()
27 │ {
28 │ dummy_or_default();
29 │ }
│ File: dummy.cpp
1 │ #include
2 │
3 │ dummy::dummy() = default;
│ File: dummy.h
1 │ #include
2 │
3 │ struct dummy {
4 │ char* ptr{};
5 │
6 │ unsigned zero = 0;
7 │ bool hp() const { return zero > 0; }
8 │
9 │ dummy();
10 │
11 │ ~dummy()
12 │ {
13 │ if (hp()) std::free(ptr);
14 │ }
15 │ };
==73841== Memcheck, a memory error detector
==73841== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al.
==73841== Using Valgrind-3.22.0 and LibVEX; rerun with -h for copyright info
==73841== Command: /tmp/exe
==73841==
==73841== Conditional jump or move depends on uninitialised value(s)
==73841==at 0x108BB8: _M_reset (optional:317)
==73841==by 0x108BB8: ~_Optional_payload (optional:441)
==73841==by 0x108BB8: ~_Optional_base (optional:512)
==73841==by 0x108BB8: dummy_or_default() (???:23)
==73841==by 0x108C27: main (main.cpp:28)
==73841==
==73841==
==73841== HEAP SUMMARY:
==73841== in use at exit: 0 bytes in 0 blocks
==73841== total heap usage: 1 allocs, 1 frees, 73,728 bytes allocated
==73841==
==73841== All heap blocks were freed -- no leaks are possible
==73841==
==73841== Use --track-origins=yes to see where uninitialised values come from
==73841== For lists of detected and suppressed errors, rerun with: -s
==73841== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 472329] std::optional use: "Conditional jump or move depends on uninitialised value(s)" (g++)
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::optional use: |"Conditional jump or move |"Conditional jump or move |depends on uninitialised|depends on uninitialised |value(s)" |value(s)" (g++) -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 485276] std::optional use: "Conditional jump or move depends on uninitialised value(s)" (clang) aarch64
https://bugs.kde.org/show_bug.cgi?id=485276 m changed: What|Removed |Added Summary|std::optional use: |std::optional use: |"Conditional jump or move |"Conditional jump or move |depends on uninitialised|depends on uninitialised |value(s)" (clang) |value(s)" (clang) aarch64 Version|unspecified |3.22.0 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 485276] std::optional use: "Conditional jump or move depends on uninitialised value(s)" (clang) aarch64
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.
[krita] [Bug 486764] New: 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.
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: Applications Product: krita Version: 5.2.2 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: tap.m.eenam...@gmail.com Target Milestone: --- Created attachment 169291 --> https://bugs.kde.org/attachment.cgi?id=169291&action=edit 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. 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. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 482365] Crash
https://bugs.kde.org/show_bug.cgi?id=482365 M changed: What|Removed |Added CC||matias...@gmail.com --- Comment #4 from M --- I can confirm that loading the provided webp file and then trying to save it as webp (default settings) results in a crash. Reproducible every time. I'm on Windows 10. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 437429] Broken color display in the Palette docker with an active OCIO config
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 still get the same issue. I also removed the kritarc and kritadisplayrc files and the resources folder to start with the default config, but no change from that either. New screenshot attached. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 445502] KPL palettes fail to open or import
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.
[krita] [Bug 444439] New: Floating-point HDR colors get clipped from painting, layer blending or color space conversion
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!) Platform: Compiled Sources OS: All Status: REPORTED Severity: normal Priority: NOR Component: Color models Assignee: krita-bugs-n...@kde.org Reporter: manuel.snudl.zeid...@gmail.com Target Milestone: --- SUMMARY I'm trying the newest Nightly e2a04dd823 on Windows and it seems there are now several problems with clipping HDR colors. If the document is in 32-bit float and uses any gamut other than the default sRGB-g10, it's not possible to get color values above 1.0 in any color channel anymore, either from paint brushes or stacking layers in Addition blend mode. If the document is converted to a different profile like sRGB-srgbtrc or ACEScg-g10, the colors also get clipped to a max of 1.0 in the process. Additionally, very saturated high-brightness colors get visually shifted in the conversion. These problems don't seem to happen with 16-bit float, but converting to 8 or 16-bit integer will also result in those color shifts, so it's not even possible to guarantee the visual appearance of the image for export in an SDR format anymore. STEPS TO REPRODUCE Conversion: 1. Create a document in 32-bit float and default sRGB-g10 2. Paint with a brush set to Addition, or stack layers in Addition mode 3. Use Image > Convert Image Color Space and choose a different profile 4. Check the resulting color channel values from the canvas Blending: 1. Create a document in 32-bit float, choose a different profile than sRGB-g10 2. Paint with a brush set to Addition, or stack layers in Addition mode 3. Merge and check the resulting color channel values from the canvas OBSERVED RESULT Loss of color information, potential visual shifts. EXPECTED RESULT Retention of the HDR colors. SOFTWARE/OS VERSIONS Krita 5.1.0-prealpha (git e2a04dd) on Windows 10 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 437429] Broken color display in the Palette docker with an active OCIO config
https://bugs.kde.org/show_bug.cgi?id=437429 M changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #17 from M --- So I think I need to reopen this report. I'm trying the newest Nightly e2a04dd823 on Windows and the same display issue is still present. There are now more general issues with floating-point colors, I put that in a new bug report since I don't know how much it relates to this report. https://bugs.kde.org/show_bug.cgi?id=39 Picking a color from an HDR palette also seems to be extra broken on 32-bit float documents, if it uses a gamut other than sRGB-g10. Whether OCIO is activated or not, the picked color is a tone-mapped version of the original color value. When picking the painted colors from the canvas they never go above 1.0, and it's immediately visible that they're not HDR with ACES or Filmic active. This problem doesn't occur with 16-bit float. Strangely, the Specific Color Selector also displays the same wrong tone-mapped values after selecting a color patch from the palette if it's set to 32-bit float and a different gamut from sRGB-g10, but not for 16-bit. Lastly, very minor UI complaint: The new version info text on the bottom of the LUT docker is quite long, at least on Windows, and increases its minimum width. So if the LUT docker is in a column with other dockers I can't shrink that as much as I previously could. That's all. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 444439] Floating-point HDR colors get clipped from painting, layer blending or color space conversion
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 above 1.0. I found is that the Specific Color Selector could show the values clipped at 1.0, but the Foreground color selector window shows the correct channel values, and that picking an HDR color from a palette would also paint a clipped or somehow tone-mapped version of the color. That would tie back to https://bugs.kde.org/show_bug.cgi?id=437429 So unless I can reproduce what I thought was happening initially, I'm assuming I was mislead by the number readouts and those blending modes are not affected. What I can confirm however is that certain color space conversions will clip color values to 1.0, possibly between linear and non-linear profiles. This is not exclusive to Krita 5.1, I can reproduce it the same way in 4.4.8 on Windows, but curiously 4.4.8 on Linux doesn't seem to have the issue. It might be a Windows specific bug, but not a regression to Krita 5.1. To reproduce on a Windows build: 1. Create a document in 16 or 32-bit float and ACEScg-g10 2. Produce some HDR color values on the canvas and merge down all layers 3. Verify from the Foreground color picker that any color channel is way above 1.0 4. Use Image > Convert Image Color Space. Leave the bit depth, choose sRGB-srgbtrc (not linear). Rendering intent can optionally be relative colorimetric 5. Check the colors on canvas again in the Foreground color picker The colors on canvas should now be clipped at 1.0. Some 16-bit float conversions seem to be more robust, but most combinations will still result in clipping on my end. You can also try the conversion result of negative float colors from Subtract. Though none of the color pickers seem to indicate negative values. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 373897] Gwenview rolls image slightly when rotating JPEG image (some leftmost pixels are moved rightmost)
https://bugs.kde.org/show_bug.cgi?id=373897 M changed: What|Removed |Added CC||manuel.snudl.zeidler@gmail. ||com --- Comment #7 from M --- Created attachment 140451 --> https://bugs.kde.org/attachment.cgi?id=140451&action=edit JPEG photo where this issue occurs I believe I'm running into the same issue. When using the Rotate Left or Rotate Right buttons on certain JPEGs, the saved image has 8 pixel rows shifted to the opposite edge upon reopening. I'm using Manjaro with the optional kde-unstable repo packages, Gwenview is currently versioned at 21.04.3.r6650.gb292af50-1. I'm attaching a photo that causes the problem on my end, see if you can reproduce it. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 479593] New: Smart Patch
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 Priority: NOR Component: Tools Assignee: krita-bugs-n...@kde.org Reporter: mdh...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Use Smart Patch heal 2. crashes app 3. running on Chrome Laptop OBSERVED RESULT paused, put up idle icon failed to complete, could not go back EXPECTED RESULT functionality SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 472329] std::optional use: "Conditional jump or move depends on uninitialised value(s)"
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:
```cpp
#include
#include
#include
#include
#include
void foo(std::optional f) {
std::cout << (f ? *f : 0) << std::endl;
std::set> test;
test.emplace(std::pair{0, 0});
auto it{test.begin()};
while (it != test.end()) {
int64_t b{it->second};
if (f && *f != b) {
it++;
break;
}
std::cout << "";
it++;
}
}
int main() { foo(std::nullopt); }
```
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 472329] std::optional use: "Conditional jump or move depends on uninitialised value(s)"
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;
test.emplace(0);
auto it{test.begin()};
while (it != test.end()) {
int64_t b{*it};
if (f && *f != b) {
it++;
break;
}
std::cout << "";
it++;
}
}
int main() { foo(std::nullopt); }
```
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 463514] Valgrind not detecting the leaks.
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 still an issue? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 362680] --error-exitcode not honored when file descriptor leaks are found
https://bugs.kde.org/show_bug.cgi?id=362680
m changed:
What|Removed |Added
Version|3.10.0 |3.21.0
CC||kde.si...@dralias.com
--- Comment #2 from m ---
Just checked that this is still an issue with 3.21:
$ cat /tmp/leak.c && gcc -g -o /tmp/leak.exe /tmp/leak.c && valgrind --version
&& valgrind --quiet --error-exitcode=2 --track-fds=yes /tmp/leak.exe ; echo $?
#include
int main() { fopen("/tmp/leak.c", "r"); }
valgrind-3.21.0
==1538349== FILE DESCRIPTORS: 4 open (3 std) at exit.
==1538349== Open file descriptor 3: /tmp/leak.c
==1538349==at 0x4967F35: open (open64.c:41)
==1538349==by 0x48F0705: _IO_file_open (fileops.c:188)
==1538349==by 0x48F08CA: _IO_file_fopen@@GLIBC_2.2.5 (fileops.c:280)
==1538349==by 0x48E4BCC: __fopen_internal (iofopen.c:75)
==1538349==by 0x401138: main (leak.c:2)
==1538349==
==1538349==
0
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 463514] Valgrind not detecting the leaks.
https://bugs.kde.org/show_bug.cgi?id=463514 m changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |NOT A BUG --- Comment #10 from m --- Ok, if the issue is not-a-bug/inactive/unreproducible mind closing it for now to avoid it showing up in the search results of open issues? If there is a minimal code to reproduce the issue reliably on the latest version of valgrind, I guess it can be reopened or a new issue opened. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 472219] Syscall param ppoll(ufds.events) points to uninitialised byte(s)
https://bugs.kde.org/show_bug.cgi?id=472219 m changed: What|Removed |Added CC||kde.si...@dralias.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 472329] New: std::optional use: "Conditional jump or move depends on uninitialised value(s)"
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
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: memcheck
Assignee: jsew...@acm.org
Reporter: kde.si...@dralias.com
Target Milestone: ---
Steps to reproduce with the cpp file:
```cpp
#include
#include
#include
#include
#include
void foo(std::optional f) {
std::cout << (f ? *f : 0) << std::endl;
static std::map> test{[] {
std::map> test;
test.emplace(true, std::pair{0, 0});
return test;
}()};
auto range{test.find(true)};
while (range != test.end()) {
auto [a, b]{range->second};
if (f && *f != a) {
range++;
continue;
}
std::cout << (a ? std::string{} : std::string{""}) << std::endl;
range++;
}
}
```
And then compilation with g++ (clang++ doesn't reproduce):
```
g++ /tmp/a.cpp -O1 -g -o /tmp/exe && valgrind --quiet /tmp/exe
```
(g++-12.3 needs -O2, and g++-13 needs -O1)
Output:
```
0
==2753084== Conditional jump or move depends on uninitialised value(s)
==2753084==at 0x4014CB: foo(std::optional) (a.cpp:16)
==2753084==by 0x401542: main (a.cpp:24)
==2753084==
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 472329] std::optional use: "Conditional jump or move depends on uninitialised value(s)"
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.
[krita] [Bug 447464] New: Gradient stops in vector tool don't work
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 Severity: normal Priority: NOR Component: Tools/Vector Assignee: krita-bugs-n...@kde.org Reporter: gett...@autistici.org Target Milestone: --- Created attachment 144828 --> https://bugs.kde.org/attachment.cgi?id=144828&action=edit video of the bug SUMMARY Gradient stops in vector tool don't work correctly: - the toggling of the stops don't work correctly with the < and > buttons (first 7 seconds in the video in the attachment) - when editing the second, third, fourth etc. stop, allways the first stop is edited (see last part of the video) STEPS TO REPRODUCE 1. Vector tool -> make polygon 2. set gradient as fill 3. Select stop with arrow ( "<" ">") buttons 4. Edit color of the stop OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: Windows 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408099] SVG File layers are not rendered
https://bugs.kde.org/show_bug.cgi?id=408099 M changed: What|Removed |Added CC||manuel.snudl.zeidler@gmail. ||com --- Comment #3 from M --- No, I can confirm this issue is still present on a Krita 5.1.0 daily build on Windows (git 7af8eaa). You can try https://commons.wikimedia.org/wiki/File:Test.svg. If drag-and-dropped into a document and choosing as File Layer it will appear as a completely transparent layer, if choosing as new Layer or as a Reference Image it renders properly. Also strangely, if choosing the new layer option it takes a solid 10 seconds for the resolution dialog to appear and the Krita window is completely frozen in the meantime. That delay is not present when I try the same thing in 4.4.8, and I don't remember it being a problem in an older 5.1 daily. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 417792] View -> Show Painting Assistants control/toggle can become inverted in its action
https://bugs.kde.org/show_bug.cgi?id=417792 M changed: What|Removed |Added CC||manuel.snudl.zeidler@gmail. ||com --- Comment #2 from M --- To add to this report, View > Show Painting Assistants can also get confused when going between multiple open documents after it was used to hide assistants in one of documents previously. View > Show Assistant Previews seems to remain correctly in sync with the visibility of the helper preview in the current document. View > Show Reference Images works as a global switch across all open documents. Maybe this option could also be changed to work per-document, that would be a bit more useful and consistent in my opinion. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 437415] New: 2 Point Perspective assistant can't be hidden through View > Show Painting Assistants
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!) Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: manuel.snudl.zeid...@gmail.com Target Milestone: --- SUMMARY View > Show Painting Assistants doesn't have an effect on the visibility of the new 2 Point Perspective assistant. STEPS TO REPRODUCE 1. Open a document 2. Add a 2 Point Perspective assistants 3. Toggle View > Show Painting Assistants OBSERVED RESULT The grid lines in 2 Point Perspective assistant cannot be hidden through this menu option, but toggling the eye icon on the little on-canvas menu for each assistant does work. EXPECTED RESULT All the lines tracing the perspective should become hidden, similar to the Vanishing Point or Perspective assistants. SOFTWARE/OS VERSIONS Tested in the 5.0.0-prealpha (git 3d23ca9) AppImage. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 437429] New: Broken color display in the Palette docker with an active OCIO config
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 OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Color models Assignee: krita-bugs-n...@kde.org Reporter: manuel.snudl.zeid...@gmail.com Target Milestone: --- Created attachment 138626 --> https://bugs.kde.org/attachment.cgi?id=138626&action=edit HDR palette SUMMARY I'm noticing that the display of color spots, including floating-point HDR colors, in the Palette docker look very different in the Krita 5 prealpha AppImage compared to Krita 4.4.3, if 1. the document is not in linear sRGB, and 2. a working OCIO config is active in the LUT management docker. I make sure that the color space of the document and the input space in the OCIO config match exactly. In Krita 4.4.3 the palette colors look correct and consistent with every color space that I can find a match for, but Krita 5 only displays them right if the document and OCIO input are (linear gamma) sRGB. The palette color in this case also doesn't match the Specific Color Selector, nor the resulting color on canvas. I always start Krita with LC_ALL=C to avoid the number formatting issue in the OCIO LUTs. STEPS TO REPRODUCE 1. Create or open a document in 16- or 32-bit floating-point, linear sRGB 2. Add an OCIO config like Filmic or ACES in the LUT docker and set the input and display settings correctly 3. Use colors picked from a palette in the Palette docker on canvas and compare their look 4. Convert the document color space to a wide gamut like ACEScg, update the OCIO input space to match it, and compare again OBSERVED RESULT Color spots are not representative of the resulting color on canvas. Even super bright color spots (at float value 16.29 in any channel) appear dimmed in terms of display brightness. EXPECTED RESULT Color spots should match the look on canvas and in the Specific Color Selector like is the case in Krita 4.4.3. SOFTWARE/OS VERSIONS Tested in the 5.0.0-prealpha (git 3d23ca9) AppImage. ADDITIONAL INFORMATION If the OCIO configs I tested with are needed: Filmic - https://github.com/sobotka/filmic-blender ACES - https://github.com/sobotka/ACES-1.2-Displays-Formatted The ACES download is very large because it includes a ton of baked LUTs and ICC profiles. ACES has a lot of input colorspaces and display output options if needed, including HDR10 / HLG display targets. I'll attach the HDR palette I used, which was created by Wolthera, if I'm not mistaken. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 437429] Broken color display in the Palette docker with an active OCIO config
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.
[krita] [Bug 405691] Screen flickering in newest 4.2.0 when running through primusrun
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-run instead and I don't think there was ever any rendering issue since then. The system info output in Krita confirms it's actually using the Nvidia GPU. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 489404] Krita seems to open file as read only
https://bugs.kde.org/show_bug.cgi?id=489404 M changed: What|Removed |Added CC||matias...@gmail.com --- Comment #2 from M --- I can confirm this on Windows 10, it happens when the file is open from explorer, applies to .kra files as well as any other image using this method. Opening Krita first, then dropping the file inside the window, or using the file>open menu doesn't have this issue. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407665] Using selections crashes Krita
https://bugs.kde.org/show_bug.cgi?id=407665 M changed: What|Removed |Added CC||manuel.snudl.zeidler@gmail. ||com --- Comment #2 from M --- My GDB output: [New Thread 0x7fffdc96b700 (LWP 25947)] QObject::startTimer: Timers cannot have negative intervals [New Thread 0x7fffd5b1d700 (LWP 25948)] [New Thread 0x7fffd531c700 (LWP 25949)] /home/snu/Applications/kritadev/install/lib64/krita-python-libs/krita added to PYTHONPATH [New Thread 0x7fffc6ecb700 (LWP 25950)] [New Thread 0x7fffc5ba0700 (LWP 25951)] [New Thread 0x7fffc535f700 (LWP 25952)] [New Thread 0x7fffc4b5e700 (LWP 25953)] [New Thread 0x7fffb7a97700 (LWP 25954)] [New Thread 0x7fffb7296700 (LWP 25955)] [New Thread 0x7fffb6a95700 (LWP 25956)] [New Thread 0x7fffb6294700 (LWP 25957)] [New Thread 0x7fffb5a93700 (LWP 25958)] [New Thread 0x7fffb5292700 (LWP 25959)] [New Thread 0x7fffb4a91700 (LWP 25960)] [New Thread 0x7fff93fff700 (LWP 25961)] [New Thread 0x7fff937fe700 (LWP 25962)] [New Thread 0x7fff92ffd700 (LWP 25963)] [New Thread 0x7fff927fc700 (LWP 25964)] [New Thread 0x7fff91ffb700 (LWP 25965)] [Thread 0x7fff91ffb700 (LWP 25965) exited] [Thread 0x7fff927fc700 (LWP 25964) exited] [Thread 0x7fff92ffd700 (LWP 25963) exited] [Thread 0x7fff937fe700 (LWP 25962) exited] [New Thread 0x7fff92ffd700 (LWP 25966)] [Thread 0x7fff92ffd700 (LWP 25966) exited] [New Thread 0x7fff92ffd700 (LWP 25968)] [Thread 0x7fff92ffd700 (LWP 25968) exited] [New Thread 0x7fff92ffd700 (LWP 25969)] Thread 32 "Thread (pooled)" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fff92ffd700 (LWP 25969)] KisSelection::pixelSelection (this=0x0) at /home/snu/Applications/kritadev/krita/libs/image/kis_selection.cc:203 203 return m_d->pixelSelection; (gdb) thread apply all backtrace Thread 32 (Thread 0x7fff92ffd700 (LWP 25969)): #0 KisSelection::pixelSelection (this=0x0) at /home/snu/Applications/kritadev/krita/libs/image/kis_selection.cc:203 #1 0x76fb37c8 in KisSelectionToolHelper::ClearPixelSelection::paint (this=) at /home/snu/Applications/kritadev/krita/libs/ui/tool/kis_selection_tool_helper.cpp:180 Backtrace stopped: Cannot access memory at address 0x7fff92ffcc58 Thread 25 (Thread 0x7fff93fff700 (LWP 25961)): Python Exception Couldn't get registers: No such process.: Couldn't get registers: No such process. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407877] Layer content not shown when file opened
https://bugs.kde.org/show_bug.cgi?id=407877 M changed: What|Removed |Added CC||manuel.snudl.zeidler@gmail. ||com --- Comment #1 from M --- Can confirm on my system (git ad31625). It happens with every document in LAB color space I tried so far. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407877] Layer content not shown when file opened
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.
[krita] [Bug 408427] Reference images are not supposed to have boolean operations applied to them
https://bugs.kde.org/show_bug.cgi?id=408427 M changed: What|Removed |Added CC||manuel.snudl.zeidler@gmail. ||com --- Comment #1 from M --- Can confirm here, 4.3.0-prealpha (git 81fdaf7). The Group/Ungroup and Logical Operations entries disappear once the selection of ref images has been changed. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408032] [duplicate layer] Krita can't move or transform right after duplicating a layer.
https://bugs.kde.org/show_bug.cgi?id=408032 M changed: What|Removed |Added CC||manuel.snudl.zeidler@gmail. ||com --- Comment #3 from M --- I noticed this too - In the Undo History the Duplicate Nodes step takes several seconds to appear, however if you click on a previous operation in that time span, the new duplication step instantly appears and the layer becomes editable. Pressing Ctrl+Z before it finishes seems to cancel the step entirely however. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408856] My lines are not respect and the pressure doesn't work.
https://bugs.kde.org/show_bug.cgi?id=408856 M changed: What|Removed |Added CC||manuel.snudl.zeidler@gmail. ||com --- Comment #1 from M --- Have you tried switching the tablet input API in Settings > Configure Krita > Tablet Settings and then restarting Krita? Bug reports are not for user support! If you need help with Krita, make a post on the Krita (KDE) forums or on reddit, or you can ask in the developer chat - you'll find the links on the Krita website. If you are entirely sure this is a bug with Krita itself and not the drivers or hardware, you will have to fill out the description template that you left empty. Currently there is no information here that lets the developers know what the problem is. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408927] New: Segmentation fault when opening this file - with backtrace
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 Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: manuel.snudl.zeid...@gmail.com Target Milestone: --- Created attachment 121014 --> https://bugs.kde.org/attachment.cgi?id=121014&action=edit Test .kra file that causes a crash SUMMARY Attempting to normally open the attached .kra file results in Krita master crashing with a segmentation fault - the file opens fine in 4.2.1 (distro package). It only contains a fill layer, a reference image and a few assistants. Strangely enough the canvas acceleration sometimes gets disabled automatically, but the crash happens regardless of it being on or off. STEPS TO REPRODUCE Simply open the attached file in Krita and it should freeze or close completely. SYSTEM INFO Version: 4.3.0-prealpha (git 62e6d33) Languages: en_US Hidpi: true Qt Version (compiled): 5.12.4 Version (loaded): 5.12.4 OS Information Build ABI: x86_64-little_endian-lp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: linux Kernel Version: 5.2.0-2-MANJARO Pretty Productname: Manjaro Linux Product Type: manjaro Product Version: unknown Hardware Information GPU Acceleration: auto Memory: 15950 Mb Number of Cores: 8 Swap Location: /tmp -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408927] Segmentation fault when opening this file - with backtrace
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.
[krita] [Bug 408938] pen pressure not working as it should in only krita. works fine elsewhere.
https://bugs.kde.org/show_bug.cgi?id=408938 M changed: What|Removed |Added CC||manuel.snudl.zeidler@gmail. ||com --- Comment #1 from M --- To clarify - did you also try to switch the tablet API in the Tablet Settings and restarting Krita afterwards? And you say the window gets cut off - does confirming the settings with Alt+O (the letter O) work? Also try disabling hi-dpi support under General > Window. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408927] Segmentation fault when opening this file - with backtrace
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 Next appimage from yesterday. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409543] SIGSEGV build d649293 clicking cancel after warning about linear RGB modes
https://bugs.kde.org/show_bug.cgi?id=409543 M changed: What|Removed |Added CC||manuel.snudl.zeidler@gmail. ||com --- Comment #1 from M --- Can confirm here. Also happens with the profile krita-2.5, lcms sRGB built-in with linear gamma TRC. My gdb output throws the same messages. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412761] Changing brush size with Shift + Drag becomes laggy when the brush size gets big.
https://bugs.kde.org/show_bug.cgi?id=412761 M changed: What|Removed |Added Status|REPORTED|RESOLVED CC||manuel.snudl.zeidler@gmail. ||com Resolution|--- |DUPLICATE --- Comment #2 from M --- *** This bug has been marked as a duplicate of bug 402831 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 402831] Resizing Brush with shift +lmb drag is lagging, and not smooth for various complex brush tips
https://bugs.kde.org/show_bug.cgi?id=402831 M changed: What|Removed |Added CC||acc4commissi...@gmail.com --- Comment #8 from M --- *** Bug 412761 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412804] New: Crash when using the Magnetic Selection Tool
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: normal Priority: NOR Component: Tools/Selection Assignee: krita-bugs-n...@kde.org Reporter: manuel.snudl.zeid...@gmail.com Target Milestone: --- Created attachment 123119 --> https://bugs.kde.org/attachment.cgi?id=123119&action=edit Test file SUMMARY The Magnetic Selection Tool can crash immediately after setting a control point with the attached test file. STEPS TO REPRODUCE 1. Open the test file and choose the the Magnetic Selection Tool 2. Set the initial control point close to the beginning of the stroke in the bottom left OBSERVED RESULT Freeze and crash after trying to place a control point. Depending on where the first control point is set it can happen immediately when placing the first one, or later on. See the attached backtrace. EXPECTED RESULT Normal tool operation. SOFTWARE/OS VERSIONS Tested in build from master (git c870d77) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412804] Crash when using the Magnetic Selection Tool
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.
[krita] [Bug 412804] Crash when using the Magnetic Selection Tool
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.
[krita] [Bug 412982] New: Crash when opening attached document
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: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: manuel.snudl.zeid...@gmail.com Target Milestone: --- Created attachment 123210 --> https://bugs.kde.org/attachment.cgi?id=123210&action=edit Test file SUMMARY Krita crashes as soon as I attempt to open the provided test file with the latest master build. It opens without issue in 4.2.7, older Next AppImage (git 511ecc7), and opened with master build about 3 days ago. SOFTWARE/OS VERSIONS Tested with master (git 8b1ac0f), AppImage (git 511ecc7 from 1. October) and 4.2.7. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412982] Crash when opening attached document
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.
[krita] [Bug 412896] Crash while double clicking and removing a magnetic lasso point/node
https://bugs.kde.org/show_bug.cgi?id=412896 M changed: What|Removed |Added CC||manuel.snudl.zeidler@gmail. ||com --- Comment #2 from M --- Created attachment 123236 --> https://bugs.kde.org/attachment.cgi?id=123236&action=edit GDB backtrace A fairly reliable way to reproduce my crash is to add and remove an anchor point repeatedly, close to an "open" edge in the image similar to the minimal test file I had for the earlier bug report. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412896] Crash while double clicking and removing a magnetic lasso point/node
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.
[krita] [Bug 413668] 1 pixel lines exceed after using Transform tool
https://bugs.kde.org/show_bug.cgi?id=413668 M changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||manuel.snudl.zeidler@gmail. ||com --- Comment #2 from M --- I can reproduce this. At first I thought it was an issue with snapping and zoom level, but even placing the transform handles pixel perfect can result in this 1 pixel overshoot on 1 or more edges after applying the transformation. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413668] 1 pixel lines exceed after using Transform tool
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 with the grid. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406373] Canvas not accepting input when the left/top resize buttons are visible
https://bugs.kde.org/show_bug.cgi?id=406373 M changed: What|Removed |Added CC||manuel.snudl.zeidler@gmail. ||com --- Comment #1 from M --- It happens for me with 4.1.8 and the pre-alpha on Linux, by dragging the canvas scroll bars left or up until the resize indicator appears. This works with mouse/touchpad as well as tablet pen input. Krita Version: 4.1.8 Qt Version (compiled): 5.12.2 Version (loaded): 5.12.2 OS Information Build ABI: x86_64-little_endian-lp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: linux Kernel Version: 5.0.7-1-MANJARO Pretty Productname: Manjaro Linux -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406250] Color space conversion with clone layer crashes - only in specific circumstances
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. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 404597] Jumpy, unpredictable zoom behavior right after canvas rotation
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.
[krita] [Bug 411917] New: Filter brush with Color Adjustment freezes Krita
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: normal Priority: NOR Component: Brush engines Assignee: krita-bugs-n...@kde.org Reporter: manuel.snudl.zeid...@gmail.com Target Milestone: --- Created attachment 122655 --> https://bugs.kde.org/attachment.cgi?id=122655&action=edit gdb backtrace SUMMARY A Filter engine brush set to use Color Adjustment curves causes Krita to freeze, if the document uses LAB or XYZ color spaces. STEPS TO REPRODUCE 1. Create a document in LAB or XYZ color space 2. Open the brush settings and choose a Filter brush preset 3. Change the filter it uses to Color Adjustment (curves) 4. Attempt to modify the curve of any channel OBSERVED RESULT Krita freezes entirely. EXPECTED RESULT The adjustments work normally on the brush like with RGB documents. SOFTWARE/OS VERSIONS Tested in 4.2.6 from distro repository and master (git cb4306b) with the same outcome. ADDITIONAL INFORMATION RGB or CMYK don't seem to cause this issue. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411932] New: Instant preview can turn off permanently
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 Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: manuel.snudl.zeid...@gmail.com Target Milestone: --- SUMMARY After switching to a Filter engine brush, then to another preset, Instant Preview stays off. STEPS TO REPRODUCE 1. Open the Brush settings 2. Enable Instant Preview 3. Select a Filter brush preset 4. Switch to a different brush preset / engine OBSERVED RESULT Instant Preview is now toggled off and has to be reenabled. EXPECTED RESULT Instant Preview only turns off temporarily as long as it cannot be used. SOFTWARE/OS VERSIONS Tested in 4.2.6 and master. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410158] Severe lag in 4.3.0 pre-alpha Brush Editor when adjusting transfer curves
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 better timing properties * before: emits signals with time range [1.0...2.0] * interval * after: emits signals with time range [0.5...1.5] * interval Bascially, now it handles it much better when interval is around 10-20 ms. With the old version it caused KisCanvas2 to drop frames and look ugly when the user pans the canvas. CCBUG:409460 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411971] New: Linked perspective assistants distort after image transformation
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 Status: REPORTED Severity: normal Priority: NOR Component: Tool/Assistants Assignee: krita-bugs-n...@kde.org Reporter: manuel.snudl.zeid...@gmail.com Target Milestone: --- SUMMARY Linked perspective assistants which share an edge get distorted after the image is transformed by scaling, rotating or shearing, or the canvas is resized. STEPS TO REPRODUCE 1. Add a perspective assistant to an open document 2. Drag out one of the edge handles to attach a shared second perspective assistant 3. Optionally add a separate perspective assistant or other assistant types for comparison 4. Use a transform operation from the Image menu, or use Resize Canvas OBSERVED RESULT The linked perspective assistant is distorted, while the other assistants are transformed correctly with the contents of the document. EXPECTED RESULT The linked perspective assistant behaves like the other types, so that it matches the image transformation. SOFTWARE/OS VERSIONS Tested in master (git 68fe323). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411917] Filter brush with Color Adjustment freezes Krita
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: You are watching all bug changes.
[krita] [Bug 411917] Filter brush with Color Adjustment freezes Krita
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 debugging could I do then? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411917] Filter brush with Color Adjustment freezes Krita
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 actual build with CMAKE_BUILD_TYPE Debug and KRITA_DEVS on. Had to figure out why logging didn't work before. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412323] New: Still-frame of last used brush shown instead of "No Preview for this engine"
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 Status: REPORTED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: manuel.snudl.zeid...@gmail.com Target Milestone: --- SUMMARY The stroke preview of the brush editor now stays on the last working brush preview instead of showing the "No Preview for this engine" message for those that don't support it, like the Clone, Quick or Shape engine. This happens in master (git f867486), but not in 4.2.6. STEPS TO REPRODUCE 1. Open the brush settings 2. Switch between presets that generate a stroke preview and one that doesn't OBSERVED RESULT The generated stroke preview of the last working preset stays. EXPECTED RESULT The "No Preview for this engine" message should appear, like in 4.2.6. SOFTWARE/OS VERSIONS Krita master (git f867486) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 402831] Resizing Brush with shift +lmb drag is lagging, and not smooth for various complex brush tips
https://bugs.kde.org/show_bug.cgi?id=402831 M changed: What|Removed |Added CC||manuel.snudl.zeidler@gmail. ||com --- Comment #6 from M --- Can confirm as well. It seems to be more noticable with the Auto tips, but a bitmap tip I tested that generates a very noisy, detailed outline causes severe slowdown and a CPU usage spike (on a single thread) from just moving the brush over the canvas. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 402831] Resizing Brush with shift +lmb drag is lagging, and not smooth for various complex brush tips
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. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412491] New: Color Adjustment curves can give incorrect result
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 Severity: normal Priority: NOR Component: Filters Assignee: krita-bugs-n...@kde.org Reporter: manuel.snudl.zeid...@gmail.com Target Milestone: --- SUMMARY When positioning the end handles of any channel curve so that the numeric values are exactly Input = Output, effectively clipping the output range without changing in-between values, the filter behaves like the curve hasn't been adjusted at all. STEPS TO REPRODUCE 1. Open Filter > Adjust > Color Adjustment curves... and pick any channel 2. Reposition the first end handle of the default linear curve and make sure the value of the Input exactly matches the Output - for example to 127, 127 on an 8-bit image to clip the lower half of the values 3. Add +/- 1 to the input and observe the immediate difference OBSERVED RESULT The adjusted result is identical to the untouched linear curve. EXPECTED RESULT The values beyond the end handles should be clipped in the adjusted image. SOFTWARE/OS VERSIONS Tested in 4.3.0-prealpha (git 511ecc7) and 4.2.6, resulting in the same behavior. ADDITIONAL INFORMATION Inserting additional curve nodes that also conform to Input = Output won't affect the result either. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412492] New: Visible tiling artifacts with Mean Removal and Sharpen as Filter Layer or Mask
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: Linux Status: REPORTED Severity: normal Priority: NOR Component: Filter Layers Assignee: krita-bugs-n...@kde.org Reporter: manuel.snudl.zeid...@gmail.com Target Milestone: --- SUMMARY If the Mean Removal or Sharpen filters are used in a Filter Layer or Filter Mask, they produce visual artifacts in the shape of square tile outlines. STEPS TO REPRODUCE 1. Add a new Filter Layer or Mask 2. Pick Mean Removal or Sharpen from the Enhance category OBSERVED RESULT Visual tiling artifacts appear on the canvas. The artifacts persist when the filter layer is flattened or merged. EXPECTED RESULT No such artifacts. SOFTWARE/OS VERSIONS Tested with 4.3.0-prealpha (git 511ecc7) and 4.2.6. These artifacts only appear in master (both my build and the latest appimage), not in 4.2.6. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412491] Color Adjustment curves can give incorrect result
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 middle and Red towards the brightest values, the image appears unaltered. When you open the layer properties and tweak the curves by a tiny amount, the adjustment turns visible. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412651] New: File overwrite warning can be skipped
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 Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: manuel.snudl.zeid...@gmail.com Target Milestone: --- SUMMARY The warning popup when trying to save a document through Save As... or Export... over an identically named file (+ format) in the folder is skipped if the File name input does not explicitly have the file ending written. This seems to only happen if the native file dialog option under Configure Krita > General > Miscellaneous is disabled. STEPS TO REPRODUCE 1. Make sure the native file dialogs option is disabled 2. Open an image file in Krita and save it into a folder 3. Overwrite it through Save As..., leave the file name unchanged but remove the file ending 4. Change the file format from the Type drop-down and try overwriting that file too OBSERVED RESULT The overwrite warning dialog is skipped. EXPECTED RESULT The overwrite warning should appear just like when the file ending is written out. SOFTWARE/OS VERSIONS Tested in master build (git 9b45d78), AppImage (git 511ecc7) and 4.2.7 from repo, all showing the same behavior. KDE Plasma 5.16.5 + Dolphin ADDITIONAL INFORMATION I'm using Plasma and Dolphin, in case that influences the behavior of the native file dialog. Original context is this reddit topic: https://www.reddit.com/r/krita/comments/dcztyv/krita_does_not_inform_me_there_is_another_file/ -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412656] Cintiq 24 inch can't use Pen after eraser side hits digital display.
https://bugs.kde.org/show_bug.cgi?id=412656 M changed: What|Removed |Added CC||manuel.snudl.zeidler@gmail. ||com --- Comment #1 from M --- Could you check if the issue is that the brush is set to 0% opacity after flipping between pen tips? In which case that ties into this bug https://bugs.kde.org/show_bug.cgi?id=389022 (see the last few comments) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410158] Severe lag in 4.3.0 pre-alpha Brush Editor when adjusting transfer curves
https://bugs.kde.org/show_bug.cgi?id=410158 M changed: What|Removed |Added CC||manuel.snudl.zeidler@gmail. ||com --- Comment #2 from M --- I can confirm this on my master build. Not only the curves are affected, but any slider throughout the brush settings I tested can produce severe slowdown, increasingly so the longer I keep dragging the slider. Maybe it's something to do with signal compressors? Almost any brush preset and engine I tested was affected and I was able to provoke 10+ seconds freezes with a Filter Engine brush. However, the Clone Engine wasn't affected (at least not noticeably), which might be because it doesn't create a preview. In the Brush Tip section I noticed that while moving the sliders with Predefined and Text tips causes the lag, for Auto tips the brush preview only updates once I let go of the slider. Should I create a separate bug report for the described problems? Version: 4.3.0-prealpha (git 600ee12) Languages: en_US Hidpi: true Qt Version (compiled): 5.13.0 Version (loaded): 5.13.0 OS Information Build ABI: x86_64-little_endian-lp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: linux Kernel Version: 5.2.2-1-MANJARO Pretty Productname: Manjaro Linux Product Type: manjaro Product Version: unknown Hardware Information GPU Acceleration: auto Memory: 15950 Mb Number of Cores: 8 Swap Location: /tmp -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405691] Screen flickering in newest 4.2.0 when running through primusrun
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. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408015] Global menu doesn't work
https://bugs.kde.org/show_bug.cgi?id=408015 M changed: What|Removed |Added CC||manuel.snudl.zeidler@gmail. ||com --- Comment #20 from M --- I can confirm it working here too with master and 4.2.5 on Plasma 5.16.4. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410583] Tilt direction stuck on canvas rotation
https://bugs.kde.org/show_bug.cgi?id=410583 M changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||manuel.snudl.zeidler@gmail. ||com --- Comment #1 from M --- I can confirm this here on master (git 232f1c2) and 4.2.5. If I'm seeing this right the brush tip gets 2x the rotation angle from the canvas, so in a full 360° canvas rotation the brush will spin around itself twice. The tilt direction sensor does still affect the brush as expected, just to clarify that. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 404597] New: Jumpy, unpredictable zoom behavior right after canvas rotation
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 OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: manuel.snudl.zeid...@gmail.com Target Milestone: --- Zooming in on the canvas immediately after rotating it, either with Ctrl + middle button or using the scroll wheel (touch ring on my Intuos) offsets the view. I think this is new, I hadn't noticed it in the nightly build before and it's quite obvious and distracting. It does not happen in 4.1.7. Version: 4.2.0-pre-alpha (git be454f9) Wishlist: Is it possible to have Ctrl + middle button zoom towards the starting cursor position? It would be in line with the scroll zoom and I think it feels more natural. Blender for example gives you that option and applies it to all 2D and 3D views. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 404597] Jumpy, unpredictable zoom behavior right after canvas rotation
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 watching all bug changes.
[krita] [Bug 404601] New: Tilt input on rotation reverses on mirrored canvas
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 Status: REPORTED Severity: normal Priority: NOR Component: Brush engines Assignee: krita-bugs-n...@kde.org Reporter: manuel.snudl.zeid...@gmail.com Target Milestone: --- I'm not sure I should create a new bug report, it's similar to https://bugs.kde.org/show_bug.cgi?id=322344 The difference is, all tilt input (X, Y, direction and elevation) reverses only after I make some change to the brush, like swapping the brush tip while the canvas is mirrored. It also only seems to affect brush rotation. I tested opacity and size controlled by tilt and those behaved fine. Flipping the mirror direction fixes it. Happens in 4.1.7 as well as current nightly 4.2.0-pre-alpha (git be454f9). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408015] Global menu doesn't work
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.
[krita] [Bug 410583] Tilt direction stuck on canvas rotation
https://bugs.kde.org/show_bug.cgi?id=410583 M changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #4 from M --- Fixed in commit d8f90d4a8968e50e709833de8543776860dcbbcb From: Dmitry Kazakov Date: Thu, 22 Aug 2019 13:03:34 +0300 Subject: [PATCH] [REGRESSION] Fix absolute brush rotation on rotated canvas -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 397559] Snapping is sloppy and unpredictable
https://bugs.kde.org/show_bug.cgi?id=397559 M changed: What|Removed |Added CC||manuel.snudl.zeidler@gmail. ||com --- Comment #5 from M --- I'd like to mention that vector point end handles also snap to the cursor position they are dragged from instead of the exact handle position. The curve points themselves snap correctly. Thanks to the person making me aware of it: https://forum.kde.org/viewtopic.php?f=139&t=162161&p=421496 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 389022] Switching between stylus eraser tip and regular tip messes up brush settings of both presets
https://bugs.kde.org/show_bug.cgi?id=389022 M changed: What|Removed |Added CC||manuel.snudl.zeidler@gmail. ||com --- Comment #10 from M --- Thanks to a user reporting on reddit, I could reproduce this behavior: 1. Start a fresh Krita instance 2. Use a brush with the regular tip 3. Flip to the eraser tip, then back to the regular one 4. The brush preset with the regular tip now has the opacity set to 0% If I flip to the eraser again, there is at least a chance it also gets 0% opacity. It still occurs most of the time if I adjust opacity first. This seems to work only once initially per session, but I could repeat the behavior using the Line Tool in the same session. Tested in master and 4.2.5. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405691] New: Screen flickering in newest 4.2.0 when running through primusrun
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 OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: OpenGL Canvas Assignee: krita-bugs-n...@kde.org Reporter: manuel.snudl.zeid...@gmail.com Target Milestone: --- Created attachment 118938 --> https://bugs.kde.org/attachment.cgi?id=118938&action=edit Video showing flickers Since a few days ago, I get severe screen flickering with black bars when I start Krita 4.2.0 Next nightly build through primusrun (so that it uses the dedicted GPU on my laptop) - before that it worked fine. If I then turn off OpenGL accelerated canvas it disappears. If I use optirun instead, there is no flickering issue. There is also no flickering problem with primusrun in Krita 4.1.8, or any other application I tested. Looking through my installed packages, neither the Nvidia driver nor Bumblebee have been updated in this timeframe. I attached a short video that shows it. Seems to be more severe in a maximized window, but never goes away completely. Version: 4.2.0-pre-alpha (git c475ecb) Languages: en_US Hidpi: true Qt Version (compiled): 5.12.2 Version (loaded): 5.12.2 OS Information Build ABI: x86_64-little_endian-lp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: linux Kernel Version: 5.0.3-1-MANJARO Pretty Productname: Manjaro Linux Product Type: manjaro Product Version: unknown 20 Mar 2019 15:25:10 +0100: Closing. OpenGL Info Vendor: "NVIDIA Corporation" Renderer: "GeForce GTX 860M/PCIe/SSE2" Version: "4.6.0 NVIDIA 418.43" Shading language: "4.60 NVIDIA" Requested format: QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) Current format:QSurfaceFormat(version 4.6, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) Version: 4.6 Supports deprecated functions true is OpenGL ES: false QPA OpenGL Detection Info supportsDesktopGL: true supportsOpenGLES: false isQtPreferOpenGLES: false == log == Supported renderers: QFlags(0x2) Surface format preference list: * QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) QSurfaceFormat::OpenGL * QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) QSurfaceFormat::OpenGLES Probing format... QSurfaceFormat::DefaultColorSpace QSurfaceFormat::OpenGL Found format: QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) QSurfaceFormat::OpenGL -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405693] New: PNG Brush tips are suddenly being recognized as GBR format instead of masks
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: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Brush engines Assignee: krita-bugs-n...@kde.org Reporter: manuel.snudl.zeid...@gmail.com Target Milestone: --- Created attachment 118940 --> https://bugs.kde.org/attachment.cgi?id=118940&action=edit PNG brush tip, that is misidentified A few of the PNG brush tips in my collection suddenly don't work correctly anymore, both in Version 4.1.8 and 4.2.0 Next nightly, as of a couple of days ago. Instead of counting as masks where the brightness is the transparency, they are now identified as GBR format, so when drawing I get the grayscale image with rectangular borders instead of transparency. Some of affected ones I made directly in Krita not long ago. I verified they were working and I use them frequently. I tried assigning sRGB and Gray color profiles in Krita and swapping channels in ImageMagick, but the only thing that worked was converting into Gimp brush format (.gbr). I attached one of the affected PNG images as an example. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405693] PNG Brush tips are suddenly being recognized as GBR format instead of masks
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.
[krita] [Bug 405693] PNG Brush tips are suddenly being recognized as GBR format instead of masks
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.
[krita] [Bug 405693] PNG Brush tips are suddenly being recognized as GBR format instead of masks
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 receiving this mail because: You are watching all bug changes.
[krita] [Bug 405693] PNG Brush tips are suddenly being recognized as GBR format instead of masks
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 | -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 404935] Window of another apps partially visible in Krita canvas
https://bugs.kde.org/show_bug.cgi?id=404935 M changed: What|Removed |Added CC||manuel.snudl.zeidler@gmail. ||com --- Comment #3 from M --- Created attachment 118988 --> https://bugs.kde.org/attachment.cgi?id=118988&action=edit Transparency on Linux It happens for me on Linux (KDE) too - I added a screenshot. Same behavior when I launch Krita with optirun. I found that disabling the compositor with Shift+Alt+F12 fixes it. Version: 4.2.0-pre-alpha (git 27678b4) Languages: en_US Hidpi: true Qt Version (compiled): 5.12.2 Version (loaded): 5.12.2 OS Information Build ABI: x86_64-little_endian-lp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: linux Kernel Version: 5.0.3-1-MANJARO Pretty Productname: Manjaro Linux Product Type: manjaro Product Version: unknown Hardware Information GPU Acceleration: auto Memory: 15951 Mb Number of Cores: 8 Swap Location: /tmp 23 Mar 2019 23:33:14 +0100: Created image "Unnamed", 2048 * 2048 pixels, 100 dpi. Color model: 8-bit integer/channel L*a*b*/Alpha (Lab identity built-in). Layers: 1 23 Mar 2019 23:33:14 +0100: Enabled weighted smoothing. 23 Mar 2019 23:33:14 +0100: Enabled weighted smoothing. 23 Mar 2019 23:33:14 +0100: Enabled weighted smoothing. 23 Mar 2019 23:33:14 +0100: Enabled weighted smoothing. 23 Mar 2019 23:33:14 +0100: Enabled weighted smoothing. 23 Mar 2019 23:33:14 +0100: Enabled weighted smoothing. 23 Mar 2019 23:33:45 +0100: Closing. OpenGL Info Vendor: "NVIDIA Corporation" Renderer: "GeForce GTX 860M/PCIe/SSE2" Version: "4.6.0 NVIDIA 418.43" Shading language: "4.60 NVIDIA" Requested format: QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) Current format:QSurfaceFormat(version 4.6, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) Version: 4.6 Supports deprecated functions true is OpenGL ES: false QPA OpenGL Detection Info supportsDesktopGL: true supportsOpenGLES: false isQtPreferOpenGLES: false == log == Supported renderers: QFlags(0x2) Surface format preference list: * QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) QSurfaceFormat::OpenGL * QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) QSurfaceFormat::OpenGLES Probing format... QSurfaceFormat::DefaultColorSpace QSurfaceFormat::OpenGL Found format: QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) QSurfaceFormat::OpenGL -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 404935] Window of another apps partially visible in Krita canvas
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) Haswell Mobile " Version: "3.0 Mesa 19.0.0" Shading language: "1.30" Requested format: QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) Current format:QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::NoProfile) Version: 3.0 Supports deprecated functions true is OpenGL ES: false QPA OpenGL Detection Info supportsDesktopGL: true supportsOpenGLES: true isQtPreferOpenGLES: false == log == Supported renderers: QFlags(0x2|0x4) Surface format preference list: * QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) QSurfaceFormat::OpenGL * QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) QSurfaceFormat::OpenGLES Probing format... QSurfaceFormat::DefaultColorSpace QSurfaceFormat::OpenGL Found format: QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) QSurfaceFormat::OpenGL -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405540] Brush Outline are white in Krita nightly build
https://bugs.kde.org/show_bug.cgi?id=405540 M changed: What|Removed |Added CC||manuel.snudl.zeidler@gmail. ||com --- Comment #3 from M --- Created attachment 119024 --> https://bugs.kde.org/attachment.cgi?id=119024&action=edit See-through brush outline I added a screenshot showing my brush outline is see-through. System info is the same as what I commented here: https://bugs.kde.org/show_bug.cgi?id=404935 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405691] Screen flickering in newest 4.2.0 when running through primusrun
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. Another way of avoiding it is starting an X session on the Nvidia GPU directly. In the terminal I see these lines repeated only with primusrun or optirun: qt.glx: qglx_findConfig: Failed to finding matching FBConfig (8 8 8 8) qt.glx: qglx_findConfig: Failed to finding matching FBConfig (1 8 8 8) qt.glx: qglx_findConfig: Failed to finding matching FBConfig (1 1 8 8) qt.glx: qglx_findConfig: Failed to finding matching FBConfig (1 1 1 8) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405691] Screen flickering in newest 4.2.0 when running through primusrun
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.
[krita] [Bug 406250] New: Color space conversion with clone layer crashes - only in specific circumstances
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: Linux Status: REPORTED Severity: normal Priority: NOR Component: Color models Assignee: krita-bugs-n...@kde.org Reporter: manuel.snudl.zeid...@gmail.com Target Milestone: --- This was observed in both version 4.1.8 and the Next nightly (git f3858d1). I'm having a hard time trying to extract a pattern here. This is the most reliable method I found: STEPS TO REPRODUCE 1. Start a fresh Krita instance 2. Create a new document - I used 1024*1024 px, L*a*b* 16-bit int 3. Make a clone layer, don't draw anything before or after 4. Convert image to color space: RGB 8-bit int, leave the default profile Krita will crash immediately most of the times with the terminal message: ASSERT (krita): "m_buffer[currentIndex].loadAcquire() > 0" in file /home/appimage/workspace/Krita_Nightly_Appimage_Build/krita/libs/image/tiles3/KisTiledExtentManager.cpp, line 87 Aborted (core dumped) Even in this case, it doesn't fail 100% reliably. Somehow, drawing on the layer before the conversion, trying other color space and precision combinations, or having another document open at the same time will significantly reduce the chance of a crash - It is still possible to provoke it after several retries. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406250] Color space conversion with clone layer crashes - only in specific circumstances
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/KisTiledExtentManager.cpp, line 53 Aborted (core dumped) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406250] Color space conversion with clone layer crashes - only in specific circumstances
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 provoke a crash this way. Other than that, what information would you need from me? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420260] Segfault when opening anything (master)
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'm hesitant to call it gone for good. With the newest build and AppImage I get a guaranteed full freeze when I try to select some particular ones of my custom brush presets from the editor window or presets docker, but that may be out of scope for this bug. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420260] Segfault when opening anything (master)
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.
[krita] [Bug 417667] Bad allocation crash
https://bugs.kde.org/show_bug.cgi?id=417667 M changed: What|Removed |Added Resolution|WORKSFORME |--- Status|RESOLVED|REOPENED Ever confirmed|0 |1 --- Comment #5 from M --- Apologies for the delay, I didn't return to the document for a while. Here's the download: https://www.dropbox.com/s/jjf24x7hta47tu7/2020%201%20macaws.kra?dl=0 I can still provoke the crash in current master. No difference when I run Krita on the Nvidia GPU instead of Intel. Easiest way to trigger I found is trying to apply a filter onto one of the source layers (macaw 1, macaw 2 in the document). Pick an adjustment filter that has curves or sliders and continuously drag a handle around until Krita freezes (usually less than 30 sec). -- You are receiving this mail because: You are watching all bug changes.
