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 444434 - crash in Tasks: Closing Evolution. I us...
crash in Tasks: Closing Evolution. I us...
Status: RESOLVED DUPLICATE of bug 442194
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-06-05 18:09 UTC by Gwegowee
Modified: 2007-06-06 10:25 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description Gwegowee 2007-06-05 18:09:18 UTC 
What were you doing when the application crashed?
Closing Evolution.  I use Exchange connector (not my choice, believe me) to connect to our corporate calendar.  I have all of the folders (i.e. mail [exchange], address [local and global], calendar [exchange], tasks [local] and memo's [local]) all saving to disk for offline use.  Maybe not the local, but it's crashed and I'm filling out the crash report so I can't check right now :-D.  I had also migrated .evolution, .gconf/apps/evolution and .gnome2_private/Evolution from a previous FC6 install.


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:47:07 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Echo

Memory status: size: 740978688 vsize: 740978688 resident: 130588672 share: 24023040 rss: 130588672 rss_rlim: 18446744073709551615
CPU usage: start_time: 1181056059 rtime: 5205 utime: 4301 stime: 904 cutime:42 cstime: 57 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/evolution'

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496402016 (LWP 3686)]
[New Thread 1189128528 (LWP 3974)]
[New Thread 1074006352 (LWP 3749)]
(no debugging symbols found)
0x0000003ce9c0d89f in waitpid () from /lib64/libpthread.so.0

+ Trace 138514

Thread 1 (Thread 46912496402016 (LWP 3686))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 ??
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 strcmp
    from /lib64/libc.so.6
  • #4 e_shell_window_set_title
  • #5 ??
  • #6 GNOME_Evolution_ShellView_setTitle
    from /usr/lib64/evolution/2.10/libeshell.so.0
  • #7 e_component_view_set_title
    from /usr/lib64/evolution/2.10/libeshell.so.0
  • #8 ??
    from /usr/lib64/evolution/2.10/components/libevolution-mail.so
  • #9 ??
    from /lib64/libglib-2.0.so.0
  • #10 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #11 ??
    from /lib64/libglib-2.0.so.0
  • #12 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #13 bonobo_main
    from /usr/lib64/libbonobo-2.so.0
  • #14 main
  • #0 waitpid
    from /lib64/libpthread.so.0 


----------- .xsession-errors (165 sec old) ---------------------
inotify_add_watch: No such file or directory
(evolution:3686): libebook-WARNING **: invalid escape, passing it through
(evolution:3686): libebook-WARNING **: invalid escape, passing it through
(evolution:3686): libebook-WARNING **: invalid escape, passing it through
(evolution:3686): libebook-WARNING **: invalid escape, passing it through
(evolution:3686): libebook-WARNING **: invalid escape, passing it through
(evolution:3686): libebook-WARNING **: invalid escape, passing it through
(evolution:3686): libebook-WARNING **: invalid escape, passing it through
--------------------------------------------------
Comment 1 palfrey 2007-06-06 10:25:58 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 442194 ***