[Unstable Update] 2020-09-13 - Kernels, Qt 5.15.1, Browser, Pamac

8 posts were split to a new topic: I2C touchpad does not function after resuming from suspend

Second time I see this when updating:

Warning: linux58-vhba-module-20200106-24 is updated - reinstalling
Warning: linux58-virtualbox-host-modules-6.1.14-12 is updated - reinstalling
Warning: linux59-vhba-module-20200106-1 is updated - reinstalling
Warning: linux59-virtualbox-host-modules-6.1.14-1 is updated - reinstalling

Not a problem?

unstable brings new linux59 5.9.0-4 and linux59-headers 5.9.0-4 today. But I can not find the source for that.

git clone https://gitlab.manjaro.org/packages/core/linux59.git

Still gets me 5.9.0-2. Where is the source?

It’s there now.

It doesnt work:

==> ERROR: 0000-prepatch-5.9-20201016.patch was not found in the build directory and is not a URL.

same here

I guess Phil forgot to push the file.

Anyways, there is another update now to 5.9.1 (where the bluetooth stuff is included now I assume)

Enabling the LCD-Filter solved this for me.

1 Like

Is dbus-x11 going to replace dbus?

Oh…Pop Shell needs it.

Ok. I will give it a try. But where are the sources for all the extramodules?

The repo


is empty.

You have to wait, the Developers are also only humans. :wink:
There are still some things they can be automated, but this is harder for Kernel Builds.

I thought that with all the 5.9 release candidates that have been published over the last couple of weeks that the extramodules directory would be populated with at least something. Even if it is old. But it is completely empty.

They usually build a package first, and then add/update git files if they don’t forget about it. I presume so based to my observations of Manjaro’s git since 2019 :smile:

I entirely dislike that “workflow” - it should be the other way around.

3 Likes

It does? :thinking:

❯ pacman -Si gnome-shell-extension-pop-shell | grep "Depends On"
Depends On      : gnome-shell  pop-shell-shortcuts

kernel 5.9.1 looks good to me. incl. zfs 0.8.5 :+1:

Several days ago I set up /etc/default/grub

just got update

Package (4)               Old Version  New Version  Net Change  Download Size

extra/grub-theme-manjaro  20.2-4       20.2-5         0.00 MiB       0.81 MiB

and saw

==> Installation: Theme is added to your /etc/default/grub: GRUB_THEME="/usr/share/grub/themes/manjaro/theme.txt"
==> Default resolution "auto"
==> If an OS icon doesn't appear probably not present in /usr/share/grub/themes/manjaro/icons simply add it or merge in
==> https://gitlab.manjaro.org/artwork/branding/grub-theme

I see that

$ cat /etc/default/grub
...
GRUB_GFXMODE=auto
...

is auto again

What was the reason to reset the setting value?

nvidia 455.28 is incompatible with linux >= 5.9

2020-10-21 - Sven-Hendrik Haase

nvidia is currently partially incompatible with linux >= 5.9 [1] [2]. While graphics should work fine, CUDA, OpenCL, and likely other features are broken. Users who’ve already upgraded and need those features are advised to switch to the linux-lts kernel for the time being until a fix for nvidia is available.

https://www.archlinux.org/news/nvidia-45528-is-incompatible-with-linux-59/

1 Like
Again grub welcome screen resolution was reset to auto
$ tail -n100 /var/log/pacman.log 
...
[2020-10-21T15:24:20+0000] [ALPM] transaction started
[2020-10-21T15:24:20+0000] [ALPM] upgraded glib2 (2.66.1-2 -> 2.66.2-1)
[2020-10-21T15:24:20+0000] [ALPM] upgraded bluedevil (1:5.20.0-1 -> 1:5.20.1-1)
[2020-10-21T15:24:20+0000] [ALPM] upgraded kdecoration (5.20.0-1 -> 5.20.1-1)
[2020-10-21T15:24:20+0000] [ALPM] upgraded breeze (5.20.0-1 -> 5.20.1-1)
[2020-10-21T15:24:21+0000] [ALPM] upgraded firefox (81.0.2-1 -> 82.0-1)
[2020-10-21T15:24:21+0000] [ALPM] upgraded firefox-i18n-en-gb (81.0.2-1 -> 82.0-1)
[2020-10-21T15:24:21+0000] [ALPM] upgraded firefox-i18n-en-us (81.0.2-1 -> 82.0-1)
[2020-10-21T15:24:21+0000] [ALPM] upgraded git (2.28.0-1 -> 2.29.0-1)
[2020-10-21T15:24:21+0000] [ALPM] upgraded grub-theme-manjaro (20.2-5 -> 20.2-6)
[2020-10-21T15:24:22+0000] [ALPM-SCRIPTLET] Generating grub configuration file ...
[2020-10-21T15:24:22+0000] [ALPM-SCRIPTLET] Found theme: /usr/share/grub/themes/manjaro/theme.txt
[2020-10-21T15:24:23+0000] [ALPM-SCRIPTLET] Found linux image: /boot/vmlinuz-5.8-x86_64
[2020-10-21T15:24:23+0000] [ALPM-SCRIPTLET] Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.8-x86_64.img
[2020-10-21T15:24:23+0000] [ALPM-SCRIPTLET] Found initrd fallback image: /boot/initramfs-5.8-x86_64-fallback.img
[2020-10-21T15:24:25+0000] [ALPM-SCRIPTLET] Adding boot menu entry for UEFI Firmware Settings ...
[2020-10-21T15:24:25+0000] [ALPM-SCRIPTLET] Found memtest86+ image: /boot/memtest86+/memtest.bin
[2020-10-21T15:24:25+0000] [ALPM-SCRIPTLET] /usr/bin/grub-probe: warning: unknown device type nvme0n1.
[2020-10-21T15:24:25+0000] [ALPM-SCRIPTLET] done
[2020-10-21T15:24:25+0000] [ALPM-SCRIPTLET] 
[2020-10-21T15:24:25+0000] [ALPM-SCRIPTLET] ==> Installation: Theme is added to your /etc/default/grub: GRUB_THEME="/usr/share/grub/themes/manjaro/theme.txt"
[2020-10-21T15:24:25+0000] [ALPM-SCRIPTLET] ==> Default resolution "auto"
[2020-10-21T15:24:25+0000] [ALPM-SCRIPTLET] ==> If an OS icon doesn't appear probably not present in /usr/share/grub/themes/manjaro/icons simply add it or merge in
[2020-10-21T15:24:25+0000] [ALPM-SCRIPTLET] ==> https://gitlab.manjaro.org/artwork/branding/grub-theme
...

and

$ cat /etc/default/grub
...
GRUB_GFXMODE=auto
...

Fixed manually again. Selected high res is present in videoinfo in grub's CLI as recommended and after re-set to that high res value still works well w/o problems.

Does anybody really need to reset grub welcome screen resolution with every grub-theme-manjaro update?

2 Likes