[Gimp-user] Bug
Hello, I am running at iMac Intel 10.6.4 64 bit and every time I take a screenshot on a Gimpmade images from logotypes there is som irritating marks at the left corner. Is this a bug or? Thanks in advance. Spender [IMG] http://i1023.photobucket.com/albums/af353/Spender19/Skrmavbild2010-09-02kl093903.png [/IMG] -- Spender (via www.gimpusers.com) ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
[Gimp-user] Bug in the Gradient tool ?
Check your Preferences. On the Tool Options page make sure that the Gradients box is checked under Paint Options Shared Between Tools. Thank Saulgoode that solved Usually i dislike share options between tools, but i see now that may be very useful for the gradient -- photocomix (via www.gimpusers.com) ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
[Gimp-user] Bug in the Gradient tool ?
it happen to me with gimp 2.8 on win XP, Not sure if may be replicated in other OS, before report as a bug i would like to be sure 1)start gimp, change the default gradient with something other you may see in the toolbox the new gradient as the active gradient 2) click on the blend tool In its dialog you will see that ignore the change, if you use it it will draw with the default gradient 3) only way to change it is from the blend tool dialog change again the gradient In a fewer words the change of gradient if done trough the toolbox widget seems ignored, even if apparently the change is accepted Only from the Blend tool dialog seems possible change the gradient That become a problem not only when directly using the blend tool (where at least the problem is visible so easier to correct) but also using filters as Gradient Map ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
Re: [Gimp-user] Bug in the Gradient tool ?
Quoting Alchemie foto\grafiche fotocom...@yahoo.it: it happen to me with gimp 2.8 on win XP, There is no GIMP 2.8; perhaps you mean 2.6.8? 1)start gimp, change the default gradient with something other you may see in the toolbox the new gradient as the active gradient 2) click on the blend tool In its dialog you will see that ignore the change, if you use it it will draw with the default gradient 3) only way to change it is from the blend tool dialog change again the gradient In a fewer words the change of gradient if done trough the toolbox widget seems ignored, even if apparently the change is accepted Only from the Blend tool dialog seems possible change the gradient Check your Preferences. On the Tool Options page make sure that the Gradients box is checked under Paint Options Shared Between Tools. ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
[Gimp-user] Bug in preference/font ?
Hy before file a report to bugzilla i thought better report here, just to check if other may replicate and if is a Windows only problem On win xp, happen with gimp 2.6.5 (official) 2.6.6 (self compiled) and Gimp-painter 2.6.6 Problem Delete from Edit/preferences/folder/font the (default) path for C/windows/font has no practical effect. Gimp totally ignore the new preference and load the same all the fonts stored in Windows/Font even if that path was removed Reload the computer do not help This is problematic also because there may be fonts incompatible with Gimp but usable by other programs (i had there a few fonts crashing gimp at loading time, at least crashing my previous version of gimp,i removed them before install 2.6 so maybe they only crashed 2.4) -- photocomix (via www.gimpusers.com) ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
[Gimp-user] bug with two displays - windows XP
Hi Gimp users and developers, I noticed that using two displays is cause of error in the tool position. The tool position does not match with the pointer position. What is even more tedious is that if I go back to the single display configuration, Gimp continues to fail. I have to reinstall Gimp. Maybe you know a workaround, at least to avoid the tool re-installation. Thanks, Giovanni This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately. ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
Re: [Gimp-user] Bug 119646 – add polygonal selecti on tool
Sven Neumann wrote: And what's the benefit then over using the paths tool? Remember, the goal here is to make it easier to create polygonal selections. You can already do that by using the Polygon mode of the path tool and converting the resulting path to a selection. Sure, you could also do it using vector layers. But does that make it easy? I don't think so. I suppose it depends on how quickly you can make shapes with vectors. If it's about the same as with paths then obviously you're right, but if we're talking Inkscape speeds then it could be useful. I fail to see why the free select tool should be modifed at all. Is it in any way related to the problem at hand? The problem of quickly creating a polygonal selection? You seconded the idea on the bugzilla thread. Perhaps we haven't even figured out yet what the problem is? Would be nice if the people who asked for the polygonal selection tool explained what they would use that tool for. What are common usage scenarios for such a tool? How does it fit into your workflow? Well, I'm not requesting it, but what I got from the bugzilla report - particularly the comic book illustrator - was that users want to be able to switch quickly between drawing straight lines and drawing squiggly lines. In other words, brush-like flexibility but through the select tool. Paths don't draw squiggles and free select doesn't do straight lines. So I'm exploring possible solutions. If a good one can't be found, that's fine by me. Regards, David ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
Re: [Gimp-user] Bug 119646 – add polygonal select ion tool
Hi, On Wed, 2006-12-13 at 20:00 +, David Marrs wrote: Well, I'm not requesting it, but what I got from the bugzilla report - particularly the comic book illustrator - was that users want to be able to switch quickly between drawing straight lines and drawing squiggly lines. In other words, brush-like flexibility but through the select tool. If that is indeed the common usage scenario, then it might be best if we attempt to integrate this feature into the free select tool. Sounds like something that we needs decent planning and should be targetted for after the 2.4 release. Sven ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
[Gimp-user] Bug 119646 – add polygonal selecti on tool
Continuing the discussion on bugzilla (1) I have a suggestion for a possble third way. I remember something being written about vector layers in gimp and found a reference to it at google.com (2). If there was a tool that enabled one to draw vectors, they could be stroked, converted to a selection or converted to paths at the user's will. Although it's not a quick fix to the problem, it does avoid the possible complication that comes with modifying the free select tool (for example, assigning shift to both add-to-selection and draw-straight-line modifiers) or adding yet another select tool that isn't quite free select and isn't quite bezier path. Regards, David Appendix --- (1) http://bugzilla.gnome.org/show_bug.cgi?id=119646 (2) http://code.google.com/soc/gimp/appinfo.html?csaid=26F82BA0B5805CD9 ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
[Gimp-user] bug hunting binaries for Fedora Core 4
The Cooperative Bug Isolation Project is a joint effort by the University of Wisconsin-Madison, UC Berkeley, and Stanford University to bring debugging into the Internet age. Instrumented applications send feedback to our analysis center, where we use statistical debugging techniques to learn what goes wrong when the software crashes. CBI is pleased to announce that prebuilt, instrumented binaries of The GIMP are now available as ready-to-install RPMs for Fedora Core 4. We track stable releases, currently 2.2.8. Several other applications are available as well; see the download page for details. What we need most of all are more runs from real users like you! Even if you've never written a line of code in your life, you can help make things better for everyone simply by using our special bug-hunting packages. Read more (http://www.cs.wisc.edu/cbi/), download some packages (http://www.cs.wisc.edu/cbi/downloads/), and join in! Fedora Core 1 and Fedora Core 2 users can help too: see the CBI downloads page for selected versions of most instrumented applications for FC1 and FC2. project info: http://www.cs.wisc.edu/cbi/ downloads:http://www.cs.wisc.edu/cbi/downloads/ ___ Gimp-user mailing list Gimp-user@lists.xcf.berkeley.edu http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
Re: [Gimp-user] bug
Hi, Jozsef Mak [EMAIL PROTECTED] writes: Maybe by accident I discovered a bug in Gimp 2.2. This is what happened. I created a new gradient. Then in the gradient editor I clicked on the edit Left color. The color picker popped up. I chose the color I wanted but I forgot to close it. Next, I clicked the Right color in the gradient editor. The color picker popped up again. At this point, there were 2 color pickers open. I chose the color for the Right color and I clicked OK; the color picker closed, the gradient editor updated. But the first color picker was still open. I clicked on the OK button to close it but nothing happened. I clicked on it repeatedly but nothing. Then I closed the gradient editor. At this point the color picker was still open. Then I clicked again on the OK button and Gimp crashed. I repeated this numerous times and always got the same result. Please open a bug report in Bugzilla then. Reporting your problem here is a good way to let it be forgotten. Sven ___ Gimp-user mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
[Gimp-user] bug
Maybe by accident I discovered a bug in Gimp 2.2. This is what happened. I created a new gradient. Then in the gradient editor I clicked on the edit Left color. The color picker popped up. I chose the color I wanted but I forgot to close it. Next, I clicked the Right color in the gradient editor. The color picker popped up again. At this point, there were 2 color pickers open. I chose the color for the Right color and I clicked OK; the color picker closed, the gradient editor updated. But the first color picker was still open. I clicked on the OK button to close it but nothing happened. I clicked on it repeatedly but nothing. Then I closed the gradient editor. At this point the color picker was still open. Then I clicked again on the OK button and Gimp crashed. I repeated this numerous times and always got the same result. This was on a windows box. I repeated the same process on my Linux box but there everything went fine. Though my Gimp linux version still haven't been updated. jozsefmak ___ Gimp-user mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
Re: [Gimp-user] bug report for gimp-2.0pre1.tar.bz2
Hi, david [EMAIL PROTECTED] writes: In other words I have a password and account number and spent some time entering the info. So what happened?? You can surely point us to the bug number then? Sven ___ Gimp-user mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
Re: [Gimp-user] bug report for gimp-2.0pre1.tar.bz2
Hi, david wrote: I did bother to log on to the bug reporting site and entered the bugbut it is still occuring. In other words I have a password and account number and spent some time entering the info. So what happened?? Excuse me, I misread this (my mind filled in the not). The bug report doesn't ring any bells, though... if it's any help, I have tried to reproduce this, and I could not. I just had a quick search in bugzilla with likely keywords, and I didn't find your bug in the open bug reports... could you quote a bugzilla number, please? Or even add a comment to the bug itself? Thanks, Dave. -- David Neary, Lyon, France E-Mail: [EMAIL PROTECTED] ___ Gimp-user mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
Re: [Gimp-user] bug report for gimp-2.0pre1.tar.bz2
On Tue, 20 Jan 2004 11:07:07 + david [EMAIL PROTECTED] wrote: I open a new document and accept the default. I select the rectangular shape tool. I draw a square in the centre of the canvas...holding down the shift key to force a square. Then I select a foreground colour...red...and select the bucket fill tool. I fill the square with the red colour. I select copy and copy what is there as is. I then paste. Thats where it crashes. Does anyone else have this problem?? Where do you paste it? I tried pasting it back onto itself and into a new image and could not replicate the action you describe. -- Owen ___ Gimp-user mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
[Gimp-user] Bug Reports
Hi Is there a simple way of repoting a bug? Can I just post it here? Cheers david ___ Gimp-user mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
Re: [Gimp-user] Bug Reports
Hi, david wrote: Is there a simple way of repoting a bug? Can I just post it here? The GIMP uses a database-backed bug tracking package called Bugzilla. This allows us to keep track of the history of bugs, and know which ones are fixed, when we would like the unfixed ones to be fixed, and so on. We share this with GNOME, and the URL is http://bugzilla.gnome.org To enter a bug, you will need a bugzilla account. This is a very easy process - when you ask to enter a bug (click on the New link), if you're not logged in you will be asked for a log-in and password, or be offered the possibility of signing up. To enter a bug against the GIMP, click New, then GIMP, and in the following (horrible looking) page, select a Component, enter a summary and a description. The rest of the stuff on this page doesn't need to be filled in, and probably shouldn't be filled in most of the time. And that's it. Guidelines for writing good bug reports are available here... http://bugzilla.gnome.org/bug-HOWTO.html Cheers, Dave. -- David Neary, Lyon, France E-Mail: [EMAIL PROTECTED] ___ Gimp-user mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
Re: [Gimp-user] Bug Reports
Hi, On Sat, 2004-01-10 at 11:07, david wrote: Is there a simple way of repoting a bug? Can I just post it here? The simplest way is to point your browser to http://bugs.gimp.org and follow the steps there. The GIMP uses GNOME Bugzilla to keep track of bugs, enhancement requests etc. Please check if your bug has been reported before prior to posting a new bug. If you're looking for a more detailed description please take a look at http://mmmaybe.gimp.org/bugs/howtos/bugzilla.html Hope this helps. Sincerely, ./Brix -- Henrik Brix Andersen [EMAIL PROTECTED] ___ Gimp-user mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
[Gimp-user] bug triage for 2.0
Hi all, As those of you who follow bugzilla may have noticed, I have started attacking bugs on the 2.0 milestone. It is now clear that not all of these will be fixed before 2.0. We will need to re-distribute the ones that will not be fixed among other milestones, or close them. As rough guidelines, anything that we hope to fix before 2.0 should stay on the 2.0 milestone. We should prioritise these, so that when we want to release, they can be moved to the 2.0.1 milestone (reserved for things that really need fixing, but which aren't going to be fixed for 2.0). Bugs which are important to fix should be addressed early in the unstable release cycle, and should therefore be added to the 2.2 milestone. We will probably add milestones when we start on a 2.1 branch to further carve up these bugs. Anything which is a feature request and doesn't have an identifiable owner should go to Future. I've thought about this, and there is a certain logic. Either the feature has an owner we can hassel to do the feature, or no-one wants to do it. In that case, there's no point adding it to a milestone closer than Future, because it won't be done. When someone claims a feature request and says they'll do it, it can then be added to a more reasonable milestone. Any bug against 1.0.x should be closed WONTFIX. 1.0.x is ancient history. Any bug which has been in NEEDINFO for longer than 6 months should be closed INCOMPLETE. The original author can then re-open it if he considers the bug is still valid and he wants to add more info. Any bug which has not had a comment added for over a year should be bumped to 2.2, and have a comment added asking what the status is. If, in 6 months time, there are still no further comments, the bug can be closed WONTFIX. We are still working towards a 2.0 release before Christmas. Looking at CVS, we are not that far away from it. I feel that the pre-release cycle will throw up some surprises and that we will have trouble getting to 2.0 that early, but that's another matter. There are now under 100 bugs on the 2.0 and 1.3.x milestones. I would like to see that reduced to around 40, and I would also like to see more than 3 or 4 people closing bugs. To get a 2.0 release soon will be a huge job, and Sven and mitch cannot carry on doing all the bug fixing. If you have any free time at all, please pick a bug and help out. Cheers, Dave. -- David Neary, Lyon, France E-Mail: [EMAIL PROTECTED] ___ Gimp-user mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
[Gimp-user] Bug Week!
Hi all! As some of you might already know, next week is the pre-2.0 GIMP Bug Week. The first pre-releases of 2.0 will start coming out the door around the end of this month, and we need to get some concentrated testing done before then, as well as classifying known bugs into those which will be fixed before 2.0 final and those which will be fixed later. For those of you who aren't familiar with the idea, a bug week is a week when we make an extra effort to find bugs (and fix them) with the assistance of the general public. We invite people to join up on IRC (irc://irc.gnome.org/#gimp) to give us feedback, to help the developers prioritize bugs to be fixed, and to report bugs (if you're intimidated by Bugzilla). Apart from bug fixing we also need GIMP users to volunteer for bug triaging. If you are unfamiliar with the concept of bug triaging, the GNOME Project has a nice description of the bug triage concept - please see http://developer.gnome.org/projects/bugsquad/triage/ So if you're a GIMP user and wants to help the developers getting the source code in shape for 2.0 - or if you're a developer with (at least) minimal experience with The GIMP and wants to help fixing bugs in the source - you should definitely show up at The GIMP Bug Week. See you at The GIMP Bug Week! On behalf of the The GIMP Developers, ./Brix -- Henrik Brix Andersen [EMAIL PROTECTED] ___ Gimp-user mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
[Gimp-user] Bug with Sobel filter ?
Hello, I think I've found a bug with the sobel filter. However before I fill a bug report I'd like to know if it is just specific to the windows version. Can people on Linux reproduce this: -Create a new image (default: 256 x 256, white background) -Swap foreground and background colour so that white is foreground -Use the text tool to create some text, do not anchor the text but promote it to a new layer -text layer to image size -uncheck keep transparency -Apply sobel This result in the outline of the text layer before it was resized. How can that be ? However if you do this (which should be equivalent to what is above): -Create a new image(default: 256 x 256, white background) -Swap foreground and background colour so that white is foreground -Create a new transparent layer -Use the text tool to create some text, anchor it to the transparent layer The result is the same as above but when I apply sobel, it works Guillaume ___ Gimp-user mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
Re: [Gimp-user] Bug with Sobel filter !
Hi. I just tried it with gim 1.2.5 on a GNU/Linux system, it did happen here. I figured out what is happening, and indeed, it may be filled in as a bug. It happens that a transparente region of the layer has got hidden RGB information. This is unseen, but you can maximize the alpha channel to Full opacity using the Curves tool. What happens is that the text tool sets the RGB color in the transparent region to a different color than Layer to Image Size does. The Sobel filter - and here is your bug - seens to ignore the alpha channel when doing it's work. Thus, your layer is seen as a white rectangle surrounded by a black background, by the Sobel filter. If you happen to have gimp-perl working, use Image-Alpha-Clear Alpha before applying the sobel filter and it will work. Actually this whole procedure shows up a bug in the text tool also - the background color it uses should not be the same as the foreground. But since the text tool is being totally rewritten for the next GIMP, and this bug doesn't byte, you can leave it off the reports, IMHO. JS -- [EMAIL PROTECTED] wrote: Hello, I think I've found a bug with the sobel filter. However before I fill a bug report I'd like to know if it is just specific to the windows version. Can people on Linux reproduce this: -Create a new image (default: 256 x 256, white background) -Swap foreground and background colour so that white is foreground -Use the text tool to create some text, do not anchor the text but promote it to a new layer -text layer to image size -uncheck keep transparency -Apply sobel This result in the outline of the text layer before it was resized. How can that be ? However if you do this (which should be equivalent to what is above): -Create a new image(default: 256 x 256, white background) -Swap foreground and background colour so that white is foreground -Create a new transparent layer -Use the text tool to create some text, anchor it to the transparent layer The result is the same as above but when I apply sobel, it works Guillaume ___ Gimp-user mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user ___ Gimp-user mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
[Gimp-user] Bug triage guides
Hi, I just found this page... http://developer.gnome.org/projects/bugsquad/triage/ ...which explains the ideas behind filtering bugs. It's actually quite a simple explanation, and applies quite well to the gimp when you substitute #gimp for #bugs :) Anyone who wants to contribute to the gimp bug triage, but who doesn't have permission to change milestones, please mail me, and I will either get you sorted, or give you a list of people who can change milestones (more likely the former). Be warned, the pointy stick approach will be in effect - if you make changes that you shouldn't (for example, to bugs in other products than the gimp), you will lose your rights. Cheers, Dave. -- David Neary, Lyon, France E-Mail: [EMAIL PROTECTED] ___ Gimp-user mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
[Gimp-user] Bug in Open file Preview
Hi! I've found a bug in the Open file... Dialog and the preview option. I don't know, if it's already reported. If you select several images and click on the preview button, gimp leaves out every second image and does not index them. You have to manually select the images and click on the preview button. I'am using Gimp 1.2.3 under GNU/Linux. -- Oliver Rapp http://www.blup-bbs.de ___ Gimp-user mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
