Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 872113

Summary: app-crypt/seahorse-42.0: segfault
Product: Gentoo Linux Reporter: Randall <ran.dall>
Component: Current packagesAssignee: Gentoo Linux Gnome Desktop Team <gnome>
Status: UNCONFIRMED ---    
Severity: normal    
Priority: Normal    
Version: unspecified   
Hardware: All   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---
Attachments: backtrace
emerge --info app-crypt/seahorse
full bt

Description Randall 2022-09-21 01:37:46 UTC
I got this SEGFAULT today and couldn't find much about it on my own or on Google.

Reproducible: Always
Comment 1 Randall 2022-09-21 01:38:22 UTC
Created attachment 813175 [details]
backtrace
Comment 2 Randall 2022-09-21 01:40:03 UTC
Created attachment 813178 [details]
emerge --info app-crypt/seahorse
Comment 3 Randall 2022-09-21 01:40:44 UTC
/var/tmp/portage/x11-libs/gtk+-3.24.34/work/gtk+-3.24.34/gtk/gtkwidgetprivate.h: No such file or directory.

This seems to be the issue.
Comment 4 Sam James archtester Gentoo Infrastructure gentoo-dev Security 2022-09-21 01:44:10 UTC
That's just a warning about gtk+ sources being missing for the backtrace, so ignore the missing .h thing.

Core was generated by `/usr/bin/seahorse --gapplication-service'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x00007f437e1c8379 in _gtk_widget_get_toplevel (widget=0x55bfe1906430) at /var/tmp/portage/x11-libs/gtk+-3.24.34/work/gtk+-3.24.34/gtk/gtkwidgetprivate.h:382
[Current thread is 1 (Thread 0x7f437903c200 (LWP 28587))]

If you type 'bt', is there no other info there?
Comment 5 Randall 2022-09-21 01:46:51 UTC
Created attachment 813181 [details]
full bt

I've uploaded the full backtrace.
Comment 6 Sam James archtester Gentoo Infrastructure gentoo-dev Security 2022-09-21 01:52:53 UTC
Thanks. You can wait for gnome@ to comment but I'd probably just report this upstream at https://gitlab.gnome.org/GNOME/seahorse/-/issues.

But I would try using calmer cflags for Seahorse and gtk+ and other GNOME libraries mentioned in the backtrace first, to see if that helps, and narrow down the problematic flag if related. Try -O2 for each of them first, see if it still happens, then work your way up.
Comment 7 Randall 2022-09-21 02:25:38 UTC
> Thanks. You can wait for gnome@ to comment but I'd probably just report this upstream at https://gitlab.gnome.org/GNOME/seahorse/-/issues.

https://gitlab.gnome.org/GNOME/seahorse/-/issues/356

> But I would try using calmer cflags for Seahorse and gtk+ and other GNOME libraries mentioned in the backtrace first, to see if that helps, and narrow down the problematic flag if related. Try -O2 for each of them first, see if it still happens, then work your way up.

That's an excellent idea. I'll try that tomorrow.