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 644061 - Crash on zoom to fit
Crash on zoom to fit
Status: RESOLVED DUPLICATE of bug 550559
Product: planner
Classification: Other
Component: General
0.14.x
Other Linux
: High critical
: ---
Assigned To: planner-maint
planner-maint
Depends on:
Blocks:
 
 
Reported: 2011-03-07 00:16 UTC by John Pirie
Modified: 2011-03-07 10:55 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description John Pirie 2011-03-07 00:16:20 UTC
Planner 0.14.4 crashes and hangs when the following procedure is followed:

1. open planner
2. Go to Actions -> Insert Task.
3. Go to Actions -> Edit Task Properties
4. Change the work field to 150d
5. Click the close button
6. Click View -> Zoom To Fit.

For me the program crashes at this point and seems to get stuck in an infinite loop, constantly printing in the terminal: 

** (planner:9466): CRITICAL **: mrp_time2_add_seconds: assertion `secs >= 0' failed


It seems that on other projects too, when the project is zoomed too far out and the user wishes to make everything bigger, zoom to fit works fine. However if the project is zoomed in too far and the user wishes to zoom out, zoom to fit crashes the program.
Comment 1 Fabio Durán Verdugo 2011-03-07 02:31:56 UTC
Thanks for taking the time to report this bug.
Without a stack trace from the crash it's very hard to determine what caused it.
Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!

I can't reproduce in FC14 the same version (0.14.4)
Comment 2 Alexandre Franke 2011-03-07 10:55:08 UTC
This is a known issue and it has been fixed in master. See bug 550559.

(In reply to comment #1)
> I can't reproduce in FC14 the same version (0.14.4)

That's probably because the version in FC14 has the patch that fixes the issue applied.

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