Skip to main content ↑ ↓
Topic: openrc scambled (Read 4530 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Re: openrc scambled

Reply #15 –
https://bbs.archlinux.org/viewtopic.php?id=125484

xf86VTActivate() and VT_ACTIVATE can be found in xorg-server, but aren't in openrc or util-linux (agetty), chvt isn't in any of these. So I guess that xorg-server should be starting up and doing the switch to tty7, but for some reason it won't in this case.  ???

Re: openrc scambled

Reply #16 –
The difference on the other PC was this file :
/etc/X11/Xwrapper.config
# Xorg.wrap configuation file
needs_root_rights = yes

That means X runs as root, even though it was started the same way.
https://wiki.archlinux.org/index.php/Xorg#Rootless_Xorg
I'm guessing running rootless the IOCTL to change tty fails for permission issues, but it works in the desktop rootless using CTRL ALT F* so it might be a case of  not having those permissions just at that point? And apparently GDM can run Gnome rootless so this must be possible to fix  ;D

Re: openrc scambled

Reply #17 –
Quote from: ####### – on
The difference on the other PC was this file :
/etc/X11/Xwrapper.config
# Xorg.wrap configuation file
needs_root_rights = yes

That means X runs as root, even though it was started the same way.
https://wiki.archlinux.org/index.php/Xorg#Rootless_Xorg
I'm guessing running rootless the IOCTL to change tty fails for permission issues, but it works in the desktop rootless using CTRL ALT F* so it might be a case of  not having those permissions just at that point? And apparently GDM can run Gnome rootless so this must be possible to fix  ;D

Interesting to see that was the cause. Here is some stuff that might help:
https://wiki.gentoo.org/wiki/Non_root_Xorg

For example your user should be part of the video group it says.
Chris Cromer

Re: openrc scambled

Reply #18 –
Thanks, another problem unscambled (and that was nothing to do with openrc) !  ;D
$ sudo usermod -a -G video $USER
And commented that other file. That fixed it, now it switches while rootless.

It also explains why Xorg terminated with this error, there must have been some video / graphics failure stopping things.
These errors were in Xorg.0.log.old, as Xorg.0.log had messages only from the new working session that started after I hit ALT F7.

[    41.443] (EE) Screen(s) found, but none have a usable configuration.
[    41.443] (EE)
Fatal server error:
[    41.443] (EE) no screens found(EE)
[    41.443] (EE)
Please consult the The X.Org Foundation support
         at http://wiki.x.org
 for help.
[    41.444] (EE) Please also check the log file at "/home/me/.local/share/xorg/Xorg.0.log" for additional information.
[    41.444] (EE)
[    41.510] (EE) Server terminated with error (1). Closing log file.

Re: openrc scambled

Reply #19 –
Quote from: Chris Cromer – on
Your problem is that you are using 2 network managers at the same time, so naturally they conflict. You have to choose between dhcpcd and netifrc, you can't use both.


thanks.  I never thought of dhcpcd as a network manager, but that  might be an apt description.  If doesn't bring up and take down  network controllers or am i wrong?

I thought that netifrc calls dhcpcd ... it is should if it is listening to its config file.

Thjaanks for the help!!

Re: openrc scambled

Reply #20 –
Quote from: mrbrklyn – on

thanks.  I never thought of dhcpcd as a network manager, but that  might be an apt description.  If doesn't bring up and take down  network controllers or am i wrong?

I thought that netifrc calls dhcpcd ... it is should if it is listening to its config file.

Thjaanks for the help!!
Netifrc runs a dhcp software(dhcpcd,  dhclient, etc) as a program at the moment it needs to resolve dhcp. However you have dhcpcd  running as a daemon, essentially that makes dhcpcd manage the network connections to assign dhcp to all the network interfaces. So this makes netifrc and dhdcpd daemon conflict since both are trying to handle dhcp.
Chris Cromer

Re: openrc scambled

Reply #21 –
Quote from: Chris Cromer – on
Netifrc runs a dhcp software(dhcpcd,  dhclient, etc) as a program at the moment it needs to resolve dhcp. However you have dhcpcd  running as a daemon, essentially that makes dhcpcd manage the network connections to assign dhcp to all the network interfaces. So this makes netifrc and dhdcpd daemon conflict since both are trying to handle dhcp.

interesting.  Why would I do that?  It seems like silly question, but it didn't likely happen by accident.  I wonder what caused me to do that.  Thats for the insite!