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 488038 - crash in Tasks: deleted a piece of mail
crash in Tasks: deleted a piece of mail
Status: RESOLVED DUPLICATE of bug 479007
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-10-18 20:25 UTC by romeo.theriault
Modified: 2007-11-29 06:22 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description romeo.theriault 2007-10-18 20:25:41 UTC
Version: 2.10

What were you doing when the application crashed?
deleted a piece of mail


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.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 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: 193421312 vsize: 193421312 resident: 100134912 share: 41086976 rss: 100134912 rss_rlim: 4294967295
CPU usage: start_time: 1192734508 rtime: 3434 utime: 3346 stime: 88 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 -1208170784 (LWP 27422)]
[New Thread -1234277488 (LWP 27546)]
[New Thread -1292911728 (LWP 27543)]
[New Thread -1235174512 (LWP 27426)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1208170784 (LWP 27422))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 ??
  • #4 <signal handler called>
  • #5 pthread_mutex_lock
    from /lib/libpthread.so.0
  • #6 camel_message_info_free
    from /usr/lib/libcamel-provider-1.2.so.10
  • #7 ??
    from /usr/lib/libcamel-provider-1.2.so.10
  • #8 camel_folder_free_message_info
    from /usr/lib/libcamel-provider-1.2.so.10
  • #9 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #10 g_hash_table_foreach
    from /lib/libglib-2.0.so.0
  • #11 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #12 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #13 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #14 ??
    from /lib/libglib-2.0.so.0
  • #15 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #16 ??
    from /lib/libglib-2.0.so.0
  • #17 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #18 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #19 main
  • #0 __kernel_vsyscall


----------- .xsession-errors (199068 sec old) ---------------------
visible window : rx = 131, ry = 277, rw = 1063, rh=633
visible window in button coords: rx = 116, ry = 10, rw = 31, rh=18
visible window : rx = -3508, ry = 305, rw = 916, rh=582
visible window in button coords: rx = 9, ry = 10, rw = 26, rh=17
viewportNumH x V = 4 x 1, viewportCurX x Y = 3 x 0
visible window : rx = -2560, ry = 0, rw = 1280, rh=993
visible window in button coords: rx = 37, ry = 2, rw = 37, rh=29
visible window : rx = -1235, ry = 99, rw = 1155, rh=877
visible window in button coords: rx = 76, ry = 4, rw = 33, rh=25
visible window : rx = -3745, ry = 66, rw = 1063, rh=633
visible window in button coords: rx = 2, ry = 3, rw = 31, rh=18
visible window : rx = 131, ry = 277, rw = 1063, rh=633
visible window in button coords: rx = 116, ry = 10, rw = 31, rh=18
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Akhil Laddha 2007-11-29 06:22:04 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 479007 ***