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 429963 - crash in Tasks: Closing evo New version:...
crash in Tasks: Closing evo New version:...
Status: RESOLVED DUPLICATE of bug 334966
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-04-15 13:07 UTC by Nicolas Mailhot
Modified: 2007-04-15 19:51 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description Nicolas Mailhot 2007-04-15 13:07:24 UTC 
What were you doing when the application crashed?
Closing evo
New version: evolution-2.10.1-4.fc7


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

System: Linux 2.6.21-0.30.rc6.mm1.fc7 #1 SMP Mon Apr 9 05:47:40 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10299905
Selinux: No
Accessibility: Enabled
GTK+ Theme: Clearlooks
Icon Theme: Echo

Memory status: size: 654295040 vsize: 654295040 resident: 52293632 share: 20590592 rss: 52293632 rss_rlim: 18446744073709551615
CPU usage: start_time: 1176641728 rtime: 811 utime: 739 stime: 72 cutime:0 cstime: 4 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib64/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 47570076307312 (LWP 1101)]
[New Thread 1090791744 (LWP 1144)]
0x000000359aa0d83f in __libc_waitpid (pid=1243, stat_loc=0x7fffe645abac, 
    options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:41
41	  int result = INLINE_SYSCALL (wait4, 4, pid, stat_loc, options, NULL);

+ Trace 127950

Thread 1 (Thread 47570076307312 (LWP 1101))

  • #0 __libc_waitpid
    at ../sysdeps/unix/sysv/linux/waitpid.c line 41
  • #1 libgnomeui_segv_handle
    at gnome-ui-init.c line 872
  • #2 <signal handler called>
  • #3 strcmp
    from /lib64/libc.so.6
  • #4 e_shell_window_set_title
    at e-shell-window.c line 1248
  • #5 impl_ShellView_setTitle
    at e-shell-view.c line 48
  • #6 GNOME_Evolution_ShellView_setTitle
    at Evolution-stubs.c line 27
  • #7 e_component_view_set_title
    at e-component-view.c line 136
  • #8 view_changed_timeout
    at mail-component.c line 582
  • #9 g_timeout_dispatch
    at gmain.c line 3422
  • #10 IA__g_main_context_dispatch
    at gmain.c line 2045
  • #11 g_main_context_iterate
    at gmain.c line 2677
  • #12 IA__g_main_loop_run
    at gmain.c line 2881
  • #13 bonobo_main
    at bonobo-main.c line 311
  • #14 main
    at main.c line 586 


----------- .xsession-errors (28 sec old) ---------------------
Bonobo accessibility support initialized
CalDAV Eplugin starting up ...
(evolution:1101): evolution-mail-WARNING **: ignored this junk plugin: not enabled or we have already loaded one
(evolution:1101): e-utils-WARNING **: Plugin 'Greffon de pourriel Spamassassin' failed to load hook 'org.gnome.evolution.mail.junk:1.0'
libnm_glib_nm_state_cb: dbus returned an error.
  (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files
(evolution:1101): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
Avertissement du gestionnaire de fenêtres : Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x6c00003 (Visionneur)
Avertissement du gestionnaire de fenêtres : meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
GTK Accessibility Module initialized
Bonobo accessibility support initialized
GTK Accessibility Module initialized
Bonobo accessibility support initialized
--------------------------------------------------
Comment 1 palfrey 2007-04-15 19:51:27 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 334966 ***