From somenxavier at posteo.net Sat Aug 1 11:41:30 2020 From: somenxavier at posteo.net (Xavier B.) Date: Sat, 1 Aug 2020 13:41:30 +0200 Subject: [Assist] Updating dbus in ARM Message-ID: <20200801134130.34c624a5c1211b41e77f84e1@posteo.net> Hi, If I want to upgrade dbus I get an error: # pacman -S dbus :: dbus is in IgnorePkg/IgnoreGroup. Install anyway? [Y/n] resolving dependencies... looking for conflicting packages... Package (1) Old Version New Version Net Change nonsystemd/dbus 1.12.16-2.nonsystemd2 1.12.16-5.nonsystemd1 0.01 MiB Total Installed Size: 0.74 MiB Net Upgrade Size: 0.01 MiB :: Proceed with installation? [Y/n] (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% error: failed to commit transaction (conflicting files) dbus: /etc/runlevels/default/dbus exists in filesystem Errors occurred, no packages were upgraded. It seems this error has a long life. Could anyone solve it? I want to install mpd and I can't (:: unable to satisfy dependency 'libdbus-1.so=3-32' required by avahi) Thanks, Xavier From somenxavier at posteo.net Sat Aug 1 16:34:58 2020 From: somenxavier at posteo.net (Xavier B.) Date: Sat, 1 Aug 2020 18:34:58 +0200 Subject: [Assist] Wifi card not recognized Message-ID: <20200801183458.268e7c0a5b2d6c3ef3f000de@posteo.net> After installing parabola in 686 machine, the network card (wifi) is not recognized. During installation, parabola recognizes it. How can I triage and solve this problem. Thanks in advance, Xavier From somenxavier at posteo.net Sat Aug 1 19:21:40 2020 From: somenxavier at posteo.net (Xavier B.) Date: Sat, 1 Aug 2020 21:21:40 +0200 Subject: [Assist] Wifi card not recognized In-Reply-To: References: <20200801183458.268e7c0a5b2d6c3ef3f000de@posteo.net> Message-ID: <20200801212140.9ba4f74a90c75abb971b5c4d@posteo.net> On Sat, 1 Aug 2020 13:28:27 -0400 Megver83 ha escrit: > Is it an ath9k card? in that case, installing the latest linux-libre > should solve that problem. When did you last tried it? I tried today (2020-08-01) and I knew parabola has some issues with some drivers [https://www.parabola.nu/news/ath9k-wifi-devices-may-not-work-with-linux-libre-576/]. In the installation, parabola (openrc version) installed linux-libre too. I tried and I got the same result: no wifi card detected. Xavier > > El 01-08-20 a las 12:34, Xavier B. escribi?: > > After installing parabola in 686 machine, the network card (wifi) is not recognized. During installation, parabola recognizes it. > > How can I triage and solve this problem. > > > > Thanks in advance, > > Xavier > > _______________________________________________ > > Assist mailing list > > Assist at lists.parabola.nu > > https://lists.parabola.nu/mailman/listinfo/assist > > > From somenxavier at posteo.net Sat Aug 1 19:22:34 2020 From: somenxavier at posteo.net (Xavier B.) Date: Sat, 1 Aug 2020 21:22:34 +0200 Subject: [Assist] Wifi card not recognized In-Reply-To: References: <20200801183458.268e7c0a5b2d6c3ef3f000de@posteo.net> Message-ID: <20200801212234.79236ab4d8b36e030d50ae67@posteo.net> I tries linux-libre-lts and linux-libre On Sat, 1 Aug 2020 13:28:27 -0400 Megver83 ha escrit: > Is it an ath9k card? in that case, installing the latest linux-libre > should solve that problem. When did you last tried it? > > El 01-08-20 a las 12:34, Xavier B. escribi?: > > After installing parabola in 686 machine, the network card (wifi) is not recognized. During installation, parabola recognizes it. > > How can I triage and solve this problem. > > > > Thanks in advance, > > Xavier > > _______________________________________________ > > Assist mailing list > > Assist at lists.parabola.nu > > https://lists.parabola.nu/mailman/listinfo/assist > > > From GNUtoo at cyberdimension.org Sat Aug 1 20:29:44 2020 From: GNUtoo at cyberdimension.org (Denis 'GNUtoo' Carikli) Date: Sat, 1 Aug 2020 22:29:44 +0200 Subject: [Assist] Wifi card not recognized In-Reply-To: <20200801183458.268e7c0a5b2d6c3ef3f000de@posteo.net> References: <20200801183458.268e7c0a5b2d6c3ef3f000de@posteo.net> Message-ID: <20200801222944.0f725439@primarylaptop.localdomain> On Sat, 1 Aug 2020 18:34:58 +0200 "Xavier B." wrote: > After installing parabola in 686 machine, the network card (wifi) is > not recognized. During installation, parabola recognizes it. How can > I triage and solve this problem. You need to look at which driver is used. Many drivers simply don't work because they require nonfree firmware which have not yet been replaced by free software. If the driver is one that is known to work with free software, then we need to investigate more to understand what is going wrong. There is a simple way to check which driver is used, if you already know the WiFi interface name. This work with most drivers as the ones requiring a firmwares still creates an interface without the firmware. The "ls /sys/class/net/" command can show the list of interfaces. For instance: > # ls /sys/class/net/ > eth0 lo usb0 wlan1 wlp1s0 Then you can look at which driver is used with a single command. For instance if your interface is "wlan1" you can use the "readlink /sys/class/net/wlan1/device/driver" command. So here I tried that as root on an ARM computer and it gave me that: > # readlink /sys/class/net/wlan1/device/driver > ../../../../../../../../../../bus/usb/drivers/r8188eu So the driver is r8188eu which is not supported. As that driver isn't supported, I added another WiFi card in that device. Here's the same command for the other WiFi card: > # readlink /sys/class/net/wlp1s0/device/driver > ../../../../../../../bus/pci/drivers/ath9k So here that driver is supported. Denis. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From somenxavier at posteo.net Sat Aug 1 20:41:52 2020 From: somenxavier at posteo.net (Xavier B.) Date: Sat, 1 Aug 2020 22:41:52 +0200 Subject: [Assist] Updating dbus in ARM In-Reply-To: <86fd83b1-bb36-dc83-8f2b-fa411b351e94@hyperbola.info> References: <20200801134130.34c624a5c1211b41e77f84e1@posteo.net> <86fd83b1-bb36-dc83-8f2b-fa411b351e94@hyperbola.info> Message-ID: <20200801224152.e94dba04d7b9b689c8c57bb9@posteo.net> Thanks but I obtained same result On Sat, 1 Aug 2020 13:27:19 -0400 Megver83 ha escrit: > remove dbus from the default runlevel (rc-update del dbus default) and > install the package > > El 01-08-20 a las 07:41, Xavier B. escribi?: > > Hi, > > > > If I want to upgrade dbus I get an error: > > > > # pacman -S dbus > > :: dbus is in IgnorePkg/IgnoreGroup. Install anyway? [Y/n] > > resolving dependencies... > > looking for conflicting packages... > > > > Package (1) Old Version New Version Net Change > > > > nonsystemd/dbus 1.12.16-2.nonsystemd2 1.12.16-5.nonsystemd1 0.01 MiB > > > > Total Installed Size: 0.74 MiB > > Net Upgrade Size: 0.01 MiB > > > > :: Proceed with installation? [Y/n] > > (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% > > error: failed to commit transaction (conflicting files) > > dbus: /etc/runlevels/default/dbus exists in filesystem > > Errors occurred, no packages were upgraded. > > > > > > > > It seems this error has a long life. Could anyone solve it? I want to install mpd and I can't (:: unable to satisfy dependency 'libdbus-1.so=3-32' required by avahi) > > > > Thanks, > > Xavier > > _______________________________________________ > > Assist mailing list > > Assist at lists.parabola.nu > > https://lists.parabola.nu/mailman/listinfo/assist > > > From bill-auger at peers.community Sat Aug 1 21:26:16 2020 From: bill-auger at peers.community (bill-auger) Date: Sat, 1 Aug 2020 17:26:16 -0400 Subject: [Assist] Updating dbus in ARM In-Reply-To: <20200801134130.34c624a5c1211b41e77f84e1@posteo.net> References: <20200801134130.34c624a5c1211b41e77f84e1@posteo.net> Message-ID: <20200801172616.1cbbe7e5@parabola> On Sat, 1 Aug 2020 13:41:30 +0200 Xavier wrote: > :: dbus is in IgnorePkg/IgnoreGroup. Install anyway? [Y/n] why is that? one other thing i notice about this BR, is that dbus is a dependency of elogind, which is essentially a mandatory 'base' package - it looks to me like that system is in a non-standard (unsupported) configuration From bill-auger at peers.community Sat Aug 1 21:32:43 2020 From: bill-auger at peers.community (bill-auger) Date: Sat, 1 Aug 2020 17:32:43 -0400 Subject: [Assist] Wifi card not recognized In-Reply-To: <20200801222944.0f725439@primarylaptop.localdomain> References: <20200801183458.268e7c0a5b2d6c3ef3f000de@posteo.net> <20200801222944.0f725439@primarylaptop.localdomain> Message-ID: <20200801173243.382e8cd8@parabola> denis, the OP states that the wifi works with the LiveISO - if that is true, then it can not be a non-free module problem the problem mentioned in that news bulletin, affected only one parabola kernel - that kernel was pulled immediately after the problem was discovered; so its not that either the one thing i know about networking with the parabola openrc system, is that you need network manager and dbus services started in the default runlevel - the previous email from Xavier indicates a problem with dbus; so that should be fixed first From bill-auger at peers.community Sat Aug 1 21:42:23 2020 From: bill-auger at peers.community (bill-auger) Date: Sat, 1 Aug 2020 17:42:23 -0400 Subject: [Assist] Wifi card not recognized In-Reply-To: <20200801222944.0f725439@primarylaptop.localdomain> References: <20200801183458.268e7c0a5b2d6c3ef3f000de@posteo.net> <20200801222944.0f725439@primarylaptop.localdomain> Message-ID: <20200801174223.7004cb0e@parabola> megver - i noticed all of your replies in this thread were quoted - none came directly from you - you are maybe not replying to the list? could you look at these forum questions - one is about openrc and the udev scripts - seems pretty bizarre - maybe you have seen something similar; or else i dont know where to begin trouble-shooting it https://labs.parabola.nu/boards/5/topics/529 the other two, i have no idea - they are in spanish? - i could only deduce that they are about a banana pi - you have a banana pi yea? - can it play audio? - i asked for details; but the OP has not responded; so maybe that one is a dead-end anyways https://labs.parabola.nu/boards/18/topics/524 https://labs.parabola.nu/boards/18/topics/525 From somenxavier at posteo.net Sun Aug 2 13:34:38 2020 From: somenxavier at posteo.net (Xavier B.) Date: Sun, 2 Aug 2020 15:34:38 +0200 Subject: [Assist] Wifi card not recognized In-Reply-To: <20200801222944.0f725439@primarylaptop.localdomain> References: <20200801183458.268e7c0a5b2d6c3ef3f000de@posteo.net> <20200801222944.0f725439@primarylaptop.localdomain> Message-ID: <20200802153438.aa410a01b34194709badec28@posteo.net> Thanks, Denis, for pointing it out, but as bill-auger said, LiveISO detected the wifi card. The problem is that after installation, parabola does not detect it @bill-auger: dbus issue is with *another* machine (ARM). The bug is this https://labs.parabola.nu/issues/2618 I have in ignore packages in pacman.conf because it is not solved and else I cannot update anything Thanks to all of you, Xavier > denis, the OP states that the wifi works with the LiveISO - if that is > true, then it can not be a non-free module problem > > the problem mentioned in that news bulletin, affected only one parabola > kernel - that kernel was pulled immediately after the problem was > discovered; so its not that either > > the one thing i know about networking with the parabola openrc system, > is that you need network manager and dbus services started in the > default runlevel - the previous email from Xavier indicates a problem > with dbus; so that should be fixed first From somenxavier at posteo.net Sun Aug 2 20:42:14 2020 From: somenxavier at posteo.net (Xavier B.) Date: Sun, 2 Aug 2020 22:42:14 +0200 Subject: [Assist] mpd id unable to install in ARM Openrc Message-ID: <20200802224214.c11854b706a850347c66111f@posteo.net> Related to my previous post [https://lists.parabola.nu/pipermail/assist/2020-August/001537.html], I can't install mpd because it depends on systemd. I have ARM machine with openrc installed: # pacman -S mpd resolving dependencies... :: There are 2 providers available for libgl: :: Repository extra 1) libglvnd :: Repository world 2) libglvnd Enter a number (default=1): :: There are 2 providers available for libjpeg: :: Repository extra 1) libjpeg-turbo :: Repository world 2) libjpeg-turbo Enter a number (default=1): looking for conflicting packages... :: systemd-libsystemd and elogind are in conflict. Remove elogind? [y/N] y :: systemd-libsystemd and libelogind are in conflict. Remove libelogind? [y/N] y error: failed to prepare transaction (could not satisfy dependencies) :: unable to satisfy dependency 'systemd-libs' required by mpd :: unable to satisfy dependency 'libelogind' required by dbus :: unable to satisfy dependency 'libelogind.so=0-32' required by dbus :: unable to satisfy dependency 'systemd' required by libpulse :: removing libelogind breaks dependency 'systemd-libs' required by device-mapper :: removing libelogind breaks dependency 'systemd-libs' required by dhcpcd :: removing libelogind breaks dependency 'libelogind' required by libnm :: removing libelogind breaks dependency 'systemd-libs' required by libusb :: removing libelogind breaks dependency 'systemd-libs' required by lvm2 :: removing elogind breaks dependency 'elogind' required by networkmanager :: removing elogind breaks dependency 'elogind' required by polkit :: removing libelogind breaks dependency 'systemd-libs' required by procps-ng :: removing libelogind breaks dependency 'systemd-libs' required by rpcbind :: removing libelogind breaks dependency 'systemd-libs' required by syslog-ng Thanks in advance, Xavier From megver83 at hyperbola.info Sun Aug 2 20:55:34 2020 From: megver83 at hyperbola.info (Megver83) Date: Sun, 2 Aug 2020 16:55:34 -0400 Subject: [Assist] mpd id unable to install in ARM Openrc In-Reply-To: <20200802224214.c11854b706a850347c66111f@posteo.net> References: <20200802224214.c11854b706a850347c66111f@posteo.net> Message-ID: Just checked its dependency tree with pactree -s and noticed that systemd-libsystemd is pulled by fluidsynth. This doesn't happen in x86_64 however, I think there's a problem with the libsystemd.so dependency. I'll see if upgrading systemd solves the issue, it looks like it provides an older libsystemd.so version which satisfies fluidsyth as systemd is more outdated in ARM. Meanwhile, as a workaround, running pacman -S --assume-installed libsystemd.so=0-32 mpd should work. El 02-08-20 a las 16:42, Xavier B. escribi?: > Related to my previous post [https://lists.parabola.nu/pipermail/assist/2020-August/001537.html], I can't install mpd because it depends on systemd. I have ARM machine with openrc installed: > > # pacman -S mpd > resolving dependencies... > :: There are 2 providers available for libgl: > :: Repository extra > 1) libglvnd > :: Repository world > 2) libglvnd > > Enter a number (default=1): > :: There are 2 providers available for libjpeg: > :: Repository extra > 1) libjpeg-turbo > :: Repository world > 2) libjpeg-turbo > > Enter a number (default=1): > looking for conflicting packages... > :: systemd-libsystemd and elogind are in conflict. Remove elogind? [y/N] y > :: systemd-libsystemd and libelogind are in conflict. Remove libelogind? [y/N] y > error: failed to prepare transaction (could not satisfy dependencies) > :: unable to satisfy dependency 'systemd-libs' required by mpd > :: unable to satisfy dependency 'libelogind' required by dbus > :: unable to satisfy dependency 'libelogind.so=0-32' required by dbus > :: unable to satisfy dependency 'systemd' required by libpulse > :: removing libelogind breaks dependency 'systemd-libs' required by device-mapper > :: removing libelogind breaks dependency 'systemd-libs' required by dhcpcd > :: removing libelogind breaks dependency 'libelogind' required by libnm > :: removing libelogind breaks dependency 'systemd-libs' required by libusb > :: removing libelogind breaks dependency 'systemd-libs' required by lvm2 > :: removing elogind breaks dependency 'elogind' required by networkmanager > :: removing elogind breaks dependency 'elogind' required by polkit > :: removing libelogind breaks dependency 'systemd-libs' required by procps-ng > :: removing libelogind breaks dependency 'systemd-libs' required by rpcbind > :: removing libelogind breaks dependency 'systemd-libs' required by syslog-ng > > > > Thanks in advance, > Xavier > _______________________________________________ > Assist mailing list > Assist at lists.parabola.nu > https://lists.parabola.nu/mailman/listinfo/assist > -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: OpenPGP digital signature URL: From mnovak10120 at gmail.com Sun Aug 16 13:42:50 2020 From: mnovak10120 at gmail.com (Michael Novak) Date: Sun, 16 Aug 2020 16:42:50 +0300 Subject: [Assist] Which graphics cards are supported by parabola? Message-ID: Is there a list of all the graphics cards that parabola (or any other fully free GNU / Linux distro) support? I heard that the most powerful cards are Nvidia Kepler architecture cards. Is that true? Because I've seen on the nouveau website that they support newer cards as well. Do these newer cards drivers are not fully free? -------------- next part -------------- An HTML attachment was scrubbed... URL: From luther at librem.one Fri Aug 21 19:06:27 2020 From: luther at librem.one (Luther Thompson) Date: Fri, 21 Aug 2020 15:06:27 -0400 Subject: [Assist] Can't update on a fresh install Message-ID: I've done a fresh install, and apparently the keys are bad. I can't do any updates. I remember finding a Parabola wiki page with a bunch of troubleshooting for bad keys, but none of the solutions there worked. I can't seem to find that page now. Since I can't set up email on the computer where I'm installing Parabola, I copy and paste any command output. Luther -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 313 bytes Desc: OpenPGP digital signature URL: From luther at librem.one Fri Aug 21 19:10:21 2020 From: luther at librem.one (Luther Thompson) Date: Fri, 21 Aug 2020 15:10:21 -0400 Subject: [Assist] Can't update on a fresh install In-Reply-To: References: Message-ID: On 8/21/20 3:06 PM, Luther Thompson wrote: > I've done a fresh install, and apparently the keys are bad. I can't do > any updates. I remember finding a Parabola wiki page with a bunch of > troubleshooting for bad keys, but none of the solutions there worked. I > can't seem to find that page now. > > Since I can't set up email on the computer where I'm installing > Parabola, I copy and paste any command output. ^can't -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 313 bytes Desc: OpenPGP digital signature URL: From bill-auger at peers.community Fri Aug 21 21:49:27 2020 From: bill-auger at peers.community (bill-auger) Date: Fri, 21 Aug 2020 17:49:27 -0400 Subject: [Assist] Can't update on a fresh install In-Reply-To: References: Message-ID: <20200821174927.37207f6a@parabola> this command will most likely solve your problem # pacman-key --keyserver hkp://pool.sks-keyservers.net --refresh-keys From luther at librem.one Fri Aug 21 22:10:23 2020 From: luther at librem.one (Luther Thompson) Date: Fri, 21 Aug 2020 18:10:23 -0400 Subject: [Assist] Can't update on a fresh install In-Reply-To: <20200821174927.37207f6a@parabola> References: <20200821174927.37207f6a@parabola> Message-ID: On 8/21/20 5:49 PM, bill-auger wrote: > this command will most likely solve your problem > > # pacman-key --keyserver hkp://pool.sks-keyservers.net --refresh-keys Did that just now. There are still 3 keys that "could not be looked up remotely". (Before, there were 4.) Here are the bad keys. I'm typing by hand, so please forgive any mistakes: 3B94A80E50A477C7 7258734B41C31549 686B063AC4BC0EC9 Luther -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 313 bytes Desc: OpenPGP digital signature URL: From bill-auger at peers.community Fri Aug 21 22:49:21 2020 From: bill-auger at peers.community (bill-auger) Date: Fri, 21 Aug 2020 18:49:21 -0400 Subject: [Assist] Can't update on a fresh install In-Reply-To: References: <20200821174927.37207f6a@parabola> Message-ID: <20200821184921.788f1f86@parabola> the key-servers have been troublesome lately - probably you just need to try again a few times to make it faster, you can update only the three remaining keys by putting the key-id after --refresh-keys, like the example below for future reference, there is a simple way to get text out of a LiveISO - (install 'gnu-netcat' if necessary) either put the text in 'a-file' then run this command: $ cat a-file | nc termbin.com 9999 or post the entire output of a command: $ some-command 2>&1 | nc termbin.com 9999 for example: $ sudo pacman-key --keyserver hkp://pool.sks-keyservers.net --refresh-keys 7258734B41C31549 2>&1 | nc termbin.com 9999 that will print a simple URL, which you can type into emails or chat From luther at librem.one Sat Aug 22 00:58:44 2020 From: luther at librem.one (Luther Thompson) Date: Fri, 21 Aug 2020 20:58:44 -0400 Subject: [Assist] Can't update on a fresh install In-Reply-To: <20200821184921.788f1f86@parabola> References: <20200821174927.37207f6a@parabola> <20200821184921.788f1f86@parabola> Message-ID: <64d0b80e-5e2c-5c41-c0f4-2c3c53e04e9c@librem.one> On 8/21/20 6:49 PM, bill-auger wrote: > the key-servers have been troublesome lately - > probably you just need to try again a few times > > to make it faster, you can update only the three > remaining keys by putting the key-id after > --refresh-keys, like the example below > > for future reference, there is a simple way to get text > out of a LiveISO - (install 'gnu-netcat' if necessary) > > either put the text in 'a-file' then run this command: > > $ cat a-file | nc termbin.com 9999 > > or post the entire output of a command: > > $ some-command 2>&1 | nc termbin.com 9999 > > for example: > > $ sudo pacman-key --keyserver hkp://pool.sks-keyservers.net --refresh-keys 7258734B41C31549 2>&1 | nc termbin.com 9999 > > that will print a simple URL, which you can type into emails or chat Thanks for the tip. When refreshing keys one at a time, as you suggested, I get this: ==> ERROR: The key identified by 3B94A80E50A477C7 could not be found locally. Same error for all 3 keys. It looks like the problem may be on my own system rather than the keyserver. Luther -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 313 bytes Desc: OpenPGP digital signature URL: From bill-auger at peers.community Sat Aug 22 01:48:47 2020 From: bill-auger at peers.community (bill-auger) Date: Fri, 21 Aug 2020 21:48:47 -0400 Subject: [Assist] Can't update on a fresh install In-Reply-To: <64d0b80e-5e2c-5c41-c0f4-2c3c53e04e9c@librem.one> References: <20200821174927.37207f6a@parabola> <20200821184921.788f1f86@parabola> <64d0b80e-5e2c-5c41-c0f4-2c3c53e04e9c@librem.one> Message-ID: <20200821214847.7a381866@parabola> without more detail, i can only suggest that you try the brute force keyring restore, described in section 2 on this wiki article: https://wiki.parabola.nu/Parabola_Keyring From luther at librem.one Sat Aug 22 02:20:08 2020 From: luther at librem.one (Luther Thompson) Date: Fri, 21 Aug 2020 22:20:08 -0400 Subject: [Assist] Can't update on a fresh install In-Reply-To: <20200821214847.7a381866@parabola> References: <20200821174927.37207f6a@parabola> <20200821184921.788f1f86@parabola> <64d0b80e-5e2c-5c41-c0f4-2c3c53e04e9c@librem.one> <20200821214847.7a381866@parabola> Message-ID: <85795f60-2ecf-3494-4aff-f4a1855b646d@librem.one> On 8/21/20 9:48 PM, bill-auger wrote: > without more detail, i can only suggest that you try the brute > force keyring restore, described in section 2 on this wiki > article: > > https://wiki.parabola.nu/Parabola_Keyring So I got to this command: sudo pacman -Syy archlinux-keyring archlinux32-keyring archlinuxarm-keyring parabola-keyring The output at https://termbin.com/nzaj only shows the first few lines. I got 'error: archlinux32-keyring: signature from "Erich Eckner ..." is marginal trust' It then says the package is corrupted due to an invalid PGP signature and does not upgrade any packages. Luther -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 313 bytes Desc: OpenPGP digital signature URL: From luther at librem.one Sat Aug 22 12:50:28 2020 From: luther at librem.one (Luther Thompson) Date: Sat, 22 Aug 2020 08:50:28 -0400 Subject: [Assist] Can't update on a fresh install In-Reply-To: <85795f60-2ecf-3494-4aff-f4a1855b646d@librem.one> References: <20200821174927.37207f6a@parabola> <20200821184921.788f1f86@parabola> <64d0b80e-5e2c-5c41-c0f4-2c3c53e04e9c@librem.one> <20200821214847.7a381866@parabola> <85795f60-2ecf-3494-4aff-f4a1855b646d@librem.one> Message-ID: <5efb1028-ea70-8a46-3c69-024a1455730e@librem.one> Update: I've also followed the instructions at https://wiki.parabola.nu/Parabola_Keyring, part 3, and I'm still getting the same errors. Luther -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 313 bytes Desc: OpenPGP digital signature URL: From bill-auger at peers.community Sat Aug 22 20:54:34 2020 From: bill-auger at peers.community (bill-auger) Date: Sat, 22 Aug 2020 16:54:34 -0400 Subject: [Assist] Can't update on a fresh install In-Reply-To: <85795f60-2ecf-3494-4aff-f4a1855b646d@librem.one> References: <20200821174927.37207f6a@parabola> <20200821184921.788f1f86@parabola> <64d0b80e-5e2c-5c41-c0f4-2c3c53e04e9c@librem.one> <20200821214847.7a381866@parabola> <85795f60-2ecf-3494-4aff-f4a1855b646d@librem.one> Message-ID: <20200822165434.1c28c503@parabola> if the error now is only with erich's key, then installing this package will resolve it # pacman -U https://www.parabola.nu/packages/core/i686/archlinux32-keyring-transition/download/ From luther at librem.one Sun Aug 23 23:39:40 2020 From: luther at librem.one (Luther Thompson) Date: Sun, 23 Aug 2020 19:39:40 -0400 Subject: [Assist] Can't update on a fresh install In-Reply-To: <20200822165434.1c28c503@parabola> References: <20200821174927.37207f6a@parabola> <20200821184921.788f1f86@parabola> <64d0b80e-5e2c-5c41-c0f4-2c3c53e04e9c@librem.one> <20200821214847.7a381866@parabola> <85795f60-2ecf-3494-4aff-f4a1855b646d@librem.one> <20200822165434.1c28c503@parabola> Message-ID: On 8/22/20 4:54 PM, bill-auger wrote: > if the error now is only with erich's key, then installing this > package will resolve it > > # pacman -U https://www.parabola.nu/packages/core/i686/archlinux32-keyring-transition/download/ I had to rerun some of the other commands after doing this, but I did eventually succeed at updating my system. Thank you for your help. Luther -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 313 bytes Desc: OpenPGP digital signature URL: