Description of problem: I tried to open a document on the remote machine in Microsoft Word. I forgot to turn on Samba and restart iptables witha custom firewall I am using. Once I turned on Samba and restarted iptables I went back to the RDP session and pressed escape to cancel the file from opening. Remina instally crashed. Version-Release number of selected component: remmina-1.0.0-5.fc18 Additional info: backtrace_rating: 4 cmdline: remmina crash_function: gdi_get_bitmap_pointer executable: /usr/bin/remmina kernel: 3.8.6-203.fc18.i686 uid: 1000 ureports_counter: 1 Truncated backtrace: Thread no. 1 (10 frames) #0 gdi_get_bitmap_pointer at /usr/src/debug/freerdp-1.0.1/libfreerdp-gdi/gdi.c:321 #1 BitBlt_BLACKNESS_32bpp at /usr/src/debug/freerdp-1.0.1/libfreerdp-gdi/32bpp.c:98 #3 BitBlt_32bpp at /usr/src/debug/freerdp-1.0.1/libfreerdp-gdi/32bpp.c:705 #4 gdi_BitBlt at /usr/src/debug/freerdp-1.0.1/libfreerdp-gdi/bitmap.c:186 #5 gdi_dstblt at /usr/src/debug/freerdp-1.0.1/libfreerdp-gdi/gdi.c:459 #6 update_recv_primary_order at /usr/src/debug/freerdp-1.0.1/libfreerdp-core/orders.c:1826 #7 update_recv_order at /usr/src/debug/freerdp-1.0.1/libfreerdp-core/orders.c:2018 #8 fastpath_recv_orders at /usr/src/debug/freerdp-1.0.1/libfreerdp-core/fastpath.c:132 #9 fastpath_recv_update at /usr/src/debug/freerdp-1.0.1/libfreerdp-core/fastpath.c:173 #10 fastpath_recv_update_data at /usr/src/debug/freerdp-1.0.1/libfreerdp-core/fastpath.c:294
Created attachment 735974 [details] File: backtrace
Created attachment 735975 [details] File: cgroup
Created attachment 735976 [details] File: core_backtrace
Created attachment 735977 [details] File: dso_list
Created attachment 735978 [details] File: environ
Created attachment 735979 [details] File: limits
Created attachment 735980 [details] File: maps
Created attachment 735981 [details] File: open_fds
Created attachment 735982 [details] File: proc_pid_status
Created attachment 735983 [details] File: var_log_messages
Created attachment 735984 [details] File: xsession_errors
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 'version' of '18'. 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 prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 to Fedora 18's end of life. 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 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.