Bug 1912159

Same here. Latest update from updates-testing broke things.
Downgraded mesa-vulkan-drivers-20.3.2-1.fc33.x86_64 to mesa-vulkan-drivers-20.2.6-1.fc33.x86_64 and it works again.

https://bugzilla.redhat.com/attachment.cgi?id=1744164 shows pidgin crashing in /lib64/libgstvulkan-1.0.so.0 , so that's the prime suspect.

I think the difference between Pidgin running older mesa-vulkan-driver is this message:

~~~
WARNING: lavapipe is not a conformant vulkan implementation, testing use only.
~~~

So I'd say that for the recent mesa, the lavapipe is used unexpectedly for some reason.

(In reply to Vít Ondruch from comment #3)
> So I'd say that for the recent mesa, the lavapipe is used unexpectedly for
> some reason.

That is possible, and would be an issue of its own.

The crash itself could still be a gstreamer1-plugins-bad-free bug though.

(In reply to Vít Ondruch from comment #3)
> So I'd say that for the recent mesa, the lavapipe is used unexpectedly for
> some reason.

Can you attach the output of vulkaninfo from that system?

Created attachment 1745816 [details]
mesa-vulkan-drivers-20.2.2-1.fc34.x86_64

vulkaninfo output for mesa-vulkan-drivers-20.2.2-1.fc34.x86_64

Created attachment 1745817 [details]
mesa-vulkan-drivers-20.3.2-1.fc34.x86_64

But the vulkaninfo with the mesa-vulkan-drivers-20.3.2-1.fc34.x86_64 behaves rather strange. The command `$ vulkaninfo 2&>1 vulkaninfo-new.log` does not create any file. It works with the `>` though, reporting similar 'lavapipe' message as pidgin:

~~~
$ vulkaninfo > vulkaninfo-new.log
WARNING: lavapipe is not a conformant vulkan implementation, testing use only.
MESA-INTEL: warning: Performance support disabled, consider sysctl dev.i915.perf_stream_paranoid=0
~~~

This seems to be the main difference:

~~~
Layers: count = 1
=================
VK_LAYER_MESA_device_select (Linux device selection layer) Vulkan version 1.1.73, layer version 1:
	Layer Extensions: count = 0
	Devices: count = 2
		GPU id = 0 (llvmpipe (LLVM 11.0.1, 256 bits))
		Layer-Device Extensions: count = 0

		GPU id = 1 (Intel(R) HD Graphics 620 (KBL GT2))
		Layer-Device Extensions: count = 0
~~~

where with the older Mesa there was just:

~~~
Layers: count = 1
=================
VK_LAYER_MESA_device_select (Linux device selection layer) Vulkan version 1.1.73, layer version 1:
	Layer Extensions: count = 0
	Devices: count = 1
		GPU id = 0 (Intel(R) HD Graphics 620 (KBL GT2))
		Layer-Device Extensions: count = 0
~~~

Not sure why llvmpipe is there, why it gets priority and why it doesn't work (while I can imagine the software renderer lags behind other implementations).

do you by any chance have DRI_PRIME set in your environment or elsewhere, or does the machine have two GPUs?

I am running into the issuses on Lenovo T470s with single GPU. This is my environment:

~~~
$ env | sort
COLORTERM=truecolor
DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
DESKTOP_SESSION=gnome
DISPLAY=:0
EDITOR=vim
GDM_LANG=cs_CZ.UTF-8
GDMSESSION=gnome
GIT_PS1_SHOWDIRTYSTATE=true
GIT_PS1_SHOWUNTRACKEDFILES=true
GJS_DEBUG_OUTPUT=stderr
GJS_DEBUG_TOPICS=JS ERROR;JS LOG
GNOME_SETUP_DISPLAY=:1
GNOME_TERMINAL_SCREEN=/org/gnome/Terminal/screen/2fe4cad1_6960_4e67_8e98_dc2ecec72a24
GNOME_TERMINAL_SERVICE=:1.116
HISTCONTROL=ignoredups
HISTSIZE=1000
HOME=/home/vondruch
HOSTNAME=fedora
LANG=cs_CZ.UTF-8
LESSOPEN=||/usr/bin/lesspipe.sh %s
LOGNAME=vondruch
LS_COLORS=rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:mi=01;37;41:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arc=01;31:*.arj=01;31:*.taz=01;31:*.lha=01;31:*.lz4=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.tzo=01;31:*.t7z=01;31:*.zip=01;31:*.z=01;31:*.dz=01;31:*.gz=01;31:*.lrz=01;31:*.lz=01;31:*.lzo=01;31:*.xz=01;31:*.zst=01;31:*.tzst=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.alz=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.cab=01;31:*.wim=01;31:*.swm=01;31:*.dwm=01;31:*.esd=01;31:*.jpg=01;35:*.jpeg=01;35:*.mjpg=01;35:*.mjpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.webp=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.ogv=01;35:*.ogx=01;35:*.aac=01;36:*.au=01;36:*.flac=01;36:*.m4a=01;36:*.mid=01;36:*.midi=01;36:*.mka=01;36:*.mp3=01;36:*.mpc=01;36:*.ogg=01;36:*.ra=01;36:*.wav=01;36:*.oga=01;36:*.opus=01;36:*.spx=01;36:*.xspf=01;36:
MAIL=/var/spool/mail/vondruch
PATH=/home/vondruch/.local/bin:/home/vondruch/bin:/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin
PS1=[\u@\h \W$(__git_ps1 " (%s)")]\$ 
PWD=/home/vondruch
QT_IM_MODULE=ibus
SESSION_MANAGER=local/unix:@/tmp/.ICE-unix/10457,unix/unix:/tmp/.ICE-unix/10457
SHELL=/bin/bash
SHLVL=0
SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
TERM=xterm-256color
USERNAME=vondruch
USER=vondruch
_=/usr/bin/env
VTE_VERSION=6201
WAYLAND_DISPLAY=wayland-0
XAUTHORITY=/run/user/1000/.mutter-Xwaylandauth.UHHMW0
XDG_CURRENT_DESKTOP=GNOME
XDG_DATA_DIRS=/home/vondruch/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share:/usr/share
XDG_MENU_PREFIX=gnome-
XDG_RUNTIME_DIR=/run/user/1000
XDG_SESSION_CLASS=user
XDG_SESSION_DESKTOP=gnome
XDG_SESSION_TYPE=wayland
XMODIFIERS=@im=ibus
~~~

So I'm not sure how this is happening but neither vulkaninfo or pidgin are loading the layer, I expect a bug in the vulkan loader or maybe the layer config file.

Working on this locally.

okay worked that bit out, but pidgin still dies, I expect this is two bugs, one in mesa layer and one in gstreamer.

Thank you for looking into this. Any news is good news.

FEDORA-2021-cd899639ab has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-cd899639ab

two bugs in mesa, one making the layer not work, and one in lavapipe exposing half an extensions that crashed pidgin.

Testing on Rawhide with, it resolves the issue. Thx for looking into this.

*** Bug 1912138 has been marked as a duplicate of this bug. ***

FEDORA-2021-cd899639ab has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-cd899639ab

FEDORA-2021-cd899639ab has been pushed to the Fedora 33 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-cd899639ab`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-cd899639ab

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

FEDORA-2021-cd899639ab has been pushed to the Fedora 33 stable repository.
If problem still persists, please make note of it in this bug report.