Bug 1141575 - [abrt] unison240-gtk: camlMain__catch_all_1055(): unison-gtk-2.40 killed by SIGSEGV
Summary: [abrt] unison240-gtk: camlMain__catch_all_1055(): unison-gtk-2.40 killed by S...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: unison240
Version: 22
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Richard W.M. Jones
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:3a121b6f4dd9e3a3c985861ee1c...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-14 21:51 UTC by bartmon
Modified: 2016-07-19 12:07 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-07-19 12:07:59 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (14.76 KB, text/plain)
2014-09-14 21:51 UTC, bartmon
no flags Details
File: cgroup (190 bytes, text/plain)
2014-09-14 21:51 UTC, bartmon
no flags Details
File: core_backtrace (2.17 KB, text/plain)
2014-09-14 21:51 UTC, bartmon
no flags Details
File: dso_list (5.87 KB, text/plain)
2014-09-14 21:51 UTC, bartmon
no flags Details
File: environ (504 bytes, text/plain)
2014-09-14 21:51 UTC, bartmon
no flags Details
File: exploitable (82 bytes, text/plain)
2014-09-14 21:51 UTC, bartmon
no flags Details
File: limits (1.29 KB, text/plain)
2014-09-14 21:51 UTC, bartmon
no flags Details
File: maps (28.43 KB, text/plain)
2014-09-14 21:51 UTC, bartmon
no flags Details
File: open_fds (138 bytes, text/plain)
2014-09-14 21:51 UTC, bartmon
no flags Details
File: proc_pid_status (946 bytes, text/plain)
2014-09-14 21:51 UTC, bartmon
no flags Details
File: var_log_messages (339 bytes, text/plain)
2014-09-14 21:51 UTC, bartmon
no flags Details

Description bartmon 2014-09-14 21:51:24 UTC
Description of problem:
I use rawhide on the host where this bug occurs (rahwide x86_64 with version 2.40.102 release 8.fc20).
1. Initiate a unison sync from remote peer (F20 x86_64 with version 2.40.102 release 5.fc20)
2. Login at remote peer
I get this error immediately in remote GUI:
     Fatal error
     Lost connection with the server
On the remote peer I get this shell output with "-debug all":
   ...
   [remote] Shell connection: ssh (ssh, -l, username, -p, 22, host.example.com, -e, none, -C, unison, -server)
   ������Lost connection with the server

As a side note, unison also segfaults when initiating rawhide->F20.

Version-Release number of selected component:
unison240-gtk-2.40.102-8.fc22

Additional info:
reporter:       libreport-2.2.3
backtrace_rating: 4
cmdline:        unison -server
crash_function: camlMain__catch_all_1055
executable:     /usr/bin/unison-gtk-2.40
kernel:         3.16.0-1.fc22.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (8 frames)
 #0 camlMain__catch_all_1055
 #1 camlMain__init_1027
 #2 camlMain__Body_1088
 #3 camlLinkgtk2__entry
 #4 caml_program
 #5 caml_start_program
 #6 __libc_csu_init
 #8 _start

Comment 1 bartmon 2014-09-14 21:51:27 UTC
Created attachment 937376 [details]
File: backtrace

Comment 2 bartmon 2014-09-14 21:51:28 UTC
Created attachment 937377 [details]
File: cgroup

Comment 3 bartmon 2014-09-14 21:51:29 UTC
Created attachment 937378 [details]
File: core_backtrace

Comment 4 bartmon 2014-09-14 21:51:30 UTC
Created attachment 937379 [details]
File: dso_list

Comment 5 bartmon 2014-09-14 21:51:31 UTC
Created attachment 937380 [details]
File: environ

Comment 6 bartmon 2014-09-14 21:51:32 UTC
Created attachment 937381 [details]
File: exploitable

Comment 7 bartmon 2014-09-14 21:51:33 UTC
Created attachment 937382 [details]
File: limits

Comment 8 bartmon 2014-09-14 21:51:35 UTC
Created attachment 937383 [details]
File: maps

Comment 9 bartmon 2014-09-14 21:51:36 UTC
Created attachment 937384 [details]
File: open_fds

Comment 10 bartmon 2014-09-14 21:51:37 UTC
Created attachment 937385 [details]
File: proc_pid_status

Comment 11 bartmon 2014-09-14 21:51:38 UTC
Created attachment 937386 [details]
File: var_log_messages

Comment 12 Richard W.M. Jones 2014-09-15 07:33:53 UTC
While we appreciate the detailed bug report, you are probably better
off asking about this on one of the upstream mailing lists.  Point
them to the stack trace and other details contained in this bug.

http://www.cis.upenn.edu/~bcpierce/unison/lists.html

Comment 13 bartmon 2014-10-08 01:18:20 UTC
Started a conversation on unison-users, see here:
https://groups.yahoo.com/neo/groups/unison-users/conversations/messages/11343

Comment 14 bartmon 2014-10-08 01:53:50 UTC
Yahoo's web interface for lists has pretty bad CC handling so not all messages are visible.

To recap: I've managed to sync between rawhide and F20 by copying over the binary from F20 to rawhide and executing it. Something has happened to the build process between releases 5.fc20 and 8.fc22. This is evidenced by file size reduction:
# release 8.fc22
-rwxr-xr-x. 1 root root 4461992 avg 19 02:31 /usr/bin/unison-gtk-2.40*
# release 5.fc20
-rwxr-xr-x. 1 jasa jasa 5251568 okt  8 03:26 unison-gtk-2.40*

Comment 15 Jaroslav Reznik 2015-03-03 16:17:35 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22

Comment 16 Matteo Settenvini 2015-03-26 09:56:42 UTC
This bug is still relevant in Fedora 22 Alpha. It renders Unison unusable for me; and it is my most important synchronization method across different machines. Could someone fix the severity of the bug to reflect that?

Comment 17 Richard W.M. Jones 2015-03-26 11:01:23 UTC
Please see comment 12.  Unless this is a bug caused by Fedora
packaging, it's being reported in entirely the wrong place.

Comment 18 Fedora End Of Life 2016-07-19 12:07:59 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.