Bug 2435819 - During an offline update (via DNF5), the user must switch between graphical and TUI mode, in the resultant Plymouth TTY, for the update to progress past SELinux relabelling.
Summary: During an offline update (via DNF5), the user must switch between graphical a...
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: plymouth
Version: 43
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-02-01 18:47 UTC by Mr. Beedell, Roke Julian Lockhart (RJLB)
Modified: 2026-03-10 09:24 UTC (History)
4 users (show)

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


Attachments (Terms of Use)
A Screenshot Of The Stuck Process (1.46 MB, image/jpeg)
2026-02-01 18:47 UTC, Mr. Beedell, Roke Julian Lockhart (RJLB)
no flags Details

Description Mr. Beedell, Roke Julian Lockhart (RJLB) 2026-02-01 18:47:07 UTC
Created attachment 2127749 [details]
A Screenshot Of The Stuck Process

# Description of problem:

When I last invoked `sudo dnf5 upgrade -y --refresh --offline && sudo dnf5 offline reboot -y`, after the 1st OS reinitialisation, the upgrade process failed to progress for ⪆ PT15M, until I sent a keypress for “Escape” — which switched the TTY to Plymouth's graphical grey background, with a white horizontal pill — then pressed it again, to revert to the TUI.

# Version-release number of selected component:

> ~~~
> RokeJulianLockhart@Beedell:~$ rpm -qa | grep plymouth
> plymouth-kcm-6.5.5-1.fc43.x86_64
> plymouth-core-libs-24.004.60-24.fc43.x86_64
> plymouth-24.004.60-24.fc43.x86_64
> plymouth-scripts-24.004.60-24.fc43.x86_64
> plymouth-graphics-libs-24.004.60-24.fc43.x86_64
> plymouth-plugin-label-24.004.60-24.fc43.x86_64
> plymouth-plugin-two-step-24.004.60-24.fc43.x86_64
> plymouth-theme-spinner-24.004.60-24.fc43.x86_64
> plymouth-system-theme-24.004.60-24.fc43.x86_64
> plymouth-devel-24.004.60-24.fc43.x86_64
> ~~~

# How reproducible:

I've solely had it occur once, as others, who corroborate this, have.

# Steps to reproduce:

1.	~~~
	#!/usr/bin/env sh
	sudo dnf5 upgrade -y --refresh --offline && \
	sudo dnf5 offline reboot -y
	~~~

2.	Send a key press for “Escape”.

# Actual results:

When DNF5 instructed SELinux to relabel itself during an offline OS upgrade, it failed to progress for ⪆ PT15M, until I sent a keypress for “Escape” — which switched the TTY to Plymouth's graphical grey background, with a white horizontal pill — then pressed it again, to revert to the TUI.

# Expected results:

I should not have needed to switch between Plymouth's horizontal pill atop a grey background, then back to its TUI, by pressing “Escape”, for the update to progress.

# Additional info:

`cat /etc/default/grub` returns:

> ~~~
> GRUB_TIMEOUT="15"
>   # Original: GRUB_TIMEOUT=5
> GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)"
>   # Original: Identical
> GRUB_DEFAULT="saved"
>   # Original: Identical
> GRUB_DISABLE_SUBMENU="true"
>   # Original: GRUB_DISABLE_SUBMENU=true
> GRUB_TERMINAL_OUTPUT="gfxterm"
>   # Original: GRUB_TERMINAL_OUTPUT="console"
> GRUB_CMDLINE_LINUX=""
>   # Original: GRUB_CMDLINE_LINUX="rhgb quiet"
> GRUB_DISABLE_RECOVERY="false"
>   # Original: GRUB_DISABLE_RECOVERY="true"
> GRUB_ENABLE_BLSCFG="true"
>   # Original: GRUB_ENABLE_BLSCFG=true
>   # Reason: https://discussion.fedoraproject.org/t/missing-boot-entries-with-grub-enable-blscfg-true/70805/3
> GRUB_GFXMODE="2560x1440,auto"
>   # Original: None
> GRUB_DISABLE_OS_PROBER="true"
>   # Original: None
>   # Reason: https://github.com/MaddieM4/os-prober/issues/5#issue-777438588
> ~~~

This was originally reported at https://discussion.fedoraproject.org/t/an-offline-update-has-not-progressed-past-relebelling-for-pt15m/180432/4, whereupon another user corroborated that they had experienced this, and advised me to report it here.

Comment 1 pg_tips 2026-03-10 09:24:38 UTC
I've also seen this in a "non-offline" upgrade.

I did a dnf update which updated (among other packages) selinux-policy and selinux-policy-targeted. On the first reboot after the update, I saw the same behaviour described in the original bug report.


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