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 452635 - crash in Tasks:
crash in Tasks:
Status: RESOLVED DUPLICATE of bug 445309
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-06-30 19:51 UTC by evan
Modified: 2007-07-02 19:16 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description evan 2007-06-30 19:51:42 UTC
Version: 2.10

What were you doing when the application crashed?



Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 110686208 vsize: 110686208 resident: 39002112 share: 25051136 rss: 39002112 rss_rlim: 4294967295
CPU usage: start_time: 1183231598 rtime: 1095 utime: 1007 stime: 88 cutime:2 cstime: 7 timeout: 0 it_real_value: 0 frequency: 100

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

(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 -1208596768 (LWP 3488)]
[New Thread -1293378672 (LWP 3790)]
[New Thread -1304515696 (LWP 3564)]
(no debugging symbols found)
0x00633402 in __kernel_vsyscall ()

Thread 2 (Thread -1293378672 (LWP 3790))

  • #0 __kernel_vsyscall
  • #1 __lll_mutex_lock_wait
    from /lib/libpthread.so.0
  • #2 _L_mutex_lock_79
    from /lib/libpthread.so.0
  • #3 pthread_mutex_lock
    from /lib/libpthread.so.0
  • #4 ??
  • #5 <signal handler called>
  • #6 pthread_mutex_lock
    from /lib/libpthread.so.0
  • #7 PR_Lock
    from /usr/lib/libnspr4.so
  • #8 ??
    from /usr/lib/libnspr4.so
  • #9 __nptl_deallocate_tsd
    from /lib/libpthread.so.0
  • #10 start_thread
    from /lib/libpthread.so.0
  • #11 clone
    from /lib/libc.so.6


----------- .xsession-errors (272 sec old) ---------------------
(evolution:3488): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `GtkPaned'
(evolution:3488): Gtk-CRITICAL **: gtk_paned_get_position: assertion `GTK_IS_PANED (paned)' failed
(evolution:3488): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `GtkPaned'
(evolution:3488): Gtk-CRITICAL **: gtk_paned_set_position: assertion `GTK_IS_PANED (paned)' failed
(evolution:3488): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `GtkPaned'
(evolution:3488): Gtk-CRITICAL **: gtk_paned_get_position: assertion `GTK_IS_PANED (paned)' failed
(evolution:3488): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `GtkPaned'
(evolution:3488): Gtk-CRITICAL **: gtk_paned_set_position: assertion `GTK_IS_PANED (paned)' failed
--------------------------------------------------
Comment 1 Karsten Bräckelmann 2007-06-30 21:42:49 UTC
Thanks for the bug report. Unfortunately, that stack trace is not very useful
in determining the cause of the crash. Could you please install some debugging
packages [1] and reproduce the crash, if possible?

Once bug-buddy pops up, you can find the stacktrace in the "details", now
containing way more information. Please copy that stacktrace and paste it as a
comment here.  Thanks!


[1] debugging packages for evolution, evolution-data-server and gtkhtml,
    plus debugging packages for some basic GNOME libs. More details can
    be found here:
    http://live.gnome.org/GettingTraces  and
    http://live.gnome.org/GettingTraces/DistroSpecificInstructions
Comment 2 Karsten Bräckelmann 2007-07-02 19:16:35 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 445309 ***