If an event is tagged with a category in web-UI I can see the category in event
description in client, but it doesn't appear under "categories" in event edit.

I have now look through the code paths in kdepim that interacts with ldap. We actually use kdepim/libkdepim/ldap/ldapclientsearch.* for getting seach relusts from ldap servers (incidenceeditor,resourcemanagement and addresslineedit).
ldapclientsearch reads the config by itself and is treiggered to reread it when the config file is changed.
it uses ldapclientsearchconfig to set a ldapserver settings with password:

Fixed by making the professional option implied for groups themselves as well.

With oanda import for proper country/currency I don't see a bug. Closing.

@machiak, please ensure to use the phrase "Resolves T1255" or "Closes T1225" to ensure the ticket is closed automatically.

Good call. If you do need further guidance, please provide a quick screen grab.

Fixed in 4b0a8e66a663

The above error message has nothing to do with synchronization but is being worked on in T1226

We currently have no information about any actual problems.

Logout and menu fixed. As for the login button, It wasn't present in the design. Should I just add another button similar to "Signup"?

This price depends on configured subscriptions. We need to find out what's wrong there.

Fix the URL for the Oanda site please.

Error 301 can be fixed simply by using https:// instead of http:// for Oanda site. However, it looks like that our request reach 30 seconds limit on their side. We need to do it in chunks.

Did you execute php bin/backend.php import_oanda after system currency change? The currencies are generated in system currency context, so this is required.

OTRS #1016876, assigned to mollekopf. There are more comments from user.

Maybe already fixed by T1206?

It's not so simple as I expected. First, on Kolab 16 I can't reproduce the issue. Second, if I snooze for 10 minutes an alarm for an event with -10 minutes alarm, I'll not see the alarm again at all. This one however, is caused by https://git.kolab.org/rRPK69d9d3b27f6cb0ef5d1e6a89a588af37ffb0bd7d, but it has other side effects.

• It would be good to have a valid ldapurl, just to make sure that kontact is creating the same.
• kdebugdialog enable kldap and retry and give us the log.

It sounds mostly like the settings to LDAP are not correct and that's why the password is not storred.

~ cat .kde/share/config/kabldaprc
[LDAP]
NumHosts=0
NumSelectedHosts=1
SelectedAuth0=Simple
SelectedBase0=dc=example,dc=org
SelectedBind0=uid=doe,ou=People,dc=example,dc=org
SelectedHost0=ldab.example.org
SelectedMech0=DIGEST-MD5
SelectedPageSize0=0
SelectedPort0=389
SelectedSecurity0=None
SelectedSizeLimit0=0
SelectedTimeLimit0=0
SelectedUser0=
SelectedVersion0=3
~

The problem is reproducable:

thanks for the tip, i just copy pasted your code which leads to one space too much

line 355 in /usr/lib/python2.7/site-packages/pykolab/xml/event.py is not properly idented. this forces wallace to die. check and correct identing.

There are responses in OTRS

Just a guess, maybe i cannot see log entries because wallace is unable to start?

OTRS #1100023
Requests for user comments should go there

OTRS #1100026
Requests for user comments should go there.

nothing.
changed warning to debug, did a complete reboot and i am still unable to see something in the log (from wallace)?
I get error messages to stout when do a kolabd --help (unicodeerror) or a kolab acl-cleanup (CYRUSError Mailbox does not exist) but i think they don´t belong into this discussion

This is quite complicated and here's a couple of bugs in Roundcube and Free-Busy.

OTRS #1100028, there are user comments on that.

In T1238#19147, @adomaitis wrote:

OTRS ticket #1016880. All requests for user comments should go there.

OTRS ticket #1016880. All requests for user comments should go there.

Can you please add a screenshot pf the password dialog. There are different dialogs, that ask for the password...
Can you chack if the password is stored in kwallet? (in ldapclient)
cat .kde/share/config/kabldaprc (replace password and host and everything else that is sensible data with fake data, but please mark the part that you replaced)

no lines in /var/log/kolab/pykolab.log ?

still unable to invite resources after this. Always get Undelivered Mail Returned to Sender...
I get no log entries in pykolab.log so i have no idea where to start searching

to those, who might be interested