Bug #129

avatar

configuration error dialog [win32]

Added by Mirco Bauer 5679 days ago. Updated 5372 days ago.

Status:Closed Start:
Priority:Urgent Due date:
Assigned to:avatarMirco Bauer % Done:

100%

Category:Frontend GNOME
Target version:0.6.4
Complexity:

Found in Version:

Votes: 0

Description

When starting smuxi on windows, you get an error dialog (which can only be closed when you are in the main window) saying:
An error occurred while loading or saving configuration information for smuxi. Some of your configuration settings may not work properly.
Message details:
Failed to launch configuration server: Failed to execute child process (No such file or directory)

Failed to launch configuration server: Failed to execute child process (No such file or directory)

Failed to launch configuration server: Failed to execute child process (No such file or directory)

Failed to launch configuration server: Failed to execute child process (No such file or directory)

This is because smuxi is a GNOME application and the GNOME libs try to initialize gconf which is somehow not working correctly (possibly a missing file).


Related issues

blocked by Smuxi - Feature #63 replace GNOME# API calls with GTK# API Closed

History

Updated by Mirco Bauer 5679 days ago

avatar

The dialog can be closed though and the application contains without errors as smuxi doesn't use gconf!

Updated by Mirco Bauer 5679 days ago

avatar

Looks like GNOME tries to connect to gconfd at startup. Supplying gconfd-2.exe and lib\GConf\2\libgconfbackend-xml.dll seems to fix this issue. But gconfd-2.exe needs to be spawned before starting smuxi (which is ugly, double ugly for dos window). So either I need to ship those + a startup script or convince GNOME to not use gconf at all.

Updated by Mirco Bauer 5593 days ago

avatar

postponed to 0.7 where this issue will be fixed by itself when dropping the GNOME# usage, see ticket #63

Updated by Mirco Bauer 5445 days ago

avatar
  • Target version changed from 0.8 to 0.6.4

Updated by Mirco Bauer 5372 days ago

avatar
  • Status changed from New to Closed
  • % Done changed from 0 to 100

As the feature/#63_drop_gnome-sharp branch is now merge with master, gconfd is not needed anymore and thus this problem goes away with it! :-)

Also available in: Atom PDF