Arch Linux User Repository

Hi @waldbaer59, the reason is that libindi reached version 2.0.0 and stellarium is not compatible.

We must wait the next release. See https://github.com/Stellarium/stellarium/issues/3038

Pre-built binaries of this package and its dependencies can be found in the arch4edu repository.

Important note: Is recommended to receive the following key before to install:

$ gpg --recv-keys BF38D4D02A328DFF

Also is possible skip the verification, adding the flag for (e.g makepkg, yay) --skippgpcheck, --nopgpfetch, respectively.

Maybe add -GNinja to cmake options to accelerate the makefile generation process...

I successfully imported the key :

gpg -v --keyserver keys.openpgp.org  --recv-keys BF38D4D02A328DFF
gpg: data source: http://keys.openpgp.org:11371
gpg: pub  rsa4096/BF38D4D02A328DFF 2012-04-07  
gpg: key BF38D4D02A328DFF: no user ID
gpg: Total number processed: 1

However I still get error of PGP signature could not be verified. Is there some way to edit the pkgbuild to skip PGP verification?

Yesterday I tried to install Stellarium using the Pikaur packet manager, and had the key error we are talking about. Then I tried the manual procedure and the PGP key verification had success. Don't know why. In the past months I tried to reinstall the keys many times.

@carlosal1015 I deleted the key and tried again, but no luck.

Skipping verification all the time might be a pain. Is there no way to get the appropriate key?

Yes @MidnightStarSign, I had the same error one week ago, therefore I download again the new keys (I think he re-upload the keys to keyserver). If have the issue below, try to delete the keys and receive keys again.

When trying to upgrade, I get this error, but have installed the keys from various posts and the pinned one :(

Not sure where to go from here and use it quite a bit.

FAILED
==> ERROR: One or more PGP signatures could not be verified!

--

root@MidnightStarSign:/home/sarah# gpg -v --recv-keys BF38D4D02A328DFF
gpg: data source: https://162.213.33.9:443
gpg: armor header: Comment: Hostname:
gpg: armor header: Version: Hockeypuck 2.1.0-152-ga266fd3
gpg: pub  rsa4096/BF38D4D02A328DFF 2012-04-07  Alexander Wolf <alex.v.wolf@gmail.com>
gpg: key BF38D4D02A328DFF: "Alexander Wolf <alex.v.wolf@gmail.com>" not changed
gpg: Total number processed: 1
gpg:              unchanged: 1

I think that could be fine to report and have a more broad discussion in

• mailing list

• Frequent Answer Question

• Common Problems for the current version

• GitHub issue tracker.

I have sporadic desktop freezing (hard lock), only resetting the machine gets me back to have access to the PC

happens mostly on exit full screen and resizing the windows, sometimes after opening without doing nothing

on the same machine and kernel I have Ubuntu with Kde Plasma and Kde Neon and there is no similar problem

no log entry about this problem anywhere

any idea what I can do?

System: Host: hm-abang Kernel: 5.16.14-hmich-rt-4 arch: x86_64 bits: 64 Desktop: KDE Plasma v: 5.24.5 Distro: ArchBang Linux CPU: Info: 8-core model: AMD FX-8300 bits: 64 type: MT MCP cache: L2: 8 MiB Speed (MHz): avg: 1503 min/max: 1400/3300 cores: 1: 1798 2: 1465 3: 1467 4: 1676 5: 1406 6: 1406 7: 1405 8: 1406 Graphics: Device-1: NVIDIA GK208 [GeForce GT 710] driver: nvidia v: 390.147 Display: x11 server: X.Org v: 21.1.3 driver: X: loaded: nvidia gpu: nvidia resolution: 1920x1080~60Hz OpenGL: renderer: GeForce GT 710/PCIe/SSE2 v: 4.6.0 NVIDIA 390.147

@carlosal1015: I checked the signature in verbose mode:

gpg --verbose --verify stellarium-0.22.0.tar.gz.asc stellarium-0.22.0.tar.gz
gpg: Signature made Sun 27 Mar 2022 13:07:50 CEST
gpg: using RSA key F57F309D74C9A94E2B6AA5D09380E47C0374E169
gpg: using subkey 9380E47C0374E169 instead of primary key BF38D4D02A328DFF
gpg: using subkey 9380E47C0374E169 instead of primary key BF38D4D02A328DFF
gpg: using pgp trust model
gpg: Good signature from "Alexander Wolf alex.v.wolf@gmail.com" [unknown]
gpg: using subkey 9380E47C0374E169 instead of primary key BF38D4D02A328DFF
gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the owner.
Primary key fingerprint: 7915 1C2E 6351 E727 8DA1 A730 BF38 D4D0 2A32 8DFF
Subkey fingerprint: F57F 309D 74C9 A94E 2B6A A5D0 9380 E47C 0374 E169
gpg: binary signature, digest algorithm SHA512, key algorithm rsa1024


I noted that gpg is using subkey 9380E47C0374E169 instead of primary key
BF38D4D02A328DFF, but I have no idea of the reason.

Adding the key seem to be ok:
gpg -v --recv-keys BF38D4D02A328DFF
gpg: data source: https://162.213.33.8:443
gpg: armor header: Comment: Hostname:
gpg: armor header: Version: Hockeypuck ~unreleased
gpg: pub rsa4096/BF38D4D02A328DFF 2012-04-07 Alexander Wolf alex.v.wolf@gmail.com
gpg: using pgp trust model
gpg: key BF38D4D02A328DFF: public key "Alexander Wolf alex.v.wolf@gmail.com" imported
gpg: Total number processed: 1
gpg: imported: 1

Also the list of the keys shows no problem:
pub rsa4096 2012-04-07 [SCEA]
79151C2E6351E7278DA1A730BF38D4D02A328DFF
uid [ unknown] Alexander Wolf alex.v.wolf@gmail.com
sub rsa1024 2012-04-07 [SEA]