Created attachment 1494772 [details] Full gdb backtrace of gnome-music Description of problem: gnutls segfaults in gnutls_cipher_auth() when starting gnome-music (a python3 application) Version-Release number of selected component (if applicable): gnutls-3.6.4-2.fc29.x86_64 glib2-2.58.1-1.fc29.x86_64 glib-networking-2.58.0-2.fc29.x86_64 python3-3.7.0-9.fc29.x86_64 How reproducible: Steps to Reproduce: 1. Start gnome-music Actual results: Segmentation fault every time Expected results: gnome-music should start Additional info: Attaching a full backtrace
Thank you. I'm moving it to glib-networking as there seems to be something strange here and I may need Michael's help. The issue seems similar to: https://gitlab.gnome.org/GNOME/glib-networking/issues/12 and I'm pretty sure there was somewhere another related discussion. Could you try "thread apply all bt" for the backtrace and also: `dnf debuginfo-install gnutls glib-networking`?
btw. I could not reproduce. In my system gnome-music starts normally, however I have an empty db of files.
Created attachment 1494821 [details] Backtraces for all threads. Here is the backtraces for all the threads.
Thank you. I've sent a scratch-build of gnutls at: https://koji.fedoraproject.org/koji/taskinfo?taskID=30288246 When completed could you verify whether it addresses the issue?
Previous build failed. New link: https://koji.fedoraproject.org/koji/taskinfo?taskID=30288347
I downloaded the RPMs but they don't install. It seems gnutls-dane needs libunbound.so.2, but my F29 only has libunbound.so.7.
nm, dnf handled it better than rpm, but gnome-music still crashes. I'll attach a new backtrace collection.
Created attachment 1495169 [details] Backtraces with gnutls-3.6.4-3.fc29 installed.
Thank you Jonas. Indeed dnf will resolve dependencies better. What about this build: https://koji.fedoraproject.org/koji/taskinfo?taskID=30305397
The last build makes gnome-music start up without crashish!
..without *crashing* I mean of course
Thank you! I'll merge it with #1634736 *** This bug has been marked as a duplicate of bug 1634736 ***