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 462360 - crash in Tasks: I
crash in Tasks: I
Status: RESOLVED DUPLICATE of bug 467846
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-08-01 04:05 UTC by volans2000
Modified: 2007-09-04 19:01 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description volans2000 2007-08-01 04:05:03 UTC
Version: 2.10

What were you doing when the application crashed?
I've tried to send a message that was in outbox, with mailbox settings that I know now, are wrong


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

System: Linux 2.6.22.1-33.fc7 #1 SMP Mon Jul 23 17:33:07 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Bluecurve

Memory status: size: 170561536 vsize: 170561536 resident: 55349248 share: 44208128 rss: 55349248 rss_rlim: 4294967295
CPU usage: start_time: 1185944650 rtime: 174 utime: 161 stime: 13 cutime:3 cstime: 7 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 -1208625440 (LWP 4739)]
[New Thread -1301439600 (LWP 4808)]
[New Thread -1311929456 (LWP 4805)]
[New Thread -1279652976 (LWP 4802)]
[New Thread -1244226672 (LWP 4801)]
[New Thread -1233327216 (LWP 4774)]
(no debugging symbols found)
0x0012d402 in __kernel_vsyscall ()

Thread 1 (Thread -1208625440 (LWP 4739))

  • #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 ---------------------
CalDAV Eplugin starting up ...
evolution-shell-Message: Killing old version of evolution-data-server...
** (evolution:4739): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:4739): 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:4739): 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:4739): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x9db8000'
(evolution:4739): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x9db8120'
(evolution:4739): e-data-server-ui-WARNING **: Key file does not have key 'smtp:__volans2000;auth_PLAIN@mail.clix.pt_'
--------------------------------------------------
Comment 1 palfrey 2007-08-01 12:24:23 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 19:01:43 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 ***