After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 656945 - side panel size reset at each startup
side panel size reset at each startup
Status: RESOLVED DUPLICATE of bug 608203
Product: evolution
Classification: Applications
Component: Shell
3.0.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2011-08-20 06:44 UTC by Yves-Alexis Perez
Modified: 2011-09-07 07:40 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Yves-Alexis Perez 2011-08-20 06:44:32 UTC 
Hey,

I was experiencing this on 2.32 but thought it might have been fixed in 3.0, but definitely not, so I'm reporting. 

Each time evolution is started, the side panel (with the folders) size is reset to a default, which is way to tiny here (or maybe it's the right panel which is too wide, no idea). Anyway, if the default size doesn't fit, it's really annoying to have to resize it each time we start evolution.

regards,
-- 
Yves-Alexis
Comment 1 Yves-Alexis Perez 2011-08-20 06:58:20 UTC 
And indeed, /apps/evolution/shell/view_defaults/folder_bar/width gconf key is reset (to 167) each time evolution starts.
Comment 2 Milan Crha 2011-09-06 17:03:12 UTC 
Thanks for a bug report. Do you have your evolution window maximized all the time and what size is it when you demaximize it? I'm asking this because there was a long-standing bug #608203 which sounds exactly the same as your issue.
Comment 3 Yves-Alexis Perez 2011-09-07 07:39:56 UTC 
Yeah, that could definitely be the same thing. Resizing the side panel when the window is not maximized, the size is kept when quitting evolution.

For now this workaround is ok, and i'll wait for 3.2 :)
Comment 4 Yves-Alexis Perez 2011-09-07 07:40:43 UTC 

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