Search Results for 'startx'

[Member ext4]

ext4 wrote:

I have seen that in antiX 22 following files (drivers)
“xserver-xorg-video-sis671″
and
xserver-xorg-video-vesa”.
are present.

How can I activate them?
“startx xserver-xorg-video-sis671” respectively in the “xorg.conf”

No one has a tip?

Es kann nur e1nen geben!

[Member ext4]

Thanks for the tips.

I have seen that in antiX 22 following files (drivers)
“xserver-xorg-video-sis671″
and
xserver-xorg-video-vesa”.
are present.

How can I activate them?
“startx xserver-xorg-video-sis671” respectively in the “xorg.conf”

PPC wrote:

Edit: is your signature a quote of “Highlander”?

Yes it is. 😉

###

Vielen Dank für die Tipps.

Ich habe gesehen, dass in antiX 22 folgende Dateien (Treiber)
“xserver-xorg-video-sis671”
und
“xserver-xorg-video-vesa
vorhanden sind.

Wie kann ich diese aktivieren?
“startx xserver-xorg-video-sis671” bzw. in der “xorg.conf”

PPC wrote:

Edit: is your signature a quote of “Highlander”?

Ja ist es. 😉

• This reply was modified 1 week, 3 days ago by ext4.

Es kann nur e1nen geben!

[Moderator Brian Masinick]

Regarding “dispense with a Display Manager and login from tty1, and “startx”, this used to be the default method in the early days, and for quite a few years many Slackware configurations, even those with a graphical user environment would still default to a command line; I’m sure there are still specific builds that continue to use this approach. While those of us used to going directly into a GUI, only having to login, then specify a single command isn’t all that difficult; it’s handy if sometimes you WANT to start in the console and sometimes start in the GUI, but if it bothers you, it’s easy to overcome it by putting a startx command directly into the login shell or a super convenient alias command.

--
Brian Masinick

[Moderator christophe]

“I also prefer to dispense with a Display Manager [eg slimski], and login from tty1, and “startx”.”

Have you considered starting with antiX core or net, and building up from there?

confirmed antiX frugaler, since 2019

[Member blur13]

“I also prefer to dispense with a Display Manager [eg slimski], and login from tty1, and “startx”.”

How do you go about doing this? What are the benefits? I thought a DM was indispensable.

Hello. I have used Antix live in the past, but this is the first time I have installed it. My daily distro has been a mixture of Debian, Devuan and Void in recent years; I have used Void every day for a few years, but have been looking for a backup alternative to run on a second computer.

It has only been a few days, but so far so good. I hate the all Desktop Environments, and use Openbox alongside Lxterminal, Tint2, etc. I also prefer to dispense with a Display Manager [eg slimski], and login from tty1, and “startx”.

I chose the Runit option as I am familiar with it from Void. I am a minimalist at heart, and always try to remove packages and services that I don’t need. As Antix evolves, I will have to work out how to live with new versions; Void is a rolling distro.

jack@picamanic

• This topic was modified 3 weeks, 2 days ago by picamanic.

Icewm-session can start using a command startx icewm-session, but how rox-icewm session can be started?

• This topic was modified 1 month, 1 week ago by RJP.

[Member rab-bits]

To remove the permission problem I ran:

sudo vesa: Ignoring device with a bound kernel driver

But, then the vesa-driver made problems whan I ran startx:

[ 209.416] (II) LoadModule: “vesa”
[ 209.416] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[ 209.416] (II) Module vesa: vendor=”X.Org Foundation”
[ 209.416] compiled for 1.20.9, module version = 2.5.0
[ 209.416] Module class: X.Org Video Driver
[ 209.416] ABI class: X.Org Video Driver, version 24.1
[ 209.416] (II) VESA: driver for VESA chipsets: vesa
[ 209.416] (++) using VT number 1

[ 209.416] vesa: Ignoring device with a bound kernel driver
[ 209.416] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
[ 209.416] (EE) Screen 0 deleted because of no matching config section.
[ 209.416] (II) UnloadModule: “vesa”
[ 209.416] (EE) Device(s) detected, but none match those in the config file.
[ 209.416] (EE)
Fatal server error:

[Member synchron]

Yes! That was a great idea @anticapitalista

I removed the packages slimski and slimsky-themes-extra-antix
After that, the pc boots into console, but without autologin.
So i changed the /etc/inittab at this line inserting the autologin:
c1:2345:respawn:/sbin/agetty --autologin <username> --noclear 38400 tty1 linux
Now the login worked and the only thing was to start firefox.
For that i choosed a dirty way with the .bashrc
i added:

ffrunning="${ps -ef | grep firefox | wc -l}"
if [ $ffrunning -eq 1 ]; then
    startx ~/bin/startfirefox.sh
fi

The if is needed in case of logging into a second shell. I dont want firefox to start twice.

Thanks for the help.

@zblsv Do you know a way to “quit” an application that is started this way? alt+f4 is not working. So the only way to escape is to log into another console and kill the firefox. If my daughter manages this way, she is old enough to play with the unlocked system 😀

[Member synchron]

Hi, thanks for your answers.
But sadly they dont help me much.

I know how to start firefox in kioskmode pointing to a website.
Like i said and you can try it.

press ctrl+alt+F6 to go to a console
login with a user
execute the following two commands:

echo "firefox --kiosk http://antixforum.com" > /tmp/firefoxkiosk.sh
startx /tmp/firefoxkiosk.sh

And there it is. A Fullscreen Firefox showing the Forum.

@Xunzi_23 So you can see that i dont need a running Desktop to start firefox
@RJP I dont need to fake keyboardinput

• This reply was modified 2 months ago by synchron.

[Member synchron]

Thanks @PPC for your suggestion. But like i described i tried this solution via the “./desktop-session/startup” file and it ends up showing round about 15 seconds the Desktop until the firefox-kiosk came up. So this is no solution.

Thanks @RJP for your answer. I tried it but did not get it running. I changed the LOAD_XDG_AUTOSTART option in ~/.desktop-session/desktop-session.conf to true, but my firefox.desktop file seems not to be loaded. Firefox does not open on startup.

Maybe my goal was not precise enough.
I dont want to start rox-icewm or any other desktop. I want to direktly start firefox. This is possible by passing the openningscript directly to “startx”. I tried this from another console-screen via ctrl+alt+f6.

To make it clearer:
My goal is to autologin to console without starting a desktop and executing the firefoxstartupscript.

Thanks

Hi,

i installed AntiX on an 20 years old 32bit netbook and it works great.
Now i try to change this little laptop into a kiosk for my little daughter.

Therefore i only want her to play around with only one, locally served website i create for her.
I managed to get an apache up and running at startup so the website is there.
And if i execute “startx firefox_startscript.sh” from a console (which only makes a “firefox –kiosk http://localhost”) i end up with what i want.

But here is my problem.
I cant suppress the displaymanager on startup to direktly start this script.
The best i can do is to start it after the desktop is loaded via the “./desktop-session/startup” file. But this would show the desktop for nearly 15 seconds and enables the closing of firefox with alt+f4. so this is not a solution i can take.

I hope someone has an idea how to achive this.

Adding my own firefox.dektop file to /usr/share/xsession was a failure and didnt work.
Directly changing /usr/local/bin/desktop-session broke my systemlogin 😀

So what i want at the end:
– autologin
– immediate execution of “firefox –kiosk http://localhost”

Thanks

[Member Cbazic]

I have no idea what I did but I kept rebooting and after the 4th or 5th reboot AntiX booted up like it’s supposed to. It reverted back to the default Roxfluxbox with login on desktop environment. It had mouse support and I logged back in. I didn’t verify my download of AntiX 22 using checksum but I ran integrity check on 2 other machines and on the target machine Toshiba Portege M200 Centrino with Nvidia GeForce FX before installing antix. I know that it was booting normaly and the only thing I did different was to switch to the Minimal JWM window manager before logging out. After that my system only booted to the CLI and after logging in and running cmd startx it booted into JWM without mouse support. I’m not used to any of the 3 types of window mangers in the distro. I’m researching the manuals for window managers now and playing with them. I’m trying AntiX to achieve the functionality for my portege that this guy did https://jansen-pcinfo.com/2020/01/13/recover-toshiba-portege-m200-laptop/

Hi all !! I am an AntiX newbie. I have some linux/Unix experience but not a lot. I installed AntiX on a Toshiba Portege m200 with Nvidia graphics card. Everything was running smoothly except I tried using a different window manager when logging off and shutting down. The window manager had a shutdown button on the right at the bottom. Now when I start the OS it boots to command line only. I then used the startx cmd and it boots to the window but I have no mouse support or mouse pad support on the laptop. Is this a bug or is it a peculiarities to the window manager I changed and used to shutdown after my last session Thanks

[Forum Admin Dave]

All that should be needed is to boot like normal. Then once logged in press “Control + Alt + f6” and type “startx /usr/local/bin/desktop-session rox-icewm” and that tty will start the second xorg instance. For single user this is how I have been doing this for a while. I think you can specify another place / f key by adding –vt[0-9].

For simultaneous multiple user system (multiseat) I do have instructions here in the forum somewhere as well as older dated instructions. The newer ones use seatd IIRC the older ones do not.

Computers are like air conditioners. They work fine until you start opening Windows. ~Author Unknown