Re: Problems connecting to VM via ssh (Ed Greshko)

2020-01-23 Thread Patrick O'Callaghan
On Thu, 2020-01-23 at 04:56 +, George R Goffe via users wrote: > You suggested that this should go to the tst mailing list. Isn't that for > testers? Maybe that's what I am? I enjoy being on the bleeding edge and > reporting bugs. If you're using anything other than the released version (cur

Re: Problems connecting to VM via ssh (Ed Greshko)

2020-01-22 Thread Ed Greshko
On 2020-01-23 12:56, George R Goffe via users wrote: > > I have re-installed this system and selected the "KDE Plasma Workspaces" but > without any optional packages since there is at least one pkg that fails and > TERMINATES the installation. I wrote a bug report on that. The installation > sho

Re: Problems connecting to VM via ssh (Ed Greshko)

2020-01-22 Thread Ed Greshko
On 2020-01-23 12:56, George R Goffe via users wrote: > > I have re-installed this system and selected the "KDE Plasma Workspaces" but > without any optional packages since there is at least one pkg that fails and > TERMINATES the installation. I wrote a bug report on that. The installation > sho

Re: Problems connecting to VM via ssh (Ed Greshko)

2020-01-22 Thread Samuel Sieb
On 1/22/20 8:56 PM, George R Goffe via users wrote: You suggested that this should go to the tst mailing list. Isn't that for testers? Maybe that's what I am? I enjoy being on the bleeding edge and reporting bugs. So, thanks for your input. The test list is for discussing issues specific to ve

Re: Problems connecting to VM via ssh (Ed Greshko)

2020-01-22 Thread George R Goffe via users
Ed, I have re-installed this system and selected the "KDE Plasma Workspaces" but without any optional packages since there is at least one pkg that fails and TERMINATES the installation. I wrote a bug report on that. The installation should at least allow the user to go back and de-select the f

Re: Problems connecting to VM via ssh (Ed Greshko)

2020-01-21 Thread Ed Greshko
On 2020-01-22 04:13, George R Goffe via users wrote: > Ed, > > Thanks for responding to my question. > > Yes. The host AND guest are both fc32 x86_64 (rawhide). I forgot to put the > rawhide in. > > Apparently tstusr is a "dup" of root. I guess it was late when I did this. > Anyway. I can login a

Re: Problems connecting to VM via ssh (Ed Greshko)

2020-01-21 Thread George R Goffe via users
Ed, Thanks for responding to my question. Yes. The host AND guest are both fc32 x86_64 (rawhide). I forgot to put the rawhide in. Apparently tstusr is a "dup" of root. I guess it was late when I did this. Anyway. I can login as root and tstusr at the console. I can su to root from tstusr and su

Re: Problems connecting to VM via ssh

2020-01-21 Thread Patrick O'Callaghan
On Tue, 2020-01-21 at 07:56 +, George R Goffe via users wrote: > I just installed a Fedora Core 32 (x86_64) system in a VM running under > VirtualBox and am trying to ssh into the VM. This should surely go to the Test List, not here. F32 is unreleased. poc ___

Re: Problems connecting to VM via ssh

2020-01-21 Thread Ed Greshko
On 2020-01-21 17:09, Ed Greshko wrote: > The above seems to indicate that "tstusr" has uid=0, gid=0.  Meaning you have > made "tstusr" > synonymous with "root"? Ooopss... Sorry, I misread the output.  You said "client", my brain said "server". You're trying to ssh from the root account to the V

Re: Problems connecting to VM via ssh

2020-01-21 Thread Ed Greshko
On 2020-01-21 15:56, George R Goffe via users wrote: > Hi, > > I just installed a Fedora Core 32 (x86_64) system in a VM running under > VirtualBox and am trying to ssh into the VM. No such animal as of yet.  F31 was the last release.  Are you talking "rawhide"? Anyway > > When I try to lo

Problems connecting to VM via ssh

2020-01-21 Thread George R Goffe via users
Hi, I just installed a Fedora Core 32 (x86_64) system in a VM running under VirtualBox and am trying to ssh into the VM. When I try to login I get a "client_loop: send disconnect: Broken pipe" message for my trouble. This is what I'm getting from the client side: ssh -v tstusr@10.28.0.4OpenSSH_8.