I really don't know how I screwed this up, but I've been "playing" with
this for hours with no success.
I have a raspberry PI file server. I rarely use the GUI and when I do
it's usually over VNC (I use KRDC) or with ssh -X.
As of today:
1 - KRDC won't connect
2 - ssh -X pi@pi (pi is defined
On Sun, Feb 4, 2018 at 11:54 AM, Shlomo Solomon
wrote:
> I really don't know how I screwed this up, but I've been "playing" with
> this for hours with no success.
>
> I have a raspberry PI file server. I rarely use the GUI and when I do
> it's usually over VNC (I use KRDC) or with ssh -X.
>
> As
On Sun, 4 Feb 2018 12:26:41 +0200
shimi wrote:
> On Sun, Feb 4, 2018 at 11:54 AM, Shlomo Solomon
> wrote:
>
> > I really don't know how I screwed this up, but I've been "playing"
> > with this for hours with no success.
> >
> > I have a raspberry PI file server. I rarely use the GUI and when I
Server side :
Please make sure you have free disk space for the user to use, and that the
current user is owning ~/.Xauthority.
Make sure that you didn't touch ForwardX11Timeout setting for sshd.conf.
This can also be caused by selinux
To verify it is not a user restriction, add a brand new user
Check the memory card. I quit using Pi due to frequent problems with
various mem cards.
I kept regular backups and images just to repair the problems.
On 04/02/2018 14:18, Borissh1983 wrote:
Server side :
Please make sure yo
