GNOME Bugzilla – Bug 491224
Open and Save dialog widths are way too wide
Last modified: 2014-12-22 16:17:25 UTC
For some weird reason, the File/Open and File/Save As dialog boxes are coming up way too wide on my system. I run a dual-monitor setup, with monitor 1 (the primary monitor, on the right) at 1920x1200 and monitor 2 (on the left) at 1280x1024. When the dialog boxes pop up, they are at least 1000 pixels wide. There is a ton of "dead" white space used by the Name column, which makes correlating it with the modified date and the preview window difficult without manually resizing the window each time I open a file. Even more inconvenient, I tend to keep the main GIMP window close to the left edge of the primary monitor screen, and about a quarter of the dialog boxes' width is actually displayed on my secondary monitor, with the boxes split across the screen. Since the GIMP doesn't save the positions of the dialog boxes, in order to be useful, I have to manually move the dialog box over onto the main screen each and every time I want to open and/or save a file. The GIMP didn't exhibit this behavior in the previous version (2.2.17) that I was running, and I uninstalled and reinstalled the program when I installed the 2.4 version.
That's a known problem in some versions of GTK+ and should go away when you upgrade. Please check the bugs on the GTK+ project, this has likely been reported before.
Reassigning to the Installer component as this should be fixed by an upgrade to GTK+ 2.12.
I am using Gtk+ 2.12.1 with svn trunk and seeing this bug, on an Ubuntu Feisty system. I will confirm the bug report and set OS to "all", but presumably it should be reassigned to Gtk+.
GIMP 2.4.1 ships with GTK+ 2.12.1, but the problem is visible there (though truthfully, I wouldn't have noticed this if not for the bug report). Anyway, it appears that GIMP positions the dialogs relatively to it's own window, so when the window is near the screen split (I'm also using 1920x1200+1280x1024 configuration), the dialog will span both displays.
*** Bug 503059 has been marked as a duplicate of this bug. ***
I assume this is no longer an issue.