[krita] [Bug 375874] Vector isn't working at all
https://bugs.kde.org/show_bug.cgi?id=375874 Boudewijn Rempt <b...@valdyas.org> changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID CC||b...@valdyas.org --- Comment #1 from Boudewijn Rempt <b...@valdyas.org> --- Hi Dominique, Please read the manual: https://docs.krita.org/Vector_Layers I'm afraid that this isn't a bug... -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 375873] PNG Need Option to Preserve Colors on Full Alpha
https://bugs.kde.org/show_bug.cgi?id=375873 Boudewijn Rempt <b...@valdyas.org> changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED CC||b...@valdyas.org Ever confirmed|0 |1 --- Comment #1 from Boudewijn Rempt <b...@valdyas.org> --- That is probably because png and tga and so on don't save your layer; it saves the composed image. And at the composition phase, a pixel with alpha 0 gets all its color channels set to 0, if I remember correctly. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 375123] live drawing invisible
https://bugs.kde.org/show_bug.cgi?id=375123 --- Comment #3 from Boudewijn Rempt <b...@valdyas.org> --- That is really weird, because the cpu-based canvas should always work... Can you try with some different cursor options? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 375720] All files with gradient maps are corrupt
https://bugs.kde.org/show_bug.cgi?id=375720 Boudewijn Rempt <b...@valdyas.org> changed: What|Removed |Added Ever confirmed|0 |1 Status|NEEDSINFO |CONFIRMED Resolution|WAITINGFORINFO |--- --- Comment #5 from Boudewijn Rempt <b...@valdyas.org> --- Thanks for the link. With the given file, I can reproduce a crash on loading: #0 0x7fffed25c0c7 in raise () at /lib64/libc.so.6 #1 0x7fffed25d478 in abort () at /lib64/libc.so.6 #2 0x7fffed299784 in () at /lib64/libc.so.6 #3 0x7fffed29f026 in malloc_printerr () at /lib64/libc.so.6 #4 0x7fffed29ffcd in _int_free () at /lib64/libc.so.6 #5 0x7444e22f in KoColorSpace::colorants() const (data=) at /home/boud/dev/deps/include/QtCore/qarraydata.h:222 #6 0x7444e22f in KoColorSpace::colorants() const (this=, x=) at /home/boud/dev/deps/include/QtCore/qvector.h:518 #7 0x7444e22f in KoColorSpace::colorants() const (this=, __in_chrg=) at /home/boud/dev/deps/include/QtCore/qvector.h:69 #8 0x7444e22f in KoColorSpace::colorants() const (other=, this=) at /home/boud/dev/deps/include/QtCore/qvector.h:74 #9 0x7444e22f in KoColorSpace::colorants() const (this=this@entry=0x11a83d0) at /home/boud/dev/krita/libs/pigment/KoColorSpace.cpp:269 #10 0x7444e439 in KoColorSpace::lumaCoefficients() const (this=this@entry=0x11a83d0) at /home/boud/dev/krita/libs/pigment/KoColorSpace.cpp:285 #11 0x7fffd05d3a27 in KisHSVAdjustmentFilter::createTransformation(KoColorSpace const*, KisPinnedSharedPtr) const (this=, cs=0x11a83d0, config=...) at /home/boud/dev/krita/plugins/filters/colorsfilters/kis_hsv_adjustment_filter.cpp:113 #12 0x761c62bf in KisColorTransformationConfiguration::colorTransformation(KoColorSpace const*, KisColorTransformationFilter const*) const (this=this@entry=0x7ad6270, cs=cs@entry=0x11a83d0, filter=filter@entry= 0x4763690) at /home/boud/dev/krita/libs/image/filter/kis_color_transformation_configuration.cc:63 #13 0x761c7d5e in KisColorTransformationFilter::processImpl(KisSharedPtr, QRect const&, KisPinnedSharedPtr, KoUpdater*) const (this=0x4763690, device=..., applyRect=..., config=..., progressUpdater=0x0) at /home/boud/dev/krita/libs/image/filter/kis_color_transformation_filter.cc:61 #14 0x761c4b8a in KisFilter::process(KisSharedPtr, KisSharedPtr, KisSharedPtr, QRect const&, KisPinnedSharedPtr, KoUpdater*) const (this=this@entry=0x4763690, src=..., dst=..., selection=..., applyRect=..., config=..., progressUpdater=progressUpdater@entry=0x0) at /home/boud/dev/krita/libs/image/filter/kis_filter.cc:129 #15 0x762189bb in KisFilterMask::decorateRect(KisSharedPtr&, KisSharedPtr&, QRect const&, KisNode::PositionToFilthy) const (this=, src=..., dst=..., rc=..., maskPos=) at /home/boud/dev/krita/libs/image/kis_filter_mask.cpp:97 #16 0x7628287b in KisMask::apply(KisSharedPtr, QRect const&, QRect const&, KisNode::PositionToFilthy) const (this=0x7ad60c0, projection=..., applyRect=..., needRect=..., maskPos=maskPos@entry=KisNode::N_ABOVE_FILTHY) at /home/boud/dev/krita/libs/image/kis_mask.cc:280 #17 0x7626a628 in KisLayer::applyMasks(KisSharedPtr, KisSharedPtr, QRect const&, KisSharedPtr, KisSharedPtr) const (this=this@entry=0x7a8b380, source=..., destination=..., requestedRect=..., filthyNode=..., lastNode=...) at /home/boud/dev/krita/libs/image/kis_layer.cc:632 #18 0x7626afa7 in KisLayer::updateProjection(QRect const&, KisSharedPtr) (this=0x7a8b380, rect=..., filthyNode=...) at /home/boud/dev/krita/libs/image/kis_layer.cc:684 #19 0x7626e0e8 in KisLayerProjectionPlane::recalculate(QRect const&, KisSharedPtr) (this=, rect=..., filthyNode=...) at /home/boud/dev/krita/libs/image/kis_layer_projection_plane.cpp:47 #20 0x7622d354 in KisAsyncMerger::startMerge(KisBaseRectsWalker&, bool) (this=this@entry=0x79c71d0, walker=..., notifyClones=notifyClones@entry=true) at /home/boud/dev/krita/libs/image/kis_async_merger.cpp:251 #21 0x7636ef43 in KisUpdateJobItem::run() (this=0x79c7190) at /home/boud/dev/build/libs/image/kritaimage_automoc.dir/../../../../krita/libs/image/kis_update_job_item.h:83 #22 0x7636ef43 in KisUpdateJobItem::run() (this=0x79c7190) at /home/boud/dev/build/libs/image/kritaimage_automoc.dir/../../../../krita/libs/image/kis_update_job_item.h:63 #23 0x7fffedf185fe in () at /home/boud/dev/deps/lib/libQt5Core.so.5 #24 0x7fffedf1b609 in () at /home/boud/dev/deps/lib/libQt5Core.so.5 #25 0x7fffed0120a4 in start_thread () at /lib64/libpthread.so.0 #26 0x7fffed30c02d in clone () at /lib64/libc.so.6 (gdb) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 375720] All files with gradient maps are corrupt
https://bugs.kde.org/show_bug.cgi?id=375720 --- Comment #6 from Boudewijn Rempt <b...@valdyas.org> --- After making sure that if krita cannot find a gradient, I got this output. Interestingly, some gradients are named (though not found, obviously, the gradients being loaded with the full path), but there are also a number of gradients with no name, which is even wronger. I think that the filter should use a different method for identifying the gradients, or maybe even store the gradients themselves in the filter config. Could not find gradient "C:/Users/GC/AppData/Roaming/krita/gradients\\.svg" Could not find gradient "C:/Users/GC/AppData/Roaming/krita/gradients\\.svg" Could not find gradient "C:/Users/GC/AppData/Roaming/krita/gradients\\.svg" Could not find gradient "skin1" Could not find gradient "C:/Users/GC/AppData/Roaming/krita/gradients/NK5644.svg" Could not find gradient "C:/Users/GC/AppData/Roaming/krita/gradients\\.svg" Could not find gradient "C:/Users/GC/AppData/Roaming/krita/gradients/NK5644.svg" Could not find gradient "C:/Users/GC/AppData/Roaming/krita/gradients\\.svg" Could not find gradient "C:/Users/GC/AppData/Roaming/krita/gradients/NK5644.svg" Could not find gradient "C:/Users/GC/AppData/Roaming/krita/gradients\\.svg" Could not find gradient "C:/Users/GC/AppData/Roaming/krita/gradients/NK5644.svg" Could not find gradient "C:/Users/GC/AppData/Roaming/krita/gradients\\.svg" Could not find gradient "C:/Users/GC/AppData/Roaming/krita/gradients/NK5644.svg" Could not find gradient "skin1" Could not find gradient "C:/Users/GC/AppData/Roaming/krita/gradients\\.svg" Could not find gradient "C:/Users/GC/AppData/Roaming/krita/gradients/NK5644.svg" Could not find gradient "skin1" Could not find gradient "C:/Users/GC/AppData/Roaming/krita/gradients\\.svg" Could not find gradient "skin1" Could not find gradient "C:/Users/GC/AppData/Roaming/krita/gradients\\.svg" Could not find gradient "skin1" Could not find gradient "C:/Users/GC/AppData/Roaming/krita/gradients/dj5644.svg" Could not find gradient "skin1" Could not find gradient "C:/Users/GC/AppData/Roaming/krita/gradients\\.svg" Could not find gradient "C:/Users/GC/AppData/Roaming/krita/gradients\\.svg" Could not find gradient "C:/Users/GC/AppData/Roaming/krita/gradients/NK5644.svg" Could not find gradient "C:/Users/GC/AppData/Roaming/krita/gradients/NK5644.svg" Could not find gradient "skin1" Could not find gradient "C:/Users/GC/AppData/Roaming/krita/gradients/dj5644.svg" Could not find gradient "C:/Users/GC/AppData/Roaming/krita/gradients\\.svg" Could not find gradient "C:/Users/GC/AppData/Roaming/krita/gradients/NK5644.svg" Could not find gradient "skin1" Could not find gradient "C:/Users/GC/AppData/Roaming/krita/gradients\\.svg" Could not find gradient "C:/Users/GC/AppData/Roaming/krita/gradients/NK5644.svg" Could not find gradient "gold" Could not find gradient "skin1" Could not find gradient "C:/Users/GC/AppData/Roaming/krita/gradients/dj5644.svg" Could not find gradient "skin1" Could not find gradient "C:/Users/GC/AppData/Roaming/krita/gradients\\.svg" Could not find gradient "C:/Users/GC/AppData/Roaming/krita/gradients/dj5644.svg" Could not find gradient "C:/Users/GC/AppData/Roaming/krita/gradients/NK5644.svg" Could not find gradient "gold" Could not find gradient "C:/Users/GC/AppData/Roaming/krita/gradients\\.svg" Could not find gradient "C:/Users/GC/AppData/Roaming/krita/gradients/NK5644.svg" Could not find gradient "gold" Could not find gradient "skin1" Could not find gradient "C:/Users/GC/AppData/Roaming/krita/gradients\\.svg" Could not find gradient "gold" Could not find gradient "skin1" Could not find gradient "C:/Users/GC/AppData/Roaming/krita/gradients\\.svg" Could not find gradient "skin1" Could not find gradient "C:/Users/GC/AppData/Roaming/krita/gradients\\.svg" Could not find gradient "C:/Users/GC/AppData/Roaming/krita/gradients/NK5644.svg" Could not find gradient "skin1" Could not find gradient "C:/Users/GC/AppData/Roaming/krita/gradients\\.svg" Could not find gradient "C:/Users/GC/AppData/Roaming/krita/gradients/NK5644.svg" Could not find gradient "gold" Could not find gradient "skin1" Could not find gradient "C:/Users/GC/AppData/Roaming/krita/gradients\\.svg" Could not find gradient "skin1" Could not find gradient "skin1" Could not find gradient "C:/Users/GC/AppData/Roaming/krita/gradients/dj5644.svg" Could n
[krita] [Bug 375716] 32 bits Krita crashes if the initial image is too big for the available memory
https://bugs.kde.org/show_bug.cgi?id=375716 Boudewijn Rempt <b...@valdyas.org> changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED Summary|Krita Crashes when |32 bits Krita crashes if |predifined A3 @ 600P.p.i|the initial image is too |canvas creation.|big for the available ||memory --- Comment #6 from Boudewijn Rempt <b...@valdyas.org> --- I cannot check the code for Photoshop and Corel Painter, so whatever they do, isn't relevant for Krita. On a 32 bits Windows, you can only allocate 2GB per process. Krita by default allows half of the available memory for an image, that is 1GB. If the image is too big it tries to swap it out to disk, but that also needs memory, and I suspect that that just isn't available. You can fiddle with the performance settings, making Krita use 2GB of memory, for instance, instead of 3/2 = 1.5, reduce undo steps and so on. See https://docs.krita.org/Performance_Settings Btw, the actual PPI isn't relevant; it's only the number of pixels that is relevant. Memory usage is width * height * number of bytes per pixel * number of layers + 1, roughly. But the bottom line is that a 7016x9920 pixel image just is too big for your computer. You will also have trouble actually painting on an image that size. There isn't much we can do at this point, I'm afraid. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 375720] All files with gradient maps are corrupt
https://bugs.kde.org/show_bug.cgi?id=375720 --- Comment #8 from Boudewijn Rempt <b...@valdyas.org> --- Git commit b517a549c2bd3e5fb75d4e4cd2c3efa9db773e63 by Boudewijn Rempt. Committed on 31/01/2017 at 10:14. Pushed by rempt into branch 'krita/3.1'. This doesn't work currently because the gradient is stored in a problematic way in the filter config: With an absolute path, which makes the file non-portable Could not find gradient "C:/Users/GC/AppData/Roaming/krita/gradients/kC5644.svg" With a plain name Could not find gradient "skin1" Or apparently without any name, I guess for the autogenerated gradients Could not find gradient "C:/Users/GC/AppData/Roaming/krita/gradients\\.svg" To fix this properly, we will need to sit down and fix the resource system. M +5-1plugins/filters/gradientmap/krita_filter_gradient_map.cpp https://commits.kde.org/krita/b517a549c2bd3e5fb75d4e4cd2c3efa9db773e63 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 375773] Multiple pop ups for Choose Screen resolution
https://bugs.kde.org/show_bug.cgi?id=375773 Boudewijn Rempt <b...@valdyas.org> changed: What|Removed |Added Ever confirmed|0 |1 CC||b...@valdyas.org Status|UNCONFIRMED |CONFIRMED --- Comment #1 from Boudewijn Rempt <b...@valdyas.org> --- I can confirm that this can happen -- it doesn't always happen, but last weekend I worked with my cintiq and windows 7 installation in three sessions. In the second session, I got the popup twice and the pen wasn't properly initialized. A reboot fixed that. But weirdly enough, the popup is modal, so it's really hard to figure out how we can manage to show it multiple times. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 375761] [Wacom] Pressure Sensitivity Not Working (only for Krita) 3.1.1
https://bugs.kde.org/show_bug.cgi?id=375761 Boudewijn Rempt <b...@valdyas.org> changed: What|Removed |Added CC||b...@valdyas.org Resolution|--- |WORKSFORME Status|UNCONFIRMED |RESOLVED --- Comment #2 from Boudewijn Rempt <b...@valdyas.org> --- I'm sorry, but this is not a bug in Krita... There is something up, but it's specific to your system. You could make a tablet log to see whether Krita actually can open the wintab dll, but even that doesn't mean a whole lot. The wacom drivers sometimes get really confused about which application gets a wintab context. Last weekend, in three drawing sessions, my own cintiq didn't work with Krita, and after a reboot it did. If you check photoshop forums, there are plenty of complaints about that, too, and even some where the user tells the Adobe people "but Krita works, so it must be a bug in Photoshop". There just isn't anything we can do from within Krita to make the drivers more stable. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 375720] All files with gradient maps are corrupt
https://bugs.kde.org/show_bug.cgi?id=375720 --- Comment #7 from Boudewijn Rempt <b...@valdyas.org> --- Git commit 2459d14e54914e34c3bd6cb4d1847026e6c65887 by Boudewijn Rempt. Committed on 31/01/2017 at 10:04. Pushed by rempt into branch 'master'. This doesn't work currently because the gradient is stored in a problematic way in the filter config: With an absolute path, which makes the file non-portable Could not find gradient "C:/Users/GC/AppData/Roaming/krita/gradients/kC5644.svg" With a plain name Could not find gradient "skin1" Or apparently without any name, I guess for the autogenerated gradients Could not find gradient "C:/Users/GC/AppData/Roaming/krita/gradients\\.svg" To fix this properly, we will need to sit down and fix the resource system. M +5-1plugins/filters/gradientmap/krita_filter_gradient_map.cpp https://commits.kde.org/krita/2459d14e54914e34c3bd6cb4d1847026e6c65887 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 375761] [Wacom] Pressure Sensitivity Not Working (only for Krita) 3.1.1
https://bugs.kde.org/show_bug.cgi?id=375761 --- Comment #5 from Boudewijn Rempt <b...@valdyas.org> --- Nope. Krita Gemini also uses the wintab api. The big difference is that Gemini doesn't ask for the tablet name. There are some other changes. BUT: Krita works with wacom tablets for hundreds of thousands of people, including the developers. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 334123] Increase maximum brush size to 3k size
https://bugs.kde.org/show_bug.cgi?id=334123 Boudewijn Rempt <b...@valdyas.org> changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||https://commits.kde.org/kri ||ta/85ec5a10916f4b5eefe36c14 ||272957154b49e4fb --- Comment #5 from Boudewijn Rempt <b...@valdyas.org> --- Git commit 85ec5a10916f4b5eefe36c14272957154b49e4fb by Boudewijn Rempt. Committed on 01/02/2017 at 13:42. Pushed by rempt into branch 'master'. Related: bug 10, bug 000 Now users can set the maximum brush size to 10,000. The default is still 1,000 -- and trust me, a 10,000 pixel diameter brush is slow and takes a huge amount of memory. CCMAIL:kimages...@kde.org M +6-4 libs/image/brushengine/kis_standard_uniform_properties_factory.cpp M +5-0libs/ui/dialogs/kis_dlg_preferences.cc M +68 -38 libs/ui/forms/wdggeneralsettings.ui M +1-1libs/ui/kis_paintop_box.cc M +2-1plugins/paintops/dynadraw/kis_dyna_paintop_settings.cpp M +2-2plugins/paintops/dynadraw/kis_dynaop_option.cpp M +5-1plugins/paintops/libpaintop/kis_auto_brush_widget.cpp M +5-1plugins/paintops/libpaintop/kis_brush_chooser.cpp https://commits.kde.org/krita/85ec5a10916f4b5eefe36c14272957154b49e4fb -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 369413] Make it possible to have brushes bigger then 1000 pixels
https://bugs.kde.org/show_bug.cgi?id=369413 --- Comment #4 from Boudewijn Rempt <b...@valdyas.org> --- I've added an option in the settings -- that's the easiest for now. It's now 10,000 hard max, but if you edit the kritarc file, you can add as many zeros as you want as long as you don't go beyond 2,147,483,647 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 375810] Print failed
https://bugs.kde.org/show_bug.cgi?id=375810 Boudewijn Rempt <b...@valdyas.org> changed: What|Removed |Added CC||b...@valdyas.org Status|UNCONFIRMED |RESOLVED Resolution|--- |LATER --- Comment #1 from Boudewijn Rempt <b...@valdyas.org> --- Krita 3.1.1 has no print functionality. Use Scribus to prepare a print-ready pdf. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 376126] [WACOM CINTIQ] No pen pressure sensitivity
https://bugs.kde.org/show_bug.cgi?id=376126 Boudewijn Rempt <b...@valdyas.org> changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED CC||b...@valdyas.org --- Comment #1 from Boudewijn Rempt <b...@valdyas.org> --- Hi, As you can see from the tablet log, Krita cannot open the wintab driver. I'm afraid that this is a driver installation problem, not a bug in Krita. That is actually always the case when a tablet doesn't register with Krita, even though some other applications might see the driver. (The other way around also happens, people reporting problems with e.g. photoshop, while they are sure it's not a driver bug "because Krita works.) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 376086] Shift + Clicking a layer eye icon does not hide other layers
https://bugs.kde.org/show_bug.cgi?id=376086 Boudewijn Rempt <b...@valdyas.org> changed: What|Removed |Added CC||b...@valdyas.org Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #1 from Boudewijn Rempt <b...@valdyas.org> --- I wonder when this broke, and whether it broke when we started using shift-click to select multiple layers, but it is broken... -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 376085] In latest git master, the brush doesn't get resized beyond 1k size with shift drag
https://bugs.kde.org/show_bug.cgi?id=376085 Boudewijn Rempt <b...@valdyas.org> changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://commits.kde.org/kri ||ta/27a1887ba3cca0cf472fec27 ||8ebbe1e653f0151c Status|CONFIRMED |RESOLVED --- Comment #2 from Boudewijn Rempt <b...@valdyas.org> --- Git commit 27a1887ba3cca0cf472fec278ebbe1e653f0151c by Boudewijn Rempt. Committed on 07/02/2017 at 11:19. Pushed by rempt into branch 'master'. M +1-1libs/ui/tool/kis_tool_paint.cc https://commits.kde.org/krita/27a1887ba3cca0cf472fec278ebbe1e653f0151c -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 376144] Krita 3.1.2 open with Problem
https://bugs.kde.org/show_bug.cgi?id=376144 Boudewijn Rempt <b...@valdyas.org> changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO CC||b...@valdyas.org --- Comment #1 from Boudewijn Rempt <b...@valdyas.org> --- Patrick, Your bug report does not contain any useful information. Please add a complete description of the problem to this bug report together with any relevant files. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 376143] Krita 3.1.2 Print Button failed
https://bugs.kde.org/show_bug.cgi?id=376143 Boudewijn Rempt <b...@valdyas.org> changed: What|Removed |Added CC||b...@valdyas.org Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #1 from Boudewijn Rempt <b...@valdyas.org> --- Krita does not provide print functionality. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 376145] Krita 3.1.2 The color palette is missing
https://bugs.kde.org/show_bug.cgi?id=376145 Boudewijn Rempt <b...@valdyas.org> changed: What|Removed |Added CC||b...@valdyas.org Resolution|--- |WORKSFORME Status|UNCONFIRMED |RESOLVED --- Comment #1 from Boudewijn Rempt <b...@valdyas.org> --- Here the color palette is not missing, there is no problem. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 376147] Krita 3.1.2 Print Botton and Print option is missing
https://bugs.kde.org/show_bug.cgi?id=376147 Boudewijn Rempt <b...@valdyas.org> changed: What|Removed |Added CC||b...@valdyas.org Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #1 from Boudewijn Rempt <b...@valdyas.org> --- Krita does not provide print functionality. You have been told this in two other bug reports and by private email. Please stop reporting this as a bug. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 375878] Eraser will not switch back to brush after turning Wacom pen back around
https://bugs.kde.org/show_bug.cgi?id=375878 Boudewijn Rempt <b...@valdyas.org> changed: What|Removed |Added CC||michy...@hotmail.com --- Comment #10 from Boudewijn Rempt <b...@valdyas.org> --- *** Bug 376160 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 376160] selected brush changes to another when flipping the tip of the tablet pencil to the seccondary tip
https://bugs.kde.org/show_bug.cgi?id=376160 Boudewijn Rempt <b...@valdyas.org> changed: What|Removed |Added Resolution|--- |DUPLICATE Status|CONFIRMED |RESOLVED CC||b...@valdyas.org --- Comment #4 from Boudewijn Rempt <b...@valdyas.org> --- It's very likely a duplicate of 375878 *** This bug has been marked as a duplicate of bug 375878 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 376147] Krita 3.1.2 Print Botton and Print option is missing
https://bugs.kde.org/show_bug.cgi?id=376147 Boudewijn Rempt <b...@valdyas.org> changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WONTFIX --- Comment #4 from Boudewijn Rempt <b...@valdyas.org> --- And Krita doesn't, and that's not a bug. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363124] AMD GPU's dont' support glLogicOp(XOR) so the brush outline isn't xorred.
https://bugs.kde.org/show_bug.cgi?id=363124 --- Comment #16 from Boudewijn Rempt <b...@valdyas.org> --- Hi Joe, Please also put this diff on phabricator -- apart from wolthera and me, most Krita developers don't look for patches in bugzilla, because of the volume of traffic. Unfortunately, as you probably know if you hung around on irc yesterday, I won't have time to dig in this week and probably also not next week. Do try to ping Nimmy, though! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 376085] In latest git master, the brush doesn't get resized beyond 1k size with shift drag
https://bugs.kde.org/show_bug.cgi?id=376085 Boudewijn Rempt <b...@valdyas.org> changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- CC||b...@valdyas.org --- Comment #4 from Boudewijn Rempt <b...@valdyas.org> --- Let's reopen it then. I won't be able to do any coding for some time, but if it stays closed, I will forget for sure. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 376144] Krita 3.1.2 open with Problem
https://bugs.kde.org/show_bug.cgi?id=376144 Boudewijn Rempt <b...@valdyas.org> changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #3 from Boudewijn Rempt <b...@valdyas.org> --- Okay, that's not useful information, since that works on all three os's I use. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 375895] Shift+LKM+drag on line-brush size
https://bugs.kde.org/show_bug.cgi?id=375895 Boudewijn Rempt <b...@valdyas.org> changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WONTFIX CC||b...@valdyas.org --- Comment #1 from Boudewijn Rempt <b...@valdyas.org> --- Hi, That's because shift has a different meaning in the line tool: it constrains the angle to 15 degrees: https://docs.krita.org/Line_Tool We're unlikely to change this behaviour because it's what people have asked us for before... -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 375874] Vector isn't working at all
https://bugs.kde.org/show_bug.cgi?id=375874 --- Comment #3 from Boudewijn Rempt <b...@valdyas.org> --- Thank probably is a bug. If Krita actually crashes you could try to generate crash information, but if it hangs there isn't much to investigate... -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 375503] MP4 render doesn't play in any program
https://bugs.kde.org/show_bug.cgi?id=375503 Boudewijn Rempt <b...@valdyas.org> changed: What|Removed |Added CC||b...@valdyas.org --- Comment #15 from Boudewijn Rempt <b...@valdyas.org> --- I guess we should make the oldest one default, and then close this bug. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 375901] Crash on opening any file
https://bugs.kde.org/show_bug.cgi?id=375901 Boudewijn Rempt <b...@valdyas.org> changed: What|Removed |Added CC||b...@valdyas.org --- Comment #1 from Boudewijn Rempt <b...@valdyas.org> --- Hi, I guess you could workaround this crash by disabling opengl -- it clearly happens right inside the intel display driver: krita.exe caused an Access Violation at location 7FFE74B042E4 in module ig75icd64.dll Reading from location 0008. It isn't the first problem we have with intel drivers -- black screens, canvas doesn't update until some gui element is selected, and now a crash again. Intel guys, you should check pointers before reading pointers! Without an actual test system this is going to be really hard to debug. We're obviously doing something the intel driver developers have never expected, but we're still using opengl correctly, as far as we know... -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 376034] Crashing
https://bugs.kde.org/show_bug.cgi?id=376034 Boudewijn Rempt <b...@valdyas.org> changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO CC||b...@valdyas.org --- Comment #1 from Boudewijn Rempt <b...@valdyas.org> --- Hi, Without more information there is nothing we can do... There's probably something weird going on on your system, your display drivers might be broken (check by disabling opengl in settings/configure krita/display), some security software might have decided to change some dll's or whatever else. Please follow https://docs.krita.org/Dr._Mingw_debugger and attach a backtrace to the report so we can at least see where Krita is crashing. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 376006] Crashed on new painting!
https://bugs.kde.org/show_bug.cgi?id=376006 Boudewijn Rempt <b...@valdyas.org> changed: What|Removed |Added CC||b...@valdyas.org Resolution|--- |WAITINGFORINFO Status|UNCONFIRMED |NEEDSINFO --- Comment #1 from Boudewijn Rempt <b...@valdyas.org> --- Hi, Since Krita doesn't crash on any of my four windows test systems, this must be something specific to your system. First check whether disabling opengl makes a difference. If that doesn't make a difference, please make a crash log (see https://docs.krita.org/Dr._Mingw_debugger) and attach it to this bug report. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 376003] Tablet Support for Wacom Cintiq 13HD does not recognize pressure sensitivity.
https://bugs.kde.org/show_bug.cgi?id=376003 Boudewijn Rempt <b...@valdyas.org> changed: What|Removed |Added CC||b...@valdyas.org Platform|Windows CE |MS Windows --- Comment #2 from Boudewijn Rempt <b...@valdyas.org> --- It's a settings problem I'm afraid. I've seen the same thing happening with my own cintiq hybrid companion now and then, which is setup as the second monitor in my case, no display duplication. Sometimes rebooting helps, sometimes the wacom settings app is confused about which monitor it is. As you can see from the tablet log, there are no stylus events coming in, only synthesized mouse events. I know that some other applications might work with this setup, but tbh, the photoshop forums and reddits are full of people telling Adobe people that Photoshop has a bug "because Krita works". In the end, it's the wacom driver that has the bug... -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 376006] Crashed on new painting!
https://bugs.kde.org/show_bug.cgi?id=376006 --- Comment #3 from Boudewijn Rempt <b...@valdyas.org> --- Settings/Configure Krita/Display -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 376006] Crashed on new painting!
https://bugs.kde.org/show_bug.cgi?id=376006 Boudewijn Rempt <b...@valdyas.org> changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |UPSTREAM --- Comment #6 from Boudewijn Rempt <b...@valdyas.org> --- If you overwrite a default brush, you can get the old one back by opening the resources folder (settings/manage resources/open resource folder) and removing the local copy. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 375901] Crash on opening any file
https://bugs.kde.org/show_bug.cgi?id=375901 Boudewijn Rempt <b...@valdyas.org> changed: What|Removed |Added CC||gamedj2...@yahoo.com --- Comment #7 from Boudewijn Rempt <b...@valdyas.org> --- *** Bug 376006 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 375901] Crash on opening any file
https://bugs.kde.org/show_bug.cgi?id=375901 Boudewijn Rempt <b...@valdyas.org> changed: What|Removed |Added Resolution|--- |UPSTREAM Status|CONFIRMED |RESOLVED --- Comment #6 from Boudewijn Rempt <b...@valdyas.org> --- Ah, thanks for the information! Then we can close as upstream -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 376006] Crashed on new painting!
https://bugs.kde.org/show_bug.cgi?id=376006 Boudewijn Rempt <b...@valdyas.org> changed: What|Removed |Added Resolution|UPSTREAM|DUPLICATE --- Comment #7 from Boudewijn Rempt <b...@valdyas.org> --- PLease check the bug I've marked as a duplicate -- that has some information on driver versions. With a correct driver, you probably won't have the problem even if opengl is enabled. *** This bug has been marked as a duplicate of bug 375901 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 375939] Crash on startup
https://bugs.kde.org/show_bug.cgi?id=375939 Boudewijn Rempt <b...@valdyas.org> changed: What|Removed |Added CC||b...@valdyas.org --- Comment #2 from Boudewijn Rempt <b...@valdyas.org> --- Hi Raius, Thanks for your report, and also thanks for adding the backtrace! Since the crash happens when loading brushes, could you a) check if the crash still happens if you move your resources folder to another location b) if not, zip up the brushes and paintoppresets folder and share that with me? c) if the crash still happens, check whether renaming the kritarc file to kritarc.bak makes a difference, and if so, share that with me? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 375901] Crash on opening any file
https://bugs.kde.org/show_bug.cgi?id=375901 Boudewijn Rempt <b...@valdyas.org> changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Component|File formats|OpenGL Canvas Ever confirmed|0 |1 Platform|Other |MS Windows --- Comment #4 from Boudewijn Rempt <b...@valdyas.org> --- Confirming, a crash with backtrace is always confirmed -- even if the crash might not be in krita itself... -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 375901] Crash on opening any file
https://bugs.kde.org/show_bug.cgi?id=375901 --- Comment #3 from Boudewijn Rempt <b...@valdyas.org> --- I still wish I could figure out exactly _why_ this crash happens. I'll mail my Intel contact tomorrow. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 372439] Export to PDF in custom size, does not export to the desired size, unfortunately, but to default size (A4).
https://bugs.kde.org/show_bug.cgi?id=372439 --- Comment #9 from Boudewijn Rempt <b...@valdyas.org> --- Git commit 8e2e0faaac8cfe3eee95f67e5e61d7fc31c9d289 by Boudewijn Rempt. Committed on 21/01/2017 at 12:33. Pushed by rempt into branch 'krita/3.1'. Remove the PDF export menu option CCMAIL: kimages...@kde.org People really should use Scribus (http://scribus.net) to make PDF's, not Krita, where the the PDF export code depends on QPrinter, which just isn't powerful enough. Krita is for creating images; for printing stuff, whether to PDF or printer, use a dedicated application. M +3-3libs/ui/KisMainWindow.cpp M +1-0libs/ui/KisMainWindow.h https://commits.kde.org/krita/8e2e0faaac8cfe3eee95f67e5e61d7fc31c9d289 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 372439] Export to PDF in custom size, does not export to the desired size, unfortunately, but to default size (A4).
https://bugs.kde.org/show_bug.cgi?id=372439 --- Comment #8 from Boudewijn Rempt <b...@valdyas.org> --- Git commit 30441fda12d6030c73a30d6242f3f6f5053c3688 by Boudewijn Rempt. Committed on 21/01/2017 at 12:30. Pushed by rempt into branch 'master'. Remove the PDF export menu option CCMAIL: kimages...@kde.org People really should use Scribus (http://scribus.net) to make PDF's, not Krita, where the the PDF export code depends on QPrinter, which just isn't powerful enough. Krita is for creating images; for printing stuff, whether to PDF or printer, use a dedicated application. M +3-3libs/ui/KisMainWindow.cpp M +1-0libs/ui/KisMainWindow.h https://commits.kde.org/krita/30441fda12d6030c73a30d6242f3f6f5053c3688 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 340085] Brush cursor border hard to see over specific color
https://bugs.kde.org/show_bug.cgi?id=340085 --- Comment #12 from Boudewijn Rempt <b...@valdyas.org> --- "So is this something Nvidia should fix? Well that depends how you look at it. But assuming that Nvidia will fix it will most likely mean that we will never ever see a fix." Yes, that's correct. Doesn't closed source software development suck? Isn't open source nice? You can not only discuss issues openly and directly with the developers, you could even try to fix issues yourself. We've worked around hundreds of issues with broken hardware drivers, broken window managers and so on, and I'm hoping someone will step up and code a workaround for this issue as well -- nobody has done that yet, though. And I haven't got time to work on this, it's just one of 319 open bugs. And this bug isn't my highest priority bug, because even though I get the green outline on my quadro, I never have the cursor disappear on white background, not even if the brush is only one pixel. Besides, there are a ton of cursor options that people can use as workarounds. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 375428] Krita Forcing Logoff
https://bugs.kde.org/show_bug.cgi?id=375428 Boudewijn Rempt <b...@valdyas.org> changed: What|Removed |Added CC||b...@valdyas.org --- Comment #1 from Boudewijn Rempt <b...@valdyas.org> --- Um... I don't see this happening in Gnome on OpenSUSE. I cannot imagine how Krita could make you logout from your desktop. Maybe the windowmanager/desktop crashes? I wonder if this also happens also if you disable opengl in Krita... -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 375429] All tools start with a straight line when drawing circles or curves
https://bugs.kde.org/show_bug.cgi?id=375429 Boudewijn Rempt <b...@valdyas.org> changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||b...@valdyas.org Status|UNCONFIRMED |NEEDSINFO --- Comment #1 from Boudewijn Rempt <b...@valdyas.org> --- Hi Patrick, This is not something that happens to everyone; it is something specific to your system. You'll need to tell us more about your system. Which version of Windows do you have, are you using the 32 or 64 bits version of Krita, what tablet do you have? What is the color model and channel depth and size of the image you're working on? Does it matter whether you enable or disable opengl (settings/configure krita/display), and if so, what GPU do you have and what is the driver version? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 375428] Krita Forcing Logoff
https://bugs.kde.org/show_bug.cgi?id=375428 Boudewijn Rempt <b...@valdyas.org> changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|UNCONFIRMED |NEEDSINFO --- Comment #4 from Boudewijn Rempt <b...@valdyas.org> --- Oh, and another can be that there's a faulty ram module in your system, and that krita pushes something else into that module, and then the desktop closes. I had that on my dev system with firefox and gcc, which kept crashing. Please also run a memory checker. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 375122] Painting with Krita all day today and noticed a few bugs.
https://bugs.kde.org/show_bug.cgi?id=375122 --- Comment #7 from Boudewijn Rempt <b...@valdyas.org> --- Always save as .kra, then export to jpeg (or png). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 375428] Krita Forcing Logoff
https://bugs.kde.org/show_bug.cgi?id=375428 --- Comment #3 from Boudewijn Rempt <b...@valdyas.org> --- It could be because Krita uses more texture memory than the other applications, if your image is very big. But I haven't seen this happen myself, so it's all guess work, and that's why I want you to disable opengl and see if the issue still occurs. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 374562] Random crash when moving/transforming a layer
https://bugs.kde.org/show_bug.cgi?id=374562 Boudewijn Rempt <b...@valdyas.org> changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Platform|Other |Ubuntu Packages CC||b...@valdyas.org Resolution|--- |WAITINGFORINFO --- Comment #3 from Boudewijn Rempt <b...@valdyas.org> --- Hi Supaiku, Could you also check with the appimage? If that also crashes for you, then we might have to make a special version with debug symbols for you, since these messages aren't useful for figuring out what is going on. If you could share one of your images, that might also be useful. Unfortunately, the lime ppa isn't available for 16.04 :-( Z-uo, since you're using 16.10, you could install Krita using the lime ppa together with the debug symbols. That way you can give us a useful backtrace when you reproduce the crash: https://launchpad.net/~kritalime/+archive/ubuntu/ppa -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 374746] Removing the color from multiple selected Frames does not work
https://bugs.kde.org/show_bug.cgi?id=374746 Boudewijn Rempt <b...@valdyas.org> changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 CC||b...@valdyas.org --- Comment #1 from Boudewijn Rempt <b...@valdyas.org> --- Hi Tobias, Thanks for your report. I can confirm the issue. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 374747] "Overwrite Preset" grayed when preview image is changed
https://bugs.kde.org/show_bug.cgi?id=374747 Boudewijn Rempt <b...@valdyas.org> changed: What|Removed |Added CC||b...@valdyas.org Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #1 from Boudewijn Rempt <b...@valdyas.org> --- Hi Tobias, You're correct... I'm not quite sure how to solve this though. Did you know, btw, that you can open a kpp file in Krita and edit it in the main canvas? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 374828] Pivot position "Canvas Rotation" seems wobbly
https://bugs.kde.org/show_bug.cgi?id=374828 Boudewijn Rempt <b...@valdyas.org> changed: What|Removed |Added Severity|normal |minor Ever confirmed|0 |1 Status|NEEDSINFO |CONFIRMED Resolution|WAITINGFORINFO |--- CC||b...@valdyas.org --- Comment #4 from Boudewijn Rempt <b...@valdyas.org> --- Yes, can confirm the issue. Your test image makes it very easy to see. I have to admit, though, that it's unlikely to get a lot of priority to fix. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 374900] Crash when changing RGB color values on Mac OS X
https://bugs.kde.org/show_bug.cgi?id=374900 Boudewijn Rempt <b...@valdyas.org> changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 CC||b...@valdyas.org --- Comment #1 from Boudewijn Rempt <b...@valdyas.org> --- Hi Dmitry, Thanks for your report. I can confirm the issue. It seems to have something to do with the accessibility interface of Qt. This is the backtrace I get: * thread #1: tid = 0xef35c, 0x000102db4d9c QtGui`QAccessible::queryAccessibleInterface(QObject*) + 156, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=EXC_I386_GPFLT) * frame #0: 0x000102db4d9c QtGui`QAccessible::queryAccessibleInterface(QObject*) + 156 frame #1: 0x000102db5f34 QtGui`QAccessibleEvent::accessibleInterface() const + 36 frame #2: 0x000102db5523 QtGui`QAccessible::updateAccessibility(QAccessibleEvent*) + 19 frame #3: 0x0001028b780f QtWidgets`QWidgetLineControl::emitCursorPositionChanged() + 191 frame #4: 0x0001028b6ca7 QtWidgets`QWidgetLineControl::finishChange(int, bool, bool) + 727 frame #5: 0x0001028bc291 QtWidgets`QWidgetLineControl::processKeyEvent(QKeyEvent*) + 4225 frame #6: 0x000102822b62 QtWidgets`QLineEdit::keyPressEvent(QKeyEvent*) + 34 frame #7: 0x000102716ca4 QtWidgets`QWidget::event(QEvent*) + 4916 frame #8: 0x000102821fc1 QtWidgets`QLineEdit::event(QEvent*) + 641 frame #9: 0x0001027ccb79 QtWidgets`QAbstractSpinBox::keyPressEvent(QKeyEvent*) + 1193 frame #10: 0x000102716ca4 QtWidgets`QWidget::event(QEvent*) + 4916 frame #11: 0x0001027cbab9 QtWidgets`QAbstractSpinBox::event(QEvent*) + 457 frame #12: 0x0001026d5a7a QtWidgets`QApplicationPrivate::notify_helper(QObject*, QEvent*) + 314 frame #13: 0x0001026d73a9 QtWidgets`QApplication::notify(QObject*, QEvent*) + 1785 frame #14: 0x0001007a0198 libkritaui.16.dylib`KisApplication::notify(this=, receiver=0x00011d969af0, event=) + 24 at KisApplication.cpp:537 [opt] frame #15: 0x000103563b14 QtCore`QCoreApplication::notifyInternal2(QObject*, QEvent*) + 164 frame #16: 0x000102736233 QtWidgets`QWidgetWindow::event(QEvent*) + 531 frame #17: 0x0001026d5a7a QtWidgets`QApplicationPrivate::notify_helper(QObject*, QEvent*) + 314 frame #18: 0x0001026d6eae QtWidgets`QApplication::notify(QObject*, QEvent*) + 510 frame #19: 0x0001007a0198 libkritaui.16.dylib`KisApplication::notify(this=, receiver=0x000105421e00, event=) + 24 at KisApplication.cpp:537 [opt] frame #20: 0x000103563b14 QtCore`QCoreApplication::notifyInternal2(QObject*, QEvent*) + 164 frame #21: 0x000102dd7ace QtGui`QGuiApplicationPrivate::processKeyEvent(QWindowSystemInterfacePrivate::KeyEvent*) + 174 frame #22: 0x000102dbf68b QtGui`QWindowSystemInterface::sendWindowSystemEvents(QFlags) + 203 frame #23: 0x000102dbc76c QtGui`QWindowSystemInterface::flushWindowSystemEvents(QFlags) + 572 frame #24: 0x0001099735d8 libqcocoa.dylib`-[QNSView handleKeyEvent:eventType:] + 1144 frame #25: 0x000109973702 libqcocoa.dylib`-[QNSView keyDown:] + 98 frame #26: 0x7fff8cf93b15 AppKit`-[NSWindow _reallySendEvent:isDelayedEvent:] + 2108 frame #27: 0x7fff8c9d2539 AppKit`-[NSWindow sendEvent:] + 517 frame #28: 0x0001099622d7 libqcocoa.dylib`-[QNSPanel superSendEvent:] + 39 frame #29: 0x0001099616e6 libqcocoa.dylib`-[QNSWindowHelper handleWindowEvent:] + 694 frame #30: 0x7fff8c95316a AppKit`-[NSApplication sendEvent:] + 4382 frame #31: 0x00010997ca0e libqcocoa.dylib`-[QNSApplication sendEvent:] + 78 frame #32: 0x7fff8c7b9df2 AppKit`-[NSApplication run] + 796 frame #33: 0x00010997921f libqcocoa.dylib`QCocoaEventDispatcher::processEvents(QFlags) + 2191 frame #34: 0x00010355fd01 QtCore`QEventLoop::exec(QFlags) + 417 frame #35: 0x000103564185 QtCore`QCoreApplication::exec() + 341 frame #36: 0x0001e3ee krita`main(argc=, argv=) + 5678 at main.cc:258 [opt] frame #37: 0x7fff9c6f25ad libdyld.dylib`start + 1 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 374544] Getting references from external hard drives
https://bugs.kde.org/show_bug.cgi?id=374544 Boudewijn Rempt <b...@valdyas.org> changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Component|Resource Management |Dockers CC||b...@valdyas.org Resolution|--- |WAITINGFORINFO --- Comment #1 from Boudewijn Rempt <b...@valdyas.org> --- Hi Jo, Are you talking about the reference images docker? Your bug report says you're using Linux. If that's correct, you can navigate the entire file system hierarchy starting with the / and that means you can go to your external drive. The same holds for the regular file open dialog. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 374590] Canvas locks up after using keyboard shortcut
https://bugs.kde.org/show_bug.cgi?id=374590 Boudewijn Rempt <b...@valdyas.org> changed: What|Removed |Added CC||tiagotcasta...@gmail.com --- Comment #2 from Boudewijn Rempt <b...@valdyas.org> --- *** Bug 374918 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 374918] Shortcuts not working
https://bugs.kde.org/show_bug.cgi?id=374918 Boudewijn Rempt <b...@valdyas.org> changed: What|Removed |Added Resolution|--- |DUPLICATE CC||b...@valdyas.org Status|UNCONFIRMED |RESOLVED --- Comment #1 from Boudewijn Rempt <b...@valdyas.org> --- Hi, This sounds like a duplicate of 374590 *** This bug has been marked as a duplicate of bug 374590 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 374590] Canvas locks up after using keyboard shortcut
https://bugs.kde.org/show_bug.cgi?id=374590 --- Comment #3 from Boudewijn Rempt <b...@valdyas.org> --- Hi, I've heard others report this is as well. I must still be doing something different, because I recently did a couple of hours of painting on OSX, but didn't see this happen. I'll keep my eyes open -- and thanks for adding a tablet log! The last lines puzzle me a bit... krita.tabletlog: "[ ] ShortcutOverride key: 0x121 mod: 0x400 text: none" krita.tabletlog: "[ ] ShortcutOverride key: 0x120 mod: 0x600 text: none" krita.tabletlog: "[ ] ShortcutOverride key: 0x54 mod: 0x600 text: none" -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 374744] "import animation frames" grayed out
https://bugs.kde.org/show_bug.cgi?id=374744 Boudewijn Rempt <b...@valdyas.org> changed: What|Removed |Added Latest Commit||https://commits.kde.org/kri ||ta/a545f536c7f83c904efc8475 ||ffa944572e190111 Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #2 from Boudewijn Rempt <b...@valdyas.org> --- Git commit a545f536c7f83c904efc8475ffa944572e190111 by Boudewijn Rempt. Committed on 23/01/2017 at 15:03. Pushed by rempt into branch 'master'. M +0-1libs/ui/KisMainWindow.cpp https://commits.kde.org/krita/a545f536c7f83c904efc8475ffa944572e190111 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 374744] "import animation frames" grayed out
https://bugs.kde.org/show_bug.cgi?id=374744 Boudewijn Rempt <b...@valdyas.org> changed: What|Removed |Added Latest Commit|https://commits.kde.org/kri |https://commits.kde.org/kri |ta/a545f536c7f83c904efc8475 |ta/88e2eae87889b4bd3e01bed4 |ffa944572e190111|bd0f157cbaf407ab --- Comment #3 from Boudewijn Rempt <b...@valdyas.org> --- Git commit 88e2eae87889b4bd3e01bed4bd0f157cbaf407ab by Boudewijn Rempt. Committed on 23/01/2017 at 15:03. Pushed by rempt into branch 'krita/3.1'. M +0-1libs/ui/KisMainWindow.cpp https://commits.kde.org/krita/88e2eae87889b4bd3e01bed4bd0f157cbaf407ab -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 374847] paintoppresets using internal patterns bug
https://bugs.kde.org/show_bug.cgi?id=374847 --- Comment #5 from Boudewijn Rempt <b...@valdyas.org> --- Yes, I can confirm the issue. I will push the patch, but keep the bug open since I'm pretty sure that the patch breaks other things. This needs a couple of days of careful consideration. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 374748] Cursor dissapears when brush-size is 0px without pressure
https://bugs.kde.org/show_bug.cgi?id=374748 Boudewijn Rempt <b...@valdyas.org> changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 CC||b...@valdyas.org --- Comment #1 from Boudewijn Rempt <b...@valdyas.org> --- Hi Tobias, I can confirm the issue. Again, not sure how to solve it because it's hard to draw an outline in this case... -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 374957] Krita select another brush preset than the one selected after start-up
https://bugs.kde.org/show_bug.cgi?id=374957 Boudewijn Rempt <b...@valdyas.org> changed: What|Removed |Added CC||b...@valdyas.org --- Comment #4 from Boudewijn Rempt <b...@valdyas.org> --- Yes, I've also seen it happen. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 374745] tooltips are wrong
https://bugs.kde.org/show_bug.cgi?id=374745 Boudewijn Rempt <b...@valdyas.org> changed: What|Removed |Added Resolution|--- |FIXED CC||b...@valdyas.org Status|UNCONFIRMED |RESOLVED --- Comment #2 from Boudewijn Rempt <b...@valdyas.org> --- No idea... But let's close the bug then :-) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 374847] paintoppresets using internal patterns bug
https://bugs.kde.org/show_bug.cgi?id=374847 Boudewijn Rempt <b...@valdyas.org> changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED CC||b...@valdyas.org -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 374745] tooltips are wrong
https://bugs.kde.org/show_bug.cgi?id=374745 --- Comment #4 from Boudewijn Rempt <b...@valdyas.org> --- Git commit 912aee6f2381819b8bf6fc0ec40e79811d2b01cb by Boudewijn Rempt. Committed on 23/01/2017 at 15:21. Pushed by rempt into branch 'krita/3.1'. This will lead to duplicated patterns, but at least not every brush will paint with the same pattern. This bug still needs careful fixing. Patch by Razvanc, thanks! CCMAIL:razvan...@yahoo.com M +1-8plugins/paintops/libpaintop/kis_embedded_pattern_manager.cpp https://commits.kde.org/krita/912aee6f2381819b8bf6fc0ec40e79811d2b01cb -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 374745] tooltips are wrong
https://bugs.kde.org/show_bug.cgi?id=374745 --- Comment #3 from Boudewijn Rempt <b...@valdyas.org> --- Git commit d6413d25e9dfabe1f20570affd9b4eec27833a91 by Boudewijn Rempt. Committed on 23/01/2017 at 15:20. Pushed by rempt into branch 'master'. This will lead to duplicated patterns, but at least not every brush will paint with the same pattern. This bug still needs careful fixing. Patch by Razvanc, thanks! CCMAIL:razvan...@yahoo.com M +1-8plugins/paintops/libpaintop/kis_embedded_pattern_manager.cpp https://commits.kde.org/krita/d6413d25e9dfabe1f20570affd9b4eec27833a91 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 375454] [XP Pen] Krita is drawing lines between end points and start points
https://bugs.kde.org/show_bug.cgi?id=375454 Boudewijn Rempt <b...@valdyas.org> changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||b...@valdyas.org Resolution|--- |DUPLICATE --- Comment #1 from Boudewijn Rempt <b...@valdyas.org> --- Hi David, Right now the xp-pen isn't supported: the drivers are, like most uc-logic based tablets beyond horrendous. It isn't like Photoshop supports the tablet: the driver developers make their drivers support photoshop. That's their first goal, and if they break the wintab spec while doing so, they don't care. Without test hardware, which we cannot afford, we cannot even try to figure out a workaround, I'm afraid. In any case, this issue also happens with other tablets, and is a duplicate of bug 363284 *** This bug has been marked as a duplicate of bug 363284 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363284] [UGEE] Krita connects strokes with previous ones
https://bugs.kde.org/show_bug.cgi?id=363284 Boudewijn Rempt <b...@valdyas.org> changed: What|Removed |Added CC||davidbarsony@gmail.com --- Comment #48 from Boudewijn Rempt <b...@valdyas.org> --- *** Bug 375454 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363284] [XP-PEN][UGEE] Krita connects strokes with previous ones
https://bugs.kde.org/show_bug.cgi?id=363284 Boudewijn Rempt <b...@valdyas.org> changed: What|Removed |Added Summary|[UGEE] Krita connects |[XP-PEN][UGEE] Krita |strokes with previous ones |connects strokes with ||previous ones -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363968] Preview thumbnail in .kra/.ora files are sometimes cropped instead of full canvas
https://bugs.kde.org/show_bug.cgi?id=363968 Boudewijn Rempt <b...@valdyas.org> changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #8 from Boudewijn Rempt <b...@valdyas.org> --- Should be fixed now. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 374981] [WACOM] Multiple click impulses in GUI with stylus
https://bugs.kde.org/show_bug.cgi?id=374981 --- Comment #4 from Boudewijn Rempt <b...@valdyas.org> --- Hm... No, no idea. I've got the same version of OSX, and I don't see it. The strange thing is that we don't handle tablet events ourselves, we get them handed by the OS, through Qt. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 375027] Krita Gemini doesn't support the n-trig pen of a surface pro, even if wintab is installed.
https://bugs.kde.org/show_bug.cgi?id=375027 --- Comment #2 from Boudewijn Rempt <b...@valdyas.org> --- *** Bug 375028 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 375027] Krita Gemini doesn't support the n-trig pen of a surface pro, even if wintab is installed.
https://bugs.kde.org/show_bug.cgi?id=375027 Boudewijn Rempt <b...@valdyas.org> changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 Summary|Stylus isn't calibrated |Krita Gemini doesn't ||support the n-trig pen of a ||surface pro, even if wintab ||is installed. CC||b...@valdyas.org --- Comment #1 from Boudewijn Rempt <b...@valdyas.org> --- Hi Austin, Krita Sketch is an older version of Krita, with a gui optimized for tablets. We lost that gui when we updated Krita to a newer version of the development platform. At that point we also fixed a number of issues with the support for the wintab drivers for the n-trig pen, but because we had changed so much code, we could not backport those changes to Krita Sketch or Krita Gemini. We're kind of stuck now. I still want to find the time to create a new tablet gui for Krita (I've also got a surface pro), but the previous guy who tried it failed, too :-( -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 375028] Stylus is unaligned
https://bugs.kde.org/show_bug.cgi?id=375028 Boudewijn Rempt <b...@valdyas.org> changed: What|Removed |Added Resolution|--- |DUPLICATE CC||b...@valdyas.org Status|UNCONFIRMED |RESOLVED --- Comment #2 from Boudewijn Rempt <b...@valdyas.org> --- *** This bug has been marked as a duplicate of bug 375027 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 375072] Mirror tool doesn't work even after uninstall and reinstall
https://bugs.kde.org/show_bug.cgi?id=375072 Boudewijn Rempt <b...@valdyas.org> changed: What|Removed |Added Platform|Windows CE |MS Windows CC||b...@valdyas.org --- Comment #1 from Boudewijn Rempt <b...@valdyas.org> --- Hi, When you say mirroring tool do you mean the "M" key to mirror the canvas, or the horizontal/vertical brush mirror lines? Have you tried to reset your configuration (uninstalling and reinstalling doesn't do that): https://docs.krita.org/KritaFAQ#Resetting_Krita_configuration -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 375073] When close to the edge, popup palette auto-selects brush under cursor.
https://bugs.kde.org/show_bug.cgi?id=375073 --- Comment #2 from Boudewijn Rempt <b...@valdyas.org> --- Aw, you already said it's plasma... -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 375073] When close to the edge, popup palette auto-selects brush under cursor.
https://bugs.kde.org/show_bug.cgi?id=375073 Boudewijn Rempt <b...@valdyas.org> changed: What|Removed |Added CC||b...@valdyas.org --- Comment #1 from Boudewijn Rempt <b...@valdyas.org> --- Hi Quiralta, I cannot reproduce this behaviour. Which window manager are you using? Is this with a tablet or a mouse? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 375253] Krita 3.1.1 crashes while painting
https://bugs.kde.org/show_bug.cgi?id=375253 Boudewijn Rempt <b...@valdyas.org> changed: What|Removed |Added Latest Commit||https://commits.kde.org/kri ||ta/ac257511dbec0a3191bbfdde ||9d886b70ec6ad574 Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #16 from Boudewijn Rempt <b...@valdyas.org> --- Git commit ac257511dbec0a3191bbfdde9d886b70ec6ad574 by Boudewijn Rempt. Committed on 22/01/2017 at 14:35. Pushed by rempt into branch 'master'. Weirdly enough, this bug only occurs on Windows 10 with the latest Wacom drivers and an older Wacom Intuos 3 or Cintiq tablet. At least, that's what we suspect. Somehow the input from this drivers drives the roation sensor crazy, and set rotation to NaN. So, first step: check whether the resulting rect is valid, we now return a 0,0 1x1 rect. Second step: check whether the rotation value happens to be NaN and return 0 in that case. Third step: make sure that the rotationLikeValue() function doesn't return NaN -- that is in the next commit. M +43 -27 libs/brush/kis_qimage_pyramid.cpp https://commits.kde.org/krita/ac257511dbec0a3191bbfdde9d886b70ec6ad574 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 375253] Krita 3.1.1 crashes while painting
https://bugs.kde.org/show_bug.cgi?id=375253 Boudewijn Rempt <b...@valdyas.org> changed: What|Removed |Added Latest Commit|https://commits.kde.org/kri |https://commits.kde.org/kri |ta/ac257511dbec0a3191bbfdde |ta/f7c4c823a80d8eab6b2e1f05 |9d886b70ec6ad574|3de81e04e7303f1c --- Comment #17 from Boudewijn Rempt <b...@valdyas.org> --- Git commit f7c4c823a80d8eab6b2e1f053de81e04e7303f1c by Boudewijn Rempt. Committed on 22/01/2017 at 14:38. Pushed by rempt into branch 'master'. This follows up on the previous commit (ac257511dbec0a3191bbfdde9d886b70ec6ad574), which had the wrong header... It wasn't a bug in QTransform, because if you set the transform's rotation to NaN, sure, it'll create an invalid rectangle. M +6-4plugins/paintops/libpaintop/kis_curve_option.h M +0-1plugins/paintops/libpaintop/kis_pressure_hsv_option.cpp https://commits.kde.org/krita/f7c4c823a80d8eab6b2e1f053de81e04e7303f1c -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 375253] Krita 3.1.1 crashes while painting
https://bugs.kde.org/show_bug.cgi?id=375253 Boudewijn Rempt <b...@valdyas.org> changed: What|Removed |Added Latest Commit|https://commits.kde.org/kri |https://commits.kde.org/kri |ta/f7c4c823a80d8eab6b2e1f05 |ta/f3bcd6c57aae1a93b4d25644 |3de81e04e7303f1c|2ee38c2ae32be9fe |https://commits.kde.org/kri |https://commits.kde.org/kri |ta/f3bcd6c57aae1a93b4d25644 |ta/3091f39a5e96ee73e6a156ac |2ee38c2ae32be9fe|f3ce64bd744c7df8 --- Comment #18 from Boudewijn Rempt <b...@valdyas.org> --- Git commit f3bcd6c57aae1a93b4d256442ee38c2ae32be9fe by Boudewijn Rempt. Committed on 22/01/2017 at 14:40. Pushed by rempt into branch 'krita/3.1'. Weirdly enough, this bug only occurs on Windows 10 with the latest Wacom drivers and an older Wacom Intuos 3 or Cintiq tablet. At least, that's what we suspect. Somehow the input from this drivers drives the roation sensor crazy, and set rotation to NaN. So, first step: check whether the resulting rect is valid, we now return a 0,0 1x1 rect. Second step: check whether the rotation value happens to be NaN and return 0 in that case. Third step: make sure that the rotationLikeValue() function doesn't return NaN -- that is in the next commit. M +43 -27 libs/brush/kis_qimage_pyramid.cpp https://commits.kde.org/krita/f3bcd6c57aae1a93b4d256442ee38c2ae32be9fe --- Comment #19 from Boudewijn Rempt <b...@valdyas.org> --- Git commit 3091f39a5e96ee73e6a156acf3ce64bd744c7df8 by Boudewijn Rempt. Committed on 22/01/2017 at 14:40. Pushed by rempt into branch 'krita/3.1'. This follows up on the previous commit (ac257511dbec0a3191bbfdde9d886b70ec6ad574), which had the wrong header... It wasn't a bug in QTransform, because if you set the transform's rotation to NaN, sure, it'll create an invalid rectangle. M +6-4plugins/paintops/libpaintop/kis_curve_option.h M +0-1plugins/paintops/libpaintop/kis_pressure_hsv_option.cpp https://commits.kde.org/krita/3091f39a5e96ee73e6a156acf3ce64bd744c7df8 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 375253] Krita 3.1.1 crashes while painting
https://bugs.kde.org/show_bug.cgi?id=375253 Boudewijn Rempt <b...@valdyas.org> changed: What|Removed |Added Latest Commit|https://commits.kde.org/kri |https://commits.kde.org/kri |ta/f7c4c823a80d8eab6b2e1f05 |ta/f3bcd6c57aae1a93b4d25644 |3de81e04e7303f1c|2ee38c2ae32be9fe |https://commits.kde.org/kri |https://commits.kde.org/kri |ta/f3bcd6c57aae1a93b4d25644 |ta/3091f39a5e96ee73e6a156ac |2ee38c2ae32be9fe|f3ce64bd744c7df8 --- Comment #18 from Boudewijn Rempt <b...@valdyas.org> --- Git commit f3bcd6c57aae1a93b4d256442ee38c2ae32be9fe by Boudewijn Rempt. Committed on 22/01/2017 at 14:40. Pushed by rempt into branch 'krita/3.1'. Weirdly enough, this bug only occurs on Windows 10 with the latest Wacom drivers and an older Wacom Intuos 3 or Cintiq tablet. At least, that's what we suspect. Somehow the input from this drivers drives the roation sensor crazy, and set rotation to NaN. So, first step: check whether the resulting rect is valid, we now return a 0,0 1x1 rect. Second step: check whether the rotation value happens to be NaN and return 0 in that case. Third step: make sure that the rotationLikeValue() function doesn't return NaN -- that is in the next commit. M +43 -27 libs/brush/kis_qimage_pyramid.cpp https://commits.kde.org/krita/f3bcd6c57aae1a93b4d256442ee38c2ae32be9fe --- Comment #19 from Boudewijn Rempt <b...@valdyas.org> --- Git commit 3091f39a5e96ee73e6a156acf3ce64bd744c7df8 by Boudewijn Rempt. Committed on 22/01/2017 at 14:40. Pushed by rempt into branch 'krita/3.1'. This follows up on the previous commit (ac257511dbec0a3191bbfdde9d886b70ec6ad574), which had the wrong header... It wasn't a bug in QTransform, because if you set the transform's rotation to NaN, sure, it'll create an invalid rectangle. M +6-4plugins/paintops/libpaintop/kis_curve_option.h M +0-1plugins/paintops/libpaintop/kis_pressure_hsv_option.cpp https://commits.kde.org/krita/3091f39a5e96ee73e6a156acf3ce64bd744c7df8 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 375479] 16-bit files are too bright; Krita should read the TIFFTAG_DCSGAMMA tag
https://bugs.kde.org/show_bug.cgi?id=375479 Boudewijn Rempt <b...@valdyas.org> changed: What|Removed |Added CC||b...@valdyas.org Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 375479] 16-bit files are too bright; Krita should read the TIFFTAG_DCSGAMMA tag
https://bugs.kde.org/show_bug.cgi?id=375479 Boudewijn Rempt <b...@valdyas.org> changed: What|Removed |Added Latest Commit|https://commits.kde.org/kri |https://commits.kde.org/kri |ta/33ea3d9259fb3ca1345ca2d5 |ta/f5a54f8b5f8656a863744388 |efeee79b9a16|03b2dccdcd67628b --- Comment #3 from Boudewijn Rempt <b...@valdyas.org> --- Git commit f5a54f8b5f8656a86374438803b2dccdcd67628b by Boudewijn Rempt. Committed on 24/01/2017 at 09:23. Pushed by rempt into branch 'krita/3.1'. Related: bug 16 Assume that 16 bit rgb tiff files without a profile are gamma corrected. It would be better for people not to generate these files, or if they did, add the TIFFTAG_DCSGAMMA tag to specify the gamma, but that's unlikely to happen. M +9-4plugins/impex/tiff/kis_tiff_converter.cc https://commits.kde.org/krita/f5a54f8b5f8656a86374438803b2dccdcd67628b -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 375479] 16-bit files are too bright; Krita should read the TIFFTAG_DCSGAMMA tag
https://bugs.kde.org/show_bug.cgi?id=375479 Boudewijn Rempt <b...@valdyas.org> changed: What|Removed |Added Latest Commit||https://commits.kde.org/kri ||ta/33ea3d9259fb3ca1345ca2d5 ||efeee79b9a16 Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #2 from Boudewijn Rempt <b...@valdyas.org> --- Git commit 33ea3d9259fb3ca1345ca2d5efeee788889b9a16 by Boudewijn Rempt. Committed on 24/01/2017 at 09:23. Pushed by rempt into branch 'master'. Related: bug 16 Assume that 16 bit rgb tiff files without a profile are gamma corrected. It would be better for people not to generate these files, or if they did, add the TIFFTAG_DCSGAMMA tag to specify the gamma, but that's unlikely to happen. M +9-4plugins/impex/tiff/kis_tiff_converter.cc https://commits.kde.org/krita/33ea3d9259fb3ca1345ca2d5efeee79b9a16 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 375072] Mirror tool doesn't work even after uninstall and reinstall
https://bugs.kde.org/show_bug.cgi?id=375072 Boudewijn Rempt <b...@valdyas.org> changed: What|Removed |Added Resolution|--- |WORKSFORME Status|UNCONFIRMED |RESOLVED --- Comment #3 from Boudewijn Rempt <b...@valdyas.org> --- Okay, closing then. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 375479] 16-bit files are too bright; Krita should read the TIFFTAG_DCSGAMMA tag
https://bugs.kde.org/show_bug.cgi?id=375479 --- Comment #1 from Boudewijn Rempt <b...@valdyas.org> --- Hm, no... I was wrong. That image doesn't contain a gamma tag. No idea where imagemagick gets it from then. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 306181] Multiple issues with the multiline text shape
https://bugs.kde.org/show_bug.cgi?id=306181 Boudewijn Rempt <b...@valdyas.org> changed: What|Removed |Added Resolution|--- |LATER Status|CONFIRMED |RESOLVED --- Comment #19 from Boudewijn Rempt <b...@valdyas.org> --- Resolving all text tool bugs as Later, since the text tool will no longer be developed, but replaced. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 330708] [ Vector shapes or objects ] 'Shadows' are not saved
https://bugs.kde.org/show_bug.cgi?id=330708 Boudewijn Rempt <b...@valdyas.org> changed: What|Removed |Added Component|Vector Objects and Tools|Text Tool -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 342223] Multiline Text Background Colour Transparency isn't saved properly
https://bugs.kde.org/show_bug.cgi?id=342223 Boudewijn Rempt <b...@valdyas.org> changed: What|Removed |Added Resolution|--- |LATER Status|CONFIRMED |RESOLVED --- Comment #9 from Boudewijn Rempt <b...@valdyas.org> --- Resolving all text tool bugs as Later, since the text tool will no longer be developed, but replaced. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 330708] [ Vector shapes or objects ] 'Shadows' are not saved
https://bugs.kde.org/show_bug.cgi?id=330708 Boudewijn Rempt <b...@valdyas.org> changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |LATER --- Comment #5 from Boudewijn Rempt <b...@valdyas.org> --- Resolving all text tool bugs as Later, since the text tool will no longer be developed, but replaced. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 370310] I can't type Chinese characters, and whenever I use multi-line the software crashes.
https://bugs.kde.org/show_bug.cgi?id=370310 Boudewijn Rempt <b...@valdyas.org> changed: What|Removed |Added Status|NEEDSINFO |RESOLVED --- Comment #4 from Boudewijn Rempt <b...@valdyas.org> --- Resolving all text tool bugs as Later, since the text tool will no longer be developed, but replaced. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 344386] [ multiline text tool ] aliasing issue ( dark outline ) under a certain font size
https://bugs.kde.org/show_bug.cgi?id=344386 Boudewijn Rempt <b...@valdyas.org> changed: What|Removed |Added Resolution|--- |LATER CC||b...@valdyas.org Component|Vector Objects and Tools|Text Tool Status|CONFIRMED |RESOLVED --- Comment #7 from Boudewijn Rempt <b...@valdyas.org> --- Closing all text tool bugs. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 372623] shadow of text is not saved
https://bugs.kde.org/show_bug.cgi?id=372623 Boudewijn Rempt <b...@valdyas.org> changed: What|Removed |Added Resolution|--- |LATER Status|CONFIRMED |RESOLVED --- Comment #3 from Boudewijn Rempt <b...@valdyas.org> --- Resolving all text tool bugs as Later, since the text tool will no longer be developed, but replaced. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 373466] Fonts don't display correctly at the point where they intersect
https://bugs.kde.org/show_bug.cgi?id=373466 Boudewijn Rempt <b...@valdyas.org> changed: What|Removed |Added Resolution|--- |LATER Status|CONFIRMED |RESOLVED --- Comment #4 from Boudewijn Rempt <b...@valdyas.org> --- Resolving all text tool bugs as Later, since the text tool will no longer be developed, but replaced. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 346799] Artistic text tool does not support cut, copy and paste.
https://bugs.kde.org/show_bug.cgi?id=346799 Boudewijn Rempt <b...@valdyas.org> changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |LATER --- Comment #4 from Boudewijn Rempt <b...@valdyas.org> --- Resolving all text tool bugs as Later, since the text tool will no longer be developed, but replaced. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 350782] Doesn't support Writing using Arabic text
https://bugs.kde.org/show_bug.cgi?id=350782 Boudewijn Rempt <b...@valdyas.org> changed: What|Removed |Added Resolution|--- |LATER Status|CONFIRMED |RESOLVED --- Comment #7 from Boudewijn Rempt <b...@valdyas.org> --- Resolving all text tool bugs as Later, since the text tool will no longer be developed, but replaced. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 348290] [ Eraser mode ] eraser icon highlight in toolbar send wrong feedback to user
https://bugs.kde.org/show_bug.cgi?id=348290 Boudewijn Rempt <b...@valdyas.org> changed: What|Removed |Added Latest Commit|https://commits.kde.org/kri |https://commits.kde.org/kri |ta/f1968fd7f55cda3a08aa0488 |ta/59d9fb6de9d72f7cc72c0999 |a3b72d186db565e8|b0c412f75f45a444 --- Comment #7 from Boudewijn Rempt <b...@valdyas.org> --- Git commit 59d9fb6de9d72f7cc72c0999b0c412f75f45a444 by Boudewijn Rempt. Committed on 24/01/2017 at 10:11. Pushed by rempt into branch 'krita/3.1'. M +6-0libs/ui/kis_paintop_box.cc https://commits.kde.org/krita/59d9fb6de9d72f7cc72c0999b0c412f75f45a444 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 348290] [ Eraser mode ] eraser icon highlight in toolbar send wrong feedback to user
https://bugs.kde.org/show_bug.cgi?id=348290 Boudewijn Rempt <b...@valdyas.org> changed: What|Removed |Added Latest Commit||https://commits.kde.org/kri ||ta/f1968fd7f55cda3a08aa0488 ||a3b72d186db565e8 Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #6 from Boudewijn Rempt <b...@valdyas.org> --- Git commit f1968fd7f55cda3a08aa0488a3b72d186db565e8 by Boudewijn Rempt. Committed on 24/01/2017 at 10:10. Pushed by rempt into branch 'master'. M +6-0libs/ui/kis_paintop_box.cc https://commits.kde.org/krita/f1968fd7f55cda3a08aa0488a3b72d186db565e8 -- You are receiving this mail because: You are watching all bug changes.
