You are not logged in.
Pages: 1
I Installed arch about a month or two ago, and enjoy it a lot. Only problem is that I'm getting weird error messages whenever I'm start a new fish instance, wether if because I'm opening a new window or launching a new shell in an existing window. Here is the error in question:
/usr/lib/Xorg.wrap: Only console users are allowed to run the X server
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error
Couldn't get a file descriptor referring to the console.After that, I get the normal fish greeter, and the shell starts normally.
I'm suspecting there are actually two different errors, a first one relating to Xorg, and another one that looks like a xdg-open error.
I've tried looking in my fish.conf, but nothing in there looks like it's trying to touch the X server.
This error only happens when fish launches, any other shell works fine.
I'm using lightdm with the lightdm-mini-greeter, which launches xmonad through the desktop file in /usr/share/xsessions. I've also tried logging from another TTY, and launching X manually using startx, with the exact same results
Which log/config files could I post which would be useful? At this point I've tried everything, I've found online, which pretty much limits itself to "add a line in /etc/X11/Xwrapper.config that says allowed_users = anybody". Unfortunately, that just prevents Xorg from launching correctly, it starts up without reading my configs, then gets killed, then starts again, in an infinite loop.
Last edited by Therk (2023-02-02 16:48:30)
Offline
So you are incorrectly starting X from your fish profile or other startup files. Remove that. If you want help doing so, post your fish configs / profile / etc.
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
By searching a bit more, I found /conf.d in my fish config directory, which sourced $OMF_PATH/init.fish. In that script I found a simple, unambiguous startx command. Removing that line removed both the errors! Kinda frustrated it was such an easy fix after weeks of trying to find the issue.
Last edited by Therk (2023-02-02 16:48:46)
Offline
So you solved one problem that came from OMF. Why stop there, remove the who OMF virus.
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
I don't understand what you mean?
Offline
OMZ/OMF is known for causing all sorts of horrific problems that are often very hard to track down. It is dreadfully bad software and should not be used by anyone.
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
The OM set of helper scripts (.. they didn't stop at breaking zsh?
) don't really have a good standing with a lot of regulars here because they constantly come up as being the source of all sorts of trouble due to a lack of care and a bunch of nonsensical assumptions they make.
Offline
Oh I didn't even know you could use fish without OMF, I'll look into it. It hasn't cause me much problems so far tho, but who knows this may become an issue some day.
Offline
Pages: 1