D-Bus errors when using Wine in Docker, but not on the host

[Greelan]

Bug Report

System Information

• Ubuntu 20.04.4 (in LXD container)
• 2.3.3.4
• Mainline

I confirm:

• [x] that I have searched for an existing bug report for this issue.
• [x] that I am using the latest available version of AMP.
• [x] that my operating system is up-to-date.

Symptoms

When running a generic instance that uses Wine in Docker, the following error appears:

dbus[267]: arguments to dbus_connection_send_with_reply_and_block() were incorrect, assertion "connection != NULL" failed in file ../../../dbus/dbus-connection.c line 3544.
This is normally a bug in some application using the D-Bus library.
  D-Bus not built with -rdynamic so unable to print a backtrace
wine: Assertion failed at address 00007F9160675CE1 (thread 0023), starting debugger...

However, the same error does not appear when using Wine outside Docker (on the host).

Some research suggests it is 32 bit process related.

It seems Ubuntu has a patch or package to address the issue, but the Debian slim images used in AMP's Docker containers do not.

Any clue how this could be fixed?

Reproduction

• Run a generic instance that uses Wine in Docker and runs 32 bit processes (such as Carrier Command 2 or Assetto Corsa).
• Compare running the same instance outside Docker.

[Greelan]

And just for completeness, this is not an issue associated with the host being a LXD container. I get the same error when running AMP on an AWS VPS.

[PhonicUK]

Is this still an issue? A lot has changed since this was opened.

[IceOfWraith]

Yes it is, there's a snippet in #the-forest channel in Discord that shows it from today.

[Greelan]

Yes

[PhonicUK]

Is this still an issue on Wine 8?

[Greelan]

No