Another testing branch update with some usual package updates for you.
Recent News:
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:
This is a wiki post; please edit as necessary.
Please, consider subscribing to the Testing Updates Announcements RSS feed
Please RTFT (Read This Fine Thread) first before reporting the same issues over and over again!
2023-03-03
2023-02-10
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:
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.
The issue is caused by update libx11 1.8.3-4 The solution: Upgrade to libx11 1.8.3-5
VLC crashes when playing a video file
It looks like there has been a regression introduced with the new version of libva (2.17.0), which is used by VLC media player. If you get the following error when executing vlc in a terminal:
you may try to change the Output option in Preferences > Video to VDPAU output instead of Automatic (or whatever value it had been set to before).
Downgrading the libva package from 2.17.0-1 to 2.16.0-1 may also work, but it is a more short-term workaround that should not be kept for too long, as sooner or later, the older package won’t be compatible with the other packages. Consider to do the solution above first.
2022-12-22
pacman-mirrors was temporarily renamed to manjaro-mirrors (the changes were reverted)
This was done to avoid confusion with an AUR / WSL package with the same name and avoid possible breakage. It should be a seamless transition.
Downgrade it to mesa 22.2.4 to resolve this issue.
2022-12-16
dbus-x11 demoted to AUR
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
The python-cairo package prior to version 1.23.0-2 was missing the compiled python module. This has been fixed in 1.23.0-2, so the upgrade will need to overwrite the untracked pyc file that was created. If you receive this error
python-cairo: /usr/lib/python3.10/site-packages/cairo/__pycache__/__init__.cpython-310.pyc exists in filesystem
signature from "Manjaro Build Server <build_at_manjaro_dot_org>" is unknown trust
Seems our signing key for our Build Server had the 2022-10-28 as expire date set when generated. This is now fixed for chroot builds and fresh as also current existing installs via manjaro-keyring 20221028-4 Simply update your system to get that package, which got pushed to all our branches.
2022-10-27
Kernel 6.1-rc# might break backlight control on old/weird laptops
Python 2 went end of life January 2020. Since then we have been actively cutting down the number of projects depending on python2 in our repositories, and we have finally been able to drop it from our distribution. If you still have python2 installed on your system consider removing it and any python2 package.
If you still require the python2 package you can keep it around, but please be aware that there will be no security updates. If you need a patched package please consult the AUR, or use an unofficial user repository.*
* Note: Unofficial user repositories are not supported
2022-08-27
Changes with Back In Time packages
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.
2022-08-23
electron12, electron13, electron14 & electron16 have been dropped to the AUR
Unsupported Electron packages have been dropped from the official repos to the AUR. They no longer receive security updates and nothing in the repos depend on them.
If you have AUR packages depending on those versions, install the binary version from the AUR to replace them; i.e., electron16-bin.
Electron 15.x.y and 16.x.y has reached end-of-support. As per Electron’s new 8-week cadence, we were supporting the latest four versions of Electron until May 2022. With this Electron 19 release, we’ll return to supporting the latest three major versions, as well as the alpha, beta, and nightly releases.
By chance we discovered that the touchscreen on our Acer Spin 3 now works. I’d given up long ago on it working and my daughter happened to wipe something from the screen and told me the UI reacted and I confirmed by closing her browser on her (lol don’t worry, she could ‘Restore Previous Session’) so I’ve no idea when it started working.
After this update fragments would start with an error in the application stating that there was no write acces to the downloads folder. Setting the downloads folder in settings did not solve this and would pop again. The client complained about no being able to connect to a service. The internal transmission webservice did run tho. Starting fragments in the terminal yielded this error:
ERROR transmission_client::client > Unable to parse json: invalid type: boolean `true`, expected i32 at line 1 column 63045
[2023-03-04 11:57:46.629] ERR torrent-metainfo.cc:630 no bencoded data to parse (84) (/build/transmission/src/transmission-4.0.1/libtransmission/torrent-metainfo.cc:630)
[2023-03-04 11:57:46.629] ERR torrent-metainfo.cc:630 no bencoded data to parse (84) (/build/transmission/src/transmission-4.0.1/libtransmission/torrent-metainfo.cc:630)
I solved this by removing the settings in ~/.config/fragments essentially forcing a clean start and return to defaults. Fragments behaves like I’m used to again. Fragments was not updated (last update to 2.1-1 was 17-01-2023) but the dependency transmission-cli was upgraded from 3.00-6 to 4.0.1-2 and this could explain the issue.
I have an ASUS TUF D4 WIFI Z690 motherboard.
After the update to the testing branch (from stable) the wifi was not working anymore.
My guess is that the hardware was not recognized because it didn’t even had the wifi checks in the Network window (see image)
I often use ProtonDB and update my profile’s system specs copied from Steam (Official Repository, with or without GPU acceleration in Steam Settings) > Help > System Information, Ctrl+A, Ctrl+C, switch to Firefox (110.0.1), go to my Profile page, paste, wait a few moments…amdgpu driver crash. The screen turns black, comes back to a frozen screen in Wayland and I have to force shut down. X11 brings me to the login screen where I can successfully attempt to login again, shut down, etc.
journalctl --since=today yields about nine chunks of the following at the time of crash;
Mar 06 22:34:41 username1 kernel: amdgpu 0000:03:00.0: amdgpu: [mmhub] page fault (src_id:0 ring:40 vmid:1 pasid:32799, for process i386-linux-gnu- pid 3853 thread i386-linux:cs0 pid 3854)
Mar 06 22:34:41 username1 kernel: amdgpu 0000:03:00.0: amdgpu: in page starting at address 0x0000800100769000 from client 0x12 (VMC)
Mar 06 22:34:41 username1 kernel: amdgpu 0000:03:00.0: amdgpu: MMVM_L2_PROTECTION_FAULT_STATUS:0x00141651
Mar 06 22:34:41 username1 kernel: amdgpu 0000:03:00.0: amdgpu: Faulty UTCL2 client ID: VCN0 (0xb)
Mar 06 22:34:41 username1 kernel: amdgpu 0000:03:00.0: amdgpu: MORE_FAULTS: 0x1
Mar 06 22:34:41 username1 kernel: amdgpu 0000:03:00.0: amdgpu: WALKER_ERROR: 0x0
Mar 06 22:34:41 username1 kernel: amdgpu 0000:03:00.0: amdgpu: PERMISSION_FAULTS: 0x5
Mar 06 22:34:41 username1 kernel: amdgpu 0000:03:00.0: amdgpu: MAPPING_ERROR: 0x0
Mar 06 22:34:41 username1 kernel: amdgpu 0000:03:00.0: amdgpu: RW: 0x1
As I write this, I’ve been able to Cut, Paste to/from; Kate, Konsole, Firefox in preparation without a problem. If I posted too much code, I apologize.
I can not reproduce this issue. But I read your error log:
It seems your system used the process i386-linux-gnu that I do not have. i386 is for 32bit system.
Can you check what is the output of $ pacman -Qo i386-linux-gnu ?