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 621964 - crash in Evolution: clicked send button (exc...
crash in Evolution: clicked send button (exc...
Status: RESOLVED DUPLICATE of bug 612178
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.30.x (obsolete)
Other All
: Normal critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2010-06-18 06:52 UTC by jochen.studivz
Modified: 2010-06-18 11:01 UTC
See Also:
GNOME target: ---
GNOME version: 2.29/2.30



Description jochen.studivz 2010-06-18 06:52:26 UTC
What were you doing when the application crashed?
clicked send button (exchange-account)


Distribution: Debian squeeze/sid
Gnome Release: 2.30.0 2010-04-26 (Debian)
BugBuddy Version: 2.30.0

System: Linux 2.6.32-trunk-686 #1 SMP Sun Jan 10 06:32:16 UTC 2010 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10707000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Aqua-Glade_PNG
GTK+ Modules: gnomebreakpad, canberra-gtk-module

Memory status: size: 284794880 vsize: 284794880 resident: 81031168 share: 25788416 rss: 81031168 rss_rlim: 18446744073709551615
CPU usage: start_time: 1276843588 rtime: 3237 utime: 2626 stime: 611 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xaa1feb70 (LWP 30407)]
[New Thread 0xaee55b70 (LWP 30394)]
[New Thread 0xab55bb70 (LWP 29955)]
[New Thread 0xabd5cb70 (LWP 29897)]
[New Thread 0xac55db70 (LWP 29896)]
[New Thread 0xac59eb70 (LWP 29888)]
[New Thread 0xaf6ecb70 (LWP 29882)]
[New Thread 0xad5beb70 (LWP 29880)]
[New Thread 0xaddbfb70 (LWP 29878)]
[New Thread 0xae5c0b70 (LWP 29876)]
[New Thread 0xb4ea5b70 (LWP 29862)]
[New Thread 0xb56a6b70 (LWP 29861)]
0xb78ab424 in __kernel_vsyscall ()

Thread 3 (Thread 0xaee55b70 (LWP 30394))

  • #0 __kernel_vsyscall
  • #1 __lll_lock_wait
    from /lib/i686/cmov/libpthread.so.0
  • #2 _L_lock_748
    from /lib/i686/cmov/libpthread.so.0
  • #3 pthread_mutex_lock
    from /lib/i686/cmov/libpthread.so.0
  • #4 ??
  • #5 <signal handler called>
  • #6 camel_exchange_utils_send_message
    from /usr/lib/evolution-data-server-1.2/camel-providers-14/libcamelexchange.so
  • #7 ??
    from /usr/lib/evolution-data-server-1.2/camel-providers-14/libcamelexchange.so
  • #8 camel_transport_send_to
    from /usr/lib/libcamel-provider-1.2.so.14
  • #9 ??
    from /usr/lib/evolution/2.30/libevolution-mail.so.0
  • #10 ??
    from /usr/lib/evolution/2.30/libevolution-mail.so.0
  • #11 ??
    from /lib/libglib-2.0.so.0
  • #12 ??
    from /lib/libglib-2.0.so.0
  • #13 start_thread
    from /lib/i686/cmov/libpthread.so.0
  • #14 clone
    from /lib/i686/cmov/libc.so.6
A debugging session is active.

	Inferior 1 [process 29859] will be detached.

Quit anyway? (y or n) [answered Y; input not from terminal]


---- Critical and fatal warnings logged during execution ----

** Gtk **: gtk_toggle_button_get_active: assertion `GTK_IS_TOGGLE_BUTTON (toggle_button)' failed 


----------- .xsession-errors (168151 sec old) ---------------------
syntax error at - line 617, near "}"
- has too many errors.
-----------------------------------------
-----------------------------------------
           OUTPUT
-----------------------------------------
syntax error at - line 564, near "()"
Global symbol "$lotAnalysis" requires explicit package name at - line 571.
syntax error at - line 581, near "}"
Global symbol "$lotAnalysis" requires explicit package name at - line 584.
Global symbol "$self" requires explicit package name at - line 584.
Global symbol "$lotAnalysis" requires explicit package name at - line 585.
Global symbol "$self" requires explicit pa
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Akhil Laddha 2010-06-18 11:01:06 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

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