Code: Select all
cd sudo chown pi:pi .Xauthority
Yes, but if it already exits and is owned by root then when X is run by pi it can't access the file and won't start. Wrong ownership is the common cause of X failing to start.
It's amusing that you think this a problem with the release rather than a consequence of something you have done that has broken your system.
As far as I can tell this is the report, but just because there is a report doesn't mean it will get fixed. In order to make things seem more secure, many people go about making changes that break the general use case but not the common use. Traditionally the X server is a setuid root program. For some time Debian has cleared the setuid bit from the server binary and created a separate setuid wrapper that calls the server. The thinking seems to be two programs are somehow easier to secure and maintain than one.PeterO wrote: ↑Mon Jun 29, 2020 2:56 pmIt's amusing that you think this a problem with the release rather than a consequence of something you have done that has broken your system.
Do you not think that if it was a problem with the release that it would not have been reported and fixed after nearly a month ?
If this was a report of a problem with the release, then please explain why has it taken a month for someone to discover that something as fundamental as the X server is not working ?
I believe it's created by your login manager (xdm, gdm, etc.). It sounds like you're not running one.
I do, for one.
On a desktop sytem, yes. But on a server do you really want a desktop running and a user logged in*? That's horribly insecure and resource inefficient.On any Linux OS, but in particular in Raspbian.
Isn't the whole point that the desktop comes up "automatically"?
Probably rare in the desktop world. May be rare in the server world but not for the reason you think. I suspect when doing remote admin that needs a GUI app the method used will be to run it over X11 forwarding to a remote X server running a desktop rather than start an entire desktop on the server. Or to use a remote X server to login to the server via XDM (or whatever the modern replacement for that is).Now, having said all that, there are specialized use cases where you do boot to a command line and then invoke startx/xinit manually, but they are rare.
Code: Select all
Maybe, but I doubt it'll shed light on the problem.I think what we should be doing is trying to figure out why OP is doing this.
Yes, tried it before my first replyejolson wrote: ↑Mon Jun 29, 2020 4:53 pm