December 2020 - Arch-general - lists.archlinux.org

[arch-general] [RFC] Potentially deprecating primus, bumblebee, virtualGL and primus_vk
by Emil Velikov 16 Feb '21

16 Feb '21

Hello all, As some of you may know, I have been an Arch user for over 5 years and a Linux graphics developer working on the whole stack from the kernel DRM all the way up-to Mesa and X. I would like to propose, partially deprecating and potentially removing some of the said packages in light of the development that has been happening over the last few years. tl;dr: these solutions have been partially or completely obsolete, for a while now ## OpenGL/GLX/etc # Background As you know, in the early days we would have both Mesa and vendors provide their own libGL.so.1 and in some cases libglx.so (xorg module). Alongside that drivers lacked dynPM, allowing you to powering off the GPU, when it's not used. To address those primus and bumblebee came about. Note: dynPM is mentioned for completeness, it won't be covered any more. # Since then Nvidia and open source drivers support client - Mesa drivers - since v17.2.0 (at least), packaged 7 Sep 2017 - Nvidia drivers - since v390.25 (at least), packaged 29 Jan 2018 ... and server-side glvnd: - xorg-xserver - since v1.20.6, packaged 23 Nov 2019 - Nvidia drivers - since v435.21, packaged 30 Aug 2019 ## Vulkan # Background On the Vulkan side the drivers are clearly separated from the start - libvulkan_$vendor.so. Yet very few applications would bother selecting the GPU, plus server-side (when using WSI_X11) wasn't complete. GL Vulkan interop was also tricky, with libGL.so.1 being provided by vendors. This resulted in primus_vk. # Since then - Mesa drivers - since 20.1.0, packaged 28 May 2020 Driver selection layer was added, falling back to DRI_PRIME [1] - Nvidia drivers - since v390.25 (at least), packaged 29 Jan 2018 Vulkan implicit layer was added - see [2] ## My proposal: Cleanup the packages, as outlined below and update the wiki. Please check out the Extra notes below. I will be more than happy to tackle this although maintainers will have to push/rebuild the packages for obvious reasons. - primus: replace with a simple compat script primusrun, which a) finds the ID_PATH_TAG for the Nvidia GPU and sets DRI_PRIME=$tag $@ - bumblebee: optirun - replace with script calling primusrun xorg config - should not be needed, double-check and drop bumblebeed - (optionally) remove no longer applicable code, config etc bumblebee - remove no longer applicable group - virtual GL: move to AUR, since it has no more users - primus_vk: replace with a simple compat script pvkrun akin to primusrun, making use of [1] and [2] ## Extra notes: - primus/bumblebee - seemingly been abandoned upstream for 4+ years. Arch maintainers having to carry fixes locally. - primus/virtualgl/primus_vk performance is worse than natively - compat primusrun/optirun/pvkrun are to minimise breakage - some legacy Nvidia drivers may lack support - those drivers live in the AUR, thus a solution for them should also be packaged there. ## Feedback I would love to hear the input from the respective maintainers and the overall Arch developer base as a whole. Is there a particular use-case that I've missed? How would you like this handled - as mentioned above, I'm happy to submit patches be that via Flyspray, email, MR or otherwise. Looking forward to your input -Emil [1] https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/1766 [2] http://download.nvidia.com/XFree86/Linux-x86_64/435.17/README/primerenderof…

4 28

[arch-general] https://git.archlinux.org/svntogit obsolete?
by Erich Eckner 13 Feb '21

13 Feb '21

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi, I was surprised to find git.archlinux.org/svntogit/packages.git/ and git.archlinux.org/svntogit/community.git/ being no longer updated since a few days. I know, there was a github mirror of the repositories set up some time ago - did I miss some deprecation notice for the old locations or is this some oversight on the arch end? regards, Erich -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEE3p92iMrPBP64GmxZCu7JB1Xae1oFAl/ffMIACgkQCu7JB1Xa e1qskg//T0HkTdj33ygNCpDNwvDf2H6V1zOBkjadlHrXph4/WkQIyYa7QJxmWXfV d0CWioelIJM4qkBpXrwTa4xMvowW7HLgvpUnCfnXSSaiCODEbJDXC/b0OokHSS9c K+9rGdMgVwfmsMevc/k919ifzmNIUkmX3tOd4lRc1CO6A2EHxFELndY3MbBhpz12 gP599BPvopC+AlYg0MEu1l0/1wAq5p0zSJvneyh2R8LIo8RW/8N7JWnmt0CJf8sM iNiBHvj7byk1Y8uXghibaN9LqLAtRTodhb++Fm5NKdHmlVAnGxrdA3aKlYJYYXsL Q/OYBSTwuhNvxXJnewLtErWjcVu7IL29gPX2Hh7Yhyf+XHScond/Z6WWza3dBYMx rEC9sknS9aSQeuvJqAyfq0mCDQJxbDFAs2p2zh0LG65pbY04yZstmDo/Al+xZV5D wwqedpiTAUVI23m9IePMfxEUnWuRaF5GYeJIa/EFmYn5OXPWMuUO/Y5p2G54QLvX Zwbxu08NDzf+jznhVw2CiP/V7SDMtdLa0hMblvD63z+ywZql0KGIjhiyA9EtXMZm NGQexY5yHyb2R5gKx8e4a7o8ZRJP/n/85laRj3dBYA1ulr5Sp7FCNdYFOLs9xz64 IygVzAJG6Og4kDD7trPl++OwLzaKZ//Qodm3w/+egG3HY75/KvM= =vYL+ -----END PGP SIGNATURE-----

3 3

[arch-general] efibootmgr doesn't change boot order!
by Peter K Haokip 21 Jan '21

21 Jan '21

I read an forum entry from nearly 6 years ago about am efibootmgr bug that Doesn't let you change the boot order on a multi OS system if you have arch linux as the default OS. Had some users report this as well in other forums. Now i am facing the that problem in my system with arch ubuntu and windows. when i change the boot order , it shows the change 'temporarily' but when i restart it boots the default (Arch linux Grub ) and the change disappears. I faced this issue last month and gave up on it since I couldn't find any detailed resource on this on the net. This list may be my last hope. If anybody could give some direction , would be much appreciated. regards, khaithang39

4 5

[arch-general] User authentication problems at OpenVPN on ArchLinux
by Jordan Borgner 31 Dec '20

31 Dec '20

Good day everyone. I'm facing a weird problem with my vpn. It fails to authenticate users despite the entered password is correct (copied and pasted). OpenVPN (version 2.5.0 on ArchLinux) itself is serviced with systemd and runs fine. I'm using OpenVPN's auth-pam plugin to authenticate users. You find the configuration- and logfiles below. When trying to log in, I get "User authentication failed" at my client and the following logging. The user was created with useradd and is able to login with ssh as well. There is no pam config for openvpn in /etc/pam.d. But it worked before without it. Does anyone have an idea on how to fix this or how to debug pam properly? journalctl -r|grep username =========================== Dec 26 13:42:41 hostname kernel: audit: type=1100 audit(1608986561.263:1183): pid=678 uid=973 auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=? acct="username" exe="/usr/bin/openvpn" hostname=? addr=? terminal=? res=failed' Dec 26 13:42:41 hostname audit[678]: USER_AUTH pid=678 uid=973 auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=? acct="username" exe="/usr/bin/openvpn" hostname=? addr=? terminal=? res=failed' Dec 26 13:42:41 hostname openvpn[678]: pam_unix(login:auth): authentication failure; logname= uid=973 euid=973 tty= ruser= rhost= user=username Dec 26 13:42:41 hostname unix_chkpwd[4160]: password check failed for user (username) /var/log/openvpn.log ==================== ip-addr [username] Peer Connection Initiated with [AF_INET6]ip-addr:52991 ip-addr PUSH: Received control message: 'PUSH_REQUEST' ip-addr Delayed exit in 5 seconds ip-addr SENT CONTROL [username]: 'AUTH_FAILED' (status=1) ip-addr SIGTERM[soft,delayed-exit] received, client-instance exiting server.conf =========== plugin /usr/lib64/openvpn/plugins/openvpn-plugin-auth-pam.so login port 1194 persist-key persist-tun proto udp proto udp6 dev tun ca /etc/openvpn/easy-rsa/pki/ca.crt cert /etc/openvpn/easy-rsa/pki/issued/manmtr.crt key /etc/openvpn/easy-rsa/pki/private/manmtr.key dh /etc/openvpn/easy-rsa/pki/dh.pem data-ciphers AES-256-GCM ;cipher AES-256-CBC auth SHA512 reneg-sec 36000 inactive 0 server 192.168.200.0 255.255.255.0 push "route 192.168.100.0 255.255.255.0" keepalive 10 36000 status openvpn-status.log log /var/log/openvpn.log verb 4 -- Jordan Borgner

3 3

[arch-general] darktable libavif libyuv update and undefined symbol
by Genes Lists 22 Dec '20

22 Dec '20

Todays update[1] of darktable along with libavif / libavif led to this message: (5/7) Probing GDK-Pixbuf loader modules... g_module_open() failed for /usr/lib/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-avif.so: /usr/lib/libyuv.so: undefined symbol: jpeg_read_raw_data I have libjpeg-turbo installed and confirme that the function is available in the library: % objdump -T /usr/lib/libjpeg.so |egrep read_raw_data 0000000000017950 g DF .text 00000000000000df LIBJPEG_8.0 jpeg_read_raw_data Anyone have ideas how to resolve this? Is it benig, or a problem on my end? thanks. [1] Updated to: darktable 2:3.2.1-3 libavif-0.8.3-1 libyuv-r2212+dfaf7534-1

3 3

[arch-general] Segmentation fault when trying to install a self-created package
by Peter Nabbefeld 20 Dec '20

20 Dec '20

Hello, as the meshroom builds (from AUR) don't work for me, I tried to create my own package by modifying the PKGBUILD file of the meshroom-git package. This results in two issues: 1. While creating the package using makepkg, the whole git repository is downloaded - that's okay, of course. But all built artifacts seem to be contained in the resulting package file. As a git build shouldn't be "static": How can I create a build file for automatic downloading and building from current repository? 2. When installing the created package (pacman -U) and trying to start Meshroom, I get: "Segmentation fault (core dumped)". It seems, there's a problem with Meshroom's private shiboken2 installation: PID: 135087 (Meshroom) UID: 1000 (peter) GID: 100 (users) Signal: 11 (SEGV) Timestamp: Sun 2020-12-20 11:04:25 CET (24min ago) Command Line: Meshroom Executable: /usr/lib/Meshroom-2020.1.1/Meshroom Control Group: /user.slice/user-1000.slice/session-9.scope Unit: session-9.scope Slice: user-1000.slice Session: 9 Owner UID: 1000 (peter) Boot ID: 4e5fb788a5324cd1b31363dee2d7b62e Machine ID: b1efa5af7b174c44adc4ec7990c10ad7 Hostname: tuchola Storage: /var/lib/systemd/coredump/core.Meshroom.1000.4e5fb788a5324cd1b31363dee2d7b62e.135087.1608458665000000.zst Message: Process 135087 (Meshroom) of user 1000 dumped core. Stack trace of thread 135087: #0 0x00007ff37636becb SbkObject_TypeF (libshiboken2.abi3.so.5.15 + 0xeecb) #1 0x00007ff37636d80d _ZN8Shiboken4initEv (libshiboken2.abi3.so.5.15 + 0x1080d) #2 0x00007ff37637fa79 _ZN8Shiboken6Module6createEPKcPv (libshiboken2.abi3.so.5.15 + 0x22a79) #3 0x00007ff3765b13e7 PyInit_shiboken2 (shiboken2.abi3.so + 0x23e7) #4 0x000055d17af0edfd n/a (Meshroom + 0x21adfd) #5 0x000055d17ae323c1 n/a (Meshroom + 0x13e3c1) #6 0x000055d17ae263b2 _PyEval_EvalFrameDefault (Meshroom + 0x1323b2) #7 0x000055d17ae1f605 n/a (Meshroom + 0x12b605) #8 0x000055d17ae31b6e _PyFunction_Vectorcall (Meshroom + 0x13db6e) #9 0x000055d17ae251ae _PyEval_EvalFrameDefault (Meshroom + 0x1311ae) #10 0x000055d17ae319ca _PyFunction_Vectorcall (Meshroom + 0x13d9ca) #11 0x000055d17ae20dcf _PyEval_EvalFrameDefault (Meshroom + 0x12cdcf) #12 0x000055d17ae319ca _PyFunction_Vectorcall (Meshroom + 0x13d9ca) #13 0x000055d17ae20b97 _PyEval_EvalFrameDefault (Meshroom + 0x12cb97) #14 0x000055d17ae319ca _PyFunction_Vectorcall (Meshroom + 0x13d9ca) #15 0x000055d17ae20b97 _PyEval_EvalFrameDefault (Meshroom + 0x12cb97) #16 0x000055d17ae319ca _PyFunction_Vectorcall (Meshroom + 0x13d9ca) #17 0x000055d17ae20b97 _PyEval_EvalFrameDefault (Meshroom + 0x12cb97) #18 0x000055d17ae319ca _PyFunction_Vectorcall (Meshroom + 0x13d9ca) #19 0x000055d17ae311b5 n/a (Meshroom + 0x13d1b5) #20 0x000055d17ae4587c _PyObject_CallMethodIdObjArgs (Meshroom + 0x15187c) #21 0x000055d17ae44dfd PyImport_ImportModuleLevelObject (Meshroom + 0x150dfd) #22 0x000055d17ae2393a _PyEval_EvalFrameDefault (Meshroom + 0x12f93a) #23 0x000055d17ae1f605 n/a (Meshroom + 0x12b605) #24 0x000055d17ae1efd1 _PyEval_EvalCodeWithName (Meshroom + 0x12afd1) #25 0x000055d17aee0a13 PyEval_EvalCode (Meshroom + 0x1eca13) #26 0x000055d17aee8023 n/a (Meshroom + 0x1f4023) #27 0x000055d17ae323c1 n/a (Meshroom + 0x13e3c1) #28 0x000055d17ae263b2 _PyEval_EvalFrameDefault (Meshroom + 0x1323b2) #29 0x000055d17ae1f605 n/a (Meshroom + 0x12b605) #30 0x000055d17ae31b6e _PyFunction_Vectorcall (Meshroom + 0x13db6e) #31 0x000055d17ae251ae _PyEval_EvalFrameDefault (Meshroom + 0x1311ae) #32 0x000055d17ae319ca _PyFunction_Vectorcall (Meshroom + 0x13d9ca) #33 0x000055d17ae20dcf _PyEval_EvalFrameDefault (Meshroom + 0x12cdcf) #34 0x000055d17ae319ca _PyFunction_Vectorcall (Meshroom + 0x13d9ca) #35 0x000055d17ae20b97 _PyEval_EvalFrameDefault (Meshroom + 0x12cb97) #36 0x000055d17ae319ca _PyFunction_Vectorcall (Meshroom + 0x13d9ca) #37 0x000055d17ae20b97 _PyEval_EvalFrameDefault (Meshroom + 0x12cb97) #38 0x000055d17ae319ca _PyFunction_Vectorcall (Meshroom + 0x13d9ca) #39 0x000055d17ae311b5 n/a (Meshroom + 0x13d1b5) #40 0x000055d17ae4587c _PyObject_CallMethodIdObjArgs (Meshroom + 0x15187c) #41 0x000055d17ae44dfd PyImport_ImportModuleLevelObject (Meshroom + 0x150dfd) #42 0x000055d17ae2393a _PyEval_EvalFrameDefault (Meshroom + 0x12f93a) #43 0x000055d17ae319ca _PyFunction_Vectorcall (Meshroom + 0x13d9ca) #44 0x000055d17ae20b97 _PyEval_EvalFrameDefault (Meshroom + 0x12cb97) #45 0x000055d17ae1f605 n/a (Meshroom + 0x12b605) #46 0x000055d17ae1efd1 _PyEval_EvalCodeWithName (Meshroom + 0x12afd1) #47 0x000055d17aee0a13 PyEval_EvalCode (Meshroom + 0x1eca13) #48 0x000055d17aee8023 n/a (Meshroom + 0x1f4023) #49 0x000055d17ae323c1 n/a (Meshroom + 0x13e3c1) #50 0x000055d17ae263b2 _PyEval_EvalFrameDefault (Meshroom + 0x1323b2) #51 0x000055d17ae1f605 n/a (Meshroom + 0x12b605) #52 0x000055d17ae31b6e _PyFunction_Vectorcall (Meshroom + 0x13db6e) #53 0x000055d17ae251ae _PyEval_EvalFrameDefault (Meshroom + 0x1311ae) #54 0x000055d17ae319ca _PyFunction_Vectorcall (Meshroom + 0x13d9ca) #55 0x000055d17ae20dcf _PyEval_EvalFrameDefault (Meshroom + 0x12cdcf) #56 0x000055d17ae319ca _PyFunction_Vectorcall (Meshroom + 0x13d9ca) #57 0x000055d17ae20b97 _PyEval_EvalFrameDefault (Meshroom + 0x12cb97) #58 0x000055d17ae319ca _PyFunction_Vectorcall (Meshroom + 0x13d9ca) #59 0x000055d17ae20b97 _PyEval_EvalFrameDefault (Meshroom + 0x12cb97) #60 0x000055d17ae319ca _PyFunction_Vectorcall (Meshroom + 0x13 Does somebody have an idea, what I could change? Kind regards, peter

1 0

[arch-general] Bug with CIFS mount
by Tasnad Kernetzky 17 Dec '20

17 Dec '20

Hi All, I suppose I hit this bug: https://bugs.archlinux.org/task/68963 and it seems it is not fully resolved. I didn't request to reopen the bug, because I'm not 100% sure it is really the same thing. I have a setup with kerberos/sssd/pam/autofs, authenticating with an active directory, and cifs mounts stopped working. Login and nfs with kerberos work fine, to the issue is quite likely with cifs. Mounting the cifs share works with libcap-ng-0.8-1, but not with libcap-ng-0.8.2-1. I have cifs-utils 6.11-2, sssd 2.4.0-2 and krb5 1.18.2-1. Did I miss something or am I hitting something special due to the setup? Does anybody have a clue what could be the issue? I include lots of details about the config and logs, but tl;dr: "mount -t cifs -o domain=DOM,sec=krb5,soft,noserverino,cifsacl,username=theUser,cruid=1234567,vers=3.0 //nas.example.com/theUser /nas/home/theUser" fails with "cifs.upcall[532824]: drop_all_capabilities: Unable to apply capability set: Success" Best, Tasnad Substituted values ================== * myMachine: the client's hostname (not fqdn) * theUser: the nonroot user trying to mount via autofs * 1234567: uid of theUser (from Active directory) * DOM: the AD domain * DOM.EXAMPLE.COM: domain, fqdn /etc/krb5.conf ============== [libdefaults] default_realm = DOM.EXAMPLE.COM udp_preference_limit = 0 default_ccache_name = FILE:/tmp/krb5cc_%{uid} dns_lookup_realm = true dns_lookup_kdc = true rdns = false ticket_lifetime = 10h renew_lifetime = 7d forwardable = true sssd.conf ========= [sssd] config_file_version = 2 domains = DOM.EXAMPLE.COM services = nss, pam [nss] default_shell = /bin/bash shell_fallback = /bin/bash filter_groups = root filter_users = root [domain/DOM.EXAMPLE.COM] id_provider = ad auth_provider = ad access_provider = simple ldap_schema = ad sudo_provider = none cache_credentials = false krb5_store_password_if_offline = false dyndns_update = false ldap_id_mapping = false use_fully_qualified_names = false enumerate = false ignore_group_members = true case_sensitive = preserving ad_enable_gc = false ad_hostname = myMachine ldap_search_base = [...] ldap_user_search_base = [...] ldap_user_search_scope = [...] ldap_group_search_base = [...] ldap_group_search_scope = [...] nsswitch.conf ============= passwd: files sss group: files sss shadow: files sss gshadow: files sss publickey: files hosts: files mymachines myhostname resolve [!UNAVAIL=return] dns networks: files protocols: files services: files sss ethers: files rpc: files netgroup: files sss automount: sss homes.autofs ============ /nas/home /etc/autofs/auto.master.d/home.map -domain=DOM,fstype=cifs,sec=krb5,soft,noserverino,cifsacl home.map ======== * -username=$USER,cruid=$UID,vers=3.0 ://nas.example.com/& cifs idmap plugin ============ /etc/cifs_utils/idmap-plugin -> /usr/lib/cifs-utils/cifs_idmap_sss.so klist ===== Ticket cache: FILE:/tmp/krb5cc_<uid> Default principal: theUser(a)DOM.EXAMPLE.COM Valid starting Expires Service principal 12/16/2020 11:31:48 12/16/2020 21:25:18 krbtgt/DOM.EXAMPLE.COM(a)DOM.EXAMPLE.COM renew until 12/23/2020 11:25:18 automount -fd ============= handle_packet: type = 3 handle_packet_missing_indirect: token 727, name theUser, request pid 532818 attempting to mount entry /nas/home/theUser lookup_mount: lookup(file): looking up theUser lookup_mount: lookup(file): theUser -> -username=$USER,cruid=$UID,vers=3.0 ://nas.example.com/& parse_mount: parse(sun): expanded entry: -username=theUser,cruid=1234567,vers=3.0 ://nas.example.com/theUser parse_mount: parse(sun): gathered options: domain=DOM,fstype=cifs,sec=krb5,soft,noserverino,cifsacl,username=theUser,cruid=1234567,vers=3.0 parse_mount: parse(sun): dequote("://nas.example.com/theUser") -> ://nas.example.com/theUser parse_mount: parse(sun): core of entry: options=domain=DOM,fstype=cifs,sec=krb5,soft,noserverino,cifsacl,username=theUser,cruid=1234567,vers=3.0, loc=://nas.example.com/theUser sun_mount: parse(sun): mounting root /nas/home, mountpoint theUser, what //nas.example.com/theUser, fstype cifs, options domain=DOM,sec=krb5,soft,noserverino,cifsacl,username=theUser,cruid=1234567,vers=3.0 do_mount: //nas.example.com/theUser /nas/home/theUser type cifs options domain=DOM,sec=krb5,soft,noserverino,cifsacl,username=theUser,cruid=1234567,vers=3.0 using module generic mount_mount: mount(generic): calling mkdir_path /nas/home/theUser mount(generic): calling mount -t cifs -o domain=DOM,sec=krb5,soft,noserverino,cifsacl,username=theUser,cruid=1234567,vers=3.0 //nas.example.com/theUser /nas/home/theUser >> mount error(126): Required key not available >> Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg) mount(generic): failed to mount //nas.example.com/theUser (type cifs) on /nas/home/theUser dev_ioctl_send_fail: token = 727 failed to mount /nas/home/theUser journalctl ============== kernel: CIFS: fs/cifs/cifsfs.c: Devname: //nas.example.com/theUser flags: 0 kernel: CIFS: fs/cifs/connect.c: Domain name set kernel: CIFS: fs/cifs/connect.c: Username: theUser kernel: CIFS: fs/cifs/connect.c: file mode: 0755 dir mode: 0755 kernel: CIFS: fs/cifs/connect.c: VFS: in mount_get_conns as Xid: 684 with uid: 0 kernel: CIFS: fs/cifs/connect.c: UNC: \\nas.example.com\theUser kernel: CIFS: fs/cifs/connect.c: Socket created kernel: CIFS: fs/cifs/connect.c: sndbuf 16384 rcvbuf 131072 rcvtimeo 0x834 kernel: CIFS: fs/cifs/connect.c: Demultiplex PID: 532823 kernel: CIFS: fs/cifs/fscache.c: cifs_fscache_get_client_cookie: (0x000[...]8/0x0000[...]d) kernel: CIFS: fs/cifs/connect.c: VFS: in cifs_get_smb_ses as Xid: 685 with uid: 0 kernel: CIFS: fs/cifs/connect.c: Existing smb sess not found kernel: CIFS: fs/cifs/smb2pdu.c: Negotiate protocol kernel: CIFS: fs/cifs/transport.c: Sending smb: smb_len=106 kernel: CIFS: fs/cifs/connect.c: RFC1002 header 0xfa kernel: CIFS: fs/cifs/smb2misc.c: SMB2 data length 122 offset 128 kernel: CIFS: fs/cifs/smb2misc.c: SMB2 len 250 kernel: CIFS: fs/cifs/transport.c: cifs_sync_mid_result: cmd=0 mid=0 state=4 kernel: CIFS: fs/cifs/misc.c: Null buffer passed to cifs_small_buf_release kernel: CIFS: fs/cifs/smb2pdu.c: mode 0x1 kernel: CIFS: fs/cifs/smb2pdu.c: negotiated smb3.0 dialect kernel: CIFS: fs/cifs/asn1.c: OID len = 7 oid = 0x1 0x2 0x348 0xbb92 kernel: CIFS: fs/cifs/asn1.c: OID len = 7 oid = 0x1 0x2 0x348 0x1bb92 kernel: CIFS: fs/cifs/asn1.c: OID len = 10 oid = 0x1 0x3 0x6 0x1 kernel: CIFS: fs/cifs/connect.c: Security Mode: 0x1 Capabilities: 0x300057 TimeAdjust: 0 kernel: CIFS: fs/cifs/smb2pdu.c: Session Setup kernel: CIFS: fs/cifs/smb2pdu.c: sess setup type 5 kernel: CIFS: fs/cifs/cifs_spnego.c: key description = ver=0x2;host=nas.example.com;ip4=10.0.0.1;sec=krb5;uid=0x0;creduid=0x12D687;user=theUser;pid=0x82155 cifs.upcall[532824]: key description: cifs.spnego;0;0;39010000;ver=0x2;host=nas.example.com;ip4=10.0.0.1;sec=krb5;uid=0x0;creduid=0x12D687;user=theUser;pid=0x82155 cifs.upcall[532824]: ver=2 cifs.upcall[532824]: host=nas.example.com cifs.upcall[532824]: ip=10.0.0.1 cifs.upcall[532824]: sec=1 cifs.upcall[532824]: uid=0 cifs.upcall[532824]: creduid=1234567 cifs.upcall[532824]: user=theUser cifs.upcall[532824]: pid=532821 cifs.upcall[532824]: get_cachename_from_process_env: pathname=/proc/532821/environ cifs.upcall[532824]: drop_all_capabilities: Unable to apply capability set: Success cifs.upcall[532824]: Exit status 1 kernel: CIFS: VFS: Verify user has a krb5 ticket and keyutils is installed kernel: CIFS: VFS: \\nas.example.com Send error in SessSetup = -126 kernel: CIFS: fs/cifs/connect.c: VFS: leaving cifs_get_smb_ses (xid = 685) rc = -126 kernel: CIFS: fs/cifs/dfs_cache.c: __dfs_cache_find: search path: \nas.example.com\theUser kernel: CIFS: fs/cifs/dfs_cache.c: get_dfs_referral: get an DFS referral for \nas.example.com\theUser kernel: CIFS: fs/cifs/fscache.c: cifs_fscache_release_client_cookie: (0x0000[...]8/0x00000[...]d) kernel: CIFS: fs/cifs/connect.c: VFS: leaving mount_put_conns (xid = 684) rc = 0 kernel: CIFS: VFS: cifs_mount failed w/return code = -126

2 2

[arch-general] [aur] Could anybody help with Meshroom installation?
by Peter Nabbefeld 13 Dec '20

13 Dec '20

Hello, I tried to install alice-vision-git together with meshroom, but it seems sth. isn't found: Meshroom-2020.1.1]$ Meshroom WARNING:root:== The following "submitters" plugins could not be loaded == * simpleFarmSubmitter: No module named 'simpleFarm' Traceback (most recent call last): File "/usr/lib/python3.9/site-packages/cx_Freeze/initscripts/__startup__.py", line 40, in run module.run() File "/home/peter/.cache/pacaur/meshroom/src/meshroom/setupInitScriptUnix.py", line 39, in run File "meshroom/ui/__main__.py", line 10, in <module> File "/home/peter/.cache/pacaur/meshroom/src/meshroom/meshroom/ui/app.py", line 18, in <module> File "shibokensupport/__feature__.py", line 142, in _import File "/home/peter/.cache/pacaur/meshroom/src/meshroom/meshroom/ui/reconstruction.py", line 169, in <module> File "/home/peter/.cache/pacaur/meshroom/src/meshroom/meshroom/ui/reconstruction.py", line 253, in ViewpointWrapper TypeError: A constant property cannot have a WRITE method or a NOTIFY signal. The strange point for me here is that Meshroom tries to find sth. using my cache - I don't think that's the way Meshroom (or any other application) should work ... Kind regards Peter

1 0

[arch-general] ArchLinux Installation with full encryption and uefi but without lvm
by joerg.jellissen＠t-online.de 13 Dec '20

13 Dec '20

Hello, i have one question. Is it possible to install ArchLinux on an UEFI System with full encryption BUT without lvm? I found no tutorial to do this. I also like to do this without grub. But i don’t understand the differences between systemd / systemd-boot and bootctl. ☹ My english is good, but not so good. ☹ I am sorry for this. Thanks for helping me Mit freundlichen Grüßen Jörg Jellissen Friesenstraße 3 47445 Moers M: 0157 35344218 http://www.joerg-jellissen.de joerg.jellissen(a)t-online.de <mailto:joerg.jellissen@t-online.de>

2 1

[arch-general] pacman trust DB issue
by Frank 13 Dec '20

13 Dec '20

Good afternoon, I'm having an issue with pacman. When running pacman to e.g. do an upgrade I get the following error message: error: cifs-utils: signature from "Tobias Powalowski <tobias.powalowski(a)googlemail.com>" is unknown trust :: File /var/cache/pacman/pkg/cifs-utils-6.11-2-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)). Do you want to delete it? [Y/n] I checked system time which should be fine, so I did a pacman-key --init pacman-key --populate archlinux this ends with the following error: ==> ERROR: Trust database could not be updated. What is it I'm missing? THX Frank -- Frank Zimmermann Jami: rhoihesse Matrix: @zimbi:matrix.org

2 2