Crash when enabling dbus access for address book access on flathub app

The flathub app crashes shortly after launching the app when enabling dbus access for the app. And if not enabling this access there are errors accessing the address books and a crash of the app when the user tries to access any address book.
with dbus access enabled:

```
Mai 07 14:07:40 username systemd[1889]: Started app-flatpak-org.tabos.roger-1685029.scope.
Mai 07 14:07:40 username systemd[1889]: Started app-gnome-org.tabos.roger-1685029.scope - Application launched by gnome-shell.
Mai 07 14:07:46 username kernel: pool-Roger Rout[1685074]: segfault at 778b84cf00a4 ip 000057057bdcd023 sp 0000778cf894cb00 error 4 in roger[1e023,57057bdbf000+15000] likely on CPU 2 (core 2, socket 0)
```
app crashes

without dbus access:

```
Mai 07 14:21:15 username systemd[1889]: Started app-flatpak-org.tabos.roger-1686996.scope.
Mai 07 14:21:15 username systemd[1889]: Started app-gnome-org.tabos.roger-1686996.scope - Application launched by gnome-shell.
Mai 07 14:21:19 username roger[1687009]: Error finishing client connection. Error: Unable to connect to “Address Book”: org.freedesktop.DBus.Error.ServiceUnknown
```

app crashes if user tries to access address books:

```
Mai 07 14:26:42 username kernel: pool-Roger Rout[1687334]: segfault at 98 ip 00005c201287b023 sp 000070bb5f270b00 error 4 in roger[1e023,5c201286d000+15000] likely on CPU 7 (core 1, socket 0)
Mai 07 14:26:42 username systemd[1889]: app-gnome-org.tabos.roger-1686996.scope: Consumed 2.769s CPU time.
```

I would guess the flathub app needs dbus access? But then crashes anyway when accessing the address books?

ubuntu 24.04, recently updated
6 core 12 thread AMD 5600G, 16GB RAM, at least 50% free
user is in fax group
printer was being installed
TR64 is activated on 7490
CAPI and signalling was activated on 7490
UPnP was activated on 7490
a user was created for access to 7490 with access rights to "Sprachnachrichten, Faxnachrichten, FRITZ!App Fon und Anrufliste"
access for rogerrouter app as flathub app is granted via the app flatseal

to recreate the issue, follow these steps:

1) journalctl --follow | grep roger
```
Mai 07 14:59:23 username sudo[1691058]: username : TTY=pts/1 ; PWD=/home/username ; USER=root ; COMMAND=/usr/bin/flatpak-coredumpctl org.tabos.roger
Mai 07 15:01:06 username systemd[1889]: Started app-flatpak-org.tabos.roger-1692063.scope.
Mai 07 15:01:12 username systemd[1889]: Started app-flatpak-org.tabos.roger-1692080.scope.
Mai 07 15:01:18 username kernel: pool-Roger Rout[1692121]: segfault at 7d4a74df92a1 ip 00005a790b710023 sp 00007d4d8aa6fb00 error 4 in roger[1e023,5a790b702000+15000] likely on CPU 5 (core 5, socket 0)
Mai 07 15:01:18 username systemd-coredump[1692124]: Process 1692092 (roger) of user 1000 dumped core.
#0 0x00005a790b710023 n/a (/app/bin/roger + 0x1e023)
```

2) flatpak run org.tabos.roger
(starting it with --gtk-debug=yes argument changes nothing) (starting it with argument -d does not work at all)

3) flatpak-coredumpctl org.tabos.roger
```
xecutable /app/bin/roger doesn't seem to be a flatpaked application.
Running: `"flatpak" "run" "--filesystem=home" "--filesystem=/tmp" "--command=gdb" "--devel" "org.tabos.roger" "/app/bin/roger" "/tmp/tmpzvzz4dip"`
Fehler: runtime/org.gnome.Sdk/x86_64/46 ist nicht installiert
Traceback (most recent call last):
File "/usr/bin/flatpak-coredumpctl", line 83, in
coredumper.run()
File "/usr/bin/flatpak-coredumpctl", line 58, in run
subprocess.check_call(flatpak_command)
File "/usr/lib/python3.12/subprocess.py", line 413, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['flatpak', 'run', '--filesystem=home', '--filesystem=/tmp', '--command=gdb', '--devel', 'org.tabos.roger', '/app/bin/roger', '/tmp/tmpzvzz4dip']' returned non-zero exit status 1.
```

Reproduce the crash with `flatpak run org.tabos.roger`, testing both DBus-enabled and restricted access, and inspect `/app/bin/roger` through `flatpak-coredumpctl`. The reported command currently cannot run because the GNOME 46 SDK is missing; done means identifying the segfault cause and preventing crashes while preserving address-book access.

Written by the indexing model from the issue text.