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 304938 - Crash after posting to newsgroup
Crash after posting to newsgroup
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Mailer
2.4.x
Other other
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2005-05-21 00:37 UTC by Matt McMinn
Modified: 2013-09-13 00:54 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10


Attachments
should fix (1.24 KB, patch)
2005-08-08 09:38 UTC, Not Zed
committed Details | Review

Description Matt McMinn 2005-05-21 00:37:42 UTC
Distribution: Debian 3.1
Package: Evolution
Severity: normal
Version: GNOME2.10.1 2.3.x
Gnome-Distributor: Debian
Synopsis: Crash after posting to newsgroup
Bugzilla-Product: Evolution
Bugzilla-Component: Mailer
Bugzilla-Version: 2.3.x
BugBuddy-GnomeVersion: 2.0 (2.10.0)
Description:
Description of the crash:
Evolution 2.4 crashed after I posted to a newsgroup.  The post was left
in my outbox, and any attempt to send it resulted in a crash.

Steps to reproduce the crash:
1. Create a new message to a newsgroup.
2. Post.
3. Crash!

Expected Results:
No crash

How often does this happen?
Everytime

Additional Information:
I'm using the source from CVS, not 2.3.x.


Debugging Information:

Backtrace was generated from '/usr/local/bin/evolution-2.4'

Using host libthread_db library "/lib/tls/libthread_db.so.1".
`system-supplied DSO at 0xffffe000' has disappeared; keeping its
symbols.
[Thread debugging using libthread_db enabled]
[New Thread -1229201280 (LWP 24821)]
[New Thread -1374032976 (LWP 27588)]
[New Thread -1373635664 (LWP 27587)]
[New Thread -1372103760 (LWP 27586)]
[New Thread -1344275536 (LWP 27342)]
[New Thread -1244283984 (LWP 27341)]
[New Thread -1262486608 (LWP 25315)]
[New Thread -1306170448 (LWP 24839)]
[New Thread -1279394896 (LWP 24838)]
[New Thread -1296172112 (LWP 24836)]
[New Thread -1287783504 (LWP 24834)]
[New Thread -1271006288 (LWP 24831)]
[New Thread -1252787280 (LWP 24829)]
[New Thread -1235764304 (LWP 24827)]
0xb74cd561 in __waitpid_nocancel () from /lib/tls/libpthread.so.0

Thread 9 (Thread -1279394896 (LWP 24838))

  • #0 __lll_mutex_lock_wait
    from /lib/tls/libpthread.so.0
  • #1 _L_mutex_lock_26
    from /lib/tls/libpthread.so.0
  • #2 ??
  • #3 _dl_map_object_deps
    from /lib/ld-linux.so.2
  • #4 segv_redirect
    at main.c line 439
  • #5 segv_redirect
    at main.c line 439
  • #6 <signal handler called>
  • #7 mail_send_message
    at mail-ops.c line 569
  • #8 send_queue_send
    at mail-ops.c line 733
  • #9 mail_msg_received
    at mail-mt.c line 556
  • #10 thread_received_msg
    at e-msgport.c line 826
  • #11 thread_dispatch
    at e-msgport.c line 907
  • #12 start_thread
    from /lib/tls/libpthread.so.0
  • #13 clone
    from /lib/tls/libc.so.6




------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-05-21 00:37 UTC -------

Comment 1 Not Zed 2005-08-08 09:34:31 UTC
Looks like this code:  It assumes mail_send is called on a transport, but this
isn't the case for posting to news which just appends the message to the folder.
	
	camel_exception_clear (ex);

	if (!( ((CamelService *)xport)->provider->flags &
CAMEL_PROVIDER_DISABLE_SENT_FOLDER)) {	
		if (sent_folder_uri) {
			folder = mail_tool_uri_to_folder (sent_folder_uri, 0, ex);
			if (camel_exception_is_set(ex)) {
				g_string_append_printf (err, _("Failed to append to %s: %s\n"

Comment 2 Not Zed 2005-08-08 09:38:06 UTC
Created attachment 50379 [details] [review]
should fix

since you're using cvs, if you can test this patch it would be handy
Comment 3 Not Zed 2005-08-08 09:40:54 UTC
oh no need to confirm i guess, i thought i couldn't reproduce but i did and this
patch fixes it
Comment 4 Not Zed 2005-08-09 03:58:50 UTC
applied, 2.3 only bug