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 569421 - another segfault
another segfault
Status: RESOLVED DUPLICATE of bug 567654
Product: evolution
Classification: Applications
Component: Mailer
2.24.x (obsolete)
Other All
: Normal critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2009-01-28 04:25 UTC by Brian J. Murrell
Modified: 2009-01-28 13:26 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24



Description Brian J. Murrell 2009-01-28 04:25:20 UTC
Steps to reproduce:
Again, not really doing anything special.

Stack trace:

Thread 1 (process 8391)

  • #0 __kernel_vsyscall
  • #1 raise
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 nsProfileLock::FatalSignalHandler
    at nsProfileLock.cpp line 212
  • #3 <signal handler called>
  • #4 vee_get_message
    at camel-vee-folder.c line 647
  • #5 camel_folder_get_message
    at camel-folder.c line 1126
  • #6 get_message_exec
    at mail-ops.c line 1824
  • #7 mail_msg_proxy
    at mail-mt.c line 520
  • #8 g_thread_pool_thread_proxy
    at /build/buildd/glib2.0-2.18.2/glib/gthreadpool.c line 265
  • #9 g_thread_create_proxy
    at /build/buildd/glib2.0-2.18.2/glib/gthread.c line 635
  • #10 start_thread
    from /lib/tls/i686/cmov/libpthread.so.0
  • #11 clone
    from /lib/tls/i686/cmov/libc.so.6


Other information:
Could we get some high priority action on this one?  This one has crashed on me no less than 12 times in the last 24h and no less than 10 times in the last 12h.  Very very annoying to have to restart Evolution every time you turn your head.
Comment 1 Akhil Laddha 2009-01-28 04:57:03 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


*** This bug has been marked as a duplicate of 567654 ***
Comment 2 Brian J. Murrell 2009-01-28 05:09:17 UTC
(In reply to comment #1)
> 
> This particular bug has already been reported into our bug tracking system, but
> we are happy to tell you that the problem has already been fixed.

Fixed?  How?  With what patch?  Please note item number 4 bug 562449 comment #18 and reply to it in the last paragraph in bug 562449 comment #20.

That reads to me like the patch is being "canceled" as it's not really working.  Can you please clarify?

> It should be
> solved in the next software version. You may want to check for a software
> upgrade.
> 
> 
> *** This bug has been marked as a duplicate of 567654 ***

Which is itself a duplicate of bug 562449.
Comment 3 Akhil Laddha 2009-01-28 05:40:57 UTC
(In reply to comment #2)
> (In reply to comment #1)
> > 
> > This particular bug has already been reported into our bug tracking system, but
> > we are happy to tell you that the problem has already been fixed.
> 
> Fixed?  How?  With what patch?  Please note item number 4 bug 562449 comment
> #18 and reply to it in the last paragraph in bug 562449 comment #20.
> 
> That reads to me like the patch is being "canceled" as it's not really working.
>  Can you please clarify?

Patch attached http://bugzilla.gnome.org/show_bug.cgi?id=567654#c11 is valid and will be committed for stable 2.24.4 release. 

I would say please reopen the bug if you see same crash after 2.24.4 also.

> 
> > It should be
> > solved in the next software version. You may want to check for a software
> > upgrade.
> > 
> > 
> > *** This bug has been marked as a duplicate of 567654 ***
> 
> Which is itself a duplicate of bug 562449.

It was marked duplicate so that all issues can be covered in a single bug.


Comment 4 Brian J. Murrell 2009-01-28 13:08:21 UTC
(In reply to comment #3)
> 
> Patch attached http://bugzilla.gnome.org/show_bug.cgi?id=567654#c11 is valid
> and will be committed for stable 2.24.4 release. 

Then why did  Srinivasa Ragavan tell hggdh not apply the patch after hggdh reported that it was not solving his SIGSEGV?
 
> I would say please reopen the bug if you see same crash after 2.24.4 also.

Which bug?  This one or bug 562449?  Certainly applying the patch in attachment 127073 [details] [review] is sufficient, yes?  I don't really have to wait for 2.24.4 do I?  I would like to confirm the patch before 2.24.4 is cut so that we can pre-empt yet another always-crashes release.
Comment 5 Akhil Laddha 2009-01-28 13:26:58 UTC
You can reopen the bug 569421 if patch attached in http://bugzilla.gnome.org/show_bug.cgi?id=567654#c11 doesn't fix the crash for you and if you have source build, you can try out the patch from bug 567654, that will be great.