Closed CleoMenezesJr closed 1 year ago
The content of that screenshot in text format would be great. Thanks
It's in the description:
thread 'tokio-runtime-worker' panicked at 'assertion failed: !(self.ptype == ProgressType::Task)', rust/src/console_progress.rs:124:9 note: run with
RUST_BACKTRACE=1
environment variable to display a backtrace
Otherwise it was an rpm-ostree status
that had run before.
Could you retry with RUST_BACKTRACE=1
and post the output here?
I am facing the same error when I try to update. I am on f38 branch. RUST_BACKTRACE=1
did not give any new output. So I tried with RUST_BACKTRACE=full
. Here is the output:
RUST_BACKTRACE=full rpm-ostree upgrade
note: automatic updates (stage) are enabled
⠓ Receiving objects; 98% (2609/2662) 889.6 kB/s 500.0 MB
Enabled rpm-md repositories: fedora-cisco-openh264 fedora-modular updates-modular updates-testing-modular updates-testing updates fedora rpmfusion-free-updates-testing rpmfusion-free rpmfusion-nonfree-updates-testing rpmfusion-nonfree phracek-PyCharm rpmfusion-nonfree-nvidia-driver rpmfusion-nonfree-steam google-chrome copr:copr.fedorainfracloud.org:vstanek:gnome-info-collect updates-archive
⠋ Receiving objects; 98% (2609/2662) 889.6 kB/s 500.0 MB
thread 'tokio-runtime-worker' panicked at 'assertion failed: !(self.ptype == ProgressType::Task)', rust/src/console_progress.rs:124:9
stack backtrace:
0: 0x562b65b70b3a - <unknown>
1: 0x562b65b99f7e - <unknown>
2: 0x562b65b69375 - <unknown>
3: 0x562b65b70905 - <unknown>
4: 0x562b65b7204f - <unknown>
5: 0x562b65b71d8b - <unknown>
6: 0x562b65b7275c - <unknown>
7: 0x562b65b724b2 - <unknown>
8: 0x562b65b70fec - <unknown>
9: 0x562b65b72202 - <unknown>
10: 0x562b65355ba3 - <unknown>
11: 0x562b65355c7d - <unknown>
12: 0x562b6580c015 - <unknown>
13: 0x562b6548232f - <unknown>
14: 0x7fe9984303c2 - g_closure_invoke
15: 0x7fe99845f4f8 - <unknown>
16: 0x7fe99844ebea - g_signal_emit_valist
17: 0x7fe99844ee13 - g_signal_emit
18: 0x7fe99859a90b - <unknown>
19: 0x7fe998586210 - <unknown>
20: 0x7fe99832b9ed - <unknown>
21: 0x7fe99832f788 - g_main_context_dispatch
22: 0x7fe99838ddd8 - <unknown>
23: 0x7fe99832ee8f - g_main_loop_run
24: 0x562b6548051a - <unknown>
25: 0x562b65473460 - <unknown>
26: 0x562b65477176 - <unknown>
27: 0x562b65470d54 - <unknown>
28: 0x562b655b646c - <unknown>
29: 0x562b6541f3f7 - <unknown>
30: 0x562b6546d872 - <unknown>
31: 0x562b65acc009 - <unknown>
32: 0x562b65abcf4b - <unknown>
33: 0x562b65ac9f1a - <unknown>
34: 0x562b65b78ae3 - <unknown>
35: 0x7fe997666c57 - start_thread
36: 0x7fe9976eca70 - __clone3
37: 0x0 - <unknown>
Aborted (core dumped)
Looks like https://github.com/coreos/rpm-ostree/issues/4284. Discussion and fix will happen there.
FYI @travier looks like rpm-ostree 2023.4 has the bulk of the fix for this (https://github.com/coreos/rpm-ostree/issues/4284#issuecomment-1553498420)
Thanks! Closing now that this is fixed
Describe the bug When using rpm-ostree, it always returns after the post script the following:
To Reproduce Please describe the steps needed to reproduce the bug:
rpm-ostree
somethingExpected behavior No Rust loga
Screenshots If applicable, add screenshots to help explain your problem.
OS version: