Bug 2549530 - Some apps can't write passwords to oo7 keyring because of invalid content type
Summary: Some apps can't write passwords to oo7 keyring because of invalid content type
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: oo7
Version: 45
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Fabio Valentini
QA Contact:
URL:
Whiteboard: RejectedBlocker AcceptedFreezeException
Depends On:
Blocks: F45FinalFreezeException, FinalFreezeException 2503681
TreeView+ depends on / blocked
 
Reported: 2026-10-12 11:17 UTC by Kamil Paral (Fedora Quality)
Modified: 2026-10-19 15:48 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github abrt libreport issues 830 0 None open Passwords can't be saved to the keyring with oo7-daemon instead of gnome-keyring-daemon 2026-10-12 11:23:50 UTC
Github linux-credentials oo7 issues 597 0 None open gnome-abrt can't save Bugzilla api key: Invalid content type: application/libreport 2026-10-12 11:17:43 UTC

Description Kamil Paral (Fedora Quality) 2026-10-12 11:17:44 UTC
Description of problem:
There is a regression in the gnome-keyring-daemon -> oo7-daemon switch, which makes some apps unable to save passwords into the keyring. 

So far, I've found these issues:
gnome-abrt: https://github.com/linux-credentials/oo7/issues/597 and https://github.com/abrt/libreport/issues/830


Version-Release number of selected component (if applicable):
oo7-daemon-0.7.0~beta-1.fc45.x86_64
oo7-portal-0.7.0~beta-1.fc45.x86_64
oo7-cli-0.7.0~beta-1.fc45.x86_64

How reproducible:
see the upstream issues

Comment 1 Kamil Paral (Fedora Quality) 2026-10-12 11:19:01 UTC
Proposing for a Blocker discussion:
"Saving passwords to and retrieving passwords from the default keyring must work for all release-blocking desktops. "
https://fedoraproject.org/wiki/Fedora_45_Final_Release_Criteria#Desktop_keyring

Comment 2 Kamil Paral (Fedora Quality) 2026-10-12 12:31:10 UTC
Note that there's also a Nautilus regression, but it seems caused by a different problem and doesn't make Nautilus completely broken like ABRT:
https://gitlab.gnome.org/GNOME/nautilus/-/work_items/4347

I'm not sure whether this actually means Nautilus fails to retrieve the already existing keyring items, unclear at this moment.

Comment 3 Lukas Ruzicka (Red Hat) 2026-10-12 17:53:29 UTC
AGREED Delayed Decision (Punt)

Discussed at the 2026-10-12 (blocker / freeze exception) review meeting:

We would like to see more data on this one before making a decision, particularly whether any significant pre-installed applications are affected by this. We hope folks will do more testing and/or look through other existing filed bugs for ones that fit this pattern.

https://meetbot-raw.fedoraproject.org//blocker-review_matrix_fedoraproject-org/2026-10-12/f45-blocker-review.2026-10-12-16.00.log.txt

Comment 4 Kamil Paral (Fedora Quality) 2026-10-14 12:37:29 UTC
(In reply to Kamil Paral (Fedora Quality) from comment #2)
> Note that there's also a Nautilus regression, but it seems caused by a
> different problem and doesn't make Nautilus completely broken like ABRT:
> https://gitlab.gnome.org/GNOME/nautilus/-/work_items/4347

I have created a separate bug for this, see bug 2552171 . 

Let's keep this bug related to just apps broken by the "invalid content type" problem.

Comment 5 Kamil Paral (Fedora Quality) 2026-10-15 13:08:50 UTC
I tried to test all preinstalled apps in F45 Workstation and didn't find any more issues. Not this one ("invalid content type") nor any other.

Comment 6 Kamil Paral (Fedora Quality) 2026-10-19 15:48:38 UTC
From https://forge.fedoraproject.org/quality/blocker-review/issues/2221 :
AGREED RejectedFinalBlocker
AGREED AcceptedFinalFreezeException


Note You need to log in before you can comment on or make changes to this bug.