Discussion:
X does not work as regular user, but it does at root
Antonio Olivares
4 years ago
Permalink
Dear kind FreeBSD users,

I have succeeded in installing FreeBSD 13 on an old eight core
machine. I created a regular user, but cannot login to X. I am
sending this from root account.
Xorg.conf
I am attaching tmp.txt from working root. I have captured the output
from /var/log/Xorg.log.* from when I try to run startx as regular
user.
Thank you in advance.



Best Regards,


Antonio

***@coolermaster:~ # uname -a
FreeBSD coolermaster 13.0-RELEASE FreeBSD 13.0-RELEASE #0
releng/13.0-n244733-ea31abc261f: Fri Apr 9 04:24:09 UTC 2021
***@releng1.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC
amd64
***@coolermaster:~ #
Gary Aitken
4 years ago
Permalink
Post by Antonio Olivares
I have succeeded in installing FreeBSD 13 on an old eight core
machine. I created a regular user, but cannot login to X. I am
sending this from root account.
Xorg.conf
I am attaching tmp.txt from working root. I have captured the output
from /var/log/Xorg.log.* from when I try to run startx as regular
user.
Thank you in advance.
It looks like some kind of keyboard issue, judging from the log file,
even though it says it is not fatal.

You might check the permissions on the tree /usr/local/share/X11/xkb

Gary
Antonio Olivares
4 years ago
Permalink
...
Dear Sir

You are correct in your assessment. The folder /tmp is not writable by my
user and as a result cannot create the /tmp/k* file by keyboard-config.
Reading the file permissions should be 1777 so as root I ran chmod 1777
/tmp/*

But after shutdown (does not shutdown) I press reboot, all is lost and upon
logging in and running startx the same thing happens. I have to login as
root run startx, run chmod 1777 /tmp/*, logout and then I can login as a
regular user. How can I check the permissions? On another machine I ran
13.0Beta1 all the way to release most things are working great (except java
web start), but I am limited in troubleshooting these things. I have to
use webcam, and the webcam was blinking when using Google meets but another
plugin(hue viewer ) helps stabilize the webcam.

Thank you for your help.

Best Regards,


Antonio
parv/freebsd
4 years ago
Permalink
...
No, no ...
Post by Antonio Olivares
But after shutdown (does not shutdown) I press reboot, all is lost and upon
logging in and running startx the same thing happens. I have to login as
root run startx, run chmod 1777 /tmp/*, logout and then I can login as a
regular user.
...

Instead of setting setuid on each & every file & directory under /tmp, you
need
to set those permissions on /tmp directory itself. Then anyone can create
the
files in /tmp & not overwrite each others'.

But before you do that, please post the output of ...

% /bin/ls -Fold /tmp

... below is from on my computer, all the directories are created (much) after
machine has rebooted & I do not set the permission on any files & directories in
/tmp ...


drwxrwxrwt 7 root wheel uarch 9 Apr 16 15:50 /tmp/


... you can set the permissions on /tmp via as root ...

% chmod 1777 /tmp



- parv
parv/freebsd
4 years ago
Permalink
On Fri, Apr 16, 2021 at 4:09 PM parv/freebsd wrote:
...
Post by parv/freebsd
Instead of setting setuid on each & every file & directory under /tmp,
Sorry, above “setuid” should have been “sticky bit”.


- parv


you need
...
parv/freebsd
4 years ago
Permalink
...
you [may] need
Post by parv/freebsd
to set those permissions on /tmp directory itself. Then anyone can create
the
files in /tmp & not overwrite each others'
...
as root ...
Post by parv/freebsd
% chmod 1777 /tmp
All the other directories are created & permissions set after booting
FreeBSD by the system. If that is not the case for you, then you may be
missing or may have mis-edited files in /etc.

Below is /tmp just after booting & I have logged in on the console and not
have started Xorg yet ...

% /bin/ls -FaCl /tmp/
total 36
drwxrwxrwt 7 root wheel 7 Apr 17 09:37 ./
drwxr-xr-x 24 root wheel 29 Apr 16 23:37 ../
drwxrwxrwt 2 root wheel 2 Apr 16 23:37 .ICE-unix/
drwxrwxrwt 2 root wheel 2 Apr 16 23:37 .X11-unix/
drwxrwxrwt 2 root wheel 2 Apr 16 23:37 .XIM-unix/
drwxrwxrwt 2 root wheel 2 Apr 16 23:37 .font-unix/
drwxr-xr-x 2 parv wheel 2 Apr 17 09:37 gimp-parv/

... that "/tmp/gimp-parv" directory is created during my shell start up. All
others are created by FreeBSD.


- parv
Antonio Olivares
4 years ago
Permalink
On Sat, Apr 17, 2021 at 2:51 PM parv/freebsd
...
***@coolermaster:~ $ cat output1.txt
drwxrwxrwt 7 root wheel uarch 8 Apr 19 08:40 /tmp/
***@coolermaster:~ $ cat output2.txt
drwxrwxrwt 7 root wheel uarch 8 Apr 19 08:40 /tmp/
***@coolermaster:~ $

***@coolermaster:~ $ /bin/ls -FaCl /tmp/
total 49
drwxrwxrwt 11 root wheel 17 Apr 19 09:45 ./
drwxr-xr-x 19 root wheel 25 Apr 19 08:40 ../
drwxrwxrwt 2 root wheel 3 Apr 19 08:45 .ICE-unix/
-r--r--r-- 1 root wheel 11 Apr 19 08:45 .X0-lock
drwxrwxrwt 2 root wheel 3 Apr 19 08:45 .X11-unix/
drwxrwxrwt 2 root wheel 2 Apr 19 08:40 .XIM-unix/
drwxrwxrwt 2 root wheel 2 Apr 19 08:40 .font-unix/
-rw------- 1 olivares wheel 3875 Apr 19 08:51 .org.chromium.Chromium.2ecL1k
drwx------ 2 olivares wheel 4 Apr 19 08:46 .org.chromium.Chromium.nZXKvi/
-rw------- 1 olivares wheel 217 Apr 19 08:45 .xfsm-ICE-O5FS10
srwxr-xr-x 1 olivares wheel 0 Apr 16 14:14
OSL_PIPE_1001_SingleOfficeIPC_749a372921d46a7f4f5b5830cf8f4a2=
srwxrwxrwx 1 olivares wheel 0 Apr 19 08:45 dbus-2iq1roUF1X=
srwxrwxrwx 1 olivares wheel 0 Apr 19 08:45 dbus-liGTAm3Uq9=
drwxr-xr-x 2 olivares wheel 2 Apr 19 09:59 hsperfdata_olivares/
drwx------ 2 olivares wheel 4 Apr 19 09:45 mozilla_olivares0/
drwxr-xr-x 3 olivares wheel 3 Apr 19 09:38 olivares/
drwx------ 2 olivares wheel 3 Apr 19 08:45 ssh-AS0nuFTMcEuw/
***@coolermaster:~ $

Thank you for helping

Best Regards,


Antonio
Antonio Olivares
4 years ago
Permalink
On Mon, Apr 19, 2021 at 10:02 AM Antonio Olivares
...
This problem has been fixed. Thanks to all FreeBSD users who helped.
Two problems remain one is shutdown, machine does not completely
shutdown and the itweb-javaws does not fully open *.jnlp files (Java
Web Start). But we shall keep trying to fix these.

Best Regards,


Antonio

Bruce Ferrell
4 years ago
Permalink
...
I fed this error message from your log into google:

Keyboard initialization failed. This could be a missing or incorrect setup of xkeyboard-config

And found this solution:

https://forums.freebsd.org/threads/xkeyboard-config-missing-or-incorrect-setup.34879/

Sorry for posting so many responses to my own thread. I apologize. I have fixed the problem, I reinstall xkbcomp and I also just deleted server-0.xkm. After reinstalling xkbcomp, I
sudo cd /tmp/server-0.xkm and I found 3 directory's from my original usr/home/mrfree directory. After deleting them all I then deleted server-0.xkm and now everything is back in
working order. Terribly sorry for the thread guys, hopefully it will help someone out one day
Pete Long
4 years ago
Permalink
Post by Bruce Ferrell
Sorry for posting so many responses to my own thread. I apologize. I have
fixed the problem, I reinstall xkbcomp and I also just deleted
server-0.xkm. After reinstalling xkbcomp, I sudo cd /tmp/server-0.xkm and
I found 3 directory's from my original usr/home/mrfree directory. After
deleting them all I then deleted server-0.xkm and now everything is back
in working order. Terribly sorry for the thread guys, hopefully it will
help someone out one day
Don't apologise. People like yourself have helped me numerous times by
coming back to the discussion and stating what worked.

I know I wasn't involved but I thought it worth mentioning.


Pete.
Bruce Ferrell
4 years ago
Permalink
...
Pete,


that wasn't me apologizing... it was from the link for the solution I found.

But, I've had the same problem in the past
Pete Long
4 years ago
Permalink
Post by Bruce Ferrell
Post by Bruce Ferrell
Sorry for posting so many responses to my own thread. I apologize. I have
[...]
Post by Bruce Ferrell
Pete,
that wasn't me apologizing... it was from the link for the solution I found.
But, I've had the same problem in the past
Now I'm apologising :)


Pete.
Bruce Ferrell
4 years ago
Permalink
Post by Pete Long
Post by Bruce Ferrell
Post by Bruce Ferrell
Sorry for posting so many responses to my own thread. I apologize. I have
[...]
Post by Bruce Ferrell
Pete,
that wasn't me apologizing... it was from the link for the solution I found.
But, I've had the same problem in the past
Now I'm apologising :)
Pete.
None needed!  LOL
Continue reading on narkive:
Loading...