[krita] [Bug 396672] Krita does not save metadata of imported images
https://bugs.kde.org/show_bug.cgi?id=396672 --- Comment #3 from Danas --- Hi David, I kind of wanted to slip without someone noticing photo editing (which seems to be a dark horse here). Sneaky me :) but Krita makes a very fine image editing in various applications in addition to digital painting. And I believe it is a bug for Krita to loose layer information in kra files once you close and open it later. It something like text editor that would loose numbers or certain phrases once you reopen your novel document to continue on writing. It's not a feature request for a new feature for photo editing stuff, but asking for a function to work properly. If that is possible to do. When it comes to exporting images without metadata you just don't merge the layers and even when you do merge, krita asks what you wanna do with metadata. By the looks of it, it seems that krita prioritizes no inclusion of metada, but was designed to support it in a basic way. So I still think that this is a valid request. Otherwise all the wonderful animation functionality of Krita could be questioned...why dp needs animation then? why not stop at digital painting only? why does it need to have a text tool? This is my point of view. Metadata support was there for a very long time and I see no reason to eliminate functionality or ignore that something is not working quite right. Or is photography not a form of art that could adapt digital painting for artistic purposes? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396672] Krita does not save metadata of imported images
https://bugs.kde.org/show_bug.cgi?id=396672 --- Comment #2 from Danas --- Hi David, I kind of wanted to slip without someone noticing photo editing (which seems to be a dark horse here). Sneaky me :) but Krita makes a very fine image editing in various applications in addition to digital painting. And I believe it is a bug for Krita to loose layer information in kra files once you close and open it later. It something like text editor that would loose numbers or certain phrases once you reopen your novel document to continue on writing. It's not a feature request for a new feature for photo editing stuff, but asking for a function to work properly. If that is possible to do. When it comes to exporting images without metadata you just don't merge the layers and even when you do merge, krita asks what you wanna do with metadata. By the looks of it, it seems that krita prioritizes no inclusion of metada, but was designed to support it in a basic way. So I still think that this is a valid request. Otherwise all the wonderful animation functionality of Krita could be questioned...why dp needs animation then? why not stop at digital painting only? why does it need to have a text tool? This is my point of view. Metadata support was there for a very long time and I see no reason to eliminate functionality or ignore that something is not working quite right. Or is photography not a form of art that could adapt digital painting for artistic purposes? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396672] New: Krita does not save metadata of imported images
https://bugs.kde.org/show_bug.cgi?id=396672 Bug ID: 396672 Summary: Krita does not save metadata of imported images Product: krita Version: git master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Layer Stack Assignee: krita-bugs-n...@kde.org Reporter: danas.a...@gmail.com Target Milestone: --- Hello, I am experiencing an issue with Krita, it doesn't save and keep meta data like exif information in imported layers. The best example is when you want to add some art to photos, you can make a complicated edit of image, save it to krita document file (*.kra) and when you open the kra file again, no metadata is present in layers that should have it. But metadata is very useful to keep your stuff organized and it would be great if Krita would keep each layer metada all the time for as many modifications of krita document as needed. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396445] Shortcut for Invert color is missing
https://bugs.kde.org/show_bug.cgi?id=396445 Danas changed: What|Removed |Added CC||danas.a...@gmail.com --- Comment #2 from Danas --- Hello, I also have this issue and it drives me nuts. Ctrl + i is just in my blood, it's really odd when it is missing. Would be great to have it back. It disappeared sometime with Krita 4.1 series. Last two releases has something changed because in keita 4.0 things were normal. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 391487] Krita ignores PNG EXIF data
https://bugs.kde.org/show_bug.cgi?id=391487 --- Comment #4 from Danas --- I am not good at technical details, but it appears that it just doesn;t want to accept EXIF from PNG. I use Darktable for processing RAW images, so everything I through to Krita is directly from Darktable with no modifications. If have JPG or TIFF it is fine, but if it is PNG then it doesn;t work, exif seems to not exist. But in Gwenview and GIMP 2.9 everything is fine with Exif and it shows it as usually. I wonder if it would be possible to force Krita to always keep Exif data from first layer? One thing I noticed that many times Krita doesn;t load exif once I close and load the .kra file even with JPG and Tiffs. It would be cool if it was possible to force Krita to always keep Exif data from the first loaded layer and have it as an option for krita document so that when you export to JPG or any other format the one wouldn't need to merge all layers and give priority to the first layer metadata. The document could always use the metadata of the first layer. Just a thought. Nowadays I use Krita a lot for photo editing instead of painting which is not primary function of Krita. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 391487] Krita ignores PNG EXIF data
https://bugs.kde.org/show_bug.cgi?id=391487 --- Comment #1 from Danas --- Sample image to test the bug https://drive.google.com/open?id=1Z7P78WYmJWo9GfsU3MtqoFaM0LXZ2ej3 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 391487] New: Krita ignores PNG EXIF data
https://bugs.kde.org/show_bug.cgi?id=391487 Bug ID: 391487 Summary: Krita ignores PNG EXIF data Product: krita Version: 3.3.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: danas.a...@gmail.com Target Milestone: --- Hello, I just faced with an issue that Krita seems to don;t see exif data in PNG images, it is fine with TIFF and JPG files, but when it comes to PNG, it looks like Krita doesn't see Exif data. Checked with Image viewer and GIMP 2.9 and same file shows Exif as it should, but Krita seems to ignore that there is exif data. Checked on Krita 3.3.3 and Krita 4 beta. same result. OS: Kubuntu 17.10 latest updates. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 382812] Mouse icon artifacts block display of desktop content
https://bugs.kde.org/show_bug.cgi?id=382812 --- Comment #26 from Danas --- (In reply to Massimo Callegari from comment #25) > @Morgan Cox I didn't say it's a solution. It's another dirty workaround to > compensate a SDDM bug. > Turns out XRender compositing affects VLC too which is pretty bad. > > Another 'workaround' is to use 'slim' instead of SDDM. > > I thought about opening a ticket in the SDDM GitHub page...but they have > 200+ open issues and doesn't seem they care that much. I think SDDM should > be abandoned for good. > > And I do totally understand your comment about Linux newbies. At the moment > I don't feel suggesting Neon/Plasma to anyone either. I have discovered that Kubuntu 17.10 isn;t affected by this bug. Quite some time has passed since my last time checking on this bug. So I decided to give Kubuntu and Kde Neon another go, since I heard there were some updates and wanted to see how it works as I wanted to go back to 16.04 LTS but both KDE Neon and Kubuntu 16.04 with latest greatest updates gave me the damned cursor bug with Nvidia drivers. tried different version, no difference. Then I thought what if it was kernel related, Kubuntu 17.10 comes with a newer kernel which at the time was 4.13 so I upgraded my Kubuntu 16.04 to Linux Kernel 4.13 and the issue is still there. Again went through many recommended workarounds and none seemed to be the good one. Went back to Kubuntu 17.10 again and have no damned cursor bug. A good starting point too look at might be the differences between Kubuntu 17.10 and Kubuntu 16.04 because Kubuntu 17.10 seems to have it solved for the users. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 382812] Mouse icon artifacts block display of desktop content
https://bugs.kde.org/show_bug.cgi?id=382812 Danas changed: What|Removed |Added CC||aff...@gmail.com --- Comment #19 from Danas --- this is definitely not only KDE Neon specific, this issue takes place on I guess every Ubuntu based OS that use KDE Plasma 5, I did a clean system installation of KDE neon and got this issue, thinking it might be because of KDE Neon I went back to Kubuntu 16.04 (also a fresh install) and the issue appeared again when my system was enabled to use Nvidia instead of Intel card. This annoying bug affect KDE users on various distro basis ( as seen mostly Ubuntu based) and has something to do with the latest updates (up until writing of this comment), KDE Plasma 5 ( older and latest releases) and systems with Nvidia cards ( as far as I was able to track). Note that other DEs doesn't seem to have this issue, KDE Plasma 5 developers should put some eyes on this, we don;t want to see users not recommending Plasma 5, it is too awesome to be ruined by something like this. It might look like a small issue but it ruins the usability to the most common daily tasks, that is really not good. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381533] Square box behind mouse cursor/pointer blocks and corrupts zones at which it's pointing
https://bugs.kde.org/show_bug.cgi?id=381533 Danas changed: What|Removed |Added CC||aff...@gmail.com --- Comment #13 from Danas --- Can confirm this bug, after upgrading to the latest Kubuntu 16.04 I also get this issue which ruins usability quite a lot. Nvidia Geforce 540M a very old card, but looks like the bug affects majority Nvidia cards. On intel Chip it all is fine. -- You are receiving this mail because: You are watching all bug changes.
