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
21 hours, 12 minutes
new criterion proposal: Window manager functionality
by Kamil Paral
Related to a recently proposed blocker [1][2], I propose a new release
criterion which would cover such cases. Here it is:
~~~~~~~~~~~~
The desktop environment must work correctly when displaying common
application content - that includes regular application windows, video
output, games and possibly other common content. Regular operations like
windows close/resize/maximize/minimize/fullscreen (when
supported/applicable), windows switching, using windows on virtual
workspaces, and similar common operations must behave as expected.
Footnote - "What does this cover?":
A small number of misbehaving applications is not a violation of this
criterion. The goal of this criterion is to ensure general functionality
for different types of applications and their operations. An example of a
violation would be e.g. if a significant number of QT applications couldn't
be resized (but they should be), or if all Java applications failed to
display any content.
~~~~~~~~~~~~~
I think this criterion could target F38 Beta Release Criteria [3] or Basic
Release Criteria [4].
Please tell me your thoughts, thanks!
Kamil
[1] https://pagure.io/fedora-qa/blocker-review/issue/1102
[2] https://bugzilla.redhat.com/show_bug.cgi?id=2178167
[3] https://fedoraproject.org/wiki/Fedora_38_Beta_Release_Criteria
[4] https://fedoraproject.org/wiki/Basic_Release_Criteria
22 hours, 48 minutes
test kernels 6.2.x in F37 - an ultimate killer
by lejeczek
Hi guys.
Just to let you know - all the kernels I tried, x.5 tin x.7
, kill the system...
.. when some video in a browser - as I do not playback any
videos allow cannot comment there - is played or paused and
some resizing or switching or showing thumbnails/miniatures
(tabs) is show/played/takes place, then Fedora starts
blinking my both monitors, laptop's builtin & external Dell.
Blinking slow, black & desktop view alternately, at ~1 sec
intervals then about ~1 min later both monitors switch black
& stay that way.
From the very blink system is irresponsible - hard
power-cycle is a must.
Interestingly(?) audio continues - until of course, all goes
black - to playback okey.
Nothing else is from koji/test, up to date from repos OS.
System - Thinkpad e14 g2 (AMD)
regards, L.
1 day, 19 hours
Feedback F38 Beta
by old sixpack13
F38 updgrade was smooth, but 2 minor Bug's:
1.
some (not all) programs now do not start in fullscreen mode, e.g. Thunderbird (closed in full screen, opens in half(?) screen)
Idea's ?
2.
in journals I see this:
[ 13.645950] systemd-journald[609]: /var/log/journal/2b1f41d17a074c0ebb0a14b4f977d212/user-1000.journal: Montonic clock jumped backwards relative to last journal entry, rotating.
[ 13.645957] systemd-journald[609]: Failed to write entry to /var/log/journal/2b1f41d17a074c0ebb0a14b4f977d212/user-1000.journal (31 items, 879 bytes), rotating before retrying: Not a XENIX named type file
I must mention that I'm running a homebrewed kernel build with nearly the .config F38 uses (mostly driver I don't need are OFF)
known ?
or should I fill a BZ ?
2 days, 8 hours
2023-03-20 - Fedora QA Meeting - Minutes
by Adam Williamson
==================================
#fedora-meeting: Fedora QA meeting
==================================
Meeting started by adamw at 15:00:39 UTC. The full logs are available at
https://meetbot.fedoraproject.org/fedora-meeting/2023-03-20/fedora-qa.202...
.
Meeting summary
---------------
* Roll Call (adamw, 15:00:59)
* Previous meeting follow-up (adamw, 15:07:24)
* 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, 15:08:13)
* Window manager release criterion proposal (adamw, 15:11:12)
* kparal proposed a criterion covering window manager functionality on
release-blocking desktops:
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.or...
(adamw, 15:12:00)
* Fedora 38 status (adamw, 15:28:40)
* Beta is out, thanks again to all who worked on it (adamw, 15:28:51)
* Final freeze is scheduled for April 4 (adamw, 15:29:17)
* blocker review meeting follows this meeting over in
#fedora-blocker-review (adamw, 15:29:31)
* Test Day / community event status (adamw, 15:46:15)
* several test days finished up since the last meeting, including DNF
test day - https://testdays.fedoraproject.org/events/152 - and
kernel 6.2 test week - https://testdays.fedoraproject.org/events/148
(adamw, 15:50:27)
* we also had the GNOME core -
https://testdays.fedoraproject.org/events/150 - and apps -
https://testdays.fedoraproject.org/events/151 test days, and i18n
test week - https://testdays.fedoraproject.org/events/147 (adamw,
15:51:20)
* ACTION: adamw to check in with sumantro on status of iot and coreos
test weeks (adamw, 15:53:39)
* Open floor (adamw, 15:53:43)
Meeting ended at 15:57:58 UTC.
Action Items
------------
* 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 to check in with sumantro on status of iot and coreos test weeks
Action Items, by person
-----------------------
* adamw
* 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 to check in with sumantro on status of iot and coreos test
weeks
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* adamw (73)
* LunaJernberg[m] (22)
* kparal (19)
* zodbot (10)
* geraldosimiao (10)
* lruzicka (9)
* kalev (3)
* neil (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
2 days, 11 hours
2023-03-06 - Fedora QA Meeting - Minutes
by Adam Williamson
==================================
#fedora-meeting: Fedora QA meeting
==================================
Meeting started by adamw at 16:01:23 UTC. The full logs are available at
https://meetbot.fedoraproject.org/fedora-meeting/2023-03-06/fedora-qa.202...
.
Meeting summary
---------------
* Roll Call (adamw, 16:01:24)
* Previous meeting follow-up (adamw, 16:07:13)
* "adamw to send out mail asking folks to vote on blockers in tickets"
- yeah, I think I did that (adamw, 16:07:47)
* "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" oh yeah, I didn't do this one yet. in
my defence things were a bit on fire (adamw, 16:08:17)
* 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, 16:08:24)
* Fedora 38 status (adamw, 16:10:55)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2175648 (kparal,
16:14:20)
* f38 is frozen for Beta, first go/no-go is Thursday, we still have
outstanding blockers that are being worked on (adamw, 16:15:41)
* Test Day / community event status (adamw, 16:22:54)
* LINK: https://testdays.fedoraproject.org/events/148
(SumantroMukherje, 16:24:13)
* LINK: https://testdays.fedoraproject.org/events/150
(SumantroMukherje, 16:25:00)
* LINK: https://testdays.fedoraproject.org/events/151
(SumantroMukherje, 16:25:00)
* LINK: https://testdays.fedoraproject.org/events/147
(SumantroMukherje, 16:25:24)
* LINK:
https://fedoraproject.org/wiki/Test_Day:2023-03-14_Fedora_38_DNF_5
(SumantroMukherje, 16:26:22)
* kernel 6.2 test week is underway at
https://testdays.fedoraproject.org/events/148 (adamw, 16:27:01)
* GNOME 44 desktop and app test days are underway at
https://testdays.fedoraproject.org/events/150 and
https://testdays.fedoraproject.org/events/151 (adamw, 16:27:19)
* i18n test week starts tomorrow at
https://testdays.fedoraproject.org/events/147 (adamw, 16:27:30)
* DNF 5 test day is on 2023-03-14:
https://fedoraproject.org/wiki/Test_Day:2023-03-14_Fedora_38_DNF_5
(adamw, 16:27:45)
* AGREED: big thanks to kparal for overhauling the GNOME test cases
(adamw, 16:32:49)
* Open floor (adamw, 16:39:38)
Meeting ended at 16:48:29 UTC.
Action Items
------------
* 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 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 (47)
* SumantroMukherje (23)
* LunaJernberg[m] (19)
* kparal (13)
* zodbot (11)
* geraldosimiao (11)
* lruzicka (6)
* yselkowitz[m] (3)
* coremodu_ (2)
* bittin (1)
* tflink (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
2 days, 11 hours
2023-03-20 @ **15:00** UTC - Fedora QA Meeting
by Adam Williamson
# Fedora Quality Assurance Meeting
# Date: 2023-03-20
# Time: **15:00** UTC
(https://fedoraproject.org/wiki/Infrastructure/UTCHowto)
# Location: #fedora-meeting on irc.libera.chat
Greetings testers!
It's meeting time again! Let's pat ourselves on the back for Fedora 38
Beta and look forward to Final.
Remember that clocks went forward in North America last weekend, so
the meeting time in UTC is an hour earlier than before. If you do not
observe daylight savings time, or your clocks did not yet go forward,
the meeting will be an hour earlier in your local time. Please double
check!
If anyone has any other items for the agenda, please reply to this
email and suggest them! Thanks.
== Proposed Agenda Topics ==
1. Previous meeting follow-up
2. Window manager release criterion proposal
3. Fedora 38 status
4. Test Day / community event status
5. Open floor
--
Adam Williamson (he/him/his)
Fedora QA
Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw(a)fosstodon.org
https://www.happyassassin.net
3 days
Fedora 38 Beta Feedback (Kernel Errors with GPU)
by jose Sarasola
Since the upgrade to the 38 beta, laptop has become quite unstable. Firefox seems to crash the GPU completely, needing to force a reboot, and brave browser is crashing randomly.
Hardware:
Lenovo ThinkPad E14 Gen 3
AMD Ryzen™ 7 5700U with Radeon™ Graphics × 16
Some attatched logs:
```
mar 20 10:14:02 jmsarasola-irontec kernel: [drm:dc_dmub_srv_wait_idle [amdgpu]] *ERROR* Error waiting for DMUB idle: status=3
mar 20 10:14:42 jmsarasola-irontec kernel: [drm:dc_dmub_srv_wait_idle [amdgpu]] *ERROR* Error waiting for DMUB idle: status=3
mar 20 10:15:11 jmsarasola-irontec kernel: [drm:dc_dmub_srv_wait_idle [amdgpu]] *ERROR* Error waiting for DMUB idle: status=3
mar 20 10:17:06 jmsarasola-irontec kernel: amdgpu 0000:04:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:40 vmid:6 pasid:32780, for process RDD Process pid 2927 thread firefox:cs0 pid 22005)
mar 20 10:17:06 jmsarasola-irontec kernel: amdgpu 0000:04:00.0: amdgpu: in page starting at address 0x0000ffffffe00000 from IH client 0x1b (UTCL2)
mar 20 10:17:06 jmsarasola-irontec kernel: amdgpu 0000:04:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00640C50
mar 20 10:17:06 jmsarasola-irontec kernel: amdgpu 0000:04:00.0: amdgpu: Faulty UTCL2 client ID: CPG (0x6)
mar 20 10:17:06 jmsarasola-irontec kernel: amdgpu 0000:04:00.0: amdgpu: MORE_FAULTS: 0x0
mar 20 10:17:06 jmsarasola-irontec kernel: amdgpu 0000:04:00.0: amdgpu: WALKER_ERROR: 0x0
mar 20 10:17:06 jmsarasola-irontec kernel: amdgpu 0000:04:00.0: amdgpu: PERMISSION_FAULTS: 0x5
mar 20 10:17:06 jmsarasola-irontec kernel: amdgpu 0000:04:00.0: amdgpu: MAPPING_ERROR: 0x0
mar 20 10:17:06 jmsarasola-irontec kernel: amdgpu 0000:04:00.0: amdgpu: RW: 0x1
mar 20 10:17:17 jmsarasola-irontec kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_high timeout, signaled seq=231317, emitted seq=231318
mar 20 10:17:17 jmsarasola-irontec kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process gnome-shell pid 1653 thread gnome-shel:cs0 pid 1689
mar 20 10:17:17 jmsarasola-irontec kernel: [drm:dc_dmub_srv_wait_idle [amdgpu]] *ERROR* Error waiting for DMUB idle: status=3
```
3 days, 2 hours
Feeback F38 Beta
by old sixpack13
F38 updgrade was smooth, but 2 minor Bug's:
1.
some (not all) programs now do not start in fullscreen mode, e.g. Thunderbird (closed in full screen, opens in half(?) screen)
Idea's ?
2.
in journals I see this:
[ 13.645950] systemd-journald[609]: /var/log/journal/2b1f41d17a074c0ebb0a14b4f977d212/user-1000.journal: Montonic clock jumped backwards relative to last journal entry, rotating.
[ 13.645957] systemd-journald[609]: Failed to write entry to /var/log/journal/2b1f41d17a074c0ebb0a14b4f977d212/user-1000.journal (31 items, 879 bytes), rotating before retrying: Not a XENIX named type file
I must mention that I'm running a homebrewed kernel build with nearly the .config F38 uses (mostly driver I don't need are OFF)
known ?
or should I fill a BZ ?
3 days, 21 hours
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, 16 hours
