GNOME Bugzilla – Bug 567113
gnome-window-properties fails to set double-click-on-title-bar properly
Last modified: 2009-01-10 19:24:00 UTC
Please describe the problem: When gnome-window-properties (i.e., "Window Preferences") is used to select the Title Bar Action: "Maximize Horizontally", the value that ends up in gconf appears as "toggle_maximize_horiz". When selecting "Maximize Vertically", the value appears as "toggle_maximize_vert" According to the descriptive help provided for that configuration item by GConf Editor, the appropriate value should be "toggle_maximize_horizontally", "toggle_maximize_vertically", etc. Steps to reproduce: 1. Using gnome panel system menu (preferences menu), activate "Windows" (gnome-window-properties). 2. Select Title-Bar Action: "Maximize Horizontally", and close. 3. Logout/Login or reboot 4. Using gconf-editor, inspect apps/metacity/general/action_doubleclick_titlebar Actual results: The action_doubleclick_titlebar value is set to 'toggle_maximize_horiz'. This results in the following ~/.xsession-errors log entry: "Window manager warning: GConf key '/apps/metacity/general/action_double_click_titlebar' is set to an invalid value", apparently being truncated at As a consequence, when the user double-clicks on the title bar, the window is simply maximized (default), Expected results: The window should instead be maximized horizontally, vertically, etc., according to the user's selection in the gnome-window-properties. Does this happen every time? This happens every time. Other information: Gnome 2.24.2.
I should also add that manually editing the value to the full text of "toggle_maximize_horizontally" or "toggle_maximize_vertically" does produce the intended behavior (the window is then properly maximized horizontally or vertically as desired).
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 554962 ***
Thank you for the response, Jens. Sorry for not finding the existing bug.