Moderator

caprea
Information about your hardware would be helpful, especially if you have a nvidia-card and then which driver you use for it.
Maybe post an inxi -zv7 from the live stick.
Can you reach from your live-stick the file /var/log/apt/history.log from the installed,broken system and post it here?
From the login-screen of C-A-F1 did you try startx ?
Forum Admin

anticapitalista
Hello again, another update.
I went with my hunch and put the antix 17 disk back in, loaded it up in safe mode (section “device”, driver “vesa”) and as before did not work. I did the following:
$ nano -w /etc/X11/xorg.conf
changed driver “vesa” to driver “mga”
saved with ctrl-X
$ startx
Aaaaand… X started up just fine, now I am in icewm and everything seems to be working fine.
so, I think this is an actual issue that could be fixed by the devs? If a matrox card is detected just use the mga driver and don’t enable any extraneous options.
Good on you for getting this working. I’ll have a look at mga driver option.
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
Member

simon
Hello again, another update.
I went with my hunch and put the antix 17 disk back in, loaded it up in safe mode (section “device”, driver “vesa”) and as before did not work. I did the following:
$ nano -w /etc/X11/xorg.conf
changed driver “vesa” to driver “mga”
saved with ctrl-X
$ startx
Aaaaand… X started up just fine, now I am in icewm and everything seems to be working fine.
so, I think this is an actual issue that could be fixed by the devs? If a matrox card is detected just use the mga driver and don’t enable any extraneous options.
@missTell to answer your question, I am doing this out of a feeling of nostalgia. This was the first computer I built back when I was a kid in 1998, I wanted to get it up and running again. As I mentioned in my first post I already do have a functioning EeePC running antix that works great. My intention was to do some word processing on the pentium II computer.
Member

stevesr0
Hi caprea,
I queried Steveo on the MXLinux forum and he said he would check if the version he used from Buster is patched.
I just read about the bug and it seemed that if is based on the setuid setting allowing someone to obtain root privileges.
It was said that if I am using a login manager (which I am) instead of using startx (for example), then I could use the chmod command to disable the access to root. I imagine this would be necessary with all three files (xserver-xorg-core, xserver-xorg-common and xserver-xorg-legacy.
So instead of changing the version, I could try that while waiting to hear from Stevo, yes (or no)?
** I queried the current permissions of the xserver files and got the following result:
$ ls -l /usr/lib/xorg/Xorg*
-rwxr-xr-x 1 root root 2423624 Jun 14 14:23 /usr/lib/xorg/Xorg
-rwsr-sr-x 1 root root 10576 Jun 14 14:23 /usr/lib/xorg/Xorg.wrap
Three questions:
(1) What is the meaning of “/usr/lib/xorg/Xorg.wrap” being outlined in RED (in LX Terminal)
(2) The permissions for Xorg.wrap include -sr-. If I don’t want that to be allowed, all I need to do is to run chmod 0755 (or would it require chmod u-s) for those files?
(3) If Stevo’s version is NOT patched and I switch from 2:1.19.6 to 2:1.19.2 (the patched antix version) is that likely to cause any other problems?
Thanks in advance.
stevesr0
stevesr0
-
This reply was modified 4 years, 5 months ago by stevesr0.
Member

panoslia
The X GUI shouldn’t be run as the root operator, so try using startx as a normal user.
Neither as root and as user dont load gui
Did you install any apps between the first time you booted after installing antiX to hard disk and the other times that it doesn’t boot to a graphical environment?
yes i install in between other apps.
yesterday i install first time antix. today in the morning i opened normal and i install apps that i wanted and after i shutdown the netbook, because i have to go.
after that i return to home i opened and from then i can’t load graphical environment.
Member

fatmac
The X GUI shouldn’t be run as the root operator, so try using startx as a normal user.
Member

panoslia
Hello
i install antix and in first time all was goos, but in restart i can’t enter in desktop only in non-gui intergace.
Login as root and i try “startx” but nothing happened.
Please an help to enter automatically in desktop mode
thanks
Member

delix02
I’m installing 17.2 from the core .iso and trying to build a X system from there.
Actually, I get the X server and icewm running as root but NOT as the normal user.
The Xorg log end then with the error message
“AddScreen/ScreenInit failed for driver 0 ”
in the web I found several solutions for this problem, however, all of them involved systemd…..
So, please let me know how I can get the xserver starting with the sysv of antiX.
Thx !
-
This topic was modified 4 years, 6 months ago by delix02.
Forum Admin

Dave
ssh into the machine as root and run
apt-get purge lightdm gdm kdm
Which should get rid of the most common login managers and leave you with the default slim login manager (which is the press f1 option).
If that only gets you to a text login chances are slim is not instead or setup funny from installing the other login manager.
First Purge slim in case it has remaining buggered files
Apt-get purge slim
Then install
Apt-get -f install slim
Alternatively from the command line you could run
startx /usr/local/bin/desktop-session space-icewm
To get one of the default desktops.
From there you can select the one you want from the desktops menu and then drop space-icewm from the command or change space-icewm to the variant you would like.
Computers are like air conditioners. They work fine until you start opening Windows. ~Author Unknown
Member

stevesr0
I am also experiencing a long boot time (5 minutes)on one of my computers with 17.1 (vs 24 seconds with 16.1). I also see a tpm (trusted platform module) error. My UUIDs in fstab and by blkid are identical. I also have a black screen (?no backlight) for most of that time.
My boot option editing doesn’t seem to take properly. I tried eliminating quiet and splash options and used xorg=intel without any change.
Except, after editing and rebooting several times, now I seem to go only to a console login. Startx doesn’t work. There is a message about lacking an xauthority file.
When it was launching to a desktop, the system worked ok.
I have wacom digitizer on this computer. Version 16.1 didn’t apparently detect or load that, while 17.1 does, so I suspect that it may be related to the initialization of the wacom files. (The Xorg.log file goes from 68 seconds at one point while working on the serial wacom driver to 312-319 seconds before then starting on the wacom stylus.
Apparently, the OP’s computer doesn’t have a wacom digitizer…
Hope that suggests something.
Steve
Member

Ordinosor
Hi everybody,
Thanks a lot for your answers. First of all, I would like to say that I have been using antiX-core for two weeks and that my OS is very stable and very light. I am really satisfied and I don’t have any big issues. My OS is fully operational.
@andfree : You are right. We just need to add “needs_root-rights=yes” to resolve the issue of not being able to run startx without being root. It’s not necessary to edit “allowed_users=console”. Therefore, I have just edited my article and correct this mistake. Thank you.
That being said, I have noticed some secondary issues and in a few days, I will tell you what it is all about. But once again, the system is operational.
Have a nice evening,
Benoît
Member

andfree
Salut Benoît,
I’ve read your article, although I’m not that good in reading french.
Me too, I’m interested about building from the core iso, even from the net iso. The net iso is an even more minimal version, but without wifi connectivity by default. I have to install “ceni” and the firmware for my wifi adapter (“firmware-linux-free”) to get wifi work.
Either I build from core or net iso, I always meet the first problem you write about in your article: the problem about running “startx” as simple (non-root) user. I also solve it in the way you write in your article, too: I install xserver-xorg-legacy and add to /etc/X11/Xrapper.config the “needs_root_rights=yes” line (without spaces before & after the “=” symbol).
This is enough for me to run “startx” and there’s not seem to be a reason for me to edit the “allowed_users=console” line (without spaces before & after the “=” symbol, again) as “allowed_users=anybody”.
Thanks for sharing your experience.
Member

andfree
I like the idea of a minimal xorg installation. I gave it a try on a live usb. I installed the antiX-17.1-net version, updated & dist-upgraded.
I have installed only these packages for the moment:
xserver-xorg-core
xinit
xserver-xorg-legacy
icewm
xserver-xorg-input-synaptics (and the touchpad works)
xserver-xorg-input-evdev (and the keyboards works)
xserver-xorg-input-mouse (and the mouse works)
rxvt-unicode
palemoon-nonsse2
ceni
firmware-linux-free (and the wifi adapter works)
No Xauthority problems when running startx, after I’ve added the “needs_root_rights=yes” line to the Xrapper.config file.
-
This reply was modified 4 years, 12 months ago by andfree.
Moderator

BobC
Maybe this will help. I seem to recall an authority problem with startx. There are other recent posts also, Maybe search for startx and authority in the search box?
https://www.antixforum.com/forums/topic/build-icewm-system-from-core-17-1/
Member

Mr.Bean
Hi there,
I tried to install Antix net-install because my goal is to have an OS that is to be lightest and slimmest as possible. So after installing the net-install iso, I tried to follow this recommendation in order to achieve my goal:
https://git.devuan.org/dev1fanboy/Upgrade-Install-Devuan/wikis/minimal-xorg-install
or this:
https://gist.github.com/perveziqbal/7bb16e7a77206b8cfba4b1e7d17c2bfb
My packages that I have installed are:
Xserver-xorg-core,
xserver-xorg-video-nvidia,
xserver-xorg-input-mouse, xserver-xorg-input-kbd, xserver-xorg-input-libinput,
x11-server-utils
xinit and
fluxbox.
Then after that, I typed startx but I’ve got an error message:
xauth: file /home/MrBean/.Xauthority does not exist… etc… etc…
xinit: giving up
xinit: unable to connect to X server: connection refused
xinit: server error
Any clue or did I miss something ?
Thx!
-
This topic was modified 5 years ago by Mr.Bean.