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 476022 - crash in Tasks: Trying to send a message...
crash in Tasks: Trying to send a message...
Status: RESOLVED DUPLICATE of bug 443410
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-09-11 21:41 UTC by xfinger
Modified: 2007-10-06 12:31 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description xfinger 2007-09-11 21:41:56 UTC
Version: 2.10

What were you doing when the application crashed?
Trying to send a message, but Evolution keeps saying bad login authentication from smtp server, theres is no way to cancel this message, it crashes whe a wrong password is typed. Keep in mind that if the password is not correct, the only way to stop evolution to try to send the message is KILL, or until it craches.
To reproduce this situation, just choose the wrong password or authentication login type, after sometime tring to cancel the messages that ask the correct password, type a wrong passwrd. Funny is that evolution displays the BAR tasks behind the one asking the correct password the another account is in duty of sending this message. Seems i used account XXXX to send (with wrong login authentication) e evolution is displayng a percent bar with the YYYY account sending the message.


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.4-65.fc7 #1 SMP Tue Aug 21 21:50:50 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 656498688 vsize: 656498688 resident: 65368064 share: 41930752 rss: 65368064 rss_rlim: 18446744073709551615
CPU usage: start_time: 1189545344 rtime: 664 utime: 625 stime: 39 cutime:1 cstime: 4 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 46912496455824 (LWP 8931)]
[New Thread 1168148816 (LWP 9210)]
[New Thread 1178638672 (LWP 9203)]
[New Thread 1084229968 (LWP 9022)]
[New Thread 1084496208 (LWP 8988)]
[New Thread 1105209680 (LWP 8958)]
(no debugging symbols found)
0x0000003f3f00d97f in waitpid () from /lib64/libpthread.so.0

Thread 1 (Thread 46912496455824 (LWP 8931))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 ??
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 ??
    from /lib64/libglib-2.0.so.0
  • #4 ??
    from /lib64/libglib-2.0.so.0
  • #5 ??
    from /lib64/libglib-2.0.so.0
  • #6 g_slice_free1
    from /lib64/libglib-2.0.so.0
  • #7 g_ptr_array_free
    from /lib64/libglib-2.0.so.0
  • #8 ??
    from /usr/lib64/librsvg-2.so.2
  • #9 ??
    from /usr/lib64/librsvg-2.so.2
  • #10 ??
    from /usr/lib64/librsvg-2.so.2
  • #11 ??
    from /usr/lib64/librsvg-2.so.2
  • #12 g_object_unref
    from /lib64/libgobject-2.0.so.0
  • #13 ??
    from /usr/lib64/gtk-2.0/2.10.0/loaders/svg_loader.so
  • #14 gdk_pixbuf_loader_close
    from /usr/lib64/libgdk_pixbuf-2.0.so.0
  • #15 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #16 gtk_icon_info_load_icon
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #17 gtk_icon_theme_load_icon
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #18 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #19 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #20 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #21 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #22 ??
    from /lib64/libgobject-2.0.so.0
  • #23 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #24 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #25 gtk_widget_realize
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #26 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #27 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #28 ??
    from /lib64/libgobject-2.0.so.0
  • #29 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #30 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #31 gtk_widget_show
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #32 gtk_dialog_run
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #33 ??
    from /usr/lib64/libedataserverui-1.2.so.8
  • #34 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #35 ??
    from /lib64/libglib-2.0.so.0
  • #36 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #37 bonobo_main
    from /usr/lib64/libbonobo-2.so.0
  • #38 main
  • #0 waitpid
    from /lib64/libpthread.so.0


----------- .xsession-errors (7411 sec old) ---------------------
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Susana 2007-10-06 12:31:14 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 443410 ***