Search
Star
Feedback
Setup for Free
© 2026 Hedgehog Software, LLC
Twitter
GitHub
Discord
System
Light
Dark
More
Communities
Docs
About
Terms
Privacy
Issue rebase from F42 to F41 - Bazzite
B
Bazzite
•
10mo ago
•
3 replies
Borduk
Issue rebase from F42 to F41
Hello y
'all
,
I
'm having issues rebasing from
b
a
z
z
i
t
e
:stable to
b
a
z
z
i
t
e
:41
.20250227
.1
. Both rpm
-ostree rebase and bazzite
-rollbacl
-helper rebase are working
, but after the reboot rpm
-ostree status shows Warning
: failed to finalize previous deployment
error
: Finalizing deployment
: Finalizing SELinux policy
: failed to run semodule
: Der Kindprozess wurde mit Status 1 beendet
and journalctl shows
Apr 19
0
0
:
1
6
:59
systemd
[1
]
: Finished ostree
-finalize
-staged
.service
- OSTree Finalize Staged Deployment
.
Apr 19
0
0
:
1
7
:47
systemd
[1
]
: Stopping ostree
-finalize
-staged
.service
- OSTree Finalize Staged Deployment
.
.
.
Apr 19
0
0
:
1
7
:47
ostree
[7107
]
: Finalizing staged deployment
Apr 19
0
0
:
1
7
:48
ostree
[7107
]
: Copying
/etc changes
: 26 modified
, 1 removed
, 99 added
Apr 19
0
0
:
1
7
:48
ostree
[7107
]
: Copying
/etc changes
: 26 modified
, 1 removed
, 99 added
Apr 19
0
0
:
1
7
:48
ostree
[7123
]
: bwrap
: execvp semodule
: No such file or directory
Apr 19
0
0
:
1
7
:48
ostree
[7107
]
: error
: Finalizing deployment
: Finalizing SELinux policy
: failed to run semodule
: Der Kindprozess wurde mit Status 1 bee
>
Apr 19
0
0
:
1
7
:48
systemd
[1
]
: ostree
-finalize
-staged
.service
: Control process exited
, code
=exited
, status
=1
/FAILURE
Apr 19
0
0
:
1
7
:48
systemd
[1
]
: ostree
-finalize
-staged
.service
: Failed with result
'exit
-code
'
.
Apr 19
0
0
:
1
7
:48
systemd
[1
]
: Stopped ostree
-finalize
-staged
.service
- OSTree Finalize Staged Deployment
.
Apr 19
0
0
:
1
7
:48
*
*
* systemd
[1
]
: ostree
-finalize
-staged
.service
: Consumed 589ms CPU time
, 89
.7M memory peak
.
other people seem to have the same issue
. found a post without solution on answer overflow
:
https://www.answeroverflow.com/m/1362354504577585334
The issue arised when trying to replace v4v2loopback
-0
.14
.0 with 0
.13
.2 but failed
.
problems rolling back from F42 to F41 - Universal Blue
Hi
,
So I decided to rollback from the F42 based bazzite because of problems with podman containers
(
https://github.com/ublue-os/bazzite/issues/2492
)
However
, doing the rollback I get the following error message
:
`
`
`
kevinh
@
a
m
d
t
o
p
:
~
$ rpm
-ostree rebase ostree
-image
-
s
i
g
n
e
d
:
d
o
c
k
e
r
:
/
/ghcr
.io
/ublue
-os
/
b
a
z
z
i
t
e
:testing
-41
.20250410
.1
Pulling
m
a
n
i
f
e
s
t
:
.
.
.
Bazzite
Join
The operating system for the next generation of gamers.
29,482
Members
View on Discord
Resources
ModelContextProtocol
ModelContextProtocol
MCP Server
Was this page helpful?
Yes
No
Similar Threads
Similar Threads
problems rolling back from F42 to F41
B
Bazzite / 🛟bazzite-help
10mo ago
Rebase from Nvidia to AMD Failed
B
Bazzite / 🛟bazzite-help
2mo ago
Rebase to Nvidia?
B
Bazzite / 🛟bazzite-help
13mo ago
rebase to F38
B
Bazzite / 🛟bazzite-help
3y ago