[Testing Update] 2022-02-01 - Kernels, Pipewire 0.3.44, Qt5, Mesa 21.3.5, Wine 7.0

Announcements Testing Updates
,
31

Yeah that is what I figured, no package seems to own it, this file isn’t owned by anything (tried pacman -Qo, tried pacman -F, tried pkgfile, tried google too which pointed me to results where this file also exist on other distribution), so it maybe is a leftover from initial installation, but it is hard to find its origin in Manjaro. But if it is a leftover, then that would mean without it we wouldn’t be able to sudo (because we don’t have the corresponding line enabled in /etc/sudoers) so I don’t know something is still weird with that theory.

I also think we can leave it or add the third ALL that wouldn’t change a lot for most/all users. I will keep the file in sudoers.d (and add the third ALL) and leave the sudoers file as default, with wheel line commented.

//EDIT: I will try to install Manjaro on VM to see if the file exist on old/current ISO installation, for the sake of curiosity.

//EDIT2: this file /etc/sudoers.d/10-installer is created at installation apparently, it is not owned by anything, but it is there at first boot of an installation (manjaro-kde-21.0.6-210607-linux510.iso).

//EDIT3: I found it, it is in the Calamares installer configuration file (users.conf), this is indeed created during the installation process:

# When *sudoersGroup* is set to a non-empty string, Calamares creates a
# sudoers file for the user. This file is located at:
#     `/etc/sudoers.d/10-installer`
# Remember to add the (value of) *sudoersGroup* to *defaultGroups*.
#
# If your Distribution already sets up a group of sudoers in its packaging,
# remove this setting (delete or comment out the line below). Otherwise,
# the setting will be duplicated in the `/etc/sudoers.d/10-installer` file,
# potentially confusing users.
sudoersGroup:    wheel

So yeah, by default no one should have the wheel line enabled in /etc/sudoers but should have the 10-installer file with the wheel group privileges.

:male_detective:

4 Likes
32

There was an update to qt5-wayland that introduced a race condition with plasmashell and kactivitymanagerd. We saw it a lot on Plasma Mobile, but I would imagine it would happen on x64 too if you have systemdBoot=true in kdeglobals config.

You can try downgrading qt5-wayland for now as that specific issue has not been fixed upstream yet.

33

Thanks @Wollie I can sudo again :slight_smile:

1 Like
34

It wasn’t laptop’s specs either. This is a high performance gaming laptop. Today pamac’s update check looks better then yesterday’s, so it looks it wasn’t the permanent issue. Nevermind, if the delay will be repeating frequently, I’ll post a bug/issue. Hopefully this was some temporary issue. We’ll see.

35

Nice, guys, thanks, we had a nice talk here. Pity that some didn’t listen.

Packages (1) manjaro-system-20220202-1

Total Download Size:   0.02 MiB
Total Installed Size:  0.00 MiB
Net Upgrade Size:      0.00 MiB

:: Proceed with installation? [Y/n] 
:: Retrieving packages...
 manjaro-system-2...    23.9 KiB  70.4 KiB/s 00:00 [#########################] 100%
(1/1) checking keys in keyring                     [#########################] 100%
(1/1) checking package integrity                   [#########################] 100%
(1/1) loading package files                        [#########################] 100%
(1/1) checking for file conflicts                  [#########################] 100%
(1/1) checking available disk space                [#########################] 100%
:: Processing package changes...
(1/1) upgrading manjaro-system                     [#########################] 100%
==> Remove obsolete 10-installer file from sudoers.d ...
==> Checking for 'os-prober' setup ...
grep: /etc/default/grub: No such file or directory
    We will reenable 'os-prober' for you ...
/tmp/alpm_vhUpDv/.INSTALL: line 99: update-grub: command not found

==> Remove obsolete 10-installer file from sudoers.d …

“Wow, really?” I thought and issued
$ sudo ls /etc/sudoers.d/
to see

openm is not in the sudoers file. This incident will be reported.

All those who haven’t uncommented the respective line in /etc/sudoers will suffer the way I do now.
I repeat, on my side no pacnew file was created when updating sudo, hence I suppose having that line commented is the DEFAULT for Manjaro systems (EDIT: reason found down here).

TLDR: login as root and edit /etc/sudoers with visudo /etc/sudoers

3 Likes
36

Well I updated the manjaro-systems package again to not to remove the file. Now we know it gets created by Calamares. The only questions is if we should adopt to the group privileges or not, as both versions work.

37

The same issue. I got the message of sudo pacman -Syu:

zesko is not in the sudoers file. This incident will be reported.

Solution:

  • Run as root: su
  • I create and edit new file vim /etc/sudoers.d/user.
%wheel ALL=(ALL) ALL
3 Likes
38

@philm , in the “known issues” section we should maybe add a point for the massive performance backdrop on btrfs file systems with kernel 5.16.
The workaround is to mount the file systems with the noautodefrag option.
The fixes were merged in the mainline and will come with kernel 5.16.5, which is currently in the unstable channel.

2 Likes
39

I think we should let it be as it was, the Calamares installer adds the user to wheel group, and creates the 10-installer file that allows user in wheel group to be able to sudo. Removing the file would require that the sudoers file is then properly reconfigured or else the user loses his sudo rights. And reconfiguring the sudoers file might be frowned upon by users, if you start automatically messing with it without user consent, especially for people who modify their system and this file and that can have issues by enabling wheel group privileges in this file.

I think that sudoers.pacnew file scare we had was not justified, merging the changes (I mean if the user does it himself by checking it) does nothing bad to the system and there is no need to remove how things worked since the beginning of time in Manjaro (or at least since I use it :D).

5 Likes
40

A simple stat 10-installer would show it is created on system creation (stat /).

No need for this drama in the first place, the user should always use drop-ins, not edit “machine” files.

I’m on unstable too and didn’t get a .pacnew either because of the above, while the default file was normally updated with the new entries`

# %wheel ALL=(ALL:ALL) NOPASSWD: ALL
...
@includedir /etc/sudoers.d
41

Kernel 5.17 rc2 panics when linux517-nvidia is installed along with it. journalctl -b -1 returns the journal of the boot before the kernel upgrade. So I guess the kernel panics at initramfs stage itself. Removing linux517-nvidia fixes the issue, but of course I am unable to use my Nvidia d-gpu.

42

That only works on unstable branch for now, as it switched to the nvidia 510 driver series …

1 Like
43

If the overall goal is to remain in-line with systemd, I think a file should be created in /etc/sudoers.d… I just question whether 10-installer is a meaningful filename that explains the files purpose.

44

i agree, my only concern is if someone gets the syntax wrong in the drop-in file will it screwup the whole sudo mechanism, does visudo syntax-checking mechanism extend to the included drop-in files.

45

Appreciate the response. I don’t have that in my kdeglobals and it seems stable enough for now. I’ll try downgrading if that changes.

47

seems you have forgotten the questionmark :grinning_face_with_smiling_eyes: , but yes it does.

48

HI all, I had this warning while updating:

(12/86) updating accountsservice                                                                             [############################################################################] 100%
warning: directory permissions differ on /var/lib/AccountsService/
filesystem: 755  package: 775

I think it should be easily solved by changing the directory permission to 775, right?

Thanks.

49

This happens when the package has different permission than what it was before, you could usually change the permission or leave it as it may be a mistake by packager. Usually not a real issue I think.

1 Like
50
1 Like
52

I’ve got issues with sudo
“$USER is not in the sudoers file. This incident will be reported”
GUI applications has no issues with getting priviledges, though. KDE Plasma

I just got it and am resolving it manually