Search Results for 'startx'

[Member ex_Koo]

Anonymous wrote:

who… is saying what?
Does lxappearance “work with i3wm?
If it does, it will continue to work ~~ the lxappearance package remains available in bullseye.

FYI, someone has “hinted at” the prospect of a new version
(with its gui skinned in gtk3, not that it will preview gtk3 themes nor inject custom gtk3 conf settings)
https://github.com/lxde-gtk3/lxappearance

re: Debian has a real hate for gksu

Maybe you can elaborate so that I can understand the intended meaning.

lxappearance works just fine with i3 & gaps and has always done so. I have never had much luck with built in theme programs from antiX MX nor even Arco running straight i3wm.
(Maybe built in is not the right word)

As for gksu thats why Debian removed it from the repo’s some time ago now, saying it was unsafe to use. Their is a forum post on Debian where people are saying there not happy it was removed.

And I do agree with the fact that gksu and sudo can be way over used at times, but the way antiX has it setup in the scripts it used in works just fine. I can remember back in my the early days of using Linux, when half my home folder was owned by root, just the over using root in the the wrong places mainly from the home directory.
The other day I had stick telling me that slim and lightdm are not save to use as well. I can easily live without them, I’m just as happy with tty xintirc & startx.

I have been testing Arco for awhile now if you don’t like typing your root password you won’t be happy with Arch base systems. By the way I like Arco just not as much as antiX the God of systems.

I would also like to see i3gaps included with the antiX installer, but because it is a fork of i3wm this will never happen. To me only on large screens i3-gaps is great but on small screens it is a waste of space like 14″ and less. Why I like gaps over i3wm, if you don’t want gaps you can turn them off.

I hope this makes sense I,m only telling my side of the story.

.

[Member marcelocripe]

Hello dear colleagues,

Unfortunately I will not be able to share all the experiences with the ISO “antiX-19-legacy-bet2_386-base.iso”, but when it is possible to register I will bring up this topic.

On 27-02-2021, I managed to revive another computer (Motherboard ECS 865PE-A rev 1.2 15-H70-01120, GeForce4 MX 440 AGP 8x Video Card, Pentium 4 Processor and 1GB DDR RAM) the ISO “antiX-19-legacy-bet2_386-base.iso”. I will try to summarize the test steps:

I had available a pendrive prepared with the windy that contained the ISOs antiX 19.3 full 32 bits, antiX 19.3 full 64 bits and antiX 19 Legacy Bet2 32 bits Base, the balenaEtcher Portable, another computer with Windows installed, another 2 GB pendrive and unfortunately I didn’t have a brush to do the cleaning.

https://ibb.co/qxBjK0t
https://ibb.co/GpGP19h

Ventoy was unable to initialize the three ISOs on the ECS 865PE-A rev 1.2 Motherboard.

On the Windows computer, I prepared the second pendrive with the balenaEtcher Portable and the ISO antiX 19.3 full 64 bits, initialized correctly and when the antiX options menu loaded, a message was displayed stating that the operating system is 64 bits and incompatible with the 32-bit device.

I prepared the second USB stick again with the balenaEtcher Portable and ISO antiX 19.3 full 32 bits, initialized correctly, made the selections in the antiX options menu, the video loaded normally and performed the installation process on the HD. When I restarted the computer, unfortunately I got the message from the image below:

https://ibb.co/xCDWZh0

I tried to use the “Boot Repair” tool, but it didn’t start in graphical mode, remaining what is shown in the image above.

I prepared the second USB stick again with the balenaEtcher Portable and the ISO “antiX-19-legacy-bet2_386-base.iso”, initialized correctly, made the selections in the antiX options menu, started in normal video mode, the video loaded normally and performed the installation process on the HD. When I restarted the computer, the video loaded normally.

Prior to the antiX 19 Legacy Bet2 32-bit Base update:

https://ibb.co/chv4WXh
https://ibb.co/k9B9L6s

After updating the antiX 19 Legacy Bet2 32 bit Base (I confirmed with “Y” on everything that was offered to be updated):

https://ibb.co/mSvhhzM

When I restarted the computer, unfortunately I got the message from the image below when trying to run the $ command
startx:

https://ibb.co/pb1K8Ds

Second attempt to install the ISO “antiX-19-legacy-bet2_386-base.iso”, initialized correctly, made the selections in the antiX options menu, started in secure video mode, the video loaded normally and performed the installation process in HD. When I restarted the computer, the video loaded normally.

Prior to the antiX 19 Legacy Bet2 32-bit Base update:

https://ibb.co/W51CQHp

After updating the antiX 19 Legacy Bet2 32 bit Base (this time I didn’t confirm everything that was offered to be updated, I answered “N”):

https://ibb.co/NSmVqdj
https://ibb.co/CBzFstD

I restarted the computer and the graphics mode loaded normally.

All the data I was able to copy from the terminal is in the file “Motherboard 865PE-A rev 1.2 15-H70-01120 with antiX 19 Legacy 32 bits 27-02-2021.txt”. I have included in this file, some texts translated by the English language internet translator to facilitate the localization of the steps for non-Portuguese speakers.

marcelocripe
(Original text in Brazilian Portuguese)

———-

Olá caros colegas,

Infelizmente eu não conseguirei compartilhar todas as experiências com a ISO “antiX-19-legacy-bet2_386-base.iso”, mas quando for possível registrar eu trarei neste tópico.

No dia 27-02-2021, eu consegui reviver mais um computador (Placa-mãe ECS 865PE-A rev 1.2 15-H70-01120, Placa de Vídeo GeForce4 MX 440 AGP 8x, Processador Pentium 4 e 1GB de Memória RAM DDR) com a ISO “antiX-19-legacy-bet2_386-base.iso”. Eu vou tentar resumir as etapas dos testes:

Eu tinha disponível um pendrive preparado com o ventoy que continha as ISOs antiX 19.3 full 32 bits, antiX 19.3 full 64 bits e antiX 19 Legacy Bet2 32 bits Base, o balenaEtcher Portátil, um outro computador com Windows instalado, um outro pendrive de 2 GB e infelizmente eu não tinha um pincel para fazer a limpeza.

https://ibb.co/qxBjK0t
https://ibb.co/GpGP19h

O ventoy não conseguiu inicializar as três ISOs na Placa-mãe ECS 865PE-A rev 1.2.

No computador com Windows, preparei o segundo pendrive com o balenaEtcher Portátil e a ISO antiX 19.3 full 64 bits, inicializou corretamente e quando o menu de opções do antiX carregou, foi exibido uma mensagem informando que o sistema operacional é 64 bits e incompatível com o dispositivo de 32 bits.

Preparei novamente o segundo pendrive com o balenaEtcher Portátil e a ISO antiX 19.3 full 32 bits, inicializou corretamente, fiz as seleções no menu de opções do antiX, o vídeo carregou normalmente e realizei o processo de instalação no HD. Quando reiniciei o computador, infelizmente obtive a mensagem da imagem abaixo:

https://ibb.co/xCDWZh0

Eu tentei utilizar a ferramenta “Reparador de Inicialização”/”Boot Repair”, mas não inicializou em modo gráfico, permanecendo o que é exibido na imagem acima.

Preparei novamente o segundo pendrive com o balenaEtcher Portátil e a ISO “antiX-19-legacy-bet2_386-base.iso”, inicializou corretamente, fiz as seleções no menu de opções do antiX, iniciei no modo de vídeo normal, o vídeo carregou normalmente e realizei o processo de instalação no HD. Quando reiniciei o computador, o vídeo carregou normalmente.

Antes da atualização do antiX 19 Legacy Bet2 32 bits Base:

https://ibb.co/chv4WXh
https://ibb.co/k9B9L6s

Após a atualização do antiX 19 Legacy Bet2 32 bits Base (eu confirmei com “Y” em tudo que foi oferecido para ser atualizado):

https://ibb.co/mSvhhzM

Quando reiniciei o computador, infelizmente obtive a mensagem da imagem abaixo ao tentar executar o comando $
startx:

https://ibb.co/pb1K8Ds

Segunda tentativa de instalação da ISO “antiX-19-legacy-bet2_386-base.iso”, inicializou corretamente, fiz as seleções no menu de opções do antiX, iniciei no modo de vídeo seguro, o vídeo carregou normalmente e realizei o processo de instalação no HD. Quando reiniciei o computador, o vídeo carregou normalmente.

Antes da atualização do antiX 19 Legacy Bet2 32 bits Base:

https://ibb.co/W51CQHp

Após a atualização do antiX 19 Legacy Bet2 32 bits Base (desta vez eu não confirmei tudo que foi oferecido para ser atualizado, respondi “N”):

https://ibb.co/NSmVqdj
https://ibb.co/CBzFstD

Reiniciei o computador e o modo gráfico carregou normalmente.

Todos os dados que eu consegui copiar do terminal estão no arquivo “Placa-mae 865PE-A rev 1.2 15-H70-01120 com o antiX 19 Legacy 32 bits 27-02-2021.txt”. Eu incluí neste arquivo, alguns textos traduzidos pelo tradutor da internet em idioma inglês para facilitar a localização das etapas para a pessoas não falantes do idioma português.

marcelocripe
(Texto original em Português do Brasil)

• This reply was modified 2 years, 2 months ago by christophe.
• This reply was modified 2 years, 2 months ago by christophe. Reason: removed code markings from around hyperlinks

Attachments:

1. Placa-mae-ECS-865PE-A-rev-1.2-15-H70-01120-com-o-antiX-19-Legacy-32-bits-27-02-2021.txt

[Member roland]

Thanks Caprea for that excellent response, ‘/usr/local/bin/ddm-mx -i nvidia’ ran through without a hitch, I chose the backports driver 340.108 as offered, then a ‘shutdown now’ finished with an invitation to type, I ran ‘startx’ which completed successfully, followed by a shutdown and cold reboot brought me to where I have not been with this build, a fully working nvidia graphics card.

Many thanks.

[Member roland]

Thanks for that response Caprea.

This morning it would boot after reporting the missing nvidia 340xx driver but halted at the invitation to login.

A manual attempt to run startx failed with xinit unable to connect to X server.

I was able to run a bash session to remove everything used by nividia as you suggested, and this finished ok having removed many modules.

However a cold reboot still terminates at the invitation to login with no attempt made to run startx. On this mainboard there is no graphics chipset and therefore without the nvidia card and drivers no graphics capability apart from bios.

When I login and try startx as superuser it fails as before, xinit unable to connect to X server.

Is there a bash method of installing the nvidia drivers, and if so would you guide me through it please? Or maybe suggest a more appropriate course of action?

Thanks for your time on this.

[Member Xecure]

Anonymous wrote:

You know that doing this will probably also bar your slim fork from officially getting into antiX?

Understood.

It’s open source.
With attention toward precluding user confusion regarding features found in (expected by) users of mainstream SLiM, I renamed the program.

It was just a joke. I have no power and no idea what the dev team’s preferences are. If someone wants to login as root they don’t need slim. They can kill slim and stop the service as root and then directly startx as root. I also agree that disabling normal root login will avoid unnecessary problems, as antiX (how I see it) is intended to be used with a normal user account.
Sorry if it looked I was implying something else. You know I am just another user here, who knows much less than everybody else.

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Member LLAP28]

Entered startx and got the following:

Attachments:

1. 

   LTP4-scaled.jpg
   

2. 

   LTP5-scaled.jpg
   

[Member Xecure]

See what happens when you do
startx

• This reply was modified 2 years, 3 months ago by Xecure.

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Anonymous]

Unfortunately I cannot get startX to run

“sudo startx”

the commandname is startx, all lowercase
and (I’m guessing, untested) the xserver can only be launched by root//sudo

After you have it right, save it to ~/.screenlayout/default.sh

Trying to understand this instruction, I explored the arandr gui and discovered
Layout }} SaveAs

ha! I had never noticed this feature. I had been accustomed to using the “unxrandr” command and manually copy/pasting…

Good afternoon, I am looking for an adequate solution for setting up vertically aligned monitors.

As I have found with other distros there does not appear to be an out-the-box display settings that works 100%. At best I have a choice of either having the wrong primary display or moving my mouse down to get the cursor to the above screen.

I did find a solution on youtube and that was perfect for about six months. However I recently tried reinstalling antix a couple of times and both times the configuration settings fail.

On starting antix it boots straight into terminal and on closing down there is a failing error… X display manager: slim not running (/var/run/slim.lock not found) stopping X display manager: slim

Ironically the youtuber states something along the lines that if anyone has similar issues they should type startX and debugging will show the syntax errors. Unfortunately I cannot get startX to run, but figure it must be something I’ve done as this was working previously without the fund and games.

Below is my config file. I hope my mistakes will be glaringly obvious to someone with more experience. Appreciate the help.

Section “Monitor”
### Monitor One (Top) Identifier typically HDMI-0, DisplayPort-0, DP-1 or VGA
Identifier “DP-4”

### Setting Resolution and Modes
## Modeline is usually not required, but you can force resolution with it
# Modeline “1920×1080” 172.80 1920 2040 2248 2576 1080 1081 1084 1118
Option “PreferredMode” “1920×1080”
Option “TargetRefresh” “60”

### Positioning the Monitor – typically “LeftOf or RightOf or Above or Below” “DisplayPort-0”
## Basic
Option “Above” “DP-3”
## Advanced
Option “Position” “0 1080”

Section “Monitor”
### Monitor Two (Bottom) Identifier typically HDMI-0, DisplayPort-0, DP-1 or VGA
Identifier “DP-3”

### Setting Resolution and Modes
## Modeline is usually not required, but you can force resolution with it
Modeline “1920×1080” 172.80 1920 2040 2248 2576 1080 1081 1084 1118
Option “PreferredMode” “1920×1080”
Option “TargetRefresh” “60”

### Positioning the Monitor
## Basic
Option “LeftOf or RightOf or Above or Below” “DisplayPort-0”

## Advanced
Option “Position” “0 0”

EndSection

I’m trying to give some life to an old ARMADA M700 installing antiX 19.2 base.
I created a CD from the iso that works perfectly on modern HW, but on the ARMADA
startx fails with the message :
Screens found, but none have a usable configuration
I’ tried tinkering with xorg.conf but I just do not have the required knowledge…
Hope someone can help…thanks in advance

btw: I know trying to revive such an old machine is nonsense, but (for me)
it is a lot of fun, and antiX is perfect for this task…

[Moderator Brian Masinick]

@Seaken64: If it’s only for you and you are familiar with startx then go for it.

I suggested using a login manager for the sake of other people; if you are more comfortable with startx and can show others how to login with your approach then do it.

I used the same thing with my very first Slackware distro and it was fast fun and efficient.

--
Brian Masinick

[Member seaken64]

Great stuff everyone! This is exactly what I need. You are helping me (and future antiX explorers) learn how to find the information I need to make better decisions about my own setup.

I am not actually sure that my goal of using startx is the correct approach. But I assumed it was going to be possible to make such a choice in antiX by modifying the scripts and config files. I first started learning Linux with Slackware and Vector. With those systems I always typed startx to go into the GUI. I’ve always liked that approach. Sometimes I just want to stay in the console and don’t want to start the X windows GUI. I like that approach instead of the automatic GUI login and then having to switch to a console on another tty. But that doesn’t mean I am right about it. It’s just what I was used to.

The other thought I had about this is that I am working with some very limited machines. I didn’t want to use the extra ram for a login manager if it is not needed. But I may go ahead and adjust my thinking on this and go ahead and run the login manager if that will lead to a more functional login/logout procedure.

Along the way I am learning about sessions. I am questioning the PAM idea as a single user on a single machine. But I get that user security is a good idea. I just am not sure I need all the security on my own machine with me being the only user. But I will continue to study these ideas and how they affect the choices we make when setting up an antiX machine.

Thank you all for your input. I am reading each and every link and search suggestion you all have made. It is enlightening and I think I may be able to grasp this process of “spinning” or creating my own Linux from an antiX CORE.

Seaken64

• This reply was modified 2 years, 4 months ago by seaken64.

[Moderator Brian Masinick]

I agree with skidoo that including at least a small login manager is a more useful choice than using only startx.

On one hand, you can insert a startx command into your login script and even conditionally code for whether or not a graphical user environment is present, but then you have to maintain that code and modify it if anything changes in the future. The memory footprint savings is not that significant, though there may be a small savings.

On the other hand, if you use slim or another login manager, you can select any different window manager, should you decide to include one, or someone else using your setup wants to experiment, it is a more familiar, flexible way. There are multiple desktop managers available, and simply using the current desktop will minimize coding changes if done right. If you have to code anything at all that points to a window or desktop, make sure to use either variables or parameters to simplify any changes, whether anticipated or not.

• This reply was modified 2 years, 4 months ago by Brian Masinick. Reason: login manager

--
Brian Masinick

[Anonymous]

> I’d like to stay with startx instead of SLiM

In a contemporary desktop linux setting… the absence of a PAM session is gonna leave ya wanting.

If not SLiM, consider at least using “nodm” (130kb package).
Here’s the nodm README page: https://sources.debian.org/src/nodm/0.13-5/README.md/

[Member seaken64]

I made a temporary fix for the Logout. I changed the command in the Preferences file to “pkill icewm”. This returns me to the default main menu entry instead of having the 6 panel logout screen come up. When I click on Logout it exits IceWM and leaves me at the console (with the weird VERY light foggy text where I can use clear to set if back to normal). I can then enter sudo reboot if I want to.

This is better than getting nothing from the desktop-session-exit panel. With that panel I cannot Logout, only reboot or shutdown. So my solution at least allows me to logout.

I will keep looking for a solution. I would like to keep the antiX six panel exit menu. I just need to figure out how to activate the Logout selection.

Anyone know how to run a logout command from that desktop-session-exit panel? I’d like to stay with startx instead of Slim.

Seaken64