From je-vv at e.email Mon Jul 1 23:03:12 2024 From: je-vv at e.email (Javier) Date: Mon, 1 Jul 2024 15:03:12 -0600 Subject: [artix-general] This sshd arch announcement about restarting the service when upgrading to 9.8p1 might be of interest (artix currently on 9.7p1) Message-ID: <92d3213c-5c71-4835-9172-91b06452641a@e.email> Original Arch post: [1]. BTW, moving to 9.8p1 is important to get fixes for current ssh vulnerabilities on [2][3]. Greetings ! -- Javier [1] https://archlinux.org/news/the-sshd-service-needs-to-be-restarted-after-upgrading-to-openssh-98p1 [2] https://stackdiary.com/openssh-race-condition-in-sshd-allows-remote-code-execution/ [3] https://www.computing.co.uk/news/4329906/critical-vulnerability-openssh-uncovered-affects-linux-systems -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature.asc Type: application/pgp-signature Size: 228 bytes Desc: OpenPGP digital signature URL: From somenxavier at posteo.net Wed Jul 10 18:01:31 2024 From: somenxavier at posteo.net (Xavier B.) Date: Wed, 10 Jul 2024 16:01:31 +0000 Subject: [artix-general] setcap assign permanently In-Reply-To: References: <20230908222351.73cfa2c75e0e11fbded73e01@posteo.net> <06f097c1-f246-47db-8d0a-bef7c8e8537b@artixlinux.org> <20230909102615.64e4faae92083ab2d6fe35c7@posteo.net> Message-ID: <20240710180131.bcfe450901ba036bc00ff016@posteo.net> On Sat, 9 Sep 2023 09:42:51 -0500 Jeff Pohlmeyer ha escrit: > > > Note that the "Target" line in the hook file is missing the leading > slash. That is intentional. > > > - Jeff Why this is intentional? Thanks, Xavier From somenxavier at posteo.net Wed Jul 17 21:15:39 2024 From: somenxavier at posteo.net (Xavier B.) Date: Wed, 17 Jul 2024 19:15:39 +0000 Subject: [artix-general] nvidia in kernel Message-ID: <20240717211539.e333994ffabde97856c9706a@posteo.net> Hi, I have a lots of traces debugs in dmesg when I use nouveu driver in kernel > 6.1 but in kernel 6.1 all is fine. I want to triage the bug, but I need help. Where do I start? Thanks in advance, Xavier From yetanothergeek at gmail.com Thu Jul 18 03:44:07 2024 From: yetanothergeek at gmail.com (Jeff Pohlmeyer) Date: Wed, 17 Jul 2024 20:44:07 -0500 Subject: [artix-general] setcap assign permanently In-Reply-To: <20240710180131.bcfe450901ba036bc00ff016@posteo.net> References: <20230908222351.73cfa2c75e0e11fbded73e01@posteo.net> <06f097c1-f246-47db-8d0a-bef7c8e8537b@artixlinux.org> <20230909102615.64e4faae92083ab2d6fe35c7@posteo.net> <20240710180131.bcfe450901ba036bc00ff016@posteo.net> Message-ID: On Wed, Jul 10, 2024 at 11:01?AM Xavier B. wrote: > > Note that the "Target" line in the hook file is missing the leading > > slash. That is intentional. > > Why this is intentional? Because that's how file paths are stored in tar archives. Pacman examines the contents of the package tarball before installing/upgrading to see if any targets match. If you include the leading slash in your hook's Target, then the name won't match and the hook won't run. - Jeff From somenxavier at posteo.net Thu Jul 18 14:23:29 2024 From: somenxavier at posteo.net (Xavier B.) Date: Thu, 18 Jul 2024 12:23:29 +0000 Subject: [artix-general] setcap assign permanently In-Reply-To: References: <20230908222351.73cfa2c75e0e11fbded73e01@posteo.net> <06f097c1-f246-47db-8d0a-bef7c8e8537b@artixlinux.org> <20230909102615.64e4faae92083ab2d6fe35c7@posteo.net> <20240710180131.bcfe450901ba036bc00ff016@posteo.net> Message-ID: <20240718142329.8343228b9c1c9f1da29950dc@posteo.net> Thanks a lot, Jeff. It works. On Wed, 17 Jul 2024 20:44:07 -0500 Jeff Pohlmeyer ha escrit: > On Wed, Jul 10, 2024 at 11:01?AM Xavier B. wrote: > > > Note that the "Target" line in the hook file is missing the leading > > > slash. That is intentional. > > > > Why this is intentional? > > Because that's how file paths are stored in tar archives. Pacman > examines the contents of the package tarball before > installing/upgrading to see if any targets match. If you include the > leading slash in your hook's Target, then the name won't match and the > hook won't run. > > - Jeff From je-vv at e.email Sun Jul 21 04:17:06 2024 From: je-vv at e.email (Javier) Date: Sat, 20 Jul 2024 20:17:06 -0600 Subject: [artix-general] libp11 version incompatibility with rng-tools Message-ID: Hello ! Currently libp11 provides: > libp11 /usr/lib/engines-3/libpkcs11.so > libp11 /usr/lib/engines-3/pkcs11.so > libp11 /usr/lib/libp11.so > libp11 /usr/lib/libp11.so.2 > libp11 /usr/lib/libp11.so.2.6.0 And it so happens rng-tools depends on libp11, but with specific soname version: > /var/log/dinit/rngd.log:/usr/bin/rngd: error while loading shared libraries: libp11.so.3: cannot open shared object file: No such file or directory I don't see Arch providing a new version of libp11: > pacman -Ss libp11 > system/libp11-kit 0.25.5-1 [installed] > Loads and enumerates PKCS#11 modules (library) > world/libp11 0.4.12-3 [installed] > A library implementing a small layer on top of the PKCS11 API > extra/libp11 0.4.12-3 [installed] > A library implementing a small layer on top of the PKCS11 API And rng-tools is even newer on Arch than Artix, besides, I tried installing the Arch newer one with same results: > world/rng-tools 6.16-2 [installed] > extra/rng-tools 6.17-1 [installed: 6.16-2] At this point I don't know if looking in the archive an older version of rng-tools would help. But it seems instead lib11 mew libraries are required. Thanks ! -- Javier -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature.asc Type: application/pgp-signature Size: 228 bytes Desc: OpenPGP digital signature URL: From somenxavier at posteo.net Thu Jul 25 22:34:30 2024 From: somenxavier at posteo.net (Xavier B.) Date: Thu, 25 Jul 2024 20:34:30 +0000 Subject: [artix-general] nvidia in kernel In-Reply-To: <20240717211539.e333994ffabde97856c9706a@posteo.net> References: <20240717211539.e333994ffabde97856c9706a@posteo.net> Message-ID: <20240725223430.2956e84130ad51ff620bebe8@posteo.net> It happens in ALL linux-lts61. Any hints? On Wed, 17 Jul 2024 21:15:39 +0200 "Xavier B." ha escrit: > Hi, > > I have a lots of traces debugs in dmesg when I use nouveu driver in kernel > 6.1 but in kernel 6.1 all is fine. > I want to triage the bug, but I need help. Where do I start? > > Thanks in advance, > Xavier From nous at artixlinux.org Fri Jul 26 12:48:56 2024 From: nous at artixlinux.org (Christos Nouskas) Date: Fri, 26 Jul 2024 13:48:56 +0300 Subject: [artix-general] nvidia in kernel In-Reply-To: <20240725223430.2956e84130ad51ff620bebe8@posteo.net> References: <20240717211539.e333994ffabde97856c9706a@posteo.net> <20240725223430.2956e84130ad51ff620bebe8@posteo.net> Message-ID: <2056349E-FD52-4287-9ED7-CD5E18EEBA25@artixlinux.org> The recommended way is bisecting the kernel (google it). On July 25, 2024 11:34:30 PM GMT+03:00, "Xavier B." wrote: >It happens in ALL linux-lts61. > >Any hints? > >On Wed, 17 Jul 2024 21:15:39 +0200 >"Xavier B." ha escrit: > >> Hi, >> >> I have a lots of traces debugs in dmesg when I use nouveu driver in kernel > 6.1 but in kernel 6.1 all is fine. >> I want to triage the bug, but I need help. Where do I start? >> >> Thanks in advance, >> Xavier >-- >artix-general mailing list >artix-general at artixlinux.org >https://lists.artixlinux.org/listinfo/artix-general -------------- next part -------------- An HTML attachment was scrubbed... URL: From somenxavier at posteo.net Fri Jul 26 13:38:47 2024 From: somenxavier at posteo.net (Xavier B.) Date: Fri, 26 Jul 2024 11:38:47 +0000 Subject: [artix-general] nvidia in kernel In-Reply-To: <2056349E-FD52-4287-9ED7-CD5E18EEBA25@artixlinux.org> References: <20240717211539.e333994ffabde97856c9706a@posteo.net> <20240725223430.2956e84130ad51ff620bebe8@posteo.net> <2056349E-FD52-4287-9ED7-CD5E18EEBA25@artixlinux.org> Message-ID: <20240726133847.bd07d6d9fa746d86deee87b9@posteo.net> I did not find anything. For temporary workarround, I disabled nouveau from kernel: nouveau.modeset=0 i915.modeset=1 in /etc/default/grub but the bug is still present if I remove that line in grub. On Fri, 26 Jul 2024 13:48:56 +0300 Christos Nouskas ha escrit: > The recommended way is bisecting the kernel (google it). > > On July 25, 2024 11:34:30 PM GMT+03:00, "Xavier B." wrote: > >It happens in ALL linux-lts61. > > > >Any hints? > > > >On Wed, 17 Jul 2024 21:15:39 +0200 > >"Xavier B." ha escrit: > > > >> Hi, > >> > >> I have a lots of traces debugs in dmesg when I use nouveu driver in kernel > 6.1 but in kernel 6.1 all is fine. > >> I want to triage the bug, but I need help. Where do I start? > >> > >> Thanks in advance, > >> Xavier > >-- > >artix-general mailing list > >artix-general at artixlinux.org > >https://lists.artixlinux.org/listinfo/artix-general From info at miraa.sakura.ne.jp Fri Jul 26 14:05:33 2024 From: info at miraa.sakura.ne.jp (www.miraa.jp) Date: Fri, 26 Jul 2024 21:05:33 +0900 Subject: [artix-general] nvidia in kernel In-Reply-To: <20240726133847.bd07d6d9fa746d86deee87b9@posteo.net> References: <20240717211539.e333994ffabde97856c9706a@posteo.net> <20240725223430.2956e84130ad51ff620bebe8@posteo.net> <2056349E-FD52-4287-9ED7-CD5E18EEBA25@artixlinux.org> <20240726133847.bd07d6d9fa746d86deee87b9@posteo.net> Message-ID: Dear Xavier, > I did not find anything. I hope the following links will help you. - https://docs.kernel.org/admin-guide/verify-bugs-and-bisect-regressions.html#the-essence-of-the-process-aka-tl-dr - https://git-scm.com/docs/git-bisect Best regards, ikedaC On 7/26/24 8:38 PM, Xavier B. wrote: > I did not find anything. > > For temporary workarround, I disabled nouveau from kernel: > > nouveau.modeset=0 i915.modeset=1 > > in /etc/default/grub > > but the bug is still present if I remove that line in grub. > > > On Fri, 26 Jul 2024 13:48:56 +0300 > Christos Nouskas ha escrit: > >> The recommended way is bisecting the kernel (google it). >> >> On July 25, 2024 11:34:30 PM GMT+03:00, "Xavier B." wrote: >>> It happens in ALL linux-lts61. >>> >>> Any hints? >>> >>> On Wed, 17 Jul 2024 21:15:39 +0200 >>> "Xavier B." ha escrit: >>> >>>> Hi, >>>> >>>> I have a lots of traces debugs in dmesg when I use nouveu driver in kernel > 6.1 but in kernel 6.1 all is fine. >>>> I want to triage the bug, but I need help. Where do I start? >>>> >>>> Thanks in advance, >>>> Xavier >>> -- >>> artix-general mailing list >>> artix-general at artixlinux.org >>> https://lists.artixlinux.org/listinfo/artix-general -------------------- ikedaC info at miraa.sakura.ne.jp http(s)://www.miraa.jp/ From somenxavier at posteo.net Sat Jul 27 15:29:26 2024 From: somenxavier at posteo.net (Xavier B.) Date: Sat, 27 Jul 2024 13:29:26 +0000 Subject: [artix-general] nvidia in kernel In-Reply-To: References: <20240717211539.e333994ffabde97856c9706a@posteo.net> <20240725223430.2956e84130ad51ff620bebe8@posteo.net> <2056349E-FD52-4287-9ED7-CD5E18EEBA25@artixlinux.org> <20240726133847.bd07d6d9fa746d86deee87b9@posteo.net> Message-ID: <20240727152926.dccaf6e12a419bc8cd6d997a@posteo.net> What do you mean? In conclusion: make custom kernel with 6.1 with adds from 6.10 and then test it? But is there any way to test which part of 6.10 fail? Which log I have to inspect? /var/log/error.log provides a lot of information: Jul 26 13:12:41 coronari kernel: nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 6013d4 [ TIMEOUT ] Jul 26 13:12:43 coronari kernel: nouveau 0000:01:00.0: gr: init failed, -16 Jul 26 13:12:44 coronari kernel: nouveau 0000:01:00.0: sec2:cmdq: timeout waiting for reply Jul 26 13:12:46 coronari kernel: nouveau 0000:01:00.0: init failed with -16 Jul 26 13:12:46 coronari kernel: nouveau: DRM-master:00000000:00000080: init failed with -16 Jul 26 13:12:46 coronari kernel: nouveau: DRM-master:00000000:00000000: init failed with -16 Jul 26 13:12:46 coronari kernel: nouveau 0000:01:00.0: DRM: Client resume failed with error: -16 Jul 26 13:12:46 coronari kernel: nouveau 0000:01:00.0: DRM: resume failed with: -16 Jul 26 13:13:01 coronari kernel: nouveau 0000:01:00.0: Xorg[2713]: failed to idle channel 3 [Xorg[2713]] but I don't know what exacty fails! Thanks in advance, On Fri, 26 Jul 2024 21:05:33 +0900 "www.miraa.jp" ha escrit: > Dear Xavier, > > > I did not find anything. > I hope the following links will help you. > > - > https://docs.kernel.org/admin-guide/verify-bugs-and-bisect-regressions.html#the-essence-of-the-process-aka-tl-dr > - https://git-scm.com/docs/git-bisect > > Best regards, > ikedaC > > On 7/26/24 8:38 PM, Xavier B. wrote: > > I did not find anything. > > > > For temporary workarround, I disabled nouveau from kernel: > > > > nouveau.modeset=0 i915.modeset=1 > > > > in /etc/default/grub > > > > but the bug is still present if I remove that line in grub. > > > > > > On Fri, 26 Jul 2024 13:48:56 +0300 > > Christos Nouskas ha escrit: > > > >> The recommended way is bisecting the kernel (google it). > >> > >> On July 25, 2024 11:34:30 PM GMT+03:00, "Xavier B." wrote: > >>> It happens in ALL linux-lts61. > >>> > >>> Any hints? > >>> > >>> On Wed, 17 Jul 2024 21:15:39 +0200 > >>> "Xavier B." ha escrit: > >>> > >>>> Hi, > >>>> > >>>> I have a lots of traces debugs in dmesg when I use nouveu driver in kernel > 6.1 but in kernel 6.1 all is fine. > >>>> I want to triage the bug, but I need help. Where do I start? > >>>> > >>>> Thanks in advance, > >>>> Xavier > >>> -- > >>> artix-general mailing list > >>> artix-general at artixlinux.org > >>> https://lists.artixlinux.org/listinfo/artix-general > > -------------------- > ikedaC > info at miraa.sakura.ne.jp > http(s)://www.miraa.jp/ > > -- > artix-general mailing list > artix-general at artixlinux.org > https://lists.artixlinux.org/listinfo/artix-general From info at miraa.sakura.ne.jp Sat Jul 27 17:54:58 2024 From: info at miraa.sakura.ne.jp (www.miraa.jp) Date: Sun, 28 Jul 2024 00:54:58 +0900 Subject: [artix-general] nvidia in kernel In-Reply-To: <20240727152926.dccaf6e12a419bc8cd6d997a@posteo.net> References: <20240717211539.e333994ffabde97856c9706a@posteo.net> <20240725223430.2956e84130ad51ff620bebe8@posteo.net> <2056349E-FD52-4287-9ED7-CD5E18EEBA25@artixlinux.org> <20240726133847.bd07d6d9fa746d86deee87b9@posteo.net> <20240727152926.dccaf6e12a419bc8cd6d997a@posteo.net> Message-ID: <2fcfef13-373d-4680-bc15-adfb1f39fbee@miraa.sakura.ne.jp> Dear Xavier, > In conclusion: make custom kernel with 6.1 with adds from 6.10 and then test it? If you have narrowed down where the cause could exist as you have already written, I don't see much point in including the latest codes in your search. > I have a lots of traces debugs in dmesg when I use nouveu driver in kernel > 6.1 but in kernel 6.1 all is fine. Best regards, ikedaC On 7/27/24 10:29 PM, Xavier B. wrote: > What do you mean? > > In conclusion: make custom kernel with 6.1 with adds from 6.10 and then test it? > But is there any way to test which part of 6.10 fail? Which log I have to inspect? /var/log/error.log provides a lot of information: > > Jul 26 13:12:41 coronari kernel: nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 6013d4 [ TIMEOUT ] > Jul 26 13:12:43 coronari kernel: nouveau 0000:01:00.0: gr: init failed, -16 > Jul 26 13:12:44 coronari kernel: nouveau 0000:01:00.0: sec2:cmdq: timeout waiting for reply > Jul 26 13:12:46 coronari kernel: nouveau 0000:01:00.0: init failed with -16 > Jul 26 13:12:46 coronari kernel: nouveau: DRM-master:00000000:00000080: init failed with -16 > Jul 26 13:12:46 coronari kernel: nouveau: DRM-master:00000000:00000000: init failed with -16 > Jul 26 13:12:46 coronari kernel: nouveau 0000:01:00.0: DRM: Client resume failed with error: -16 > Jul 26 13:12:46 coronari kernel: nouveau 0000:01:00.0: DRM: resume failed with: -16 > Jul 26 13:13:01 coronari kernel: nouveau 0000:01:00.0: Xorg[2713]: failed to idle channel 3 [Xorg[2713]] > > but I don't know what exacty fails! > > Thanks in advance, > > On Fri, 26 Jul 2024 21:05:33 +0900 > "www.miraa.jp" ha escrit: > >> Dear Xavier, >> >>> I did not find anything. >> I hope the following links will help you. >> >> - >> https://docs.kernel.org/admin-guide/verify-bugs-and-bisect-regressions.html#the-essence-of-the-process-aka-tl-dr >> - https://git-scm.com/docs/git-bisect >> >> Best regards, >> ikedaC >> >> On 7/26/24 8:38 PM, Xavier B. wrote: >>> I did not find anything. >>> >>> For temporary workarround, I disabled nouveau from kernel: >>> >>> nouveau.modeset=0 i915.modeset=1 >>> >>> in /etc/default/grub >>> >>> but the bug is still present if I remove that line in grub. >>> >>> >>> On Fri, 26 Jul 2024 13:48:56 +0300 >>> Christos Nouskas ha escrit: >>> >>>> The recommended way is bisecting the kernel (google it). >>>> >>>> On July 25, 2024 11:34:30 PM GMT+03:00, "Xavier B." wrote: >>>>> It happens in ALL linux-lts61. >>>>> >>>>> Any hints? >>>>> >>>>> On Wed, 17 Jul 2024 21:15:39 +0200 >>>>> "Xavier B." ha escrit: >>>>> >>>>>> Hi, >>>>>> >>>>>> I have a lots of traces debugs in dmesg when I use nouveu driver in kernel > 6.1 but in kernel 6.1 all is fine. >>>>>> I want to triage the bug, but I need help. Where do I start? >>>>>> >>>>>> Thanks in advance, >>>>>> Xavier >>>>> -- >>>>> artix-general mailing list >>>>> artix-general at artixlinux.org >>>>> https://lists.artixlinux.org/listinfo/artix-general >> -------------------- >> ikedaC >> info at miraa.sakura.ne.jp >> http(s)://www.miraa.jp/ >> >> -- >> artix-general mailing list >> artix-general at artixlinux.org >> https://lists.artixlinux.org/listinfo/artix-general -------------------- ikedaC info at miraa.sakura.ne.jp http(s)://www.miraa.jp/ From je-vv at e.email Sun Jul 28 05:33:12 2024 From: je-vv at e.email (Javier) Date: Sat, 27 Jul 2024 21:33:12 -0600 Subject: [artix-general] Thunderbird 115.13.0 breaks sequoia-octopus-librnp and sequoia-octopus-librnp-git Message-ID: Hi ! Recent thunderbird upgrade to 115.13.0 breaks both sequoia-octopus-librnp and sequoia-octopus-librnp-git. For the non git version (omniverse): > JavaScript error: chrome://openpgp/content/BondOpenPGP.jsm, line 68: Error: RNP version 1.8.1-519f010+sequoia-openpgp-1.19.0 does not meet minimum required 0.17.1. > 2024-07-28 02:42:59.285675724 UTC: sequoia-octopus: rnp_identifier_iterator_create: parameter "ctx" is null For the git version (galaxy): > JavaScript error: chrome://openpgp/content/BondOpenPGP.jsm, line 68: Error: RNP version 1.8.0-7c3868e+sequoia-openpgp-1.19.0 does not meet minimum required 0.17.1. > JavaScript error: chrome://messenger/content/aboutMessage.js, line 119: NS_ERROR_ILLEGAL_VALUE: Component returned failure code: 0x80070057 (NS_ERROR_ILLEGAL_VALUE) [nsIWebProgress.addProgressListener] It seems a newer version is required by TB... I see a v1.9.0 tag available from the upstream repo [1], so not sure if all required is using that tag, whether on the non git package, or the git package or both... BTW, I tried getting a snapshot from AUR of the sequoia-octopus-librnp [2] and update it from 1.8.0 to 1.9.0, and I found weird linking errors: > = note: /usr/bin/ld: /home/general/.pkgs/src/others/sequoia-octopus-librnp/src/sequoia-octopus-librnp-v1.9.0/target/release/deps/libgit2-4f9e09f3140e75b9.rlib(git2-4f9e09f3140e75b9.git2.98da0f301bb5e698-cgu.11.rcgu.o): in function `::drop': > git2.98da0f301bb5e698-cgu.11:(.text._ZN68_$LT$git2..signature..Signature$u20$as$u20$core..ops..drop..Drop$GT$4drop17h9360da20e5b6ed7aE+0x10): undefined reference to `git_signature_free' And a bunch others pretty similar, all relate with git... Sad, :( At any rate, reverting TB and preventing it to upgrade is the workaround, whether using the non git or the git version of sequoia-octopus-librnp. Thanks ! -- Javier [1] https://gitlab.com/sequoia-pgp/sequoia-octopus-librnp/-/tags/v1.9.0 [2] https://aur.archlinux.org/packages/sequoia-octopus-librnp -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature.asc Type: application/pgp-signature Size: 228 bytes Desc: OpenPGP digital signature URL: From je-vv at e.email Sun Jul 28 06:07:01 2024 From: je-vv at e.email (Javier) Date: Sat, 27 Jul 2024 22:07:01 -0600 Subject: [artix-general] [rng-utils] rngd failing to start due to missing libp11.so.3, when libp11.so.2 is available Message-ID: <88be523a-434e-40c1-9951-ac26d57c483f@e.email> Hello ! It's been a while since rngd is failing to start with: > /usr/bin/rngd: error while loading shared libraries: libp11.so.3: cannot open shared object file: No such file or directory But then: > % ls /usr/lib/libp11.so* > /usr/lib/libp11.so@ /usr/lib/libp11.so.2@ /usr/lib/libp11.so.2.6.0* And: > % pacman -Qo /usr/lib/libp11.so > /usr/lib/libp11.so is owned by libp11 0.4.12-3 Moreover: > % pacman -Ss libp11 > system/libp11-kit 0.25.5-1 [installed] > Loads and enumerates PKCS#11 modules (library) > world/libp11 0.4.12-3 [installed] > A library implementing a small layer on top of the PKCS11 API > extra/libp11 0.4.12-3 [installed] > A library implementing a small layer on top of the PKCS11 API It's not that artix is out of date with respect to arch, they both provide the same version of libp11. Though rng-tools on artix is behind arch (6.16-2 vs. 6.17-1): > % pacman -Ss rng-tools > world/rng-tools 6.16-2 [installed] > Random number generator related utilities > world/rng-tools-dinit 20211102-4 (dinit-world) [installed] > dinit service scripts for rng-tools > world/rng-tools-openrc 20210505-1 (openrc-galaxy) > OpenRC rng-tools init script > world/rng-tools-runit 20180314-5 (runit-galaxy) > Runit service script for rng-tools > world/rng-tools-s6 20230829-1 (s6-world) > s6-rc service scripts for rng-tools > extra/rng-tools 6.17-1 [installed: 6.16-2] > Random number generator related utilities But that shouldn't be the issues, since a more recent version of rngd would required even more up to date libp11 dependencies. On arch, I don't see issues filed against libp11 neither rng-tools, so that confuses me. Anyone else noticing it? I have no clue how to deal with this. Thanks ! -- Javier -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature.asc Type: application/pgp-signature Size: 228 bytes Desc: OpenPGP digital signature URL: From artist at artixlinux.org Sun Jul 28 16:51:21 2024 From: artist at artixlinux.org (artist) Date: Sun, 28 Jul 2024 16:51:21 +0200 Subject: [artix-general] Thunderbird 115.13.0 breaks sequoia-octopus-librnp and sequoia-octopus-librnp-git In-Reply-To: References: Message-ID: sequoia-octopus-librnp-git has been updated to the latest version in galaxy, but not been tested. sequoia-octopus-librnp no longer serves any purpose and has been removed. artist On a bended knee, or systemd, you will never live free On 7/28/24 05:33, Javier wrote: > Hi ! > > Recent thunderbird upgrade to 115.13.0 breaks both > sequoia-octopus-librnp and sequoia-octopus-librnp-git.? For the non > git version (omniverse): > >> JavaScript error: chrome://openpgp/content/BondOpenPGP.jsm, line 68: >> Error: RNP version 1.8.1-519f010+sequoia-openpgp-1.19.0 does not meet >> minimum required 0.17.1. >> 2024-07-28 02:42:59.285675724 UTC: sequoia-octopus: >> rnp_identifier_iterator_create: parameter "ctx" is null > > For the git version (galaxy): > >> JavaScript error: chrome://openpgp/content/BondOpenPGP.jsm, line 68: >> Error: RNP version 1.8.0-7c3868e+sequoia-openpgp-1.19.0 does not meet >> minimum required 0.17.1. >> JavaScript error: chrome://messenger/content/aboutMessage.js, line >> 119: NS_ERROR_ILLEGAL_VALUE: Component returned failure code: >> 0x80070057 (NS_ERROR_ILLEGAL_VALUE) [nsIWebProgress.addProgressListener] > > It seems a newer version is required by TB... > > I see a v1.9.0 tag available from the upstream repo [1], so not sure > if all required is using that tag, whether on the non git package, or > the git package or both...? BTW, I tried getting a snapshot from AUR > of the sequoia-octopus-librnp [2] and update it from 1.8.0 to 1.9.0, > and I found weird linking errors: > >> ? = note: /usr/bin/ld: >> /home/general/.pkgs/src/others/sequoia-octopus-librnp/src/sequoia-octopus-librnp-v1.9.0/target/release/deps/libgit2-4f9e09f3140e75b9.rlib(git2-4f9e09f3140e75b9.git2.98da0f301bb5e698-cgu.11.rcgu.o): >> in function `> core::ops::drop::Drop>::drop': >> git2.98da0f301bb5e698-cgu.11:(.text._ZN68_$LT$git2..signature..Signature$u20$as$u20$core..ops..drop..Drop$GT$4drop17h9360da20e5b6ed7aE+0x10): >> undefined reference to `git_signature_free' > > And a bunch others pretty similar, all relate with git...? Sad, :( > > At any rate, reverting TB and preventing it to upgrade is the > workaround, whether using the non git or the git version of > sequoia-octopus-librnp. > > Thanks ! > > From je-vv at e.email Mon Jul 29 04:09:54 2024 From: je-vv at e.email (Javier) Date: Sun, 28 Jul 2024 20:09:54 -0600 Subject: [artix-general] Thunderbird 115.13.0 breaks sequoia-octopus-librnp and sequoia-octopus-librnp-git In-Reply-To: References: Message-ID: On 2024-07-28 08:51 AM, artist wrote: > sequoia-octopus-librnp-git has been updated to the latest version in galaxy, but not been tested. > sequoia-octopus-librnp no longer serves any purpose and has been removed. > > artist sequoia-octopus-librnp-git reached galaxy already, and it's working fine :) Thanks a lot @artist ! -- Javier PS: sequoia-octopus is already gone from the repos BTW. -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature.asc Type: application/pgp-signature Size: 228 bytes Desc: OpenPGP digital signature URL: