Search Results for 'xinitrc'

A laptop that I’ve switched from Gentoo linux to Antix. Screen resolution is 1200×800 (correct). I’ve got Netflix Basic without commercials, which runs at 1280×720. Netflix is letterboxed with a thin black band at the top and one at the bottom. In Gentoo I inserted “xterm -e xrandr –output LVDS1 –scale 1×0.9” in .xinitrc to scale the 800 vertical to 720, and get rid of the letterboxing. In Antix I can manually do this with roxterm and the vertical zooms in as requested. There doesn’t seem to be a .xinitrc file on my system to autoexecute. Into what file would I insert the command…

roxterm -e xrandr --output LVDS1 --scale 1x0.9

[Member Robin]

Open a terminalwindow, e.g. roxterm.

First make a backup-copy of your existing keymap layout:

xmodmap -pke > ~/.xmodmap.original

Now you can do the modifications, e.g.:

	xmodmap -e "keycode  10 = 1 exclam 1 exclam onesuperior U2116 onesuperior"
	xmodmap -e "keycode  11 = 2 at 2 at twosuperior onehalf twosuperior"
	xmodmap -e "keycode  12 = 3 numbersign 3 numbersign threesuperior U2153 threesuperior"
	xmodmap -e "keycode  13 = 4 dollar 4 dollar sterling onequarter sterling"
	xmodmap -e "keycode  14 = 5 percent 5 percent UFFE0 U2155 UFFE0"
	xmodmap -e "keycode  15 = 6 dead_diaeresis 6 dead_diaeresis notsign U2159 notsign"
	xmodmap -e "keycode  16 = 7 ampersand 7 ampersand U2103 U2150 U2103"
	xmodmap -e "keycode  17 = 8 asterisk 8 asterisk degree oneeighth degree"
	xmodmap -e "keycode  18 = 9 parenleft 9 parenleft U2154 U2151 U2154"
	xmodmap -e "keycode  19 = 0 parenright 0 parenright U00BE U2152 U00BE"
	xmodmap -e "keycode  20 = minus underscore minus underscore emdash endash emdash"
	xmodmap -e "keycode  21 = equal plus equal plus section plusminus section"
	xmodmap -e "keycode  24 = q Q q Q slash U03A9 slash"
	xmodmap -e "keycode  25 = w W w W question U2156 question"
	xmodmap -e "keycode  26 = e E e E EuroSign U2157 EuroSign"
	xmodmap -e "keycode  27 = r R r R paragraph U2158 paragraph"
	xmodmap -e "keycode  28 = t T t T registered U215A registered"
	xmodmap -e "keycode  29 = y Y y Y leftarrow U215C leftarrow"
	xmodmap -e "keycode  30 = u U u U downarrow uparrow downarrow"
	xmodmap -e "keycode  31 = i I i I rightarrow U215D rightarrow"
	xmodmap -e "keycode  32 = o O o O oslash Oslash oslash"
	xmodmap -e "keycode  33 = p P p P U2718 U2714 U2718"
	xmodmap -e "keycode  34 = dead_acute dead_grave dead_acute dead_grave U2030 U2031 U2030"
	xmodmap -e "keycode  38 = a A a A U2074 U2084 U2074"
	xmodmap -e "keycode  39 = s S s S U2075 U2085 U2075"
	xmodmap -e "keycode  40 = d D d D U2076 U2086 U2076"
	xmodmap -e "keycode  41 = f F f F U2077 U2087 U2077"
	xmodmap -e "keycode  42 = g G g G U2078 U2088 U2078"
	xmodmap -e "keycode  43 = h H h H U2079 U2089 U2079"
	xmodmap -e "keycode  44 = j J j J U2070 U2080 U2070"
	xmodmap -e "keycode  45 = k K k K U1D6FC U2081 U1D6FC"
	xmodmap -e "keycode  46 = l L l L U1D6FD U2082 U1D6FD"
	xmodmap -e "keycode  47 = U00E7 U00C7 U00E7 U00C7 U1D6FE U2083 U1D6FE"
	xmodmap -e "keycode  49 = apostrophe quotedbl apostrophe quotedbl multiply division multiply"
	xmodmap -e "keycode  52 = z Z z Z guillemotright U203A guillemotright"
	xmodmap -e "keycode  53 = x X x X guillemotleft U2039 guillemotleft"
	xmodmap -e "keycode  55 = v V v V doublelowquotemark singlelowquotemark doublelowquotemark"
	xmodmap -e "keycode  56 = b B b B leftdoublequotemark leftsinglequotemark leftdoublequotemark"
	xmodmap -e "keycode  57 = n N n N rightdoublequotemark rightsinglequotemark rightdoublequotemark"
	xmodmap -e "keycode  58 = m M m M mu U260F mu"
	xmodmap -e "keycode  59 = comma less comma less U1D706 U2BF3 U1D706"
	xmodmap -e "keycode  60 = period greater period greater U1D717 U2B1C U1D717"
	xmodmap -e "keycode  61 = semicolon colon semicolon colon U1D719 U2BEE U1D719"
	xmodmap -e "keycode  94 = backslash bar backslash bar U254E UFE19 U254E"

(this is an example for pt_BR advanced keyboard only. you’ll need to adapt the modifications to your needs)
When you are content with the result, save the modified keyboard layout to a file:

xmodmap -pke > ~/.xmodmap.pt_BR_special

If there happened any errors, causing you not being able to write any longer, simply restart PC, then your default keyboard layout will be back immediately.
But if all keys are assigned as you prefer it, you can make the changes permanent. If not existing, create the (hidden) file ~/.xinitrc within your home folder.

touch ~/.xinitrc

Open the file using leafpad or geany and append the following line:

xmodmap ~/.xmodmap.pt_BR_special

Save the file.

Windows is like a submarine. Open a window and serious problems will start.

[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.

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.

[Forum Admin anticapitalista]

antiX is built using the build-iso tools pointed out by marcello. This enables consistency of builds and it took us years (yes plural) to develop. MX and AVLinux are now using it, modified of course. All antiX isos are built from scratch using this tool; there is no remaster of anything from Debian. Any budding devs should really use this tool rather than remaster/snapshot.

At the same time as ‘perfecting’ build-iso, we developed our unique live system (including persistence, remaster, snapshot), initially influenced by MEPIS and KNOPPIX live scripts. Our live system also took years to develop and it is completely different from Debian live. MX and AVLinux also use our live system. https://antixlinux.com/the-most-extensive-live-usb-on-the-planet/

Dave also developed the desktop series of scripts, which basically provides a sort of ‘desktop environment’ for antiX-base and full. Early versions of antiX used the common .xinitrc ‘way’ to load window managers, which is fine, but limited IMO. ‘daves-desktop’ is unique to antiX.

Of course we do not use systemd nor elogind. This means we have to provide nosystemd packages. A cursory look into the nosystemd repos will show how much work is needed, particularly on Debian sid where we are playing catch up. We also provide our version of runit scripts that are different to how Debian runs runit.

So, yes, a lot of work from lots of people have gone into making antiX what it is.

Build-iso basically does these things within a chroot.

1. debootstrap basic apps from Debian
2. Immediately after this, we remove all systemd packages out of debootstrap
3. Packages are installed from Debian and antiX repos
4. eudev replaces udev
5. squashfs file created (we call this linuxfs)
6. live system added to create bootable live iso.

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

antiX with runit - leaner and meaner.

I am using antiX 22 runit core. Attached inxi output.

Goal: I do not want the antiX base/full menu files created on generating an ISO for distribution.

After using iso-snapshot and boot or installing from the ISO, the /etc/skel directory contains .fluxbox/menu, .icewm/menu, and .jwm/menu. These were not present prior to using iso-snapshot nor was desktop-menu-antix installed.

Are these in fact created by iso-snapshot?
If true, can it be disabled using an “-x?”
Guidance on preventing or removing them would be appreciated.

iso-snapshot syntax I used to create the ISO.

iso-snapshot -c -r -s -z lz4 -x Desktop -x Documents -x Downloads -x Music -x Networks -x Pictures -x Steam -x Videos -x VirtualBox -f "$isoname"

Resulting /etc/skel.

ls -a /etc/skel/
./  ../  .config/  .fluxbox/  .gtkrc-2.0  .icewm/  .icons/  .jwm/  .xinitrc  .Xresources

dpkg-query results.

sudo dpkg-query -S /etc/skel/.fluxbox/menu
dpkg-query: no path found matching pattern /etc/skel/.fluxbox/menu

Edit: updated title

• This topic was modified 4 months ago by techore.
• This topic was modified 4 months ago by techore.
• This topic was modified 3 months, 3 weeks ago by Brian Masinick.

Attachments:

1. inxi.txt

[Moderator christophe]

andyprough wrote:

Up
0
I’m assuming you created an ~/.xinitrc file with the “exec jwm” or whatever window manager line to instruct startx what to do.

From my experience, if you only have one wm installed, startx will use it automatically (at least it works that way with jwm).

It’s probably a good way to do it (andyprough’s suggestion), so you can change it up in the future.

confirmed antiX frugaler, since 2019

[Moderator Brian Masinick]

andyprough wrote:

I’m assuming you created an ~/.xinitrc file with the “exec jwm” or whatever window manager line to instruct startx what to do.

One thing I didn’t note is that I did not use runit or Sid last night with my core installation. So it could be one of those like you said.

Yeah, I don’t know about that either. I’ve built antiX Core many times in the past, but with my current network availability, it’s difficult to find ANY wired network solutions around me anymore; therefore I generally need a setup with that built in; otherwise I’m forced to hack my solutions (which I’ve done too), but that takes too much time to do very often (unless I build tools to copy ALL of the stuff I need, and I haven’t done that).

I am, however, using a runit version of antiX 22 right now on my HP-14, and in fact, I had to hack in some firmware, a different kernel, and a few modules to get this one working too.
So yes, it CAN be done, but it takes work, and the specifics will VARY from system to system.

In my case, I needed a newer kernel to support my hardware; brought that in, didn’t work. Found that my wireless firmware was missing one file, brought the missing file in; STILL no go. So I went to MX Linux, which I believe was one of the distros working here, looked at everything it had in place, and literally copied every /lib/module, kernel related config and module files, anything else I could spot that interacted or mentioned the kernel or the wireless firmware I was using, and finally got it working; that’s a LOT of work that required hours of research. On top of that, REGULAR MX Linux doesn’t work either; I have to have the AHS (Advanced Hardware Support) stuff for newer images in order to get it working. PCLinuxOS, MX Linux AHS, and openSUSE have these; I got siduction working too; don’t remember if it worked immediately or if I had to do the same prep; seems to me I had to do it to something else; anyway, once I did it on this hardware, it was easier to copy it from a working system, but these kinds of issues are not exactly “portable” to fix; they can differ slightly for each hardware platform in question; some may work out of the box, others need tweaks.

That’s one positive of my Dell Inspiron 5558; it has always worked with my hardware AND software!

--
Brian Masinick

[Member andyprough]

I’m assuming you created an ~/.xinitrc file with the “exec jwm” or whatever window manager line to instruct startx what to do.

One thing I didn’t note is that I did not use runit or Sid last night with my core installation. So it could be one of those like you said.

[Member techore]

You have not provided details on what you have tried, but you may want to experiment with “xset s off; xset -dpms; xset s noblank” and disable any power management and screen saver. Once you got it working, tweak until satisfied.

I set xset, dpms, and xss-lock from ~/.xinitrc.

[Member stevesr0]

Hi male,

Thanks for comment.

my .xinitrc is:

#!/bin/sh
exec openbox-session

I believe that I need to do a fresh live install and since being root wasn’t helpful (and not advisable), I will go back to plain old demo. Need to review persistence before reinstalling.

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 Xaver]

So far I have not thought about getting rid of dbus too. Inspired by this thread I have done some research.
Dbus seems to be a severe security risk: https://vulmon.com/searchpage?q=dbus&sortby=byriskscore

Therefore I have checked, if my antiX-21-runit-sid (no elogind, polkitd policykit-1 or gvfs) would run without dbus too.
[compare: https://www.antixforum.com/forums/topic/antix-21-net-runit-sid_x64-with-seatd-3-problems-encoutered/ ]

First step was do put the runit debus service down. But this did not change much. dbus-daemon and dbus-launch were still running after reboot. Then I simulated a purge of dbus-daemon and dbus-x11:

# apt purge -s dbus-daemon dbus-x11

This would deinstall all xorg and most of my system – obviously not a good idea.

dbus-daemon and dbus-launch are running independently from the runit dbus service. How can I stop them.?
I have used a quite brutal method: disable them by changing their names:

renamed in /usr/bin/
dbus-launch –> dbus-launch_X
dbus-run-session –> dbus-run-session_X
dbusdaemon –> dbusdaemon_X 
then:
# apt-mark hold dbus dbus-daemon dbus-x11

Now no dbus is running, but all the dependencies to it are fufilled. Most software can be installed.
If needed, I can easily switch back to dbus.

What are the limitations?
Connman had to be replaced by Ceni. XFCE4-panel would not start (too bad – nice panel apps). Plank does work, but cannot be configured. Concerning the openbox desktop these are all the limitations which I have discovered so far.
My desktop consists of openbox, tint2, rofi, wmdrawer (a good and lighter replacement for plank) and spacefm (gtk2-version) with udevil.
Jgmenu does work fine too, but I prefer the openbox menu configured with obmenu2.
Login only works with .xinitrc – lxdm does not work.

Poweroff/Reboot with desktop-session-exit does not work regularly. I have to logout first and then shut down:

$ bash -c "openbox --exit && sudo poweroff"

Since polkitd is absent, there are dummies needed to fulfill policykit dependencies.
For that I have created and installed two dummies: policykit-1_99.9.9-9dummy and libpolkit-qt5-1-1_99.9.9-9dummy.
Most application can be installed now, even KDE stuff. But k3b cannot be installed, because it needs libsystemd0 and udisks2, which needs dbus.

Iso snapshot and persist do not show any problems.
Firefox-ESR and even Falkon are working fine and seem to be faster than on my antix-sysv-sid with dbus.
The whole system is a fully functional antiX and semms to be very fast and stable.

Only a few questions are still unresolved:

(1) Is there a more elegant way to keep dbus-daemon and dbus-launch from running than by renaming them?

(2) If I boot an iso-snapshot from usb, there is no network connection. I have to run Ceni in order to connect. Which setting have I missed?

(3) @ anticapitalista
You have stated, that LXDM would work without dbus. I get an error message:
[“Warning: dbus disabled by local settings”]
What is your trick to make LXDM work?

(4) lightdm gave me a hard time to deinstall it (pre-install script error). ‘dpkg-reconfigure lxdm’ still lists lightdm as an option. Where is this stored?

(5) Running from usb I sometimes notice high cpu load, when the system should be idle. The cause: lxtask indicates multiple instances of udevd. A restart of udevd service and then starting udevd again brings the system back to normal.
Research in the web clarfies, that this is a general udevd problem.
Is there any general cure?

• This reply was modified 8 months, 4 weeks ago by Xaver.
• This reply was modified 8 months, 4 weeks ago by Xaver.
• This reply was modified 8 months, 4 weeks ago by Xaver.