How do you figure? We have 1.3.0+47+gb02ebf5-1, not 1.3.0.
EDIT: It seems the Pop!_OS packages use later commits. They added SHA1 support, bumped some dependencies and updated a few translations since January. I just pushed 1.3.0+56+ge208056-1.
How do you figure? We have 1.3.0+47+gb02ebf5-1, not 1.3.0.
EDIT: It seems the Pop!_OS packages use later commits. They added SHA1 support, bumped some dependencies and updated a few translations since January. I just pushed 1.3.0+56+ge208056-1.
also give a spin to the ventoy
app: it let you to forget to “burn” ISOs and just copy in any file manager instead and also you will forget to have only single ISO on a drive.
PS it supports many images but not every.
Ventoy is really useful. The only ISO that couldn’t be started with ventoy that I came across was ChromeOS.
Here is a workaround if suspend does not work on stable Kernels:
https://wiki.archlinux.org/title/Bluetooth#Bluetooth_immediately_waking_up_suspend-to-idle_devices
[Edit]
Power off / Reboot as no function if this is applied
… and network does not reconnect
With today’s update, does kwrite really conflict with kate now?
Anyone aware of requiring shellcheck
package now for Konsole 22.08 on Plasma when wanting to use quick commands plugin?
Found that:
now kate
provides both kate & kwrite, so win-win
Changes with Back In Time packages as of 1.3.2-3
backintime
has been renamed to backintime-qt
backintime-cli
has been renamed to backintime
After replacing backintime-cli
with backintime
, you will need to install backintime-qt
manually if you want the Qt frontend installed again.
We we’re able to isolate the restart and shutdown issue. In Arch (June 1st ISO), the splash screen message on Kernel 5.19.3 (restart only) was about network and mirrors list refresh. We are not using Ethernet, turn it OFF in the BIOS removes the bug.
All is good now.
pacman -Qii linux60
Name : linux60
Version : 6.0.0rc2-1
Description : The Linux60 kernel and modules
Architecture : x86_64
URL : https://www.kernel.org/
Licenses : GPL2
Groups : None
After steam package replaced steam-manjaro, I had to mark the former as explicitly installed, since it was marked as orphan.
I’m aware of that. My point is that the new package wasn’t set as ex·plic·it·ly installed as it was steam-manjaro.
The name is not my point!
Seems like an anomaly; mine is explicitly installed.
Thanks, @Jaypee. I appreciate your kindness for checking it out.
In other news, networkmanager 1.40 has reached us.
@Yochanan out of curiosity, does manjaro ship its kernels with Multipath TCP enabled?
For the grub update do I need to boot iso to do:
grub-install …?
What grub update?
The Package update Bro