Unable to install locally built rpms
by Ralf Corsépius
Hi,
on f38, I am unable to install any locally built package (signed with a
local key, I have been using for many years):
# rpm -U xpetri-0.4.8-0.fc38.x86_64.rpm
error: xpetri-0.4.8-0.fc38.x86_64.rpm: Header V4 RSA/SHA256 Signature,
key ID a6b9312e: BAD
error: xpetri-0.4.8-0.fc38.x86_64.rpm cannot be installed
# rpm -qip xpetri-0.4.8-0.fc38.x86_64.rpm
error: xpetri-0.4.8-0.fc38.x86_64.rpm: Header V4 RSA/SHA256 Signature,
key ID a6b9312e: BAD
error: xpetri-0.4.8-0.fc38.x86_64.rpm: not an rpm package (or package
manifest)
# dnf install xpetri-0.4.8-0.fc38.x86_64.rpm
Last metadata expiration check: 1:30:47 ago on Tue 28 Feb 2023 06:25:45
AM CET.
Dependencies resolved.
...
0.4.8-0.fc38 @commandline
...
Installing dependencies:
...
Downloading Packages:
(1/6): XXX.rpm ...
Total
1.2 MB/s |
130 kB 00:00
...
Problem opening package XXX.rpm
...
The downloaded packages were saved in cache until the next successful
transaction.
You can remove cached packages by executing 'dnf clean packages'.
Error: GPG check FAILED
Worse, after trying forcefully to install packages using rpm -U --nogpg
this happens:
# rpm -qa
gpg-pubkey-d651ff2e-5dadbbc1
gpg-pubkey-8ff214b4-3afa5d46
gpg-pubkey-a6b9312e-5227e975
gpg-pubkey-94843c65-5dadbc64
error: rpmdbNextIterator: skipping h# 5
Header V4 DSA/SHA1 Signature, key ID 8ff214b4: BAD
Header SHA256 digest: OK
Header SHA1 digest: OK
error: rpmdbNextIterator: skipping h# 6
Header V3 RSA/SHA1 Signature, key ID d651ff2e: BAD
Header SHA256 digest: OK
Header SHA1 digest: OK
gpg-pubkey-5323552a-6112bcdc
...
=> nogpg is not ignored, as it is supposed to be.
What are people supposed to do?
Ralf
19 hours, 30 minutes
Fedora Linux 38 blocker status summary
by Ben Cotton
We've branched F38 from Rawhide, so it's time to start everyone's
favorite Friday email from Ben! The F38 Beta freeze begins on 21
February. The current target release date is the early target date
(2023-03-14).
Action summary
====================
Accepted blockers
-----------------
1–3. distribution — {Workstation,Everything,Server} boot x86_64 image
exceeds maximum size — ASSIGNED
ACTION: Relevant Teams to reduce image size or increase the limit
Proposed blockers
-----------------
1. anaconda — installer fails to boot in text mode or rescue mode with
systemd 253 — MODIFIED
ACTION: Maintainers to build an update that includes upstream PR
2. grub2 — ext4 filessystem support missing — NEW
ACTION: Maintainer to diagnose issue
NEEDINFO: ausil
3. kwin — kwin_wayland often crashed when used as the sddm Wayland
compositor and logging out of Plasma resulting in a black screen — NEW
ACTION: Maintainer to diagnose issue
4. mesa — KDE crashes on start with mesa-23.0.0~rc3-3.fc38 — ASSIGNED
ACTION: Maintainer to diagnose issue
Bug-by-bug detail
=============
Accepted blockers
-----------------
1–3. distribution — {Workstation,Everything,Server} boot x86_64 image
exceeds maximum size — ASSIGNED
https://bugzilla.redhat.com/show_bug.cgi?id=2149246
https://bugzilla.redhat.com/show_bug.cgi?id=2151495
https://bugzilla.redhat.com/show_bug.cgi?id=2151497
Image sizes exceed the specified limits. The choices are to either
shrink the image by removing packages or to riase the limits.
Proposed blockers
-----------------
1. anaconda — https://bugzilla.redhat.com/show_bug.cgi?id=2165433 — MODIFIED
installer fails to boot in text mode or rescue mode with systemd 253
anaconda is writing systemd units to an unexpected area. Upstream PR
4534 contains a candidate fix:
https://github.com/rhinstaller/anaconda/pull/4534
2. grub2 — https://bugzilla.redhat.com/show_bug.cgi?id=2166412 — NEW
ext4 filessystem support missing
Between grub2-2.06-76 and grub2-2.06-78, grub2 apparently lost the
ability to detect ext4 filesystems.
3. kwin — https://bugzilla.redhat.com/show_bug.cgi?id=2168034 — NEW
kwin_wayland often crashed when used as the sddm Wayland compositor
and logging out of Plasma resulting in a black screen
Logging out of Plasma sometimes triggers a kwin crash. This may be
limited to running in a virtual machine.
4. mesa — https://bugzilla.redhat.com/show_bug.cgi?id=2164667 — ASSIGNED
KDE crashes on start with mesa-23.0.0~rc3-3.fc38
A recent mesa update caused both GNOME and KDE to crash on start.
Update FEDORA-2023-40b973fa06 fixed GNOME, but KDE is still seeing
this issue. The root cause is still uncertain.
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
5 days, 14 hours
Xfce ~ Lost all menu icons in Rawhide and Beta Branch
by Ian Laurie
In Rawhide (fc39) and the beta branch (fc38), with all updates applied,
I'm seeing all menu icons are gone in Xfce... both the system menu and
right-click context menus.
Seems the Settings Tab in Settings->Appearance now has all options
turned off, including "Show images in menus". Updates did this.
Ticking this option brings sanity back. Was this really intentional or
is it a bug? I think this deviation from traditional defaults is going
to cause beginners a lot of grief.
The Xfce updates in the total update payload were as follows:
xfce4-about-4.18.2-1.fc38.x86_64
xfce4-notifyd-0.8.0-1.fc38.x86_64
xfce4-panel-4.18.2-1.fc38.x86_64
xfce4-power-manager-4.18.1-1.fc38.x86_64
xfce4-session-4.18.1-1.fc38.x86_64
xfce4-settings-4.18.2-1.fc38.x86_64
I'm guessing it was xfce4-settings that did it? If this was intentional
I think it was a really bad idea.
Ian
--
Ian Laurie
FAS: nixuser | IRC: nixuser
TZ: Australia/Sydney
2 weeks, 4 days
Joining Fedora QA
by Mark Rosenbaum
Hello,
I am looking to join Fedora QA and help mostly with triage/bug reproducibility. I am currently a contributor to a multitude of open source projects including the Chromium Project where I hold bug editing permissions(mark.rosenbaum(a)chromium.org).
I look forward to working with you,
Mark Rosenbaum
3 weeks, 1 day
Fedora 38: GDM not recognizing Wayland, only X11
by Scott Beamer
Greetings,
I did a fresh install of Fedora 38 on 19 February from the latest Live
images (both Workstation and KDE Spin).
Workstation install lists no option for either X11 or Wayland. Default
GNOME selection lands you in a GNOME session under X11.
I then installed the "KDE Plasma Workspaces" package group.
GDM then listed Plasma as an option, but only under X11.
I then switched from GDM to SDDM and SDDM shows options for both KDE and
GNOME under either X11 or Wayland.
If I select GNOME (Wayland) in SDDM and log in, I'm indeed logged into a
GNOME session under Wayland.
I did the reverse in the KDE Spin. SDDM recognized both Wayland and
X11, switching to GDM only gave me X11 as an option under either GNOME
or KDE.
Has anyone else seen this?
Scott
3 weeks, 5 days
Re: Test upgrades from F37 to F38 - it will take you just a minute
by Luna Jernberg
Did this 16th February and it worked then, other then a few packages
missing in F38 that was in F37 then mostly Google Fonts and RPM Fusion
stuff
On 2/22/23, Miroslav Suchý <msuchy(a)redhat.com> wrote:
> Do you want to make Fedora 38 better? Please spend 1 minute of your time and
> try to run:
>
> # Run this only if you use default Fedora modules
> # next time you run any DNF command default modules will be enabled again
> sudo dnf module reset '*'
>
> dnf --releasever=38 --setopt=module_platform_id=platform:f38 \
> --enablerepo=updates-testing \
> $(rpm -q fedora-repos-modular >/dev/null && echo
> --enablerepo=updates-testing-modular) \
> --assumeno distro-sync
>
>
> This command does not replace `dnf system-upgrade`, but it will reveals
> potential problems.
>
> You may also run `dnf upgrade` before running this command.
>
>
> The `--assumeno` will just test the transaction, but does not make the
> actual upgrade.
>
>
> In case you hit dependency issues, please report it against the appropriate
> package.
>
> Or against fedora-obsolete-packages if that package should be removed in
> Fedora 38. Please check existing reports against
>
> fedora-obsolete-packages first:
>
> https://red.ht/2kuBDPu
>
> and also there is already bunch of "Fails to install" (F38FailsToInstall)
> reports:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=F38FailsToInstall
>
> Thank you
>
> Miroslav
>
4 weeks
2023-02-20 - Fedora QA Meeting - Minutes
by Adam Williamson
==================================
#fedora-meeting: Fedora QA meeting
==================================
Meeting started by adamw at 16:01:09 UTC. The full logs are available at
https://meetbot.fedoraproject.org/fedora-meeting/2023-02-20/fedora-qa.202...
.
Meeting summary
---------------
* Roll Call (adamw, 16:02:08)
* Previous meeting follow-up (adamw, 16:09:24)
* "adamw to send out mail asking folks to vote on blockers in tickets"
- yeah, uh, I forgot. I'll do it later! I promise! this is also what
I keep saying about all those boxes in the garage (adamw, 16:11:14)
* ACTION: adamw to send out mail asking folks to vote on blockers in
tickets (adamw, 16:11:23)
* Fedora 38 status (adamw, 16:12:16)
* F38 has branched, openQA update test gating is enabled, beta freeze
starts in ~22 hours (adamw, 16:13:03)
* kparal wisely foresaw that tightened package crypto requirements
would cause major problems with popular third-party packages, see
https://bugzilla.redhat.com/show_bug.cgi?id=2170878 , this is
currently going through the normal blocker process but we may well
send it through the fesco blocker process if nobody speaks up to say
our understanding is incorrect (adamw, 16:29:31)
* Test Day / community event status (adamw, 16:31:25)
* sumantro has been off sick so we don't have all dates and details
nailed down yet, but several test days are in the pipeline,
including GNOME, i18n, Cloud, CoreOS, IoT, kernel 6.2, dnf5, and
probably the anaconda web installer (adamw, 16:36:40)
* we're also hoping to run an onboarding session soon (adamw,
16:36:50)
* there are a couple of outstanding workstation wg tickets that relate
to our testing events:
https://pagure.io/fedora-workstation/issue/359 and
https://pagure.io/fedora-workstation/issue/329 (adamw, 16:43:06)
* Open floor (adamw, 16:47:53)
* ACTION: adamw to read up on how the matrix/irc bridging works for
topic setting, and get sumantro appropriate rights to set topics on
both sides in the test day channel (adamw, 17:00:43)
Meeting ended at 17:04:21 UTC.
Action Items
------------
* adamw to send out mail asking folks to vote on blockers in tickets
* adamw to read up on how the matrix/irc bridging works for topic
setting, and get sumantro appropriate rights to set topics on both
sides in the test day channel
Action Items, by person
-----------------------
* adamw
* adamw to send out mail asking folks to vote on blockers in tickets
* adamw to read up on how the matrix/irc bridging works for topic
setting, and get sumantro appropriate rights to set topics on both
sides in the test day channel
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* adamw (87)
* chromebittin (28)
* SumantroMukherje (27)
* kparal (23)
* zodbot (7)
* rishi[m] (7)
* coremodule (4)
* neil (3)
* travier (1)
* tflink[m] (1)
* jforbes (1)
Generated by `MeetBot`_ 0.4
.. _`MeetBot`: https://fedoraproject.org/wiki/Zodbot#Meeting_Functions
--
Adam Williamson (he/him/his)
Fedora QA
Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw(a)fosstodon.org
https://www.happyassassin.net
1 month
f37/f38 "systemd still uses the old version"
by Felix Miata
# mount <yada>
mount: (hint) your fstab has been modified, but systemd still uses
the old version; use 'systemctl daemon-reload' to reload.
mount: (hint) your fstab has been modified, but systemd still uses
the old version; use 'systemctl daemon-reload' to reload.
mount: (hint) your fstab has been modified, but systemd still uses
the old version; use 'systemctl daemon-reload' to reload.
mount: (hint) your fstab has been modified, but systemd still uses
the old version; use 'systemctl daemon-reload' to reload.
#
This recently started in F37 and continues with upgrades to F38. I make /any/
change to fstab, then reboot, and next attempt to mount anything manually that was
nofail or noauto in fstab, or had been mounted and I wish to remount, produces the
above messages, no matter how many boots have occurred since the actual fstab
edit. It used to be that a reboot constituted a systemctl daemon-reload, but that
seems to have disappeared. I found nothing on point in bugzilla. How does it track
what the old fstab contained, or that it changed when any change occurred one or
morer boots ago?
--
Evolution as taught in public schools is, like religion,
based on faith, not based on science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata
1 month
