Re: User no boot -

On Sun, 28 Jun 2020 at 18:05, Bob Goodwin wrote: > The boot problems are fixed with a new Fedora 32 instillation. > > Thanks to everyone who responded to my request for help. > Glad to hear the new install worked. > > Presently Samba has been installed and appears to be near working . I > follo

Re: User no boot -

On 2020-06-26 19:26, George N. White III wrote: On Fri, 26 Jun 2020 at 20:00, Bob Goodwin > wrote: My Samba server began refusing my effort to access it as bobg or any thing else I created to test with, it only let me connect as root. By "connect", do

Re: User no boot -

On 2020-06-27 07:16, Ed Greshko wrote: Well, root should be able to do*everything*.  So, it sounds as if that system has much more issues than just new users not "working". ° Definitely not true, try the Thunar File Manager as root, well I guess you can force it but it protests. However,I on

Re: User no boot -

On 2020-06-27 07:16, Ed Greshko wrote: Well, root should be able to do*everything*.  So, it sounds as if that system has much more issues than just new users not "working". ° Definitely not true, try the Thunar File Manager as root, well I guess you can force it but it protests. However,I on

Re: User no boot -

On 2020-06-27 18:47, Bob Goodwin wrote: > > > On 2020-06-26 22:33, Ed Greshko wrote: >> Oh, when are you planning to do the install?  Are you going to do a fresh >> install of F32, or?? > I would hope this weekend if I can get help. My equipment arrangement has > grown over the years and the comp

Re: User no boot -

On Jun 26, 2020, at 21:52, Bob Goodwin wrote: > So I tried the following: > > Logout root via ssh: > [root@box48 ~]# logout > Connection to 192.168.50.148 closed. > > Log in bobg: > [bobg@WS1 ~]$ ssh bobg@192.168.50.148 > bobg@192.168.50.148's password: > Last login: Tue May 26 15:16:50 2020 fro

Re: User no boot -

On 2020-06-26 22:33, Ed Greshko wrote: Oh, when are you planning to do the install?  Are you going to do a fresh install of F32, or?? I would hope this weekend if I can get help. My equipment arrangement has grown over the years and the computers are in rack and panel type enclosures secured

Re: User no boot -

On 6/27/20 12:01 AM, Jon LaBadie wrote: On Fri, Jun 26, 2020 at 09:51:50PM -0400, Bob Goodwin wrote: [bobg@WS1 ~]$ ssh bob@192.168.50.148 bob@192.168.50.148's password: Last login: Tue May 26 15:20:58 2020 from 192.168.50.57 /bin/bash: Permission denied Connection to 192.168.50.148 closed. Both

Re: User no boot -

On Fri, Jun 26, 2020 at 09:51:50PM -0400, Bob Goodwin wrote: > > > On 2020-06-26 19:55, Ed Greshko wrote: > > On 2020-06-27 07:50, Bob Goodwin wrote: > > > > > > On 2020-06-26 19:29, Ed Greshko wrote: > > > > I think you mean > > > > > > > > 1.  Connected monitor and keyboard and booted to

Re: User no boot -

On 2020-06-27 09:51, Bob Goodwin wrote: > So I tried the following: > > Logout root via ssh: > [root@box48 ~]# logout > Connection to 192.168.50.148 closed. > > Log in bobg: > [bobg@WS1 ~]$ ssh bobg@192.168.50.148 > bobg@192.168.50.148's password: > Last login: Tue May 26 15:16:50 2020 from 192.168

Re: User no boot -

On 6/26/20 6:51 PM, Bob Goodwin wrote: Log in bobg: [bobg@WS1 ~]$ ssh bobg@192.168.50.148 bobg@192.168.50.148's password: Last login: Tue May 26 15:16:50 2020 from 192.168.50.57 /bin/bash: Permission denied Connection to 192.168.50.148 closed. Now that is the kind of details we're looking for.

Re: User no boot -

On 2020-06-26 19:55, Ed Greshko wrote: On 2020-06-27 07:50, Bob Goodwin wrote: On 2020-06-26 19:29, Ed Greshko wrote: I think you mean 1.  Connected monitor and keyboard and booted to a command line login prompt. 2.  Logged in as root 3.  Used startx and got an xfce desktop 4.  Created

Re: User no boot -

On 2020-06-27 07:50, Bob Goodwin wrote: > > > On 2020-06-26 19:29, Ed Greshko wrote: >> I think you mean >> >> 1.  Connected monitor and keyboard and booted to a command line login prompt. >> 2.  Logged in as root >> 3.  Used startx and got an xfce desktop >> 4.  Created a new user using "usera

Re: User no boot -

On Fri, 2020-06-26 at 19:17 -0400, Bob Goodwin wrote: > I connected a monitor and keyboard and could start it with startx > and logged in as root, got an xfce desktop and went from there but as > I said, it has to be as root. It would allow me to create new users > but they could not do anything .

Re: User no boot -

On 2020-06-26 19:29, Ed Greshko wrote: I think you mean 1.  Connected monitor and keyboard and booted to a command line login prompt. 2.  Logged in as root 3.  Used startx and got an xfce desktop 4.  Created a new user using "useradd". . Yes exactly as you say, But I have not logged out,

Re: User no boot -

On 2020-06-27 07:17, Bob Goodwin wrote: > > > On 2020-06-26 19:02, Samuel Sieb wrote: >> >> More details.  What do you mean by "boot for any user"?  How are you trying >> to login?  How were you accessing it without an IP address?? > I connected a monitor and keyboard  and could start it with sta

Re: User no boot -

On Fri, 26 Jun 2020 at 20:00, Bob Goodwin wrote: > My Samba server began refusing my effort to access it as bobg or any > thing else I created to test with, it only let me connect as root. By "connect", do you mean you are logging in from another system using, e.g., ssh, from a console, or from

Re: User no boot -

On 2020-06-26 19:02, Samuel Sieb wrote: More details.  What do you mean by "boot for any user"?  How are you trying to login?  How were you accessing it without an IP address?? I connected a monitor and keyboard  and could start it with startx and logged in as root, got an xfce desktop and

Re: User no boot -

On 6/26/20 3:58 PM, Bob Goodwin wrote: My Samba server began refusing my effort to access it as bobg or any thing else I created to test with, it only let me connect as root. Not much of a problem since I rarely needed administrative access to it and the primary users, the iPhone users, still c

User no boot -

My Samba server began refusing my effort to access it as bobg or any thing else I created to test with, it only let me connect as root. Not much of a problem since I rarely needed administrative access to it and the primary users, the iPhone users, still connected without difficulty. The time