Bug 1045130

Summary: [abrt] xrdp: __memcpy_sse2_unaligned(): xrdp-chansrv killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Samuel Greenfeld <samuel>
Component: xrdpAssignee: Itamar Reis Peixoto <itamar>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: bazanluis20, Denis.Ryndine, eddie, fischerjd, itamar, lavie, sergmerkelov, th.neuber
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/0ece10b14506106296224a5237b25546dccfc682
Whiteboard: abrt_hash:5ae4c837b1a7a8464a4b66b392893b20aca2ea22
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 13:38:17 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Samuel Greenfeld 2013-12-19 16:45:25 UTC 
Description of problem:
The origin of this is unknown, but may be related to RDP session reconnection.

I am unable to reconnect to RDP sessions that ended up on the GNOME lock screen because it constantly acts as if I pressed return while typing my password (only a few dots/keystrokes at most show before being told the password is incorrect).

Version-Release number of selected component:
xrdp-0.6.0-0.8.fc20

Additional info:
reporter:       libreport-2.1.10
backtrace_rating: 4
cmdline:        xrdp-chansrv
crash_function: __memcpy_sse2_unaligned
executable:     /usr/sbin/xrdp-chansrv
kernel:         3.11.10-301.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            0

Truncated backtrace:
Thread no. 1 (4 frames)
 #0 __memcpy_sse2_unaligned at ../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S:161
 #1 clipboard_event_selection_notify at clipboard.c:892
 #2 clipboard_check_wait_objs at clipboard.c:1128
 #3 channel_thread_loop at chansrv.c:488
Comment 1 Samuel Greenfeld 2013-12-19 16:45:29 UTC 
Created attachment 839069 [details]
File: backtrace
Comment 2 Samuel Greenfeld 2013-12-19 16:45:31 UTC 
Created attachment 839070 [details]
File: cgroup
Comment 3 Samuel Greenfeld 2013-12-19 16:45:32 UTC 
Created attachment 839071 [details]
File: core_backtrace
Comment 4 Samuel Greenfeld 2013-12-19 16:45:34 UTC 
Created attachment 839073 [details]
File: dso_list
Comment 5 Samuel Greenfeld 2013-12-19 16:45:35 UTC 
Created attachment 839074 [details]
File: environ
Comment 6 Samuel Greenfeld 2013-12-19 16:45:37 UTC 
Created attachment 839075 [details]
File: exploitable
Comment 7 Samuel Greenfeld 2013-12-19 16:45:38 UTC 
Created attachment 839076 [details]
File: limits
Comment 8 Samuel Greenfeld 2013-12-19 16:45:40 UTC 
Created attachment 839077 [details]
File: maps
Comment 9 Samuel Greenfeld 2013-12-19 16:45:41 UTC 
Created attachment 839078 [details]
File: open_fds
Comment 10 Samuel Greenfeld 2013-12-19 16:45:43 UTC 
Created attachment 839079 [details]
File: proc_pid_status
Comment 11 Samuel Greenfeld 2013-12-19 16:45:44 UTC 
Created attachment 839080 [details]
File: var_log_messages
Comment 12 Lavie 2014-11-18 21:59:06 UTC 
Is there any intent to fix this? This is a major bug for anyone who depends on remote access.
Comment 13 Fedora End Of Life 2015-05-29 10:03:40 UTC 
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 14 Lavie 2015-05-29 13:45:17 UTC 
I see that this has been fixed in Fedora 21.
Comment 15 Fedora End Of Life 2015-06-29 13:38:17 UTC 
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.
Comment 16 Denis.Ryndine 2015-07-01 06:41:54 UTC 
A work around is to disable the locking in Gnome settings. This has to be done for each user Gnome settings.
dconf->org->gnome->desktop->screensaver,  untick lock-enabled
                          ->remote-access  untick lock-screen-on-disconnect      

(Pity Fedora 20 EOL, moving to latest Fedora would be a project)