Bug 449840 - Gimp save dialog broken
Summary: Gimp save dialog broken
Status: RESOLVED DUPLICATE of bug 445923
: 458685 (view as bug list)
Alias: None
Product: openSUSE 11.1
Classification: openSUSE
Component: GNOME (show other bugs)
Version: RC 1
Hardware: Other Other
: P3 - Medium : Minor (vote)
Target Milestone: ---
Assignee: Federico Mena Quintero
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-11-27 21:09 UTC by Michael Monreal
Modified: 2008-12-23 21:54 UTC (History)
2 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
Screenshot (18.86 KB, image/png)
2008-11-27 21:10 UTC, Michael Monreal
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Monreal 2008-11-27 21:09:39 UTC
The save dialog in (at least) gimp is broken, have a look at the screenshot. It looks like it does not set a correct minimum window size.
Comment 1 Michael Monreal 2008-11-27 21:10:28 UTC
Created attachment 256348 [details]
Screenshot
Comment 2 Vincent Untz 2008-12-12 15:12:28 UTC
Michael: I can't reproduce this. Do you still see it?
Comment 3 Vincent Untz 2008-12-13 03:04:54 UTC
*** Bug 458685 has been marked as a duplicate of this bug. ***
Comment 4 Karl Eichwalder 2008-12-15 07:55:35 UTC
> Karl: I can't reproduce this. Can you reproduce this each time you open GIMP?
> (please reply in bug 449840).

As I said, it happens the first time you try to same an image.

To repro it create a new user.  As this new user start gimp. Click "New", paint a dot and click "File" > "Save as".
Comment 5 Michael Monreal 2008-12-15 19:40:23 UTC
I'm also still seeing this, still on RC1. Is there a way to update to GM/Final yet?
Comment 6 Vincent Untz 2008-12-19 14:34:29 UTC
Michael: I guess that you know how to update to GM now ;-) (couldn't reply earlier, sorry)
Comment 7 Federico Mena Quintero 2008-12-23 21:54:16 UTC
Marking as duplicate of bug #445923 - the patch in there fixes this problem.

*** This bug has been marked as a duplicate of bug 445923 ***