Ubuntu
seahorse package

Unable to launch seahorse

Bug #1843895 reported by Olivier Febwin
18
This bug affects 4 people
Affects Status Importance Assigned to Milestone
seahorse (Ubuntu)
Incomplete
Low
Unassigned

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

Revision history for this message
Olivier Febwin (febcrash) wrote :

This issue occurs only on Xorg session (ubuntu 19.04).
No problem on Wayland session.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

Before using gdb do '$ export GDK_SYNCHRONIZE=1'

What version of Ubuntu are you using

no longer affects: xorg (Ubuntu)
Changed in seahorse (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Olivier Febwin (febcrash) wrote :

This issue occurs only on Xorg session (ubuntu 19.04).
No problem on Wayland session.

Revision history for this message
Sebastien Bacher (seb128) wrote :

it looks similar to taht upstream report, https://gitlab.gnome.org/GNOME/seahorse/issues/228

Revision history for this message
zwigno (zwigno) wrote :

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.

Revision history for this message
joncamfield (jon-camfield) wrote :

This also impacts other stores (mine only crashes when I switch to GPG keys).

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.