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 381394 - crash in Project Management: creating a new calendar
crash in Project Management: creating a new calendar
Status: RESOLVED DUPLICATE of bug 325759
Product: planner
Classification: Other
Component: General
0.14.x
Other All
: High critical
: ---
Assigned To: planner-maint
planner-maint
Depends on:
Blocks:
 
 
Reported: 2006-12-01 20:17 UTC by brunodal
Modified: 2006-12-05 23:31 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description brunodal 2006-12-01 20:17:40 UTC
Version: 0.14.2

What were you doing when the application crashed?
creating a new calendar


Distribution: Mandriva Linux release 2007.1 (Cooker) for i586
Gnome Release: 2.16.2 2006-11-22 (Mandriva)
BugBuddy Version: 2.16.0

Memory status: size: 0 vsize: 0 resident: 0 share: 0 rss: 0 rss_rlim: 0
CPU usage: start_time: 0 rtime: 0 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0

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

(no debugging symbols found)
Using host libthread_db library "/lib/i686/libthread_db.so.1".
Comment 1 brunodal 2006-12-02 09:28:47 UTC
instruction to repeat the crash.
planner: untitled document, gantt view (it language)
click on: gestione calendari, new
with: calendari esistenti: predefinito (selected)
    : nome del nuovo calendario: 3Turni
    : click option: deriva da un calendario
clik on: crea
Comment 2 André Klapper 2006-12-02 14:04:21 UTC
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Comment 3 brunodal 2006-12-03 09:33:22 UTC
[bruno@note ~]$ gdb /usr/bin/planner
GNU gdb 6.3-8mdv2007.0 (Mandriva Linux release 2007.0)
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i586-mandriva-linux-gnu"...(no debugging symbols found)
Using host libthread_db library "/lib/i686/libthread_db.so.1".

(gdb) run
Starting program: /usr/bin/planner
Reading symbols from shared object read from target memory...(no debugging symbols found)...done.
Loaded system supplied DSO at 0xbfffe000
[Thread debugging using libthread_db enabled]
[New Thread -1227289792 (LWP 5862)]
Bonobo accessibility support initialized
GTK Accessibility Module initialized

** ERROR **: file gailtreeview.c: line 2277 (idle_expand_row): assertion failed: (GTK_IS_TREE_VIEW (tree_view))
aborting...

Program received signal SIGABRT, Aborted.
[Switching to Thread -1227289792 (LWP 5862)]
0xbfffe410 in __kernel_vsyscall ()
(gdb) thread apply all bt

Thread 1 (Thread -1227289792 (LWP 5862))

  • #0 __kernel_vsyscall
  • #1 raise
    from /lib/i686/libc.so.6
  • #2 abort
    from /lib/i686/libc.so.6
  • #3 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #4 g_log
    from /usr/lib/libglib-2.0.so.0
  • #5 g_assert_warning
    from /usr/lib/libglib-2.0.so.0
  • #6 gail_tree_view_new
    from /usr/lib/gtk-2.0/modules/libgail.so
  • #7 g_source_is_destroyed
    from /usr/lib/libglib-2.0.so.0
  • #8 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #9 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #10 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #11 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #12 main

Comment 4 André Klapper 2006-12-05 23:31:47 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 325759 ***