Minor glitch, battery widget shows double mouse entries.
Minor glitch, battery widget shows double mouse entries.
This will be a huge change for people who wants to have dual booting, like the classic Manjaro/Windows dual boot. This is not really a bug in itself, as it is intentionally disabled and not by accident because of a programming error, but this choice means that people won’t be able to boot Windows from GRUB, which is something that we were usually able to do on Manjaro and with Linux OS in general and somehow has become the “de facto” standard in term of behavior.
Manjaro will most likely suffer from this choice for a time, and I do expect a lot of complains from the users, outcrying that “MY DUAL BOOT IS BROKEN CAN’T BOOT TO WINDOWS” or even worse, “OH MY GOD MANJARO DELETED WINDOWS HOLY CRAP” simply because they can’t see Windows in GRUB anymore.
Plus, any new user trying to do a dual boot will have an unpleasant surprise that they have to change the configuration of GRUB in order to have access to GRUB inside Windows, and I am afraid that Manjaro will be compared to Ubuntu, Linux Mint, etc., where it still works as it used to be (although there is no guarantee that it won’t change in the future).
For people that use UEFI, you can still boot Windows manually by selecting it in the boot override menu or whatever, although it is much less convenient than selecting it from GRUB I suppose.
I know it has been disabled for security reasons. But disabling it is not without consequence. Hopefully users will be able to accept this new reality. I would understand if Manjaro devs revert their decision for the sake of convenience and user-friendliness though.
Of course, people that use Manjaro as their only operating system has nothing to fear from this change, obviously.
EDIT: Just noticed that it was already a thing in Stable, which would explain (partly perhaps) the relatively bad result in the pool. My bad.
Dual boot on 2 separat nvmes and you are Safe
@pheiduck You would still have to go in the UEFI to manually select your OS, right?
Yep, in my workflow it is the best way, I don’t want to mix partitions on a Single drive and fixing issues at night when the System won’t boot because Windows Overwrites something
Linux chaplindev-arch 5.11.4-1-MANJARO #1 SMP PREEMPT Sun Mar 7 16:15:35 UTC 2021 x86_64 GNU/Linux NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.56 Tue Feb 23 23:31:36 UTC 2021
Just updated, so far so good as expected, Thanks Manjaro Team :). Just some logs from jornalctd but does not interrupt the PC performance so far:
Its depressing just how many threads there have been since yesterday "my grub is broken ". Is it really that difficult to read the update thread before or even after you update?
Unfortunately, there are more people who have the money to buy a computer than people who have the brains to use it.
Well then. If Manjaro really does dualboot
so difficult, it’s probably time to say goodbye.
Is like with windows.
I’m on kde but using openbox instead of kwin. I use krunner to search window titles. With the update, it has stopped working. I type, but it doesn’t autocomplete window titles anymore. Maybe it depends on kwin now? Anyone knows?
This started happening after the update. Not sure if it’s related
but it’s not difficult. read the 2nd post and you’re golden.
Some days ago I said Good Bye to Windows and dual booting, just Manjaro as main/unique system. Nothing more needed.
I don’t see the relationship between the grub developers and Manjaro…
never mind. switched to rofi instead of worrying about a fix. But a pity, krunner is nice
Couldn’t care less about this decision… in fact I applaud it. Haven’t had to boot to windows and not being there in grub as a reminder is awesome.
As already said elsewhere: This is an upstream decision, i.e. set by the Grub developers themselves, not Manjaro.
Hence, you will surely encounter the same situation with other distributions using Grub as well.
The solution is as simple as editing
/etc/default/grub with root privileges, manually adding the line
/etc/default/grub (or modifying that line accordingly if already present).
sudo update-grub, and you’re done
A post was split to a new topic: Grub2 | Secure Boot Bypass 2021 - Update highly recommended
Today, another update arrived:
[2021-03-10T20:24:30+0100] [ALPM] upgraded cryptsetup (2.3.4-2 -> 2.3.4-3) [2021-03-10T20:24:30+0100] [ALPM] upgraded git (2.30.1-1 -> 2.30.2-1) [2021-03-10T20:24:31+0100] [ALPM] upgraded grub (2.04-19 -> 2.04-21) [2021-03-10T20:24:31+0100] [ALPM] upgraded iso-codes (4.5.0-1 -> 4.6.0-1) [2021-03-10T20:24:31+0100] [ALPM] upgraded liblouis (3.16.0-1 -> 3.17.0-1) [2021-03-10T20:24:33+0100] [ALPM] upgraded linux510 (5.10.21-1 -> 5.10.22-1) [2021-03-10T20:24:38+0100] [ALPM] upgraded linux510-headers (5.10.21-1 -> 5.10.22-1) [2021-03-10T20:24:38+0100] [ALPM] upgraded linux510-nvidia-390xx (390.141-24 -> 390.141-25) [2021-03-10T20:24:47+0100] [ALPM] upgraded linux511 (5.11.4-1 -> 5.11.5-1) [2021-03-10T20:24:53+0100] [ALPM] upgraded linux511-headers (5.11.4-1 -> 5.11.5-1) [2021-03-10T20:24:53+0100] [ALPM] upgraded linux511-nvidia-390xx (390.141-7 -> 390.141-8) [2021-03-10T20:25:02+0100] [ALPM] upgraded linux54 (5.4.103-1 -> 5.4.104-1) [2021-03-10T20:25:09+0100] [ALPM] upgraded linux54-headers (5.4.103-1 -> 5.4.104-1) [2021-03-10T20:25:11+0100] [ALPM] upgraded linux54-nvidia-390xx (390.141-17 -> 390.141-18) [2021-03-10T20:25:19+0100] [ALPM] upgraded os-prober (1.78-0 -> 1.78-0.1) [2021-03-10T20:25:19+0100] [ALPM] upgraded smbclient (4.13.4-1 -> 4.13.5-1) [2021-03-10T20:25:19+0100] [ALPM] upgraded samba (4.13.4-1 -> 4.13.5-1)
So far, no problems. Good work, thank you very much!
I came up with the solution to the problem myself, but I still find it annoying to have to make manual changes after every update that contains Grub.
People who know less are then first of all lost.
So sorry again, I was not sufficiently informed then.