GNOME Bugzilla – Bug 659301
gradient editor will not redisplay after I close it
Last modified: 2011-11-01 22:22:15 UTC
I am using gimp2.6.11 in Natty Narwhal 11.04 with Unity. When I start gimp, edit a gradient i messed up, couldn't undo(no undo button) so I closed it and then when i tried to reopen it, it wouldn't display. tried from every from all windows and docks, double checked there wasn't a window hiding. So now I'm down to restarting gimp everytime this happens. Very frustrating. Also Sometimes when im working with multiple windows in gimp, if I select one of them, and go to the menu (unity at the top of the desktop), it will only display about 5-10px of the menu from top to bottom when i click on the menu. Lots of glitches. Is this a Unity problem, does anyone know if 11.10 OneiricOcelot is any better? I've been tempted to test it out on another machine, and afraid of a system crash. I've been looking at this link... https://wiki.ubuntu.com/OneiricOcelot/TechnicalOverview but was wondering if anyone has successfully upgraded without problems to apache or if it is even going to fix these gimp problems... sorry for long post, I will attach a screen pic next time i get the 2nd glitch Frenzy
Does clicking "edit" in the gradient list bring it back, or double clicking the icon in the same list?
I just tried it. After I edit a gradient once, I am unable to bring back the list (as a separate window). When I run the program from the beginning and I am able to edit or create a new gradient, I can see the edit options and it's all gravy, but as soon as I close the window I have to restart the whole program. I'll try troubleshooting some more later.
Looks like it's the same behaviour as in bug https://bugzilla.gnome.org/show_bug.cgi?id=662240 Unfortunately it's most likely Ubuntu fault. I've reported a bug on Launchpad, so you can mark it as affecting you or add some comment. Link to the bug: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/878510
Thanks, resolving as duplicate. *** This bug has been marked as a duplicate of bug 662240 ***