[krita] [Bug 483069] Memory leak in KRITA in CONFYUI
https://bugs.kde.org/show_bug.cgi?id=483069 Raghavendra kamath changed: What|Removed |Added CC||ra...@raghukamath.com --- Comment #4 from Raghavendra kamath --- The plugin is not official and if there is no memory leak with Krita without the plugin then it is not a Krita issue. Can you reproduce this with other similar plugins. PLease report bugs to the plugin maker -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 459488] Layer > Convert > "To file layer" is named differently than other "Convert to ..." options
https://bugs.kde.org/show_bug.cgi?id=459488 Raghavendra kamath changed: What|Removed |Added Status|CONFIRMED |RESOLVED CC||ra...@raghukamath.com Resolution|--- |FIXED --- Comment #4 from Raghavendra kamath --- This has been now fixed and the patch is merged here - https://invent.kde.org/graphics/krita/-/merge_requests/2034 If the error persists please comment I can re open this bug. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 478846] Pasting From external does nothing, pasting layer info from previous session crashes
https://bugs.kde.org/show_bug.cgi?id=478846 Raghavendra kamath changed: What|Removed |Added Status|REOPENED|CONFIRMED --- Comment #5 from Raghavendra kamath --- Oops ignore my comment I intended to close another bug and closed the wrong bug- reopening now. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 478846] Pasting From external does nothing, pasting layer info from previous session crashes
https://bugs.kde.org/show_bug.cgi?id=478846 Raghavendra kamath changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 478846] Pasting From external does nothing, pasting layer info from previous session crashes
https://bugs.kde.org/show_bug.cgi?id=478846 Raghavendra kamath changed: What|Removed |Added CC||ra...@raghukamath.com Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #4 from Raghavendra kamath --- This has been now fixed and the patch is merged here - https://invent.kde.org/graphics/krita/-/merge_requests/2034 If the error persists please comment I can re open this bug. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477570] When using a stylus the cursor is shown as a cross when hovering over native-Wayland Qt software
https://bugs.kde.org/show_bug.cgi?id=477570 --- Comment #4 from Raghavendra kamath --- The cursor doesn't change when hovering over the edge of the window so resize and other operations become troublesome. Also I think applications do provide cursors like firefox provides adwaita cursors. krita will provide the tool cursor I think But on the desktop the crosshair cursor as a default is not so much useful in my opinion. If the user needs they should be able to choose it I think. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 477748] Feature to set raw sample rate and raw suppress rate for graphic tablets
https://bugs.kde.org/show_bug.cgi?id=477748 --- Comment #7 from Raghavendra kamath --- Suppress and sample can be used to reduce too much sensitivity for some people this helps in reducing small the wiggle in line. It averages the data to give a smoother points. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 477898] New: Ability to switch to relative mode for graphic tablet
https://bugs.kde.org/show_bug.cgi?id=477898 Bug ID: 477898 Summary: Ability to switch to relative mode for graphic tablet Classification: Applications Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_tablet Assignee: plasma-b...@kde.org Reporter: ra...@raghukamath.com CC: aleix...@kde.org Target Milestone: --- SUMMARY Tablets are by default operated under absolute mode where the point on the tablet is mapped to the point on the screen. There is one more mode where the tablets behaves like a mouse. It is called relative mode. In this mode the point on the tablet is not matched to the point on the screen, if you lift the pen and start from a different position the cursor will continue to move from the existing position. This is like how touchpads work. Some artists like to use this mode. Wacom calls this the mouse mode in their tablet settings application on Microsoft windows. You can also check the gnome documentation for this feature to better understand it - https://help.gnome.org/users/gnome-help/stable/wacom-mode.html.en This mode was present in the wacom tablet kcm in X11 due to the switch to wayland, this feature is not implemented in the new kcm. To bring graphic tablet experience on wayland on par to X11, I request this mode to added back the new tablet kcm. STEPS TO REPRODUCE 1. Open tablet kcm on wayland and try to set the relative mode for the tablet -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 477748] Feature to set raw sample rate and raw suppress rate for graphic tablets
https://bugs.kde.org/show_bug.cgi?id=477748 --- Comment #2 from Raghavendra kamath --- If I may ask what is the difference between "normal" and "wishlist"? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 477787] New: Feature to set and switch different mode of the touch ring or touch strip on the tablet
https://bugs.kde.org/show_bug.cgi?id=477787 Bug ID: 477787 Summary: Feature to set and switch different mode of the touch ring or touch strip on the tablet Classification: Applications Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_tablet Assignee: plasma-b...@kde.org Reporter: ra...@raghukamath.com CC: aleix...@kde.org Target Milestone: --- SUMMARY Some most popular tablets have the ability to switch modes of the touch ring or the touch strip. Bassed on the mode the shortcut assigned to the touch ring changes so that use can choose which shortcut to use depending on the situation. For example in mode 1 user can have zoom in and zoom out shortcuts mapped to the touch ring and in mode 2 they can have shortcut to resize the brush. This helps the artists to quickly utilise multiple shortcuts in the same touch ring without the need to take away the hand from the tablet. Libinput too supports this. here is the documentation for it - https://wayland.freedesktop.org/libinput/doc/latest/tablet-support.html#tablet-pad-modes If you want to read more here is the description page of the touch ring on wacom website. - https://101.wacom.com/UserHelp/en/TouchRing.htm notice there is a diagram showing 4 different modes shown by a led indicator besides the touch ring. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477784] New: Ability to have a list of multiple colour profiles to be used for a monitor on wayland
https://bugs.kde.org/show_bug.cgi?id=477784 Bug ID: 477784 Summary: Ability to have a list of multiple colour profiles to be used for a monitor on wayland Classification: Plasma Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: ra...@raghukamath.com Target Milestone: --- SUMMARY Sometimes artists need different colour profile for different job. They might be doing print work so they would have created a profile for print job and a profile for general viewing and media consumption. So it will help if the display section in the system settings where user assigns a colour profile had a list of colour profile that the user can choose from a checkbox. This was earlier possible in colord kcm on X11 I am not sure if it should be files under kwin or colord so I am filling it here any way. STEPS TO REPRODUCE 1. Open display section of the systemsettings under wayland 2. You will notice that it has a browse button where you can load one colour profile for the display. OBSERVED RESULT User can't have multiple colour profile loaded and select one of them according to the occasion EXPECTED RESULT User should have the ability to load multiple colour profiles and choose any one of them at a given time -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 457705] Feature to change the pressure curve of the graphic tablet in the tablet KCM
https://bugs.kde.org/show_bug.cgi?id=457705 --- Comment #7 from Raghavendra kamath --- For me as a user it doesn't matter if it is wayland or X11, user should not know if it is wayland or X11 what matter is that they are able to continue on their work. Plasma 5 had this feature in system settings section and the new plasma 6 system setting section it is not there. For me plasma 6 is next release of plasma 5 and you removed (did not implement it). You can't call a regression a wishlist. in any case I do not want to argue here as it is not contributing to this bug report. I have not changed the severity now as you instructed. But personally as a user this is a regression which needs to be fixed, and not stashed aside as a wishlist which is not important. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 457705] Feature to change the pressure curve of the graphic tablet in the tablet KCM
https://bugs.kde.org/show_bug.cgi?id=457705 --- Comment #5 from Raghavendra kamath --- Well I think this can be called as a regression since this is a downgrade from existing feature which is removed from plasma 5 to plasma 6. moreover this is not a optional feature. But anyway you can decide that thank you for your time. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 477752] No ability to assign shortcut to the touch rings on graphic tablet on wayland
https://bugs.kde.org/show_bug.cgi?id=477752 --- Comment #1 from Raghavendra kamath --- Created attachment 163637 --> https://bugs.kde.org/attachment.cgi?id=163637=edit screenshot showing the touch ring configuration under x11 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 477752] New: No ability to assign shortcut to the touch rings on graphic tablet on wayland
https://bugs.kde.org/show_bug.cgi?id=477752 Bug ID: 477752 Summary: No ability to assign shortcut to the touch rings on graphic tablet on wayland Classification: Applications Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_tablet Assignee: plasma-b...@kde.org Reporter: ra...@raghukamath.com CC: aleix...@kde.org Target Milestone: --- SUMMARY Various graphic tablets have a touch ring on one side along with the buttons. Artists use this ring to assign keys to this ring's touch rotation, for example a key is assigned to clockwise and another for counter clockwise touch rotation. This helps is getting more natural actions in dedicated application like brush reszies in krita, zoom in zoom out in image viewer or just scrolling on firefox. Current kcm doesn't even list these rings and there is no way to assign shortcut for these. STEPS TO REPRODUCE 1. Connect a tablet which has a touch ring in it 2. Go to tablet kcm under wayland and try to assign or change the shortcut for this. I am also attaching a screenshot of earlier tablet kcm where this ring is shown and there are entries to change shortcut for this. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 477750] Need a better UI for graphic tablet button and pen button mapping kcm on wayland
https://bugs.kde.org/show_bug.cgi?id=477750 --- Comment #3 from Raghavendra kamath --- I should note that currently the text gets bold when we press the button on the tablet so this helps in knowing which button is which but a layout would be good in addition to this. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 477750] Need a better UI for graphic tablet button and pen button mapping kcm on wayland
https://bugs.kde.org/show_bug.cgi?id=477750 --- Comment #2 from Raghavendra kamath --- Created attachment 163635 --> https://bugs.kde.org/attachment.cgi?id=163635=edit Current kcm showing the page for pen button mapping. Which shows which button is which by showing us a visual button layout Current kcm showing the page for pen button mapping. Which shows which button is which by showing us a visual button layout -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 477750] Need a better UI for graphic tablet button and pen button mapping kcm on wayland
https://bugs.kde.org/show_bug.cgi?id=477750 --- Comment #1 from Raghavendra kamath --- Created attachment 163634 --> https://bugs.kde.org/attachment.cgi?id=163634=edit Current kcm showing the page for tablet button mapping. Which shows which button is which by showing us a visual button layout Current kcm showing the page for tablet button mapping. Which shows which button is which by showing us a visual button layout -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 477750] New: Need a better UI for graphic tablet button and pen button mapping kcm on wayland
https://bugs.kde.org/show_bug.cgi?id=477750 Bug ID: 477750 Summary: Need a better UI for graphic tablet button and pen button mapping kcm on wayland Classification: Applications Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_tablet Assignee: plasma-b...@kde.org Reporter: ra...@raghukamath.com CC: aleix...@kde.org Target Milestone: --- SUMMARY Currently the tablet kcm seems to look like bare minimum page. Earlier on x11 the settings page used to show the drawing and button layout properly so that the user understood which button they are mapping to a shortcut. Currently all the buttons are listed as button 1 button 2 button 3 and so on. On a tablet these buttons can have odd numbering so a simple visual indication would be better for usability. This but report is also for showing a drawing or visual representation of the pen buttons. There is also an issue of the pen being names as "tool" while the pen may be called as a tool in the code it doesn;t help a normal user that much. It can be called "Pen button 1" "Pen button 2" and so on instead of "Tool button 1" "Tool button 2" etc. I attaching a screenshot of how it look under X11 STEPS TO REPRODUCE 1. Open tablet kcm under wayland and check if you can see which button is which on your tablet. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477570] When using a stylus the cursor is shown as a cross when hovering over native-Wayland Qt software
https://bugs.kde.org/show_bug.cgi?id=477570 --- Comment #2 from Raghavendra kamath --- In addition to the odd cursor the cursor also doesn't change to show grab handles and other things. So it becomes hard to grab a window and resize it while using a tablet. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 477748] New: No ability to set raw sample and suppress rate for graphic tablets
https://bugs.kde.org/show_bug.cgi?id=477748 Bug ID: 477748 Summary: No ability to set raw sample and suppress rate for graphic tablets Classification: Applications Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_tablet Assignee: plasma-b...@kde.org Reporter: ra...@raghukamath.com CC: aleix...@kde.org Target Milestone: --- SUMMARY On wayland tablet kcm there is no option to set sample rate and supress rate. Supress and sample rate determine if the data coming from the tablet need to be smoothed out or not. Some artist prefer to change these settings so the data from the tablet can be controlled either to smooth things out or to have unfiltered raw response. Currently in addition lack to editing pressure curve there is no way to set these two options. STEPS TO REPRODUCE 1. Open graphic tablet settings in the systemsetting in wayland. 2. Try to set raw sample rate and supress rate 3. Compare this to tablet kcm in xorg Note: this is not a wishlist item this can be considered a regression as tablet kcm in previous plasma 5 releases had these feature but now it is not there. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 457705] Feature to change the pressure curve of the graphic tablet in the tablet KCM
https://bugs.kde.org/show_bug.cgi?id=457705 Raghavendra kamath changed: What|Removed |Added Severity|wishlist|major -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 477671] New: There is no way to save and utilise different tablet configuration profiles and change them with a shortcut on wayland
https://bugs.kde.org/show_bug.cgi?id=477671 Bug ID: 477671 Summary: There is no way to save and utilise different tablet configuration profiles and change them with a shortcut on wayland Classification: Applications Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_tablet Assignee: plasma-b...@kde.org Reporter: ra...@raghukamath.com CC: aleix...@kde.org Target Milestone: --- SUMMARY: On X11 wacom tablet kcm we have ability to save different profile and cycle between these profiles using the shortcut Meta + Ctrl + P and Meta + ctrl + N This is particularly helpful to configure tablets for various programs, in one application I can assign the buttons to do something else than the next one. I can also have different pressurve curve (which is not available yet on wayland) settings for different scenarios like while doing comic inking I can have a different curve than while doing colouring work. STEPS TO REPRODUCE 1. Open system settings in plasma wayland and go to graphic tablet settings 2. Check whether you can create or change profiles OBSERVED RESULT There is no way to create configuration profile. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477570] New: When using a graphic tablet the cursor is shown as a cross cursor
https://bugs.kde.org/show_bug.cgi?id=477570 Bug ID: 477570 Summary: When using a graphic tablet the cursor is shown as a cross cursor Classification: Plasma Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: ra...@raghukamath.com Target Milestone: --- SUMMARY I tried wayland and kde plasma with neon-unstable-20231119-1118 iso and when I tried to use the desktop my cursor when using a graphic tablet was a cross shape. It changed to adwaita arrow inside firefox and then normal plasma breeze arrow inside xwayland application. This results in fairly inconsistency cursor ideally all the cursor should be of one family. If the goal is to differentiate various devices then all app should use the same cursor while using that device and there should be more p[leasant cursor instead of a cross cursor for other device perhaps a cursor with slight variation in value like gray etc. STEPS TO REPRODUCE 1. Download neon-unstable-20231119-1118 iso 2. Login to plasma desktop 3. use any graphic tablet and observe the cursor OBSERVED RESULT Cursor should be normal plasma cursor EXPECTED RESULT Cursor is now a cross cursor. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 476326] White Frames/Missing Frames during Recording
https://bugs.kde.org/show_bug.cgi?id=476326 Raghavendra kamath changed: What|Removed |Added Ever confirmed|0 |1 Status|RESOLVED|REOPENED Resolution|WORKSFORME |--- CC||ra...@raghukamath.com --- Comment #3 from Raghavendra kamath --- We havehltiple reports for this on KA so let us re open this and solve it -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 476982] Can't draw on Wayland: huge parralax and no way to fix calibration of the stylus on the GUI
https://bugs.kde.org/show_bug.cgi?id=476982 Raghavendra kamath changed: What|Removed |Added CC||ra...@raghukamath.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 476033] New: Wave filter is missing from the filter mask and filter layer list
https://bugs.kde.org/show_bug.cgi?id=476033 Bug ID: 476033 Summary: Wave filter is missing from the filter mask and filter layer list Classification: Applications Product: krita Version: 5.2.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Filters Assignee: krita-bugs-n...@kde.org Reporter: ra...@raghukamath.com Target Milestone: --- SUMMARY The wave filter is missing in the filter mask and filter layer list. It is present in the Filter > Other > Wave menu. STEPS TO REPRODUCE 1. Open krita 5.2 or nightly build 2. Check the wave filter in Filter > Other > Wave menu. 3. Now try to add this as a filter mask you will find that it is not present in the filter list -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 475557] layer styles do not take in to account content beyond canvas boundary when adding them, but do so when document is reopened.
https://bugs.kde.org/show_bug.cgi?id=475557 Raghavendra kamath changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #2 from Raghavendra kamath --- Hmm. I couldn't reproduce in 5.2 and also in 5.3 strange. We can close this for now. I will keep an eye on this if we encounter it again we will file a report again or reopen this later. The user too can't reproduce it. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 475609] Mitchell scale up image cause artifact on image
https://bugs.kde.org/show_bug.cgi?id=475609 Raghavendra kamath changed: What|Removed |Added CC||ra...@raghukamath.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 475557] New: layer styles do not take in to account content beyond canvas boundary when adding them, but do so when document is reopened.
https://bugs.kde.org/show_bug.cgi?id=475557 Bug ID: 475557 Summary: layer styles do not take in to account content beyond canvas boundary when adding them, but do so when document is reopened. Classification: Applications Product: krita Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: layer styles Assignee: krita-bugs-n...@kde.org Reporter: ra...@raghukamath.com Target Milestone: --- SUMMARY When a user adds a layer style to a layer containing data beyond canvas boundary, Krita doesn't only takes into account the data that appears on canvas. but as soon as you close and reopen the file it applies the layer style to whole content even which is beyond the canvas. And for layer style I believe it is better to take layer content boundary rather than canvas boundary, as far as I know this is how it works in photoshop. People can move layer to the edges and have some content of the layer go beyond the canvas boundary. The issue arises only when adding a layer style, once the document is saved and reopened the layer style works as expected. STEPS TO REPRODUCE 1. Open a new document add some square shapes at the edge of the boundary 2. move these square beyond the canvas boundary a bit 3. Add drop dhadow layer style, you will notice the drop shadow appears for the content that is inside the canvas boundary OBSERVED RESULT When adding layer style content outside the canvas boundary is ignored EXPECTED RESULT Layer boundary instead of canvas boundary should be taken in to account when adding layer style. This was reported on KA by a user, you can see the screenshot showing the issue of cut off drop shadow in the topic - https://krita-artists.org/t/drop-shadow-gap-on-edge-of-image-if-a-layers-pixel-data-is-off-canvas/75469 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 475203] The cursor for 'edit shapes tool' is not obvious on black color
https://bugs.kde.org/show_bug.cgi?id=475203 Raghavendra kamath changed: What|Removed |Added CC||ra...@raghukamath.com --- Comment #1 from Raghavendra kamath --- I think there is a merge request to solve this - https://invent.kde.org/graphics/krita/-/merge_requests/1920 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 461259] Allow assignment of modifier keys to tablet buttons on Wayland
https://bugs.kde.org/show_bug.cgi?id=461259 Raghavendra kamath changed: What|Removed |Added CC||ra...@raghukamath.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 474859] New: ffmpeg is missing from release candidate android build
https://bugs.kde.org/show_bug.cgi?id=474859 Bug ID: 474859 Summary: ffmpeg is missing from release candidate android build Classification: Applications Product: krita Version: 5.2.0-rc1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: ra...@raghukamath.com Target Milestone: --- SUMMARY Users noted that Release candidate version on android is missing ffmpeg. Since built in ffmpeg was one of the highlights of this release, user are dismayed with this issue. here is a post from one such user - https://krita-artists.org/t/krita-5-2-release-candidate-is-out-please-help-us-in-another-round-of-testing/74137/9 STEPS TO REPRODUCE 1. Open release candidate on android 2. try to export timelapse or animation OBSERVED RESULT ffmpeg is missing Android 13 on a Galaxy Tab S9 Ultra. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 474803] New: FFmpeg render presets not working for webm and mp4
https://bugs.kde.org/show_bug.cgi?id=474803 Bug ID: 474803 Summary: FFmpeg render presets not working for webm and mp4 Classification: Applications Product: krita Version: nightly build (please specify the git hash!) Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Dockers/Recorder Assignee: krita-bugs-n...@kde.org Reporter: ra...@raghukamath.com Target Milestone: --- I am using latest nightly build and I have also tested a build given by dmitry for ffmpeg crash. On both the default presets for mp4 an webm fail to render. The mp4 preset is using libx264 changing it to -c:v libopenh264 works and the ffmpeg renders the mp4 files correctly. STEPS TO REPRODUCE 1. Open latest nightly and draw something 2. be sure to record the drawing 3. Export the timelapse with any of the mp4 or webm presets OBSERVED RESULT ffmpeg gives error -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 349785] Intelligent auto-hide mode ("Dodge Windows") that hides the panel only when windows are maximized or move over it
https://bugs.kde.org/show_bug.cgi?id=349785 Raghavendra kamath changed: What|Removed |Added CC|ra...@raghukamath.com | -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 447351] transparent images/formats have no visual indication about the file dimension, which leads to confusion when doing a drag operation
https://bugs.kde.org/show_bug.cgi?id=447351 Raghavendra kamath changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450874] Plasma Wayland remaps virtual tablet input
https://bugs.kde.org/show_bug.cgi?id=450874 Raghavendra kamath changed: What|Removed |Added CC||ra...@raghukamath.com --- Comment #8 from Raghavendra kamath --- I think this is similar to this bug report - https://bugs.kde.org/show_bug.cgi?id=457703 ? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 473603] Exporting the time-lapse trough recorder gives "FFMPEG crashed" error and video is not exported (git 8bacaa0)
https://bugs.kde.org/show_bug.cgi?id=473603 --- Comment #8 from Raghavendra kamath --- Mp4 and mp4 with flash effect doesn't work as shown in the screenshot, webm also gives and error Export failed. FFmpeg message: [vp8_v4l2m2m @ 0x56085c82a740] Could not find a valid device Error initializing output stream 0:0 -- Error while opening encoder for output stream #0:0 - maybe incorrect parameters such as bit_rate, rate, width or height Conversion failed! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 473603] Exporting the time-lapse trough recorder gives "FFMPEG crashed" error and video is not exported (git 8bacaa0)
https://bugs.kde.org/show_bug.cgi?id=473603 --- Comment #7 from Raghavendra kamath --- I think this may be a different issue. Instead of a crash i think individual presets are bugging out like webm and mp4. Because mkv export worked -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 473603] Exporting the time-lapse trough recorder gives "FFMPEG crashed" error and video is not exported (git 8bacaa0)
https://bugs.kde.org/show_bug.cgi?id=473603 --- Comment #6 from Raghavendra kamath --- here is what the ffmpeg log file says /tmp/.mount_krita-meSKCk/usr/bin/ffmpeg -hide_banner -y -framerate 30 -i /home/raghu/Desktop/recorder/20230915142113/%07d.jpg -framerate 30 -start_number 15-1 -i /home/raghu/Desktop/recorder/20230915142113/%07d.jpg -filter_complex [0]loop=5*30:size=1:start=15[main1]; [main1]scale=3500:3500[main2]; [main2]loop=1:size=1:start=0[main3]; [main3]setpts=PTS-STARTPTS[main4]; [1]split [first1][transition1]; [transition1]scale=3500:3500 [transition2]; [transition2]loop='if(gte(2, 1), 1*30, 0)':size=1:start=1[transition3]; [transition3]setpts=PTS-STARTPTS[transition4]; [transition4][main4]xfade=transition=smoothright:duration=0.5:offset=0[v1]; [v1]setpts=PTS-STARTPTS[v2]; [v2]trim=start_frame=1[v3]; [first1]loop='if(gte(2, 1), (2*30) - 0.5, 2*30)':size=1:start=1[preview1]; [preview1]scale=3500:3500[preview2]; [preview2]setpts=PTS-STARTPTS[preview3]; [preview3][v3] concat [final1]; [final1] setpts=PTS-STARTPTS[final2]; [final2] trim=start_frame=1 -c:v libx264 -r 30 -pix_fmt yuv420p /home/raghu/Desktop/recorder/1.mp4 = [mjpeg @ 0x5585084dbec0] EOI missing, emulating Input #0, image2, from '/home/raghu/Desktop/recorder/20230915142113/%07d.jpg': Duration: 00:00:00.50, start: 0.00, bitrate: N/A Stream #0:0: Video: mjpeg (Baseline), yuvj420p(pc, bt470bg/unknown/unknown), 3500x3500 [SAR 96:96 DAR 1:1], 30 fps, 30 tbr, 30 tbn, 30 tbc Input #1, image2, from '/home/raghu/Desktop/recorder/20230915142113/%07d.jpg': Duration: 00:00:00.03, start: 0.00, bitrate: N/A Stream #1:0: Video: mjpeg (Baseline), yuvj420p(pc, bt470bg/unknown/unknown), 3500x3500 [SAR 96:96 DAR 1:1], 30 fps, 30 tbr, 30 tbn, 30 tbc Unknown encoder 'libx264' -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 473603] Exporting the time-lapse trough recorder gives "FFMPEG crashed" error and video is not exported (git 8bacaa0)
https://bugs.kde.org/show_bug.cgi?id=473603 --- Comment #4 from Raghavendra kamath --- Created attachment 161629 --> https://bugs.kde.org/attachment.cgi?id=161629=edit Attaching the error dialog when rednering via built in ffmpeg Sorry this bug is still present in the nightly appimage. The version shows (git fe971a1) Attaching an image to show the error dialog. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 473603] New: Exporting the time-lapse trough recorder gives "FFMPEG crashed" error and video is not exported (git 8bacaa0)
https://bugs.kde.org/show_bug.cgi?id=473603 Bug ID: 473603 Summary: Exporting the time-lapse trough recorder gives "FFMPEG crashed" error and video is not exported (git 8bacaa0) Classification: Applications Product: krita Version: nightly build (please specify the git hash!) Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: * Unknown Assignee: krita-bugs-n...@kde.org Reporter: ra...@raghukamath.com Target Milestone: --- SUMMARY When rendering the timelapse recorded in krita ffmpeg gives error and doesn't export the video. I tried all the formats gif, mkv, webm mp4 all give ffmpeg crashed error. This might also affect animation export too. The ffmpeg path is mapped to "/tmp/.mount_krita-N1yWQW/usr/bin/ffmpeg" STEPS TO REPRODUCE 1. Open latest nightly build and open a document to record a timelapse 2. Open recorder docker and set it up for recording, draw some strokes and stop recording 3. Export the recording using the default preset. OBSERVED RESULT Export doesn't happen and ffmpeg crash error dialog pops up. EXPECTED RESULT Export should happen as usual. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 473131] More than one spaces are ignored in text (git 287099d)
https://bugs.kde.org/show_bug.cgi?id=473131 --- Comment #2 from Raghavendra kamath --- Hi Wolthera, Yes I had already filed this report before asking. So sorry. We can close this -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 473131] New: More than one spaces are ignored in text (git 287099d)
https://bugs.kde.org/show_bug.cgi?id=473131 Bug ID: 473131 Summary: More than one spaces are ignored in text (git 287099d) Classification: Applications Product: krita Version: nightly build (please specify the git hash!) Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Tool/Text Assignee: krita-bugs-n...@kde.org Reporter: ra...@raghukamath.com Target Milestone: --- SUMMARY While adding text block multiple spaces are compressed into one space. STEPS TO REPRODUCE 1. Download latest nightly build and create a new document 2. Add a text block and add more than one space in the text OBSERVED RESULT Multiple spaces are compressed into one EXPECTED RESULT Spaces in text should be kept intact -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 471960] Frequent random crashes
https://bugs.kde.org/show_bug.cgi?id=471960 Raghavendra kamath changed: What|Removed |Added CC||ra...@raghukamath.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 471026] New: Krita regenerates layer thumbnail every time user switches between open documents. (git 21c16b5)
https://bugs.kde.org/show_bug.cgi?id=471026 Bug ID: 471026 Summary: Krita regenerates layer thumbnail every time user switches between open documents. (git 21c16b5) Classification: Applications Product: krita Version: nightly build (please specify the git hash!) Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Layer Stack Assignee: krita-bugs-n...@kde.org Reporter: ra...@raghukamath.com Target Milestone: --- SUMMARY In the recent nightlies when user switches between two or more document the switch has delay and other issues. The major one is the layer thumbnails in the layer docker is regenerated every time the switch happens. This adds to a lag during the switch, the progress bar sometimes shows updating thumbnails. The user can't paint or colour pick during this slight registration time. STEPS TO REPRODUCE 1. Open the test files attached here in krita 2. Switch to subwindow mode in krita settings (don't know if this has any effect) 3. Ctrl tab to switch between these two documents. I am also providing a link to a video which shows how it behaves in my machine. https://box.raghukamath.com/cloud/index.php/s/4z2xe3Sx5g3owfC You can download both test files from here https://box.raghukamath.com/cloud/index.php/s/J3kQoF6SYfW3eLC -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 469109] Gradient dither adds dither to areas which are supposed to be transparent
https://bugs.kde.org/show_bug.cgi?id=469109 --- Comment #6 from Raghavendra kamath --- I too was of the same opinion. I suggested for not adding the option on the IRC. but deif lour said that currently the colour in end point of the gradient is extended so if the gradient is from black to white the white is filled till the end of the canvas no matter where the user places the last end point. So by that logic krita extends the transparency till the end and that is why dithering is applied to whole canvas no matter where you end your gradient, since the fill is extended till the edge of the canvas. Hope I explained it correctly. If we end the gradient where the user places the last end point it would break the existing behavior of coloured gradient. We should check what other software do in this situation. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 469109] Gradient dither adds dither to areas which are supposed to be transparent
https://bugs.kde.org/show_bug.cgi?id=469109 Raghavendra kamath changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #4 from Raghavendra kamath --- I think as deif lou suggests an option to ignore area with transparency would be good. It is okay to add dither to partially transparent area but not for fully transparent area. Also setting it to reported again since this will be closed by bug janitor in 30 days without any resolution. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 469109] New: Gradient dither adds dither to areas which are supposed to be transparent
https://bugs.kde.org/show_bug.cgi?id=469109 Bug ID: 469109 Summary: Gradient dither adds dither to areas which are supposed to be transparent Classification: Applications Product: krita Version: nightly build (please specify the git hash!) Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Tools Assignee: krita-bugs-n...@kde.org Reporter: ra...@raghukamath.com Target Milestone: --- SUMMARY Adding a gradient with dithering enabled adds dither to areas which are transparent. The pattern really very transparent but it becomes obvious when you duplicate the layer 10 to 15 times or just load a selection by selecting opaque or ctrl clicking on layer thumbnail. This pattern gives issues when other effects like mean removal or sharpening are applied or if the layer has multiply blend mode. This also makes the element larger and it becomes a hassle when transforming things as small elements can actually be entire canvas. STEPS TO REPRODUCE 1. Open a new document 2. Delete the background layer content to make the document with transparent background 3. Add a small radial gradient in a corner anywhere with black colour. the preset for the gradient is foreground to transparent. 4. Load a selection based on this layer by ctrl clicking on the layer thumbnail or right click and do select opaque. OBSERVED RESULT Dithers are present across the canvas EXPECTED RESULT Dithering should only be present in place of colour and opaque region -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 468197] 16 bit psd files saved from photoshop show corrupted layers
https://bugs.kde.org/show_bug.cgi?id=468197 Raghavendra kamath changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #6 from Raghavendra kamath --- Here is the test file https://box.raghukamath.com/cloud/index.php/s/xQLfY5BywGBxTdC Sorry it got deleted when I migrated my files to some other drive. This file and all other files saved from photoshop in 16 bit do not load in krita. You can also create a file from photoshop in 16 bit rgb and then test again. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 169225] Parental controls KCM
https://bugs.kde.org/show_bug.cgi?id=169225 Raghavendra kamath changed: What|Removed |Added CC||ra...@raghukamath.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 468197] 16 bit psd files saved from photoshop show corrupted layers
https://bugs.kde.org/show_bug.cgi?id=468197 --- Comment #2 from Raghavendra kamath --- Another krita-artists user reporting the same - https://krita-artists.org/t/16bit-psd-files/52365 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 468197] New: 16 bit psd files saved from photoshop show corrupted layers
https://bugs.kde.org/show_bug.cgi?id=468197 Bug ID: 468197 Summary: 16 bit psd files saved from photoshop show corrupted layers Classification: Applications Product: krita Version: nightly build (please specify the git hash!) Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: ra...@raghukamath.com Target Milestone: --- SUMMARY PSD files which are saved from photoshop and which have 16 bit integer channel rgb colour profiles show corrupted layers. The layers will have glitched data rendering the file useless. I think Krita is is not importing the file properly. 16 bit PSD files which are saved from krita open properly. Here is a test file for your reference. (The file size is a bit large so adding cloud link) https://box.raghukamath.com/cloud/index.php/s/go5BDw78oAkxsNq This issue was also encountered by on of the krita-artists members. here is the post - https://krita-artists.org/t/psds-loading-corrupted/59057 STEPS TO REPRODUCE 1. Download the test file from here 2. Open the file in krita OBSERVED RESULT Colours are glitched on all layers EXPECTED RESULT Colours and the file should appear normal with supported features. System information - Krita Version: 5.2.0-prealpha (git 9920d23) Hidpi: true Qt Version (compiled): 5.15.7 Version (loaded): 5.15.7 OS Information Build ABI: x86_64-little_endian-lp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: linux Kernel Version: 6.2.9-200.fc37.x86_64 Pretty Productname: Fedora Linux 37 (KDE Plasma) Product Type: fedora Product Version: 37 Desktop: KDE Locale Languages: en_US C locale: hi_IN.UTF-8 QLocale current: en QLocale system: hi QTextCodec for locale: UTF-8 OpenGL Info Vendor: "NVIDIA Corporation" Renderer: "NVIDIA GeForce GTX 750 Ti/PCIe/SSE2" Driver version: "4.6.0 NVIDIA 530.41.03" Shading language: "4.60 NVIDIA" Requested format: QSurfaceFormat(version 3.3, options QFlags(), 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(), 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) GL version: 4.6 Supports deprecated functions false Is OpenGL ES: false supportsBufferMapping: true supportsBufferInvalidation: true forceDisableTextureBuffers: false Extensions: GL_NV_parameter_buffer_object GL_NV_texture_rectangle GL_ARB_shader_objects GL_OVR_multiview2 GL_EXT_texture_compression_latc GL_ARB_gpu_shader5 GL_ARB_point_sprite GL_ARB_explicit_uniform_location GL_NV_vertex_array_range2 GL_ARB_copy_buffer GL_ARB_map_buffer_alignment GL_NV_draw_vulkan_image GL_ARB_sparse_buffer GL_EXT_blend_equation_separate GL_KHR_debug GL_NV_explicit_multisample GL_NV_occlusion_query GL_EXT_texture_env_add GL_ARB_shading_language_include GL_ARB_cull_distance GL_NV_gpu_program4_1 GL_NV_uniform_buffer_unified_memory GL_NV_ES1_1_compatibility GL_ARB_texture_query_levels GL_ARB_seamless_cube_map GL_ARB_shader_draw_parameters GL_NV_fragment_program_option GL_NV_vdpau_interop GL_EXT_vertex_array GL_ARB_stencil_texturing GL_EXT_texture_compression_dxt1 GL_NV_vertex_program2 GL_ARB_tessellation_shader GL_NV_fence GL_ARB_invalidate_subdata GL_ARB_framebuffer_object GL_ARB_texture_env_combine GL_ARB_texture_compression_bptc GL_ARB_half_float_vertex GL_ARB_gl_spirv GL_NV_packed_depth_stencil GL_KHR_shader_subgroup GL_ARB_arrays_of_arrays GL_NV_draw_texture GL_EXT_provoking_vertex GL_ARB_transpose_matrix GL_ARB_indirect_parameters GL_ARB_shader_image_load_store GL_EXT_stencil_wrap GL_EXT_stencil_two_side GL_EXT_texture_env_dot3 GL_ARB_query_buffer_object GL_NV_texture_shader2 GL_EXT_blend_func_separate GL_NV_bindless_multi_draw_indirect GL_ATI_draw_buffers GL_ARB_depth_clamp GL_NV_blend_minmax_factor GL_EXT_texture_edge_clamp GL_EXT_vertex_array_bgra GL_ARB_texture_rg GL_NV_conditional_render GL_NV_shader_thread_group GL_ARB_robust_buffer_access_behavior
[krita] [Bug 465086] Clone brush cursor is improperly rendered
https://bugs.kde.org/show_bug.cgi?id=465086 Raghavendra kamath changed: What|Removed |Added CC||ra...@raghukamath.com --- Comment #2 from Raghavendra kamath --- Created attachment 157743 --> https://bugs.kde.org/attachment.cgi?id=157743=edit screenshot showing the x mark In addition to this there is occasional X mark on normal brushes too with an offset. Attaching a screenshot of a normal non clone brush having the x mark appear on canvas randomly -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 467517] New: Hue saturation filter dialog shows black sliders at start (git 14447ec)
https://bugs.kde.org/show_bug.cgi?id=467517 Bug ID: 467517 Summary: Hue saturation filter dialog shows black sliders at start (git 14447ec) Classification: Applications Product: krita Version: nightly build (please specify the git hash!) Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Filters Assignee: krita-bugs-n...@kde.org Reporter: ra...@raghukamath.com Target Milestone: --- SUMMARY In the nightly builds, the hue saturation filter dialog starts up with all the sliders showing on black bar. When the user clicks to change the values the colours appear. STEPS TO REPRODUCE 1. Download krita nightly 2. Create a new document 3. Open Hue saturation filter dialog - Ctrl U or Filters > Adjust > HSV Adjustment ## SYSTEM INFORMATION Krita Version: 5.1.3 Hidpi: true Qt Version (compiled): 5.12.12 Version (loaded): 5.12.12 OS Information Build ABI: x86_64-little_endian-lp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: linux Kernel Version: 6.1.18-200.fc37.x86_64 Pretty Productname: Fedora Linux 37 (KDE Plasma) Product Type: fedora Product Version: 37 Desktop: KDE Locale Languages: en_US C locale: hi_IN.UTF-8 QLocale current: en QLocale system: hi QTextCodec for locale: UTF-8 OpenGL Info Vendor: "Intel" Renderer: "Mesa Intel(R) UHD Graphics 770 (ADL-S GT1)" Version: "4.6 (Compatibility Profile) Mesa 22.3.7" Shading language: "4.60" 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 supportsBufferMapping: true supportsBufferInvalidation: true forceDisableTextureBuffers: false Extensions: "GL_EXT_compiled_vertex_array" "GL_ARB_texture_compression_rgtc" "GL_ARB_transpose_matrix" "GL_AMD_seamless_cubemap_per_texture" "GL_ARB_base_instance" "GL_EXT_shader_framebuffer_fetch_non_coherent" "GL_KHR_parallel_shader_compile" "GL_ARB_ES3_1_compatibility" "GL_ATI_draw_buffers" "GL_ARB_gpu_shader_fp64" "GL_ARB_compute_shader" "GL_AMD_query_buffer_object" "GL_ARB_texture_query_levels" "GL_ARB_depth_clamp" "GL_ARB_shader_precision" "GL_ARB_timer_query" "GL_ARB_direct_state_access" "GL_EXT_texture_object" "GL_NV_texture_env_combine4" "GL_EXT_gpu_program_parameters" "GL_EXT_texture_env_add" "GL_ARB_seamless_cube_map" "GL_EXT_texture_swizzle" "GL_ARB_depth_texture" "GL_ARB_shader_atomic_counter_ops" "GL_ARB_clear_buffer_object" "GL_AMD_vertex_shader_layer" "GL_ARB_provoking_vertex" "GL_EXT_texture_cube_map" "GL_EXT_framebuffer_multisample_blit_scaled" "GL_EXT_texture_compression_rgtc" "GL_ARB_shader_storage_buffer_object" "GL_NV_texgen_reflection" "GL_EXT_packed_float" "GL_EXT_texture_sRGB" "GL_ARB_transform_feedback2" "GL_ARB_texture_multisample" "GL_EXT_framebuffer_blit" "GL_ARB_depth_buffer_float" "GL_ARB_viewport_array" "GL_EXT_provoking_vertex" "GL_EXT_texture3D" "GL_ATI_fragment_shader" "GL_ARB_texture_mirrored_repeat" "GL_ARB_pipeline_statistics_query" "GL_ARB_vertex_shader" "GL_ARB_explicit_attrib_location" "GL_EXT_separate_specular_color" "GL_EXT_packed_pixels" "GL_ARB_draw_instanced" "GL_EXT_vertex_array_bgra" "GL_EXT_texture_rectangle" "GL_ARB_polygon_offset_clamp" "GL_ARB_shader_atomic_counters" "GL_ARB_vertex_type_2_10_10_10_rev" "GL_EXT_fog_coord" "GL_ARB_multi_draw_indirect" "GL_SUN_multi_draw_arrays" "GL_ARB_copy_image" "GL_EXT_shadow_funcs" "GL_ARB_multisample" "GL_ARB_texture_filter_anisotropic" "GL_ARB_fragment_layer_viewport" "GL_EXT_texture_edge_clamp" "GL_ARB_shader_objects" "GL_ATI_texture_compression_3dc" "GL_EXT_vertex_array" "GL_ARB_conservative_depth" "GL_ARB_vertex_buffer_object" "GL_ARB_uniform_buffer_object" "GL_ARB_shader_image_size"
[krita] [Bug 461894] Paste into active layer will paste at the canvas center
https://bugs.kde.org/show_bug.cgi?id=461894 --- Comment #3 from Raghavendra kamath --- There is a feedback thread on KA about this https://krita-artists.org/t/copy-and-paste-to-active-layer-dont-respect-the-position-of-copy-anymore/52121/17 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 461894] Paste into active layer will paste at the canvas center
https://bugs.kde.org/show_bug.cgi?id=461894 Raghavendra kamath changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||ra...@raghukamath.com --- Comment #2 from Raghavendra kamath --- I can confirm this on Linux. This is indeed annoying -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 463113] Pasting as reference when plain text is in the clipboard causes a crash
https://bugs.kde.org/show_bug.cgi?id=463113 Raghavendra kamath changed: What|Removed |Added CC||ra...@raghukamath.com Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Raghavendra kamath --- I can confirm this on Fedora 37 with latest nightly build. I encountered it day before yesterday when I was pasting an image as reference with the short-cut, but I didn't understand what happened now I know why it crashed I was also copy pasting lot of text at the time -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 462879] Krita doesn't switch and makes newly imported or created layer active [git 9ba7789]
https://bugs.kde.org/show_bug.cgi?id=462879 --- Comment #1 from Raghavendra kamath --- This happens even to the newly added or created layer via the add button in the layer docker. Ideally Krita should switch to the newly created layer -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 462879] Krita doesn't switch and makes newly imported or created layer active [git 9ba7789]
https://bugs.kde.org/show_bug.cgi?id=462879 Raghavendra kamath changed: What|Removed |Added Summary|Krita doesn't switch and|Krita doesn't switch and |makes newly imported layer |makes newly imported or |active when importing via |created layer active [git |menu or drag and drop [git |9ba7789] |9ba7789]| -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 462879] New: Krita doesn't switch and makes newly imported layer active when importing via menu or drag and drop [git 9ba7789]
https://bugs.kde.org/show_bug.cgi?id=462879 Bug ID: 462879 Summary: Krita doesn't switch and makes newly imported layer active when importing via menu or drag and drop [git 9ba7789] Classification: Applications Product: krita Version: nightly build (please specify the git hash!) Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Layer Stack Assignee: krita-bugs-n...@kde.org Reporter: ra...@raghukamath.com Target Milestone: --- SUMMARY This is most probably a side effect of the new check-box feature added in the layer docker. When the user imports a new layer krita doesn't switch active layer to the newly imported layer. user has to click on it again to activate it. Generally when people import a new layer they intend to move it or transform it or perform other operations on it. So it is ideal to have the newly imported layer to become automatically active. STEPS TO REPRODUCE 1. Open krita from the nightly build and create a new document 2. Import a layer either via Layer > Import/Export > Import layer or drag and drop an image 3. Notice the new layer is not automatically selected and active -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 352519] Delete, cut copy and paste recursively from a group or multiple selected layer
https://bugs.kde.org/show_bug.cgi?id=352519 Raghavendra kamath changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #11 from Raghavendra kamath --- I am closing this as this is already implemented now. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 461556] Adding a reference image via tool option or drag and drop crashes krita (git 4225dad)
https://bugs.kde.org/show_bug.cgi?id=461556 --- Comment #3 from Raghavendra kamath --- I noticed that the nightly build hangs when opening images which have reference images embeded. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 461631] Whenever I click on customised Inc 25 brush (on a main screen, in settings), Krita immediately crashes. So, I can’t remove or change this brush in any way.
https://bugs.kde.org/show_bug.cgi?id=461631 Raghavendra kamath changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #4 from Raghavendra kamath --- I can confirm that the brush attached here crashes krita on my system. The discussion is here on KA - https://krita-artists.org/t/brush-bug-and-krita-crash/51346/7 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 461631] Whenever I click on customised Inc 25 brush (on a main screen, in settings), Krita immediately crashes. So, I can’t remove or change this brush in any way.
https://bugs.kde.org/show_bug.cgi?id=461631 Raghavendra kamath changed: What|Removed |Added CC||ra...@raghukamath.com --- Comment #3 from Raghavendra kamath --- Created attachment 153619 --> https://bugs.kde.org/attachment.cgi?id=153619=edit brush file that makes krita crash -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 461556] New: Adding a reference image via tool option or drag and drop crashes krita (git 4225dad)
https://bugs.kde.org/show_bug.cgi?id=461556 Bug ID: 461556 Summary: Adding a reference image via tool option or drag and drop crashes krita (git 4225dad) Classification: Applications Product: krita Version: nightly build (please specify the git hash!) Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Tools/Reference Images Assignee: krita-bugs-n...@kde.org Reporter: ra...@raghukamath.com Target Milestone: --- SUMMARY Dragging and dropping an image to add it as a reference image crashes krita. It also crashes when I got to add reference image via the tool options of the reference image tool. STEPS TO REPRODUCE 1. Open a new document and drag and drop an image and choose insert as reference image. Alternatively 1. Open a new document select the reference image tool and got to tool option docker. 2. Click on the plus icon to add a reference image. Then choose a png or jpg image OBSERVED RESULT Krita crashes on choosing and image EXPECTED RESULT A reference image should be added without crashing krita -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 338132] Add mechanism to show/hide dockers floating using shorcuts
https://bugs.kde.org/show_bug.cgi?id=338132 Raghavendra kamath changed: What|Removed |Added CC||rainco...@gmail.com --- Comment #7 from Raghavendra kamath --- *** Bug 441841 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 441841] Assignable shortcuts for dockers
https://bugs.kde.org/show_bug.cgi?id=441841 Raghavendra kamath changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||ra...@raghukamath.com --- Comment #1 from Raghavendra kamath --- *** This bug has been marked as a duplicate of bug 338132 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 460461] New: Using line tool repeatedly and undoing results in irrecoverable data loss of tile data.
https://bugs.kde.org/show_bug.cgi?id=460461 Bug ID: 460461 Summary: Using line tool repeatedly and undoing results in irrecoverable data loss of tile data. Classification: Applications Product: krita Version: 5.1.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: OpenGL Canvas Assignee: krita-bugs-n...@kde.org Reporter: ra...@raghukamath.com Target Milestone: --- SUMMARY I think this bug is of a bit serious nature as it results in data loss. We got two users complaining on KA about tile crashing and resulting in data loss while using the line tool and undoing the actions repeatedly. I am copy pasting Freyalupens remarks here : "For demonstration, here’s a video I recorded on 5.2.x (git 939408c), just repeatedly using the line tool for a few minutes; brush is “b) Basic-2 Opacity”. Before that I was using “b) Basic-1”, but nothing was happening, so I switched brushes. Could be it only happens with certain brushes, could be the act of switching brushes somehow triggers it, could be I was just (un)lucky. After a while it just randomly happens, trying to undo it causes a safe assert in libs/image/tiles3/kis_memento_manager.cc, line 275, and redoing in line 332. (For fun I turned on all the logging options. The Unknown transform parameter : "" being logged is from kis_dynamic_sensor::id2sensor(). The brush is trying to use some sort of incorrect sensor or something, but the message is very unhelpfully worded.)" You can check the thread where this bug is discussed here - https://krita-artists.org/t/using-brush-or-line-tools-sometimes-delete-part-of-the-layer-in-a-square-rectangle-pattern/48985 There is also a video of the bug happening in the thread linked above. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 460299] New: Wrap around mode shows artefacts and broken tiles for brushes made with engines than pixel brush engine. [git 2264a44]
https://bugs.kde.org/show_bug.cgi?id=460299 Bug ID: 460299 Summary: Wrap around mode shows artefacts and broken tiles for brushes made with engines than pixel brush engine. [git 2264a44] Classification: Applications Product: krita Version: nightly build (please specify the git hash!) Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: CPU Canvas Assignee: krita-bugs-n...@kde.org Reporter: ra...@raghukamath.com Target Milestone: --- SUMMARY Wrap around mode doesn't work correctly and shows artefacts and broken seamless tiling when used with brush engine other than pixel brush. STEPS TO REPRODUCE 1. Open Krita and initiate wrap around mode. 2. Choose a brush which belongs to a brush engine other than pixel brush engine and paint -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 458475] Performance highly degraded with filters
https://bugs.kde.org/show_bug.cgi?id=458475 Raghavendra kamath changed: What|Removed |Added CC||tomtomtomreportingin@gmail. ||com --- Comment #11 from Raghavendra kamath --- *** Bug 459517 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 459517] [master] Performance when working under filter layers is significantly worse (likely due to layer thumbnail generation)
https://bugs.kde.org/show_bug.cgi?id=459517 Raghavendra kamath changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||ra...@raghukamath.com --- Comment #1 from Raghavendra kamath --- *** This bug has been marked as a duplicate of bug 458475 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 459512] Opening a psd file which has fill layer will make krita unresponsive or crash. Having the psd in recent document will make krita to hang on startup
https://bugs.kde.org/show_bug.cgi?id=459512 Raghavendra kamath changed: What|Removed |Added Severity|normal |crash -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 459512] New: Opening a psd file which has fill layer will make krita unresponsive or crash. Having the psd in recent document will make krita to hang on startup
https://bugs.kde.org/show_bug.cgi?id=459512 Bug ID: 459512 Summary: Opening a psd file which has fill layer will make krita unresponsive or crash. Having the psd in recent document will make krita to hang on startup Classification: Applications Product: krita Version: nightly build (please specify the git hash!) Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: ra...@raghukamath.com Target Milestone: --- SUMMARY If a psd file contains fill layer either saved from photoshop or from krita itself. krita crashes or hangs when opening that file. if you reopen krita and if this file is in the recent document list, krita will hang or crash on startup. STEPS TO REPRODUCE 1. Create a new document. 2. Add a new fill layer with any colour 3. Save the document as PSD and now close krita and open that PSD. OBSERVED RESULT Krita hangs or crashes. EXPECTED RESULT File should be opened normally This happens on both windows and linux. This was first reported on krita-artists here - https://krita-artists.org/t/krita-5-1-1-crash-on-startup-reinstallation-does-not-work/48185/1 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412232] Color Inconsistencies in Krita neutral theme on welcome screen
https://bugs.kde.org/show_bug.cgi?id=412232 Raghavendra kamath changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #5 from Raghavendra kamath --- Yes we can close this. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 457636] Feature to map pen buttons to keys / sequence of keys or commands
https://bugs.kde.org/show_bug.cgi?id=457636 --- Comment #10 from Raghavendra kamath --- Can we test it in neon? Is it in the same settings kcm? Thanks -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 457705] There is no option to edit/adjust and set the pressure curve of the graphic tablet in the tablet KCM [wayland]
https://bugs.kde.org/show_bug.cgi?id=457705 --- Comment #2 from Raghavendra kamath --- Created attachment 151216 --> https://bugs.kde.org/attachment.cgi?id=151216=edit Screenshot showing an edited curve with bezier handles The red dots in the screenshot are bezier handles the artist can use them to tweak the curve. The position of the points can be moved too to set the maximum pressure or minimum starting pressure. To get an idea also check the pressure curve setting in krita -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 457705] There is no option to edit/adjust and set the pressure curve of the graphic tablet in the tablet KCM [wayland]
https://bugs.kde.org/show_bug.cgi?id=457705 --- Comment #1 from Raghavendra kamath --- Created attachment 151215 --> https://bugs.kde.org/attachment.cgi?id=151215=edit screenshot showing the edit dialog -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 457705] New: There is no option to edit/adjust and set the pressure curve of the graphic tablet in the tablet KCM [wayland]
https://bugs.kde.org/show_bug.cgi?id=457705 Bug ID: 457705 Summary: There is no option to edit/adjust and set the pressure curve of the graphic tablet in the tablet KCM [wayland] Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_tablet Assignee: plasma-b...@kde.org Reporter: ra...@raghukamath.com CC: aleix...@kde.org Target Milestone: --- SUMMARY In earlier KCM for the graphic tablets there was a way to edit the curve for pressure input data coming from the tablet. Artists have different style of painting, some press the tablet hard and some softly to make a mark. To adjust ones style artists use the pressure curve to regulate how much pressure is needed to make a mark on the canvas. This feature is missing in the newer implementation of the tablet KCM under wayland. Some pens have both eraser tip and normal tip so ideally pressure curve of both the sides needs to be adjusted. I am attaching a screenshot of the old tablet KCM to show the edit dialog. The edit dialog also showed the amount of pressure the artist is applying in blue to help them gauge it better. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 457704] New: Drag handle button in custom area selection option scrolls the KCM page instead of resizing the selection [wayland]
https://bugs.kde.org/show_bug.cgi?id=457704 Bug ID: 457704 Summary: Drag handle button in custom area selection option scrolls the KCM page instead of resizing the selection [wayland] Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_tablet Assignee: plasma-b...@kde.org Reporter: ra...@raghukamath.com CC: aleix...@kde.org Target Milestone: --- SUMMARY *** There is a drag handle button to select a custom area of the screen to map it to the tablet. This button is a bit hard to use by tablet as well as mouse. If it is dragged vertically it scrolls the entire kcm page STEPS TO REPRODUCE 1. Go to tablet configuration page in systemsettings under wayland 2. choose custom area in the options and click and drag the drag handle button. OBSERVED RESULT Whole kcm screen scrolls up EXPECTED RESULT A selection outline drag should be initiated. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 457636] Ability to map pen and tablet buttons to keys / sequence of keys or commands doesn't exist in tablet KCM [wayland]
https://bugs.kde.org/show_bug.cgi?id=457636 --- Comment #8 from Raghavendra kamath --- Created attachment 151214 --> https://bugs.kde.org/attachment.cgi?id=151214=edit Screenshot showing tablet button mapping from old kcm -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 457636] Ability to map pen and tablet buttons to keys / sequence of keys or commands doesn't exist in tablet KCM [wayland]
https://bugs.kde.org/show_bug.cgi?id=457636 Raghavendra kamath changed: What|Removed |Added Summary|Tablet Tools Configuration |Ability to map pen and ||tablet buttons to keys / ||sequence of keys or ||commands doesn't exist in ||tablet KCM [wayland] --- Comment #7 from Raghavendra kamath --- Adding screenshot of the -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 457636] Tablet Tools Configuration
https://bugs.kde.org/show_bug.cgi?id=457636 Raghavendra kamath changed: What|Removed |Added CC||ra...@raghukamath.com --- Comment #6 from Raghavendra kamath --- Should I file a different report for button mapping on the tablets as well? or is it okay to bundle all the buttons on pen and tablet in here? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 433045] Tablet configuration does not exist in wayland
https://bugs.kde.org/show_bug.cgi?id=433045 --- Comment #25 from Raghavendra kamath --- A bug report for not being able to select tablet surface area to map to entire screen area - https://bugs.kde.org/show_bug.cgi?id=457703 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 457703] New: There is no option to select an area on the tablet to map it to the entire screen [wayland]
https://bugs.kde.org/show_bug.cgi?id=457703 Bug ID: 457703 Summary: There is no option to select an area on the tablet to map it to the entire screen [wayland] Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_tablet Assignee: plasma-b...@kde.org Reporter: ra...@raghukamath.com CC: aleix...@kde.org Target Milestone: --- Created attachment 151213 --> https://bugs.kde.org/attachment.cgi?id=151213=edit screenshot showing how tablet area is mapped in exisiting kcm SUMMARY The recent feature addition to new graphic tablet kcm under Wayland is awesome and a huge relief. However currently it lacks an option to select a portion of the tablet surface to map that area to the screen [monitor] area. User can draw a custom area currently but this is for selecting the portion of the screen and not the tablet. While selecting a portion of the are of screen to limit tablet input to that area is good. Majority of users would choose to select a position of the tablet surface to map it to entire screen. A use case for this is user having a large non graphic tablet (the non display one) and wanting to use only a portion of the tablet surface for the screen. STEPS TO REPRODUCE 1. Boot into neon unstable under wayland and go to tablet section in the system settings 2. try to select an are of the tablet to map it to entire screen. There is custom area but it only allows users to select the screen are and not the tablet area. OBSERVED RESULT No way to visually select tablet surface area to map it to entire screen EXPECTED RESULT User should be shown a graphic of the tablet currently they are using and a way to draw and select area of the tablet surface to map it to entire screen. I am attaching a screenshot of the existing tablet KCM under xorg to show how it is achieved in it. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 433045] Tablet configuration does not exist in wayland
https://bugs.kde.org/show_bug.cgi?id=433045 --- Comment #19 from Raghavendra kamath --- (In reply to Aleix Pol from comment #17) > Please try it. Hi Aleix, I tried the tablet configuration page in the KCM, the problem of the aspect ratio is solved by the second option in the dropdown I think it is "Fit output in tablet". I would prefer this to be the default option. However these are some of my observation. 1 - the cursor when using graphic tablet is a + cursor and not the regular arrow cursor of breeze. 2 - The drag to resize handle to adjust custom area doesn't work properly with the tablet as well as mouse. For me it only worked if I dragged horizontally and not vertically. When I tried to drag in diagonally to reduce the area of the screen it scrolled the whole page. 3 - There is only way to draw active on the screen to be used by entire tablet surface and there is no way (at-least visually) to draw or select an area of the tablet to be mapped to entire screen. This is use case is much more prevalent than mapping a portion of screen to entire tablet surface. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 433045] Tablet configuration does not exist in wayland
https://bugs.kde.org/show_bug.cgi?id=433045 --- Comment #16 from Raghavendra kamath --- @Aleix Pol thanks for the recent feature of mapping the portion of the screen to tablet. Is mapping a portion of the tablet to target screen possible with this MR? Because that is more important than mapping portion of screen to entire tablet area. More often the screen aspect ratio is different than the tablet area aspect ratio and when drawing a perfect circle we get an egg shape -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 433045] Tablet configuration does not exist in wayland
https://bugs.kde.org/show_bug.cgi?id=433045 --- Comment #11 from Raghavendra kamath --- Created attachment 150198 --> https://bugs.kde.org/attachment.cgi?id=150198=edit screenshot showing the dialog box for remaping individual button -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 433045] Tablet configuration does not exist in wayland
https://bugs.kde.org/show_bug.cgi?id=433045 --- Comment #10 from Raghavendra kamath --- Created attachment 150197 --> https://bugs.kde.org/attachment.cgi?id=150197=edit screenshot showing the button on stylus This is the screenshot showing the buttons on the stylus -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 433045] Tablet configuration does not exist in wayland
https://bugs.kde.org/show_bug.cgi?id=433045 --- Comment #9 from Raghavendra kamath --- Created attachment 150196 --> https://bugs.kde.org/attachment.cgi?id=150196=edit screenshot showing the express button on tablet The current KCM for tablets under X11 is perfect and gives extensive options. This is great reference of how it should work and look. I am attaching screenshots of existing KCM for your reference of remapping buttons on the tablet and also for remapping button of the stylus. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 450961] Add support for open / import and export of photoshop's PSB file format
https://bugs.kde.org/show_bug.cgi?id=450961 --- Comment #5 from Raghavendra kamath --- Please download the test file from the following link https://box.raghukamath.com/cloud/index.php/s/BSHaFWTHySomt6s The tarball has screenshots of layers for your reference too -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 450961] Add support for open / import and export of photoshop's PSB file format
https://bugs.kde.org/show_bug.cgi?id=450961 --- Comment #4 from Raghavendra kamath --- I understand I'll arrange for a psb test file. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 450961] Add support for open / import and export of photoshop's PSB file format
https://bugs.kde.org/show_bug.cgi?id=450961 --- Comment #2 from Raghavendra kamath --- I can provide you psb files made with photoshop. I think we already have psb import support but it is not proper? and it would be best to have psb export too -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 450961] New: Add support for open / import and export of photoshop's PSB file format
https://bugs.kde.org/show_bug.cgi?id=450961 Bug ID: 450961 Summary: Add support for open / import and export of photoshop's PSB file format Product: krita Version: 5.0.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: ra...@raghukamath.com Target Milestone: --- SUMMARY .PSB is a format are used by photoshop to handle large documents, particularly documents over 2 gb of file size. When we try to save a psd file from Krita and if the size goes above 2gb photoshop doesn't open it saying incompatible psd version. This is due to a fake limitation of 2gb file size. Often times users have a situation to deal with psb files while working and collaborating with thirdparties using photoshop and PSB file format compatibility comes in the way. I would like to request adding support for opening psb and saving to psb to ease this situation. This is my personal experience too and also saw a recent request on reddit - https://www.reddit.com/r/krita/comments/t333jt/opening_psb_workaround/ -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 447906] Thumbnailer Previews Broken for kra, xcf, png (not jpg, mp4, mkv)
https://bugs.kde.org/show_bug.cgi?id=447906 Raghavendra kamath changed: What|Removed |Added CC||ra...@raghukamath.com -- You are receiving this mail because: You are watching all bug changes.
[wacomtablet] [Bug 450758] New: Settings changed through wacom kcm are not applied and do not work
https://bugs.kde.org/show_bug.cgi?id=450758 Bug ID: 450758 Summary: Settings changed through wacom kcm are not applied and do not work Product: wacomtablet Version: 3.2.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: general Assignee: jazzv...@gmail.com Reporter: ra...@raghukamath.com Target Milestone: --- SUMMARY When I try to change any settings like assign keys to button on the pad or change the mapping of the tablet area, the settings are not applied or work. STEPS TO REPRODUCE 1. Open tablet kcm and assign some keys to button or map the tablet areas and press apply 2. Check if the settings are applied. Operating System: Fedora Linux 35 KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.16.9-200.fc35.x86_64 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-4790K CPU @ 4.00GHz Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 750 Ti/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 447841] New: Rate parameter in the Color section is not documented
https://bugs.kde.org/show_bug.cgi?id=447841 Bug ID: 447841 Summary: Rate parameter in the Color section is not documented Product: krita Version: 5.0.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Documentation Assignee: krita-bugs-n...@kde.org Reporter: ra...@raghukamath.com Target Milestone: --- I tried to find information about the rate parameter that is listed under the Color section of brush editor but couldn't find it. I think it is not documented yet. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 447393] Overlay icons that show up when hovering over folders and files in browse mode have white icons on gray background
https://bugs.kde.org/show_bug.cgi?id=447393 Raghavendra kamath changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #1 from Raghavendra kamath --- With a update to libraries this bug got fixed by itself. So closing this now -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 447393] New: Overlay icons that show up when hovering over folders and files in browse mode have white icons on gray background
https://bugs.kde.org/show_bug.cgi?id=447393 Bug ID: 447393 Summary: Overlay icons that show up when hovering over folders and files in browse mode have white icons on gray background Product: gwenview Version: 21.04.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: ra...@raghukamath.com Target Milestone: --- Created attachment 144790 --> https://bugs.kde.org/attachment.cgi?id=144790=edit screenshot showing white icons on gray background SUMMARY The overlay action icons that show up when the user hovers over an folder or an image in browse mode have white coloured icons on gray background. It makes it hard to see what the icon is for. There is also no tool tip text for these icons. Moreover some actions like rotate which should be shown on images also show up on folders too, where they do nothing obviously. STEPS TO REPRODUCE 1. Open gwenview and click on the browse button in the top tool bar. 2. Hover over a folder or image while browsing. I am adding a screenshot for your reference Operating System: Fedora Linux 35 KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 Kernel Version: 5.15.10-200.fc35.x86_64 (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 447351] New: transparent images/formats have no visual indication about the file dimension, which leads to confusion when doing a drag operation
https://bugs.kde.org/show_bug.cgi?id=447351 Bug ID: 447351 Summary: transparent images/formats have no visual indication about the file dimension, which leads to confusion when doing a drag operation Product: dolphin Version: 21.08.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: ra...@raghukamath.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 144760 --> https://bugs.kde.org/attachment.cgi?id=144760=edit screenshot showing transparent images in dolphin without file dimension border In Dolphin transparent images and file formats which support transparent thumbnails do not have any indication about their file dimensions. They just show empty area around them. User has to guess the empty area between files while doing a drag ans select operation. Jpg and other formats have nice shadow around them, but transparent images do not have this. while this is inconsistent On vdg room I understood that this is done to avoid ugly rectangle around icons. Having rectangle border around icons would be odd and look ugly, I think there should be some indication of the image area. Looking at macos and windows I see that they show a box around the element on hover. Macos shows name and element in separate highlight box on hover. Our own app gwenview also has this feature , it shows a blue box around the file dimension on hover. I think having this box on hover would solve this issue of user getting confused about the file dimension boundary. I am attaching a screenshot of a scenario where I have few transparent png images. Often common case when you render animation as png sequences. You can see that it becomes hard to know where the image starts and where empty dolphin window is to start a selection drag and not drag the image itself. -- You are receiving this mail because: You are watching all bug changes.
