From je-vv at e.email Wed Mar 1 08:02:44 2023 From: je-vv at e.email (Javier) Date: Wed, 1 Mar 2023 01:02:44 -0600 Subject: [artix-general] [universe] ungoogled-chromium 110.0.5481.177-1 missing package signature Message-ID: Just like the title says... I confirmed the lack of the signature on [1] and [2], not sure the rest... -- Javier [1] https://universe.artixlinux.org [2] https://mirror1.artixlinux.org/universe -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 228 bytes Desc: OpenPGP digital signature URL: From je-vv at e.email Wed Mar 1 09:24:09 2023 From: je-vv at e.email (Javier) Date: Wed, 1 Mar 2023 02:24:09 -0600 Subject: [artix-general] [universe] ungoogled-chromium 110.0.5481.177-1 missing package signature In-Reply-To: References: Message-ID: <69f586d7-ed62-d410-1f54-c0d99c0d16a0@e.email> On 3/1/23 01:02, Javier wrote: > Just like the title says...? I confirmed the lack of the signature on [1] and [2], not sure the rest... Now available. Thanks ! -- Javier -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 228 bytes Desc: OpenPGP digital signature URL: From charliebrownau at protonmail.com Wed Mar 1 09:53:04 2023 From: charliebrownau at protonmail.com (charliebrownau) Date: Wed, 01 Mar 2023 08:53:04 +0000 Subject: [artix-general] Is it Time to reject Wayland and pipewire , just as some rejected SubvertD Message-ID: <_6Mvnw3Px8jvRGcYbxILIkkfyMksvFNKBElJnrKBis5_3Nfoth0VOKWbSkAKy1D8wBt20vJHMCPOVZjj0Vgz76w0IMGeMaUDIE3bcXHpBUA=@protonmail.com> Gday Is it Time to reject Wayland and pipewire , just as some rejected SubvertD Why isnt their efforts to make programs work without subvertD Dbus Python pipewire mono/dotnet Why do we need the latest shiney thing Why cant we go out own way , with our own future Do we really need ((( CORPORATIONS ))), ((( CoC))) and ((( FREE DESKTOP ))) pushed down everyone's Distro Or is Arch, Artix and others just being complaint sheeple accepting and going along with latest thing pushed to screw over the community and Linux itself I can see a time that people will just give up on Linux and the huge problems exist with it and getting WORSE and Migrate to BSD instead to start over a fresh and hopefully keep the parasites and the problems out in the first place Do we really need the latest shiney patched on the hour or maybe its time to reject ((( ROLLING ))) and move to a long term just works stable approach to software releases and software design ________ Regards Charliebrownau * Email - charliebrownau at protonmail.com * Website - http://charliebrownau.com/ * Video - https://www.JoshwhoTV.com/channel/charliebrownau * Social - https://pieville.net/@charliebrownau * Delta Chat - charliebrownau at joshwho.net Sent with Proton Mail secure email. ------- Original Message ------- On Wednesday, March 1st, 2023 at 8:24 AM, artix-general-request at artixlinux.org wrote: > Send artix-general mailing list submissions to > artix-general at artixlinux.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.artixlinux.org/listinfo/artix-general > or, via email, send a message with subject or body 'help' to > artix-general-request at artixlinux.org > > You can reach the person managing the list at > artix-general-owner at artixlinux.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of artix-general digest..." > > > Today's Topics: > > 1. Re: Thunderbird (world) 102.7 breaks sequoia-octopus-librnp > (universe) 1.4.1-2 (Javier) > 2. Re: FYI: Thunderbird 102.7 not able to authenticate to > enterprise 0365 (depends on admin actions) (Javier) > 3. thunar reporting no gvs on wayland/wayfire (Javier) > 4. Broken prometheus-openrc package (??????? ?????) > 5. [universe] ungoogled-chromium 110.0.5481.177-1 missing > package signature (Javier) > 6. Re: [universe] ungoogled-chromium 110.0.5481.177-1 missing > package signature (Javier) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sat, 18 Feb 2023 16:50:24 -0600 > From: Javier je-vv at e.email > > To: artix-general at artixlinux.org > Subject: Re: [artix-general] Thunderbird (world) 102.7 breaks > sequoia-octopus-librnp (universe) 1.4.1-2 > Message-ID: 4e30bc12-6725-ef69-25e3-f18be71bf9e0 at e.email > > Content-Type: text/plain; charset="utf-8"; Format="flowed" > > On 2/18/23 12:54, artist wrote: > > > sequoia-octopus-librnp-git is now in universe for any testers > > > > artist > > > Working fine with up to date TB (102.7.2-1). > > Thanks a lot @artist > > -- > Javier > > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: OpenPGP_signature > Type: application/pgp-signature > Size: 228 bytes > Desc: OpenPGP digital signature > URL: https://lists.artixlinux.org/archives/artix-general/attachments/20230218/6a8308e6/attachment-0001.sig > > > ------------------------------ > > Message: 2 > Date: Tue, 21 Feb 2023 00:18:50 -0600 > From: Javier je-vv at e.email > > To: artix-general at artixlinux.org > Subject: Re: [artix-general] FYI: Thunderbird 102.7 not able to > authenticate to enterprise 0365 (depends on admin actions) > Message-ID: b73eeb05-fe5e-1d8a-e2a8-e669a2df52a9 at e.email > > Content-Type: text/plain; charset="utf-8"; Format="flowed" > > On 2/7/23 12:05, artist wrote: > > > The current version?betterbird-102.7.1-7 in omniverse works, also for add-ons like TB-Sync. > > Intermittent issues seem related to 'fixes' confirmed to break o365 as confirmed by Money$lot here: https://twitter.com/MSFT365Status > > > > artist > > > Just to confirm, I'm using latest 102.7.2-1 TB Artix version, and it's working fine, as before authentication got broken. > > Actually I added to "TBSync" + "Provider for Exchange ActiveSync", "Category Manager" from the same set of extensions. However even with that combo, I didn't get "Contacts" to actually work for me. It wasn't working before, I was just waiting that perhaps with "Category Manager" addition, those enterprise contacts would show up, :( > > Is there any other solution, apart from TBSync and company, plus perhaps davmail, that anyone is aware to work fine with enterprise o365? This is apparently a known issue, according to [1] and [2]. > > -- > Javier > > > [1] https://github.com/jobisoft/EAS-4-TbSync/issues/213 > [2] https://github.com/jobisoft/TbSync/issues/620 > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: OpenPGP_signature > Type: application/pgp-signature > Size: 228 bytes > Desc: OpenPGP digital signature > URL: https://lists.artixlinux.org/archives/artix-general/attachments/20230221/0e03cda3/attachment-0001.sig > > > ------------------------------ > > Message: 3 > Date: Mon, 27 Feb 2023 01:18:35 -0600 > From: Javier je-vv at e.email > > To: artix-general artix-general at artixlinux.org > > Subject: [artix-general] thunar reporting no gvs on wayland/wayfire > Message-ID: 0919bd54-b987-e039-e6e1-67aa718af321 at e.email > > Content-Type: text/plain; charset="utf-8"; Format="flowed" > > Hi ! > > For those using thunar or nemo under wayland, but not through gnome neither kde, do you know how to make them work with gvfs. On thunar, at least on advanced preferences I can see a big note on yellow warning about the lack of gvfs. > > On Xorg, with LXQt, thunar doesn't complain at all, and show the trash, and the FS correctly, of course no warnings about gvfs on the advanced preferences. I have gvfs and a bunch of its plugins already installed. > > An alternative is using nautilus, but it's not respecting $GDK_DPI_SCALE env var, and the gsettings for gnome do not work, so I can't really read the tiny letters. But it does show the trash, so I guess no problems with it. > > Any one using a gui file manager, hopefully gtk, with gvfs, under wayland, and working fine? > > Thanks ! > > -- > Javier > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: OpenPGP_signature > Type: application/pgp-signature > Size: 228 bytes > Desc: OpenPGP digital signature > URL: https://lists.artixlinux.org/archives/artix-general/attachments/20230227/aff82a3f/attachment-0001.sig > > > ------------------------------ > > Message: 4 > Date: Tue, 28 Feb 2023 15:22:44 +0300 > From: ??????? ????? doletov.fyodor at yandex.ru > > To: "artix-general at artixlinux.org" artix-general at artixlinux.org > > Subject: [artix-general] Broken prometheus-openrc package > Message-ID: 236651677586591 at mail.yandex.ru > > Content-Type: text/plain; charset="us-ascii" > > An HTML attachment was scrubbed... > URL: https://lists.artixlinux.org/archives/artix-general/attachments/20230228/e2a0751e/attachment-0001.htm > > > ------------------------------ > > Message: 5 > Date: Wed, 1 Mar 2023 01:02:44 -0600 > From: Javier je-vv at e.email > > To: artix-general artix-general at artixlinux.org > > Subject: [artix-general] [universe] ungoogled-chromium > 110.0.5481.177-1 missing package signature > Message-ID: e3d19aad-ee4a-4b11-6be9-946788029b40 at e.email > > Content-Type: text/plain; charset="utf-8"; Format="flowed" > > Just like the title says... I confirmed the lack of the signature on [1] and [2], not sure the rest... > > -- > Javier > > [1] https://universe.artixlinux.org > [2] https://mirror1.artixlinux.org/universe > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: OpenPGP_signature > Type: application/pgp-signature > Size: 228 bytes > Desc: OpenPGP digital signature > URL: https://lists.artixlinux.org/archives/artix-general/attachments/20230301/794a65e2/attachment-0001.sig > > > ------------------------------ > > Message: 6 > Date: Wed, 1 Mar 2023 02:24:09 -0600 > From: Javier je-vv at e.email > > To: artix-general artix-general at artixlinux.org > > Subject: Re: [artix-general] [universe] ungoogled-chromium > 110.0.5481.177-1 missing package signature > Message-ID: 69f586d7-ed62-d410-1f54-c0d99c0d16a0 at e.email > > Content-Type: text/plain; charset="utf-8"; Format="flowed" > > On 3/1/23 01:02, Javier wrote: > > > Just like the title says...? I confirmed the lack of the signature on [1] and [2], not sure the rest... > > > Now available. Thanks ! > > -- > Javier > > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: OpenPGP_signature > Type: application/pgp-signature > Size: 228 bytes > Desc: OpenPGP digital signature > URL: https://lists.artixlinux.org/archives/artix-general/attachments/20230301/6fe72c67/attachment.sig > > > ------------------------------ > > Subject: Digest Footer > > artix-general mailing list > artix-general at artixlinux.org > https://lists.artixlinux.org/listinfo/artix-general > > > ------------------------------ > > End of artix-general Digest, Vol 46, Issue 1 > ******************************************** From m1sha at linux.ucla.edu Tue Mar 7 21:38:44 2023 From: m1sha at linux.ucla.edu (Misha Kruezhev) Date: Tue, 07 Mar 2023 21:38:44 +0100 Subject: [artix-general] kcoreaddons-5.103.0-1-x86_64 (world) supposedly corrupt Message-ID: # pacman -Sy polkit-kde-agent using 10 different mirrors I am getting "error: failed retrieving file 'kcoreaddons-5.103.0-1-x86_64.pkg.tar.zst' from : Maximum file size exceeded" supposedly the server was down, so the package probably failed to build properly. From jc_gargma at iserlohn-fortress.net Tue Mar 7 22:08:33 2023 From: jc_gargma at iserlohn-fortress.net (jc_gargma) Date: Tue, 07 Mar 2023 13:08:33 -0800 Subject: [artix-general] kcoreaddons-5.103.0-1-x86_64 (world) supposedly corrupt In-Reply-To: References: Message-ID: <13221659.uLZWGnKmhe@iserlohn-fortress.net> > supposedly the server was down, so the package probably failed to > build properly. It is not just kcoreaddons. I was trying to update one of my devices on Monday and found that every single kde frameworks 5.103.0 package is either corrupted in the manner you describe, or is rejected by pacman due to an invalid package signature. Specifically, frameworkintegration kdeclarative kdecoreaddons kded kidletime kitemviews kjobwigdets oxygen-icons are corrupted. When these are set to --ignore, all others fail signature checking. It is doubly odd as I updated another device on Sunday and the same packages were downloaded and installed without issue. I can only conclude artix pushed a stealth rebuild of kde frameworks 5.103.0 on Monday in which something went very wrong. Or the master package storage server has suffered massive data corruption which is being circulated out to mirrors. -jc -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 228 bytes Desc: This is a digitally signed message part. URL: From artist at artixlinux.org Tue Mar 7 22:45:26 2023 From: artist at artixlinux.org (artist) Date: Tue, 7 Mar 2023 22:45:26 +0100 Subject: [artix-general] kcoreaddons-5.103.0-1-x86_64 (world) supposedly corrupt In-Reply-To: <13221659.uLZWGnKmhe@iserlohn-fortress.net> References: <13221659.uLZWGnKmhe@iserlohn-fortress.net> Message-ID: Until you get kcoreaddons-5.103.0-2.1 , the mirror you use is not yet up-to date. artist On a bended knee, or systemd, you will never live free On 3/7/23 22:08, jc_gargma wrote: >> supposedly the server was down, so the package probably failed to >> build properly. > It is not just kcoreaddons. I was trying to update one of my devices on > Monday and found that every single kde frameworks 5.103.0 package is > either corrupted in the manner you describe, or is rejected by pacman > due to an invalid package signature. > > Specifically, > > frameworkintegration > kdeclarative > kdecoreaddons > kded > kidletime > kitemviews > kjobwigdets > oxygen-icons > > are corrupted. > When these are set to --ignore, all others fail signature checking. > > It is doubly odd as I updated another device on Sunday and the same > packages were downloaded and installed without issue. I can only > conclude artix pushed a stealth rebuild of kde frameworks 5.103.0 on > Monday in which something went very wrong. > > Or the master package storage server has suffered massive data corruption > which is being circulated out to mirrors. > > > -jc > From somenxavier at posteo.net Wed Mar 8 12:10:09 2023 From: somenxavier at posteo.net (Xavier B.) Date: Wed, 8 Mar 2023 11:10:09 +0000 Subject: [artix-general] Segmentation fault in sylpheed Message-ID: <20230308121009.17abd725d3462b3f2aa51b21@posteo.net> Hi, I'm user of sylpheed (mail client). In almost every running I get this: $ export LANG=C && sylpheed --debug prohibit_duplicate_launch: checking socket: /tmp/sylpheed-1000 prohibit_duplicate_launch: creating socket: /tmp/sylpheed-1000 /usr/share/themes/Adwaita-dark/gtk-2.0/hacks.rc:28: error: invalid string constant "normal_entry", expected valid string constant Segmentation fault Anyone could help me to triage this error? Thanks in advance, Xavier From nous at artixlinux.org Wed Mar 8 22:59:41 2023 From: nous at artixlinux.org (Christos Nouskas) Date: Wed, 8 Mar 2023 23:59:41 +0200 Subject: [artix-general] Segmentation fault in sylpheed In-Reply-To: <20230308121009.17abd725d3462b3f2aa51b21@posteo.net> References: <20230308121009.17abd725d3462b3f2aa51b21@posteo.net> Message-ID: <20230308235941.1bdd8c05@hyperion.xyzzy.xyz> On Wed, 8 Mar 2023 11:10:09 +0000 "Xavier B." wrote: > /usr/share/themes/Adwaita-dark/gtk-2.0/hacks.rc:28: error: invalid string > constant "normal_entry", expected valid string constant Segmentation fault Perhaps if you switch to another theme instead of Adwaita-dark? -- https://systemd-free.artixlinux.org -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 488 bytes Desc: OpenPGP digital signature URL: From somenxavier at posteo.net Thu Mar 9 15:00:58 2023 From: somenxavier at posteo.net (Xavier B.) Date: Thu, 9 Mar 2023 14:00:58 +0000 Subject: [artix-general] Segmentation fault in sylpheed In-Reply-To: <20230308235941.1bdd8c05@hyperion.xyzzy.xyz> References: <20230308121009.17abd725d3462b3f2aa51b21@posteo.net> <20230308235941.1bdd8c05@hyperion.xyzzy.xyz> Message-ID: <20230309150058.8f1db0d91824ce7a0fc35683@posteo.net> It seems it works. But why? On Wed, 8 Mar 2023 23:59:41 +0200 Christos Nouskas ha escrit: > On Wed, 8 Mar 2023 11:10:09 +0000 > "Xavier B." wrote: > > /usr/share/themes/Adwaita-dark/gtk-2.0/hacks.rc:28: error: invalid string > > constant "normal_entry", expected valid string constant Segmentation fault > > Perhaps if you switch to another theme instead of Adwaita-dark? > > -- > https://systemd-free.artixlinux.org > From nous at artixlinux.org Sat Mar 11 11:37:42 2023 From: nous at artixlinux.org (Christos Nouskas) Date: Sat, 11 Mar 2023 12:37:42 +0200 Subject: [artix-general] Segmentation fault in sylpheed In-Reply-To: <20230309150058.8f1db0d91824ce7a0fc35683@posteo.net> References: <20230308121009.17abd725d3462b3f2aa51b21@posteo.net> <20230308235941.1bdd8c05@hyperion.xyzzy.xyz> <20230309150058.8f1db0d91824ce7a0fc35683@posteo.net> Message-ID: <20230311123742.4232a61b@hyperion.xyzzy.xyz> On Thu, 9 Mar 2023 14:00:58 +0000 "Xavier B." wrote: > It seems it works. But why? > > On Wed, 8 Mar 2023 23:59:41 +0200 > Christos Nouskas ha escrit: > > > On Wed, 8 Mar 2023 11:10:09 +0000 > > "Xavier B." wrote: > > > /usr/share/themes/Adwaita-dark/gtk-2.0/hacks.rc:28: error: invalid > > > string constant "normal_entry", expected valid string constant It's in the error message, perhaps you should report to/ask the theme maintainer, I'm not really qualified to answer. -- https://systemd-free.artixlinux.org -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 488 bytes Desc: OpenPGP digital signature URL: From rptnix at amerytel.net Sat Mar 18 02:25:50 2023 From: rptnix at amerytel.net (epektasis) Date: Fri, 17 Mar 2023 20:25:50 -0500 Subject: [artix-general] libreoffice-still 7.4.6.2-1.2 in /opt/ Message-ID: <20230318012550.GA10307@fiberart> Good evening. Libreoffice-still 7.4.6.2-1.2 was upgraded, with liborcus, tonight. Strangely, libreoffice no longer depends upon liborcus (so I removed liborcus). But now libreoffice is installed in /opt/, which is a change from all previous versions which were installed in /usr/lib/. Are these changes intentional? I didn't think Artix was installing programs into /opt/ (no other programs from Artix are there). e. From artist at artixlinux.org Sat Mar 18 23:34:56 2023 From: artist at artixlinux.org (artist) Date: Sat, 18 Mar 2023 23:34:56 +0100 Subject: [artix-general] libreoffice-still 7.4.6.2-1.2 in /opt/ In-Reply-To: <20230318012550.GA10307@fiberart> References: <20230318012550.GA10307@fiberart> Message-ID: <13090c92-2636-9f3d-2bf1-0f86952c2527@artixlinux.org> These are static pkgs, to circumvent a problem caused by a recent liborcus update. A new LO-still pkg has now been built to change the /opt location to /usr/lib, but needs some testing before being updated in the repo. Also the same needs to be built for LO-fresh. I'll update here and in the forum when done. artist On a bended knee, or systemd, you will never live free On 3/18/23 02:25, epektasis wrote: > Good evening. Libreoffice-still 7.4.6.2-1.2 was upgraded, with liborcus, > tonight. Strangely, libreoffice no longer depends upon liborcus (so I > removed liborcus). But now libreoffice is installed in /opt/, which is > a change from all previous versions which were installed in /usr/lib/. Are > these changes intentional? I didn't think Artix was installing programs > into /opt/ (no other programs from Artix are there). > e. > > From artist at artixlinux.org Sun Mar 19 11:21:14 2023 From: artist at artixlinux.org (artist) Date: Sun, 19 Mar 2023 11:21:14 +0100 Subject: [artix-general] libreoffice-still 7.4.6.2-1.2 in /opt/ In-Reply-To: <13090c92-2636-9f3d-2bf1-0f86952c2527@artixlinux.org> References: <20230318012550.GA10307@fiberart> <13090c92-2636-9f3d-2bf1-0f86952c2527@artixlinux.org> Message-ID: <7f54c91b-e1eb-cc27-f0c3-dc7c205c6c07@artixlinux.org> LO-fresh and -still have been updated in universe and omniverse respectively. I did some testing but am only an occasional user. artist On a bended knee, or systemd, you will never live free On 3/18/23 23:34, artist wrote: > These are static pkgs, to circumvent a problem caused by a recent > liborcus update. > A new LO-still pkg has now been built to change the /opt location to > /usr/lib, but needs some testing before being updated in the repo. > Also the same needs to be built for LO-fresh. > > I'll update here and in the forum when done. > > artist > > On a bended knee, or systemd, you will never live free > > On 3/18/23 02:25, epektasis wrote: >> Good evening.? Libreoffice-still 7.4.6.2-1.2 was upgraded, with >> liborcus, >> tonight.? Strangely, libreoffice no longer depends upon liborcus (so I >> removed liborcus).? But now libreoffice is installed in /opt/, which is >> a change from all previous versions which were installed in >> /usr/lib/.? Are >> these changes intentional?? I didn't think Artix was installing programs >> into /opt/ (no other programs from Artix are there). >> ????e. >> >> > From rptnix at amerytel.net Sun Mar 19 22:34:03 2023 From: rptnix at amerytel.net (epektasis) Date: Sun, 19 Mar 2023 16:34:03 -0500 Subject: [artix-general] libreoffice-still 7.4.6.2-1.2 in /opt/ In-Reply-To: <7f54c91b-e1eb-cc27-f0c3-dc7c205c6c07@artixlinux.org> References: <20230318012550.GA10307@fiberart> <13090c92-2636-9f3d-2bf1-0f86952c2527@artixlinux.org> <7f54c91b-e1eb-cc27-f0c3-dc7c205c6c07@artixlinux.org> Message-ID: <20230319213403.GA10325@fiberart> Thank you. The files are back to /usr/lib/libreoffice/ and the /usr/bin/libreoffice link is found. Thanks for all the work on these releases. e. On Sun, Mar 19, 2023 at 11:21:14AM +0100, artist wrote: > LO-fresh and -still have been updated in universe and omniverse > respectively. > I did some testing but am only an occasional user. > > artist > > On a bended knee, or systemd, you will never live free > > On 3/18/23 23:34, artist wrote: > > These are static pkgs, to circumvent a problem caused by a recent > > liborcus update. > > A new LO-still pkg has now been built to change the /opt location to > > /usr/lib, but needs some testing before being updated in the repo. > > Also the same needs to be built for LO-fresh. > > > > I'll update here and in the forum when done. > > > > artist > > > > On a bended knee, or systemd, you will never live free > > > > On 3/18/23 02:25, epektasis wrote: > > > Good evening.? Libreoffice-still 7.4.6.2-1.2 was upgraded, with > > > liborcus, > > > tonight.? Strangely, libreoffice no longer depends upon liborcus (so I > > > removed liborcus).? But now libreoffice is installed in /opt/, which is > > > a change from all previous versions which were installed in > > > /usr/lib/.? Are > > > these changes intentional?? I didn't think Artix was installing programs > > > into /opt/ (no other programs from Artix are there). > > > ????e. > > > > > > > > > > -- > artix-general mailing list > artix-general at artixlinux.org > https://lists.artixlinux.org/listinfo/artix-general From je-vv at e.email Mon Mar 20 09:20:56 2023 From: je-vv at e.email (Javier) Date: Mon, 20 Mar 2023 02:20:56 -0600 Subject: [artix-general] jami-qt seg faulting, :( Message-ID: > [New Thread 0x7fff367fc6c0 (LWP 25043)] > [New Thread 0x7fff35ffb6c0 (LWP 25044)] > [New Thread 0x7fff317fa6c0 (LWP 25045)] > Daemon is running > No migration required > [Thread 0x7fff317fa6c0 (LWP 25045) exited] > [New Thread 0x7fff30ff96c0 (LWP 25046)] > > Thread 34 "jami-qt" received signal SIGSEGV, Segmentation fault. > [Switching to Thread 0x7fff537fe6c0 (LWP 25016)] > 0x0000000000000000 in ?? () > (gdb) bt > #0 0x0000000000000000 in () > #1 0x00007fffeb8564e8 in () at /usr/lib/libjami.so.13 > #2 0x00007fffeb756ed3 in () at /usr/lib/libjami.so.13 > #3 0x00007fffeb0d72c3 in std::execute_native_thread_routine(void*) (__p=0x55555630f900) at /build/gcc/src/gcc/libstdc++-v3/src/c++11/thread.cc:82 > #4 0x00007fffeae9ebb5 in start_thread (arg=) at pthread_create.c:444 > #5 0x00007fffeaf20d90 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 Note that **/usr/lib/libjami.so.13** is owned by jami-daemon: > % pacman -Qo /usr/lib/libjami.so.13 > /usr/lib/libjami.so.13 is owned by jami-daemon 20220722-7 Weird enough, it's seg faulting whether using the artix jami-daemon (galaxy) or the one from arch (community). Anyone aware? Not sure if a rebuild is required, since it's too weird the back trace shows a failure on stdc++... Thanks ! -- Javier -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 228 bytes Desc: OpenPGP digital signature URL: From artist at artixlinux.org Mon Mar 20 09:52:56 2023 From: artist at artixlinux.org (artist) Date: Mon, 20 Mar 2023 09:52:56 +0100 Subject: [artix-general] jami-qt seg faulting, :( In-Reply-To: References: Message-ID: As it happens an update was built in staging - so consider it experimental for now. You can try it using eg. pacman -U https://mirror.clarkson.edu/artix-linux/repos/galaxy-goblins/os/x86_64/jami-daemon-20220722-8-x86_64.pkg.tar.zst artist On a bended knee, or systemd, you will never live free On 3/20/23 09:20, Javier wrote: >> [New Thread 0x7fff367fc6c0 (LWP 25043)] >> [New Thread 0x7fff35ffb6c0 (LWP 25044)] >> [New Thread 0x7fff317fa6c0 (LWP 25045)] >> Daemon is running >> No migration required >> [Thread 0x7fff317fa6c0 (LWP 25045) exited] >> [New Thread 0x7fff30ff96c0 (LWP 25046)] >> >> Thread 34 "jami-qt" received signal SIGSEGV, Segmentation fault. >> [Switching to Thread 0x7fff537fe6c0 (LWP 25016)] >> 0x0000000000000000 in ?? () >> (gdb) bt >> #0? 0x0000000000000000 in? () >> #1? 0x00007fffeb8564e8 in? () at /usr/lib/libjami.so.13 >> #2? 0x00007fffeb756ed3 in? () at /usr/lib/libjami.so.13 >> #3? 0x00007fffeb0d72c3 in std::execute_native_thread_routine(void*) >> (__p=0x55555630f900) at >> /build/gcc/src/gcc/libstdc++-v3/src/c++11/thread.cc:82 >> #4? 0x00007fffeae9ebb5 in start_thread (arg=) at >> pthread_create.c:444 >> #5? 0x00007fffeaf20d90 in clone3 () at >> ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 > > Note that **/usr/lib/libjami.so.13** is owned by jami-daemon: > >> % pacman -Qo /usr/lib/libjami.so.13 >> /usr/lib/libjami.so.13 is owned by jami-daemon 20220722-7 > > Weird enough, it's seg faulting whether using the artix jami-daemon > (galaxy) or the one from arch (community). > > Anyone aware?? Not sure if a rebuild is required, since it's too weird > the back trace shows a failure on stdc++... > > Thanks ! > > From ruben at mrbrklyn.com Mon Mar 20 20:39:26 2023 From: ruben at mrbrklyn.com (Ruben Safir) Date: Mon, 20 Mar 2023 15:39:26 -0400 Subject: [artix-general] libreoffice is crashing Message-ID: (soffice:5659): Gtk-WARNING **: 15:34:39.726: Theme parsing error: gtk.css:166:34: The :insensitive pseudo-class is deprecated. Use :disabled instead. (soffice:5659): Gtk-WARNING **: 15:34:39.726: Theme parsing error: gtk.css:187:34: The :inconsistent pseudo-class is deprecated. Use :indeterminate instead. Unspecified Application Error http://www.mrbrklyn.com/docs/calccrash.png etc -- So many immigrant groups have swept through our town that Brooklyn, like Atlantis, reaches mythological proportions in the mind of the world - RI Safir 1998 http://www.mrbrklyn.com DRM is THEFT - We are the STAKEHOLDERS - RI Safir 2002 http://www.nylxs.com - Leadership Development in Free Software http://www.brooklyn-living.com Being so tracked is for FARM ANIMALS and extermination camps, but incompatible with living as a free human being. -RI Safir 2013 From je-vv at e.email Mon Mar 20 21:31:34 2023 From: je-vv at e.email (Javier) Date: Mon, 20 Mar 2023 14:31:34 -0600 Subject: [artix-general] jami-qt seg faulting, :( In-Reply-To: References: Message-ID: <8dca214d-63ab-ff71-b3fb-65a53bdb9793@e.email> On 3/20/23 02:52, artist wrote: > As it happens an update was built in staging - so consider it experimental for now. > > You can try it using eg. > > pacman -U https://mirror.clarkson.edu/artix-linux/repos/galaxy-goblins/os/x86_64/jami-daemon-20220722-8-x86_64.pkg.tar.zst > > artist Needed the following: > pacman -R git-delta > pacman -U https://mirror.clarkson.edu/artix-linux/repos/goblins/os/x86_64/libgit2-1%3A1.6.2-1-x86_64.pkg.tar.zst > pacman -U https://geo.mirror.pkgbuild.com/community-staging/os/x86_64/git-delta-0.15.1-2-x86_64.pkg.tar.zst > pacman -U https://mirror.clarkson.edu/artix-linux/repos/galaxy-goblins/os/x86_64/jami-daemon-20220722-8-x86_64.pkg.tar.zst Although jami-daemon doesn't indicate it depends on libgit2, it actually does. And the staging version depends on libgit2.so.1.6, so the staging version of gitlib2 was also required. And git-delta (optional for aurutils 11-1 and 12.1-1, and not available on artix), also depends on libgit2, so it needed to be upgraded as well, but from community staging... After that, jami-qt doesn't seg fault anymore, :) Thanks a lot @artist ! -- Javier -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 228 bytes Desc: OpenPGP digital signature URL: From je-vv at e.email Mon Mar 20 21:43:09 2023 From: je-vv at e.email (Javier) Date: Mon, 20 Mar 2023 14:43:09 -0600 Subject: [artix-general] libreoffice is crashing In-Reply-To: References: Message-ID: <2431f151-1453-7b0a-f497-e7f4eb57a329@e.email> On 3/20/23 13:39, Ruben Safir wrote: > (soffice:5659): Gtk-WARNING **: 15:34:39.726: Theme parsing error: > gtk.css:166:34: The :insensitive pseudo-class is deprecated. Use > :disabled instead. > > (soffice:5659): Gtk-WARNING **: 15:34:39.726: Theme parsing error: > gtk.css:187:34: The :inconsistent pseudo-class is deprecated. Use > :indeterminate instead. > Unspecified Application Error > > http://www.mrbrklyn.com/docs/calccrash.png > > etc Would it be a gtk theme issue? Have you tried another gtk theme? BTW, I'm using Materia-dark, from community/materia-gtk-theme, and it's working fine. Greetings ! -- Javier -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 228 bytes Desc: OpenPGP digital signature URL: From jmjl at su.tilde.green Sun Mar 26 06:59:14 2023 From: jmjl at su.tilde.green (jmjl) Date: Sun, 26 Mar 2023 06:59:14 +0200 Subject: [artix-general] [Forum] Cloudflare configuration Message-ID: Hello dear artix server administrators, I have a few recommendations to give out: The forum seems to have a Ban IP feature, but as nginx or apache isn't configured properly, the forum just bans Cloudflare. I don't know how to do this in apache, but in nginx I know how. (The following text maybe will help if apache is used as I don't know how to configure it in apache) The solution that I think you guys want is to make nginx or apache2 take the header `CF-Connecting-IP` and make that be the IP the forum receives by setting it as the real IP. Nginx doesn't let us set a IP as the real IP but it does let us set a header which is exactly what we need, to get that done we'd do something like the following in nginx: ``` # IPv4 set_real_ip_from 103.21.244.0/22; set_real_ip_from 103.22.200.0/22; set_real_ip_from 103.31.4.0/22; set_real_ip_from 104.16.0.0/12; set_real_ip_from 108.162.192.0/18; set_real_ip_from 131.0.72.0/22; set_real_ip_from 141.101.64.0/18; set_real_ip_from 162.158.0.0/15; set_real_ip_from 172.64.0.0/13; set_real_ip_from 173.245.48.0/20; set_real_ip_from 188.114.96.0/20; set_real_ip_from 190.93.240.0/20; set_real_ip_from 197.234.240.0/22; set_real_ip_from 198.41.128.0/17; # IPv6 set_real_ip_from 2400:cb00::/32; set_real_ip_from 2405:8100::/32; set_real_ip_from 2405:b500::/32; set_real_ip_from 2606:4700::/32; set_real_ip_from 2803:f800::/32; set_real_ip_from 2c0f:f248::/32; set_real_ip_from 2a06:98c0::/29; # Header real_ip_header CF-Connecting-IP; # (src: https://rdr-it.com/en/tips/nginx-get-the-visitors-real-ip-with-cloudflare/) # (archived src: # - http://web.archive.org/web/20230326045529/https://rdr-it.com/en/tips/nginx-get-the-visitors-real-ip-with-cloudflare/ # ) ``` That snippet of code should be added inside the server block of each site that uses Cloudflare proxying. From m1sha at linux.ucla.edu Mon Mar 6 17:25:18 2023 From: m1sha at linux.ucla.edu (Misha Kruezhev) Date: Mon, 06 Mar 2023 16:25:18 -0000 Subject: [artix-general] kcoreaddons-5.103.0-1-x86_64 (world) supposedly corrupt Message-ID: # pacman -Sy polkit-kde-agent using 10 different mirrors I am getting "error: failed retrieving file 'kcoreaddons-5.103.0-1-x86_64.pkg.tar.zst' from : Maximum file size exceeded" supposedly the server was down, so the package probably failed to build properly. From nous at artixlinux.org Mon Mar 27 22:27:21 2023 From: nous at artixlinux.org (Christos Nouskas) Date: Mon, 27 Mar 2023 23:27:21 +0300 Subject: [artix-general] [Forum] Cloudflare configuration In-Reply-To: References: Message-ID: <20230327232721.3373c6e5@hyperion.xyzzy.xyz> On Sun, 26 Mar 2023 06:59:14 +0200 "jmjl" wrote: > Hello dear artix server administrators, I have a few recommendations to > give out: > The forum seems to have a Ban IP feature, but as nginx or apache isn't > configured properly, the forum just bans Cloudflare. >...< Thanks, implemented. -- https://systemd-free.artixlinux.org -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 488 bytes Desc: OpenPGP digital signature URL: From ruben at mrbrklyn.com Tue Mar 28 17:38:16 2023 From: ruben at mrbrklyn.com (Ruben Safir) Date: Tue, 28 Mar 2023 11:38:16 -0400 Subject: [artix-general] [Forum] Cloudflare configuration In-Reply-To: References: Message-ID: <20230328153816.GA20002@www2.mrbrklyn.com> why? On Sun, Mar 26, 2023 at 06:59:14AM +0200, jmjl wrote: > Hello dear artix server administrators, I have a few recommendations to > give out: > The forum seems to have a Ban IP feature, but as nginx or apache isn't > configured properly, the forum just bans Cloudflare. > I don't know how to do this in apache, but in nginx I know how. (The > following text maybe will help if apache is used as I don't know how to > configure it in apache) > > The solution that I think you guys want is to make nginx or apache2 > take the header `CF-Connecting-IP` and make that be the IP the forum > receives by setting it as the real IP. Nginx doesn't let us set a IP as > the real IP but it does let us set a header which is exactly what we > need, to get that done we'd do something like the following in nginx: > > ``` > # IPv4 > set_real_ip_from 103.21.244.0/22; > set_real_ip_from 103.22.200.0/22; > set_real_ip_from 103.31.4.0/22; > set_real_ip_from 104.16.0.0/12; > set_real_ip_from 108.162.192.0/18; > set_real_ip_from 131.0.72.0/22; > set_real_ip_from 141.101.64.0/18; > set_real_ip_from 162.158.0.0/15; > set_real_ip_from 172.64.0.0/13; > set_real_ip_from 173.245.48.0/20; > set_real_ip_from 188.114.96.0/20; > set_real_ip_from 190.93.240.0/20; > set_real_ip_from 197.234.240.0/22; > set_real_ip_from 198.41.128.0/17; > # IPv6 > set_real_ip_from 2400:cb00::/32; > set_real_ip_from 2405:8100::/32; > set_real_ip_from 2405:b500::/32; > set_real_ip_from 2606:4700::/32; > set_real_ip_from 2803:f800::/32; > set_real_ip_from 2c0f:f248::/32; > set_real_ip_from 2a06:98c0::/29; > # Header > real_ip_header CF-Connecting-IP; > # (src: https://rdr-it.com/en/tips/nginx-get-the-visitors-real-ip-with-cloudflare/) > # (archived src: > # - http://web.archive.org/web/20230326045529/https://rdr-it.com/en/tips/nginx-get-the-visitors-real-ip-with-cloudflare/ > # ) > ``` > > That snippet of code should be added inside the server block of each > site that uses Cloudflare proxying. > -- > artix-general mailing list > artix-general at artixlinux.org > https://lists.artixlinux.org/listinfo/artix-general -- So many immigrant groups have swept through our town that Brooklyn, like Atlantis, reaches mythological proportions in the mind of the world - RI Safir 1998 http://www.mrbrklyn.com DRM is THEFT - We are the STAKEHOLDERS - RI Safir 2002 http://www.nylxs.com - Leadership Development in Free Software http://www2.mrbrklyn.com/resources - Unpublished Archive http://www.coinhangout.com - coins! http://www.brooklyn-living.com Being so tracked is for FARM ANIMALS and extermination camps, but incompatible with living as a free human being. -RI Safir 2013 From jmjl at su.tilde.green Tue Mar 28 19:08:16 2023 From: jmjl at su.tilde.green (jmjl) Date: Tue, 28 Mar 2023 19:08:16 +0200 Subject: [artix-general] [Forum] Cloudflare configuration In-Reply-To: <20230328153816.GA20002@www2.mrbrklyn.com> References: <20230328153816.GA20002@www2.mrbrklyn.com> Message-ID: Because else the forum thinks Cloudflare is a user, and when forum admins try to ban by IP, they ban Cloudflare's IP. On Tue Mar 28, 2023 at 5:38 PM CEST, Ruben Safir wrote: > why? > > > On Sun, Mar 26, 2023 at 06:59:14AM +0200, jmjl wrote: > > Hello dear artix server administrators, I have a few recommendations to > > give out: > > The forum seems to have a Ban IP feature, but as nginx or apache isn't > > configured properly, the forum just bans Cloudflare. > > I don't know how to do this in apache, but in nginx I know how. (The > > following text maybe will help if apache is used as I don't know how to > > configure it in apache) > > > > The solution that I think you guys want is to make nginx or apache2 > > take the header `CF-Connecting-IP` and make that be the IP the forum > > receives by setting it as the real IP. Nginx doesn't let us set a IP as > > the real IP but it does let us set a header which is exactly what we > > need, to get that done we'd do something like the following in nginx: > > > > ``` > > # IPv4 > > set_real_ip_from 103.21.244.0/22; > > set_real_ip_from 103.22.200.0/22; > > set_real_ip_from 103.31.4.0/22; > > set_real_ip_from 104.16.0.0/12; > > set_real_ip_from 108.162.192.0/18; > > set_real_ip_from 131.0.72.0/22; > > set_real_ip_from 141.101.64.0/18; > > set_real_ip_from 162.158.0.0/15; > > set_real_ip_from 172.64.0.0/13; > > set_real_ip_from 173.245.48.0/20; > > set_real_ip_from 188.114.96.0/20; > > set_real_ip_from 190.93.240.0/20; > > set_real_ip_from 197.234.240.0/22; > > set_real_ip_from 198.41.128.0/17; > > # IPv6 > > set_real_ip_from 2400:cb00::/32; > > set_real_ip_from 2405:8100::/32; > > set_real_ip_from 2405:b500::/32; > > set_real_ip_from 2606:4700::/32; > > set_real_ip_from 2803:f800::/32; > > set_real_ip_from 2c0f:f248::/32; > > set_real_ip_from 2a06:98c0::/29; > > # Header > > real_ip_header CF-Connecting-IP; > > # (src: https://rdr-it.com/en/tips/nginx-get-the-visitors-real-ip-with-cloudflare/) > > # (archived src: > > # - http://web.archive.org/web/20230326045529/https://rdr-it.com/en/tips/nginx-get-the-visitors-real-ip-with-cloudflare/ > > # ) > > ``` > > > > That snippet of code should be added inside the server block of each > > site that uses Cloudflare proxying. > > -- > > artix-general mailing list > > artix-general at artixlinux.org > > https://lists.artixlinux.org/listinfo/artix-general > > -- > So many immigrant groups have swept through our town > that Brooklyn, like Atlantis, reaches mythological > proportions in the mind of the world - RI Safir 1998 > http://www.mrbrklyn.com > > DRM is THEFT - We are the STAKEHOLDERS - RI Safir 2002 > http://www.nylxs.com - Leadership Development in Free Software > http://www2.mrbrklyn.com/resources - Unpublished Archive > http://www.coinhangout.com - coins! > http://www.brooklyn-living.com > > Being so tracked is for FARM ANIMALS and extermination camps, > but incompatible with living as a free human being. -RI Safir 2013 From somenxavier at posteo.net Thu Mar 30 20:31:30 2023 From: somenxavier at posteo.net (Xavier B.) Date: Thu, 30 Mar 2023 18:31:30 +0000 Subject: [artix-general] tikz error on context Message-ID: <20230330203130.1f3ad84c6a75b191cd73d8d5@posteo.net> When I upgrade texlive to the latest version, I get this error when I use tikz module (a minimal example at the end): return { ["filename"]="/usr/share/texmf-dist/tex/generic/pgf/basiclayer/pgfcorepoints.code.tex", ["lastcontext"]="\n \n \\inaccessible \n \n \"\n\\pgfmath at catcodes ->\\catcode `\\==12 \\catcode `\\,=12 \\catcode `\\|=12 \\catcode `\\&=12 \\let \"\n \\pgfmath at char@quote \n\\pgfmathparse ->\\begingroup \\pgfmath at catcodes \n \\pgfmath at quickparsefalse \\ifpgfmathfloat \\let \\pgfmath at parse@next =\\pgfmathfloatparsenumber \\else \\let \\pgfmath at parse@next =\\pgfmathparse@ \\fi \\pgfmath at parse@next \n \\pgfmathparse \n {1cm}\\ifpgfmathmathunitsdeclared \\pgf at x \\pgfmathresult mu\\relax \\else \\pgf at x \\pgfmathresult pt\\relax \\fi \n\\pgfmath at next #1#2->#2\n \n...\nl.926 \\pgfsetxvec{\\pgfpoint{1cm}{0cm}}\n ", ["lastluaerror"]="?", ["lasttexerror"]="! Missing control sequence inserted", ["linenumber"]=926, ["offset"]=10, } Sample: \usemodule[tikz] \starttext {\bf a} \tikz (0,0) -- (1,0); \stoptext ConTeXt version ConTeXt ver: 2023.03.10 12:15 MKIV Thanks in advance, Xavier