Red Hat Bugzilla – Bug 985982
gnome-rdp startup Glib-GObject-WARNING and kill process issues
Last modified: 2015-02-17 11:14:32 EST
Description of problem:
Starting gnome-rdp from command line generates terminal errors. Starting gnome-rdp from icon, not terminal, the same errors are reported in the system log.
Closing gnome-rdp by Xing the window does not terminate the process. xkilling the gnome-rdp window, if started from a terminal, will terminate the process but issues this error:
gnome-rdp: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
No error is seen in system logs if Xkilling when gnome-rdp is invoked from icon.
Version-Release number of selected component (if applicable):
[dudek@blackf19 ~]$ uname -r ; rpm -q gnome-rdp gnome-shell glib2 gtk2 gtk-sharp2 gnome-sharp gnome-desktop-sharp mono-core libappindicator-sharp libappindicator spice-glib spice-gtk3
Steps to Reproduce:
[dudek@blackf19 ~]$ gnome-rdp
(gnome-rdp:2055): GLib-GObject-WARNING **: gsignal.c:2475: signal `child-added' is invalid for instance `0x194f410' of type `GtkMenu'
(gnome-rdp:2055): GLib-GObject-WARNING **: gsignal.c:2475: signal `child-added' is invalid for instance `0x194f5b0' of type `GtkMenu'
The number 2055 as seen in the error message (gnome-rdp:2055) is the PID for gnome-rdp.exe. After Xing the gnome-rdp windows to close it as normal the process hangs onto the terminal. A ^C frees the terminal for more use but the gnome-rdp.exe process is still running.
[root@blackf19 ~]# ps -ef | grep rdp
dudek 2055 1915 3 10:27 pts/1 00:00:00 mono /usr/lib64/gnome-rdp/gnome-rdp.exe
Issues still exists with most current Fedora 19 packages:
[root@blackf19 ~]# uname -r ; rpm -q gnome-rdp gnome-shell glib2 gtk2 gtk-sharp2 gnome-sharp gnome-desktop-sharp mono-core libappindicator-sharp libappindicator spice-glib spice-gtk3
See the same issue with Fedora 20 and rawhide Fedora 21 packages.
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.
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
Thank you for reporting this bug and we are sorry it could not be fixed.