[dolphin] [Bug 371765] New: Documents suddenly open as archives
https://bugs.kde.org/show_bug.cgi?id=371765 Bug ID: 371765 Summary: Documents suddenly open as archives Product: dolphin Version: 16.08.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: hewa...@gmail.com Target Milestone: --- Suddenly documents such as ODT or DOCX (probbly othes too) open as archives when double clicked instead of with the program in their file type association. I have to do "Right Click -> Open with" to open them properly. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 371765] Documents suddenly open as archives
https://bugs.kde.org/show_bug.cgi?id=371765 --- Comment #2 from Storm Engineer --- (In reply to Christoph Feck from comment #1) > Right click the file > Properties > File Type Options. Did you even read my comment? "instead of with the program in their file type association" = The associations are CORRECT. Ark is NOT in the list. The first element is LibreOffice. And they are NOT opening with Ark, but within Dolphin with a "krarc:/" path, just like archives should look like when opened within Dolphin as folders. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 371765] Documents suddenly open as archives
https://bugs.kde.org/show_bug.cgi?id=371765 --- Comment #4 from Storm Engineer --- Yes, after removing Krusader it opens with LibreOffice again. But the question is, why Dolphin decided suddenly that documents should be treated as archives in regard of the "open archives as folders" option whereas before it didn't do that? I have "open archives as folders" enabled for years, and documents always opened with LibreOffice before. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 371765] Documents suddenly open as archives
https://bugs.kde.org/show_bug.cgi?id=371765 --- Comment #5 from Storm Engineer --- Note: Reinstalling Krusader restores the incorrect behavior. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 452502] New: Krita refuses to open valid files based on extension
https://bugs.kde.org/show_bug.cgi?id=452502 Bug ID: 452502 Summary: Krita refuses to open valid files based on extension Product: krita Version: 5.0.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: storm.ant...@gmail.com Target Milestone: --- SUMMARY I have tried to open one of the save backup files created by Krita, with the ".kra.1~" extension, only to be told Krita can't open it because it's not the right file type. After being renamed to ".kra" it opened without a problem. Krita, especially on Linux, should use file headers instead of extensions to determine if something is of a supported file type. This used to work previously. STEPS TO REPRODUCE 1. Change a valid .kra file's extension to something invalid. 2. Try to open it. OBSERVED RESULT Krita will claim it's the wrong file type. EXPECTED RESULT Krita should open the file like it used to. SOFTWARE/OS VERSIONS Krita Version: 5.0.2 Languages: en_US, en, en_US, en, hu_HU, hu Hidpi: false Qt Version (compiled): 5.15.2 Version (loaded): 5.15.3 OS Information Build ABI: x86_64-little_endian-lp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: linux Kernel Version: 5.17.1-arch1-1 Pretty Productname: Arch Linux Product Type: arch Product Version: unknown Desktop: KDE OpenGL Info Vendor: "NVIDIA Corporation" Renderer: "NVIDIA GeForce GTX 750 Ti/PCIe/SSE2" Version: "4.6.0 NVIDIA 510.60.02" Shading language: "4.60 NVIDIA" -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 452481] Krita crashes when Flattening images with reference pictures
https://bugs.kde.org/show_bug.cgi?id=452481 Storm Engineer changed: What|Removed |Added CC||storm.ant...@gmail.com --- Comment #2 from Storm Engineer --- I can repo on Arch. Flattening, scaling, and converting color space all causes Krita to freeze and crash - but the 5.0.2 appimage, and Arch's 5.0.2 package. After deleting the reference images neither of those actions cause a problem. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 452481] Krita crashes when Flattening images with reference pictures
https://bugs.kde.org/show_bug.cgi?id=452481
--- Comment #4 from Storm Engineer ---
SESSION: 11 Apr 2022 21:02:02 +0200. Executing krita
Krita Version: 5.0.2, Qt version compiled: 5.15.2, loaded: 5.15.3. Process ID:
13115
-- -- -- -- -- -- -- --
11 Apr 2022 21:02:02 +0200: Style: breeze. Available styles: Breeze, Oxygen,
Windows, Fusion
11 Apr 2022 21:02:04 +0200: Database is up to date. Version: 0.0.15, created by
Krita 5.0.0, at Sat Jan 1 20:32:58 2022
11 Apr 2022 21:02:06 +0200: Could not load resourcepalettes/Palette1.kpl
11 Apr 2022 21:02:06 +0200: Could not load resourcepalettes/Palette2.kpl
11 Apr 2022 21:02:06 +0200: Could not load resourcepalettes/Palette3.kpl
11 Apr 2022 21:02:06 +0200: Could not load resourcepalettes/Palette.kpl
11 Apr 2022 21:02:06 +0200: Could not retrieve md5 for
resourcepaintoppresets/Special_dyna_dots.kpp
11 Apr 2022 21:02:06 +0200: Could not add
resource{d45362f1-dbd3-424d-803c-57565ccf0757}
11 Apr 2022 21:02:06 +0200: Could not retrieve md5 for
resourcepalettes/Pastel5x2.kpl
11 Apr 2022 21:02:08 +0200: SAFE ASSERT (krita): "result.size() == 1" in file
/build/krita/src/krita-5.0.2/libs/resources/KisStoragePlugin.cpp, line 92
11 Apr 2022 21:02:21 +0200: Removing autosave file:
/home/storm/Data/Art/--Digital/--Source/Jasper-bust/Jasper-bust.kra-autosave.kra
11 Apr 2022 21:02:21 +0200: Importing application/x-krita to
application/x-krita. Location:
/home/storm/Data/Art/--Digital/--Source/Jasper-bust/Jasper-bust.kra. Real
location: /home/storm/Data/Art/--Digital/--Source/Jasper-bust/Jasper-bust.kra.
Batchmode: 0
11 Apr 2022 21:02:23 +0200: Loaded image from application/x-krita. Size: 2481 *
3509 pixels, 4.16667 dpi. Color model: 16-bit integer/channel RGB/Alpha
(sRGB-elle-V2-g10.icc). Layers: 11
KRITA DID NOT CLOSE CORRECTLY
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 452481] Krita crashes when Flattening images with reference pictures
https://bugs.kde.org/show_bug.cgi?id=452481 --- Comment #5 from Storm Engineer --- I've also just created a new image in 8 bit, pasted a random image from Google as ref, made 3 layers, tried to flatten, and the same happened. So it's not tied to the file I was working on. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 394414] Brush preset thumbnails are the wrong aspect and often hidden and unselectable
https://bugs.kde.org/show_bug.cgi?id=394414 --- Comment #20 from Storm Engineer --- I haven't experienced this with git master since it went to 5.0, and the last time I built master a few weeks ago this was still the case. I don't know when will I have the time to build it again to verify but I would wager it was indeed an issue with the older code that is replaced. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 265801] Add a "Create guide(s) from selected shape(s)" feature
https://bugs.kde.org/show_bug.cgi?id=265801 --- Comment #5 from Storm Engineer --- Just for reference: my duplicate ticket was suggesting the ability to simply load vector images as assistants. Another option would be to let us use the existing vector drawing tools to draw on a vector layer and convert* that. I think both could be implemented simultaneously. *What if we add a new layer type: assistant layer? For the most part, this would be a normal raster/vector layer that was given a flag and would live in a dedicated "assistant layers" docker to keep the normal layers docker clean. These layers would be hidden regardless of their per-layer visibility when "hide assistants" is enabled, otherwise could be toggled from there. Actually, this assistant layers docker could also have an entry for regular assistants, to make it easy to find, select, show/hide them, and perhaps even group them in folders like normal layers. The new layer mentioned above could be called "Custom assistant" layer to set it apart from the built in ones. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 415906] Non intuitive process to create New Shortcuts schemes gives the impression Load/Save does not work.
https://bugs.kde.org/show_bug.cgi?id=415906 --- Comment #8 from Storm Engineer --- May I ask what is the current the status of this? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 394414] Using brush presets search sometimes changes thumbnail size
https://bugs.kde.org/show_bug.cgi?id=394414 Storm Engineer changed: What|Removed |Added CC||storm.ant...@gmail.com --- Comment #7 from Storm Engineer --- I don't think it's directly related to the search. My thumbnails are always incorrect by default, often a column of them being hidden as they would be outside the sub-window. Changing the Thumbnail size slider will change the distortion, and sometimes a certain size will cause them to render inside the sub-window properly, but not always. The only time thumbs look correct is when either via tags or search, there are only a very few (eg 6-8) thumbnails displaying. P.s.: Arch Linux + KDE5 here. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 395506] "use same aspect as pixel" ignores monitor resolution when calculating display size
https://bugs.kde.org/show_bug.cgi?id=395506 Storm Engineer changed: What|Removed |Added CC|storm.ant...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 394414] Using brush presets search sometimes changes thumbnail size
https://bugs.kde.org/show_bug.cgi?id=394414 Storm Engineer changed: What|Removed |Added Version|4.0.3 |git master -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407661] New: Weird file open failure related to icc profiles?
https://bugs.kde.org/show_bug.cgi?id=407661 Bug ID: 407661 Summary: Weird file open failure related to icc profiles? Product: krita Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: storm.ant...@gmail.com Target Milestone: --- I restarted Krita. After that it could not open any .kra files I tried. It threw the same two lines of error for each layer in my file: Could not load pixel data: reference_images/layers/layer9. Could not load profile: reference_images/layers/layer9.icc. The files did contain several reference images, but all of them are standard sRGB, and all the layers were 16 bit RGB. Restarted Krita again, and now all files opened properly as expected. I don't know a reliable way to reproduce this at the moment. Krita Version: 4.2.0-alpha (git 351ae7e) Languages: en_US Hidpi: false Qt Version (compiled): 5.12.3 Version (loaded): 5.12.3 OS Information Build ABI: x86_64-little_endian-lp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: linux Kernel Version: 5.0.13-arch1-1-ARCH Pretty Productname: Arch Linux Product Type: arch Product Version: unknown Hardware Information GPU Acceleration: auto Memory: 16006 Mb Number of Cores: 8 Swap Location: /tmp -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407661] Weird file open failure related to icc profiles?
https://bugs.kde.org/show_bug.cgi?id=407661 Storm Engineer changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Storm Engineer --- Snudl on IRC said they had the same issue and it was fixed after building latest master so I built fresh and it seems to be fixed indeed. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407665] New: Using selections crashes Krita
https://bugs.kde.org/show_bug.cgi?id=407665 Bug ID: 407665 Summary: Using selections crashes Krita 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: storm.ant...@gmail.com Target Milestone: --- Using selections crashes Krita. Reproduce: - Open or create a file - Try to use the rectangular selection tool Krita Version: 4.2.0-beta (git fb226d0) Languages: en_US Hidpi: false Qt Version (compiled): 5.12.3 Version (loaded): 5.12.3 OS Information Build ABI: x86_64-little_endian-lp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: linux Kernel Version: 5.0.13-arch1-1-ARCH Pretty Productname: Arch Linux Product Type: arch Product Version: unknown Hardware Information GPU Acceleration: auto Memory: 16006 Mb Number of Cores: 8 Swap Location: /tmp -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 394414] Brush preset thumbnails are the wrong aspect and often hidden and unselectable
https://bugs.kde.org/show_bug.cgi?id=394414 Storm Engineer changed: What|Removed |Added Summary|Using brush presets search |Brush preset thumbnails are |sometimes changes thumbnail |the wrong aspect and often |size|hidden and unselectable -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 394414] Brush preset thumbnails are the wrong aspect and often hidden and unselectable
https://bugs.kde.org/show_bug.cgi?id=394414 --- Comment #8 from Storm Engineer --- Created attachment 120219 --> https://bugs.kde.org/attachment.cgi?id=120219&action=edit Screenshot comparison Edited the title to better reflect the nature of the issue, and added a new screenshot to demonstrate. Note: on the left several presets are missing because they are outside the boundary of the presets button's dropdown. When adjusting the thumb size in the dropdown, the thumbs in the docker get resized correctly. When size is adjusted from the docker, it will display the same issue the dropdown does. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 394414] Brush preset thumbnails are the wrong aspect and often hidden and unselectable
https://bugs.kde.org/show_bug.cgi?id=394414 --- Comment #9 from Storm Engineer --- Created attachment 120223 --> https://bugs.kde.org/attachment.cgi?id=120223&action=edit Starting state This is how the dropdown looks for me right after starting Krita (current master). :-O -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407801] New: Recent colors vertical rows should be populated vertically
https://bugs.kde.org/show_bug.cgi?id=407801 Bug ID: 407801 Summary: Recent colors vertical rows should be populated vertically Product: krita Version: git master Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Color Selectors Assignee: krita-bugs-n...@kde.org Reporter: storm.ant...@gmail.com Target Milestone: --- When recent colors for the color selector is set to horizontal, and more than one rows, it will be populated top to bottom and then left to right, instead of the other way around, which would make more sense. OBSERVED RESULT With two rows, the colors are populated as: 1 3 5 7 2 4 6 EXPECTED RESULT It should be: 1 2 3 4 5 6 7 SOFTWARE/OS VERSIONS Krita Version: 4.2.0-beta (git fb226d0) Languages: en_US Hidpi: false Qt Version (compiled): 5.12.3 Version (loaded): 5.12.3 OS Information Build ABI: x86_64-little_endian-lp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: linux Kernel Version: 5.0.13-arch1-1-ARCH Pretty Productname: Arch Linux Product Type: arch Product Version: unknown -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407839] New: Custom shortcuts constantly getting wiped
https://bugs.kde.org/show_bug.cgi?id=407839 Bug ID: 407839 Summary: Custom shortcuts constantly getting wiped Product: krita Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Shortcuts and Canvas Input Settings Assignee: krita-bugs-n...@kde.org Reporter: storm.ant...@gmail.com Target Milestone: --- I've lost my custom shortcuts at least ten times by now and I'm still confused about what is going on. I would set a bunch of custom shortcuts, and they work. I can quit Krita and they will be in place when I start again. However, trying to save them into a custom scheme will wipe everything from BOTH current settings AND the scheme you are saving, except those shortcuts you changed during the present run of Krita. STEPS TO REPRODUCE 1. Set a few custom shortcuts and save them in a scheme. 2. Restart Krita. 3. Change a shortcut, and save the scheme again. OBSERVED RESULT All previously set shortcuts will be wiped and stop working, and the scheme file will contain only the last change, not the shortcuts saved previously. EXPECTED RESULT Saving a scheme should preserve everything currently in effect, and save that all into the scheme. Krita Version: 4.2.0-beta (git 4cb9902) Languages: en_US Hidpi: false Qt Version (compiled): 5.12.3 Version (loaded): 5.12.3 OS Information Build ABI: x86_64-little_endian-lp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: linux Kernel Version: 5.0.13-arch1-1-ARCH Pretty Productname: Arch Linux Product Type: arch Product Version: unknown Hardware Information GPU Acceleration: auto Memory: 16006 Mb Number of Cores: 8 Swap Location: /tmp -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 394414] Brush preset thumbnails are the wrong aspect and often hidden and unselectable
https://bugs.kde.org/show_bug.cgi?id=394414 --- Comment #11 from Storm Engineer --- As I have stated several times I experience this on Linux, so it's not Windows related. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407513] Gamut mask selectable area has an offset to visible mask
https://bugs.kde.org/show_bug.cgi?id=407513 Storm Engineer changed: What|Removed |Added CC||storm.ant...@gmail.com --- Comment #1 from Storm Engineer --- I have noticed this before, but it seems to be fixed in master. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407977] New: Gamut mask status should be saved to Krita file
https://bugs.kde.org/show_bug.cgi?id=407977 Bug ID: 407977 Summary: Gamut mask status should be saved to Krita file Product: krita Version: git master Platform: Other OS: All Status: REPORTED Severity: normal Priority: NOR Component: Color Selectors Assignee: krita-bugs-n...@kde.org Reporter: storm.ant...@gmail.com Target Milestone: --- Currently gamut mask selection and rotation are not saved. In order to be able to continue work on the same file consistently, both the selected mask and its rotation should be saved into the Krita file. Without this the only way to ensure consistency between work sessions is by writing the selection and rotation down and manually restoring it. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407978] New: Popup palette closes instantly with stylus
https://bugs.kde.org/show_bug.cgi?id=407978 Bug ID: 407978 Summary: Popup palette closes instantly with stylus Product: krita Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: storm.ant...@gmail.com Target Milestone: --- Just built master. When my Wacom stylus' button is used as right click to open the popup palette, it will instantly close again unless I try my best to make the button click as quick as possible. If the button is held down the palette stays until the button is released - however if the stylus is moved while the button is held, the palette will randomly close and open again. It does not happen with regular mouse click. This issue was not present in my previous build from about a week ago. Krita Version: 4.2.0-beta (git 439f570) Languages: en_US Hidpi: false Qt Version (compiled): 5.12.3 Version (loaded): 5.12.3 OS Information Build ABI: x86_64-little_endian-lp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: linux Kernel Version: 5.1.3-arch1-1-ARCH Pretty Productname: Arch Linux Product Type: arch Product Version: unknown Hardware Information GPU Acceleration: auto Memory: 16006 Mb Number of Cores: 8 Swap Location: /tmp -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 394414] Brush preset thumbnails are the wrong aspect and often hidden and unselectable
https://bugs.kde.org/show_bug.cgi?id=394414 --- Comment #12 from Storm Engineer --- Please disregard my previous comment. I've misread "window" as "Windows". Sorry about that. So, for me this just happens 100% of the time, no matter what I do with the window, dockers, or anything, and I can not produce a state where it does not happen. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408326] New: Popup palette will disappear when releasing stylus button
https://bugs.kde.org/show_bug.cgi?id=408326 Bug ID: 408326 Summary: Popup palette will disappear when releasing stylus button Product: krita Version: git master Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: storm.ant...@gmail.com Target Milestone: --- My previous report on this seems to have vanished so reporting again. --- When using my Wacom stylus button set as Right click to open the Popup Palette, the palette will close on button release, unless I'm clicking it especially fast. If I hold the button down and move the stylus the palette will randomly jump around following it, and sometimes close and reopen as well. It does not happen with the house. Krita Version: 4.2.0-beta (git 77c9d6b) Languages: en_US Hidpi: false Qt Version (compiled): 5.12.3 Version (loaded): 5.12.3 OS Information Build ABI: x86_64-little_endian-lp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: linux Kernel Version: 5.1.4-arch1-1-ARCH Pretty Productname: Arch Linux Product Type: arch Product Version: unknown -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 394414] Brush preset thumbnails are the wrong aspect and often hidden and unselectable
https://bugs.kde.org/show_bug.cgi?id=394414 --- Comment #14 from Storm Engineer --- My number of presets changes often because I'm constantly creating new ones, and sometimes remove ones added by bundles that I don't need. But I have a very large number, around 5-600 presets total. If I use search or show tags instead of "all", I notice that the more presets displayed at once the worse it gets. Apparently adjusting thumbnail size affects only the height not the width, which causes the distortion. Maybe this is why there are more thumbs in a row than what can fit, because they are wider than they should be? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407978] Popup palette closes instantly with stylus
https://bugs.kde.org/show_bug.cgi?id=407978 --- Comment #19 from Storm Engineer --- Just fully updated Arch and rebuilt master and there is no difference, same behavior as when reported. (KDE 5) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 394414] Brush preset thumbnails are the wrong aspect and often hidden and unselectable
https://bugs.kde.org/show_bug.cgi?id=394414 Storm Engineer changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #17 from Storm Engineer --- Sorry, I missed when this was closed. The issue is still present for me with 4.3.0-prealpha (git 3e21da9) Reopening as requested. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409749] Stylus eraser keeps resetting to basic brush
https://bugs.kde.org/show_bug.cgi?id=409749 --- Comment #1 from Storm Engineer --- As of 4.3.0-prealpha (git 3e21da9), this issue is still present for me. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409748] Brush preset docker/dropdown only saves las used tag if when quiting krita the tag is not set to "All".
https://bugs.kde.org/show_bug.cgi?id=409748 --- Comment #6 from Storm Engineer --- As of 4.3.0-prealpha (git 3e21da9), this issue is still present for me. -- 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 #5 from Storm Engineer --- Does the reporter or anyone else know of a still good commit so I could do a bisect on this? -- 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 #7 from Storm Engineer --- Alright, I'll see if I can start from there. Thank you! -- 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 #10 from Storm Engineer --- Ah, sorry, I wanted to bisect this but life happened and I forgot... :( As for the how: I noticed that the more I rotate the more it will jump. I hope this helps a bit. Without knowing the code I would guess the value of the rotation somehow gets mixed with the position/panning value. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407978] Popup palette closes instantly with stylus
https://bugs.kde.org/show_bug.cgi?id=407978 Storm Engineer changed: What|Removed |Added Status|RESOLVED|CLOSED --- Comment #22 from Storm Engineer --- I don't have any such checkbox in my Wacom tablet settings, and I still experience this... -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409748] New: Brush preset dropdown keeps changing to a tag
https://bugs.kde.org/show_bug.cgi?id=409748 Bug ID: 409748 Summary: Brush preset dropdown keeps changing to a tag Product: krita Version: git master Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: storm.ant...@gmail.com Target Milestone: --- Every time Krita starts the brush presets dropdown will have the tag "Textures" selected instead of All, or whatever it was left on. STEPS TO REPRODUCE 1. Set the dropdown to All, or any tag 2. Restart Krita OBSERVED RESULT The dropdown is always reset to show the same tag EXPECTED RESULT The dropdown should either reset to All, or be left on the last used tag. Krita Version: 4.3.0-prealpha (git 1766363) Languages: en_US Hidpi: false 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.1.16-arch1-1-ARCH Pretty Productname: Arch Linux Product Type: arch Product Version: unknown Hardware Information GPU Acceleration: auto Memory: 16006 Mb Number of Cores: 8 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409749] New: Stylus eraser keeps resetting to basic brush
https://bugs.kde.org/show_bug.cgi?id=409749 Bug ID: 409749 Summary: Stylus eraser keeps resetting to basic brush Product: krita Version: git master Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: tablet support Assignee: krita-bugs-n...@kde.org Reporter: storm.ant...@gmail.com Target Milestone: --- Every time Krita starts the eraser side of my Wacom stylus is changed to the preset "Basic tip default". STEPS TO REPRODUCE 1. Chose a preset with the Eraser side 2. Restart Krita OBSERVED RESULT The eraser tip is reset to the same brush preset every time EXPECTED RESULT Eraser tip is left on whatever preset it last had. Krita Version: 4.3.0-prealpha (git 1766363) Languages: en_US Hidpi: false 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.1.16-arch1-1-ARCH Pretty Productname: Arch Linux Product Type: arch Product Version: unknown Hardware Information GPU Acceleration: auto Memory: 16006 Mb Number of Cores: 8 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409751] New: Docker height creep when using canvas only mode
https://bugs.kde.org/show_bug.cgi?id=409751 Bug ID: 409751 Summary: Docker height creep when using canvas only mode Product: krita Version: git master Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Dockers Assignee: krita-bugs-n...@kde.org Reporter: storm.ant...@gmail.com Target Milestone: --- When using canvas only mode, every time I return from it, certain dockers get slightly taller pushing dockers below and under them to smaller size. STEPS TO REPRODUCE 1. Have a bunch of dockers on top of each other in a sidebar. So far I could reproduce with: Layers docker, Advanced color selector 2. Enter canvas-only mode then return to normal mode. 3. Repeat this several times OBSERVED RESULT Certain dockers get slightly taller each time EXPECTED RESULT Docker size should say the same as before Krita Version: 4.3.0-prealpha (git 1766363) Languages: en_US Hidpi: false 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.1.16-arch1-1-ARCH Pretty Productname: Arch Linux Product Type: arch Product Version: unknown Hardware Information GPU Acceleration: auto Memory: 16006 Mb Number of Cores: 8 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409748] Brush preset dropdown keeps changing to a tag
https://bugs.kde.org/show_bug.cgi?id=409748 --- Comment #3 from Storm Engineer --- It maybe depending on how many tags you have. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409748] Brush preset docker/dropdown only saves las used tag if when quiting krita the tag is not set to "All".
https://bugs.kde.org/show_bug.cgi?id=409748 --- Comment #5 from Storm Engineer --- I never use the tags, I always have it in All. Yet next run ut will show the "Textures" tag again. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410514] New: Undo history corrupted, layer content lost
https://bugs.kde.org/show_bug.cgi?id=410514 Bug ID: 410514 Summary: Undo history corrupted, layer content lost Product: krita Version: git master Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: storm.ant...@gmail.com Target Milestone: --- I was trying to undo some free transforms, when suddenly my layer content disappeared, and the canvas stopped updating, and nothing I tried (eg. toggling layers on/off) helped. I tried to scribble on the layer and that appeared, but undoing that the layer returned to empty I went back in the undo history several steps before the scribble - the canvas was still not updating but I hoped it is only visual. I saw my previous drawing in the undo history thumbnails. I saved and restarted Krita. Upon opening my file, the layer in question contained nothing but the scribble that I supposedly undo-d. All previous content were lost permanently. I don't know how to reproduce. SOFTWARE/OS VERSIONS Krita Version: 4.3.0-prealpha (git cec1505) Languages: en_US Hidpi: false 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.4-arch1-1-ARCH Pretty Productname: Arch Linux Product Type: arch Product Version: unknown Hardware Information GPU Acceleration: auto Memory: 16006 Mb Number of Cores: 8 Swap Location: /tmp -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410514] Undo history corrupted, layer content lost
https://bugs.kde.org/show_bug.cgi?id=410514 --- Comment #2 from Storm Engineer --- (In reply to Boudewijn Rempt from comment #1) > Please update: cec1505 isn't that old, but Dmitry fixed a bunch of issues in > the transform tool. Alright, I'll post here if the issue happens again. -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 409568] Options disappear on bottom bar in version 5.1.1-2
https://bugs.kde.org/show_bug.cgi?id=409568 Storm Engineer changed: What|Removed |Added CC||storm.ant...@gmail.com --- Comment #3 from Storm Engineer --- Arch user here. I cannot find any bug reports on this on Arch side, nor can I find any such reference anywhere. So who says it's an Arch bug and on what do they base this? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 393113] Crop Tool: crop image without cropping the layers data
https://bugs.kde.org/show_bug.cgi?id=393113 --- Comment #6 from Storm Engineer --- Victor, I don't understand why you want this functionality placed in a different tool when it can simply be a checkbox on the tool settings of the corp tool? The dialog to change canvas size is nice and all when you do something calculated but doesn't allow simple visual re-composing of the canvas in the way the crop tool would if the checkbox to not discard off-canvas areas is added. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 404783] KDE Plasma slow shutdown/reboot/logout
https://bugs.kde.org/show_bug.cgi?id=404783 Storm Engineer changed: What|Removed |Added CC||storm.ant...@gmail.com --- Comment #4 from Storm Engineer --- I also experience very slow start and shutdown, also Plasma 5 on Arch, system on SSD. Someone suggested it may be my desktop widgets - and teh widgets load exactly the moment the 10-15 sec long "hang time" in the middle of teh GUI loading ends. Does the reporter here use widgets? Also, I'm a noob so please let me know what logs should I uploaded and how to get them. Journal from the moment of logging in via console: https://pastebin.com/vjMN7Y0y Some interesting parts with several sec delays: Mar 09 07:19:31 Camelot systemd[1]: Started Session 1 of user storm. Mar 09 07:19:32 Camelot kernel: resource sanity check: requesting [mem 0x000c-0x000f], which spans more than PCI Bus :00 [mem 0x000d-0x000d3fff window] Mar 09 07:19:32 Camelot kernel: caller _nv001094rm+0xe3/0x1d0 [nvidia] mapping multiple BARs Mar 09 07:19:33 Camelot systemd[659]: Started D-Bus User Message Bus. Mar 09 07:19:35 Camelot systemd-timesyncd[585]: Synchronized to time server 5.39.184.5:123 (2.arch.pool.ntp.org). Mar 09 07:19:38 Camelot dbus-daemon[705]: [session uid=1000 pid=705] Activating service name='org.kde.kglobalaccel' requested by ':1.5' (uid=1000 pid=739 comm="kded5 [kdeinit5] ") Mar 09 07:19:38 Camelot dbus-daemon[705]: [session uid=1000 pid=705] Successfully activated service 'org.kde.kglobalaccel' Mar 09 07:19:39 Camelot dbus-daemon[589]: [system] Activating via systemd: service name='org.freedesktop.ColorManager' unit='colord.service' requested by ':1.23' (uid=1000 pid=739 comm="kded5 [kdeinit5] ") Mar 09 07:19:45 Camelot dbus-daemon[589]: [system] Activating via systemd: service name='org.freedesktop.UDisks2' unit='udisks2.service' requested by ':1.59' (uid=1000 pid=888 comm="/usr/bin/dolphin -session 10afd0e16500015516182050") Mar 09 07:19:45 Camelot systemd[1]: Starting Disk Manager... Mar 09 07:19:45 Camelot udisksd[1053]: udisks daemon version 2.8.1 starting Mar 09 07:19:58 Camelot dbus-daemon[705]: [session uid=1000 pid=705] Activating service name='org.kde.kuiserver' requested by ':1.20' (uid=1000 pid=840 comm="/usr/bin/plasmashell ") Mar 09 07:19:58 Camelot dbus-daemon[705]: [session uid=1000 pid=705] Successfully activated service 'org.kde.kuiserver' Mar 09 07:20:10 Camelot dbus-daemon[589]: [system] Failed to activate service 'org.freedesktop.UDisks2': timed out (service_start_timeout=25000ms) Mar 09 07:20:14 Camelot dbus-daemon[589]: [system] Activating via systemd: service name='org.freedesktop.UDisks2' unit='udisks2.service' requested by ':1.59' (uid=1000 pid=888 comm="/usr/bin/dolphin -session 10afd0e16500015516182050") Mar 09 07:20:18 Camelot dbus-daemon[589]: [system] Successfully activated service 'org.freedesktop.UDisks2' Mar 09 07:20:18 Camelot systemd[1]: Started Disk Manager. Not sure if my issue is related. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 404783] KDE Plasma slow shutdown/reboot/logout
https://bugs.kde.org/show_bug.cgi?id=404783 --- Comment #5 from Storm Engineer --- [storm@Camelot] (~) $ systemd-analyze blame 32.659s udisks2.service 8.064s dhcpcd@enp3s0.service 724ms lvm2-monitor.service 680ms systemd-logind.service 631ms systemd-journal-flush.service 555ms dev-sda2.device 396ms home-storm-misc-swapfile.swap 273ms systemd-timesyncd.service 207ms upower.service 198ms systemd-fsck@dev-disk-by\x2duuid-68CB\x2d49A9.service 198ms systemd-fsck@dev-disk-by\x2duuid-6140ad0c\x2dca18\x2d42ca\x2dacd4\x2d0ed77f7f0700.service 192ms systemd-udevd.service 172ms systemd-fsck@dev-disk-by\x2duuid-9b9b2009\x2d57e5\x2d473c\x2d97cd\x2deaa63c3dc8b8.service 127ms user@1000.service 113ms polkit.service 94ms systemd-modules-load.service 71ms systemd-udev-trigger.service 69ms home.mount 58ms systemd-journald.service 52ms systemd-tmpfiles-setup-dev.service 47ms boot.mount 38ms systemd-binfmt.service 35ms systemd-tmpfiles-clean.service 34ms home-storm-misc.mount 33ms systemd-tmpfiles-setup.service [...] This corresponds with my second snippet above. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 404783] KDE Plasma slow shutdown/reboot/logout
https://bugs.kde.org/show_bug.cgi?id=404783 --- Comment #6 from Storm Engineer --- Sorry for the comment spam. Apparently udisk2 is not the culprit. I remoed that issue via disabling Dropbox (see: https://bbs.archlinux.org/viewtopic.php?id=239449 ) but that didn't solve the problem. Now: systemd-analyze blame 8.213s dhcpcd@enp3s0.service 2.833s udisks2.service 682ms systemd-journal-flush.service 675ms systemd-logind.service 619ms lvm2-monitor.service 551ms dev-sda2.device 388ms home-storm-misc-swapfile.swap 289ms systemd-timesyncd.service 269ms upower.service 255ms systemd-fsck@dev-disk-by\x2duuid-68CB\x2d49A9.service 191ms systemd-fsck@dev-disk-by\x2duuid-6140ad0c\x2dca18\x2d42ca\x2dacd4\x2d0ed77f7f0700.service 189ms systemd-udevd.service 160ms systemd-fsck@dev-disk-by\x2duuid-9b9b2009\x2d57e5\x2d473c\x2d97cd\x2deaa63c3dc8b8.service 156ms user@1000.service 116ms polkit.service 103ms packagekit.service 85ms systemd-udev-trigger.service 83ms systemd-modules-load.service 78ms home.mount 66ms systemd-journald.service 60ms boot.mount 45ms systemd-tmpfiles-setup-dev.service systemd-analyze critical-chain: multi-user.target @10.253s └─getty.target @10.252s └─getty@tty1.service @10.251s └─systemd-user-sessions.service @10.242s +7ms └─network.target @10.240s └─dhcpcd@enp3s0.service @2.025s +8.213s └─basic.target @2.023s └─sockets.target @2.022s └─dbus.socket @2.021s └─sysinit.target @2.019s └─systemd-timesyncd.service @1.729s +289ms └─systemd-tmpfiles-setup.service @1.692s +33ms └─local-fs.target @1.690s └─tmp.mount @1.686s +3ms └─swap.target @1.681s └─home-storm-misc-swapfile.swap @1.292s +388ms └─home-storm-misc.mount @1.262s +28ms └─home.mount @1.141s +78ms └─systemd-fsck@dev-disk-by\x2duuid-6140ad0c\x2dca18\x2d42ca\x2dacd4\x2d0ed77f7f0700.service @949ms +191ms └─local-fs-pre.target @939ms └─lvm2-monitor.service @318ms +619ms └─lvm2-lvmetad.service @364ms └─systemd-journald.socket @312ms └─system.slice @295ms └─-.slice @295ms (Ignore the 8 sec for DHCP, that happens before login and is due to my crap router) Journal: https://pastebin.com/q8CRRte0 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411536] New: Weird resize crash only when specific values are used
https://bugs.kde.org/show_bug.cgi?id=411536 Bug ID: 411536 Summary: Weird resize crash only when specific values are used Product: krita Version: git master Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Resize/Scale Image/Layer Assignee: krita-bugs-n...@kde.org Reporter: storm.ant...@gmail.com Target Milestone: --- I can crash Krita with 100% consistency using canvas resize and image rescale with specific values, but when I use slightly different values, it doesn't crash. More interestingly, I can reproduce in both master, and the 4.2 Alpha appimage. STEPS TO REPRODUCE 1. Open the template file: https://www.dropbox.com/s/25s09dsxqm67gxs/1.41%5B%E2%88%9A2%5D%7C420x297mm%22A3%22%5B4962x3509px%5D.kra?dl=0 2. Resize canvas (constraint proportion UN-ticked) to 410 * 287 mm 3. Scale image (constraint proportions and adjust print separately are UN-ticked) to 584 * 410 mm OBSERVED RESULT Krita crashes promptly Krita Version: 4.3.0-prealpha (git e96181d) Languages: en_US Hidpi: false 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.11-arch1-1-ARCH Pretty Productname: Arch Linux Product Type: arch Product Version: unknown Hardware Information GPU Acceleration: auto Memory: 16006 Mb Number of Cores: 8 Swap Location: /tmp 02 Sep 2019 19:41:06 +0200: Importing application/x-krita to application/x-krita. Location: /home/storm/.local/share/krita/templates/Art Templates by Storm/.source/1.41[√2]|420x297mm"A3"[4962x3509px].kra. Real location: /home/storm/.local/share/krita/templates/Art Templates by Storm/.source/1.41[√2]|420x297mm"A3"[4962x3509px].kra. Batchmode: 0 02 Sep 2019 19:41:07 +0200: Instant Preview Setting: 0 02 Sep 2019 19:41:07 +0200: Enabled stabilizer. 02 Sep 2019 19:41:07 +0200: Enabled stabilizer. 02 Sep 2019 19:41:07 +0200: Enabled stabilizer. 02 Sep 2019 19:41:07 +0200: Enabled stabilizer. 02 Sep 2019 19:41:07 +0200: Enabled stabilizer. 02 Sep 2019 19:41:07 +0200: Enabled stabilizer. 02 Sep 2019 19:41:07 +0200: Instant Preview Setting: 0 02 Sep 2019 19:41:10 +0200: Instant Preview Setting: 0 02 Sep 2019 19:42:22 +0200: ASSERT (krita): "row < 0x7FFF && col < 0x7FFF" in file /home/storm/misc/git-repos/krita/master/libs/image/tiles3/kis_tile_hash_table2.h, line 133 OpenGL Info Vendor: "NVIDIA Corporation" Renderer: "GeForce GTX 750 Ti/PCIe/SSE2" Version: "4.6.0 NVIDIA 435.21" Shading language: "4.60 NVIDIA" Requested format: QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) Current format:QSurfaceFormat(version 4.6, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) Version: 4.6 Supports deprecated functions true is OpenGL ES: false QPA OpenGL Detection Info supportsDesktopGL: true supportsOpenGLES: true isQtPreferOpenGLES: false == 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) 2 * 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) 4 Probing format... QSurfaceFormat::DefaultColorSpace 2 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) 2 == end log == -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411536] Weird resize crash only when specific values are used
https://bugs.kde.org/show_bug.cgi?id=411536 --- Comment #1 from Storm Engineer --- New observations: 1. After doing the canvas resize, interacting with Layer 1 in any way also triggers the crash. 2. If I make a brushstroke on layer 1 before canvas resize, I'm not able to trigger the crash anymore. -- 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 Storm Engineer changed: What|Removed |Added CC||storm.ant...@gmail.com --- Comment #1 from Storm Engineer --- I'M experiencing this as well with master since about a week or so. It seems to be random, as it does not always happen, but maybe 1-2 times out of 3. -- 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 #2 from Storm Engineer --- Forgot: Building master from git on Arch. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396158] Vanishing point assistant rays should be hidden when assistants are hidden
https://bugs.kde.org/show_bug.cgi?id=396158 --- Comment #3 from Storm Engineer --- Any update on this? I'm relying on VP assistants heavily and they are very painful to use with all those rays displaying. :( -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406155] New: Flattening the image resets background color and opacity
https://bugs.kde.org/show_bug.cgi?id=406155 Bug ID: 406155 Summary: Flattening the image resets background color and opacity Product: krita Version: git master Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: OpenGL Canvas Assignee: krita-bugs-n...@kde.org Reporter: storm.ant...@gmail.com Target Milestone: --- Flattening the image resets background color to #00 and opacity to 0. This results in the image having a transparent BG even if it didn't have before. STEPS TO REPRODUCE 1. Set Image background color and opacity to any value 2. Flatten image OBSERVED RESULT BG color and opacity are reset EXPECTED RESULT BG color and opacity should be preserved SOFTWARE/OS VERSIONS Krita Version: 4.2.0-pre-alpha (git 9dac9dc) Languages: en_US Hidpi: false 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.5-arch1-1-ARCH Pretty Productname: Arch Linux Product Type: arch Product Version: unknown Hardware Information GPU Acceleration: auto Memory: 16006 Mb Number of Cores: 8 Swap Location: /tmp -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406157] New: Krita hangs on converting color space
https://bugs.kde.org/show_bug.cgi?id=406157 Bug ID: 406157 Summary: Krita hangs on converting color space Product: krita Version: git master Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Color models Assignee: krita-bugs-n...@kde.org Reporter: storm.ant...@gmail.com Target Milestone: --- Krita hangs on converting color space Posted as per request of Dmitry Backtrace: https://pastebin.com/8g7b27G5 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406155] Flattening the image resets background color and opacity
https://bugs.kde.org/show_bug.cgi?id=406155 --- Comment #2 from Storm Engineer --- Just built master fresh again. At the moment I can't reproduce either. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406157] Krita hangs on converting color space
https://bugs.kde.org/show_bug.cgi?id=406157 --- Comment #2 from Storm Engineer --- I can't reproduce anymore with current master. Fixed? -- 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 #3 from Storm Engineer --- Created attachment 119231 --> https://bugs.kde.org/attachment.cgi?id=119231&action=edit Tablet event logs I have created tablet event logs, I hope they can be of some use. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422059] 4.3 Beta hard-depends on OpenEXR 2.4
https://bugs.kde.org/show_bug.cgi?id=422059 --- Comment #2 from Storm Engineer --- I did a full clean build (wiping directory) now and the issue didn't happen, so it seems this was my fault. Sorry. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420260] New: Segfault when opening anything (master)
https://bugs.kde.org/show_bug.cgi?id=420260 Bug ID: 420260 Summary: Segfault when opening anything (master) Product: krita Version: git master Platform: Compiled Sources OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: storm.ant...@gmail.com Target Milestone: --- Created attachment 127652 --> https://bugs.kde.org/attachment.cgi?id=127652&action=edit GDB backtrace Krita crashes (segfault) when trying to open anything, including new document. STEPS TO REPRODUCE 1. Start Krita 2. Create new document or open existing OBSERVED RESULT Segfault SOFTWARE/OS VERSIONS Krita Version: 5.0.0-prealpha (git 4a37f35) Languages: en_US, en, en_US, en, hu_HU, hu Hidpi: false Qt Version (compiled): 5.14.2 Version (loaded): 5.14.2 OS Information Build ABI: x86_64-little_endian-lp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: linux Kernel Version: 5.6.4-arch1-1 Pretty Productname: Arch Linux Product Type: arch Product Version: unknown Desktop: KDE OpenGL Info Vendor: "NVIDIA Corporation" Renderer: "GeForce GTX 750 Ti/PCIe/SSE2" Version: "4.6.0 NVIDIA 440.82" Shading language: "4.60 NVIDIA" Requested format: QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) Current format:QSurfaceFormat(version 4.6, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) Version: 4.6 Supports deprecated functions true is OpenGL ES: false QPA OpenGL Detection Info supportsDesktopGL: true supportsOpenGLES: true isQtPreferOpenGLES: false Hardware Information GPU Acceleration: auto Memory: 15981 Mb Number of Cores: 8 Swap Location: /tmp Current Settings Current Swap Location: /tmp Current Swap Location writable: true Undo Enabled: true Undo Stack Limit: 100 Use OpenGL: true Use OpenGL Texture Buffer: true Use AMD Vectorization Workaround: false Canvas State: OPENGL_SUCCESS Autosave Interval: 300 Use Backup Files: true Number of Backups Kept: 3 Backup File Suffix: ~ Backup Location: Same Folder as the File Backup Location writable: false Use Win8 Pointer Input: false Use RightMiddleTabletButton Workaround: true Levels of Detail Enabled: false Use Zip64: false Display Information Number of screens: 2 Screen: 0 Name: DP-0 Depth: 24 Scale: 1 Resolution in pixels: 1600x900 Manufacturer: Dell Inc. Model: DELL IN2030M- Refresh Rate: 59.9782 Screen: 1 Name: DVI-I-0 Depth: 24 Scale: 1 Resolution in pixels: 1680x1050 Manufacturer: Acer Technologies Model: Acer P221W- Refresh Rate: 59.9543 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 415906] Non intuitive process to create New Shortcuts schemes gives the impression Load/Save does not work.
https://bugs.kde.org/show_bug.cgi?id=415906 --- Comment #5 from Storm Engineer --- I agree that the current behavior is confusing and difficult to use. I would like to suggest the following behavior from the GUI's/user's perspective: - Have following buttons/combobox options next to list: New, Load, Save, Delete, Rename, Export, Import - "New" adds a new empty profile to the list - "Load" loads the selected profile into current settings. Display warning if current settings has unsaved changes. - "Save" saves current into selected profile. Display "Are you sure you want to overwrite?" warning. - "Delete" and "Rename" does just that on selected profile. Warning for deleting, obviously. - "Import" and "Export" would be the only options requiring the user to select files, should be used for making backups, sharing settings with others, etc. - If changes are made, display "modified" in place of selected profile to clearly indicate that current settings are not reflecting a profile anymore and are unsaved. Thus the only actions that would modify current settings are hitting Load, or making manual changes, and the only action modifying saved profiles is hitting Save. Saving, loading, creating and deleting would be seamless without the user having to select file paths. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 415906] Non intuitive process to create New Shortcuts schemes gives the impression Load/Save does not work.
https://bugs.kde.org/show_bug.cgi?id=415906 --- Comment #6 from Storm Engineer --- Adding to the above: If clicking Save while the "modified" message is displayed (in other words, without selecting a profile), or while a default profile is selected, it would works as "save as", asking for what the name of the new profile should be. The list should also contain an option "New preset" that we can select for saving it as a new one if something was selected before. This would use 3 types of files in 3 locations: - Default presets, located in Krita install folder. These would be unchangable, allowing them to be updated with new shortcuts as new features are added. - User shortcuts, located in user settings folder. - Current settings, stored in an rc file in generic settings location -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 416515] New: Krita cannot save if file contains reference images
https://bugs.kde.org/show_bug.cgi?id=416515 Bug ID: 416515 Summary: Krita cannot save if file contains reference images Product: krita Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: storm.ant...@gmail.com Target Milestone: --- If I add reference images to my file, any save attempt, manual or autosave will fail with the following error: "Could not save [file path] Reason: Unknown error" The following error is printed in the terminal: libpng error: known incorrect sRGB profile libpng error: known incorrect sRGB profile saving binary data failed Deleting the reference images makes save work again. STEPS TO REPRODUCE 1. Open a file, try saving. 2. Add one or more reference images, try saving again. 3. Delete reference images, try saving again. OBSERVED RESULT Save fails if reference images are present. EXPECTED RESULT Saving should work. SOFTWARE/OS VERSIONS Krita Version: 4.3.0-prealpha (git ef0a009) Languages: en_US, en, en_US, en, hu_HU, hu Hidpi: false Qt Version (compiled): 5.14.0 Version (loaded): 5.14.0 OS Information Build ABI: x86_64-little_endian-lp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: linux Kernel Version: 5.4.13-arch1-1 Pretty Productname: Arch Linux Product Type: arch Product Version: unknown -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 416515] Krita cannot save if file contains reference images
https://bugs.kde.org/show_bug.cgi?id=416515 --- Comment #2 from Storm Engineer --- libpng 1.6.37 I'm going to downgrade qt and see if that fixes it. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 416515] Krita cannot save if file contains reference images
https://bugs.kde.org/show_bug.cgi?id=416515 --- Comment #4 from Storm Engineer --- Yes, Arch. Sadly I could not test downgrading qt, because a partial downgrade caused Plasma to be unable to start. But Arch actually moved on from qt 5.12 last June, and from libpng 1.6.34 in 2017. Version histories: https://git.archlinux.org/svntogit/packages.git/log/trunk?h=packages/qt5-base https://git.archlinux.org/svntogit/packages.git/log/trunk?h=packages/libpng -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 416515] Krita cannot save if file contains reference images
https://bugs.kde.org/show_bug.cgi?id=416515 --- Comment #6 from Storm Engineer --- The PNG loads and saves fine in Gwenview. I can also save it just fine with Krita when opened as an image, saving only fails when it's inserted as a reference image. P.s.: I see you changed the platform. I'm confused about that property. What does it actually refer to? The Krita build's origin (shipped by repo vs compiled)? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 416515] Krita cannot save if file contains reference images
https://bugs.kde.org/show_bug.cgi?id=416515 --- Comment #15 from Storm Engineer --- Sorry for the late reply. Do you still need my assistance with this? -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 417720] New: "Open with Gwenview" entry when rightclicking empty space in folder
https://bugs.kde.org/show_bug.cgi?id=417720 Bug ID: 417720 Summary: "Open with Gwenview" entry when rightclicking empty space in folder Product: gwenview Version: 19.12.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: storm.ant...@gmail.com Target Milestone: --- Since a recent update, when right clicking the empty area in a folder in Dolphin, the menu "Open with Gwenview" is injected to the top, pushing the "New" submenu down. STEPS TO REPRODUCE 1. Open a folder in Dolphin 2. Right click empty area OBSERVED RESULT Top entry is "Open with Gwenview" EXPECTED RESULT Top entry should be "New", and there shouldn't be a Gwenview entry at all. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.66.0 Qt Version: 5.14.1 Kernel Version: 5.5.2-arch1-1 OS Type: 64-bit Processors: 8 × Intel® Core™ i7-2600 CPU @ 3.40GHz Memory: 15.6 GiB of RAM ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 417640] unintuitive right mouse click default behavior for create new
https://bugs.kde.org/show_bug.cgi?id=417640 --- Comment #4 from Storm Engineer --- As of today on Arch, this is still not fixed. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422059] New: 4.3 Beta hard-depends on OpenEXR 2.4
https://bugs.kde.org/show_bug.cgi?id=422059 Bug ID: 422059 Summary: 4.3 Beta hard-depends on OpenEXR 2.4 Product: krita Version: 4.3.0-beta1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: storm.ant...@gmail.com Target Milestone: --- Building 4.3 Beta on Arch fils because the current version of OpenEXR on Arch is 2.5, and the build script specifically looks for 2.4. Downgrading to 2.4 for now solved it. STEPS TO REPRODUCE 1. Try to build with OpenEXR 2.5 OBSERVED RESULT make[2]: *** No rule to make target '/usr/lib/libHalf-2_4.so', needed by 'libs/pigment/libkritapigment.so.19.0.0'. Stop. make[1]: *** [CMakeFiles/Makefile2:11076: libs/pigment/CMakeFiles/kritapigment.dir/all] Error 2 libHalf is part of OpenEXR. EXPECTED RESULT It should detect that the installed version is 2.5 SOFTWARE/OS VERSIONS Linux/KDE Plasma: Archj Linux + Plasma 5 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 354688] Can't remove file File Association in System Settings
https://bugs.kde.org/show_bug.cgi?id=354688 --- Comment #6 from Storm Engineer --- I would love to hear from the devs about the status of this as well. It's a real pain that sometimes things will open with the corresponding Windows application under Wine instead of the properly installed corresponding Linux application. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 393113] Crop Tool: crop image without cropping the layers data
https://bugs.kde.org/show_bug.cgi?id=393113 Storm Engineer changed: What|Removed |Added CC||storm.ant...@gmail.com --- Comment #4 from Storm Engineer --- This is a feature that has a lot of valid use cases, so I second it. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396155] New: Reference images tool lacks features
https://bugs.kde.org/show_bug.cgi?id=396155 Bug ID: 396155 Summary: Reference images tool lacks features Product: krita Version: git master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Tools/Reference Images Assignee: krita-bugs-n...@kde.org Reporter: storm.ant...@gmail.com Target Milestone: --- Created attachment 113750 --> https://bugs.kde.org/attachment.cgi?id=113750&action=edit Demonstration of problem 1 Right now the new Reference images tool doesn't have much to offer over simply using a layer. The two huge advantages of the old references docker were that 1; It could be docked into, or floated over the GUI, saving precious canvas area real estate 2; Was fixed to the GUI and immune to panning and zooming of canvas, staying usable at all times Even if you have two or more huge screens and can afford to never zoom in and always keep the reference images pinned around the canvas in view, doing this can be very inconvenient, especially if you rotate the canvas. But if you have smaller screen space, then actually using a layer is better because you can erase irrelevant parts of the ref image to save space. The old docker offered the perfect solution to this, which is why I relied heavily on it and I also believe that's why many others loved it. Attached mockups to demonstrate the problem. This tool is right now in no way a replacement for the old ref images docker as it lacks the abilities that made said docker so useful. Please add the following abilities to make it useful: - Pin ref = Ref image ignores canvas zoom/pan/rotation and stays absolutely positioned relative to the screen (or of that's not possible, relative to the Krita window) ( - Optionally, separate pin for scale, rotation and position.) - Ref on top = Ref image can display over the GUI This way the new tool would be a proper replacement for the old docker, with an overall better functionality than the old one. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396155] Reference images tool lacks features
https://bugs.kde.org/show_bug.cgi?id=396155 --- Comment #1 from Storm Engineer --- Created attachment 113751 --> https://bugs.kde.org/attachment.cgi?id=113751&action=edit Demonstration of problem 2 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396158] New: Vanishing point assistant rays should be hidden when assistants are hidden
https://bugs.kde.org/show_bug.cgi?id=396158 Bug ID: 396158 Summary: Vanishing point assistant rays should be hidden when assistants are hidden Product: krita Version: git master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Tool/Assistants Assignee: krita-bugs-n...@kde.org Reporter: storm.ant...@gmail.com Target Milestone: --- Created attachment 113752 --> https://bugs.kde.org/attachment.cgi?id=113752&action=edit Demonstration of issue The new Vanishing point assistant now has a set of rays coming from the center. Since there are a lot of them it can be distracting, especially if we have several vanishing points. Being able to hide them without having to hide assistant previews would solve this. Current behavior: Hiding Assistants only hides the center point and not the rays. Expected behavior: The ray should be hidden leaving only the line through the cursor. Attached screenshot to demonstrate issue. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396168] New: Asistants ignore rescaling of image
https://bugs.kde.org/show_bug.cgi?id=396168 Bug ID: 396168 Summary: Asistants ignore rescaling of image Product: krita Version: git master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Tool/Assistants Assignee: krita-bugs-n...@kde.org Reporter: storm.ant...@gmail.com Target Milestone: --- Assistants are unaffected by rescaling the image, and so they will be incorrect after rescale. Steps to repo: 1; Create an image 2; Place assistants and specific points 3; Rescale image to 50% width and height. Actual behavior: Assistants retain their position relative to the original image size. Expected behavior: Assistants retain position and scale relative to the image's new dimensions. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396155] Reference images tool lacks features
https://bugs.kde.org/show_bug.cgi?id=396155 --- Comment #3 from Storm Engineer --- (In reply to Quiralta from comment #2) > Just want to make a "cross reference" with the dialog in the phabricator and > google+ Thank you! :) I would appreciate if you also add any points I'm having here that may not be in those discussions yet - since you are already familiar with those, and I have very little time right now. I see great potential in the new tool, if these points are addressed and maybe even more functionality is added it could be a really amazing tool. I recommend to look at PureRef, by far the most popular app in the World that adds similar functionality. Lots of people use it and everyone who does loves it, so probably a good place to look for a good example. https://www.pureref.com/ -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396158] Vanishing point assistant rays should be hidden when assistants are hidden
https://bugs.kde.org/show_bug.cgi?id=396158 --- Comment #2 from Storm Engineer --- (In reply to Scott Petrovic from comment #1) > So what you are wanting for is that the vanishing point lines to be part of > the show assistant checkbox, not the assistant preview checkbox. Yes. They are way too visually distracting to be always on, while the line through the cursor is fairly subtle. Tying it to "Show assistants" instead allows you to have only the subtle line. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 397342] New: Scale image - Print size adjustment is broken
https://bugs.kde.org/show_bug.cgi?id=397342 Bug ID: 397342 Summary: Scale image - Print size adjustment is broken Product: krita Version: git master Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: storm.ant...@gmail.com Target Milestone: --- The print size spin boxes under "Image/Scale image to new size" behave incorrectly. When I try to input values the fields are populated by incorrect numbers. These numbers are a small fragment of the number entered. Eg. Print size in my file is 776 x 1233 mm. When I input "800" in the first field, the values are overwritten to 125 x 202. The wrong number gets bigger by increasing the input number, but the result is not consistent. Clicking the increase/decrease arrows increase the value by about 0.35, instead of 1. Updating the value of the DpI field seems to update dimensions correctly. Reproducible both with Git master and the 4.0.4 and 4.1.1 appimages. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 397558] New: Guides ignore change of canvas shape
https://bugs.kde.org/show_bug.cgi?id=397558 Bug ID: 397558 Summary: Guides ignore change of canvas shape Product: krita Version: git master Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: storm.ant...@gmail.com Target Milestone: --- If the canvas shape changes via rescaling image, rotating or resizing canvas, the guides will not follow along, and simply stay at the same absolute position they were before. When resizing canvas guides will ignore the offset as well. Expected behavior: Guides should keep their position relative to the canvas through resize/rotation. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 397559] New: Snapping is sloppy and unpredictable
https://bugs.kde.org/show_bug.cgi?id=397559 Bug ID: 397559 Summary: Snapping is sloppy and unpredictable Product: krita Version: git master Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: storm.ant...@gmail.com Target Milestone: --- Snapping is unpredictable, it often seems to snap to random positions while refuse to snap to actual elements such as image borders or guides. Also, snapping looks at the cursor position, not the bounding box. This makes it very hard or impossible to snap objects' edges to anything is you would need to move the object while holding it by its edge/corner. Finally, apparently there is no easy way to enable/disable snapping altogether, forcing one to go and enable/disable all the "snapping to" options one by one. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 391696] Right click with wacom pen auto selects whatever I hover over
https://bugs.kde.org/show_bug.cgi?id=391696 Storm Engineer changed: What|Removed |Added CC||storm.ant...@gmail.com --- Comment #4 from Storm Engineer --- This exists for a long time on Linux as well, and is still present in current 4.0 master as of today, using the kernel drivers. (Sorry I kept forgetting to report it.) This also causes context menus to operate in a "hold and release to select" manner, which I thought to be intentional. Additionally, when using the context menu in the layers docker, if I move the cursor over one of the layer color swatches as I hold right click to navigate the menu the color gets selected even if I just pass over it without releasing. Conclusion: This behavior makes using popup palette and menus very painful, so even if it's intentional, please change it or make it optimal. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 391850] New: Autosave lag is back
https://bugs.kde.org/show_bug.cgi?id=391850 Bug ID: 391850 Summary: Autosave lag is back Product: krita Version: git master Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: storm.ant...@gmail.com Target Milestone: --- When Krita auto-saves the whole program freezes entirely for 4-6 seconds. If you can't reproduce, try with a large file. I can't regression test right now, but I believe my last master build without this issue was about one to one and a half weeks ago. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 390027] Auto save paints a straight lines when I paint with brush
https://bugs.kde.org/show_bug.cgi?id=390027 Storm Engineer changed: What|Removed |Added CC||storm.ant...@gmail.com --- Comment #3 from Storm Engineer --- Not sure if related but the autosave lag just made a return in master: bug 391850 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 391850] Autosave lag is back
https://bugs.kde.org/show_bug.cgi?id=391850 --- Comment #2 from Storm Engineer --- Sorry, I have my limits too. I said I don't have time because building git commits is the only method I was aware of, and that takes me 40 minutes each time (for clean build). I didn't know appimages of git master exist, you should have just said so. With krita-4.0.0-beta1-b322ae6-x86_64 the issue is not present. Freeze is proportional to the size of document. With 3000 x 3000 8bit sRGB single layer it's 2 seconds, with 5000 x 5000 nit's 3-4. With my work file about 4000 x 7000 16 bit and several layers it's in a range of 5-8 sec. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 391850] Autosave lag is back
https://bugs.kde.org/show_bug.cgi?id=391850 --- Comment #3 from Storm Engineer --- Created attachment 111424 --> https://bugs.kde.org/attachment.cgi?id=111424&action=edit video of issue -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 391696] Right click with wacom pen auto selects whatever I hover over on the popup palette
https://bugs.kde.org/show_bug.cgi?id=391696 --- Comment #8 from Storm Engineer --- (In reply to Alvin Wong from comment #6) > it also happens when using a mouse. I can confirm. I never noticed.* > I don't see a problem with them Using the menus and palette with my Wacom pen is very frustrating and sometimes outright painful. Constantly selecting things I don't mean, constantly picking brushes and colors when I just want to open the palette. And most importantly it makes no sense since the side button is set to be a right click - why is this right click behaving entirely different from my mouse right click? * The huge difference is that a mouse cursor generally stays in the same place as you click - a pen held hovering over the tablet is unstable, so it's very easy for it to move over to the first option before you release the button, by accident. I believe press and hold only makes sense in the case of touch and should not be default for anything with buttons (eg stylus/pen, mouse, trackball, touchpad buttons, etc.) Touch and hold could be a great _optional_ feature for the minority who own and use a touch enabled device, but shouldn't be default behavior, especially when not even using touch. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 391927] New: [Wish] Ability to export/import curves
https://bugs.kde.org/show_bug.cgi?id=391927 Bug ID: 391927 Summary: [Wish] Ability to export/import curves Product: krita Version: git master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Brush engines Assignee: krita-bugs-n...@kde.org Reporter: storm.ant...@gmail.com Target Milestone: --- Krita offers amazing flexibility in brush settings. When creating complex brushes, it may involve using several custom curves. It would be very useful if said curves could easily be copied in some way to other settings, or be shared with other people. Thus I think the ability to export/import curves as a simple (XML?) file would be great. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 391927] Ability to export/import curves from the brush editor
https://bugs.kde.org/show_bug.cgi?id=391927 --- Comment #1 from Storm Engineer --- When mentioning this on IRC Deevad suggested copy/paste buttons at the curves, however, this has two downsides: - Doesn't allow sharing between users - In case of copying several curves to a new brush you would have to constantly go back and forth, instead of exporting them all, then importing them all. So I believe import/export would be better than copy/paste. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 391696] Right click with wacom pen auto selects whatever I hover over on the popup palette
https://bugs.kde.org/show_bug.cgi?id=391696 --- Comment #10 from Storm Engineer --- (In reply to Alvin Wong from comment #9) > When I said this, it was referring to the context menus in other areas: Oh sorry, I misread it, my bad. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 393317] New: Popup palette right click only partially disabled
https://bugs.kde.org/show_bug.cgi?id=393317 Bug ID: 393317 Summary: Popup palette right click only partially disabled Product: krita Version: git master Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: storm.ant...@gmail.com Target Milestone: --- commit c7e6c0184f95 "Disable right-clicking on popup palette" is only partially working for me. - Right clicking on the painttop presets still selects them and closes palette - Right clicking on the recent colors ring closes palette without selecting The rest ignores right click properly. Arch Linux 64 bit + KDE 5 Master at 19f6e2ab340570 (not clean build) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 393317] Popup palette right click only partially disabled
https://bugs.kde.org/show_bug.cgi?id=393317 --- Comment #2 from Storm Engineer --- (In reply to Quiralta from comment #1) > I can still pick the foreground color Interestingly, I can not reproduce your issue. Could be that it's some instability that causes different symptoms, or no symptoms, varying from system to system? I'm going to try a clean build now. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 393317] Popup palette right click only partially disabled
https://bugs.kde.org/show_bug.cgi?id=393317 --- Comment #3 from Storm Engineer --- Clean build: same result -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 388254] Add an option to resize canvas to selection or an option in crop tool to resize canvas without deleting pixel
https://bugs.kde.org/show_bug.cgi?id=388254 Storm Engineer changed: What|Removed |Added CC||storm.ant...@gmail.com --- Comment #1 from Storm Engineer --- I second this. It sucks when you crop for composition then you realize you want to make it bigger again later, but all cropped data is lost. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 378846] If canvas is zoomed out, brushes get very slow
https://bugs.kde.org/show_bug.cgi?id=378846 --- Comment #8 from Storm Engineer --- Yes I use smoothing but is it normal that it gets extremely laggy from zooming out? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 378846] If canvas is zoomed out, brushes get very slow
https://bugs.kde.org/show_bug.cgi?id=378846 --- Comment #9 from Storm Engineer --- I played around with Stabilizer. Unticking "scalable distance" made the lag go away. I'm just curious if it is normal behavior that it lags so much with scalable on a large canvas. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 384906] Krita refuses to save
https://bugs.kde.org/show_bug.cgi?id=384906 --- Comment #2 from Storm Engineer --- I haven't encountered this issue in a while. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 387997] New: Zooming results in "Edit guides" history entry
https://bugs.kde.org/show_bug.cgi?id=387997 Bug ID: 387997 Summary: Zooming results in "Edit guides" history entry Product: krita Version: git master Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: storm.ant...@gmail.com Target Milestone: --- Zooming after making brushstrokes results in an "Edit guides" entry in undo history, even for documents that do not have any guides. To reproduce: 1; make a brushstroke 2; Zoom canvas in or out. Just built from Master. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 387998] New: Transformation is auto-applied every few seconds when memory usage is high
https://bugs.kde.org/show_bug.cgi?id=387998 Bug ID: 387998 Summary: Transformation is auto-applied every few seconds when memory usage is high Product: krita Version: git master Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Tools/Transform Assignee: krita-bugs-n...@kde.org Reporter: storm.ant...@gmail.com Target Milestone: --- When working with large files if I didn't save in a while at some point this starts happening. I still had several GB of free RAM (6-8 GB free from 16 total). The transformation, be it free transform or liquify simply gets applies every few seconds, making working with it impossible. Saving the document helps usually, but sometimes Krita has to be closed and re-opened to free up RAM for the issue to go away. Steps to reproduce: 1; Open large canvas and do memory intensive operations (eg. painting with large brushes), but don't save. 2; Once Krita's memory usage goes up, try transforming. Issue is present for a while, I just kept forgetting to make a ticket. :( -- You are receiving this mail because: You are watching all bug changes.
