apport-gtk crashed with SIGSEGV in _gtk_settings_get_screen(settings=0x0) from gtk_css_value_icon_theme_compute() from gtk_css_static_style_compute_value()

StacktraceTop:
 _gtk_settings_get_screen (settings=0x0) at ../../../../gtk/gtksettings.c:3319
 gtk_css_value_icon_theme_compute (icon_theme=<optimized out>, property_id=<optimized out>, provider=<optimized out>, style=<optimized out>, parent_style=<optimized out>) at ../../../../gtk/gtkcssiconthemevalue.c:84
 gtk_css_static_style_compute_value (style=0x1e7c320, provider=0x0, parent_style=0x0, id=3, specified=0x7f53258b9b20 <inherit>, section=0x0) at ../../../../gtk/gtkcssstaticstyle.c:237
 _gtk_css_lookup_resolve (lookup=lookup@entry=0x1e7e790, provider=provider@entry=0x0, style=style@entry=0x1e7c320, parent_style=parent_style@entry=0x0) at ../../../../gtk/gtkcsslookup.c:122
 gtk_css_static_style_new_compute (provider=provider@entry=0x0, matcher=matcher@entry=0x0, parent=parent@entry=0x0) at ../../../../gtk/gtkcssstaticstyle.c:195

Status changed to 'Confirmed' because the bug affects multiple users.

Tracking in: https://errors.ubuntu.com/problem/815a179408135a894bbb5921adef3757563c75c5

Looking at the stack trace, there is pygi_callable_info_invoke (source: pygobject) -> pygi_invoke_c_callable (source: pygobject) -> gtk_builder_add_from_file (source: gtk+3.0) -> _gtk_settings_get_screen (source: gtk+3.0)

To fix this bug in apport, gtk_builder_add_from_file should raise an Exception. So I mark gtk+3.0 as affected.

Status changed to 'Confirmed' because the bug affects multiple users.

More duplicate bug reports: bug #1988982 and bug #1989036.

the stacktrace is similar to https://gitlab.gnome.org/GNOME/gtk/-/issues/3310

Investigated this, it is due to the theming code failing to get a settings object, probably due to the shell not running at the time. The GTK functions that return the settings object are allowed to return NULL, and this case was not being handled in GTK. The attached patch contains three fixes in GTK to handle these cases. These cases were found by forcing the settings object to be NULL and then running a test program and fixing the segfaults.

Applied the patch to the package and re-run test case (killall -11 gnome-shell), but apport still crashed. See attached _usr_share_apport_apport-gtk.1000.crash.

Print-line debugging shows that the Python code for that crash is in GTKUserInterface.__init__:

```
    self.widgets.add_from_file(
        os.path.join(os.path.dirname(argv[0]), "apport-gtk.ui")
    )
```

Are there any updates on this issue?
My Ubuntu 22.04 is crashing on daily basis :-(

@bdrung - Speaking to the desktop team they indicated apport should catch the error and work around the issue given that a gtk fix isn't forthcoming.

Sadly you cannot catch a C library segfault within Python code.

Clarifying from a Desktop perspective. Upstream isn't going to care about the issue because GTK3 isn't actively maintained at this point and it's not a 'real world issue' in the sense of it's an error that is hit when the session closes in an unprompted manner, which means no user would see a visible consequence if it wasn't the crash handler catching it.

It's a situation that should ideally be resolved and Robert tried to fix it but the patch needs more work and it's lower priority than other items so we didn't get to investigate more yet.

One other way would be to teach apport to ignore issues on session closing (which I think was done some years ago but maybe that isn't working anymore?)

Apport is written in Python and uses try-except, but it does not catch segmentation faults.

Dear @Sebastien Bacher (seb128)

It isn't true that it isn't 'real world issue' (at least in my case). My Ubuntu 22.04 is randomly crashing (approximately once per day), all applications are closed and systems go to the login screen. During the crash time, I'm losing all my work, so it is seriously touching my daily tasks.
Due to the above, I will be appreciated, if someone will fix the bug.

Best regards,
Andrzej

@Andrzej, right, but the issue is that your session is closing and that's a probably in a key component as the shell, session manager and graphical server. Resolving the fact that 'ubuntu-bug', the bug report helper is being hit by the session closing would not solve your issue. You should for other .crash reports on your system and probably submit those