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 506509 - segmentation fault handling broken
segmentation fault handling broken
Status: RESOLVED DUPLICATE of bug 580419
Product: evolution-data-server
Classification: Platform
Component: general
2.26.x (obsolete)
Other All
: Normal normal
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-12-31 00:44 UTC by Christian Krause
Modified: 2009-08-24 19:45 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26



Description Christian Krause 2007-12-31 00:44:04 UTC
Please describe the problem:
I've started evolution-data-server-1.12 from the command line to track a different problem. Finally it crashed and the following was printed:
---------------------------
sh: /usr/libexec/gnome_segv2: No such file or directory
---------------------------
No bug buddy was called and no other kind of segfault handling happened.


Steps to reproduce:
1. start e-d-s from command line
2. do something that it crashes ;-)

Actual results:
error message is printed out:
---------------------------
sh: /usr/libexec/gnome_segv2: No such file or directory
---------------------------

Expected results:
bug-buddy should be started

Does this happen every time?
whenever e-d-s crashes

Other information:
I've searched a little bit in the source and it looks like, that in e-d-s/src/server.c "GNOMEUI_SERVERDIR "/gnome_segv2";" is started.

According to
http://svn.gnome.org/viewvc/libgnomeui/trunk/libgnomeui/?view=query&dir=&file=.*segv.*&file_match=regex&who=&who_match=exact&comment=&comment_match=exact&querysort=date&hours=2&date=all&mindate=&maxdate=&limit_changes=100
(first entry) the tool gnome_segv2 is deprecated and was removed.

I'm not 100% sure about the correct replacement, but the gnome_segv2 calls should be removed and e-d-s should be adapted to the replacement (if there is any ;-)  ).
Comment 1 Christian Krause 2008-06-15 08:37:17 UTC
it looks like that the problem is still in the e-d-s which is distributed with Fedora 9. I'll update the version...

Comment 2 Akhil Laddha 2009-08-21 12:17:11 UTC
This version is no longer maintained, which means that it will not receive any
further security or bug fix updates.
The current stable GNOME and Evolution version is 2.26.

Can you please check again whether this issue still happens in Evolution 2.24
or 2.26 and update this report by adding a comment and changing the "Version"
field? Thanks a lot.

Again thank you for reporting this bug and we are sorry it could not be fixed
for the version you originally used here.

Without feedback this report will be closed as INCOMPLETE in 6 weeks.
Comment 3 Christian Krause 2009-08-21 13:46:39 UTC
(In reply to comment #2)
> This version is no longer maintained, which means that it will not receive any
> further security or bug fix updates.
> The current stable GNOME and Evolution version is 2.26.
> 
> Can you please check again whether this issue still happens in Evolution 2.24
> or 2.26 and update this report by adding a comment and changing the "Version"
> field? Thanks a lot.

Yes, the bug is still present:
grep segv2 evolution-data-server-2.26.3/src/server.c 
        gnome_segv_path = GNOMEUI_SERVERDIR "/gnome_segv2";
Comment 4 Christian Krause 2009-08-21 13:48:41 UTC
Please can somebody change the Status back to OPEN? I can only change it to RESOLVED or NEEDINFO, however the info was provided. ;-)
Comment 5 Akhil Laddha 2009-08-24 03:59:01 UTC
which distro do you have ?
Comment 6 Christian Krause 2009-08-24 19:29:58 UTC
I'm using Fedora. As far as I can see in the source code, the problem is in e-d-s shipped with Fedora 10 (2.24.5) as well as in Fedora 11 (2.26.3).

I'm quite sure that the problem is completly independend of the distribution: e-d-s uses a utility which was deprecated in gnome a long time ago:

http://mail.gnome.org/archives/release-team/2007-August/msg00092.html
Comment 7 Matthew Barnes 2009-08-24 19:45:03 UTC
It's been taken care of in 2.27.  Closing as a dupe.

*** This bug has been marked as a duplicate of bug 580419 ***