Search Results for 'startx'

[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

[Member sybok]

Pardon my lack of understanding.
SLiM(ski), naively interpreted by me as “also the login screen”, runs X as root (‘ps -ef | grep -i slim’ easily verifies it; hm, I could have thought of that sooner).

Just curious, would it be easily possible to switch it to a dedicated user, as is the GDM’s way?
Is the graphical session (of a user and entered/managed through SLiM(ski)) itself run with a user privilege X’s then?
Or “is it” the same X run as root?

The post at Devuan forum (by Head_on_a_Stick) mentions using ‘startx’ (which according to its man-pages is a frontend for ‘xinit’) as an alternative to run X as a user.
I interpret the text and code as follows: that one boots into a terminal TTY1 and when the user logs in, the X is started, i.e. no “fancy” login screen (by slim(ski)) but shell prompt instead.
Using it instead of slim(ski) would result into a feature loss (switching desktops via F1 before logging in).

[Forum Admin anticapitalista]

slim/slimski run X as root.
startx should run X as user.
Apparently,gdm or whatever it is called now, starts X as user,

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

[Moderator christophe]

If you find you need to boot to the console instead of booting directly into an X session, look at this thread:

https://www.antixforum.com/forums/topic/startx-on-antix-base-and-full/

Maybe this will give you what you are looking for?

Edit:
If you are booting live (not installed), add “3” (without quotes) at the end of the bootloader command line. That should bring you to the console without x (runlevel 3).

• This reply was modified 3 months ago by christophe. Reason: Added another thought
• This reply was modified 3 months ago by christophe.

confirmed antiX frugaler, since 2019

[Member techore]

After reading your post, I am not sure that I understand. Also, I would recommend linking a post if you are going to reference one from another thread. The thread you referenced has 117 posts as of right now.

If you want to launch an application at start of xorg, using startx or xinit, update ~/.xinitrc by placing the program to launch before the window manager. However, I suspect you are using a display manager. If true, you may need to configure it to launch the program. Looks for its configuration file and read its man page or home page. There should be instructions.

[Member techore]

This may help.

Login as root or use sudo.

Install xorg packages. Package xserver-xorg-legacy permits use of startx.

apt install xorg xinput xserver-xorg-legacy

Install twm, cyrillic font, and xterm for testing. They can all be removed later.

apt install twm xfonts-cyrillic xterm

Update Xwrapper.conf.

echo "needs_root_rights=yes" >> /etc/X11/Xwrapper.config

Login with your user account not root.

nano ~/.xinitrc

Results

xterm &
exec twm

Test before proceeding.

startx

Desktop should display using twm. Click to deposit xterm then left mouse click on the desktop, select “Exit,” then “Yes, really quit.”

Reference: https://gitlab.com/techore/antix-dwm-guide/-/blob/main/docs/xorg.md#install-xorg

The above is a starting point for installing the window manager of your choice and updating .xinitrc. Obviously, you need a working display driver.

[Member techore]

1. typo

cp "$confdir/patches.def.h" "$confdir/patches.h"

Fixed and thank you! To get updates:

cd /usr/local/src/antix-dwm
git pull

2. On the screenshot. You should see a dialog, so something isn’t right. From a terminal:

antixscreenshot.sh

If you are unable to open a shell after ‘startx’, you can edit using nano .xinitrc and place command above exec dwm like ‘kitty &’ or any terminal you want to use. After startx, the terminal should be launched.

3. On neovim and 32 bit. Ouch! I’ll take some time out to learn more on 32 bit and neovim. It does highlight a concern I had with the ton of customizations I did with neovim which in turn resulted with having to use a newer github version. I could just install the Debian repo package and create a neovim-nvchad installation script to run after OS installation. Something for me to think on.

4. building dwm. Ensure you have the build requirements installed.

https://gitlab.com/-/ide/project/techore/antix-dwm/tree/main/-/build/git-dwm.sh/

With all the above being said, I’ve never tried to do an antiX 32 bit build.

• This reply was modified 3 months, 1 week ago by techore.

[Member techore]

The assumption is you will be using a display manager.

No idea why using startx versus a display manager is considered legacy. Someone upstream of antiX made that decision.

and, I don’t use a display manager, either. Nothing wrong with display managers but I prefer to use tty1 for simple or quick tasks.

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

Hi!
I have installed Antix 22 Core on my USB drive and it is working fine other than Xserver.
I installed Xorg with apt install xorg
X server start without any issue with root user
I also installed lightdm and it was working fine with lightdm too

Created .xinitrc echo "exec xterm" > .xinitrc
# startx (as root) works fine.

$ startx (as USER)Ended with Errors

xf86EnableIOPrts: fialed to set IOPL for I/O (Operation not permitted)
Error: Kernel is too old for Iris. Consider upgrading to kernel v4.16.

Fatal server error: AddScree/ScreenInit failed for driver 0

Can anyone please help me?

• This topic was modified 3 months, 2 weeks ago by Shail Murtaza.
• This topic was modified 3 months, 2 weeks ago by Shail Murtaza.
• This topic was modified 3 months, 2 weeks ago by Shail Murtaza.

[Member SolusSpider]

Update on my testing…

After days of research and trying, I now have antiX booting at 1600×900 on my Alienware M15x laptop using Nouveau driver.
In https://www.antixforum.com/forums/topic/can-antix-use-nouveau-driver/ @xecure posted about placing this in the boot parameters:

xorg=nouveau nouveau.modeset=1

When I booted I noticed much smaller font on the terminal, which was a great sign.
Then I ran these commands:

sudo Xorg -configure
sudo cp /root/xorg.conf.new /etc/X11/xorg.conf
startx

Running lxrandr confirmed that the system is running at Resolution: 1600×900 Refresh Rate: 59.98
Feeling so good!!!

• This reply was modified 3 months, 3 weeks ago by SolusSpider.
• This reply was modified 3 months, 3 weeks ago by SolusSpider.
• This reply was modified 3 months, 3 weeks ago by SolusSpider.

[Moderator Brian Masinick]

Please beware if you are a Sid user; there is yet another qtbase-abi issue in Sid; for me, it broke sddm and I had to resort to either re-enabling lightdm to start my X server display or use startx. Sddm is broken because of this, and so is anything else that has dependencies on qtbase-abi.

--
Brian Masinick

[Member techore]

Older Asus ROG laptop running antiX 22 dwm spin with qutebrowser and terminal open.

               total        used        free      shared  buff/cache   available
Mem:            31Gi       515Mi        30Gi        21Mi       444Mi        30Gi
Swap:          8.0Gi          0B       8.0Gi
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: Laptop System: ASUSTeK product: G750JX v: 1.0 serial: <filter>
  Mobo: ASUSTeK model: G750JX v: 1.0 serial: <filter>
    UEFI: American Megatrends v: G750JX.208 date: 08/19/2013
Battery:
  ID-1: BAT0 charge: 50.7 Wh (98.8%) condition: 51.3/89.2 Wh (57.5%)
    volts: 15.1 min: 15.1 model: ASUSTeK G750-59 serial: N/A status: N/A
CPU:
  Info: quad core model: Intel Core i7-4700HQ bits: 64 type: MT MCP
    arch: Haswell rev: 3 cache: L1: 256 KiB L2: 1024 KiB L3: 6 MiB
  Speed (MHz): avg: 2395 high: 2397 min/max: 800/3400 cores: 1: 2395
    2: 2396 3: 2395 4: 2395 5: 2396 6: 2397 7: 2397 8: 2396 bogomips: 38315
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: NVIDIA GK106M [GeForce GTX 770M] vendor: ASUSTeK driver: nvidia
    v: 470.161.03 arch: Kepler pcie: speed: 2.5 GT/s lanes: 16 bus-ID: 01:00.0
    chip-ID: 10de:11e0
  Device-2: IMC Networks USB2.0 UVC HD Webcam type: USB driver: uvcvideo
    bus-ID: 3-7:4 chip-ID: 13d3:5188
  Display: server: X.Org v: 1.20.11 driver: X: loaded: nvidia
    unloaded: fbdev,modesetting,nouveau,vesa alternate: nv gpu: nvidia
    resolution: 1920x1080~60Hz
  OpenGL: renderer: NVIDIA GeForce GTX 770M/PCIe/SSE2
    v: 4.6.0 NVIDIA 470.161.03 direct render: Yes
Network:
  Device-1: Broadcom BCM4352 802.11ac Wireless Network Adapter
    vendor: AzureWave driver: wl v: kernel pcie: speed: 5 GT/s lanes: 1
    bus-ID: 03:00.0 chip-ID: 14e4:43b1
  IF: wlan0 state: down mac: <filter>
  Device-2: Qualcomm Atheros QCA8171 Gigabit Ethernet vendor: ASUSTeK
    driver: alx v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: d000
    bus-ID: 04:00.0 chip-ID: 1969:10a1
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:
  Local Storage: total: 704.24 GiB used: 6.23 GiB (0.9%)
Info:
  Processes: 209 Uptime: 4m Memory: 31.28 GiB used: 941.8 MiB (2.9%)
  Init: runit v: N/A runlevel: 2 Compilers: gcc: 10.2.1 alt: 10 Packages:
  apt: 1354 Shell: fish v: 3.1.2 running-in: kitty inxi: 3.3.19

[Member techore]

I ran into a problem using iso-snapshot via cli (-c) and “edit_boot_menu=yes.”

It launches the default editor and prints at the top of the screen “Processing command…” where the three dots blink. Attempting to exit nano using ctrl-x or :q using vi/vim/nvim do not work and ctrl+c/z results with iso-snapshot aborting. Not exactly a surprise that last bit.

I don’t use xorg (startx) as part of my spin creation process, but seeing a reference to leafpad in the iso-snapshot.conf, I installed leafpad, startx, and iso-snapshot without “-c” and it worked using leafpad. Substituting leafpad with a cli text editor in iso-snapshot.conf resulted with “Processing command…” It does state GUI text editor in the conf file so not exactly surprising.

The option “-c” and having to launch xorg and install a GUI editor feels like a contradiction and my preference is to do all this from the cli wihthout xorg. I know, I am stubborn. 🙂

I can change my process and launch xorg but is this an oversight?

Correction: see struck-out text.

• This reply was modified 4 months ago by techore.

[Member stevesr0]

hi olsztyn,

You are correct. Thanks for correcting my mistake <g>.

I looked over my files and some online info on /etc/xdg/autostart and /etc/xdg/openbox/autostart. The only apparent difference to expect from the loading of /edg/autostart is that the .desktop files should start applications. However, I don’t know yet how to test whether these are active or not on my system.

The three step sequence I believe, is that startx launches X, then the ~/.desktop-session/default-desktop launches openbox and then /etc/xdg/openbox/ launch applications that run within openbox.

(Parenthetical) Question: In my default-desktop file, I just changed the “openbox” entry to “openbox-session” and restarted X without obvious change. Which do you have in your default-desktop file?

stevesr0

[Member techore]

testing.. and more testing.. inxi -zv3x

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 System: HP product: HP Z6 G4 Workstation v: N/A
    serial: <filter> Chassis: type: 3 serial: <filter>
  Mobo: HP model: 81C6 v: MVB 0C serial: <filter> UEFI: HP v: P60 v02.75
    date: 09/28/2021
CPU:
  Info: 2x 18-core model: Intel Xeon Gold 6140 bits: 64 type: MT MCP SMP
    arch: Skylake rev: 4 cache: L1: 2x 1.1 MiB (2.2 MiB) L2: 2x 18 MiB (36 MiB)
    L3: 2x 24.8 MiB (49.5 MiB)
  Speed (MHz): avg: 1214 high: 3530 min/max: 1000/3700 cores: 1: 1791
    2: 1069 3: 1570 4: 1000 5: 1195 6: 1000 7: 1353 8: 1000 9: 1898 10: 1001
    11: 1110 12: 1000 13: 1294 14: 1545 15: 1000 16: 1247 17: 1755 18: 1817
    19: 1000 20: 1000 21: 1000 22: 1000 23: 1000 24: 1000 25: 1001 26: 1000
    27: 1000 28: 1000 29: 1000 30: 1000 31: 1000 32: 1000 33: 1000 34: 1000
    35: 1000 36: 1000 37: 1398 38: 2464 39: 1069 40: 1984 41: 1000 42: 1000
    43: 1000 44: 2701 45: 3530 46: 1782 47: 1272 48: 1544 49: 1550 50: 1000
    51: 1000 52: 1000 53: 1000 54: 1516 55: 1000 56: 1000 57: 1000 58: 1000
    59: 1000 60: 1000 61: 1000 62: 1000 63: 1000 64: 1000 65: 1000 66: 1000
    67: 1000 68: 1000 69: 1000 70: 1000 71: 1000 72: 1000 bogomips: 331499
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: NVIDIA GP104GL [Quadro P4000] vendor: Hewlett-Packard driver: N/A
    arch: Pascal pcie: speed: 2.5 GT/s lanes: 16 bus-ID: 21:00.0
    chip-ID: 10de:1bb1
  Display: server: X.Org v: 1.20.11 driver: X: loaded: N/A unloaded: fbdev
    gpu: N/A resolution: 3840x2160
  OpenGL: renderer: llvmpipe (LLVM 11.0.1 256 bits) v: 4.5 Mesa 20.3.5
    compat-v: 3.1 direct render: Yes
Network:
  Device-1: Intel Ethernet 10G X550T driver: ixgbe v: kernel pcie:
    speed: 8 GT/s lanes: 4 port: N/A bus-ID: 17:00.0 chip-ID: 8086:1563
  IF: eth0 state: down mac: <filter>
  Device-2: Intel Ethernet 10G X550T driver: ixgbe v: kernel pcie:
    speed: 8 GT/s lanes: 4 port: N/A bus-ID: 17:00.1 chip-ID: 8086:1563
  IF: eth1 state: down mac: <filter>
  IF-ID-1: usb0 state: up speed: N/A duplex: N/A mac: <filter>
Drives:
  Local Storage: total: 968.44 GiB used: 4.94 GiB (0.5%)
Info:
  Processes: 723 Uptime: 6h 51m Memory: 31.11 GiB used: 2.62 GiB (8.4%)
  Init: runit v: N/A runlevel: 2 Compilers: gcc: 10.2.1 alt: 10 Packages:
  apt: 1105 Shell: fish v: 3.1.2 running-in: kitty inxi: 3.3.19