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 507833 - crash in Tasks: Clicked on a message to ...
crash in Tasks: Clicked on a message to ...
Status: RESOLVED DUPLICATE of bug 239441
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-01-07 13:47 UTC by Brian Butterfield
Modified: 2008-02-05 08:38 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description Brian Butterfield 2008-01-07 13:47:25 UTC 
Version: 2.10

What were you doing when the application crashed?
Clicked on a message to read. 


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.22.1-41.fc7 #1 SMP Fri Jul 27 18:10:34 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 268406784 vsize: 268406784 resident: 158982144 share: 36143104 rss: 158982144 rss_rlim: 4294967295
CPU usage: start_time: 1199712164 rtime: 8750 utime: 7543 stime: 1207 cutime:3 cstime: 6 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 -1209174304 (LWP 28713)]
[New Thread -1358955632 (LWP 28828)]
[New Thread -1279956080 (LWP 28758)]
[New Thread -1258976368 (LWP 28756)]
[New Thread -1248093296 (LWP 28755)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 184383

Thread 1 (Thread -1209174304 (LWP 28713))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 ??
  • #4 <signal handler called>
  • #5 ??
    from /usr/lib/evolution/2.10/libetable.so.0
  • #6 ??
    from /usr/lib/evolution/2.10/libetable.so.0
  • #7 resort_model
    from /usr/lib/evolution/2.10/libetable.so.0
  • #8 ??
    from /lib/libglib-2.0.so.0
  • #9 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #10 ??
    from /lib/libglib-2.0.so.0
  • #11 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #12 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #13 main
  • #0 __kernel_vsyscall 


----------- .xsession-errors (1470112 sec old) ---------------------
(evolution:3091): GLib-GObject-WARNING **: invalid (NULL) pointer instance
(evolution:3091): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
(evolution:3091): GLib-GObject-WARNING **: invalid (NULL) pointer instance
(evolution:3091): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
(evolution:3091): GLib-GObject-WARNING **: invalid (NULL) pointer instance
(evolution:3091): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
(evolution:3091): GLib-GObject-WARNING **: invalid (NULL) pointer instance
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Akhil Laddha 2008-02-05 08:38:03 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but
we are happy to tell you that the problem has already been fixed. It should be
solved in the next software version. You may want to check for a software
upgrade.

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