Nerijus Baliūnas
Nerijus Baliūnas
brctl show ``` bridge name bridge id STP enabled interfaces br0 8000.549f350629ca no em2 vnet0 vnet1 vnet2 virbr0 8000.525400dbf7a0 yes virbr0-nic ```
Why to create additional virbr at all?
I applied the patch in http://lists.ovirt.org/pipermail/kimchi-devel/2015-February/009779.html to 1.4.1, but still the same error: Unable to create bridge virbr0: File already exists
I am using the following patch for now: ``` --- a/src/kimchi/model/networks.py +++ b/src/kimchi/model/networks.py @@ -79,7 +79,7 @@ else: kimchi_log.error("Fatal: Cannot activate default network " "because of %s, exit kimchid", e.message)...
Can anyone explain me, what this problem is about at all? Why kimchi cannot use the existing virbr0 and insists on creating a new interface?
I "fixed" it by using the following: ``` diff --git a/v4/export/config.go b/v4/export/config.go index b7bf104..a46168c 100644 --- a/v4/export/config.go +++ b/v4/export/config.go @@ -182,8 +182,8 @@ func (conf *Config) String() string { func...
Fedora 36 has quite recent mesa - 22.0.3.
Crash still happens with mesa 22.1.2.
Crash does not happen with `flatpak install fedora net.sourceforge.liferea`, but still happens with `flatpak install flathub net.sourceforge.liferea`. So workaround for me is to use flatpak version from remote fedora.
`GDK_BACKEND=x11 liferea` works, so the crash happens only on Wayland it seems.