Search Results for 'startx'

[Member olsztyn]

andyprough wrote:

Did you do the thing that Christophe said? You have to do it for startx to work:

Edit your /etc/X11/Xwrapper.config.
Add at the bottom of the file:
needs_root_rights=yes

Yes. I did.

Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters

[Member andyprough]

Did you do the thing that Christophe said? You have to do it for startx to work:

Edit your /etc/X11/Xwrapper.config.
Add at the bottom of the file:
needs_root_rights=yes

[Member olsztyn]

Just to report first setback:
startx does not work as expected. Fails with the following:

xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error

I have a feeling this might be related to Runit as init, but I hope it is not… Based on antiX 22 Runit Core.
Not sure how to proceed.
This is an example why I miss antiX SID Base (or about that) in SID antiX inventory of ISOs…

Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters

[Moderator christophe]

I like to make my core systems even more minimal than base, because I don’t think we an get any better than antiX (base/full) itself.
So, I don’t know if this is something that will help, but I’ll tell you what I do:
I run the apt update, then run:
sudo apt install xorg xserver-xorg-legacy xinit roxterm-gtk2 conky-legacy-all jwm volumeicon-alsa-legacy acpi pmount feh
(This gets the basics, a good minimal window manager, conky, terminal — just basics.)
Then add whatever programs you use.
Edit your /etc/X11/Xwrapper.config.
Add at the bottom of the file:
needs_root_rights=yes

Copy /etc/jwm/system.jwmrc to /home/demo/.jwmrc
(assuming you’re running live.)

You’ll have to edit it by hand, to add/remove/change it. It’s like the antiX base/full versions, but all in one file.
“man jwm” will be helpful here.
Run startx to start X at any point after you have installed the basics & have edited Xwrapper.conf.
I hope this helps, my friend. 🙂

• This reply was modified 5 months, 1 week ago by christophe.

confirmed antiX frugaler, since 2019

[Member techore]

Down with a bug the last week, pox on the person that brought it into work, but managed to get out of bed long enough to rework antix-core dwm respin. Closer to completion but a dozen or so items to remediate before publishing.

For kicks, I decided to see if the respin would install on a firewall appliance sitting on my project bench.

I discovered “x” under xorg provides window manager info!

inxi -v3xz

System:
  Kernel: 5.10.142-antix.2-amd64-smp arch: x86_64 bits: 64 compiler: gcc
    v: 10.2.1 Desktop: dwm v: 6.4 dm: startx
    Distro: antiX-22-runit_x64-core Grup Yorum 18 October 2022
    base: Debian GNU/Linux 11 (bullseye)
Machine:
  Type: Desktop Mobo: N/A model: QD-CMU01 serial: N/A
    BIOS: American Megatrends v: MCMU0202.V03 date: 07/20/2022
CPU:
  Info: quad core model: Intel Core i7-10610U bits: 64 type: MT MCP
    arch: skylake note: check rev: 1 cache: L1: 256 KiB L2: 1024 KiB L3: 8 MiB
  Speed (MHz): avg: 4819 high: 4897 min/max: 400/4900 cores: 1: 4801
    2: 4795 3: 4803 4: 4853 5: 4807 6: 4800 7: 4803 8: 4897 bogomips: 36799
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel driver: i915 v: kernel ports: active: HDMI-A-1
    empty: DP-1,HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:9bcc
  Display: server: X.Org v: 1.20.11 driver: X: loaded: modesetting
    unloaded: fbdev,vesa gpu: i915 resolution: 1280x1024~60Hz
  Message: Unable to show GL data. Required tool glxinfo missing.
Network:
  Device-1: Intel Ethernet I225-V driver: igc v: kernel pcie: speed: 5 GT/s
    lanes: 1 port: N/A bus-ID: 02:00.0 chip-ID: 8086:15f3
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-2: Intel Ethernet I225-V driver: igc v: kernel pcie: speed: 5 GT/s
    lanes: 1 port: N/A bus-ID: 03:00.0 chip-ID: 8086:15f3
  IF: eth1 state: down mac: <filter>
  Device-3: Intel Ethernet I225-V driver: igc v: kernel pcie: speed: 5 GT/s
    lanes: 1 port: N/A bus-ID: 04:00.0 chip-ID: 8086:15f3
  IF: eth2 state: down mac: <filter>
  Device-4: Intel Ethernet I225-V driver: igc v: kernel pcie: speed: 5 GT/s
    lanes: 1 port: N/A bus-ID: 05:00.0 chip-ID: 8086:15f3
  IF: eth3 state: down mac: <filter>
  Device-5: Qualcomm Atheros AR9485 Wireless Network Adapter
    vendor: Lite-On driver: ath9k v: kernel pcie: speed: 2.5 GT/s lanes: 1
    bus-ID: 06:00.0 chip-ID: 168c:0032
  IF: wlan0 state: down mac: <filter>
  Device-6: Intel Ethernet I225-V driver: igc v: kernel pcie: speed: 5 GT/s
    lanes: 1 port: N/A bus-ID: 07:00.0 chip-ID: 8086:15f3
  IF: eth4 state: down mac: <filter>
  Device-7: Intel Ethernet I225-V driver: igc v: kernel pcie: speed: 5 GT/s
    lanes: 1 port: N/A bus-ID: 08:00.0 chip-ID: 8086:15f3
  IF: eth5 state: down mac: <filter>
  Device-8: Intel Ethernet I225-V driver: igc v: kernel pcie: speed: 5 GT/s
    lanes: 1 port: N/A bus-ID: 09:00.0 chip-ID: 8086:15f3
  IF: eth6 state: down mac: <filter>
  Device-9: Intel Ethernet I225-V driver: igc v: kernel pcie: speed: 5 GT/s
    lanes: 1 port: N/A bus-ID: 0a:00.0 chip-ID: 8086:15f3
  IF: eth7 state: down mac: <filter>
Drives:
  Local Storage: total: 476.94 GiB used: 5.01 GiB (1.1%)
Info:
  Processes: 193 Uptime: 4m Memory: 15.52 GiB used: 521.1 MiB (3.3%)
  Init: runit v: N/A runlevel: 2 Compilers: gcc: 10.2.1 alt: 10 Packages:
  apt: 1114 Shell: fish v: 3.1.2 running-in: kitty inxi: 3.3.19

Once I recover from this bug, I hope to complete the respin, use it on my daily driver for a couple weeks, then publish.

I want to thank @anticapitalista and the others for this amazing Linux distribution. Especially, the antix-core runit version. Love it!

• This reply was modified 5 months, 2 weeks ago by techore.
• This reply was modified 5 months, 2 weeks ago by techore.

[Member stevesr0]

UPDATE:
No problem after reboot. Of course, my system is different, since I am running Sid not testing and using startx and Openbox. I don’t know your hardware -mine is an oldish Fujitsu Lifebook from 2006.

Happy to compare any packages you think might be causing problem with 5.10 kernels.

———————————————————————————–

I am running Sid with 5.10.142 antiX kernel. Last full-upgrade today. No problems that I am aware of. I will report back after rebooting. N.B. I am using startx not slimski.

stevesr0

• This reply was modified 7 months, 1 week ago by stevesr0.

Title: Problems after updating antiX 19.3

Hello.

I know that I don’t usually participate much in the antiX forum, as I would certainly have difficulties to explain my doubts or difficulties here. However, I consult the tutorials created by PPC in the area in Portuguese frequently.
Usually my doubts or difficulties are answered with tutorials or in Whatsapp and Telegram groups (antiX Linux in Portuguese).
Today I asked for help in the groups, regarding the problems that occurred after the antiX 19.3 update, marcelocripe promptly answered and helped me, including creating this topic on the forum.
I will detail everything that marcelocripe and I did (via video conference).

1 – Yesterday I updated antiX 19.3 and used it normally until I turned off the computer.

2 – Today I turned on the computer to start antiX 19.3 which is installed on the hard drive.

3 – I entered my username and password.

4 – The toolbar and arrow do not appear on the screen.

5 – marcelocripe instructed me to press Ctrl+Esc to display the antiX menu or Ctrl+Alt+Backspace to bring up the login screen, but nothing happened.

6 – marcelocripe instructed me to press Ctrl+Alt+F1 to display the black screen. He noted that it was still necessary to enter the username and password, he told me that maybe SLIM is having some kind of problem.

7 – After I applied the command “startx”, the screen appeared with the toolbar, but the arrow did not appear on the screen. The Ctrl+Esc and Ctrl+Alt+F1 key combinations don’t work anymore, the Num Lock key doesn’t turn on or off the keyboard’s signal light, the Ctrl+Alt+Backspace key combination didn’t work either. marcelocripe noticed that the system monitor is orange and at very high levels, according to him, this demonstrates high levels of processing. I had to turn off the computer by pressing the power button on the computer.

8 – After the computer turned on again, marcelocripe instructed me to press the Ctrl+Alt+F1 keys to display the black screen and apply the commands “sudo apt update” and “sudo apt upgade”. I re-applied the command “startx” and the same situation happened that I described in item number 7.

That’s when marcelocripe said something to me that made my stomach flutter, “we’re going to need to ask for help on the antiX forum”. When he told me this, I soon realized that the problem must be too complicated for us to have to ask for help here.

I ask for the help of people who have more experience than marcelocripe, certainly your help will help marcelocripe learn to solve this type of problem, because I’m not a computer technician, I’m just a computer user.

marcelocripe told me that the other option would be to install antiX again, but this time we could install antiX 21. I talked to marcelocripe about the options available for a quick solution to the problem, but I thought the following, antiX never gave problem before for me, on the contrary, antiX has always been the best solution for me, my problem can serve to help solve other people’s problem, so I prefer to wait for the help that I believe I will receive from the forum.

Right now I’m starting with the LiveUSB that marcelocripe told me to keep for use in an emergency situation.

Thank you.

Vania.

Note: marcelocripe, thank you very much for your patience and readiness in always wanting to help us.

Título: Problemas após a atualização do antiX 19.3

Olá.

Eu sei que eu não costumo participar muito do fórum do antiX, pois certamente eu teria dificuldades para explicar as minhas dúvidas ou dificuldades aqui. Contudo, eu consulto os tutoriais criados pelo PPC na área em Português frequentemente.
Normalmente as minhas dúvidas ou dificuldades são respondidas com os tutoriais ou nos grupos de Whatsapp e Telegram (antiX Linux em Português).
Hoje eu pedi ajuda nos grupos, referente aos problemas que ocorreram após a atualização do antiX 19.3, o marcelocripe prontamente me atendeu e me ajudou, inclusive a criar este tópico no fórum.
Eu vou detalhar tudo o que fizemos o marcelocripe e eu (por vídeo conferência).

1 – Ontem eu atualizei o antiX 19.3 e utilizei normalmente até desligar o computador.

2 – Hoje eu liguei o computador para iniciar o antiX 19.3 que está instalado no disco rígido.

3 – Digitei o meu nome de usuário e a minha senha.

4 – A barra de ferramentas e a seta não aparecem na tela.

5 – O marcelocripe me instruiu a pressionar as teclas Ctrl+Esc para exibir o menu do antiX ou Ctrl+Alt+Backspace para aparecer a tela de início de sessão, mas nada aconteceu.

6 – O marcelocripe me instruiu a pressionar as teclas Ctrl+Alt+F1 para exibir a tela preta. Ele observou que ainda era necessário entrar com o nome de usário e a senha, ele me disse que talvez o SLIM esteja com algum tipo de problema.

7 – Após eu aplicar o comando “startx”, a tela apareceu com a barra de ferramentas, mas a seta não apareceu na tela. As combinações de teclas Ctrl+Esc e Ctrl+Alt+F1 não funcionam mais, a tecla Num Lock não acende ou apaga a luz de sinalização do teclado, a combinação de teclas Ctrl+Alt+Backspace também não funcionou. O marcelocripe percebeu que o monitor do sistema está com uma cor laranja e em níveis muito alto, segundo ele, isso demonstra altos níveis de processamento. Eu precisei desligar o computador pressionando o botão de ligar o computador.

8 – Após o computador ligar novamente, o marcelocripe me instruiu a pressionar as teclas Ctrl+Alt+F1 para exibir a tela preta e aplicar os comandos “sudo apt update” e “sudo apt upgade”. Eu apliquei novamente o comando “startx” e aconteceu a mesma situação que eu descrevi no item número 7.

Foi quando o marcelocripe me disse algo que me deu um frio no estomago, “nós vamos precisar pedir ajuda no fórum do antiX”. Quando ele me disse isso, eu logo percebi que o problema deve ser muito complicado para nós termos que pedir ajuda aqui.

Eu peço a ajuda das pessoas que possuem mais experiência que o marcelocripe, certamente a ajuda de vocês servirão para o marcelocripe aprender a resolver este tipo de problema, pois eu não sou técnia em computadores, eu sou apenas uma usuária de computador.

O marcelocripe me disse que a outra opção seria instalar novamente o antiX, mas que desta vez poderíamos instalar o antiX 21. Eu conversei com o marcelocripe sobre as opções disponíveis para a solução rápida do problema, mas eu pensei o seguinte, o antiX nunca deu problema antes para mim, ao contrário, o antiX sempre foi a melhor solução para mim, o meu problema pode servir para ajudar a resolver o problema de outras pessoas, então, eu prefiro aguardar a ajuda que acredito que irei receber do fórum.

Neste momento eu estou iniando com o LiveUSB que o marcelocripe me disse para guardar para utilziar em uma situação de emergência.

Muito obrigada.

Vania.

Observação: marcelocripe, muito obrigada por sua paciência e prontidão em sempre querer nos ajudar.

Attachments:

1. Ajuda-1.zip
2. Ajuda-2.zip

Hi!

I’ve been running the 4.9 kernel on antiX 19.5 without any issues. Today I tried installing the 5.10 kernel to see if there would be any performance improvements. Got the following message during install:

Setting up linux-image-5.10.137-antix.1-amd64-smp (5.10.137-antix.1-amd64-smp-1) …
Warning: Unable to find an initial ram disk that I know how to handle.
Will not try to make an initrd.
Error! Bad return status for module build on kernel: 5.10.137-antix.1-amd64-smp (x86_64)
Consult /var/lib/dkms/ndiswrapper/1.61/build/make.log for more information.
Error! Bad return status for module build on kernel: 5.10.137-antix.1-amd64-smp (x86_64)
Consult /var/lib/dkms/nvidia-legacy-340xx/340.108/build/make.log for more information.

When starting with the 5.10 kernel X fails to load and I’m stuck on tty1, issuing startx fails. Anyone got any clues?

the nvidia log file has over 3000 lines but near the top it has:

echo >&2 ” ERROR: Kernel configuration is invalid.”; \
echo >&2 ” include/generated/autoconf.h or include/config/auto.conf are missing.”;\
echo >&2 ” Run ‘make oldconfig && make prepare’ on kernel src to fix it.”; \

[Member stevesr0]

Update.

I can confirm that (in my hands <g>), using a live usb (net install) running Sid repos doesn’t launch X.

Today, I used the “regular” antiX-21 net install live usb and was able to launch X. But after updating, I no longer was able to. Then I tried the sysvinit antiX-21 Sid iso posted by anticapitalista on 22 January and that failed in exactly the same way as the stable version that I upgraded to Sid repos.

Running startx, both give an error message about not finding modules.builtin.modinfo in /usr/lib/modules/.

If anyone is successfully running a liveUSB of antiX-21 using Sid repos and able to launch X, please let me know <g>.

I shall have to regroup at this point and consider trying with a “fuller” iso…

Thanks to all who are reading this (especially if they offer advice <g>).

stevesr0

[Member stevesr0]

Update:

Again, I was able to use the live usb of sysvinit antiX-21 netinstall to launch X windows using stable repositories via startx with openbox. However, again after switching to the Sid repositories, X fails to launch.

I suspect that during the full-upgrade to Sid, the modules.builtin.modinfo are removed, because I think they were present when running the stable repositories.

So, I will repeat a fresh boot and see if I can confirm this.

If this is the case, I am suspicious that it is somehow due to the version of kmod, because similar bugs have been reported recently.

Any wise words of advice always appreciated.

stevesr0

[Anonymous]

Hello steve,

if you want to start your installations with startx, then I assume that your USER also has a .xinitrc in his /home, which has this entry among others:
exec openbox-session

Others are mandatory commented out?

Finally, I don’t think it’s a good idea to run startx as root!

[Member stevesr0]

Hi olsztyn,

Thanks for responding.

You are probably correct about remastering being easier.

However, I am unfamiliar with remastering – and even the varied persistence options.

So, as a first step, I am trying to see if I can get a systemd, elogind,libelogind0 and dbus free environment that I can install the set of Pipewire packages that anticapitalista created and posted (see his post on the What types of dependencies? thread).

I believe I am very close to achieving the install (ta-da). Then, I will see if it doesn’t works and gives clues as to what it needs.

I am currently stuck trying to launch an X session using Openbox as a window manager. This is the same as my installed Sid, which I use as a comparator.

Where I am stuck is when I issue a startx command (as root), I get an error message “permission denied”.
I have edited the Xwrapper.config to allow all users (the default was anyone on the console).

So, I am not sure if (a) a reboot would solve things (if I had persistence <g>), (b) a logout and relogin will work (without losing the current nonpersistent setup) or (c) there is something wrong with my setup.

I (and my live antiX) will sleep on it tonight.

Any thoughts welcomed to start X, or to run pipewire without launching a GUI (X or Wayland).

stevesr0

[Member stevesr0]

Hi Xaver,

Thanks for your post.

I am runnning a Sid (hard disk install) and am running Pipewire as a sound server in order to be able to switch inputs and outputs easily. Working well, but does require libelogind0 (although not IIRC elogind, maybe because I have seatd installed).

Mine is a somewhat minimalist system built from (IIRC) net and I use OpenBox and startx. My init is sysvinit.

I plan to follow your lead in building a minimalistic live usb, that I can try to get Pipewire running without libelongind0.

I have read that some people running nonsystemd distros have found ways of running Pipewire; but I am not sure whether they have run “pure” nonsystemd versions with seatd or other approach NOT involving elogind or libelogind0.

One particular aspect is whether the “dependency” PIpewire has on systemd/elogind is only for launching and stopping. Supposedly,if that is the case, environmental statements that set a default user run directory might allow Pipewire to work.

My first attempts will involve creating a dummy file for libelogind0 and elogind and setting the recommended environmental variable and seeing whether that works at all.

I will post a follow up with my results.

**N.B. I have started a thread “Pipewire without systemd”, so I will post there rather than hijack your thread.

As an aged noobie, I imagine my path forward will be rather slow and prolonged, so any input from others with a similar interest in runnning Pipewire without systemd or elogind are very welcome.

**N.B.2 As anticapitalista has emphasized in several posts, only Pipewire in the Sid and testing repositories is considered to be ready for routine use, not the versions in older repositories (stable, old stable).

stevesr0

• This reply was modified 9 months ago by stevesr0.

[Member andyprough]

andyprough wrote:

I’m wondering if seatd will resolve one thing for me. I removed slim/slimski, and have been logging into my window manager with a tty login script. That was giving me a frozon Xorg, but I read anti’s post about startx, and once I added ‘needs_root_rights=yes’ to /etc/X11/Xwrapper.conf then my xorg was working.

However, I think it’s supposed to be ideal to run xorg as a normal user instead of as root. I read that seatd will

Seat management takes care of mediating access to shared devices (graphics, input), without requiring the applications needing access to be root.

Does this mean that with seatd I will no longer need the ‘needs_root_rights=yes’ line?

Just curious.

Answering my own question – I did not realize when I posted the above question that ownership of the Xorg process is handed over to the user rather than staying with root, even though I’m using the ‘needs_root_rights=yes’ option. So this isn’t a problem that needs to be addressed by seatd from what I can tell.

[Member Xaver]

So far problems (1) and (3) have been solved:
(1) package ‘resolveconf’ was missing (see post #85326 and #85330)
(3) further runit-services are not needed (see post #85258)

Problem (2) still exists: The system freezes on wakeup after suspend (booted live from usb).

I have noticed, that there is a nosystemd1-version of lightdm. I have installed it and indeed, the belonging runit services are installed too.
Unfortunately with running lightdm service the system still freezes on wakeup after suspend.

Using the ligtdm runit service as blueprint I have created a runit service for lxdm as well.
It does work fine, but I do not notice any diffence compared to having no service. Freeze still happens.

Lightdm seems to need polkit for reboot and shutdown. From lxdm reboot and shutdown work fine. So if the refined settings of lightdm are not needed, lxdm is the better (and lighter) choice.

.xinitrc
I have checked, if login with .xinitrc would work better. Unfortunately I have failed to start the system this way.
The openbox-desktop is loaded and looks as it should, but no keyboard or mouse input is possible.
Could this hangup show a hint to the cause of the freeze on wakeup?
Would I need a runit service for startx/.xinitrc too?

• This reply was modified 10 months, 1 week ago by Xaver.