I have a powerful machine that I want to use as a multi-seat system. It has two graphic cards and two pairs of keyboards and mice. I've been able to successfully configure two "seats" using udev and Xorg.conf, and launch two X servers from a script so two users can have independent sessions. Just for the record, here's my udev rules file, where I identify each USB hub and label the devices and the seats: SUBSYSTEM=="drm", KERNEL=="card[0-9]*", ATTRS{vendor}=="0x10de", DRIVERS=="nvidia", TAG+="master-of-seat" # SUBSYSTEM=="drm", KERNEL=="card0", ENV{ID_SEAT}="seat0" # SUBSYSTEM=="drm", KERNEL=="card1", ENV{ID_SEAT}="seat1" SUBSYSTEM=="input", ENV{ID_INPUT.tags}="input_default" # KVM HUBS KERNELS=="3-2", ATTRS{bDeviceClass}=="09", ENV{KVM_HUB}="1", ENV{ID_SEAT}="seat0" KERNELS=="3-8", ATTRS{bDeviceClass}=="09", ENV{KVM_HUB}="2", ENV{ID_SEAT}="seat1" # Devices of HUB 1 KERNEL=="event*", ENV{KVM_HUB}=="1", ATTRS{bInterfaceProtocol}=="01" SYMLINK+="kvm_keyboard_1" KERNEL=="event*", ENV{KVM_HUB}=="1", ATTRS{bInterfaceProtocol}=="02" SYMLINK+="kvm_mouse_1" # Devices of HUB 2 KERNEL=="event*", ENV{KVM_HUB}=="2", ATTRS{bInterfaceProtocol}=="01" SYMLINK+="kvm_keyboard_2" KERNEL=="event*", ENV{KVM_HUB}=="2", ATTRS{bInterfaceProtocol}=="02" SYMLINK+="kvm_mouse_2" # Default seat SUBSYSTEM=="input", TAG=="seat", ENV{ID_SEAT}=="" , ENV{ID_SEAT}="seat0" # set all tags accordingly ENV{ID_SEAT}!="", ENV{ID_INPUT.tags}+="$env{ID_SEAT}" TAG+="$env{ID_SEAT}" The relevant part of my xorg.conf file looks like this: Section "ServerFlags" # Option "AutoAddDevices" "false" # Option "AutoEnableDevices" "false" Option "DefaultServerLayout" "Layout0" Option "AllowMouseOpenFail" "true" Option "Xinerama" "0" EndSection # --------------------------------------------------------------- # LAYOUT Section "ServerLayout" Identifier "Layout0" Screen "Screen0" MatchSeat "seat0" Option "Clone" "off" EndSection Section "ServerLayout" Identifier "Layout1" Screen "Screen1" MatchSeat "seat1" Option "Clone" "off" EndSection As I said, **I can successfully launch** two independent sessions using the following script, but I'd like this to happen automatically on boot. #!/bin/bash set +x rm /etc/X11/xorg.conf cp ./xorg_independientes /etc/X11/xorg.conf # X (:0) systemctl stop gdm killall Xorg killall X systemctl restart gdm sleep 7 # X (:1) su - sit -c "startx /usr/bin/gnome-session -- :1 vt4 -layout Layout1 -seat seat1 -sharevts" & sleep 10 DISPLAY=:1 xhost + My approach would be setting the default target runlevel to 4 (so it has everything but graphics) and then placing these commands in a script somewhere.

I get this error when running 'startx'. What is this 'nv' module, and how do I stop Xorg from trying to load it? EDIT: I am going to try to blacklist the module 'nv' using the kernel command line. I'll update this post if that works. I installed the Nvidia drivers, nouveau drivers and intel drivers. I also added the Nvidia drivers to /etc/mkinitcpio.conf (in MODULES). I'm on the latest version of Arch Linux. What I tried: - Created the xorg.conf file using nvidia-xconfig. On doing 'startx', nothing happens until I type 'exit' - Deleted the xorg.conf file. It yields the nv module error Also, is there a way to use the intel drivers instead of the nvidia drivers? I'd like to use this as a last resort.

I login from the tty. my .xinit file had the command exec i3I got tired of constantly retyping startx after login so i put exec startxat the end of my .bash_profile. now every time I type my login credentials it flashes a failed startx the reprompts me for the login credentials again. I can't log into the computer anymore. I tried pressing ctrl-c which didn't do anything and I tried holding the power button which just turned off the laptop. edit: I use the newest version of Linux mint cinnamon which comes with light DM display manager by default. I had only disabled it for a day which was when the issue happened

Ever since I updated debian, evince has been slow to startup - it takes about half a minute. Once it is open, it works fine, its just slow to open. It never used to take that long - it just used to take a couple of seconds. How can I get it going fast again? $ uname -a Linux mypc 5.10.0-9-amd64 #1 SMP Debian 5.10.70-1 (2021-09-30) x86_64 GNU/Linux I noticed that evince is hanging at the following line for about half a minute: $ strace evince ... eventfd2(0, EFD_CLOEXEC|EFD_NONBLOCK) = 11 write(11, "\1\0\0\0\0\0\0\0", 8) = 8 write(10, "\1\0\0\0\0\0\0\0", 8) = 8 futex(0x562f5b8ffac0, FUTEX_WAKE_PRIVATE, 1) = 1 futex(0x562f5b909b30, FUTEX_WAKE_PRIVATE, 1) = 1 futex(0x562f5b8bd158, FUTEX_WAKE_PRIVATE, 1) = 1 poll([{fd=11, events=POLLIN}], 1, 25000) = 1 ([{fd=11, revents=POLLIN}]) read(11, "\1\0\0\0\0\0\0\0", 16) = 8 poll([{fd=11, events=POLLIN}], 1, 25000) = 0 (Timeout) # /dev/null 2>&1 && \ startx -- :0 vt1 # if using rxvt or urxvt immediately set the window to fullscreen if [[ $TERM == *"rxvt"* ]]; then # make the window with rxvt in the name the active window wmctrl -a rxvt # make the active window fullscreen wmctrl -r ":ACTIVE:" -b add,fullscreen fi **Edit: add some dbus information** $ ls -l ~/.dbus/session-bus/ total 28 -rw-r--r-- 1 me me 465 Nov 8 06:23 c984eb16cbd294a01d56c2ac523f7100-0 -rw-r--r-- 1 me me 465 Nov 6 14:11 c984eb16cbd294a01d56c2ac523f7100-1 -rw-r--r-- 1 me me 476 Apr 24 2017 c984eb16cbd294a01d56c2ac523f7100-10 -rw-r--r-- 1 me me 465 Jun 5 2017 c984eb16cbd294a01d56c2ac523f7100-100 -rw-r--r-- 1 me me 476 Apr 7 2017 c984eb16cbd294a01d56c2ac523f7100-11 -rw-r--r-- 1 me me 465 Nov 6 14:37 c984eb16cbd294a01d56c2ac523f7100-2 -rw-r--r-- 1 me me 463 May 6 2016 c984eb16cbd294a01d56c2ac523f7100-3 $ echo $DBUS_SESSION_BUS_ADDRESS # empty!

i want make it automatically to start with no-cursor: startx -- -nocursor this is worked but this is command..i want to autostart to user: kiosk.. (but i don't want to use "unclutter") i'm not understand where i will can add script or file configure startx with no-cursor.. .xinitrc? or other file configure.. i use opensuse 15.6 with openbox so i ask here, i hope find your help hand code.. :-) thank you

I am running OpenBSD on a laptop with X windows starting on f5 vtty via Xenodm login manager. I am unable to start another session of X from different vtty.  xinit or startx fails with Fatal server error:  - no console drivers found. Supported drivers: wscons Since, X11 is running well on default window I figured that I should be able to launch addition session on different ttys

I need some help on this. When I boot into Debian 10 (buster) x86_64 with Plasma KDE it doesn't go into the graphical environment and I have to first login in the terminal and then run 'startx' I looked around a bunch and still haven't solved this. - running systemctl status graphical.target: > graphical.target - Graphical Interface > > Loaded: loaded (/lib/systemd/system/graphical.target; indirect; vendor preset: enabled) > > Active: active since Thu 2020-04-09 12:11:13 WEST; 6min ago > > Docs: man:systemd.special(7) > > running 'systemctl get-default' > systemctl get-default > > graphical.target - running systemctl list-dependencies graphical.target everything seems OK - running systemctl status display-manager.service > sddm.service - Simple Desktop Display Manager > > Loaded: loaded (/lib/systemd/system/sddm.service; indirect; vendor preset: enabled) > > Active: active (running) since Thu 2020-04-09 12:11:13 WEST; 8min ago > > Docs: man:sddm(1) > > man:sddm.conf(5) > > Process: 389 ExecStartPre=/bin/sh -c [ "$(basename $(cat /etc/X11/default-display-manager 2>/dev/null))" = "sddm" ] > (code=exited, s > > Main PID: 394 (sddm) > > Tasks: 2 (limit: 4915) > > Memory: 13.3M > > CGroup: /system.slice/sddm.service > > └─394 /usr/bin/sddm

As root, I changed one user’s home directory to a soft link to another drive (while the user was not logged in). Then this user could not run startx anymore, though other users with the same .xinitrc and also in audio group still could. Changing back to the previous home directory or setting it via usermod did not help. No error on console, startx exits with success, only this hint appears if logging: xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted) Here is a log (xorg’s log is much longer but does not seem to have more to offer). root@Freesia/~# startx >& /tmp/startxlog root@Freesia/~# cat /tmp/startxlog X.Org X Server 1.20.4 X Protocol Version 11, Revision 0 Build Operating System: Linux 5.10.0-21-amd64 x86_64 Debian Current Operating System: Linux Freesia 4.19.0-9-amd64 #1 SMP Debian 4.19.118-2+deb10u1 (2020-06-07) x86_64 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.19.0-9-amd64 root=UUID=27ab16fe-4180-4d31-ba99-60476076083f ro quiet Build Date: 28 March 2023 05:03:02PM xorg-server 2:1.20.4-1+deb10u9 (https://www.debian.org/support) Current version of pixman: 0.36.0 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/home/alex/.local/share/xorg/Xorg.1.log", Time: Tue Mar 19 17:47:00 2024 (==) Using system config directory "/usr/share/X11/xorg.conf.d" xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted) (II) modeset(0): Initializing kms color map for depth 24, 8 bpc. xinit: connection to X server lost waiting for X server to shut down (II) Server terminated successfully (0). Closing log file. I tried to delete and recreate the user with the legacy home directory, to no avail.

I am currently working on a display manager for linux using the startx command. The program is running as _root_ (as a display manager normally does) and then drops to a normal user (in this case _kuglatec_). I tested and verified it using whoami which returned kuglatec. Then I started the x server but it cant locate the log file at /root/.local/share/xorg/Xorg.0.log which it shouldn't actually do since xorg isn't running as root and the log file is located an /home/kuglatec/.local/share/xorg/Xorg.0.log. I think that xorg somehow runs as root and tries to access the nonexistent file. Any ideas? Source code of the operating function: https://pastebin.com/GqT28xyq

I, as I can believe anyone around, have been firing /usr/bin/startx for decades experiencing nothing but 100% satisfaction for the job it serves. If it works… don't fix it ! The author of the script is however explicit : > Site administrators are STRONGLY urged to write nicer versions. I am left just curious : - Does anyone know what historical reasons compelled the author to write such strong statement ? - Has anyone ever written any "*nicer version*", how and what for ? ---------- Nota : I see a number of requests to close this question for the reason it would trigger opinion based answers.
I understand how the *"nicer"* qualifier could suggest taste judgements but I just can't imagine the author "*STRONGLY urging*" administrators to commit aesthetic changes. Just lots of things are opened to changes in that script, from forcing client / server arguments, honoring / ignoring users .*rc to even incidentally forking whatever else than /usr/bin/xinit. All these fiddlings + many more I don't even imagine particularly in the field of security, would certainly depend on perfectly reasonable motives and fit the purpose of special use cases. This is exactly what this question is about.

I use bspwm with a simple .xinitrc config file instead of a display manager, and there is only a simple exec dbus-launch bspwm command there. Whenever I start a program via, for example, dmenu_run (which itself is started via sxhkd after sourcing bspwmrc file), the output from that program goes straight to the tty from which the X session was started. For instance if I run echo it will write the message to the tty, instead of just ignoring it (despite the fact that, from my understanding, there shouldn't be any file descriptors to which echo could write). What confuses me most, is that many other programs that can too write to stdout (steam, firefox, mpv...), actually don't pollute the tty despite also being started via dmenu_run. **Why?** And the worst thing yet, some programs like w3m, not only show their output but also stay interactive even after exiting the X11 session. **Why and how** does this happen, and how can I prevent it?

Same symptom as ["xf86EnableIO: failed to enable I/O ports 0000-03ff (Operation not permitted)"](https://askubuntu.com/questions/1481183/xf86enableio-failed-to-enable-i-o-ports-0000-03ff-operation-not-permitted) , which solution was: > Looks like a lot of people are having similar issues today. In my case, on Ubuntu 22.04.3 I fixed the issue by installing ubuntu-desktop: > > sudo apt install ubuntu-desktop because the [root cause was](https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2030262) : > I noticed xorg and the whole desktop (lubuntu first, kubuntu later at another laptop) had been removed However, that's not the case for my Debian 12 bookworm, which I have just upgraded kernel from linux-image-6.1.0-9-amd64 to linux-image-6.1.0-13-amd64, and right afterwards, my startx is failing. I posted the full log at: https://pastebin.com/tAfEBazQ The most important line seems to be xf86EnableIO: failed to enable I/O ports 0000-03ff (Operation not permitted) I tried the answer from https://unix.stackexchange.com/questions/159124/xf86enableioports-failed-to-set-iopl-for-i-o-operation-not-permitted , and can confirm that the sudo chmod u+s /usr/bin/xinit is not working for my case. I believe it is purely kernel related as - I can boot from my old linux-image-6.1.0-9-amd64 and able to startx - and with linux-image-6.1.0-13-amd64 and even with elevated xinit my startx is still failing - My xserver-xorg is the same after kernel upgrade, and is already the latest version. Judging from that fact that merely swapping the kernel when booting makes the vital differences, the kernel upgrade seems to be the root cause. But I'm wondering how to fix it. PS. More info: I use startx as myself as always, and

$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:    Debian GNU/Linux 12 (bookworm)
Release:        12
Codename:       bookworm

$ apt-cache policy xserver-xorg
xserver-xorg:
  Installed: 1:7.7+23
  Candidate: 1:7.7+23
  Version table:
 *** 1:7.7+23 500
        500 http://deb.debian.org/debian  bookworm/main amd64 Packages
         80 http://deb.debian.org/debian  trixie/main amd64 Packages
        100 /var/lib/dpkg/status

$ plocate vesa.conf | wc
      0       0       0

$ plocate xorg.conf.d | grep /etc/
/etc/X11/xorg.conf.d

$ ls /etc/X11/xorg.conf.d | wc
      0       0       0

$ stat /usr/bin/xinit
  File: /usr/bin/xinit
  Size: 19064           Blocks: 40         IO Block: 4096   regular file
Device: 8,11    Inode: 524333      Links: 1
Access: (4755/-rwsr-xr-x)  Uid: (    0/    root)   Gid: (    0/    root)

I am running Windows 10 as a Virtualbox Host and Arch Linux as Guest. During startup, vboxdrv.service fails. The tty starts fine, I can do everything inside it. However, startx leads to what I believe to be the normal stdout, but after that, nothing happens, I have no graphical interface, my i3wm does not start. My guess is that this behaviour is linked to vboxdrv.service failing at startup. Relevant information might be: systemctl status vboxdrv.service:

vboxdrv.service - VirtualBox Linux kernel module
     Loaded: loaded (/opt/VirtualBox/vboxdrv.sh; enabled; vendor preset: disabled)
     Active: failed (Result: exit-code) since Sun 2020-04-05 11:25:10 CEST, 11 min ago
    Process: 359 ExecStart=/opt/VirtualBox/vboxdrv.sh start (code=exited, status=1/FAILURE)

Apr 05 11:25:08 archlinux-vm systemd: Starting VirtualBox Linux kernel module...
Apr 05 11:25:10 archlinux-vm vboxdrv.sh: vboxdrv.sh: Starting VirtualBox services.
Apr 05 11:25:10 archlinux-vm vboxdrv.sh: Starting VirtualBox services.
Apr 05 11:25:10 archlinux-vm vboxdrv.sh: vboxdrv.sh: failed: modprobe vboxpci failed. Please use 'dmesg' to find out why.
Apr 05 11:25:10 archlinux-vm systemd: vboxdrv.service: Control process exited, code=exited, status=1/FAILURE
Apr 05 11:25:10 archlinux-vm systemd: vboxdrv.service: Failed with result 'exit-code'
Apr 05 11:25:10 archlinux-vm systemd: Failed to start VirtualBox Linux kernel module.

dmesg | grep vboxpci yields nothing. dmesg | grep vboxdrv:

[    7.200636] vboxdrv: loading out-of-tree module taints kernel.
[    7.200840] vboxdrv: module verification failed: signature and/or required key missing - taintig kernel
[    7.209208] vboxcrv: Found 1 processor cores
[    7.246471] vboxdrv: TSC mode is Invariant, tentative frequency 2711995959 Hz
[    7.246472] vboxdrv: Successfully loaded version 6.1.4 (interface 0x002d0001)

startx:

X.Org X Server 1.20.8
X Protocol Version 11, Revision 0
Build Operating System: Linux Arch Linux
Current Operating System: Linux archlinux-vm 5.5.13-arch2-1 # SMP PREEMPT Mon, 30 Mar 2020 20:42:41 +0000 x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=894e6e02-38f6-4798-b936-431c8287803a rw quiet
Build Date: 30 March 2020 05:05:45AM

Current version of pixman: 0.38.4
        Before reporting problems, check http://wiki.x.org 
        to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational, 
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/home/[username]/.local/share/xorg/Xorg.0.log", Time: Sun Apr  5 11:25:30 2020
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
_

and blocking the tty. pacman -Qs virtualbox:

local/virtualbox-guest-modules-arch 6.1.4-12
    Virtualbox guest kernel modules for Arch Kernel
local/virtualbox-guest-utils 6.1.4-5
    VirtualBox Guest userspace utilities
local/virtualbox-host-modules-arch 6.1.4-12
    Virtualbox host kernel modules for Arch Kernel

EDIT: I have updated the machine again (it asked me whether I want to replace virtualbox-guest-modules with linux, I gladly agreed in hope of fixing the problem with the update, but behaviour stays the same), new pacman -Qs virtualbox:

local/linux 5.6.2.arch1-2
    The Linux kernel and modules
local/virtualbox-guest-utils 6.1.4-5
    VirtualBox Guest userspace utilities
local/virtualbox-host-modules-arch 6.1.4-15
    Virtualbox host kernel modules for Arch Kernel

This has been happening for about two weeks now, probably after updating my machine. Before, everything was fine. What can I do?

I upgraded my Linux Mint to Release 20 Ulyana from Release 18. After the upgrade now my Mint boot to login prompt on command line. I can login fine but i have to type startx on command line to get to my desktop. I like it to be same as before where i boot to desktop straight. what i'm missing here?. please help. As per instructions i have installed lightdm services. After reboot and checking status of the lightdm service i get the following status. Looks like something is missing. systemctl status lightdm ● lightdm.service - Light Display Manager Loaded: loaded (/lib/systemd/system/lightdm.service; indirect; vendor preset: enabled) Active: active (running) since Sat 2021-11-27 20:10:21 PST; 1min 47s ago Docs: man:lightdm(1) Process: 965 ExecStartPre=/bin/sh -c [ "$(basename $(cat /etc/X11/default-display-manager 2>/dev/null))" = "lightdm" ] (code=exited, status=0/SUCCESS) Main PID: 975 (lightdm) Tasks: 5 (limit: 4576) Memory: 97.7M CGroup: /system.slice/lightdm.service ├─ 975 /usr/sbin/lightdm └─1008 /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch Nov 27 20:10:23 smaqsood-LinuxMint lightdm: gkr-pam: gnome-keyring-daemon started properly Nov 27 20:10:25 smaqsood-LinuxMint lightdm: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory Nov 27 20:10:25 smaqsood-LinuxMint lightdm: PAM adding faulty module: pam_kwallet.so Nov 27 20:10:25 smaqsood-LinuxMint lightdm: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory Nov 27 20:10:25 smaqsood-LinuxMint lightdm: PAM adding faulty module: pam_kwallet5.so Nov 27 20:10:25 smaqsood-LinuxMint lightdm: pam_succeed_if(lightdm:auth): requirement "user ingroup nopasswdlogin" not met by user "smaqsood" Nov 27 20:10:36 smaqsood-LinuxMint lightdm: gkr-pam: unable to locate daemon control file Nov 27 20:10:36 smaqsood-LinuxMint lightdm: gkr-pam: stashed password to try later in open session Nov 27 20:10:36 smaqsood-LinuxMint lightdm: pam_unix(lightdm:session): session opened for user smaqsood by (uid=0) Nov 27 20:10:36 smaqsood-LinuxMint lightdm: gkr-pam: gnome-keyring-daemon started properly and unlocked keyring

I have been using my backtrack version 5 on the Virtualbox for some time now but I had a resolution problem and after searching found out I better install VirtualGuest additions. However after installing it startx does not work anymore and gives me segmentation fault. as follows: Segmentation fault at address 0x7f7b26129800 caught signal 11(segmentation fault). Server aborting Please consult the http://wiki.x.org foundation support Please check the log file at "var/log/Xorg.0.log" for additional information. ddxSigGiveUp: closing log giving up. xinit: no such file or directory (errno 2). unable to connect to x server. xinit: no such process (errno 3). Server error.

I use __Manjaro Linux__ and after an update, when I boot, journalctl says the system reached graphical target, but it starts up in tty1 and I need to type startx to start the **KDE**. Then I type my password again in a kdewallet popup, to connect to wifi. After that, everything works fine. In __Manjaro__, the gui starts in tty1, while in other distros, it usually starts in tty7. I tried setting the default to graphical.target with the systemctl command, and by editing grub menu by replacing the quit parameter by systemd.unit=graphical.target, but it still starts up in the tty1 session. I also tried adding a custom entry in the grub menu, but that does not help either. To add this to the grub menu: - copy the first grub menu entry from /boot/grub/grub.cfg into the file /etc/grub.d/40_custom - replace the quit command by systemd.unit=graphical.target - change the menuentry title and run sudo update-grub Any ideas on how to get the system to start normal again. I posed the question in the __Manjaro__ forum a week ago, but there is no reply. I suppose it will be faster to just re-install, but I am curious why this happens, and how to correct it. --- Thanks for the tips. I found that ssdm is installed but not active, it is masked. When I try to re-install it, I get this error: sudo pacman -S sddm warning: sddm-0.19.0-2.2 is up to date -- reinstalling ... error: sddm: signature from "Philip Müller (Called Little)" is invalid :: File /var/cache/pacman/pkg/sddm-0.19.0-2.2-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)). Do you want to delete it? [Y/n] error: failed to commit transaction (invalid or corrupted package (PGP signature)) Errors occurred, no packages were upgraded. [marc@ass ~]$ systemctl enable sddm.service Failed to enable unit: Unit file /usr/lib/systemd/system/sddm.service is masked. When I look for /usr/lib/systemd/system/sddm.service, I see that it is empty. Am I correct that there is some kind of packaging error, and that due to the corrupted package, the system blocked it from starting ? If the package is corrupt, should not more people have this problem ? Should I wait some time for the package to get repaired, or should I uninstall it and install another greeter like lightdm ?

I am running the python window app in startx, it works fine, but there is one issue. the issue will be in the next two images.\ -First image, Python app running in Linux GUI [window app in GUI](https://github.com/TarikVUT/Store-/blob/main/images/in%20GUI.png) \ -Second image, Python app running in Linux startx [window app in startx](https://github.com/TarikVUT/Store-/blob/main/images/In%20startx.png) As you can see the window app in startx is losing its frame. \ I have added the below code to **.xinitrc**

#!/bin/bash
#to set mouse cursor
xsetroot -cursor_name arrow
#to run startpython.py
exec python /home/GUI/startpython.py

What is the way to make the window in (startx) look like window in GUI (enable the frame around the window), without the frame I can close the window using (x). **Any idea?**

I am new to Arch and did a fresh install. I have configured it to use dwm and I start it with startx. The problem is that some commands in xinitrc seem to not run. It clearly works to some extend, because dwm is starting, but i can't say the same for other commands. My xintirc is located: ~/.xinitrc (or /home/xor/.xinitrc) and looks like this: exec dwm set xkbmap de feh --bg-scale ~/background.png xinput set-prop "UNIW0001:00 093A:0255 Touchpad" 349 1 xinput set-prop "UNIW0001:00 093A:0255 Touchpad" 326 1 xrandr --setprovideroutputsource modesetting NVIDIA-0 xrandr --auto It should start dwm(which it does), set the keyboard layout to german qwertz(which works), set a background image(which does not work) adjust some touchpad settings(which does not work), and do something with the nvidia driver(Not exactly sure what it does, i guess it enables the card/driver, but I know that the drivers work and I can use my GPU). I can paste the not working commands in a terminal and they work. Is there somewhere an error log for the file xinit, and what is the problem in my case? Thanks for help!

For context, my file/directory structure and contents are mostly copied from how it is in Luke Smith's dotfiles (voidrice ). Also, the "..." lines in the code blocks aren't code and represent omitted lines in the file. I have this in my ~/.zprofile:

#!/bin/zsh
...
export XINITRC="${XDG_CONFIG_HOME:-$HOME/.config}/x11/xinitrc"

And this in my aliases file that ~/.zshrc sources (~/.config/shell/aliasrc):

#!/bin/bash
...
esx() { exec startx "$XINITRC" "$@" -- -keeptty >~/xorg.log 2>&1; }
sx() { startx "$XINITRC" "$@" -- -keeptty >~/xorg.log 2>&1; }

(The "--" part of the functions' commands onwards is for logging ) This is what ~/.config/x11/xinitrc looks like:

#!/bin/sh
sysresources="/etc/X11/xinit/.Xresources"
userXprofile="${XDG_CONFIG_HOME:-$HOME/.config}/x11/xprofile" # empty file atm
[ -f "$sysresources" ] && xrdb -merge "$sysresources"
xrdb -merge ${XDG_CONFIG_HOME:-$HOME/.config}/x11/xresources & xrdbpid=$!
if [ -d /etc/X11/xinit/xinitrc.d ] ; then
 for f in /etc/X11/xinit/xinitrc.d/?*.sh ; do
  [ -x "$f" ] && . "$f"
 done
 unset f
fi
if [ -f "$userXprofile" ]; then
    . "$userXprofile"
else
    . "$HOME/.xprofile"
fi
[ -n "$xrdbpid" ] && wait "$xrdbpid"
case $1 in
   awesome|awesomeWM) exec awesome;;
   xfce|xfce4) exec startxfce4;;
   openbox) exec openbox;;
esac

Basically, the intention is to run either esx or sx with the name of whatever window manager or desktop environment I want to use for that particular session. It works properly with esx, but sx will pass the value of $XINITRC to ~/.config/x11/xinitrc as $1 instead of the WM/DE I picked. I tried "fixing" sx by excluding the first argument: sx() { startx "$XINITRC" "${@:2}" -- -keeptty >~/xorg.log 2>&1; } but xinitrc still has $1 as $XINITRC. As a band-aid fix, ~/.config/x11/xinitrc gets rid of the first positional argument if it's "$XINITRC":

[ "$1" = "$XINITRC" ] && shift
case $1 in
...

But I hate this solution and would much rather know why sx is screwing up in the first place. Does anyone know why this is happening?

TLDR; I haven't being able to make ~/.xinitrc being read at any moment. Not even if i edit /etc/X11/xinit/xinitrc. I used to have i3wm so i really didn't use ~/.xinitrc at all i just made programs ran editing i3's config file. I tried editing my ~/.xinitrc but the file just wasn't being read. Now i uninstalled i3wm hoping to use dwm but after executing dwm from my xinitrc file it just wasn't working, whenever i execute startx i just get my terminal (urxvt) displayed awefully, even though i executed dwm from the xinitrc. Now i workaround this issue with this command startx /usr/local/bin/dwm which works well. I also noticed that i didn't have .xsession file i think i deleted all .x files when i was using i3wm. Any ideas how can i get my xinitrc file to be read when starting X? Thanks for reading. This is my xinitrc file.

#!/bin/sh

# /etc/X11/xinit/xinitrc
#
# global xinitrc file, used by all X sessions started by xinit (startx)

# invoke global X session script
. /etc/X11/Xsession

sct 2000 &
setxkbmap us &

exec dwm