Bug 1272135

Summary: [abrt] remmina: __strncpy_sse2_unaligned(): remmina killed by SIGSEGV
Product: [Fedora] Fedora Reporter: YAR <friets>
Component: remminaAssignee: Pavel Alexeev <pahan>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: negativo17, pahan
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/314edb7a26305e3d0be4c28f5d5a2b8cfa249b06
Whiteboard: abrt_hash:ed60454b8a9629e6c371580291fed40f83f6716c;VARIANT_ID=workstation;
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 18:13:56 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1361774    
Bug Blocks:    
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: mountinfo
none
File: namespaces
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description YAR 2015-10-15 14:38:49 UTC 
Description of problem:
I have no idea, I have Remmina running most of the day and I just started a new session.

Version-Release number of selected component:
remmina-1.2.0-0.5.git.b3237e8.fc22

Additional info:
reporter:       libreport-2.6.2
backtrace_rating: 4
cmdline:        remmina
crash_function: __strncpy_sse2_unaligned
executable:     /usr/bin/remmina
global_pid:     7741
kernel:         4.1.10-200.fc22.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (5 frames)
 #0 __strncpy_sse2_unaligned at ../sysdeps/x86_64/multiarch/strcpy-sse2-unaligned.S:296
 #1 strncpy at /usr/include/bits/string3.h:126
 #2 rdpdr_process_connect at /usr/src/debug/FreeRDP-24a752a70840f3e4b027ba7c020af71f2bcfd94a/channels/rdpdr/client/rdpdr_main.c:510
 #3 rdpdr_virtual_channel_client_thread at /usr/src/debug/FreeRDP-24a752a70840f3e4b027ba7c020af71f2bcfd94a/channels/rdpdr/client/rdpdr_main.c:931
 #4 thread_launcher at /usr/src/debug/FreeRDP-24a752a70840f3e4b027ba7c020af71f2bcfd94a/winpr/libwinpr/thread/thread.c:257
Comment 1 YAR 2015-10-15 14:38:54 UTC 
Created attachment 1083284 [details]
File: backtrace
Comment 2 YAR 2015-10-15 14:38:55 UTC 
Created attachment 1083285 [details]
File: cgroup
Comment 3 YAR 2015-10-15 14:38:56 UTC 
Created attachment 1083286 [details]
File: core_backtrace
Comment 4 YAR 2015-10-15 14:38:58 UTC 
Created attachment 1083287 [details]
File: dso_list
Comment 5 YAR 2015-10-15 14:38:59 UTC 
Created attachment 1083288 [details]
File: environ
Comment 6 YAR 2015-10-15 14:39:00 UTC 
Created attachment 1083289 [details]
File: limits
Comment 7 YAR 2015-10-15 14:39:02 UTC 
Created attachment 1083290 [details]
File: maps
Comment 8 YAR 2015-10-15 14:39:03 UTC 
Created attachment 1083291 [details]
File: mountinfo
Comment 9 YAR 2015-10-15 14:39:05 UTC 
Created attachment 1083292 [details]
File: namespaces
Comment 10 YAR 2015-10-15 14:39:06 UTC 
Created attachment 1083293 [details]
File: open_fds
Comment 11 YAR 2015-10-15 14:39:08 UTC 
Created attachment 1083294 [details]
File: proc_pid_status
Comment 12 YAR 2015-10-15 14:39:09 UTC 
Created attachment 1083295 [details]
File: var_log_messages
Comment 13 Fedora End Of Life 2016-07-19 18:13:56 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.