Bug 1498437 - gnome-rdp fails to start rdesktop
Summary: gnome-rdp fails to start rdesktop
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-rdp
Version: 26
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Luis Bazan
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1504711 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-10-04 10:29 UTC by Frank Crawford
Modified: 2018-05-29 12:44 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-05-29 12:44:45 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Frank Crawford 2017-10-04 10:29:30 UTC
Description of problem:
gnome-rdp fails to start up any remote desktop connections.

Version-Release number of selected component (if applicable):
gnome-rdp-0.3.1.0-15.fc26.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Start up gnome-rdp
2. Select a site
3. Nothing starts

Actual results:
No connections start

Expected results:
A connection starts

Additional info:
Output in log:
Information: Creating process for rdesktop  -p "<password>" -k en-us -g 1024x768 -f -a 16 -z -x l -5 -r sound:local agc
Error: No process is associated with this object.
Verbose: System.InvalidOperationException: No process is associated with this object.
  at System.Diagnostics.Process.EnsureState (System.Diagnostics.Process+State state) [0x0001e] in <f8255d9ef0594d18ae2c0d97286b9a80>:0 
  at System.Diagnostics.Process.EnsureState (System.Diagnostics.Process+State state) [0x00037] in <f8255d9ef0594d18ae2c0d97286b9a80>:0 
  at System.Diagnostics.Process.GetProcessHandle (System.Int32 access, System.Boolean throwIfExited) [0x00089] in <f8255d9ef0594d18ae2c0d97286b9a80>:0 
  at System.Diagnostics.Process.GetProcessHandle (System.Int32 access) [0x00000] in <f8255d9ef0594d18ae2c0d97286b9a80>:0 
  at System.Diagnostics.Process.WaitForInputIdle (System.Int32 milliseconds) [0x00002] in <f8255d9ef0594d18ae2c0d97286b9a80>:0 
  at System.Diagnostics.Process.WaitForInputIdle () [0x00000] in <f8255d9ef0594d18ae2c0d97286b9a80>:0 
  at (wrapper remoting-invoke-with-check) System.Diagnostics.Process:WaitForInputIdle ()
  at GnomeRDP.SessionHost.WorkerThread () [0x0005c] in <794978738ed449a4b4f09b95276c2dc4>:0

Comment 1 Brian Dudek 2017-10-17 18:19:39 UTC
Just upgraded from Fedora 19 and was working fine.  Now running Fedora 26 and have the exact issue Crawford describes.  Have installed all of the mono, gtk, and glib packages I could think of still with no luck.

Comment 2 Petr Pisar 2018-01-03 14:24:24 UTC
*** Bug 1504711 has been marked as a duplicate of this bug. ***

Comment 3 Fedora End Of Life 2018-05-03 08:28:35 UTC
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. 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 '26'.

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 26 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.

Comment 4 Fedora End Of Life 2018-05-29 12:44:45 UTC
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
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.


Note You need to log in before you can comment on or make changes to this bug.