evolution crashed with SIGSEGV in em_utils_composer_send_cb()

Bug #125985 reported by Gary Toth
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
evolution (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: evolution

Attempted to send email

ProblemType: Crash
Architecture: i386
Date: Sat Jul 14 09:46:40 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/evolution
NonfreeKernelModules: nvidia
Package: evolution 2.11.5-Oubuntu1
PackageArchitecture: i386
ProcCmdline: evolution
ProcCwd: /home/gary
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: evolution
StacktraceTop:
 em_utils_composer_send_cb ()
 g_cclosure_marshal_VOID__VOID ()
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
 ?? ()
Title: evolution crashed with SIGSEGV in em_utils_composer_send_cb()
Uname: Linux Guido 2.6.22-7-generic #1 SMP Mon Jun 25 17:33:14 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin netdev plugdev powerdev scanner video

Tags: apport-crash
Revision history for this message
Gary Toth (gjtoth) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:IA__g_cclosure_marshal_VOID__VOID (closure=0x8c7f028, return_value=0x0, n_param_values=1, param_values=0xbfe5c89c, invocation_hint=0xbfe5c77c,
IA__g_closure_invoke (closure=0x8c7f028, return_value=0x0, n_param_values=1, param_values=0xbfe5c89c, invocation_hint=0xbfe5c77c)
signal_emit_unlocked_R (node=0x85d4260, detail=0, instance=0x878fa28, emission_return=0x0, instance_and_params=0xbfe5c89c)
IA__g_signal_emit_valist (instance=0x878fa28, signal_id=425, detail=0, var_args=0xb77c2015 "\203�004[]�220\215t&")
IA__g_signal_emit (instance=0x878fa28, signal_id=425, detail=0) at /build/buildd/glib2.0-2.13.6/gobject/gsignal.c:2243

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Revision history for this message
C de-Avillez (hggdh2) wrote :

Thanks your for your bug report. Is this error repeatable?

If so, can you repeat it at will -- and how?

Changed in evolution:
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Gary Toth (gjtoth) wrote : Re: [Bug 125985] Re: evolution crashed with SIGSEGV in em_utils_composer_send_cb()

hggdh wrote:
> Thanks your for your bug report. Is this error repeatable?
>
> If so, can you repeat it at will -- and how?
>
> ** Changed in: evolution (Ubuntu)
> Importance: Undecided => Medium
> Status: New => Incomplete
>
>
Yes, I am able to replicate it at will. I simply attempt to send email
via SMTP and it crashes.

--
A grenade thrown into a kitchen in France would result in Linoleum blown apart.
<><~~~~~~~~~~~~~~~~~~~~~~
Gary J. Toth
Louisville, Kentucky, USA
Sunday, July 15, 2007 04:30 PM
Registered Linux User #402142

Joshua 24:15

Revision history for this message
C de-Avillez (hggdh2) wrote :

Is the account you are using enabled (Edit/Preferences; verify the account *is* cheked enabled; then Edit the account, and check on the SMTP settings)?

If all is correct, then...

1. has it ever worked?
2. Can you run Evo as follows:

   env CAMEL_DEBUG=all evolution > evo.log 2>&1

then try to send an email. It should crash. After the crash collect the 'evo.log file generated in (2) above, plus the ~/.xsession-errors file, and attach them, here.

Revision history for this message
Gary Toth (gjtoth) wrote :

hggdh wrote:
> Is the account you are using enabled (Edit/Preferences; verify the
> account *is* cheked enabled; then Edit the account, and check on the
> SMTP settings)?
>
> If all is correct, then...
>
> 1. has it ever worked?
> 2. Can you run Evo as follows:
>
> env CAMEL_DEBUG=all evolution > evo.log 2>&1
>
> then try to send an email. It should crash. After the crash collect the
> 'evo.log file generated in (2) above, plus the ~/.xsession-errors file,
> and attach them, here.
>
>
Here's what I've discovered thusfar:

I had two accounts. One of them to my webhost and the other is a GMail
account. If I attempt to send to my webhost account (SMTP), Evolution
crashes. HOWEVER, if I send through GMail's SMTP, it sends just fine.
So, apparently, the problem lies with the SMTP server and not
Evolution... I think.

--
Marathon runners with bad footwear suffer the agony of de feet.
<><~~~~~~~~~~~~~~~~~~~~~~
Gary J. Toth
Louisville, Kentucky, USA
Monday, July 16, 2007 02:50 PM
Registered Linux User #402142

Joshua 24:15

Revision history for this message
C de-Avillez (hggdh2) wrote :

Still, Evo should gracefully fail, not just scream bloody murder & flop.

But this is better: at least you are able to (partially) work.

Revision history for this message
Gary Toth (gjtoth) wrote :

hggdh wrote:
> Still, Evo should gracefully fail, not just scream bloody murder & flop.
>
> But this is better: at least you are able to (partially) work.
>
I agree. However, at least I know where to begin to sort things out.

Thanks!

--
I can see clearly now, the brain is gone...
<><~~~~~~~~~~~~~~~~~~~~~~
Gary J. Toth
Louisville, Kentucky, USA
Monday, July 16, 2007 03:45 PM
Registered Linux User #402142

Joshua 24:15

Revision history for this message
C de-Avillez (hggdh2) wrote :

Gary, do you want to pursue the issue?

Revision history for this message
Gary Toth (gjtoth) wrote :

hggdh wrote:
> Gary, do you want to pursue the issue?
>
No. I'm almost positive it's an issue with the webhost. I've also
tried it through an in-house smtp server and it works just fine. I'll
get in contact with my webhost and see what they can work up. They're
pretty darned good.

Thanks, though. I really like Evo and would be hard-pressed to do
without it.

--
Adults are just kids who owe money.
<><~~~~~~~~~~~~~~~~~~~~~~
Gary J. Toth
Louisville, Kentucky, USA
Monday, July 16, 2007 08:50 PM
Registered Linux User #402142

Joshua 24:15

Revision history for this message
C de-Avillez (hggdh2) wrote :

Closing invalid as requested per user.

Changed in evolution:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.