Bug 2036454 - Anaconda installer fails to start: gnome-kiosk exited with status 1, libvulkan.so.1missing
Summary: Anaconda installer fails to start: gnome-kiosk exited with status 1, libvulka...
Keywords:
Status: CLOSED DUPLICATE of bug 2036724
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: rawhide
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-01 21:51 UTC by François Rigault
Modified: 2022-01-03 18:37 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2022-01-03 18:37:04 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 2036467 1 unspecified CLOSED Chromium conflicts with the vulkan-loader package 2022-01-06 20:52:29 UTC

Description François Rigault 2022-01-01 21:51:04 UTC
Description of problem:
Anaconda fails to start
see: https://openqa.fedoraproject.org/tests/1093342#step/_boot_to_anaconda/13


Version-Release number of selected component (if applicable):
latest Fedora-Server-netinst-x86_64-Rawhide-20220101.n.0.iso

How reproducible:
booting a VM with Fedora-Server-netinst-x86_64-Rawhide-20220101.n.0.iso


Steps to Reproduce:
1. prepare a kickstart file 
2. boot the latest iso file in qemu-kvm
3.

Actual results:
anaconda fails with a python error claiming gnome-kiosk exited with status 1

Expected results:
installation starts


Additional info:
from X.log: (also in https://openqa.fedoraproject.org/tests/1093342/file/_boot_to_anaconda-X.log)
[    59.869] (EE) AIGLX error: dlopen of /usr/lib64/dri/swrast_dri.so failed (libvulkan.so.1: cannot open shared object file: No such file or directory)

this file is normally provided as part of package vulkan-loader.
This file used to exist in Fedora-Server-netinst-x86_64-35-1.2.iso for example, but is missing from the latest Rawhide.

Comment 1 François Rigault 2022-01-03 18:37:04 UTC
actually in issue in chromium (2036467)

*** This bug has been marked as a duplicate of bug 2036724 ***


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