Glib error gives Invalid byte sequence in conversion input

[m.rick@…]

I am not sure it is a Glib related error, but I have installed Glom in a new fresh installation and when I Stat it I get this error when i want to create a new brand new database file:

information for file '/Users/aymeric/Desktop/Nantes voirie/Nantes voirie.glom': 
Glib::ustring GlomBakery::get_file_display_name(const Glib::ustring &): uri=file:///Users/aymeric/Desktop/Nantes%20voirie/Nantes%20voirie.glom): error: Error when getting information for file '/Users/aymeric/Desktop/Nantes voirie/Nantes voirie.glom': 0
Glib::ustring GlomBakery::get_file_display_name(const Glib::ustring &): uri=file:///Users/aymeric/Desktop/Nantes%20voirie/Nantes%20voirie.glom): error: 
(<unknown>:81958): glibmm-CRITICAL **: 
unhandled exception (type Glib::Error) in signal handler:
domain: g_convert_error
code  : 1
what  : Invalid byte sequence in conversion input

It creates the database folder, but won't create the ~.glom file describing the database and it won't initialize the database and won't create the database configuration. I can create a database from the included examples and I can use already existing databases.

I didn't have it with previous versions.

I have a back-up of December and it does work well, while dbus, glib and glibmm libraries have the same versions… And the Glom binary is the same version as well. I made a packaged version of it (December) that works well too.

I installed Glom with the following steps:

1. port install gtk3 +quartz+python27
2. port install gtk2 +quartz+python27
3. port install libglade2 +quartz
4. port install py27-pygtk +quartz
5. port install avahi +gtk+gtk3+quartz+x11
6. port install libepc
7. port install libgda5 +db60+postgresql94+quartz
8. port install evince +quartz
9. port -f deactivate gtk3 @3.18.6_0+quartz
10. port install gtk3 +x11+python27
11. port install gcr
12. port -f deactivate gtk3 @3.18.6_0+x11
13. port activate gtk3 @3.18.6_0+quartz
14. port install glom +db60+postgresql94+quartz

[m.rick@…]

I have also discovered that the unworking version adds a slash after the name of the new database, like it was a path, it doesn't with the working version. Capture d’écran 2016-01-20 à 22.13.32.png​

It doesn't seem D-Bus related, because it happens wether D-Bus is running or not.