GIMP issueshttps://gitlab.gnome.org/GNOME/gimp/-/issues2023-11-05T10:29:15Zhttps://gitlab.gnome.org/GNOME/gimp/-/issues/7859Selection outline does not show up on first try with Fuzzy Select & Select by...2023-11-05T10:29:15ZJeffery SmallSelection outline does not show up on first try with Fuzzy Select & Select by Color with GIMP 2.10.30### Environment/Versions
- GIMP version: 2.10.30
- Package: <!--[flatpak? Installer from gimp.org? If another installer, tell us where from] (write it after the > symbol)--> 2.10.30-0focal2 Ubuntu package
- Operating System: <!--[Window...### Environment/Versions
- GIMP version: 2.10.30
- Package: <!--[flatpak? Installer from gimp.org? If another installer, tell us where from] (write it after the > symbol)--> 2.10.30-0focal2 Ubuntu package
- Operating System: <!--[Windows? macOS? Linux? All?] (write it after the > symbol) --> Linux Xubuntu 20.04
<!--Note: bug reporters are expected to have verified the bug still exists
either in the last stable version of GIMP or on updated development code
(master branch).-->
### Description of the bug
<!--Please describe your issue with details.
Add screenshot or other files if needed.(write it after the > symbol)-->
Ever since upgrading to 2.10.30 the first selection made using Fuzzy Select or Select by Color fails to show the active selection (i.e., with marching ant outlines). The selection HAS been made, it is simply not displayed. Only after the next use of the tool does the selection display.
### Reproduction
Is the bug reproducible? <!--[Always / Randomly / Happened only once ] (write it after the > symbol)--> This bug is 100% reproducible.
Reproduction steps:
1. Select tool and make a selection. Nothing shows.
2. Make 2nd selection and total selection shows.
3. Tool operates properly after this point.
Expected result:
Should see selection after first mouse click.2.10.38https://gitlab.gnome.org/GNOME/gimp/-/issues/10471gimp_edit_copy(): doesn't behave like docs or 2.102024-03-21T17:10:22ZLloyd Konnekerkonnekerl@gmail.comgimp_edit_copy(): doesn't behave like docs or 2.10Possibly this is just a reminder to update the docs.
### Reproduction
1. Starting fresh GIMP, open wilber.png
2. Enlarge the canvas
3. Drag out a selection off the layer, but in the canvas, say in lower right, in the checkerboard area....Possibly this is just a reminder to update the docs.
### Reproduction
1. Starting fresh GIMP, open wilber.png
2. Enlarge the canvas
3. Drag out a selection off the layer, but in the canvas, say in lower right, in the checkerboard area.
4. In the SF Console (gimp-edit-copy 1 #(2)) meaning copy the selection out of layer with ID 2.
Expected result: SF Console prints (0) meaning boolean result is false.
Actual result: prints (1)
Per the PDB Browser, which says " This procedure will fail if the selected area lies completely outside the bounds of the current drawables and there is nothing to copy from."
BTW, it should say "procedure will return false..." since the procedure can fail harder: the PDB procedure failed to return anything.
You can probably reproduce without using the ScriptFu Console. Choose Edit>Copy. Then Edit>Paste should remain disabled i.e. greyed out because the copy failed to put anything on the clipboard? But its not disabled, and if e.g. you choose Edit>PasteAs>NewImage you get a new image that seems devoid of pixels.
### Additional information
Behaves differently in 2.10, similar steps do print (0).
If the change in behavior is intended, the annotations for the PDB procedure need updating.
Otherwise, a bug.3.0 RC1https://gitlab.gnome.org/GNOME/gimp/-/issues/9978can't move or zoom viewport while altering selection2024-02-25T14:03:41ZAkiracan't move or zoom viewport while altering selection### Environment/Versions
- GIMP version: 2.99.17
- Package: flatpak
- Operating System: linux mint 21.2
### Description of the bug
i can't scroll around my image or zoom in/out while dragging a selection box resize handle anymore. why...### Environment/Versions
- GIMP version: 2.99.17
- Package: flatpak
- Operating System: linux mint 21.2
### Description of the bug
i can't scroll around my image or zoom in/out while dragging a selection box resize handle anymore. why? this was so useful to get precise measurements across large distances in gimp 2.10
### Reproduction
1. create a new image
2. make a selection
3. click and hold on to any of the resizing handles
4. try to use the scroll wheel to move the visible area of the image
Expected result: able to move or zoom viewport while resizing selection
Actual result: unable to do so3.0https://gitlab.gnome.org/GNOME/gimp/-/issues/8095Creating a stroke around a circular selection does not create a circle2023-07-08T14:54:45ZRuman GerstCreating a stroke around a circular selection does not create a circle### Environment/Versions
- GIMP version:2.10.24
- Package: Ubuntu packages (APT)
- Operating System: Kubuntu 21.10
**Info:** Tested it also with the latest beta Flatpak version
### Description of the bug
A user expecting to create a ...### Environment/Versions
- GIMP version:2.10.24
- Package: Ubuntu packages (APT)
- Operating System: Kubuntu 21.10
**Info:** Tested it also with the latest beta Flatpak version
### Description of the bug
A user expecting to create a circular outline will intuitively choose the option to create a circular selection and create a stroke around it. With increasing width of the stroke, the result becomes less circular.
To generated the expected behavior, users must create a path (see this video from 2009: https://www.youtube.com/watch?v=NqAozyd4AhU), which is less intuitive and involves additional steps.
![Screenshot_20220417_203544](/uploads/d45878ec319408468d896cb2895ccf62/Screenshot_20220417_203544.png)
![Screenshot_20220417_203607](/uploads/fb68c07c21ed18506b0a37456e241f72/Screenshot_20220417_203607.png)
![Screenshot_20220417_203614](/uploads/2d820e7fb0ca92f06d20ec4b539376f0/Screenshot_20220417_203614.png)
### Reproduction
Is the bug reproducible? <!--[Always / Randomly / Happened only once ] (write it after the > symbol)--> Always
Reproduction steps:
1. Create a circular selection with fixed 1:1 ratio
2. Go to Edit > Stroke selection...
3. Choose a line width > 1 (e.g. 50 or 100)
4. Click "Stroke"
Expected result: A perfect circle around the selected area with even thickness
Actual result: A circular object with uneven thickness and 4 visible indentations
### Additional information
If you have a backtrace for a crash or a warning, paste it here.
None3.2Shubham DauleShubham Daulehttps://gitlab.gnome.org/GNOME/gimp/-/issues/2572Selection tools cause entire canvas to melt and become black2023-05-11T08:53:53ZGhost UserSelection tools cause entire canvas to melt and become blackGIMP version:
2.10.8
Operating System: Windows 10. As for the updates version, it is November 25 2018 and there's no available updates pending.
Package: [flatpak? Installer from gimp.org? If another installer, tell us where from]
http...GIMP version:
2.10.8
Operating System: Windows 10. As for the updates version, it is November 25 2018 and there's no available updates pending.
Package: [flatpak? Installer from gimp.org? If another installer, tell us where from]
https://download.gimp.org/mirror/pub/gimp/v2.10/windows/gimp-2.10.8-setup-2.exe
# Description of the bug
Any time I make a selection of any sort with either the box select, lasso, or circular select, the entire canvas goes crazy.
It is not easy to explain. Basically, ever pixel on the canvas begins to get darker, and move to the lower left, and eventually my whole
canvas turns black. It's very bizarre and basically makes using any selection tool unusable. In order to get things back to normal,
I can either reload the document, or go to Select->None, then move another tool such as the paintbrush or the pencil around the canvas. As the cursor moves around the canvas, it "clears up" the canvas areas that it touches, returning it to it's normal look.
Please describe your issue with details.
Add screenshot or other files if needed.
# Reproduction
Is the bug reproducible? [Always / Randomly / Happened only once ]
EVERY TIME. NO EXCEPTIONS.
One thing that might be different in my case, which is an exception from other users, is my computer is a
Wacom Mobile Studio Pro 16". Probably not a heck of a lot of people with this particular computer using GIMP.
Maybe if it's hardware related, it could explain why this bug hasn't been reported by anyone else yet.
Reproduction steps:
1. Select any selection tool.
2. Make a selection on the canvas.
3. Watch the chaos unfold.
…
Expected result: I should have a selected group of pixels that I can move around inside of the canvas.
Actual result: My entire canvas melts like butter in an oven.
# Additional information
If you have a backtrace for a crash or a warning, paste it here.
The program never actually "crashes".2.10https://gitlab.gnome.org/GNOME/gimp/-/issues/1635Brush Clipboard Mask feature doesn't working correctly with selection shapes2024-02-15T20:11:13ZAmerico GobboBrush Clipboard Mask feature doesn't working correctly with selection shapesGIMP version: 2.99.1
Operating System: Linux, Fedora 28, GNOME
Package: from git
# Description of the bug
When you try to feed the brush clipboard with a free selection or another regular shape, e.g., a circle, the '**Clipboard Mask**...GIMP version: 2.99.1
Operating System: Linux, Fedora 28, GNOME
Package: from git
# Description of the bug
When you try to feed the brush clipboard with a free selection or another regular shape, e.g., a circle, the '**Clipboard Mask**' doesn't follow the selection shape... always the figure is shown as full square, where the side measure, of this square, is the more large dimension find in the selection.
I have tested also with(1) and without alpha(2) channel with a background color, also tested in a transparent layer(3)... and we have the same issue in all three cases
Expected result: as occurs with **Clipboard Image**, where the selection shape is obeyed by the feature.2.10https://gitlab.gnome.org/GNOME/gimp/-/issues/349Nudging sometimes moves either zero or two pixels2020-04-12T10:27:02ZBugzillaNudging sometimes moves either zero or two pixels## Submitted by Alexander Thomas
**[Link to original bug (#635186)](https://bugzilla.gnome.org/show_bug.cgi?id=635186)**
## Description
When nudging selection boundaries with the arrow keys, e.g. after having drawn a rectangular sel...## Submitted by Alexander Thomas
**[Link to original bug (#635186)](https://bugzilla.gnome.org/show_bug.cgi?id=635186)**
## Description
When nudging selection boundaries with the arrow keys, e.g. after having drawn a rectangular selection, sometimes the selection boundary can only be moved in increments of two pixels. This only seems to happen at zoom levels that are powers of two (200%, 400%, 800% etc).
Steps to reproduce:
1. Open any image
2. Zoom in to 200%
3. Make any rectangular selection
4. Either try to nudge the position of the entire selection or one of its edges/corners with the arrow keys
5. Repeat steps 3 and 4 several times.
Expected results:
The selection or its edge always moves with an increment of one pixel.
Actual results:
Sometimes the selection or its edge will alternate between not moving at all and moving two pixels when pressing the same arrow key in succession.
This seems related to [bug 620355](https://bugzilla.gnome.org/show_bug.cgi?id=620355) in some way. It has been present in many previous versions of GIMP and now it has annoyed me enough since then to file this bug report. A workaround is to zoom in to e.g. 201%.
Version: 2.6.11
### See also
* [Bug 779040](https://bugzilla.gnome.org/show_bug.cgi?id=779040)2.10https://gitlab.gnome.org/GNOME/gimp/-/issues/10949Selection outline not visible when using "Fuzzy Select" or "Select by Color" ...2024-03-02T20:03:54ZHorschtSelection outline not visible when using "Fuzzy Select" or "Select by Color" without a preexisting selection### Environment/Versions
- GIMP version: 2.10.36
- Package: Installer from gimp.org (direct download)
- Operating System: Windows 10 Version 22H2 (OS Build 19045.4046)
### Description of the bug
Selection outline is not visible when u...### Environment/Versions
- GIMP version: 2.10.36
- Package: Installer from gimp.org (direct download)
- Operating System: Windows 10 Version 22H2 (OS Build 19045.4046)
### Description of the bug
Selection outline is not visible when using "Fuzzy Select" or "Select by Color" when there is no prior selection. It does exist though and when switching to the pencil tool it also appears again.
### Reproduction
Always
Reproduction steps:
1. Clear selection using Select None
2. Choose the "Fuzzy Select" or "Select by Color" tool
3. Click on a color
Expected result:
Marching ants selection outline becomes visible, showing the selected area
Actual result:
Marching ants selection outline does not show up, as if the selection didn't work
### Additional information
![gimp-2.10_8BtUxoValJ](/uploads/fe60da0bffcf51eaca9eebc228d35a4f/gimp-2.10_8BtUxoValJ.mp4)https://gitlab.gnome.org/GNOME/gimp/-/issues/10840Interaction after copying and pasting a selection to a new layer2024-02-15T11:18:29ZMark SweeneyInteraction after copying and pasting a selection to a new layer**Operating System:** All
### Description of the feature
When copying and pasting a selection to a new layer, should the selection be removed, and transform be activated?
### Use cases
It's visually confusing to retain the selection ...**Operating System:** All
### Description of the feature
When copying and pasting a selection to a new layer, should the selection be removed, and transform be activated?
### Use cases
It's visually confusing to retain the selection after copying and pasting, ctrl-c, ctrl-v.
when copying and pasting, then step might usually be a transformation?
![cut-and-paste.mp4](/uploads/6d4c3d267894256b3662c749ba0090d6/cut-and-paste.mp4)https://gitlab.gnome.org/GNOME/gimp/-/issues/10754Unhandled Exception when attempting to copy a selection of any pixels width, ...2024-02-05T15:20:41ZJohn ArbuckleUnhandled Exception when attempting to copy a selection of any pixels width, 1 pixel height### Environment/Versions
- GIMP version: GIMP 2.10.36
- Package: <!--[flatpak? Installer from gimp.org? If another installer, tell us where from] (write it after the > symbol)--> Installer
- Operating System: <!--[Windows? macOS? Linux?...### Environment/Versions
- GIMP version: GIMP 2.10.36
- Package: <!--[flatpak? Installer from gimp.org? If another installer, tell us where from] (write it after the > symbol)--> Installer
- Operating System: <!--[Windows? macOS? Linux? All?] (write it after the > symbol) --> Windows
### Description of the bug
<!--Please describe your issue with details.
Add screenshot or other files if needed.(write it after the > symbol)-->
When attempting to copy a selection of X pixels in width, 1 pixel height, I receive a fatal error - unhandled exception. I've tested this with multiple images, any selection of 1 pixel height causes a crash when copying.
https://i.imgur.com/BxZvZxY.png
### Reproduction
Is the bug reproducible? <!--[Always / Randomly / Happened only once ] (write it after the > symbol)--> Always.
Reproduction steps:
1. Make a selection of any width but 1 pixel high.
2. Copy via CTRL+C or similar.
3. Receive the error, crash.
…
Expected result: The selection will be copied as normal.
Actual result: GIMP crashes.
### Additional informationhttps://gitlab.gnome.org/GNOME/gimp/-/issues/10677Crash after select all of image2024-02-07T16:54:34ZSimon SpringettCrash after select all of image<!-- Copy-paste this whole debug data to report to developers -->
```
GNU Image Manipulation Program version 2.10.36
git-describe: GIMP_2_10_36
Build: org.gimp.GIMP_official.arm64 rev 0 for macos
# C compiler #
Apple clang version 14....<!-- Copy-paste this whole debug data to report to developers -->
```
GNU Image Manipulation Program version 2.10.36
git-describe: GIMP_2_10_36
Build: org.gimp.GIMP_official.arm64 rev 0 for macos
# C compiler #
Apple clang version 14.0.3 (clang-1403.0.22.14.1)
Target: arm64-apple-darwin22.5.0
Thread model: posix
InstalledDir: /Library/Developer/CommandLineTools/usr/bin
# Libraries #
using babl version 0.1.106 (compiled against version 0.1.106)
using GEGL version 0.4.46 (compiled against version 0.4.46)
using GLib version 2.78.0 (compiled against version 2.78.0)
using GdkPixbuf version 2.42.10 (compiled against version 2.42.10)
using GTK+ version 2.24.33 (compiled against version 2.24.33)
using Pango version 1.50.14 (compiled against version 1.50.14)
using Fontconfig version 2.14.2 (compiled against version 2.14.2)
using Cairo version 1.17.6 (compiled against version 1.17.6)
```
> fatal error: Segmentation fault: 11
Stack trace:
```
0 libgimpbase-2.0.0.dylib 0x0000000102148510 gimp_stack_trace_print + 680
1 gimp 0x0000000100fb56e4 gimp_eek + 312
2 gimp 0x0000000100fb55ac gimp_eek + 0
3 gimp 0x0000000100fb6154 gimp_init_for_testing + 0
4 libsystem_platform.dylib 0x00000001827c5a24 _sigtramp + 56
5 libobjc.A.dylib 0x00000001823c9764 _objc_msgSend_uncached + 68
6 libobjc.A.dylib 0x00000001823c9764 _objc_msgSend_uncached + 68
7 libgdk-quartz-2.0.0.dylib 0x0000000102066618 _gdk_quartz_window_update_position + 48
8 libgdk-quartz-2.0.0.dylib 0x00000001020666c4 _gdk_windowing_update_window_sizes + 88
9 libgdk-quartz-2.0.0.dylib 0x00000001020644e0 screen_changed_idle + 56
10 libgdk-quartz-2.0.0.dylib 0x0000000102030de4 gdk_threads_dispatch + 64
11 libglib-2.0.0.dylib 0x00000001033b44d4 g_main_context_dispatch_unlocked + 236
12 libglib-2.0.0.dylib 0x00000001033b47c0 g_main_context_iterate_unlocked + 392
13 libglib-2.0.0.dylib 0x00000001033b4a44 g_main_loop_run + 120
14 gimp 0x0000000100fb4f68 app_run + 1000
15 gimp 0x0000000100fb7ef0 main + 1320
16 dyld 0x00000001824150e0 start + 2360
```2024-02-14https://gitlab.gnome.org/GNOME/gimp/-/issues/10490Copy selection pastes selection within the boundaries of the whole image in O...2024-03-04T08:20:40ZPeter BurnCopy selection pastes selection within the boundaries of the whole image in Office Software in Gimp 2.99.16<!-- ⚠️ IMPORTANT: READ ME! ⚠️
This is the default template for bug reports.
For feature requests or performance issues, please switch instead to the appropriate template in the "Choose a template" list.
It is important that you fill al...<!-- ⚠️ IMPORTANT: READ ME! ⚠️
This is the default template for bug reports.
For feature requests or performance issues, please switch instead to the appropriate template in the "Choose a template" list.
It is important that you fill all the fields of the template.
-->
### Environment/Versions
- GIMP version: 2.99.16
- Package: Installer from https://www.gimp.org/
- Operating System: Windows 10
<!--Note: bug reporters are expected to have verified the bug still exists
either in the last stable version of GIMP or on updated development code
(master branch).-->
### Description of the bug
<!--Please describe your issue with details.
Add screenshot or other files if needed.(write it after the > symbol)-->
Copy selection pastes selection within the boundaries of the whole image (= much larger than the selection itself) in Office Software like LibreOffice or ONLYOFFICE
In contrast: It works as expected (paste only the selection with the size of the selection in Ofice Software) in Gimp 2.10.36
+ It also works always as expected in Gimp itself (paste as new layer/image)
### Reproduction
Is the bug reproducible? <!--[Always / Randomly / Happened only once ] (write it after the > symbol)-->
Reproduction steps:
1. Open an image
2. Make a selection
3. Copy the selection
4. Paste in Office Software
…
Expected result:
Paste selection in it's own size
Actual result:
Paste selection in the (much larger) boundaries of the original image, but only selection is visible
### Additional information
If you have a backtrace for a crash or a warning, paste it here.https://gitlab.gnome.org/GNOME/gimp/-/issues/10346Options for pasting new floating selections2023-11-16T19:30:01Zgnome gitlabOptions for pasting new floating selections**Operating System:** <!--[Windows? macOS? Linux? All?] (write it after the > symbol) --> Windows
### Description of the feature
A configurable option to set whether a new floating selection created using CTRL+V (and it's derivatives) ...**Operating System:** <!--[Windows? macOS? Linux? All?] (write it after the > symbol) --> Windows
### Description of the feature
A configurable option to set whether a new floating selection created using CTRL+V (and it's derivatives) has it's alpha channels locked or unlocked.
For now I'm back to 2.8 where new floating selections do not have their alpha channels locked by default and to discard a floating selection I just press DELETE, and don't have to click another button before being able to delete it.https://gitlab.gnome.org/GNOME/gimp/-/issues/10046GIMP 2.99.16 Clipboard image and Clipboard Mask are always sized to canvas si...2023-12-25T12:16:05ZPixLabGIMP 2.99.16 Clipboard image and Clipboard Mask are always sized to canvas size or 1024 pixels (whatever is smaller), even if the selected area is even smaller
### Environment/Versions
- GIMP version: 2.99.16
- Package: flathing from gimp.org and appimage from a guy on github
- Operating System: Ubuntu-MATE 20.04
### Description of the bug
create a brush whatever form, then crop the laye...
### Environment/Versions
- GIMP version: 2.99.16
- Package: flathing from gimp.org and appimage from a guy on github
- Operating System: Ubuntu-MATE 20.04
### Description of the bug
create a brush whatever form, then crop the layer to content (Like in GIMP 2,10), then just copy (or alpha to selection and Ctrl+C) to put that draw as a brush in the clipboard.
INSTEAD of being a brush in the clipboard (image or Mask) our draw **is in a corner** of a 1024 pixels squared image, thus making our brush totally useless to use.
Clipboard image brush:
![screenshot_20230918-112313](/uploads/697b7f4c7bd46a1f11eb3d139c2d0900/screenshot_20230918-112313.jpg)
Clipboard mask:
![screenshot_20230918-112802](/uploads/2799dae5eb4fe978cd42352c41846971/screenshot_20230918-112802.jpg)https://gitlab.gnome.org/GNOME/gimp/-/issues/9981App Hang B1 error with Gimp 2.10.34.02023-09-16T15:23:46ZMathew BaileyApp Hang B1 error with Gimp 2.10.34.0I'm having an App Hang B1 error with Gimp 2.10.34.0. It involves the Select by Color tool & the issue is always reproducible as follows:When Select by Color tool is used to click on an area for editing or copying,Gimp hangs with Not Resp...I'm having an App Hang B1 error with Gimp 2.10.34.0. It involves the Select by Color tool & the issue is always reproducible as follows:When Select by Color tool is used to click on an area for editing or copying,Gimp hangs with Not Responding & stays that way until it is closed & restarted,but after restarting,the issue persists. I also tried uninstalling Gimp & removing the remainder of it from Windows registry & reinstalling it to no success. The error & what is related is shown here.-
```
A problem caused this program to stop interacting with Windows.
Faulting Application Path: C:\Program Files\GIMP 2\bin\gimp-2.10.exe
Problem signature
Problem Event Name: AppHangB1
Application Name: gimp-2.10.exe
Application Version: 2.10.34.0
Application Timestamp: 63fcd6be
Hang Signature: b738
Hang Type: 134217728
OS Version: 10.0.22621.2.0.0.768.101
Locale ID: 1033
Additional Hang Signature 1: b738ccca877551bbc3dc623b9e73018a
Additional Hang Signature 2: cf45
Additional Hang Signature 3: cf45672493d1f897f409ba97baf7877f
Additional Hang Signature 4: b738
Additional Hang Signature 5: b738ccca877551bbc3dc623b9e73018a
Additional Hang Signature 6: cf45
Additional Hang Signature 7: cf45672493d1f897f409ba97baf7877f
Extra information about the problem
Bucket ID: 983c8a684579989a104a4d6a9d73a9ad (1173835773186910637)
```https://gitlab.gnome.org/GNOME/gimp/-/issues/9784An Idea for a Simple (ish) Way to Implement Better Shape Tools in GIMP2024-02-29T10:03:52ZMichael DaviesAn Idea for a Simple (ish) Way to Implement Better Shape Tools in GIMP**Operating System:** <!--[Windows? macOS? Linux? All?] (write it after the > symbol) --> All
### Description of the feature
The current workflow for creating shapes in GIMP is through the selection tools. For example, you grab the Ell...**Operating System:** <!--[Windows? macOS? Linux? All?] (write it after the > symbol) --> All
### Description of the feature
The current workflow for creating shapes in GIMP is through the selection tools. For example, you grab the Ellipse select tool, then click and drag your mouse on the canvas and release to create a circle selection. Then, you go to the "Paths" dialogue and convert the selection to a path. From there, you can scale the path up or down, or stroke or fill the path. Of course, you can also scale the selection up or down and fill the selection.
What if the shape select tools (ellipse select and rectangle select) were tweaked slightly to accommodate the option to immediately draw a shape using a path instead of a selection? For example, the user clicks a radio button labeled "Draw Selection" or "Draw Path," and if the "Draw Path" option is selected, it displays additional options for interacting with the path (see attached photo below).
Perhaps this is me being naïve because I'm not a developer, but one implementation of this could be that you somehow script it so that when a person draws the shape with the selection area, the selection is automatically converted to a path upon release of the mouse (as if the user clicked "Selection to Path," but without them needing to click anything). Or, the path could be drawn upon hitting the enter key, thus allowing the user to adjust the area first before finalizing the drawing of the shape (and telling GIMP when to execute drawing the path).
![Draw_Path_or_Draw_Selection_Shape_Selection_Tools](/uploads/ebc8d61200c10912240d733c17cb98a5/Draw_Path_or_Draw_Selection_Shape_Selection_Tools.jpg)
**Another option**, which is more simple, is to have a "Selection to Path" button directly inside the Tool Options for both shape selection tools (see other attached photo). That way the user doesn't have to navigate to a new dialogue and find the small button that performs this feature (in the paths dialogue). It would essentially be a shortcut key for the action.
![Selection_to_Path_shortcut](/uploads/999f46e094780a307ac8b487ce0550e6/Selection_to_Path_shortcut.jpg)
<!-- Please describe your feature with details.
Add screenshots, design images or other files which would help for
understanding the feature or for implementation.
Also add links when needed, for instance for implementation standards
or other relevant resources.-->
### Use cases
<!-- If not obvious, explain the use cases or problems to solve. -->These features would make it easier to draw shapes as svg paths, and fill and stroke these paths for quicker shape creation.https://gitlab.gnome.org/GNOME/gimp/-/issues/9707Missing selection frame on pasted partially transparented pixels2023-07-07T11:37:17ZRyszard AdamusMissing selection frame on pasted partially transparented pixels### Environment/Versions
Windows 10x64 22H2 / Gimp 2.10.34
### Description of the bug
Working on image with layer contained only transparent pixels (with different percent of transparencies)
i have found that if i select pixels which ar...### Environment/Versions
Windows 10x64 22H2 / Gimp 2.10.34
### Description of the bug
Working on image with layer contained only transparent pixels (with different percent of transparencies)
i have found that if i select pixels which are slightly visible, copy the selection and paste it then the selection frame is no visible
around pasted fragment. If i select group of pixels where some are less transparent and the rest is slightly visible then after pasted
selection frame is drawn only around these less transparent pixels, the rest is not framed, although both are pasted correctly.
Sometimes there is no selection frame at all.
And second thing, if i select 100% transparent area, copy and paste it, there is no selection frame (which is logical because null was pasted) but Gimp shows me that the area is pasted and is waiting to anchor it with ALT+H key. Maybe in such case the paste should do nothing at all.
![przep_diaged_grey_maska2.xcf](/uploads/5fa41d13c7b63cd219b7e2da854b350a/przep_diaged_grey_maska2.xcf)
![selected](/uploads/f4df6731f371c394b182b5fb2771418a/selected.png)
![pasted](/uploads/e95754b4ecdc2d13469c711936a15738/pasted.png)https://gitlab.gnome.org/GNOME/gimp/-/issues/9706Critical errors when using the Fuzzy select tool2024-02-07T19:28:35ZL BlankenshipCritical errors when using the Fuzzy select tool<!-- Copy-paste this whole debug data to report to developers -->
```
GNU Image Manipulation Program version 2.99.14
git-describe: unknown (unsupported)
Build: org.gimp.GIMP_official.arm64 rev 1 for macos
# C compiler #
Apple clang ver...<!-- Copy-paste this whole debug data to report to developers -->
```
GNU Image Manipulation Program version 2.99.14
git-describe: unknown (unsupported)
Build: org.gimp.GIMP_official.arm64 rev 1 for macos
# C compiler #
Apple clang version 14.0.0 (clang-1400.0.29.202)
Target: arm64-apple-darwin21.6.0
Thread model: posix
InstalledDir: /Library/Developer/CommandLineTools/usr/bin
# Libraries #
using babl version 0.1.98 (compiled against version 0.1.98)
using GEGL version 0.4.40 (compiled against version 0.4.40)
using GLib version 2.70.5 (compiled against version 2.70.5)
using GdkPixbuf version 2.42.9 (compiled against version 2.42.9)
using GTK+ version 3.24.34 (compiled against version 3.24.34)
using Pango version 1.50.7 (compiled against version 1.50.7)
using Fontconfig version 2.14.1 (compiled against version 2.14.1)
using Cairo version 1.17.4 (compiled against version 1.17.4)
```
> GIMP-CRITICAL: gimp_image_new_from_drawables: assertion 'drawables != NULL' failed
Stack trace:
```
0 libgimpbase-3.0.0.dylib 0x000000010291eae8 gimp_stack_trace_print + 532
1 gimp 0x00000001020d5a1c gui_message + 396
2 gimp 0x0000000102019be8 gimp_message_log_func + 292
3 libglib-2.0.0.dylib 0x00000001034e7784 g_logv + 780
4 libglib-2.0.0.dylib 0x00000001034e7408 g_log + 28
5 libglib-2.0.0.dylib 0x00000001034e71f8 g_return_if_fail_warning + 32
6 gimp 0x00000001022a6780 gimp_image_new_from_drawables + 612
7 gimp 0x000000010210d3bc gimp_fuzzy_select_tool_get_mask + 288
8 gimp 0x0000000102133a28 gimp_region_select_tool_get_mask + 144
9 gimp 0x00000001021333e8 gimp_region_select_tool_button_press + 220
10 gimp 0x0000000102146114 gimp_tool_button_press + 172
11 gimp 0x00000001020a338c gimp_display_shell_canvas_tool_events + 5656
12 libgtk-3.0.dylib 0x0000000104253cc0 _gtk_marshal_BOOLEAN__BOXED + 116
13 libgobject-2.0.0.dylib 0x0000000102ff00e8 g_closure_invoke + 220
14 libgobject-2.0.0.dylib 0x0000000103004f00 signal_emit_unlocked_R + 1320
15 libgobject-2.0.0.dylib 0x0000000103005af4 g_signal_emit_valist + 1648
16 libgobject-2.0.0.dylib 0x0000000103006040 g_signal_emit + 28
17 libgtk-3.0.dylib 0x0000000104213fdc gtk_widget_event_internal + 300
18 libgtk-3.0.dylib 0x00000001040ea76c propagate_event + 388
19 libgtk-3.0.dylib 0x00000001040e9b74 gtk_main_do_event + 1068
20 libgdk-3.0.dylib 0x00000001036ea8c4 _gdk_event_emit + 64
21 libgdk-3.0.dylib 0x000000010370ff70 gdk_event_dispatch + 52
22 libglib-2.0.0.dylib 0x00000001034e169c g_main_context_dispatch + 240
23 libglib-2.0.0.dylib 0x00000001034e19b8 g_main_context_iterate + 432
24 libglib-2.0.0.dylib 0x00000001034e1a20 g_main_context_iteration + 60
25 libgio-2.0.0.dylib 0x00000001032e429c g_application_run + 464
26 gimp 0x000000010201935c app_run + 476
27 gimp 0x00000001020186c4 main + 1136
28 dyld 0x000000018251bf28 start + 2236
```
> GIMP-CRITICAL: gimp_container_remove: assertion 'object != NULL' failed
Stack trace:
```
0 libgimpbase-3.0.0.dylib 0x000000010291eae8 gimp_stack_trace_print + 532
1 gimp 0x00000001020d5a1c gui_message + 396
2 gimp 0x0000000102019be8 gimp_message_log_func + 292
3 libglib-2.0.0.dylib 0x00000001034e7784 g_logv + 780
4 libglib-2.0.0.dylib 0x00000001034e7408 g_log + 28
5 libglib-2.0.0.dylib 0x00000001034e71f8 g_return_if_fail_warning + 32
6 gimp 0x000000010225c6ec gimp_container_remove + 372
7 gimp 0x000000010210d3e4 gimp_fuzzy_select_tool_get_mask + 328
8 gimp 0x0000000102133a28 gimp_region_select_tool_get_mask + 144
9 gimp 0x00000001021333e8 gimp_region_select_tool_button_press + 220
10 gimp 0x0000000102146114 gimp_tool_button_press + 172
11 gimp 0x00000001020a338c gimp_display_shell_canvas_tool_events + 5656
12 libgtk-3.0.dylib 0x0000000104253cc0 _gtk_marshal_BOOLEAN__BOXED + 116
13 libgobject-2.0.0.dylib 0x0000000102ff00e8 g_closure_invoke + 220
14 libgobject-2.0.0.dylib 0x0000000103004f00 signal_emit_unlocked_R + 1320
15 libgobject-2.0.0.dylib 0x0000000103005af4 g_signal_emit_valist + 1648
16 libgobject-2.0.0.dylib 0x0000000103006040 g_signal_emit + 28
17 libgtk-3.0.dylib 0x0000000104213fdc gtk_widget_event_internal + 300
18 libgtk-3.0.dylib 0x00000001040ea76c propagate_event + 388
19 libgtk-3.0.dylib 0x00000001040e9b74 gtk_main_do_event + 1068
20 libgdk-3.0.dylib 0x00000001036ea8c4 _gdk_event_emit + 64
21 libgdk-3.0.dylib 0x000000010370ff70 gdk_event_dispatch + 52
22 libglib-2.0.0.dylib 0x00000001034e169c g_main_context_dispatch + 240
23 libglib-2.0.0.dylib 0x00000001034e19b8 g_main_context_iterate + 432
24 libglib-2.0.0.dylib 0x00000001034e1a20 g_main_context_iteration + 60
25 libgio-2.0.0.dylib 0x00000001032e429c g_application_run + 464
26 gimp 0x000000010201935c app_run + 476
27 gimp 0x00000001020186c4 main + 1136
28 dyld 0x000000018251bf28 start + 2236
```
> GIMP-CRITICAL: gimp_pickable_flush: assertion 'GIMP_IS_PICKABLE (pickable)' failed
Stack trace:
```
0 libgimpbase-3.0.0.dylib 0x000000010291eae8 gimp_stack_trace_print + 532
1 gimp 0x00000001020d5a1c gui_message + 396
2 gimp 0x0000000102019be8 gimp_message_log_func + 292
3 libglib-2.0.0.dylib 0x00000001034e7784 g_logv + 780
4 libglib-2.0.0.dylib 0x00000001034e7408 g_log + 28
5 libglib-2.0.0.dylib 0x00000001034e71f8 g_return_if_fail_warning + 32
6 gimp 0x000000010210d3fc gimp_fuzzy_select_tool_get_mask + 352
7 gimp 0x0000000102133a28 gimp_region_select_tool_get_mask + 144
8 gimp 0x00000001021333e8 gimp_region_select_tool_button_press + 220
9 gimp 0x0000000102146114 gimp_tool_button_press + 172
10 gimp 0x00000001020a338c gimp_display_shell_canvas_tool_events + 5656
11 libgtk-3.0.dylib 0x0000000104253cc0 _gtk_marshal_BOOLEAN__BOXED + 116
12 libgobject-2.0.0.dylib 0x0000000102ff00e8 g_closure_invoke + 220
13 libgobject-2.0.0.dylib 0x0000000103004f00 signal_emit_unlocked_R + 1320
14 libgobject-2.0.0.dylib 0x0000000103005af4 g_signal_emit_valist + 1648
15 libgobject-2.0.0.dylib 0x0000000103006040 g_signal_emit + 28
16 libgtk-3.0.dylib 0x0000000104213fdc gtk_widget_event_internal + 300
17 libgtk-3.0.dylib 0x00000001040ea76c propagate_event + 388
18 libgtk-3.0.dylib 0x00000001040e9b74 gtk_main_do_event + 1068
19 libgdk-3.0.dylib 0x00000001036ea8c4 _gdk_event_emit + 64
20 libgdk-3.0.dylib 0x000000010370ff70 gdk_event_dispatch + 52
21 libglib-2.0.0.dylib 0x00000001034e169c g_main_context_dispatch + 240
22 libglib-2.0.0.dylib 0x00000001034e19b8 g_main_context_iterate + 432
23 libglib-2.0.0.dylib 0x00000001034e1a20 g_main_context_iteration + 60
24 libgio-2.0.0.dylib 0x00000001032e429c g_application_run + 464
25 gimp 0x000000010201935c app_run + 476
26 gimp 0x00000001020186c4 main + 1136
27 dyld 0x000000018251bf28 start + 2236
```
> GIMP-CRITICAL: GeglBuffer *gimp_pickable_contiguous_region_by_seed(GimpPickable *, gboolean, gfloat, gboolean, GimpSelectCriterion, gboolean, gint, gint): assertion 'GIMP_IS_PICKABLE (pickable)' failed
> GIMP-CRITICAL: gimp_image_new_from_drawables: assertion 'drawables != NULL' failed
> GIMP-CRITICAL: gimp_container_remove: assertion 'object != NULL' failed
> GIMP-CRITICAL: gimp_pickable_flush: assertion 'GIMP_IS_PICKABLE (pickable)' failed
> GIMP-CRITICAL: GeglBuffer *gimp_pickable_contiguous_region_by_seed(GimpPickable *, gboolean, gfloat, gboolean, GimpSelectCriterion, gboolean, gint, gint): assertion 'GIMP_IS_PICKABLE (pickable)' failedhttps://gitlab.gnome.org/GNOME/gimp/-/issues/9688Selection with handles: moving using keyboard only possible when mouse pointe...2024-02-26T15:40:04ZJacob BoeremaSelection with handles: moving using keyboard only possible when mouse pointer is inside selectionOS: Windows 10 Home, 64-bits.
GIMP: both 2.10.34 and current master.
When making a rectangular or oval selection, the keyboard keys Alt+Ctrl(+Shift) can be used to move the selection. There is however an, in my eyes, counterintuitiv...OS: Windows 10 Home, 64-bits.
GIMP: both 2.10.34 and current master.
When making a rectangular or oval selection, the keyboard keys Alt+Ctrl(+Shift) can be used to move the selection. There is however an, in my eyes, counterintuitive difference between showing the selection with adjustment handles, and just the selection outline.
- When we show only the selection outline (happens when clicking inside the selection), the mentioned keys can be used to move the selection, no matter where the mouse cursor is. To me, this seems to be the most logical.
- However, when the selection adjustment handles are visible, the movement keys only work if the mouse pointer is inside the selection (except when inside the corner areas, which will change the selection size). I don't know if there are technical reasons for this, but from a user point of view, it would be better to also allow movement when the mouse is outside the selection.https://gitlab.gnome.org/GNOME/gimp/-/issues/9632After many "magic wand selection tool" uses program is baraly responding2023-07-31T03:51:28ZDaniel MartinekAfter many "magic wand selection tool" uses program is baraly responding### Environment/Versions
- GIMP Version: 2.10.34
- Package: <!--[flatpak? Installer from gimp.org? If another installer, tell us where from] (write it after the > symbol)--> gimp.org installer
- Operating System: <!--[Windows? macOS? Li...### Environment/Versions
- GIMP Version: 2.10.34
- Package: <!--[flatpak? Installer from gimp.org? If another installer, tell us where from] (write it after the > symbol)--> gimp.org installer
- Operating System: <!--[Windows? macOS? Linux? All?] (write it after the > symbol) --> windows 11
<!-- Note: bug reporters are expected to have verified the bug still exists
either in the last stable version of GIMP or on updated development code
(master branch). --> I am on latest stable version.
### Issue Description
<!-- Please provide a general description of the issue. -->
I was selecting a thing with the magic wand selection tool. First two selections followed by color corection were fine. (I was sellecting each object 5 to 10 minutes). When finishing the third object (took half an hour I guess amd occasianly using box select in subtract mode) I noticed a huge slowdown. First when switching tool mode from add to subtract. Now whole window feels sluggish. I tryed deleting change history (which was 153MB at that point). It did not help.
### Performance Log
<!-- Please record a performance log demonstrating the issue, and attach it to the report.
For more information, see
https://developer.gimp.org/core/debug/performance-logs/
[2023-06-20_23-12-49_Daniel_Martinek.etl](/uploads/086a39850f5ff917cace01a7490c0715/2023-06-20_23-12-49_Daniel_Martinek.etl)
[gimp-performance1.log](/uploads/a965d372de99983212b84404b85e4043/gimp-performance1.log)
### Performance Log Description
<!-- Please describe in detail the actions performed in the performance log.
If you added empty event markers to the log, please provide a description for them here.
If you recorded a screencast while recording the log, please attach it here. -->
### Additional Information
<!-- If there is any additional information, please provide it here. -->