Version-Release number of selected component: remmina-1.0.0-7.fc18 Additional info: reporter: libreport-2.1.4 backtrace_rating: 4 cmdline: /usr/bin/remmina crash_function: gdi_memblt executable: /usr/bin/remmina kernel: 3.9.4-200.fc18.x86_64 runlevel: N 5 uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 gdi_memblt at /usr/src/debug/freerdp-1.0.1/libfreerdp-gdi/gdi.c:624 #1 update_recv_primary_order at /usr/src/debug/freerdp-1.0.1/libfreerdp-core/orders.c:1826 #2 update_recv_order at /usr/src/debug/freerdp-1.0.1/libfreerdp-core/orders.c:2018 #3 fastpath_recv_orders at /usr/src/debug/freerdp-1.0.1/libfreerdp-core/fastpath.c:132 #4 fastpath_recv_update at /usr/src/debug/freerdp-1.0.1/libfreerdp-core/fastpath.c:173 #5 fastpath_recv_update_data at /usr/src/debug/freerdp-1.0.1/libfreerdp-core/fastpath.c:294 #6 fastpath_recv_updates at /usr/src/debug/freerdp-1.0.1/libfreerdp-core/fastpath.c:310 #7 rdp_recv_fastpath_pdu at /usr/src/debug/freerdp-1.0.1/libfreerdp-core/rdp.c:762 #8 rdp_recv_pdu at /usr/src/debug/freerdp-1.0.1/libfreerdp-core/rdp.c:770 #9 rdp_recv_callback at /usr/src/debug/freerdp-1.0.1/libfreerdp-core/rdp.c:830 Potential duplicate: bug 836520
Created attachment 761283 [details] File: backtrace
Created attachment 761284 [details] File: cgroup
Created attachment 761285 [details] File: core_backtrace
Created attachment 761286 [details] File: dso_list
Created attachment 761287 [details] File: environ
Created attachment 761288 [details] File: limits
Created attachment 761289 [details] File: maps
Created attachment 761290 [details] File: open_fds
Created attachment 761291 [details] File: proc_pid_status
Created attachment 761292 [details] File: var_log_messages
Created attachment 761293 [details] File: xsession_errors
I am connecting to a local WMWare workstation which is sometimes unstable, the VMWare front-end dies. The instability is normally associated with me taking captures of parts of the full-screen with Lotus Notes client. The issue seems to affect my older Win XP image. reporter: libreport-2.1.6 backtrace_rating: 3 cmdline: remmina crash_function: gdi_memblt executable: /usr/bin/remmina kernel: 3.10.12-100.fc18.x86_64 package: remmina-1.0.0-7.fc18 reason: Process /usr/bin/remmina was killed by signal 11 (SIGSEGV) runlevel: N 5 uid: 1000
I was using the application against a local VMWare Work-station Windows Server. I have found that the VMWare Workstation Front-end would die, leaving the Server running in the back-ground. I have been using remmina to connect to the VMWare Image running minimised, which allows me to use the Windows images for much longer. I am using VMWorkstation v9.0.2 on Fedora 18. I have found that remmina dies whether the Windows client is XP or Windows 7. Windows 7 seems to be very stable, I also have hibernated the Fedora image, running on my laptop, several times - to no ill effect to Fedora. Remmina would just close after using it for a while. reporter: libreport-2.1.7 backtrace_rating: 3 cmdline: remmina crash_function: gdi_memblt executable: /usr/bin/remmina kernel: 3.11.4-101.fc18.x86_64 package: remmina-1.0.0-7.fc18 reason: Process /usr/bin/remmina was killed by signal 11 (SIGSEGV) runlevel: N 5 type: CCpp uid: 1000
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.