mira-dev team mailing list archive

[Max Bossino <688792@xxxxxxxxxxxxxxxxxx>]

The output of Mira Client and Server up to the failed connection stage
is as follows:

Mira Client:
-----
$ ./mira_client 
FilesUtility Loaded
127.0.0.1
adding to buffer...
OUT: L test as
bytes_transferred: 20
IN: E L Bad Credentials
-----

Mira Server:
-----
$ ./mira_server 
This server has UUID: 69bad5cf-7262-4eb3-a218-a5262b9403de
ret_val in MiraUtility::utility_data_directory is: /opt/mira/69bad5cf-7262-4eb3-a218-a5262b9403de
UtilityManager(): /opt/mira/69bad5cf-7262-4eb3-a218-a5262b9403de/Utilities
Lib name: Files
Dynamically opened library....
Loaded function pointers....
Loaded Files Utility
ret_val in MiraUtility::utility_data_directory is: /opt/mira/69bad5cf-7262-4eb3-a218-a5262b9403de
Running File Server
Running File Server loop
Accepted connection from: 127.0.0.1
bytes_transferred: 10
IN: L test as
[OUT]: E L Bad Credentials
OUT: E L Bad Credentials
-----

-- 
You received this bug notification because you are a member of Mira Core
Development Team, which is subscribed to Mira Groupware.
https://bugs.launchpad.net/bugs/688792

Title:
  New User action disabled after trying to Connect to a Server