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 342920 - The Application "/usr/libexec/evolution-data-server-1.6" has quit unexpectedly.
The Application "/usr/libexec/evolution-data-server-1.6" has quit unexpectedly.
Status: RESOLVED DUPLICATE of bug 319076
Product: evolution-data-server
Classification: Platform
Component: Calendar
1.6.x (obsolete)
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2006-05-25 13:43 UTC by Klaas Groot
Modified: 2006-05-25 21:08 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description Klaas Groot 2006-05-25 13:43:08 UTC
Steps to reproduce:
1. Install gnome-pilot applet 2.0.12 applet
2. Start evolution (optional)
3. Connect Palm ans start synchronization
4. The pilot applet comes up and makes you nervous with much flickering
(anoying!)
5. Palm displays progress and displays "Synchinizeng DateBook"
6. After a while (minutes or around a hour) the crash window appears.



Stack trace:
Debugging Information:

Backtrace was generated from '/usr/libexec/evolution-data-server-1.6'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1489639744 (LWP 18334)]
[New Thread -1503368272 (LWP 18344)]
[New Thread -1494717520 (LWP 18335)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0xa74baaf1 in waitpid () from /lib/tls/libc.so.6

Thread 1 (Thread -1489639744 (LWP 18334))

  • #0 waitpid
    from /lib/tls/libc.so.6
  • #1 strtold_l
    from /lib/tls/libc.so.6
  • #2 system
    from /lib/tls/libc.so.6
  • #3 system
    from /lib/tls/libpthread.so.0
  • #4 ??
  • #5 ??
  • #6 _IO_stdin_used
  • #7 ??
  • #8 _dl_rtld_di_serinfo
    from /lib/ld-linux.so.2
  • #9 <signal handler called>
  • #10 pvl_head
    from /usr/lib/libecal-1.2.so.3
  • #11 icalcomponent_as_ical_string
    from /usr/lib/libecal-1.2.so.3
  • #12 icalcomponent_as_ical_string
    from /usr/lib/libecal-1.2.so.3
  • #13 e_cal_backend_file_todos_get_type
    from /usr/lib/evolution-data-server-1.2/extensions/libecalbackendfile.so
  • #14 g_child_watch_add
    from /usr/lib/libglib-2.0.so.0
  • #15 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #16 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #17 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #18 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #19 ??
  • #20 _IO_stdin_used
  • #21 ??
  • #22 _IO_stdin_used
  • #23 ??
  • #0 waitpid
    from /lib/tls/libc.so.6




Other information:
Description of the crash:
When synchronizing my Sony Clie (PEG-UX50/E) with Evolution i get the
error: "The Application "/usr/libexec/evolution-data-server-1.6" has
quit unexpectedly.". This happens during the synchronization of the
DateBook (Agenda). I have a very big datebook. 

Expected Results:
Synchronization from my Palm to Evolution (one way).

How often does this happen?
Every time a try to synchonize.

Additional Information:
JPilot does have no troubles synchronizing it, but after the data is in
JPilot there is not much I can do with it. Therfore I would like to
synchronize with Evolution. Jpilot synchronizes in a few minutes.
Evolution will probably take hours to finish. 

Using KDE 3.5, it takes more than a hour to crash, without finishing the
databook synchronization. On Gnome 2.14.1 it takes a few minutes to
crash. Both are running on Debian unstable. I use kernel 2.6.16.
Comment 1 Christian Kirbach 2006-05-25 21:08:10 UTC
Thanks for the bug report. 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?

Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.

please post it to the other report.

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