Description of problem: it just happened in the middle of using the remote connection with RDP protocol. Version-Release number of selected component: freerdp-1.0.2-2.fc19 Additional info: reporter: libreport-2.1.5 backtrace_rating: 4 cmdline: xfreerdp -g 1440x800 -k en-us -u d33tah -p ********* -D -X 96469442 -a 24 --plugin rdpsnd --plugin rdpdr --data disk media /media -- -x l --rfx --ignore-certificate 127.0.0.1:3389 crash_function: pa_queue_pop executable: /usr/bin/xfreerdp kernel: 3.9.6-200.fc18.x86_64 runlevel: N 5 uid: 1000 var_log_messages: Jul 17 02:13:26 localhost abrt[2257]: Saved core dump of pid 32235 (/usr/bin/xfreerdp) to /var/tmp/abrt/ccpp-2013-07-17-02:13:25-32235 (92143616 bytes) xsession_errors: Truncated backtrace: Thread no. 1 (10 frames) #5 pa_queue_pop at pulsecore/queue.c:106 #6 prepare_next_write_item at pulsecore/pstream.c:468 #7 do_write at pulsecore/pstream.c:566 #8 do_something at pulsecore/pstream.c:186 #9 dispatch_defer at pulse/mainloop.c:684 #10 pa_mainloop_dispatch at pulse/mainloop.c:899 #11 pa_mainloop_iterate at pulse/mainloop.c:939 #12 pa_mainloop_run at pulse/mainloop.c:954 #13 thread at pulse/thread-mainloop.c:88 #14 internal_thread_func at pulsecore/thread-posix.c:83 Potential duplicate: bug 858949
Created attachment 774565 [details] File: backtrace
Created attachment 774566 [details] File: cgroup
Created attachment 774567 [details] File: core_backtrace
Created attachment 774568 [details] File: dso_list
Created attachment 774569 [details] File: environ
Created attachment 774570 [details] File: limits
Created attachment 774571 [details] File: maps
Created attachment 774572 [details] File: open_fds
Created attachment 774573 [details] File: proc_pid_status
Been seeing this since I went to F19. It occurs about 6-10 times a day (I am a heavy user of RDP to a Windows 7 desktop). Annoying, but not a show stopper bug for me. I log back in to RDP session and pick up right where it crashed. It happens sometimes while I am typing, other times when I am away from my computer.
F19 here as well. I have been in situations where I can't log back in. That is, 1. freedesktop crashes 2. I log in again 3. but even before the windows screen is fully redrawn freedesktop crashes again I get most crashes while opening small dialog boxes.
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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 19 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.
It was still broken in Fedora 20. I couldn't get it to work at all in Fedora 21 (it just hung) so I have abandoned it completely in favour of Remmina.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.