Hide Forgot
Description of problem: When I run planner on F16 it opens up with a default minimum window size of 2573x498, and doesn't let me shrink it (I can only make it taller or wider). Also, it doesn't respond to gnome-shell gestures: if I drag it to the top it doesn't maximize, and if I drag it to either the right or left side of the screen it doesn't occupy half of the screen. This makes it unusable. Version-Release number of selected component (if applicable): 0.14.5-4 How reproducible: Always. Steps to Reproduce: 1. run 'planner' 2. 3. Actual results: The program starts with a minimum window size of 2573x498, and the window can't be maximized. Expected results: The last window size should be used, and the window should behave like any other GNOME window. Additional info: I am using two monitors, with a virtual desktop resolution of 3600x1080, and nvidia drivers. This is the only GNOME application with such weird behavior.
works fine on a single screen anyway, http://osdir.com/ml/planner-list/2011-11/msg00000.html suggests it been a bug for a while however
"Works for me" with multi-head, can I get the output of... gconftool-2 --dump /apps/planner/ui please
(In reply to comment #1) > works fine on a single screen anyway, > http://osdir.com/ml/planner-list/2011-11/msg00000.html suggests it been a bug > for a while however Yep. That was me as well ;-)
(In reply to comment #2) > "Works for me" with multi-head, can I get the output of... > > gconftool-2 --dump /apps/planner/ui > > please Sure, here it goes: <gconfentryfile> <entrylist base="/apps/planner/ui"> <entry> <key>active_view</key> <value> <string>resource_usage_view</string> </value> </entry> <entry> <key>main_window_height</key> <value> <int>498</int> </value> </entry> <entry> <key>main_window_maximized</key> <value> <bool>false</bool> </value> </entry> <entry> <key>main_window_position_x</key> <value> <int>906</int> </value> </entry> <entry> <key>main_window_position_y</key> <value> <int>168</int> </value> </entry> <entry> <key>main_window_width</key> <value> <int>2573</int> </value> </entry> </entrylist> </gconfentryfile> BTW thks for the prompt reply.
Does anyone that is *not* you have this problem :-) ? I can't seem to reproduce it from scratch. Clearly the "main_window_width" setting is now stored as 2573, so presumably at this stage its simply honouring its own configuration, with a probably original bug of selecting that value in the first place, but I can't get it to pick a stupid original value when I blow away my config. Anyway, if you (making sure planner is shutdown) do... gconftool-2 -s /apps/planner/ui/main_window_width 500 -t int gconftool-2 -s /apps/planner/ui/main_window_position_x 100 -t int and launch planner again does it then have a sane 500 pixel wide window ? or does it persist with the mega width.
(In reply to comment #5) > Does anyone that is *not* you have this problem :-) ? I can't seem to reproduce > it from scratch. Yeah, I know, I've been cursed ;-) It does seem too odd, I know, but for some reason it happens here. > Clearly the "main_window_width" setting is now stored as 2573, so presumably at > this stage its simply honouring its own configuration, with a probably original > bug of selecting that value in the first place, but I can't get it to pick a > stupid original value when I blow away my config. > > Anyway, if you (making sure planner is shutdown) do... > > gconftool-2 -s /apps/planner/ui/main_window_width 500 -t int > gconftool-2 -s /apps/planner/ui/main_window_position_x 100 -t int > > and launch planner again does it then have a sane 500 pixel wide window ? or > does it persist with the mega width. Unfortunately, the changes are stored, but the window still appears ridiculously large: shadow ~ gconftool-2 -s /apps/planner/ui/main_window_width 500 -t int shadow ~ gconftool-2 -s /apps/planner/ui/main_window_position_x 100 -t int shadow ~ gconftool-2 --dump /apps/planner/ui <gconfentryfile> <entrylist base="/apps/planner/ui"> <entry> <key>active_view</key> <value> <string>resource_usage_view</string> </value> </entry> <entry> <key>main_window_height</key> <value> <int>498</int> </value> </entry> <entry> <key>main_window_maximized</key> <value> <bool>false</bool> </value> </entry> <entry> <key>main_window_position_x</key> <value> <int>100</int> </value> </entry> <entry> <key>main_window_position_y</key> <value> <int>168</int> </value> </entry> <entry> <key>main_window_width</key> <value> <int>500</int> </value> </entry> </entrylist> </gconfentryfile> shadow ~ planner & [1] 22890 shadow ~ xwininfo xwininfo: Please select the window about which you would like information by clicking the mouse in that window. xwininfo: Window id: 0x340004e "Unnamed - Planner" Absolute upper-left X: 101 Absolute upper-left Y: 196 Relative upper-left X: 10 Relative upper-left Y: 36 Width: 2573 Height: 498 Depth: 24 Visual: 0x21 Visual Class: TrueColor Border width: 0 Class: InputOutput Colormap: 0x20 (installed) Bit Gravity State: NorthWestGravity Window Gravity State: NorthWestGravity Backing Store State: NotUseful Save Under State: no Map State: IsViewable Override Redirect State: no Corners: +101+196 -926+196 -926-386 +101-386 -geometry 2573x498+91+160 shadow ~ gconftool-2 --dump /apps/planner/ui <gconfentryfile> <entrylist base="/apps/planner/ui"> <entry> <key>active_view</key> <value> <string>resource_usage_view</string> </value> </entry> <entry> <key>main_window_height</key> <value> <int>498</int> </value> </entry> <entry> <key>main_window_maximized</key> <value> <bool>false</bool> </value> </entry> <entry> <key>main_window_position_x</key> <value> <int>100</int> </value> </entry> <entry> <key>main_window_position_y</key> <value> <int>168</int> </value> </entry> <entry> <key>main_window_width</key> <value> <int>2573</int> </value> </entry> </entrylist> </gconfentryfile> So... should I look for a priest? ;-) Any other clue?
Also, please don't forget the fact that, as I mentioned on planner list, it isn't opening files created by planner 0.14.4 (it opens as if nothing had been loaded, but doesn't issue any errors). I use planner 0.14.4 on Ubuntu 11.04 at work. I rebuilt planner 0.14.4-34 from a F15 SRPM and it at least opens the files created by 0.14.4, even though it suffers from the same window size problem (at least I get to edit my data). Maybe I should file a separate issue for this?
Wow... I guess I just fixed it by accident. I opened 0.14.4-34 and I realized the scrollbar for the left-hand panel on the Gantt view (with WBS, Name and Work columns) was tiny because the 2nd column (Name) was huge. I resized it and -- bingo! -- I regained control of the window size! =) My guess is that planner internally uses the desired size for this panel (considering the real size of its columns) when it calculates the minimum size for the window, and this was causing the problem (it doesn't explain however why the window wouldn't maximize -- which it does now). After fixing this on 0.14.4 I was able to upgrade back to 0.14.5 and it was working again. ... except for the fact that it doesn't open a .planner file passed on the command line. If I do planner somefile.planner on 0.14.4 it works, but if I do it on 0.14.5 it opens as if no file has been informed. If I then open the file from the application it loads and displays correctly. So, I am now able to use planner on F16 again, but something's broken.
so original problem got a workaround anyway, closing. Feel free to file a new one if there is a remaining problem. Mixing them in one issue will lead to lots of confusion.
(In reply to Andre Costa from comment #8) > Wow... I guess I just fixed it by accident. > > I opened 0.14.4-34 and I realized the scrollbar for the left-hand panel on > the Gantt view (with WBS, Name and Work columns) was tiny because the 2nd > column (Name) was huge. I resized it and -- bingo! -- I regained control of > the window size! =) > > My guess is that planner internally uses the desired size for this panel > (considering the real size of its columns) when it calculates the minimum > size for the window, and this was causing the problem (it doesn't explain > however why the window wouldn't maximize -- which it does now). > > After fixing this on 0.14.4 I was able to upgrade back to 0.14.5 and it was > working again. > > ... except for the fact that it doesn't open a .planner file passed on the > command line. If I do > > planner somefile.planner > > on 0.14.4 it works, but if I do it on 0.14.5 it opens as if no file has been > informed. If I then open the file from the application it loads and displays > correctly. > > So, I am now able to use planner on F16 again, but something's broken. Thanks I had exactly the same resize problem with planner 0.14.5 and this fixed it for me!