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 463861 - crash in Tasks:
crash in Tasks:
Status: RESOLVED DUPLICATE of bug 455180
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
: 466014 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-08-06 04:26 UTC by benny-kc
Modified: 2007-10-02 10:48 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description benny-kc 2007-08-06 04:26:57 UTC
What were you doing when the application crashed?



Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 139919360 vsize: 139919360 resident: 39243776 share: 22085632 rss: 39243776 rss_rlim: 4294967295
CPU usage: start_time: 1186413495 rtime: 3757 utime: 3541 stime: 216 cutime:0 cstime: 0 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 -1208801568 (LWP 3280)]
[New Thread -1229005936 (LWP 3620)]
[New Thread -1302877296 (LWP 3619)]
[New Thread -1323857008 (LWP 3609)]
[New Thread -1249617008 (LWP 3381)]
[New Thread -1228457072 (LWP 3356)]
[New Thread -1270596720 (LWP 3344)]
(no debugging symbols found)
0x00497402 in __kernel_vsyscall ()

Thread 1 (Thread -1208801568 (LWP 3280))

  • #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 /lib/libglib-2.0.so.0
  • #6 ??
    from /lib/libglib-2.0.so.0
  • #7 ??
    from /lib/libglib-2.0.so.0
  • #8 g_slice_free1
    from /lib/libglib-2.0.so.0
  • #9 g_slist_free_1
    from /lib/libglib-2.0.so.0
  • #10 g_slist_remove
    from /lib/libglib-2.0.so.0
  • #11 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #12 ??
    from /lib/libglib-2.0.so.0
  • #13 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #14 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #15 main
  • #0 __kernel_vsyscall


----------- .xsession-errors (36 sec old) ---------------------
(evolution:3280): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x8bcf6c0'
(evolution:3280): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:3280): e-data-server-ui-WARNING **: Key file does not have group 'Passwords-Mail'
(evolution:3280): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:3280): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:3280): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:3280): e-data-server-ui-WARNING **: Key file does not have key 'smtp:__benny-kc;auth_LOGIN@165.108.159.14_'
(evolution:3280): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:3280): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:3280): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:3280): e-data-server-ui-WARNING **: Key file does not have key 'smtp:__benny-kc;auth_LOGIN@165.108.159.14_'
(evolution:3280): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
--------------------------------------------------
Comment 1 palfrey 2007-08-13 14:11:31 UTC
*** Bug 466014 has been marked as a duplicate of this bug. ***
Comment 2 Suman Manjunath 2007-10-02 10:48:20 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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