Fedora 45: repeated Default keyring unlock prompts after system upgrade

未关闭
#685 4 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
48/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
fedora, linux, rust

调研方向

Start by reading the oo7 daemon prompt and migration logs described in the report, then inspect how the daemon discovers and unlocks keyrings. The issue does not identify a failing test or a known cause, so first gather the requested non-sensitive logs and reproduce the behavior. Done means explaining why unlock prompts recur and providing a way to restore access without losing credentials.

由索引模型根据 Issue 内容生成。

描述

server

After a system upgrade, applications repeatedly display:

Authentication required — An application wants access to the keyring “Default”, but it is locked.

Entering my administrator password results in an incorrect-password error. Multiple reboots have not resolved the issue. The prompts were absent for several boots before returning.

Environment
  • Fedora Linux 45 Workstation
  • oo7-daemon: 0.7.0~beta^1.e91b98a-1.fc45.x86_64
  • gnome-keyring package is not currently installed
Logs

The user journal repeatedly reports:

oo7_daemon::prompt: Keyring Default failed to unlock, incorrect secret.

The daemon also reports:

oo7_daemon::service: Discovered 2 keyring(s), 0 pending migration(s)

The keyring directory contains:

default.keyring
default.keyring~
default.keyring.lock
login.keyring
login.keyring.migrated
user.keystore
v1/
Expected behavior

The keyring unlocks normally without repeated prompts during application use.

Actual behavior

Prompts recur whenever applications try to access stored credentials.

Could this be related to the GNOME Keyring → oo7 migration? How can I diagnose and restore access without losing stored credentials? Please advise which additional non-sensitive logs would help.

No keyring files have been deleted or reset during this investigation.

主要语言
Rust
星标
481
派生
62
平均合并
9 小时 51 分钟
30 天内合并 PR
55

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

linux-credentials/oo7 的其他 Issue

查看 linux-credentials/oo7 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。