/usr/share/apport/apport-gtk:AttributeError:on_show_details_clicked:ui_update_view

[errors.ubuntu.com bug bridge]

```
Traceback (most recent call last):
  File "/usr/share/apport/apport-gtk", line 576, in on_show_details_clicked
    self.ui_update_view(['ExecutablePath'])
  File "/usr/share/apport/apport-gtk", line 130, in ui_update_view
    not self.report._is_binary(self.report[key]):
AttributeError: 'Report' object has no attribute '_is_binary'
```

The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.28.1-0ubuntu3.3, the problem page at https://errors.ubuntu.com/problem/59f5d6210b0c3768c7347bef75839806b09896f0 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/.

[Benjamin Drung (bdrung)]

Commit 6c946206e512609b7fb0fd2661bcd497a1295a2c ("Make ProblemReport.is_binary a public method") renamed the method. This commit is part of Apport 2.23.0. Following package combination can explain the stack trace:

* apport-gtk 2.20.11-0ubuntu82.6
* python3-apport 2.28.1-0ubuntu2

We already have a breakage declared:

```
Package: python3-apport
Breaks: apport (<< 2.23.1), apport-gtk (<< 2.23.1), apport-kde (<< 2.23.1)

Package: apport-gtk
Depends: python3-apport (>= ${source:Version})
```

See bug #1997759

[Benjamin Drung (bdrung)]

I would only expect this kind of crash during dist-upgrade between jammy and noble, but that could not explain cases like https://errors.ubuntu.com/oops/49f12b97-fcc9-11ef-b312-fa163ec8ca8c that say " Upgraded to noble on 2025-01-01 (66 days ago)"