However, none of these is actually the X server, and although xinit starts the server, the server executable often has the setuid bit set, meaning even though xinit has a non-privileged UID, X will still run as root. You could also try dm, since display managers usually have this in their name ( gdm, etc). Recently Linux distributions started to switching to rootless/SUIDless Xorg binary, so the X. In the past Xorg used to run as root, and the /usr/bin/Xorg binary had SUID bit set, so there was no problem with permissions whatsoever. I have also tried 2.6.15-no3, which worked fine for me before (I re-installed my system). To run X, you need read/write access to a tty device you want the X to run on (in your case tty7 ). pstree -ph -u pi (while the X session is running) output may also be informative. Also, when I start gdm (/etc/init.d/xdm start) as root, I get the same kernel panic. Is anything getting started Could you have a look through the output from startx, /.xsession-errors and /var/log/Xorg.0.log and see if something fails. If nothing turns up, try ps -fA | grep X this one involves more clutter.įinally, if there is no process with capital X in its name, try x you may at least find commands used to control it, such as startx or xinit. If I run startx as root, everything works fine, with direct rendering etc. If this is 0, then the process is running root. This removes the column headers, but the UID is the numerical one on the left. Since it almost certainly at least has capital X in it (e.g., Xorg, X11), an alternative is to filter through grep: ps -o uid,comm -A | grep X This presumes that the executable is called X - if there's no such process, you will have to target something else. Will give you information for all the X servers that are running (there can be more than one). While it is not strictly necessary, since elogind can be started upon receiving an event over dbus, it will clash with other services that depend on elogind, like fwupd, resulting in OpenRC trying to start already started elogind and thus failing to do so.There are a few ways to output the user ID (UID) with ps a simple one is with -f: ps -fC X The elogind users are recommended to add elogind to the boot runlevel.
#Startx only runs as root driver
If either the systemd or elogind USE flag is enabled on x11-base/xorg-server together with the suid USE flag, instead of installing with suid enabled, x11-base/xorg-server will be installed with suid-wrapper, which will only preserve suid if the graphics driver in use really requires root.
#Startx only runs as root update
Users of systemd profile and users of desktop profiles (both systemd and non-systemd ones) will already have a logind interface provided users of OpenRC with default profile will be required to globally enable the elogind USE flag and update the system with emerge -ND It is also required to re-login after elogind has been enabled, to activate it. Add group (I could solve that only doing this) tty requid that your need belong tty group, so type this with sudo or root sudo usermod -aG tty yourname But I got error like ' 4343.663 (EE) open /dev/fb0: Permission denied' /dev/fb0s group is video, so run sudo usermod -aG video yourname to add youuser could access /dev/fb0.
0 kommentar(er)
