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 497223 - crash in Project Management: trying to edit a fixed d...
crash in Project Management: trying to edit a fixed d...
Status: RESOLVED DUPLICATE of bug 372694
Product: planner
Classification: Other
Component: General
0.14.x
Other All
: High critical
: ---
Assigned To: planner-maint
planner-maint
: 497230 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-11-15 22:39 UTC by ajcantu
Modified: 2008-01-10 20:56 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Attachments
planner file that causes error (10.22 KB, application/x-planner)
2008-01-10 20:40 UTC, ajcantu
Details

Description ajcantu 2007-11-15 22:39:59 UTC
Version: 0.14.2

What were you doing when the application crashed?
trying to edit a fixed duration task


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.23.1-10.fc7 #1 SMP Fri Oct 19 14:35:28 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 392781824 vsize: 392781824 resident: 25190400 share: 17682432 rss: 25190400 rss_rlim: 18446744073709551615
CPU usage: start_time: 1195148719 rtime: 369 utime: 344 stime: 25 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/planner'

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496318896 (LWP 8614)]
(no debugging symbols found)
0x0000003456e0e0ff in waitpid () from /lib64/libpthread.so.0

Thread 1 (Thread 46912496318896 (LWP 8614))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 g_cclosure_marshal_VOID__BOOLEAN
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 g_cclosure_marshal_VOID__BOOLEAN
    from /usr/lib64/libplanner-1.so.0
  • #4 mrp_task_manager_recalc
    from /usr/lib64/libplanner-1.so.0
  • #5 mrp_object_set
    from /usr/lib64/libplanner-1.so.0
  • #6 ??
  • #7 ??
  • #8 ??
  • #9 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #10 g_cclosure_marshal_VOID__BOOLEAN
    from /lib64/libgobject-2.0.so.0
  • #11 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #12 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #13 g_cclosure_marshal_VOID__BOOLEAN
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #14 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #15 g_cclosure_marshal_VOID__BOOLEAN
    from /lib64/libgobject-2.0.so.0
  • #16 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #17 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #18 g_cclosure_marshal_VOID__BOOLEAN
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #19 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #20 g_cclosure_marshal_VOID__BOOLEAN
    from /lib64/libgobject-2.0.so.0
  • #21 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #22 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #23 g_cclosure_marshal_VOID__BOOLEAN
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #24 g_cclosure_marshal_VOID__BOOLEAN
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #25 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #26 g_cclosure_marshal_VOID__BOOLEAN
    from /lib64/libgobject-2.0.so.0
  • #27 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #28 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #29 g_cclosure_marshal_VOID__BOOLEAN
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #30 gtk_propagate_event
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #31 gtk_main_do_event
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #32 g_cclosure_marshal_VOID__BOOLEAN
    from /usr/lib64/libgdk-x11-2.0.so.0
  • #33 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #34 g_cclosure_marshal_VOID__BOOLEAN
    from /lib64/libglib-2.0.so.0
  • #35 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #36 gtk_main
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #37 main
  • #0 waitpid
    from /lib64/libpthread.so.0


----------- .xsession-errors (258752 sec old) ---------------------
Xlib:  extension "SHAPE" missing on display ":0.0".
Xlib:  extension "SHAPE" missing on display ":0.0".
Xlib:  extension "SHAPE" missing on display ":0.0".
Xlib:  extension "SHAPE" missing on display ":0.0".
Xlib:  extension "SHAPE" missing on display ":0.0".
Xlib:  extension "SHAPE" missing on display ":0.0".
Xlib:  extension "SHAPE" missing on display ":0.0".
Xlib:  extension "SHAPE" missing on display ":0.0".
Xlib:  extension "SHAPE" missing on display ":0.0".
Xlib:  extension "SHAPE" missing on display ":0.0".
Xlib:  extension "SHAPE" missing on display ":0.0".
Xlib:  extension "SHAPE" missing on display ":0.0".
Xlib:  extension "SHAPE" missing on display ":0.0".
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Maurice van der Pot 2008-01-10 20:14:12 UTC
*** Bug 497230 has been marked as a duplicate of this bug. ***
Comment 2 Maurice van der Pot 2008-01-10 20:16:20 UTC
Do you have a .planner file that I can use to reproduce this problem?

Alternatively, can you attach a stacktrace that includes debug symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.
Thanks in advance.
Comment 3 ajcantu 2008-01-10 20:40:49 UTC
Created attachment 102539 [details]
planner file that causes error

repro steps:

1) in the task list area, double-click on "4.1.1" to edit WBS "4.1.1 Merge..."
2) attempt to uncheck "Fixed duration" checkbox and application crashes
Comment 4 Maurice van der Pot 2008-01-10 20:56:57 UTC
Great, thanks! I verified that this problem has been fixed in the current development version. The next release will contain this fix.
It's actually a duplicate of another bug report.


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