GNOME Bugzilla – Bug 522443
Gimp layer manage problem - Don't show Current Layer
Last modified: 2008-10-30 20:11:16 UTC
Please describe the problem: when create a new picture, button don't work for layer manage. Need click up auto button, These is button can work. Second, Click current Layer, click edit picture area, don't show current layer for layer manage. Steps to reproduce: 1. create new picture, first problem can reproduced. 2. click current layer for layer manage. click edit picture area. don't show current layer for layer manage. second problem can reproduced. Actual results: 1. create new picture, first problem can reproduced. 2. click current layer for layer manage. click edit picture area. don't show current layer for layer manage. second problem can reproduced. Expected results: When create new picture, create new layer, can show layer for layer manage. When click current layer for layer manage, click edit picture area, can show current layer for layer manage. Does this happen every time? Every time Other information: no have , thank you. i hope these is problem can solve.
Please don't use the bug-tracker to ask for help. Obviously you have problems using GIMP and you will certainly get people to help you if you ask on the gimp-user mailing-list.
Actually - This is not a user error... there is a clash somewhere that causes this problem... It started with this latest release. Whether or not it is a Gimp problem is another issue... Basically all of the controls on the layer dialog are completely inactive no matter how many images you create... To fix the issue on my system (Arch) - I had to delete my user profile (it got corrupted) and switch from the murrine engine to clearlooks... So it may be a problem with murrine...
Sorry , I am install gimp 2.4.5 to another computer Today. gimp no have problem. about layer problem. maybe is user profile problem. Best when install gimp let it look at profile later. Thank you everyone.
I'm going to un-resolve this, because there is clearly something wrong if the controls in the layers dialog don't work. It's hard to see how a theme engine could be responsible. I won't confirm the bug report, but INVALID doesn't seem right at this point. Bug reporters, what distro are you using, and what window manager, please?
Arch Linux 2007.08-2 with Fluxbox and Murrine... I deleted my profile, and haven't seen the problem again. I can get Gimp to crash consistently with Murrine though...
When select a layer , leave layer manage , click picture edit area. current layer is color too light see not pure for layer manange. This is a problem.
Jbaker: can you clarify what "deleted my profile" means exactly? Do you mean the "config" folder in your home dir, or the .gimp-2.4 folder, or something else? (The murrine crash has been reported before: we think it is a problem in murrine, not Gimp.) Wide288: what Linux distro are you using? Is it Ubuntu, Debian, Arch, or what? What window manager? Is it metacity, fluxbox, or what?
I use Gimp 2.4.5 for windows XP now.
The folder I deleted was the .gimp-2.4 in my home directory. I'm one of those users that completely customize my Gimp setup. I've had these types of problems before. A new release comes out, and because of different changes to the standard "menurc", "sessionrc", and "controllerrc" files my profile will not work with the new release... This could very well be one of those times... Since I do customize so drastically, I always try to save my "menurc" file and "controllerrc" file and just have Gimp recreate all other folders and files. But this time that didn't work so I ended up just starting a new profile from scratch... Currently murrine is working fine as long as I don't switch to the small theme. Gimp will crash on murrine with the small theme when you create a new image. It will open images fine, but crashes when creating a new image... The strangest thing to me about this problem is that the layers in the image and the controls in the layer dialog were all visible and active as long as the layers dialog was not docked with any other dialog. As soon as I docked the layers dialog, the layers disappeared, and all widgets switched to inactive. I'll keep using the setup I have now, and if the problem happens again I'll investigate a little more and upload the profile...
Created attachment 107379 [details] Corrupted "sessionrc" It's the "sessionrc" file... Notes: - Tested this file on Arch Linux, Ubuntu Linux, and Windows XP... They all have the same problem... - I never hand edited this file, this was written purely by Gimp... - As long as the layers dialog remains docked, You cannot see the layers in the image and the controls are inactive. Undock it, and it starts working... - You can even close all of the other dialogs in the setup, close and restart Gimp to have Gimp re-write the sessionrc, and the problem still persists...
The sessionrc file shows that you have "follow active image" set to False for that dock. (This is controlled by a check-box in the image-selector at the top of the dock.) I expect that if you change this, it will start to work. Could you check, please?
Good Eye, that did it... :o) A couple of things of that would help in the future: If the "Follow active image" is set to false and there are no images open... - All dialogs could be set to the first opened or created image... - Or at least the combo box could have "No image selected" - When docking or undocking dialogs, each dialog should maintain it's own settings... --- This is what caught me... I was working on a project and I had two images open. I had pulled my layers dialog out at some point and I wanted to copy some paths from one image to the other so I set my paths dialog to false. and then I ended up docking my layers dialog back onto the paths dialog. I did not realize that docking dialogs changed the "follow active image" setting... and it won't revert back when undocked... because I did not explicitly set the setting on the layers dialog, I really didn't think of checking it... anyway... problem solved and something learned... thanks, jbaker
"Follow active image" is a property of the dock, not of an individual dialog -- otherwise it would be impossible to know. Anyway, it is clear now that this is NOTABUG -- but even so it might be worth thinking about whether there is any way to make this more intuitive. I'm sure Sven knew right from the start what the problem was, so this has basically been a learning experience for me. Thanks for helping me figure it out.