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 379106 - crash in Project Management: Saving a project.
crash in Project Management: Saving a project.
Status: RESOLVED DUPLICATE of bug 347555
Product: planner
Classification: Other
Component: General
0.14
Other All
: High critical
: ---
Assigned To: planner-maint
planner-maint
Depends on:
Blocks:
 
 
Reported: 2006-11-25 12:37 UTC by andrew.jones11235
Modified: 2006-11-27 22:40 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description andrew.jones11235 2006-11-25 12:37:46 UTC
What were you doing when the application crashed?
Saving a project.  


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.18-1.2849.fc6 #1 SMP Fri Nov 10 12:45:28 EST 2006 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: Enforcing
Accessibility: Disabled
----------- .xsession-errors ---------------------
  self.statusbar = gnome.ui.AppBar (True, True)
Traceback (most recent call last):
  File "/usr/lib/python2.4/site-packages/gnomebt/manager.py", line 274, in ?
    BTManager ().main ()
  File "/usr/lib/python2.4/site-packages/gnomebt/manager.py", line 85, in __init__
    if not self.btctl.is_initialised():
gobject.GError: Can't get device id of hci0
(planner:18571): Gtk-CRITICAL **: gtk_widget_event: assertion `WIDGET_REALIZED_FOR_EVENT (widget, event)' failed
(planner:18571): Gtk-CRITICAL **: gtk_widget_event: assertion `WIDGET_REALIZED_FOR_EVENT (widget, event)' failed
(planner:18571): Gtk-CRITICAL **: gtk_widget_event: assertion `WIDGET_REALIZED_FOR_EVENT (widget, event)' failed
** (bug-buddy:18611): WARNING **: Couldn't load icon for Open Folder
--------------------------------------------------

Memory status: size: 75194368 vsize: 0 resident: 75194368 share: 0 rss: 16592896 rss_rlim: 0
CPU usage: start_time: 1164457213 rtime: 0 utime: 1725 stime: 0 cutime:1667 cstime: 0 timeout: 58 it_real_value: 0 frequency: 0

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208191280 (LWP 18571)]
(no debugging symbols found)
0x00b9a402 in __kernel_vsyscall ()

Thread 1 (Thread -1208191280 (LWP 18571))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 planner_gantt_print_do
  • #5 planner_gantt_row_get_geometry
  • #6 gnome_canvas_root
    from /usr/lib/libgnomecanvas-2.so.0
  • #7 gnome_canvas_item_new
    from /usr/lib/libgnomecanvas-2.so.0
  • #8 gtk_marshal_BOOLEAN__VOID
    from /usr/lib/libgtk-x11-2.0.so.0
  • #9 g_value_set_static_boxed
    from /lib/libgobject-2.0.so.0
  • #10 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #11 g_signal_override_class_closure
    from /lib/libgobject-2.0.so.0
  • #12 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #13 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #14 gtk_widget_get_default_style
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 gnome_canvas_window_to_world
    from /usr/lib/libgnomecanvas-2.so.0
  • #16 gnome_canvas_set_scroll_region
    from /usr/lib/libgnomecanvas-2.so.0
  • #17 g_source_is_destroyed
    from /lib/libglib-2.0.so.0
  • #18 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #19 g_main_context_check
    from /lib/libglib-2.0.so.0
  • #20 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #21 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #22 main
  • #0 __kernel_vsyscall

Comment 1 andrew.jones11235 2006-11-26 20:58:41 UTC
I don't know if the information above gives you any useful information, but here are a couple comments based on my first experience with Planner:

1:  I had entered several very similar tasks (my project was to relocate several servers in sequence so as to minimize the downtime for users).  One subtask that appeared in several tasks was "Shut down server", and this line depended on a previous activity and in turn another activity depended on this line.  I noticed that when defining dependencies I selected the correct line which corresponded to the server that I was working on but when I checked the Gantt chart the dependency was defined as depending on the *first* instance of "Shut down Server" which corresponded to a different server.  I know nothing about the Gnome API but I assume the listbox is returning the selected text and not the index of the selected text - which would have helped to avoid this issue.   If Planner cannot handle identical task / subtask names could it check for duplicates at the time they are entered?  Planner started becoming slightly less than stable when this issue occurred but I thought I had fixed it by renaming subtasks to "Shut down server <Servername>"

2:  Fortunately the planner files are written in XML so I repaired the file that was slightly corrupted when it crashed so it was legal XML but planner still crashes with it.  I created a new project and copied in most of the data from the old one.  I am not sure but I *think* it started failing when I entered resource usage.  It allowed me to enter usage and it is quite possible that at some times a resource is 500% utilized.  I was expecting to be able to enter all tasks and utilizations then juggle their timing until I could see 100% utilization or less throughout.  It was only after I had entered utilizations and tried to display the gantt chart that the newly created project started failing and inviting me to submit more bug reports.

As this is my first bug report I have no idea if anyone is going to read this or care.  If you need any more information please let me know.  I kept a few backups of the project in various stages of development until it started failing.

Rgds,

andy jones
Comment 2 andrew.jones11235 2006-11-27 17:34:21 UTC
<some time later>  I installed Planner for windows on my windows box and the file that crashes Planner for Linux works just fine.  I think the issue is with my Linux setup.  (Installed it a few days ago and Planner is the only application I have used seriously so far)

I have changed the bug status to NOTABUG

Rgds,

Andy Jones
Comment 3 André Klapper 2006-11-27 22:39:49 UTC
no, it isn't *your* setup, it's really planner's linux binary that differs - see bug 347555. :-)
Comment 4 André Klapper 2006-11-27 22:40:22 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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