| Summary: | cervisia with cvs over ssh goes to wrong port number | ||
|---|---|---|---|
| Product: | [Applications] cervisia | Reporter: | gregry_7 |
| Component: | general | Assignee: | Christian Loose <christian.loose> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version First Reported In: | 3.7.0 | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: |
attachment-16722-0.html
attachment-16722-1.dat cervisia.txt |
||
|
Description
gregry_7
2012-09-04 21:50:38 UTC
I should also note: In cervisia, under 'Repository', selecting the only entry and hitting 'Modify', I have also tried putting both "ssh" and "ssh -p 22" (without the quotes) in the "Use remote shell:" field. Initially it was blank. None of those 3 settings worked either Created attachment 73688 [details] attachment-16722-0.html Hi On Tuesday 04 September 2012 21:56:54 gregry_7@yahoo.com wrote: > https://bugs.kde.org/show_bug.cgi?id=306269 > > --- Comment #1 from gregry_7@yahoo.com --- > I should also note: In cervisia, under 'Repository', selecting the only > entry and hitting 'Modify', does that entry look like ":ext:gggggg@192.168.1.201:/usr/local/cvsroot"? > I have also tried putting both "ssh" and "ssh > -p 22" (without the quotes) in the "Use remote shell:" field. Initially it > was blank. None of those 3 settings worked either If you're using ssh it should be ssh. Do you use ssh_agent? I've no clue how Cervisia would use port 514. Are you sure that it's really Cervisia and not another program? Cheers, André Andre, Thanks for your reply. > does that entry look like ":ext:gggggg@192.168.1.201:/usr/local/cvsroot"? Yes, the contents of Repository->Modify->Repository exactly matches the CVSROOT environment variable. > If you're using ssh it should be ssh. > > Do you use ssh_agent? If I do use ssh_agent, it's not intentional. How would I tell? > I've no clue how Cervisia would use port 514. Are you sure that it's really Cervisia and not another program? I'm certain its not another application. It's Cervisia, or something that it invokes. Your comments about "Use remote shell:" needing to be "ssh" made me try that again. I believe I have found a different bug that somewhat explains the issue, but it can be worked around. Initially, my "Use remote shell:" field was empty. I tried setting it to "ssh" and doing an update, but I still saw the same behavior (tcp connection attempted to port 514 of the server instead of 22). Today, I also ran "ps aux --forest" meanwhile. Although the "Use remote shell:" was changed to "ssh" in Cervisia, its still using rsh. If I return to the "Use remote shell:" settings, it shows the "ssh" that I placed there, even though rsh was invoked. See attachment. However, If I leave that set to "ssh", close and restart cervisia, then do an update, it works. Then, it correctly invokes ssh instead of rsh. Thanks for your help. ________________________________ From: Andre Woebbeking <woebbeking@kde.org> To: gregry_7@yahoo.com Sent: Wednesday, September 5, 2012 4:21 PM Subject: [Bug 306269] cervisia with cvs over ssh goes to wrong port number https://bugs.kde.org/show_bug.cgi?id=306269 --- Comment #2 from Andre Woebbeking <woebbeking@kde.org> --- Hi On Tuesday 04 September 2012 21:56:54 gregry_7@yahoo.com wrote: > https://bugs.kde.org/show_bug.cgi?id=306269 > > --- Comment #1 from gregry_7@yahoo.com --- > I should also note: In cervisia, under 'Repository', selecting the only > entry and hitting 'Modify', does that entry look like ":ext:gggggg@192.168.1.201:/usr/local/cvsroot"? > I have also tried putting both "ssh" and "ssh > -p 22" (without the quotes) in the "Use remote shell:" field. Initially it > was blank. None of those 3 settings worked either If you're using ssh it should be ssh. Do you use ssh_agent? I've no clue how Cervisia would use port 514. Are you sure that it's really Cervisia and not another program? Cheers, André Created attachment 73689 [details]
attachment-16722-1.dat
Created attachment 73690 [details]
cervisia.txt
Hmm, I replied to your email from yahoo's webmail, and my comment shows up as an attachment... I'll re-paste it here. Andre, Thanks for your reply. > does that entry look like ":ext:gggggg@192.168.1.201:/usr/local/cvsroot"? Yes, the contents of Repository->Modify->Repository exactly matches the CVSROOT environment variable. > If you're using ssh it should be ssh. > > Do you use ssh_agent? If I do use ssh_agent, it's not intentional. How would I tell? > I've no clue how Cervisia would use port 514. Are you sure that it's really Cervisia and not another program? I'm certain its not another application. It's Cervisia, or something that it invokes. Your comments about "Use remote shell:" needing to be "ssh" made me try that again. I believe I have found a different bug that somewhat explains the issue, but it can be worked around. Initially, my "Use remote shell:" field was empty. I tried setting it to "ssh" and doing an update, but I still saw the same behavior (tcp connection attempted to port 514 of the server instead of 22). Today, I also ran "ps aux --forest" meanwhile. Although the "Use remote shell:" was changed to "ssh" in Cervisia, its still using rsh. If I return to the "Use remote shell:" settings, it shows the "ssh" that I placed there, even though rsh was invoked. See attachment. However, If I leave that set to "ssh", close and restart cervisia, then do an update, it works. Then, it correctly invokes ssh instead of rsh. Thanks for your help. To be thorough about the bug report, I guess it should also be noted that the value of environment variable CVS_RSH (which has been set to "ssh" all along) being ignored seems to also be a bug. > --- Comment #3 from gregry_7@yahoo.com --- > > Do you use ssh_agent? > > If I do use ssh_agent, it's not intentional. How would I tell? Well, it makes your life much easier if you use ssh keys with passphrase. If you use it it's normally started with your session and if you add a passphrase to it that passphrase is cached by the agent and applied when you use ssh. > Your comments about "Use remote shell:" needing to be "ssh" made me try that > again. I believe I have found a different bug that somewhat explains the > issue, but it can be worked around. > > Initially, my "Use remote shell:" field was empty. Because not everyone uses ssh. > I tried setting it to > "ssh" and doing an update, but I still saw the same behavior (tcp > connection attempted to port 514 of the server instead of 22). Today, I > also ran "ps aux --forest" meanwhile. Although the "Use remote shell:" was > changed to "ssh" in Cervisia, its still using rsh. If I return to the "Use > remote shell:" settings, it shows the "ssh" that I placed there, even > though rsh was invoked. See attachment. > > However, If I leave that set to "ssh", close and restart cervisia, then do > an update, it works. Then, it correctly invokes ssh instead of rsh. That sounds like a bug. If you configure ssh as remote shell it should be used immediately and not after next startup. > Thanks for your help. You're welcome. > --- Comment #7 from gregry_7@yahoo.com --- > To be thorough about the bug report, I guess it should also be noted that > the value of environment variable CVS_RSH (which has been set to "ssh" all > along) being ignored seems to also be a bug. I'd call that a feature request :-) Cervisia doesn't look into CVS_RSH it only sets it when calling CVS. Cervisia was probably made for people who don't care about enviroment variables. Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone! Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone! Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |