Welcome to another stable update. So what do we have with this one?
- We updated systemd to set loglevel notice when quiet is set
- Calamares got updated accordingly incl. an important bug-fix
- Some more Deepin updates
- We updated firefox to v64b4
- Nvidia drivers are now at 410.73
- Some more bootsplash themes
- Added jdk 11
- Plane theme got updated
- We updated linux419 once more. Now we support more Netbooks
- Pamac got updated to 7.2.1
- Some more translations to manjaro-hello, still missing French and Dansk
- The usual upstream updates incl. python
We hope with all these changes Manjaro to be more efficient for you all.
Current supported Kernels
- linux316 3.16.59
- linux318 3.18.124 [EOL]
- linux44 4.4.162
- linux49 4.9.135
- linux414 4.14.78
- linux417 4.17.19 [EOL]
- linux418 4.18.16
- linux419 4.19.0
- linux414-rt 4.14.71_rt44
- linux416-rt 4.16.18_rt11
- linux418-rt 4.18.12_rt7-1
Package Updates (Sun Oct 28 17:44:24 CET 2018)
- stable community x86_64: 236 new and 233 removed package(s)
- stable core x86_64: 13 new and 10 removed package(s)
- stable extra x86_64: 108 new and 101 removed package(s)
- stable multilib x86_64: 8 new and 8 removed package(s)
A detailed list of all changes can be found here.
- No issue, everything went smoothly
- Yes there was an issue. I was able to resolve it myself.(Please post your solution)
- Yes i am currently experiencing an issue due to the update. (Please post about it)
Check if your mirror has already synced:
#bladebook - shipping to Switzerland this fall!
Currently we are working on a new Manjaro-Hardware project, the Bladebook Fall 2018. It will be powered by Manjaro KDE v18.0 and the latest Intel Apollo Lake Quad-Core HD APU. Having a fanless metal material (cassis gold-rose), a eMMC as storage (additional M2-SSD possible) and will have a long battery life. You can now pre-order your #bladebook when you live in Switzerland. We will start shipping in CW46 and will take orders from you in CW44. Find out more on our hardware page or the shop.
Manjaro v18.0 released!
We finally made it. Manjaro-Illyria 18.0 got released.
The Xfce edition remains our flagship offering and has received the attention it deserves. Few can claim to offer such a polished, integrated and leading-edge Xfce experience. We ship Xfce 4.13 with this release of Manjaro.
We mainly focused on polishing the user experience on the desktop and window manager, and on updating some components to take advantage of newly available technologies such as switching to a new theme we call Adapta-Maia. The new feature Display-Profiles allows you to store one or more profiles for a particular display configuration that you may be using. To make the deal a little sweeter we implemented auto-applying of profiles when new displays are connected.
Our KDE edition continues to deliver this powerful, mature and feature-rich desktop environment with a unique look-and-feel, and with the perks of Manjaro’s latest tools. We ship now Plasma 5.14 desktop in combination with the latest KDE-Apps 18.08. There’s a new Display Configuration widget for screen management which is useful for presentations. Switching primary monitor when plugging in or unplugging monitors is now smoother. The Network widget now works for SSH VPN tunnels again. The Audio Volume widget now has a built in speaker test feature moved from Phonon settings and Plasma now warns on logout when other users are logged in.
Kernel 4.19 LTS is used for this release, such as the latest drivers available to date. Relative to the last installation media release, our tools have been improved and polished.
The Manjaro Settings Manager (MSM) now provides an easy-to-use graphical interface for installing and removing the many series of kernels we offer. Manjaro’s selection of readily available kernels remains the most extensive of all Linux distribution we know of. At the time of this release, eight kernel-series are available directly from our binary repositories, ranging from the mature & rock-solid 3.16 series to the latest 4.19 release. Additionally we offer three realtime kernel series. Such a wide array of available kernel options results in extensive hardware support, getting the most out of your system for you, be it old or new.
With Pamac v7.2 we fixed known issues and added new functions. Followed features you can expect:
- pamac-gtk: add edit build files support
- pamac-cli: add edit build files support
- pamac-cli: add clone action
- pamac-cli: build action now has an --no-clone option to only use local build files
- pamac-cli: build action without argument now tries to build from the PKGBUILD in the current dir
- pamac-cli: added a CLI mode to pamac, which acts similar to apt-get
With Manjaro Hello we added new functions. Followed features you can expect:
- you can now maintain suggested packages by the community directly in the welcome screen under the applications option
- UI enhancements
- updated translations
We hope you enjoy this release and let us know what you think of Illyria.
Known issues with v18.0 release
- XFCE: In the settings Manager, the mouse fails to scroll apps in settings manager (GTK+ 3 regression)
- Calamares: may delete partitions during disk-probe in really rare conditions. bug, talk
Changes made to pamac
With v7.2.1, Pamac has the ability to edit build files in both pamac-gtk and pamac-cli.
But it’s not the only one improvement, pamac-cli is now a complete AUR helper and an advanced build tool:
Tracking build files:
It now keeps all build files in the configured pamac build dir that is now
This way it can track when a new version is available from AUR or if changes were made by yourself and propose you to view the diff.
Pamac now has a
cloneaction and build has a
--no-cloneoption. They permit to ease building a package when you want to do important manual modifications.
How to use it ?
If a standard
pamac build foodoes all automatically you can do it step by step:
Clone the build files with all dependencies :
pamac clone --recurse foo
Edit them as you want, then :
pamac build --no-clone foo
Or go the foo directory and run:
pamac build --no-clone
You can even create your own PKGBUILD files and build them with:
pamac build --no-clone --builddir /my/build/dir <pkgname>
or in the PKGBUILD directory:
pamac build --no-clone
If there are dependencies to build, all files must be in the same directory with one subdir per package.
All dependencies will be checked and the correct build order will be found.
Changes made to grub package
1. What is the GRUB hidden menu change?
The main motivation for adding this is, to get to a fully flickerfree boot.
2. How to enable hidden GRUB menu?
On new Manjaro v18.0 installs this will be enabled by default. If your system has been upgraded to v18.0 from an older release, you can enable it by running these commands:
- update your system to get latest systemd
- install linux418 or linux419:
sudo pacman -S linux41[x]
- check that you have
GRUB_CMDLINE_LINUXand comment out any
sed -i -e 's|fsck||g' /etc/mkinitcpio.conf && sudo pacman -S systemd-fsck-silent
- You may want to consider early kms and fastboot for intel hardware
sudo mkinitcpio -P
sudo grub-editenv - set menu_auto_hide=1
- reboot your system
Note the grub-update will overwrite any manual changes you’ve made to your grub.cfg (normally no manually changes are done to this file).
If your system has Windows on it, but you boot it only once a year so you would still like to hide the GRUB menu, you can tell GRUB to ignore the presence of Windows by running:
sudo grub-editenv - set menu_auto_hide=2
3. How to disable hidden GRUB menu
To permanently disable the auto-hide feature run:
sudo grub-editenv - unset menu_auto_hide
That is it.
4.How to access the GRUB menu when hidden
If for some reason you need to access the GRUB menu while it is hidden there are multiple ways to get to it:
While booting keep SHIFT pressed, usually you need to first press SHIFT when the vendor logo is shown by the firmware / when the firmware says e.g. “Press F2 to enter setup” if you press it earlier it may not be seen. Note this may not work on some machines.
During boot press ESC or F8 while GRUB loads (simply press the key repeatedly directly after power on until you are in the menu).
Force the previous boot to be considered failed:
Press CTRL + ALT + DEL while booting so that the system reboots before hitting the display manager (lightdm, gdm, sddm)
Press CTRL + ALT + F6 to switch away from your display manager, followed by CTRL + ALT + DEL.
Press the power-button for 4 seconds to force the machine off. Either of these will cause the
boot_successgrub_env flag to not get set and the menu will show the next boot.
Manually set the menu show once flag by running: "grub-set-bootflag menu_show_once" This will cause the menu to show for 60 seconds before continuing with the default boot-option.
4. When is a boot considered successful ?
boot_success grub_env flag gets set when you login as a normal user and your session lasts at least 2 minutes.
So if you e.g. login, do something and then within 30 seconds type reboot in a terminal (instead of doing the reboot from the menu) then this will not count as a successful boot and the menu will show the next boot.