Another stable branch update with some usual package updates for you.
get a whopping 82% off + 2 months free on your subscription with Surfshark VPN
Recent News:
Manjaro, like many other open-source projects, relies on the generosity of its community through donations and corporate sponsorships to support its growth and development. These donations are essential in covering the various expenses incurred in the operations of the project such as server costs, software development tools, infrastructure expenses, training, flying people to events or conferences and the salaries of key developers. With the help of these donations, Manjaro is able to secure the necessary financial stability that allows the project to continuously improve and remain active. If you love Manjaro, consider to donate!
As you might have seen some of our team were able to attend FOSDEM 2023 and the conference proved to be incredibly productive for us. See our blog post for more.
Previous News
Finding information easier about Manjaro
Finding information easier about Manjaro always has been a topic that needed to be solved. With our new search we have put all Manjaro data accessible in one place and divided by sections so it makes it easier to digest: New Manjaro search engine is available | Blog
AUR (Arch User Repository) packages are neither supported by Arch nor Manjaro. Posts about them in Announcement topics are off-topic and will be flagged, moved or removed without warning.
We now have Gradience in the Manjaro community repo (also available as a Flatpak) for your theme customization pleasure. There are community presets (currently unavailable) available or you can create your own.
Our in-house Layouts Switcher application by @Chrysostomus has some new features as well as various improvements and fixes:
Check if the UUID of your encrypted drive matches in your config files.
Based on the manual, unlike filesystem UUIDs, UUIDs for encrypted devices must be specified without dash separators. So check /boot/grub/grub.cfg for entries like cryptomount -u 3722dfb2-3b32-414b-bd59-4329fa92b6a9 and try to remove the dash separators.
If you modified the above configuration, you then need to update the grub menu with sudo update-grub.
A message “no such cryptodisk found” may appear on the following reboot, but should not prevent you from continuing by typing any key.
You may still want to have a liveUSB ready, in the rare case your bootloader does break, in which case you will need to reinstall grub.
Switch to the base-devel meta package requires manual intervention
2023-02-12 - Robin Candau
On February 2nd, the base-devel package group has been replaced by a meta package of the same name.
If you installed the base-devel package group prior to this date, explicitly re-install it to get the new base-devel package installed on the system:
A solution, regarding to rob215x, is:
VLC would crash immediately when trying to play any video. I opened VLC directly, and changed Preferences > Video > Output from “Automatic” to “VDPAU” and it works now. I found that solution on another thread but I still don’t understand the problem and why VDPAU works.
2023-01-24
PHP 8.2 update and introduction of legacy branch
2023-01-13 - Pierre Schmitz
The php packages have been updated to the latest version 8.2. In addition to this, a new set of php-legacy packages have been introduced. These will follow the oldest but still actively supported PHP branch. This enables users to install the latest version but also introduces the option to use third party applications that might rely on an older version. Both branches will be kept up to date following our rolling release model. php and php-legacy can be installed at the same time as the latter uses a -legacy suffix for its binaries and configuration files.
In addition to this, the php7 packages have been removed as they reached end of life. The imap extension will no longer be provided as it relies on the c-client library which has been abandoned for many years.
dbus-x11 was installed out of the box on some flavors of Manjaro as of a year ago, but is no longer needed. If you have it installed, please replace it with dbus using the following:
sudo pacman -Syu dbus
XFCE becomes unusable if libxfce4ui-nocsd is still installed
So far XFCE Classic project hasn’t updated yet to 4.18 series. We pushed 4.17.0 version of the package, but don’t know if that helps in that situation. It is recommended to install the regular libxfce4ui package to avoid issues and comment on this issue: libxfce4ui 4.18.0 released · Issue #15 · Xfce-Classic/libxfce4ui-nocsd · GitHub
Well, from the previous and this update OBS lost libDeckLink.so and gives no such file or directory on it… May anyone help?
details
info: ---------------------------------
warning: Failed to load 'en-US' text for module: 'decklink-captions.so'
warning: Failed to load 'en-US' text for module: 'decklink-output-ui.so'
libDeckLinkAPI.so: no such file or directory
warning: A DeckLink iterator could not be created. The DeckLink drivers may not be installed
warning: Failed to initialize module 'decklink.so'
info: [pipewire] Available captures:
info: [pipewire] - Desktop capture
info: [pipewire] - Window capture
info: NVENC supported
zsh: segmentation fault (core dumped) obs
I have updated the mirrors, but there is no systemd update, as stated in the title of this thread.
I checked on Packages and is reported systemd 252.9-1: the same which I already have on the system:
There was a problem like this earlier this year and it seems to be related to some Nvidia drivers (I assume you have an nVidia GPU since the log states that NVENC is supported). For some people (me included) removing the libva-vdpau-driver package and replacing it with libva-nvidia-driver (from the AUR).
Others reported that a complete reinstall of nVidia drivers (switch to open-source driver → reboot system → switch to nvidia driver → reboot system) was the only way to solve it.
Here you can find the full thread: OBS-Studio not working after last update
Yes, it’s 1050 Ti, you’re right and I’m not sure at dealing with Nvidia drivers as I have had bad experience with it, but thank you for sharing that topic anyway. The only thing I didn’t try was using Snap/Flatpak versions, but I don’t really like to update them.
When I encountered this issue, switching to the Flatpak version sadly did not help. If you’re uncomfortable with changing the graphics driver - which I can fully relate to - I’d recommend replacing libva-vdpau-driver with libva-nvidia-driver. Even though the two packages are named “libva-something-driver” they are only involved with video en-/decoding, the odds of ending up with a system stuck at boot or broken display setup are very unlikely.
X11 is fully ■■■■■■■Using wayland for now as resetting all plasma settings didn’t help. If anybody found a solution on how to fix plasma while using x11 let me know.
As a last resort, I could do a full system rollback.
Hello everyone, the latest updates, yesterday, today created a problem that I have not yet figured out how to solve. Adding an Open VPN connection via a file(as usual), everything is ok, but after a reboot, the VPN connection disappears (as it never was). Deleted everything, re-created it, didn’t help. Does anyone know how this can be solved? Thanks
After the update, I started to have this weird issue, that I’m not sure how to troubleshoot.
When loading a YouTube video in firefox, the page loads fine, but there is no player or video.
Video playback works fine on other devices and when using mpv+ytdl.
So it’s not network issue.
Running in safe mode profile results in the same issue.
Not sure if this is the place to report it, but I guess it has something to do with mesa driver since I’m using hardware accelerated decoding.
EDIT:
Yup, switching to SW decoding solve it.
Not sure if anyone else is having the same issue.
chromium-112.0.5615.49-1-x86_64 89.0 MiB 576 KiB/s 02:38 [####################################################] 100%
Total ( 7/65) 406.4 MiB 2.56 MiB/s 02:39 [####################################################] 100%
error: failed retrieving file 'lib32-mesa-23.0.1-2.1-x86_64.pkg.tar.zst.sig' from mirror.alpix.eu : Operation too slow. Less than 1 bytes/sec transferred the last 10 seconds
error: failed retrieving file 'noto-fonts-20230401-1-any.pkg.tar.zst.sig' from mirror.alpix.eu : Operation too slow. Less than 1 bytes/sec transferred the last 10 seconds
warning: failed to retrieve some files
Hey @philm, I’m one of the users who are facing the no such cryptodisk found issue that doesn’t actually prevent boot (so pressing a key/waiting will trigger boot), I was wondering a couple things, sorry if I’m being thick:
Should I apply the 20230406 update if I’m still facing the issue, or am I supposed to have solved the issue first?
When you say check grub.cfg for entries like cryptomount -u 3722dfb2-... and try to remove the dash separators: does this advice apply to those who are still able to boot? I’m worried that doing this will cause the full-on boot-blocking issue in my case. I have tried the other solutions suggested (short of sudo grub-install) to no avail.
Chromium HW acceleration appears to be broken for me, but hopefully it will come back in a future update. No worries, I can wait for the fix from upstream.
Same issue here, Chromium does not manage to initialize graphics acceleration:
[42307:42307:0406/151139.659447:ERROR:angle_platform_impl.cc(43)] Display.cpp:1019 (initialize): ANGLE Display::initialize error 0: Internal Vulkan error (-3): Initialization of an object could not be completed for implementation-specific reasons, in ../../third_party/angle/src/libANGLE/renderer/vulkan/RendererVk.cpp, initialize:1654.
ERR: Display.cpp:1019 (initialize): ANGLE Display::initialize error 0: Internal Vulkan error (-3): Initialization of an object could not be completed for implementation-specific reasons, in ../../third_party/angle/src/libANGLE/renderer/vulkan/RendererVk.cpp, initialize:1654.
[42307:42307:0406/151139.659593:ERROR:gl_display.cc(504)] EGL Driver message (Critical) eglInitialize: Internal Vulkan error (-3): Initialization of an object could not be completed for implementation-specific reasons, in ../../third_party/angle/src/libANGLE/renderer/vulkan/RendererVk.cpp, initialize:1654.
[42307:42307:0406/151139.659643:ERROR:gl_display.cc(793)] eglInitialize SwANGLE failed with error EGL_NOT_INITIALIZED
[42307:42307:0406/151139.659684:ERROR:gl_display.cc(819)] Initialization of all EGL display types failed.
[42307:42307:0406/151139.659721:ERROR:gl_ozone_egl.cc(26)] GLDisplayEGL::Initialize failed.
[42307:42307:0406/151139.660053:ERROR:angle_platform_impl.cc(43)] Display.cpp:1019 (initialize): ANGLE Display::initialize error 0: Internal Vulkan error (-3): Initialization of an object could not be completed for implementation-specific reasons, in ../../third_party/angle/src/libANGLE/renderer/vulkan/RendererVk.cpp, initialize:1654.
ERR: Display.cpp:1019 (initialize): ANGLE Display::initialize error 0: Internal Vulkan error (-3): Initialization of an object could not be completed for implementation-specific reasons, in ../../third_party/angle/src/libANGLE/renderer/vulkan/RendererVk.cpp, initialize:1654.
[42307:42307:0406/151139.660116:ERROR:gl_display.cc(504)] EGL Driver message (Critical) eglInitialize: Internal Vulkan error (-3): Initialization of an object could not be completed for implementation-specific reasons, in ../../third_party/angle/src/libANGLE/renderer/vulkan/RendererVk.cpp, initialize:1654.
[42307:42307:0406/151139.660158:ERROR:gl_display.cc(793)] eglInitialize SwANGLE failed with error EGL_NOT_INITIALIZED
[42307:42307:0406/151139.660196:ERROR:gl_display.cc(819)] Initialization of all EGL display types failed.
[42307:42307:0406/151139.660234:ERROR:gl_ozone_egl.cc(26)] GLDisplayEGL::Initialize failed.
[42307:42307:0406/151139.661750:ERROR:viz_main_impl.cc(186)] Exiting GPU process due to errors during initialization
For now, downgrading back to Chromium 111 from the last release works just fine for me.
AUR (Arch User Repository) packages are neither supported by Arch nor Manjaro. Posts about them in Announcement topics are off-topic and will be flagged, moved or removed without warning.
2023-04-06
