Search Results for 'xinitrc'

[Member zeh]

Hi Jim,

1)
/tmp in / (with plenty of space)
File properties, Permissions Tab:
Owner: root
Group: root
permissions rwx , rwx , rwx / –S

2) /media/home/axTest/.Xauthority
File properties, Permissions Tab:
Owner: root
Group: root
permissions rw- , — , — / —

3)
From slim.conf (before and after reinstallation)
default_path /usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
default_xserver /usr/bin/X11/X
xserver_arguments -nolisten tcp

4)
xinitrc
/media/rootaXTest/etc/X11/xinit/xinitrc
File properties, Permissions Tab:
Owner: root
Group: root
permissions rwx , r-x , r-x / —

Restarted after having reinstalled slim. No difference:
blank screen, Ctrl+Alt-F1 gives me the system in text mode (before I said CLI, meaning the same – system in text mode). ‘startx’ produces errors and ‘sudo startx’ gives me icewm in root session (with a different menu, no background image, no access to fluxbox or JWM).

Restarted again after having renamed xinitrc:
blank screen, Ctrl+Alt-F1 gave me the system in text mode; ‘sudo startx’ didn’t give me icewm, rather a black screen and a terminal. I could launch apps from the terminal (root mode) – synaptic, spacefm, palemoon – which ran with some interface limitations (e. g., no window menu).
Restarted once again ater having renamed the file back to xinitrc – could start icewm with ‘sudo startx’ as before.

Regards,
Zeh

[Member wildstar84]

The fact that you got X to start up at all is a good sign. I’ve never had much luck in Antix w/startx. I just always use the default runlevel 5 which should start up X on it’s own. A cpl. more things to check

1) Where is /tmp set up – ramdisk, or in root (and it’s not full/has plenty of space)? Make sure it’s permissions 777 (so that X run as you can create temp. files, etc.

2) Make sure your .Xauthority file isn’t somehow owned by root, but by you (I’ve had root take ownership of it before, perhaps by running X as root, as you did?).

3) Perhaps, reconfigure or reinstall slim, perhaps it’s config file (/etc/slim.conf) isn’t right?

4) If you have a .xinitrc file, perhapes check / rename it (to try not using it). I still think that starting up the normal way (no “startx”) and it drops you to a terminal login-prompt SHOULD put some useful error messages in /var/log/Xorg.0.log or slim.log or auth.log which should give some clue as to why X failed to start as user.

Those are the only things I can think of for now.

Regards,

Jim

[Anonymous]

Why on the ArchWiki they says:

Warning: The SliM project has been abandoned (last release was 2013, the project homepage is down), and is not fully compatible with systemd, including logind sessions. Consider using a different Display manager or Xinitrc.

arch-linux is not debian
https://packages.debian.org/search?keywords=slim&searchon=names&suite=all&section=all

[Member lucbertz]

Thank you, Dave.

Be aware, I’d like to understand, not to judge or say what to do to anyone. antiX is really good: reliable, fast and solid. In order to learn and to keep all extremely simple, I would like to start from core.

I understand there is nothing wrong in antiX SLiM package; in fact it works smoothly in the base distribution.
I ask why not to change the slim package name with “antix” as prefix or suffix or why not to add the customized slim configuration file in desktop-session-antix package.

The matter in my case is only in /etc/slim.conf . In the end I will reinstall the antiX slim package, keeping the configuration coming from Stretch, which works smoothly.

Why on the ArchWiki they says:

Warning: The SliM project has been abandoned (last release was 2013, the project homepage is down), and is not fully compatible with systemd, including logind sessions. Consider using a different Display manager or Xinitrc.

Source: https://wiki.archlinux.org/index.php/SLiM

[Forum Admin Dave]

As far as I know there is nothing wrong with the antiX slim other than in your case, the default login_cmd uses desktop-session. So in a core build you would either keep it the same and install desktop-session-antix or comment that login_cmd and remove the comment for the xinitrc login_cmd in /etc/slim.conf

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

[Anonymous]

Do you have a .xinitrc file in your home directory?

In a recent discussion, antiX-Dave mentioned that ~/.xinitrc is not sourced during normal antiX operation (telinit 5)

[Member fungalnet]

But startx worked before you shifted to testing?
It might be that you were asked somewhere to keep your previous .conf file or install the distribution’s version and you may have kept something incompatible. What if you try to reinstall xorg xorg-xinit your desktop or window manager.
Do you have a .xinitrc file in your home directory?
What about xf86-video-intel

• This reply was modified 4 years, 3 months ago by fungalnet.

anti-X - Adélie - obarun - systemd Free Space

[Moderator Brian Masinick]

Dave wrote:

I don’t think .xinitrc is used and as such caprea’s suggestion would be the correct replacement file.

I am thinking that perhaps bash is not being loaded when a terminal is opened… this would be visible by the user prompt not being colourful and showing the path. You can verify if this is the case by typing “bash” as the first command in terminal and see if it makes a difference. If it does then /bin/bash likely needs to be specified in /etc/passwd as the user shell.

If that is the case, you may also be able to add commands to .bashrc

If so make sure they run only in the interactive invocation of the Bash resource file .bashrc.

Otherwise non-interactive scripts could be adversely impacted.

--
Brian Masinick

[Forum Admin Dave]

I don’t think .xinitrc is used and as such caprea’s suggestion would be the correct replacement file.

I am thinking that perhaps bash is not being loaded when a terminal is opened… this would be visible by the user prompt not being colourful and showing the path. You can verify if this is the case by typing “bash” as the first command in terminal and see if it makes a difference. If it does then /bin/bash likely needs to be specified in /etc/passwd as the user shell.

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

[Moderator Brian Masinick]

Anonymous wrote:

results of a quick websearch “session setxkbmap” indicate adding that line into ~/.xinitrc should be effective

That makes good sense since it is a keyboard mapping that activates with the X server, therefore initialize it in the X init file, a.k.a. .xinitrc.

--
Brian Masinick

[Anonymous]

results of a quick websearch “session setxkbmap” indicate adding that line into ~/.xinitrc should be effective

[Anonymous]

That line is in the desktop session configuration. Enabling it should make desktop-session start the autostart items without dex.

But doing so would seem to bring an all-or-nothing scenario:
per user FULL opt-out via placement of ~/.noxautostart (i can’t recall the exact flagfile name)
or
user winds up with “all sorts of crap” being autostarted, due to entries placed in the system-wide dir by various package installers

Ability to selectively ignore the “all sorts of crap” is the reason I chose dex.
Maybe (didn’t bother testing) xdg supports per-user shunting of individual entries, checking whether a locally placed same-named .desktop file exists and the local copy contains a restrictive NoDisplay=True (or similar) line? Even so, coding the “easy peasy GUI” would require tomjiggery and would be prone to edge-case breakage. (“Sorry, a .desktop file named ‘spacefm.desktop’ already esists. Choose a different name”, or “Sorry, a .desktop file with a localized ‘Comment’ matching ‘blahblah’ already exists”, or other silly conditional-checking)

skidoo wrote:
https://www.antixforum.com/forums/topic/is-it-safe-to-install-the-budgie-desktop-from-the-repos/#post-14402

the capability is there but is essentially ignored by antiX the desktop-session mechanism. Thankfully so, IMO ~~ too often, individual programs silently install “all sorts of crap” to the system-wide dir. Begs ongoing maintenance b/c after deleting the items you don’t want… checks performed each time an installed package is upgraded are prone to REinject its autostart entry(ies).

/etc/xdg/autostart/
~/.config/autostart/
https://specifications.freedesktop.org/autostart-spec/0.5/ar01s02.html
IIRC, contents of the per-user directory SUPPLEMENT (they do not OVERRIDE) the system-wide entries

see also:
https://wiki.debian.org/Xinitrc
https://wiki.debian.org/Xsession

[Anonymous]

like the Startup folder in the Windoze world

BobC, the capability is there but is essentially ignored by antiX the desktop-session mechanism. Thankfully so, IMO ~~ too often, individual programs silently install “all sorts of crap” to the system-wide dir. Begs ongoing maintenance b/c after deleting the items you don’t want… checks performed each time an installed package is upgraded are prone to REinject its autostart entry(ies).

/etc/xdg/autostart/
~/.config/autostart/
https://specifications.freedesktop.org/autostart-spec/0.5/ar01s02.html
IIRC, contents of the per-user directory SUPPLEMENT (they do not OVERRIDE) the system-wide entries

see also:
https://wiki.debian.org/Xinitrc
https://wiki.debian.org/Xsession

good/easy way to select and edit desktop files

Which is easier:
mess with creating/editing/placing myriad .desktop files into /etc/xdg/autostart/ and ~/.config/autostart/ (and babysit those dirs)
or
edit launchstring lines within the antiX -provided centralized “startup” file?

if they would need to be different depending on which window manager

In antiX, it’s your choice. If you WANT a given item to autostart only upon launching fluxbox, you can do so.
(within the general “startup” file, wrap an item’s launch command within a conditional statement, or edit the fluxbox-specific configfile)

[Member ex_Koo]

This is in reply to male asking to change the default desktop.

(Just found an easier way.
/home/you/.desktop-session/default-desktop = change to fluxbox reboot fluxbox is now your default..)

You can easily change your default log in desktop yourself. etc/slim.conf

# Available sessions (first one is the default).
# The current chosen session name is replaced in the login_cmd
# above, so your login command can handle different sessions.
# see the xinitrc.sample file shipped with slim sources
sessions rox-fluxbox,space-fluxbox,fluxbox,herbstluftwm,i3,i3_with_debug_log_,rox-icewm,space-icewm,icewm,rox-jwm,space-jwm,jwm

And in the same file. = Are over typing your user name & password every time you log in to your desktop with slim.
Then do this for password only..

# Focus the password field on start when #default_user is set
# Set to "yes" to enable this feature
focus_password      yes

# Automatically login the default user (without entering
# the password. Set to "yes" to enable this feature
#auto_login          yes

# default user, leave blank or remove this line
# for avoid pre-loading the username.
default_user        koo

To learn about i3 here are some Great Video

Code Cast i3 videos (Great to learn i3)

Luke Smith more Advanced i3 (GOD)

• This reply was modified 4 years, 5 months ago by ex_Koo.
• This reply was modified 4 years, 5 months ago by ex_Koo.
• This reply was modified 4 years, 5 months ago by ex_Koo.

[Member ex_Koo]

Anonymous wrote:

Apparently I understand only station here…

How can I recommend i3 after manjaro to a beginner? The developers of antiX could also set fluxbox as default Desktop…

You can easily set what ever default desktop you wish in AntiX just by editing a file.
etc/slim.conf

# Available sessions (first one is the default).
# The current chosen session name is replaced in the login_cmd
# above, so your login command can handle different sessions.
# see the xinitrc.sample file shipped with slim sources
sessions rox-fluxbox,space-fluxbox,fluxbox,herbstluftwm,i3,i3_with_debug_log_,rox-icewm,space-icewm,icewm,rox-jwm,space-jwm,jwm

And in the same file. = Are over typing your user name & password every time you log in to your desktop with slim.
Then do this for password only..

`
# Focus the password field on start when #default_user is set
# Set to “yes” to enable this feature
focus_password yes

# Automatically login the default user (without entering
# the password. Set to “yes” to enable this feature
#auto_login yes

# default user, leave blank or remove this line
# for avoid pre-loading the username.
default_user koo

Also have a look in your home folder .desktop-session folder lots of .conf to play with here. Just backup the folder first Just in case of an opps..

I would always recommend i3 to new users…

Code Cast i3 videos Great to learn i3

Luke Smith more Advanced i3 (GOD)

I have used manjaro i3 myself very nice indeed.But I would install i3 from debian buster server onto AntiX anytime over using manjaro as their kernel updates can be pretty unstable at times.
Who ever builds the kernels for AntiX you are my Stable Hero.

• This reply was modified 4 years, 5 months ago by ex_Koo.
• This reply was modified 4 years, 5 months ago by ex_Koo.