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 447939 - crash in Tasks: configurer (evolution)
crash in Tasks: configurer (evolution)
Status: RESOLVED DUPLICATE of bug 467846
Product: evolution
Classification: Applications
Component: Tasks
2.10.x (obsolete)
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
aklapper[fc7]
Depends on:
Blocks:
 
 
Reported: 2007-06-15 16:40 UTC by celticb
Modified: 2007-09-04 22:22 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description celticb 2007-06-15 16:40:10 UTC
What were you doing when the application crashed?
configurer (evolution)


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:35:01 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: 105189376 vsize: 105189376 resident: 24059904 share: 17154048 rss: 24059904 rss_rlim: 4294967295
CPU usage: start_time: 1181925445 rtime: 76 utime: 70 stime: 6 cutime:1 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 -1208731936 (LWP 3078)]
[New Thread -1252770928 (LWP 3102)]
[New Thread -1220174960 (LWP 3097)]
(no debugging symbols found)
0x00ef2402 in __kernel_vsyscall ()

Thread 1 (Thread -1208731936 (LWP 3078))

  • #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 ---------------------
(evolution:3022): e-utils-WARNING **: Cannot resolve symbol 'org_gnome_new_mail_config' in plugin '/usr/lib/evolution/2.10/plugins/liborg-gnome-new-mail-notify.so' (not exported?)
BBDB spinning up...
(evolution:3022): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x9067000'
(evolution:3022): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x9067120'
CalDAV Eplugin starting up ...
** (evolution:3078): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:3078): DEBUG: mailto URL program: evolution
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:3078): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:3078): e-data-server-ui-WARNING **: Le fichier de clés n'a pas de groupe « Passwords-Mail »
--------------------------------------------------
Comment 1 palfrey 2007-06-29 16:37:21 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.
Can you get us a stack trace with debugging symbols? Please see
http://live.gnome.org/GettingTraces for more information on how to do so and
reopen this bug or report a new one. Thanks in advance!
Comment 2 Tobias Mueller 2007-09-04 22:22:28 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 467846 ***