[opensuse-kde] KRDC 4.11 on oS 12.3 br0ken?
Hi everyone, in our mixed (Windows/Linux/Solaris) office environment, I often have to use KRDC to connect to a Windows terminal server. After upgrading to 4.11, the screen stays blue, no login is possible. And yes, I restarted KDE after upgrading to 4.11 :-) After "zypper in --oldpackage krdc-4.10.5-1.92.3" everything is fine, so the bug (if it is one) is in KRDC, not somewhere inside KDE. Can someone confirm this? Regards, Werner -- -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Am Donnerstag, 15. August 2013, 12:43:24 schrieb Werner Flamme:
in our mixed (Windows/Linux/Solaris) office environment, I often have to use KRDC to connect to a Windows terminal server. After upgrading to 4.11, the screen stays blue, no login is possible.
And yes, I restarted KDE after upgrading to 4.11 :-)
After "zypper in --oldpackage krdc-4.10.5-1.92.3" everything is fine, so the bug (if it is one) is in KRDC, not somewhere inside KDE.
Can someone confirm this?
Hi Werner, I have not upgraded to 4.11 yet but the symptom you describe is similar to what I experience when trying to connect via krdc to a VMWare Guest running Opensuse 13.1 Milestone 3 IIRC - not sure if this had already KDE 4.11 Development in it. So far i did not had much time to troubleshoot the issue . Blue screen and no connection . My KRDC runs on a Opensuse 12.3 with KDE 4.10.5 kind regards Stefan -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Am Donnerstag, 15. August 2013, 13:24:21 schrieb Stefan Kunze:
Am Donnerstag, 15. August 2013, 12:43:24 schrieb Werner Flamme:
in our mixed (Windows/Linux/Solaris) office environment, I often have to use KRDC to connect to a Windows terminal server. After upgrading to 4.11, the screen stays blue, no login is possible.
And yes, I restarted KDE after upgrading to 4.11 :-)
After "zypper in --oldpackage krdc-4.10.5-1.92.3" everything is fine, so the bug (if it is one) is in KRDC, not somewhere inside KDE.
Can someone confirm this?
Hi Werner,
I have not upgraded to 4.11 yet but the symptom you describe is similar to what I experience when trying to connect via krdc to a VMWare Guest running Opensuse 13.1 Milestone 3 IIRC - not sure if this had already KDE 4.11 Development in it. So far i did not had much time to troubleshoot the issue . Blue screen and no connection . My KRDC runs on a Opensuse 12.3 with KDE 4.10.5
Sounds like https://bugzilla.novell.com/show_bug.cgi?id=834991 which also has a solution/workaround. (In short krdc form 4.11 needs freerdp but this is missing as a dependency.) Christian -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Christian Trippe [15.08.2013 15:58]:
Am Donnerstag, 15. August 2013, 13:24:21 schrieb Stefan Kunze:
Am Donnerstag, 15. August 2013, 12:43:24 schrieb Werner Flamme:
in our mixed (Windows/Linux/Solaris) office environment, I often have to use KRDC to connect to a Windows terminal server. After upgrading to 4.11, the screen stays blue, no login is possible.
And yes, I restarted KDE after upgrading to 4.11 :-)
After "zypper in --oldpackage krdc-4.10.5-1.92.3" everything is fine, so the bug (if it is one) is in KRDC, not somewhere inside KDE.
Can someone confirm this?
Hi Werner,
I have not upgraded to 4.11 yet but the symptom you describe is similar to what I experience when trying to connect via krdc to a VMWare Guest running Opensuse 13.1 Milestone 3 IIRC - not sure if this had already KDE 4.11 Development in it. So far i did not had much time to troubleshoot the issue . Blue screen and no connection . My KRDC runs on a Opensuse 12.3 with KDE 4.10.5
Sounds like https://bugzilla.novell.com/show_bug.cgi?id=834991 which also has a solution/workaround. (In short krdc form 4.11 needs freerdp but this is missing as a dependency.)
Thank you, Christian. I tried "zypper in freerdp", but I receive a "No update candidate for 'freerdp-1.0.2-11.4.1.x86_64'. The highest available version is already installed." Regards, Werner -- -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Thursday 15 August 2013 15:58:34 Christian Trippe wrote:
Sounds like https://bugzilla.novell.com/show_bug.cgi?id=834991 which also has a solution/workaround. (In short krdc form 4.11 needs freerdp but this is missing as a dependency.)
Christian
I have updated the KRDC package and added freerdp as buildrequires and as requires. This should resolve the missing dependency. If it resolves the issue, I am not sure off. Regards Raymond -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Raymond Wooninck [15.08.2013 20:04]:
On Thursday 15 August 2013 15:58:34 Christian Trippe wrote:
Sounds like https://bugzilla.novell.com/show_bug.cgi?id=834991 which also has a solution/workaround. (In short krdc form 4.11 needs freerdp but this is missing as a dependency.)
Christian
I have updated the KRDC package and added freerdp as buildrequires and as requires. This should resolve the missing dependency. If it resolves the issue, I am not sure off.
Today I found the time to look for it. I did a "zypper in krdc-4.11.0-17.1" to install the package from K:R:411 repo. The package freerdp-1.0.2-11.4.1.x86_64 was already installed. The issue is not solved. I never understood why adding a dependency should solve a problem, when the required package is already installed for other reasons and krdc works with the 4.10 release. I then issued "strace /usr/bin/krdc > ./krdc411.strace 2>&1" and got a file of about 3 MB, which I cannot post, even on susepaste ;-). After "zypper in --oldpackage krdc-4.10.5-1.92.3" I issued "strace /usr/bin/krdc > ./krdc410.strace 2>&1" and the connection succeeded at once. The strace is about 2.4 MB in size. What can I look for in the strace files? A diff does not make much sense, because the memory addresses differ between the runs. gzip makes files of 103058 and 116921 bytes of the straces. Someone interested in reading them? I'll post them off list... Regards, Werner -- -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Friday 23 August 2013 09:59:19 Werner Flamme wrote:
Today I found the time to look for it. I did a "zypper in krdc-4.11.0-17.1" to install the package from K:R:411 repo. The package freerdp-1.0.2-11.4.1.x86_64 was already installed.
The issue is not solved. I never understood why adding a dependency should solve a problem, when the required package is already installed for other reasons and krdc works with the 4.10 release.
I then issued "strace /usr/bin/krdc > ./krdc411.strace 2>&1" and got a file of about 3 MB, which I cannot post, even on susepaste ;-).
Comparing the 4.10 version of KRDC (which depends on rdesktop) with the 4.11 version (which depends on xfreerdp), might not make really sense. Let see first if the underlying technology is working. If you perform the following: xfreerdp <servername>, do you get the login screen ? Or do you see here the same issue ? Regards Raymond -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Friday 23 August 2013 09:59:19 Werner Flamme wrote:
Today I found the time to look for it. I did a "zypper in krdc-4.11.0-17.1" to install the package from K:R:411 repo. The package freerdp-1.0.2-11.4.1.x86_64 was already installed.
Werner, Can you try to run KRDC 4.11 from the command-line and see if you have any logs from there. It could be maybe that your servers have NLA auth activated and then the password prompt (if you did not save the password in kwallet) is being given on the command prompt. Please let me know, because this particular bug (https://bugs.kde.org/show_bug.cgi?id=322361) got already resolved and we could add the upstream commit. Regards Raymond -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Raymond Wooninck [23.08.2013 10:17]:
On Friday 23 August 2013 09:59:19 Werner Flamme wrote:
Today I found the time to look for it. I did a "zypper in krdc-4.11.0-17.1" to install the package from K:R:411 repo. The package freerdp-1.0.2-11.4.1.x86_64 was already installed.
Werner,
Can you try to run KRDC 4.11 from the command-line and see if you have any logs from there. It could be maybe that your servers have NLA auth activated and then the password prompt (if you did not save the password in kwallet) is being given on the command prompt.
Please let me know, because this particular bug (https://bugs.kde.org/show_bug.cgi?id=322361) got already resolved and we could add the upstream commit.
Raymond, I did so and the only 2 lines I got are QDBusObjectPath: invalid path "" krdc(24796)/kdeui (kdelibs): Attempt to use QAction "remote_desktop_dockwidget" with KXMLGUIFactory! I do not get a password prompt at the console nor do I get a login screen in the GUI. The GUI seems to show an enormous big blue screen since the sliders at the right side and at the bottom are quite small (so the can be pushed a long way) - though I defined a screen resolution of 1600x1000, which fits nicely onto my 1920x1200 screen. BTW, I try to connect to a Windows 200 R2 server. 2nd attempt: Ticking "Remember password (kwallet)" did not bring a password prompt either. 3rd attempt: Adding "-u user -p pwd" in the extra options field did nothing. Regards, Werner -- -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Friday 23 August 2013 10:35:12 Werner Flamme wrote:
Raymond,
I did so and the only 2 lines I got are
QDBusObjectPath: invalid path "" krdc(24796)/kdeui (kdelibs): Attempt to use QAction "remote_desktop_dockwidget" with KXMLGUIFactory!
Werner, what about running just the xfreerdp <servername> ?? What does this deliver ? As indicated in my first reply, let's first test if the underlying technology is working. Raymond -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Raymond Wooninck [23.08.2013 10:50]:
On Friday 23 August 2013 10:35:12 Werner Flamme wrote:
Raymond,
I did so and the only 2 lines I got are
QDBusObjectPath: invalid path "" krdc(24796)/kdeui (kdelibs): Attempt to use QAction "remote_desktop_dockwidget" with KXMLGUIFactory!
Werner, what about running just the xfreerdp <servername> ?? What does this deliver ? As indicated in my first reply, let's first test if the underlying technology is working.
Hi Raymond, i tried several times, and indeed xfreerdp seems to be the culprit: first attempt: ---snip--- $ xfreerdp paext connected to paext:3389 Password: @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ WARNING: CERTIFICATE NAME MISMATCH! @ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ The hostname used for this connection (paext) does not match the name given in the certificate: PAEXT.intranet.ufz.de A valid certificate for the wrong name should NOT be trusted! Certificate details: Subject: CN = PAEXT.intranet.ufz.de Issuer: CN = PAEXT.intranet.ufz.de Thumbprint: 51:65:01:22:7c:3d:0d:9f:5d:90:43:75:57:29:b0:0c:b8:20:e1 The above X.509 certificate could not be verified, possibly because you do not have the CA certificate in your certificate store, or the certificate has expired. Please look at the documentation on how to create local certificate store for a private CA. Do you trust the above certificate? (Y/N) Y SSL_read: Failure in SSL library (protocol error?) Authentication failure, check credentials. If credentials are valid, the NTLMSSP implementation may be to blame. ---pins--- second attempt, with FQDN: ---snip--- $ xfreerdp PAEXT.intranet.ufz.de connected to PAEXT.intranet.ufz.de:3389 Password: Certificate details: Subject: CN = PAEXT.intranet.ufz.de Issuer: CN = PAEXT.intranet.ufz.de Thumbprint: 51:65:01:22:7c:3d:0d:9f:5d:90:43:75:57:29:b0:0c:b8:20:e1 The above X.509 certificate could not be verified, possibly because you do not have the CA certificate in your certificate store, or the certificate has expired. Please look at the documentation on how to create local certificate store for a private CA. Do you trust the above certificate? (Y/N) Y SSL_read: Failure in SSL library (protocol error?) Authentication failure, check credentials. If credentials are valid, the NTLMSSP implementation may be to blame. ---pins--- third attempt, some more parameters, at least the certificate is known now: ---snip--- $ xfreerdp PAEXT.intranet.ufz.de -d INTRANET.ufz.de -u wflamme connected to PAEXT.intranet.ufz.de:3389 Password: SSL_read: Failure in SSL library (protocol error?) Authentication failure, check credentials. If credentials are valid, the NTLMSSP implementation may be to blame. ---pins--- And yes, I am sure I did not make a typo with my password ;-) The next tries I do not quote here. I tried "--ntlm 2", "--ntlm 1", "--sec rdp", "--no-nla", "--no-rdp", each in a new attempt. The output was always the same as on the third attempt. Regards, Werner -- -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Friday 23 August 2013 11:17:52 Werner Flamme wrote:
Raymond Wooninck [23.08.2013 10:50]:
On Friday 23 August 2013 10:35:12 Werner Flamme wrote:
Raymond,
I did so and the only 2 lines I got are
QDBusObjectPath: invalid path "" krdc(24796)/kdeui (kdelibs): Attempt to use QAction "remote_desktop_dockwidget" with KXMLGUIFactory!
Werner, what about running just the xfreerdp <servername> ?? What does this deliver ? As indicated in my first reply, let's first test if the underlying technology is working.
Hi Raymond, i tried several times, and indeed xfreerdp seems to be the culprit:
---snip--- $ xfreerdp PAEXT.intranet.ufz.de -d INTRANET.ufz.de -u wflamme connected to PAEXT.intranet.ufz.de:3389 Password: SSL_read: Failure in SSL library (protocol error?) Authentication failure, check credentials. If credentials are valid, the NTLMSSP implementation may be to blame. ---pins---
And yes, I am sure I did not make a typo with my password ;-)
The next tries I do not quote here. I tried "--ntlm 2", "--ntlm 1", "--sec rdp", "--no-nla", "--no-rdp", each in a new attempt. The output was always the same as on the third attempt.
Hi Werner, Unfortunately I can't help you with this. My advice is to raise a bug on bugzilla.novell.com for this one. You can copy and paste your email in there as this already contains quite some information. Regards Raymond -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Raymond Wooninck [23.08.2013 11:23]:
On Friday 23 August 2013 11:17:52 Werner Flamme wrote:
Raymond Wooninck [23.08.2013 10:50]:
On Friday 23 August 2013 10:35:12 Werner Flamme wrote:
Raymond,
I did so and the only 2 lines I got are
QDBusObjectPath: invalid path "" krdc(24796)/kdeui (kdelibs): Attempt to use QAction "remote_desktop_dockwidget" with KXMLGUIFactory!
Werner, what about running just the xfreerdp <servername> ?? What does this deliver ? As indicated in my first reply, let's first test if the underlying technology is working.
Hi Raymond, i tried several times, and indeed xfreerdp seems to be the culprit:
---snip--- $ xfreerdp PAEXT.intranet.ufz.de -d INTRANET.ufz.de -u wflamme connected to PAEXT.intranet.ufz.de:3389 Password: SSL_read: Failure in SSL library (protocol error?) Authentication failure, check credentials. If credentials are valid, the NTLMSSP implementation may be to blame. ---pins---
And yes, I am sure I did not make a typo with my password ;-)
The next tries I do not quote here. I tried "--ntlm 2", "--ntlm 1", "--sec rdp", "--no-nla", "--no-rdp", each in a new attempt. The output was always the same as on the third attempt.
Hi Werner,
Unfortunately I can't help you with this. My advice is to raise a bug on bugzilla.novell.com for this one. You can copy and paste your email in there as this already contains quite some information.
Hi Raymond, I added some words to <https://bugzilla.novell.com/show_bug.cgi?id=808901>, which was opened in march and confirmed in april, but no action was taken :-\ Regards, Werner -- -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Friday 23 August 2013 15:27:53 Werner Flamme wrote:
Hi Raymond,
I added some words to <https://bugzilla.novell.com/show_bug.cgi?id=808901>, which was opened in march and confirmed in april, but no action was taken :-\
Regards,
Werner Hi Werner,
I am afraid that won't help. That bug is about KRDC and as indicated we already established that your issue is with xfreerdp. Also the issue in that bug report is different than yours, as that this is about vnc and NOT rdp. I strongly advice you to open a new bug report for xfreerdp not working on openSUSE 12.3. Regards Raymond -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Friday 23 August 2013 18.01:34 Raymond Wooninck wrote:
On Friday 23 August 2013 15:27:53 Werner Flamme wrote:
Hi Raymond,
I added some words to <https://bugzilla.novell.com/show_bug.cgi?id=808901>, which was opened in march and confirmed in april, but no action was taken :-\
Regards,
Werner Hi Werner,
I am afraid that won't help. That bug is about KRDC and as indicated we already established that your issue is with xfreerdp. Also the issue in that bug report is different than yours, as that this is about vnc and NOT rdp.
I strongly advice you to open a new bug report for xfreerdp not working on openSUSE 12.3.
Regards
Raymond
Unfortunately for you xfreerdp work correctly under 12.3 I've using it almost everyday against all sort of server (XP, Win Vista, Win 7 (32,64), 2003R2, 2008R2 & 2012 How I'm using it is xfreerdp -0 -z -x b -k 0x0000100C --plugin cliprdr --nsc --ignore-certificate --no-nla --fonts --gdi hw also with some plugins when needed --rfx --rfx-mode video --plugin rdpsnd --data pulse -- --plugin drdynvc --data tsmf:audio:pulse -- --plugin audin --plugin rdpdr --data disk:sigeom:/sigeom -- and the login part -n "$HOSTNAME" -u "$USR" -p $PASS -d "$DOM" "$PC" Could you recheck with ... What would be interested is to find the way krdc call the server. -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch openSUSE Member GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Bruno Friedmann [24.08.2013 07:41]:
On Friday 23 August 2013 18.01:34 Raymond Wooninck wrote:
On Friday 23 August 2013 15:27:53 Werner Flamme wrote:
Hi Raymond,
I added some words to <https://bugzilla.novell.com/show_bug.cgi?id=808901>, which was opened in march and confirmed in april, but no action was taken :-\
Regards,
Werner Hi Werner,
I am afraid that won't help. That bug is about KRDC and as indicated we already established that your issue is with xfreerdp. Also the issue in that bug report is different than yours, as that this is about vnc and NOT rdp.
I strongly advice you to open a new bug report for xfreerdp not working on openSUSE 12.3.
Regards
Raymond
Unfortunately for you xfreerdp work correctly under 12.3 I've using it almost everyday against all sort of server (XP, Win Vista, Win 7 (32,64), 2003R2, 2008R2 & 2012
How I'm using it is xfreerdp -0 -z -x b -k 0x0000100C --plugin cliprdr --nsc --ignore-certificate --no-nla --fonts --gdi hw also with some plugins when needed --rfx --rfx-mode video --plugin rdpsnd --data pulse -- --plugin drdynvc --data tsmf:audio:pulse -- --plugin audin --plugin rdpdr --data disk:sigeom:/sigeom -- and the login part -n "$HOSTNAME" -u "$USR" -p $PASS -d "$DOM" "$PC"
Could you recheck with ...
What would be interested is to find the way krdc call the server.
Where do I get information about plugins? I did not install any. And --data is not on my manpage, what does it mean? And what is "RemoteFX"? I never used that AFAIK. Same is valid for "NSCodec", I don't even know it. I didn't need any additional parameters with rdesktop or krdc 4.10. Yes, it was nice if krdc would give a hint what options are used when invoking xfreerdp. Like, dropping a log line... The following command does work: xfreerdp -k 0x00000407 -x l -z -g 1600x1000 -u wflamme -d INTRANET.ufz.de PAEXT.intranet.ufz.de How can I integrate that into krdc's options? Can I put in in ~/.kde4/config/krdcrc, in the respective "extraOptions=" line? But in this file, I see a "KeyboardLayout=3" :-\ Regards, Werner -- -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Werner Flamme [26.08.2013 10:21]:
Bruno Friedmann [24.08.2013 07:41]:
On Friday 23 August 2013 18.01:34 Raymond Wooninck wrote:
On Friday 23 August 2013 15:27:53 Werner Flamme wrote:
Hi Raymond,
I added some words to <https://bugzilla.novell.com/show_bug.cgi?id=808901>, which was opened in march and confirmed in april, but no action was taken :-\
Regards,
Werner Hi Werner,
I am afraid that won't help. That bug is about KRDC and as indicated we already established that your issue is with xfreerdp. Also the issue in that bug report is different than yours, as that this is about vnc and NOT rdp.
I strongly advice you to open a new bug report for xfreerdp not working on openSUSE 12.3.
Regards
Raymond
Unfortunately for you xfreerdp work correctly under 12.3 I've using it almost everyday against all sort of server (XP, Win Vista, Win 7 (32,64), 2003R2, 2008R2 & 2012
How I'm using it is xfreerdp -0 -z -x b -k 0x0000100C --plugin cliprdr --nsc --ignore-certificate --no-nla --fonts --gdi hw also with some plugins when needed --rfx --rfx-mode video --plugin rdpsnd --data pulse -- --plugin drdynvc --data tsmf:audio:pulse -- --plugin audin --plugin rdpdr --data disk:sigeom:/sigeom -- and the login part -n "$HOSTNAME" -u "$USR" -p $PASS -d "$DOM" "$PC"
Could you recheck with ...
What would be interested is to find the way krdc call the server.
Where do I get information about plugins? I did not install any. And --data is not on my manpage, what does it mean? And what is "RemoteFX"? I never used that AFAIK. Same is valid for "NSCodec", I don't even know it. I didn't need any additional parameters with rdesktop or krdc 4.10.
Yes, it was nice if krdc would give a hint what options are used when invoking xfreerdp. Like, dropping a log line...
The following command does work:
xfreerdp -k 0x00000407 -x l -z -g 1600x1000 -u wflamme -d INTRANET.ufz.de PAEXT.intranet.ufz.de
How can I integrate that into krdc's options? Can I put in in ~/.kde4/config/krdcrc, in the respective "extraOptions=" line? But in this file, I see a "KeyboardLayout=3" :-\
OK, krdc 4.11 opens a connection, when I give "-k 0x00000407 -z -u wflamme -d INTRANET.ufz.de" in the "Extra Options" line in the KRDC GUI. The screen did not open without "-k 0x00000407", what I think is strange. And now that I'm on the website www.freerdp.com, I see "remmina" as a menu entry. Remmina works fine here, except that it does not support the common clipboard of local host and remote machine, at least it does not work and I see no GUI switch for it. Looking at the User Manual, I nearly fell off my chair. Printer redirection with "/printer", the remote host ist given with a preceding "/v:" - is this really the same software? The parameters are quite different from those on the manpage that came with xfreerdp (where I see nothing about shared resources like printers and clipboard at all). At least, the common clipboard is available via krdc without additional parameters ;-) Regards, Werner -- -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Monday 26 August 2013 10.44:58 Werner Flamme wrote:
Werner Flamme [26.08.2013 10:21]:
Bruno Friedmann [24.08.2013 07:41]:
On Friday 23 August 2013 18.01:34 Raymond Wooninck wrote:
On Friday 23 August 2013 15:27:53 Werner Flamme wrote:
Hi Raymond,
I added some words to <https://bugzilla.novell.com/show_bug.cgi?id=808901>, which was opened in march and confirmed in april, but no action was taken :-\
Regards,
Werner Hi Werner,
I am afraid that won't help. That bug is about KRDC and as indicated we already established that your issue is with xfreerdp. Also the issue in that bug report is different than yours, as that this is about vnc and NOT rdp.
I strongly advice you to open a new bug report for xfreerdp not working on openSUSE 12.3.
Regards
Raymond
Unfortunately for you xfreerdp work correctly under 12.3 I've using it almost everyday against all sort of server (XP, Win Vista, Win 7 (32,64), 2003R2, 2008R2 & 2012
How I'm using it is xfreerdp -0 -z -x b -k 0x0000100C --plugin cliprdr --nsc --ignore-certificate --no-nla --fonts --gdi hw also with some plugins when needed --rfx --rfx-mode video --plugin rdpsnd --data pulse -- --plugin drdynvc --data tsmf:audio:pulse -- --plugin audin --plugin rdpdr --data disk:sigeom:/sigeom -- and the login part -n "$HOSTNAME" -u "$USR" -p $PASS -d "$DOM" "$PC"
Could you recheck with ...
What would be interested is to find the way krdc call the server.
Where do I get information about plugins? I did not install any. And --data is not on my manpage, what does it mean? And what is "RemoteFX"? I never used that AFAIK. Same is valid for "NSCodec", I don't even know it. I didn't need any additional parameters with rdesktop or krdc 4.10.
Yes, it was nice if krdc would give a hint what options are used when invoking xfreerdp. Like, dropping a log line...
The following command does work:
xfreerdp -k 0x00000407 -x l -z -g 1600x1000 -u wflamme -d INTRANET.ufz.de PAEXT.intranet.ufz.de
How can I integrate that into krdc's options? Can I put in in ~/.kde4/config/krdcrc, in the respective "extraOptions=" line? But in this file, I see a "KeyboardLayout=3" :-\
OK, krdc 4.11 opens a connection, when I give "-k 0x00000407 -z -u wflamme -d INTRANET.ufz.de" in the "Extra Options" line in the KRDC GUI.
The screen did not open without "-k 0x00000407", what I think is strange.
And now that I'm on the website www.freerdp.com, I see "remmina" as a menu entry. Remmina works fine here, except that it does not support the common clipboard of local host and remote machine, at least it does not work and I see no GUI switch for it.
Looking at the User Manual, I nearly fell off my chair. Printer redirection with "/printer", the remote host ist given with a preceding "/v:" - is this really the same software? The parameters are quite different from those on the manpage that came with xfreerdp (where I see nothing about shared resources like printers and clipboard at all).
At least, the common clipboard is available via krdc without additional parameters ;-)
Regards, Werner
Welcome on the big mess of freerdp. I was waiting & hoping they will publish the 1.1 branch but seems we will not have it for 13.1 http://sourceforge.net/mailarchive/forum.php?thread_name=51E6F0DD.2020809%40thinstuff.at&forum_name=freerdp-devel I've determined the different options for plugin by reading the wiki, and try & error method. I suspect that lot of frontend are still trying to find their way between old rdesktop and new freerdp. -- Bruno Friedmann Ioda-Net S�rl www.ioda-net.ch openSUSE Member GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Bruno Friedmann [27.08.2013 10:54]:
On Monday 26 August 2013 10.44:58 Werner Flamme wrote:
Werner Flamme [26.08.2013 10:21]:
Bruno Friedmann [24.08.2013 07:41]:
On Friday 23 August 2013 18.01:34 Raymond Wooninck wrote:
On Friday 23 August 2013 15:27:53 Werner Flamme wrote:
Hi Raymond,
I added some words to <https://bugzilla.novell.com/show_bug.cgi?id=808901>, which was opened in march and confirmed in april, but no action was taken :-\
Regards, > Werner Hi Werner,
I am afraid that won't help. That bug is about KRDC and as indicated we already established that your issue is with xfreerdp. Also the issue in that bug report is different than yours, as that this is about vnc and NOT rdp.
I strongly advice you to open a new bug report for xfreerdp not working on openSUSE 12.3.
Regards
Raymond
Unfortunately for you xfreerdp work correctly under 12.3 I've using it almost everyday against all sort of server (XP, Win Vista, Win 7 (32,64), 2003R2, 2008R2 & 2012
How I'm using it is xfreerdp -0 -z -x b -k 0x0000100C --plugin cliprdr --nsc --ignore-certificate --no-nla --fonts --gdi hw also with some plugins when needed --rfx --rfx-mode video --plugin rdpsnd --data pulse -- --plugin drdynvc --data tsmf:audio:pulse -- --plugin audin --plugin rdpdr --data disk:sigeom:/sigeom -- and the login part -n "$HOSTNAME" -u "$USR" -p $PASS -d "$DOM" "$PC"
Could you recheck with ...
What would be interested is to find the way krdc call the server.
Where do I get information about plugins? I did not install any. And --data is not on my manpage, what does it mean? And what is "RemoteFX"? I never used that AFAIK. Same is valid for "NSCodec", I don't even know it. I didn't need any additional parameters with rdesktop or krdc 4.10.
Yes, it was nice if krdc would give a hint what options are used when invoking xfreerdp. Like, dropping a log line...
The following command does work:
xfreerdp -k 0x00000407 -x l -z -g 1600x1000 -u wflamme -d INTRANET.ufz.de PAEXT.intranet.ufz.de
How can I integrate that into krdc's options? Can I put in in ~/.kde4/config/krdcrc, in the respective "extraOptions=" line? But in this file, I see a "KeyboardLayout=3" :-\
OK, krdc 4.11 opens a connection, when I give "-k 0x00000407 -z -u wflamme -d INTRANET.ufz.de" in the "Extra Options" line in the KRDC GUI.
The screen did not open without "-k 0x00000407", what I think is strange.
And now that I'm on the website www.freerdp.com, I see "remmina" as a menu entry. Remmina works fine here, except that it does not support the common clipboard of local host and remote machine, at least it does not work and I see no GUI switch for it.
Looking at the User Manual, I nearly fell off my chair. Printer redirection with "/printer", the remote host ist given with a preceding "/v:" - is this really the same software? The parameters are quite different from those on the manpage that came with xfreerdp (where I see nothing about shared resources like printers and clipboard at all).
At least, the common clipboard is available via krdc without additional parameters ;-)
Regards, Werner
Welcome on the big mess of freerdp.
Thanks :-(
I was waiting & hoping they will publish the 1.1 branch but seems we will not have it for 13.1 http://sourceforge.net/mailarchive/forum.php?thread_name=51E6F0DD.2020809%40thinstuff.at&forum_name=freerdp-devel I've determined the different options for plugin by reading the wiki, and try & error method.
I suspect that lot of frontend are still trying to find their way between old rdesktop and new freerdp.
I tried /printers, --printers and -printers just to get the "connection impossible" message. Why ist it "impossible"? This may be incompatible or invalid parameters, but impossible? Were there any good reasons for switching to freerdp? At least in this mailing list I find nothing about it. Or was it just the "feature" that freerdp is available on Windows too? Sighing, Werner -- -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
I tried /printers, --printers and -printers just to get the "connection impossible" message. Why ist it "impossible"? This may be incompatible or invalid parameters, but impossible?
I never seen --printers in xfreerdp man page The plugin is documented as --plugin rdpdr --data printer:<printername>:<driver> -- (Don't forget the -- at the end!)
Were there any good reasons for switching to freerdp? At least in this mailing list I find nothing about it. Or was it just the "feature" that freerdp is available on Windows too?
freerdp is a new project due to the total abandon of rdesktop with a new (too new) architecture.
Sighing, Werner
Also take care of sample, they have actually 3 branches the stable last publish is 1.0.2 (1.0.3 will certainly appears soon or not) 1.1 which is at beta stage actually will lots of issues 1.2 which is the current devel. Look like they're trying to run after too much rabbit at the same time. -- Bruno Friedmann Ioda-Net S�rl www.ioda-net.ch openSUSE Member GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Bruno Friedmann [28.08.2013 16:02]:
I tried /printers, --printers and -printers just to get the "connection impossible" message. Why ist it "impossible"? This may be incompatible or invalid parameters, but impossible?
I never seen --printers in xfreerdp man page
I did not see this either. I just figured out that this might be a possible parameter follwing the "old syntax"/"new syntax" part of the docu, since the new way is "/printers".
The plugin is documented as --plugin rdpdr --data printer:<printername>:<driver> --
(Don't forget the -- at the end!)
My manpage says nothing out rdpdr :-( But the Ubuntu manpage that can be found on <http://manpages.ubuntu.com/manpages/maverick/man1/xfreerdp.1.html> does.
Were there any good reasons for switching to freerdp? At least in this mailing list I find nothing about it. Or was it just the "feature" that freerdp is available on Windows too? freerdp is a new project due to the total abandon of rdesktop with a new (too new) architecture.
Also take care of sample, they have actually 3 branches the stable last publish is 1.0.2 (1.0.3 will certainly appears soon or not) 1.1 which is at beta stage actually will lots of issues 1.2 which is the current devel.
When the documentation is splitted properly, I have no problem with that. The Ubuntu manpage is from version 0.7, but seems to work for my 1.0.2 also; the manpage in my rpm is obviously incomplete. The option "--plugin pluginname" is described as "load pluginname", but there is no list which plugins exist.
Look like they're trying to run after too much rabbit at the same time.
Indeed. -- -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Stefan Kunze [15.08.2013 13:24]:
Am Donnerstag, 15. August 2013, 12:43:24 schrieb Werner Flamme:
in our mixed (Windows/Linux/Solaris) office environment, I often have to use KRDC to connect to a Windows terminal server. After upgrading to 4.11, the screen stays blue, no login is possible.
And yes, I restarted KDE after upgrading to 4.11 :-)
After "zypper in --oldpackage krdc-4.10.5-1.92.3" everything is fine, so the bug (if it is one) is in KRDC, not somewhere inside KDE.
Can someone confirm this?
Hi Werner,
I have not upgraded to 4.11 yet but the symptom you describe is similar to what I experience when trying to connect via krdc to a VMWare Guest running Opensuse 13.1 Milestone 3 IIRC - not sure if this had already KDE 4.11 Development in it. So far i did not had much time to troubleshoot the issue . Blue screen and no connection . My KRDC runs on a Opensuse 12.3 with KDE 4.10.5
Hi Stefan, hmmmm, after downgrading krdc, every connection works. Re-Upgrading causes every connection to fail. Re-downgrading and everything works again. I do not think that the RDP server is the problem in my case. Sometimes I had the problem with 4.10 before, but on second try everything worked fine. I did not experience any problems for some weeks now. And remmina works too, if krdc 4.11 is installed, with exactly the servers krdc refuses to connect to. Regards, Werner -- -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
participants (5)
-
Bruno Friedmann -
Christian Trippe -
Raymond Wooninck -
Stefan Kunze -
Werner Flamme