[Unstable Update] 2023-05-21 - Repository changes

Announcements Unstable Updates
,
1

Hello community,

Another unstable branch update with some (un)usual package updates for you.

:information_source: The Arch git migration is now complete.

The [community] repository has been merged into [extra] and is now empty. It may take a bit of time for mirrors to catch up.

:point_right: Update your system and merge the pacman pacnew /etc/pacman.conf.pacnew file.

sudo pacman -Syu "pacman>=6.0.2-11"

Notable Package Updates:

  • Usual KDE-git, Python and Haskell updates

Additional Info

Info about Python 3.11

:information_source: You will need to rebuild any AUR Python packages that install files to site-packages or link to libpython3.10.so. :information_source:

Print a list of of packages that have files in /usr/lib/python3.10/ :

pacman -Qoq /usr/lib/python3.10/

Rebuild them all at once:*

pamac build $(pacman -Qoq /usr/lib/python3.10)

* Note that if any fail to build, you’ll have to rebuild what’s remaining one or a few at a time.

Use rebuild-detector to see if anything else needs to be rebuilt:

checkrebuild
Info about AUR packages

:warning: 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.

Get our latest daily developer images now from Github: Plasma, GNOME, XFCE. You can get the latest stable releases of Manjaro from CDN77.

  • 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)

0 voters

Check if your mirror has already synced:

5 Likes
3

Known issues and solutions

This is a wiki post; please edit as necessary.
Please, consider subscribing to the Unstable Updates Announcements RSS feed

Please RTFT (Read This Fine Thread) first before reporting the same issues over and over again!

:arrow_right: 2023-05-21

The "community" repository has been merged into "extra" and is now empty

The [community] repository has been merged into [extra] and is now empty. It may take a bit of time for mirrors to catch up.

:point_right: Update your system and merge the pacman pacnew /etc/pacman.conf.pacnew file.

sudo pacman -Syu "pacman>=6.0.2-11"

2023-05-06

Many applications (firefox, thunderbird, etc) slow to start on desktops other than Gnome

There is a bug with xdg-desktop-portal-gnome (more details here).

Workaround for gtk-based desktops (including Xfce) 
sudo pacman -Rdd xdg-desktop-portal-gnome
sudo pacman -S xdg-desktop-portal-gtk
Workaround for KDE 
sudo pacman -Rdd xdg-desktop-portal-gnome
sudo pacman -S xdg-desktop-portal-kde
Workaround for Lxqt 
sudo pacman -Rdd xdg-desktop-portal-gnome
sudo pacman -S xdg-desktop-portal-lxqt
Workaround for desktops using hyprland 
sudo pacman -Rdd xdg-desktop-portal-gnome
sudo pacman -S xdg-desktop-portal-hyprland
Workaround for desktops using wlroots 
sudo pacman -Rdd xdg-desktop-portal-gnome
sudo pacman -S xdg-desktop-portal-wlr

2023-05-03

Help with upgrading Python packages that were installed from AUR or PyPI

:information_source: You will need to rebuild any AUR Python packages that install files to site-packages or link to libpython3.10.so. :information_source:

Print a list of of packages that have files in /usr/lib/python3.10/ :

pacman -Qoq /usr/lib/python3.10/

Rebuild them all at once:*

pamac build $(pacman -Qoq /usr/lib/python3.10)

* Note that if any fail to build, you’ll have to rebuild what’s remaining one or a few at a time.

Use rebuild-detector to see if anything else needs to be rebuilt:

checkrebuild

See also:
[HowTo] After a Python interpreter upgrade, reinstall non-working Python packages

2023-04-07

2023-03-31

GRUB: some backwards hardware compatibility has been restored

A modification has been reverted in order to restore support to old motherboards: [Unstable Update] 2023-02-17 - Plasma 5.27 LTS, GNOME, Python - #51 by philm

GRUB, LUKS and full disk encryption: 'no such cryptodisk found'

Following grub’s update, new configuration may be needed to be manually applied:

  • Check for modifications to /etc/default/grub
    Most notably, if you use LUKS with full disk encryption, you may need to:
    • check that GRUB_ENABLE_CRYPTODISK=y is not commented out
  • Don’t use tools like grub-customizer as it may create issues with the grub.cfg file.
  • 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.

For more details:

Info about recent NVIDIA packaging changes

[Testing Update] 2023-03-25 - Kernels, Firefox, Deepin, GNOME, NVIDIA, Wine - #42 by philm

Possible kernel fs block code regression in 6.2.3 umounting usb drives

With kernel 6.2.3 when you simply plug in a usb external drive, mount it and umount it, then the journal has a kernel Oops. A bug report, that includes the journal output was submitted at. 217174 – Plugging in usb external drive, mount and umount causes kernel Oops Discussion can be found here: Re: Possible kernel fs block code regression in 6.2.3 umounting usb drives — Linux Stable Kernel Updates

kernel 5.15.99+ Black/empty screen during boot with i915 Intel gfx. No ways to do anything

Seems there is a regression introduced with 5.15.99 kernel update: [i915]drm:add_taint_for_CI [i915]] CI tainted:0x9 by intel_gt_init+0xae/0x2d0 [i915] (#8284) · Issues · drm / intel · GitLab. My thoughts here: [Testing Update] 2023-03-11 - Kernels, Mesa 22.3.7, Phosh, LibreOffice 7.4.6 - #31 by philm

NVIDIA 530.41.03-1 high refresh rate problems

FS#77975 - [nvidia] 530.41.03-1 high refresh rate problems

2023-02-12

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:

pacman -Syu base-devel

– Arch Linux - News: Switch to the base-devel meta package requires manual intervention

2023-02-03

vlc player crashes while playing videos

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.

– Arch Linux - News: PHP 8.2 update and introduction of legacy branch

2022-12-20

pacman-mirrors was temporarily renamed to manjaro-mirrors (changed has been 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.

Sign in · GitLab You will need to rebuild any AUR Python packages that install files to site-packages. :information_source:

Print a list of them:

pacman -Qoq /usr/lib/python3.10

Rebuild them all at once:*

pamac build $(pacman -Qoq /usr/lib/python3.10)

* Note that if any fail to build, you’ll have to rebuild what’s remaining one or a few at a time.s/-/issues/183

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

XFCE Classic project became obsolete with the 4.18 series and is no longer required. If you still have it installed, please replace it with the normal package:

sudo pacman -S libxfce4ui
1 Like
6

Everything seems fine.
Very small update for me. Just 9 packages.

Mostly writing to note:
Nothing extra was required aside from paying attention to /etc/pacman.conf.pacnew post upgrade.

2 Likes
7

So the repos (after merging) are just the following to confirm?

[core]
Include = /etc/pacman.d/mirrorlist

[extra]
Include = /etc/pacman.d/mirrorlist

[multilib]
Include = /etc/pacman.d/mirrorlist
4 Likes
8

if we update with pacman and no pamac, community.files is not updated/empty

Alter edit pacman.conf, this (big) file will never be deleted/updated
same with manjaro-zsh-config / pkgfile ?

so, (re-)update .files before edit pacman.conf

9

Does this mean Manjaro will do that as well because [community] is not empty on Manjaro gitlab :wink:

10

That’s the whole idea. One will not receive pacman 6.0.2-11 until their mirror has synced with the changes.

We won’t be making changes on GitLab until the repo changes are in all branches with both x86_64 and ARM.

2 Likes
11

I think @papajoke may have been referring to the need to specifically update the files database prior to changing pacman.conf:

sudo pacman -Fy

since pamac update will do this automatically, but pacman -Syu will not.

12

I always run sudo pacman -Fy after sudo pacman -Syu. :wink:

3 Likes
13

Whereas I’m not sure most manjaro users ever use any variant pacman -F :spider_web:

But I suppose this does bring up some points that have gone unspoken.

Which is more or less that you want to run the things twice.

First you get everything new and changed:

sudo pacman -Syu
sudo pacman -Fy

Then you want to manage your pacnews - specifically pacman.conf.pacnew:
(example using meld and directly)

meld admin:////etc/pacman.conf.pacnew admin:////etc/pacman.conf

Then do it again so everything is lined up:

sudo pacman -Syu
sudo pacman -Fy
6 Likes
14

Don’t you think that with the repo updates that your post should be part of the first or second post?

15

Well … theres also some info missing there.
We are in the Unstable section of course :wink:

But just to fill it out …

The proper way to deal with pacnews is by using pacdiff.
It will print pacnew/pacsave/etc/s with just

pacdiff -o

But … it wont be easy to manage using pacdiff if you havent set DIFFPROG and/or SUDO_EDITOR.
Even then … in its current state you wont be able to edit things unless you run it with sudo.
Which of course is extra bad if you rely on a graphical editor to manage diffs.

I patched pacdiff to use syntax like above which should work if you have a diff application supported by KIO/GVFS/Polkit:

https://0x0.st/HNgz.sh

If you save it and run it you will have an edit option:

curl -o mandiff https://0x0.st/HNgz.sh
chmod +x mandiff
bash mandiff

Example run:

$ bash mandiff 
==> pacnew file found for /etc/pacman.conf
:: (V)iew, (E)dit, (M)erge, (S)kip, (R)emove pacnew, (O)verwrite with pacnew, (Q)uit: [v/e/m/s/r/o/q]

image
image1920×813 49.3 KB

image
image1920×813 115 KB

No warranties. Have fun. :blush:

4 Likes
16

You meant this?

$ du -hs /var/cache/pkgfile/*
310M /var/cache/pkgfile/community.files
18M /var/cache/pkgfile/core.files
88M /var/cache/pkgfile/extra.files
560K /var/cache/pkgfile/multilib.files

17

pkgfile is its own thing. (and not installed on every system - like here)
why it uses its own cache, I have no idea … but it do.

18

yes (300Mo ??? :crazy_face:)

After remove repo in pacman.conf, run

[ -f /var/tmp/pamac/dbs/sync/community.db ] && sudo rm -v /var/tmp/pamac/dbs/sync/community.*
[ -f /var/lib/pacman/sync/community.db ] && sudo rm -v /var/lib/pacman/sync/community.*
[ -f /var/cache/pkgfile/community.db ] && sudo rm -v /var/cache/pkgfile/community.*
3 Likes
19

yeah and it constantly updates via its service…
oh and when you were already annoyed that you typed car instead of cat … it will then parse all of those databases to see if there is in fact a program providing the car executable … so you wait for another 20 seconds to get your prompt back. Pure joy :sweat_smile:

20

it will be more fun now as extra and community most likely will be like 400 MB in size.

21

Funny yes, do you remember when we propose/inform arch linux dev to increase community db size since was at the limite size :smile:

22

In case you don’t know manjaro-tools-base.git still has community repo in it.

It’s all been updated today so many thanks.

23

This is my solution to it, which can be found here: :wink:

    if [[ -n $DIFFPROG ]]; then
        sudo -E pacdiff
    else
        sudo -E DIFFPROG="meld" pacdiff
    fi
1 Like