abrt detected a crash. Attached file: backtrace cmdline: evolution component: evolution executable: /usr/bin/evolution kernel: 2.6.31.5-127.fc12.x86_64 package: evolution-2.28.0-2.fc12 rating: 3 reason: Process was terminated by signal 6
Created attachment 374414 [details] File: backtrace
Thanks for a bug report. There doesn't seem to be any Evolution code related to the abort itself, the other threads are idle there, thus I'm reassigning this to dbus.
*** Bug 542675 has been marked as a duplicate of this bug. ***
Same issue on Gentoo/XFCE desktop. This bug is perfectly reproducible with evolution-2.30.3 - each time I'm trying save attachment to removable device (usb stick) evolution aborts. Milan, are you sure this is not a bug in evolution as backtrace says different: _dbus_warn_check_failed ( format=0x3daba33740 "arguments to %s() were incorrect, assertion \"%s\" failed in file %s line %d.\nThis is normally a bug in some application using the D-Bus library.\n") at dbus-internals.c:283 args = {{gp_offset = 40, fp_offset = 48, May be I should report this issue into gnome bugzilla?
Do you mean that even the backtrace doesn't contain any direct calls from evolution, then, based on dbus error message, evolution can be the initiator, passing incorrect arguments, which are processed later, through the message queue? If so, then yes, it might be possible too. Note that upcoming Evolution 2.32 doesn't use dbus-glib, but it's using GDBus internally. You said "when saving to a removable decide", does it mean when saving to a hard-drive it behaves as expected? Is the backtrace same for the crashing thread as here? I wouldn't expect Evolution doing anything specially for removable devices, it sounds rather like something from the file chooser dialog (there are crashes involving file chooser dialog filled for evolution, though with a different warning message).
Err, after I've read your message I've decided to crash evolution another time as described but ... failed. Ok, since upcoming 2.32 uses dbus differently I'll hope that this bug will go away :) Thank you, Milan for help.
Thanks for re-testing. I'm closing this for now, but we can reopen if something similar would happen with 2.32.0+.