Notable Changes: Packages updated for the live and minimal install environments.
Click here to see the full blog post
Is the lightdm failed to start issue for intel machines solved with this?
If someone is interested or need 4.14 kernel to boot i just rebuild the nvidia-Antergos-ISO:
I found a bug and some werid stuff in the new Antergos release:
~/.e/ewhich seems weird
bashrcfile should be
.bashrc, that way the alias are not working
EDIT: VBox bug is fixed!. Congratulations @developers ! I just tested both Gnome and XFCE4!
Item 3 about bashrc: I agree separation between bashrc and .bashrc is not really needed.
In general, I’d prefer the default contents of .bashrc to be very minimal, containing only things that are very important to have, but no personal tweaks. Some examples of personal tweaks are OK, provided they are initially commented out!
Personal tweaks are a matter of the user.
In the new ISO, for Xfce, so far the only slight “downgrade” is that xfce4-whiskermenu-plugin is no more installed by default. Naturally it can easily be installed from the repos.
Otherwise I’m pleased with the result.
Mostly all this stuff is done by cnchi, so not related to the ISO itself.
As cnchi will be updated independently.
Cnchi Antergos - GitHub
So it would help @developers to create bug report there too, on this issues.
Item 3 about bashrc: I agree separation between bashrc and .bashrc is not really needed
I know it’s possible to have another file only with alias, but in this case they are not working, so i guess the files was named incorrectly… Anyway something is causing alias to fail…
You can make aliases in ~/bashrc work by writing this to the end of ~/.bashrc:
if [ -e ~/bashrc ] ; then source ~/bashrc fi
Is this what you meant?
yes, but it was not working right after install (out of the box) under Antergos yesterday when i tried. I deleted the virtual machine already so i cant test it again.
There should not be a bashrc file, it’s a bug (from antergos-desktop-settings), but tbh, it’s not harmful.
.bashrc should be ok… can you guys post its contents here so we can check it’s ok?
XFCE should be themed, this is really a bug. To be honest, we do not test all DE’s with each release… as each release happens once a month, it would require a lot of effort from our part.
We’ll do some tests and fix XFCE setup asap.
Thanks for reporting it!
can you guys post its contents here so we can check it’s ok?
i need to install it again here since i removed the vm, but is something like:
# # ~/.bashrc # # If not running interactively, don't do anything [[ $- != *i* ]] && return alias ls='ls --color=auto' PS1='[\[email protected]\h \W]\$ ' # >>>>BEGIN ADDED BY CNCHI INSTALLER<<<< # BROWSER=/usr/bin/chromium EDITOR=/usr/bin/nano # >>>>>END ADDED BY CNCHI INSTALLER<<<<< #
The alias are in the
bashrc file which is not being called inside
# # ~/.bashrc # # If not running interactively, don't do anything [[ $- != *i* ]] && return alias ls='ls --color=auto' PS1='[\[email protected]\H \W]\$ ' alias pacrepo='sudo reflector -l 20 -f 10 --save /etc/pacman.d/mirrorlist' alias pacman='sudo pacman' alias journalctl='sudo journalctl' alias pacu='sudo pacman -Syu --noconfirm' alias auru='yaourt -Syua --noconfirm' alias systemctl='sudo systemctl' alias se='ls /usr/bin | grep' export EDITOR=nano export QT_STYLE_OVERRIDE=gtk export QT_SELECT=qt5 if [[ $LANG = '' ]]; then export LANG=en_US.UTF-8 fi
# # ~/.bash_profile # [[ -f ~/.bashrc ]] && . ~/.bashrc
at the end the only problem is that file is being created as bashrc instead of .bashrc
a single dot changed everything hehehe
It’s not that simple!
.bashrc comes with the bash package, so it cannot be modified by another package (
That’s why it was called
bashrc. The problem is a bad chosen name… I’ve renamed it to
.bashrc.aliases as some of you suggested.
I’ve also modified Cnchi to modify
.bashrc itself, to load
.bashrc.aliases if it exists.
If you have a
bashrc file in your home (without the starting dot!) and you don’t need the aliases you can simply delete it.
Looks like your connection to Antergos Community Forum was lost, please wait while we try to reconnect.