First step for any troubleshooting in the GUI… run it from the
command line and see what happens. Also you seem to know already you
are trying to use rdesktop so load that manually and see what happens
(not loading via tsclient).
Good luck.
dcasux wrote:
> Hey there, everyone…newbie here.
>
> I ran suse 11.0 great…I love it…I use only suse at home.
>
> I connect to a windows network via Terminal Services from Suse, and
> used rdesktop via the Terminal Services Client GUI all the time in 11.0.
>
> I downloaded the 11.1 DVD and upgraded my computer. Once I did so, my
> TS client would no longer start.
>
> I click on the icon…nothing happens.
>
> I’m too newb to troubleshoot the issue…(log files, etc)…soo…any
> newb help would be great as I used that tool all the time.
>
> Thank you!
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
What about ‘tsclient’ from the console? If you can run something
properly from the shell (not specifying any absolute or relative paths
or anything but just using the system $PATH environment variable) but
cannot run something when trying via ‘Alt+F2’ then I’m not sure what
else to check on the GUI side. You could create a script in ~/bin and
mark it executable with the same name (‘tsclient1’ for example) and have
that try to load ‘tsclient’ (the system executable) to see if there is
anything you can capture there… maybe use strace at that point if it
does not work.
Good luck.
dcasux wrote:
> ab@novell.com;1917915 Wrote:
> First step for any troubleshooting in the GUI… run it from the
> command line and see what happens. Also you seem to know already you
> are trying to use rdesktop so load that manually and see what happens
> (not loading via tsclient).
>
> Good luck.
>
>
>
>
>
> dcasux wrote:
>>>> Hey there, everyone…newbie here.
>>>>
>>>> I ran suse 11.0 great…I love it…I use only suse at home.
>>>>
>>>> I connect to a windows network via Terminal Services from Suse, and
>>>> used rdesktop via the Terminal Services Client GUI all the time in
> 11.0.
>>>> I downloaded the 11.1 DVD and upgraded my computer. Once I did so,
> my
>>>> TS client would no longer start.
>>>>
>>>> I click on the icon…nothing happens.
>>>>
>>>> I’m too newb to troubleshoot the issue…(log files, etc)…soo…any
>>>> newb help would be great as I used that tool all the time.
>>>>
>>>> Thank you!
>>>>
>>>>
> thanks a lot. And a quick reply. Much appreciated!
> Rdesktop works fine from the terminal…so it must be something with
> the GUI.
> FYI, I did uninstall and reinstall both rdesktop and the GUI.
> Any other ideas?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
Error:
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See GConf configuration system for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See GConf configuration system for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See GConf configuration system for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See GConf configuration system for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See GConf configuration system for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
tsclient clames that it cannot save the session info.
Otherwise very nice build (outside some minor flaws).