Bug 1202115 - [abrt] vinagre: g_type_check_instance_cast(): vinagre killed by SIGSEGV
Summary: [abrt] vinagre: g_type_check_instance_cast(): vinagre killed by SIGSEGV
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: vinagre
Version: 22
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Bastien Nocera
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:39d30578d81045991e75349940d...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-03-15 14:58 UTC by lea89
Modified: 2016-07-19 13:03 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-19 13:03:03 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (39.02 KB, text/plain)
2015-03-15 14:58 UTC, lea89
no flags Details
File: cgroup (190 bytes, text/plain)
2015-03-15 14:58 UTC, lea89
no flags Details
File: core_backtrace (8.44 KB, text/plain)
2015-03-15 14:58 UTC, lea89
no flags Details
File: dso_list (16.32 KB, text/plain)
2015-03-15 14:58 UTC, lea89
no flags Details
File: environ (1.66 KB, text/plain)
2015-03-15 14:58 UTC, lea89
no flags Details
File: limits (1.29 KB, text/plain)
2015-03-15 14:58 UTC, lea89
no flags Details
File: maps (78.55 KB, text/plain)
2015-03-15 14:58 UTC, lea89
no flags Details
File: open_fds (1.15 KB, text/plain)
2015-03-15 14:58 UTC, lea89
no flags Details
File: proc_pid_status (954 bytes, text/plain)
2015-03-15 14:58 UTC, lea89
no flags Details
File: var_log_messages (2.34 KB, text/plain)
2015-03-15 14:58 UTC, lea89
no flags Details

Description lea89 2015-03-15 14:58:01 UTC
Description of problem:
Hello, vinagre stopped working.
Problem description: 1) opened vinagre 2) filled out the parameters for a SSH connection 3) When clicked was closed unexpectedly.

Possible Solution:
I repeated the steps and the same thing happened.
Then activate SSH (service sshd start) on the machine that is going to make the connection and it worked.

Version-Release number of selected component:
vinagre-3.15.91-1.fc22

Additional info:
reporter:       libreport-2.4.0
backtrace_rating: 4
cmdline:        vinagre
crash_function: g_type_check_instance_cast
executable:     /usr/bin/vinagre
kernel:         4.0.0-0.rc2.git0.1.fc22.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (4 frames)
 #0 g_type_check_instance_cast at gtype.c:4060
 #1 emit_delayed_signal at plugins/ssh/vinagre-ssh-tab.c:56
 #5 g_main_context_iteration at gmain.c:3869
 #6 g_application_run at gapplication.c:2308

Comment 1 lea89 2015-03-15 14:58:05 UTC
Created attachment 1001977 [details]
File: backtrace

Comment 2 lea89 2015-03-15 14:58:06 UTC
Created attachment 1001978 [details]
File: cgroup

Comment 3 lea89 2015-03-15 14:58:08 UTC
Created attachment 1001979 [details]
File: core_backtrace

Comment 4 lea89 2015-03-15 14:58:09 UTC
Created attachment 1001980 [details]
File: dso_list

Comment 5 lea89 2015-03-15 14:58:11 UTC
Created attachment 1001981 [details]
File: environ

Comment 6 lea89 2015-03-15 14:58:12 UTC
Created attachment 1001982 [details]
File: limits

Comment 7 lea89 2015-03-15 14:58:15 UTC
Created attachment 1001983 [details]
File: maps

Comment 8 lea89 2015-03-15 14:58:16 UTC
Created attachment 1001984 [details]
File: open_fds

Comment 9 lea89 2015-03-15 14:58:17 UTC
Created attachment 1001985 [details]
File: proc_pid_status

Comment 10 lea89 2015-03-15 14:58:19 UTC
Created attachment 1001986 [details]
File: var_log_messages

Comment 11 Fedora End Of Life 2016-07-19 13:03:03 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.