Version-Release number of selected component: freerdp-1.0.2-6.fc20 Additional info: reporter: libreport-2.1.11 backtrace_rating: 4 cmdline: xfreerdp -g 1024x768 -k 0x00000409 -u d33tah -p ********* -D -X 106955195 -a 24 --plugin rdpsnd --plugin rdpdr --data disk media /media -- -x l --rfx --ignore-certificate --plugin cliprdr -t 3389 127.0.0.1 crash_function: pa_queue_push executable: /usr/bin/xfreerdp kernel: 3.9.6-200.fc18.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #5 pa_queue_push at pulsecore/queue.c:74 #6 pa_pstream_send_packet at pulsecore/pstream.c:349 #7 pa_pstream_send_tagstruct_with_creds at pulsecore/pstream-util.c:41 #8 pa_stream_update_timing_info at pulse/stream.c:1987 #9 request_auto_timing_update at pulse/stream.c:394 #10 pa_stream_trigger at pulse/stream.c:2392 #11 rdpsnd_process_message_close at /usr/src/debug/freerdp-1.0.2/channels/rdpsnd/rdpsnd_main.c:374 #12 rdpsnd_process_receive at /usr/src/debug/freerdp-1.0.2/channels/rdpsnd/rdpsnd_main.c:420 #13 svc_plugin_process_data_in at /usr/src/debug/freerdp-1.0.2/libfreerdp-utils/svc_plugin.c:249 #14 svc_plugin_thread_func at /usr/src/debug/freerdp-1.0.2/libfreerdp-utils/svc_plugin.c:278 Potential duplicate: bug 858936
Created attachment 851805 [details] File: backtrace
Created attachment 851806 [details] File: cgroup
Created attachment 851807 [details] File: core_backtrace
Created attachment 851808 [details] File: dso_list
Created attachment 851809 [details] File: environ
Created attachment 851810 [details] File: limits
Created attachment 851811 [details] File: maps
Created attachment 851812 [details] File: open_fds
Created attachment 851813 [details] File: proc_pid_status
Created attachment 851814 [details] File: var_log_messages
Another user experienced a similar problem: I am connected to a Windows XP through krdc. This crash and several ones similar to this one seem to happen when a window or dialog box is to be displayed. It doesn't happen for each window/dialog that's being opened though but rather frequently still. Examples. This has already happened when - I'm opening a Windows explorer Window - An installer pops up a small dialog window to ask for a language - A java app in internet explorer pops up a small dialog to ask for a username and password - ... reporter: libreport-2.2.1 backtrace_rating: 4 cmdline: xfreerdp -g 1280x1024 -k 0x00000813 -u janssege -p ********* -D -X 18874524 -a 16 --plugin rdpsnd --plugin rdpdr --data disk media /media -- -x l --rfx --ignore-certificate --plugin cliprdr -t 3389 192.168.93.53 crash_function: pa_queue_push executable: /usr/bin/xfreerdp kernel: 3.13.10-200.fc20.x86_64 package: freerdp-1.0.2-6.fc20 reason: xfreerdp killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: Running xfreerdp with -g 1200x1600 -k de -u $USER -d $DOMAIN -a 16 --plugin drdynvc --data audin -- --plugin rdpsnd --plugin cliprdr $IP Clicking on a link in the IE browser under windows, xfreerdp crashed. This happens OFTEN. It is just the first time I am reporting it. reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: xfreerdp -g 1200x1600 -k de -u pdbmwilc -d domfsc01 -a 16 --plugin drdynvc --data audin -- --plugin rdpsnd --plugin cliprdr 192.168.101.185 crash_function: pa_queue_push executable: /usr/bin/xfreerdp kernel: 3.15.10-200.fc20.x86_64 package: freerdp-1.0.2-6.fc20 reason: xfreerdp killed by SIGABRT runlevel: N 5 type: CCpp uid: 1004
Reassigning the component, as this is obviously related to pulseaudio.
Although the trace files are not exactly the same, it looks like bug 1054987, bug 985159 and bug 1059707 are all reporting the same issue (or at least closely related). They all report crash on a pulseaudio function: pa_queue_push (bug 1054987) pa_queue_free (bug 1059707) pa_queue_pop (bug 985159) Perhaps these should be treated together ? They are at least all highly annoying... Enough so for me to switch to rdesktop until this gets fixed.
Oh, perhaps I should add that I'm using freerdp from within krdc. In there I have set the Sound preference for this particular connection to "On This Computer". That's probably responsible for the "--plugin rdpsnd" part in the command line parameters. If I change this preference to "On Remote Computer" the "--plugin rdpsnd" parameter is not present on the command line and xfreerdp no longer crashes. The same if I set the preference to "Disable Sound" - no crashes. So both options can be used as a workaround.
(In reply to info from comment #15) > The same if I set the preference to "Disable Sound" - no crashes. > > So both options can be used as a workaround. ... but only if no sound is needed ...
This problem is still present. However I am not so certain any more that it's pulseaudio's fault. I have been using bidirectional pulseaudio sound through the virt-manager console on a Windows VM running lync telephone conferencing for hours with no single crash. If I connect to the same Windows system with freerdp, it takes a few minutes only before this error occurs. The two scenarios are pretty similar AFAICs. Thus I tend to believe that the crash has something to do with the way the pulseaudio library is used in freerdp. Nonetheless, it's frustrating to see that this problem has been open for more than a year without drawing any attention from either pulseaudio or freerdp engineers. For me at least, the problem totally forfeits using RDP with sound from a Linux client.
I've tried to reproduce the crashes, however unsuccessfully. Is it possible to reproduce the crash by e.g. playing some sound from "Sound" dialog in "Control panel"? I haven't seen any crashes for F21, can you prove it?
This used to happen to me when I participated in telephone conferences using Microsoft Lync over freerdp. I have just tried a lync test call and didn't see a crash (but sound quality was horrible).
We need to find some reliable reproducer (or have some more info) to be able fix this issue...
Does it crash also when alsa backend is used instead? "--plugin rdpsnd --data alsa --"
(In reply to Ondrej Holy from comment #21) > Does it crash also when alsa backend is used instead? > "--plugin rdpsnd --data alsa --" I haven't tried, but at least it won't crash with the same stack.
I haven't seen any crashes in F21 any more. I wanted to try the suggestion in comment 21, but it appears that xfreerdp in F21 has completely overhauled the command line options. Adding "--plugin rdpsnd --data alsa --" on a F21 command line just fails. Instead I have tried with "/sound:sys:alsa" which seems to be the closest match (and the only combination listed in the man page): $ xfreerdp /sound:sys:alsa /w:1800 /h:1100 /kbd:0x00000813 /u:janssege /bpp:16 /network:lan /rfx /port:3389 /v:192.168.93.53 "/p:krlBB26c:" +decorations loading channel rdpdr loading channel rdpsnd This seems to work without a hitch. Sound is played on my local F21 machine correctly.
As an experiment I also tried "/sound:sys:pulse". This seems to work as well. I don't know if this is a proper setting though - it was just a guess.
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.
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.
BTW, This is the fix: https://github.com/FreeRDP/FreeRDP/pull/2694