If this helps, I can prevent it from crashing if I use GTK_DEBUG=no- pixel-cache OR GDK_RENDERING=recording with some caveats.
GDK_RENDERING=recording works but has lots of rendering artifacts. GDK_RENDERING=image does not crash but Passwords/Login does not render. Certificates/Secure Shell/PGP Keys render fine. If I use GTK_DEBUG=no-pixel-cache everything seems to work properly. I agree with the link above that it seems related to the number of passwords in the Login store. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/1843895 Title: Unable to launch seahorse Status in seahorse package in Ubuntu: Incomplete Bug description: When I try to run seahorse, I've these errors: (seahorse:11732): Gdk-ERROR **: 14:45:20.702: The program 'seahorse' received an X Window System error. This probably reflects a bug in the program. The error was 'BadAlloc (insufficient resources for operation)'. (Details: serial 1008 error_code 11 request_code 130 (MIT-SHM) minor_code 5) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Trappe pour point d'arrêt et de trace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1843895/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
