Description of problem: Followed the setup screen after installing it from Gnome Software, when it said "Downloading... Sit down relax" it crashed. Bug presists after reinstall. Version-Release number of selected component: python3-3.10.0-1.fc35 Additional info: reporter: libreport-2.15.2 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-glib-com.usebottles.bottles-8928.scope cmdline: /usr/bin/python3 /usr/bin/bottles crash_function: _gtk_css_value_compute executable: /usr/bin/python3.10 journald_cursor: s=ecbde1502ebd44e29e3ec958f66d8d84;i=f1c;b=9f152d89d76d4e50af5f2c6f324ccf08;m=16a8b820a;t=5cf9591f72dbb;x=e2bd9f5c15102eaf kernel: 5.14.15-300.fc35.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000
Created attachment 1838541 [details] File: backtrace
Created attachment 1838542 [details] File: core_backtrace
Created attachment 1838543 [details] File: cpuinfo
Created attachment 1838544 [details] File: dso_list
Created attachment 1838545 [details] File: environ
Created attachment 1838546 [details] File: exploitable
Created attachment 1838547 [details] File: limits
Created attachment 1838548 [details] File: maps
Created attachment 1838549 [details] File: mountinfo
Created attachment 1838550 [details] File: open_fds
Created attachment 1838551 [details] File: proc_pid_status
It's a /usr/bin/bottles crash.
FEDORA-2022-14524d28ef has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-14524d28ef
FEDORA-2022-14524d28ef has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-14524d28ef` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-14524d28ef See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-14524d28ef has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.