1

When mounting an SSD encrypted with VeraCrypt on Ubuntu 24.04, I get the following alerts:

# veracrypt /dev/sda2 /mnt/crucial

** (veracrypt:18207): WARNING **: 19:02:42.514: Unable to connect to dbus: The connection is closed

(veracrypt:18207): GLib-GIO-CRITICAL **: 19:02:42.627: g_dbus_connection_register_object: assertion 'G_IS_DBUS_CONNECTION (connection)' failed

(veracrypt:18207): GLib-GIO-CRITICAL **: 19:02:42.627: g_dbus_connection_register_object: assertion 'G_IS_DBUS_CONNECTION (connection)' failed

(veracrypt:18207): GLib-GIO-CRITICAL **: 19:02:42.627: g_dbus_connection_get_unique_name: assertion 'G_IS_DBUS_CONNECTION (connection)' failed

(veracrypt:18207): GLib-GIO-CRITICAL **: 19:03:11.816: g_dbus_connection_register_object: assertion 'G_IS_DBUS_CONNECTION (connection)' failed

(veracrypt:18207): GLib-GIO-CRITICAL **: 19:03:11.816: g_dbus_connection_register_object: assertion 'G_IS_DBUS_CONNECTION (connection)' failed

(veracrypt:18207): GLib-GIO-CRITICAL **: 19:03:11.816: g_dbus_connection_get_unique_name: assertion 'G_IS_DBUS_CONNECTION (connection)' failed

(veracrypt:18207): GLib-GIO-CRITICAL **: 19:03:13.685: g_dbus_connection_register_object: assertion 'G_IS_DBUS_CONNECTION (connection)' failed

(veracrypt:18207): GLib-GIO-CRITICAL **: 19:03:13.685: g_dbus_connection_register_object: assertion 'G_IS_DBUS_CONNECTION (connection)' failed

(veracrypt:18207): GLib-GIO-CRITICAL **: 19:03:13.685: g_dbus_connection_get_unique_name: assertion 'G_IS_DBUS_CONNECTION (connection)' failed

The partition mounts successfully, but the same errors occur even if I only want to display the VeraCrypt version:

# veracrypt --version

** (veracrypt:52318): WARNING **: 21:10:33.650: Unable to connect to dbus: The connection is closed

(veracrypt:52318): GLib-GIO-CRITICAL **: 21:10:34.235: g_dbus_connection_register_object: assertion 'G_IS_DBUS_CONNECTION (connection)' failed

(veracrypt:52318): GLib-GIO-CRITICAL **: 21:10:34.235: g_dbus_connection_register_object: assertion 'G_IS_DBUS_CONNECTION (connection)' failed

(veracrypt:52318): GLib-GIO-CRITICAL **: 21:10:34.235: g_dbus_connection_get_unique_name: assertion 'G_IS_DBUS_CONNECTION (connection)' failed

DBus activates correctly without errors.

On a second Ubuntu 24.04 system on another PC with the same SSD, there are no error messages.

Any idea how to solve this?

Improve this question
1
  • If it works as expected the "critical" errors reported aren't that critical at the end of day. As far as I can remember I never used it in commands. Tried just now, just veracrypt and got 2 different errors: g_value_set_boxed: assertion 'G_VALUE_HOLDS_BOXED (value)' failed... Commented Aug 15 at 14:39

0

Reset to default

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.