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 498539 - crash in Tasks: Download my mail
crash in Tasks: Download my mail
Status: RESOLVED DUPLICATE of bug 364700
Product: evolution
Classification: Applications
Component: Tasks
2.10.x (obsolete)
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-11-20 15:56 UTC by f1gma
Modified: 2007-11-21 22:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description f1gma 2007-11-20 15:56:15 UTC
Version: 2.10

What were you doing when the application crashed?
Download my mail


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.23.1-21.fc7 #1 SMP Thu Nov 1 21:09:24 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: 122261504 vsize: 122261504 resident: 38666240 share: 31047680 rss: 38666240 rss_rlim: 4294967295
CPU usage: start_time: 1195574130 rtime: 98 utime: 81 stime: 17 cutime:0 cstime: 1 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 -1208678688 (LWP 3743)]
[New Thread -1268778096 (LWP 3770)]
[New Thread -1233826928 (LWP 3769)]
[New Thread -1222816880 (LWP 3760)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1208678688 (LWP 3743))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 ??
  • #4 <signal handler called>
  • #5 g_main_context_check
    from /lib/libglib-2.0.so.0
  • #6 ??
    from /lib/libglib-2.0.so.0
  • #7 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #8 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #9 main
  • #0 __kernel_vsyscall


----------- .xsession-errors (8 sec old) ---------------------
alarm-notify.c:316 (cal_opened_cb) file:///home/fifou/.evolution/memos/local/system - Calendar Status 0
alarm-queue.c:551 (load_alarms) - Setting Call backs 
alarm-queue.c:1998 (alarm_queue_add_async) - 0x9d61d00
alarm-notify.c:316 (cal_opened_cb) contacts:/// - Calendar Status 0
alarm-queue.c:585 (load_alarms_for_today) - From Tue Nov 20 16:54:43 2007
 to Tue Nov 20 16:54:43 2007
alarm-queue.c:522 (load_alarms) 
alarm-queue.c:551 (load_alarms) - Setting Call backs 
alarm-queue.c:1998 (alarm_queue_add_async) - 0xb7101940
alarm-queue.c:585 (load_alarms_for_today) - From Tue No** Message: <info>  Vous êtes connecté au réseau sans fil « Livebox-a5f1 ».
CalDAV Eplugin starting up ...
** (evolution:3743): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:3743): DEBUG: mailto URL program: evolution
--------------------------------------------------
Comment 1 Akhil Laddha 2007-11-21 06:02:44 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.
Could you please install some debugging packages [1], start the application as
normal, 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 in advance!

[1] debugging packages for evolution, evolution-data-server, gtkhtml, gtk,
glib, gnome-vfs, libgnome and libgnomeui (as far as those packages are provided
by your distribution). More details can be found here:
http://live.gnome.org/GettingTraces
Comment 2 Tobias Mueller 2007-11-21 22:47:19 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 364700 ***