Categories

• Announcements

  New releases are announced here! If you have any feedback to a specific version, feel free to reply to these topics.

  Final releases

  Alpha, beta and RC releases
  200
  Topics
  684
  Posts

  

  Hi @amaccuish, there have been some fixes and also more logging. Please update to the latest master branch version. @june @white-eagle thanks for reporting the umlaut issue. Unfortunately I didn’t have time to debug it more extensively yet. Manfred
• General Discussion

  A place to talk about whatever you want

  Development

  Projects
  174
  Topics
  792
  Posts

  

  I am agreeing that you don’t have to specify defaults any more as they are built in. That is why mine is commented out. It just seems strange that kopano-server and kopano-dbadm do not recognise the same set of defaults. I would have thought it was a bug.
• Kopano Groupware Core
  926
  Topics
  5807
  Posts

  

  Thanks! a note is the INSTALL should be sufficient then. ;-)
• Kopano WebApp

  Plugins for Kopano WebApp
  577
  Topics
  2902
  Posts

  

  Hi Walter, yes, you’re right. I think I must have had “tomatoes on my eyes”. ;-) Thanks!
• Kopano DeskApp
  160
  Topics
  715
  Posts

  

  Hi marty, thanks for the quick response! So I do not need to do further testing, just have to wait for the fix… ;-)
• Synchronising (mobile) devices via Z-Push

  General usage of Z-Push

  Z-Push when using Kopano

  Z-Push when using other backends
  415
  Topics
  2845
  Posts

  

  @divB said in Suffering from sync loops: Try a different mail app. i have seen simular things on android. due to… i still have one zarafa 6.30 running with an old z-push. I also notice with some apps, that if they have a mail and contacts and callendar, you need to install all of the same supplier. 0x8004010F - code: 12, if its the same as on a real exchange, disable GAB in z-push is worth a try. or create one that the use can access. if in the mail app, an option exist about offline adress books, disable it. A few suggestion you could try, to keep it running, but upgrading is the best option.
• Kopano OL Extension (KOE)
  148
  Topics
  859
  Posts

  

  Solved!!! No it works over the ol-extension installed at Outlook. Perfect! Thanks!
• Kopano Meet & WebMeetings
  47
  Topics
  243
  Posts

  

  Thanks for the report. Fixed in https://stash.kopano.io/projects/KWM/repos/kwmserver/commits/d0411f38fa1cb9dd9f6f8e9b1289518e1d7b3323 and will be in the next release.
• Kopano Mattermost

  For questions around the Mattermost packages provided by Kopano.

  16
  Topics
  87
  Posts

  

  @_r9 thanks for sharing. The documentation I was referring to was the included Apache vhost in our Mattermost packages, but since you’re running in Docker you are probably not using these. These had already something quite similar to your code, except it used a header edit. But on the other hand since we both consulted the same apache documentation it also had the same unset.
• LibreOffice Online, Kopano Documents Editor and Kopano Documents

  Section for questions around LibreOffice Online, Kopano Documents Editor and Kopano Documents

  6
  Topics
  23
  Posts

  

  Dear all, I have installed Kopano LibreOffice Online from the repository on Devuan 9.0 (ascii), which is Debian without systemd in a privileged LXC container. Installation was without problems. Since I cannot use the systemd-start script, I tried to start loolwsd for testing purposes manually with the command inside the systemd script: sudo -u lool /usr/bin/loolwsd --version --o:sys_template_path=/opt/lool/systemplate --o:lo_template_path=/opt/libreoffice5.4 --o:child_root_path=/opt/lool/child-roots --o:file_server_root_path=/usr/share/libreoffice-online Unfortunately I get the following errors: wsd-07041-07041 12:48:17.639901 [ loolwsd ] WRN SSL support: SSL is disabled.| wsd/LOOLWSD.cpp:748 loolforkit version details: 5.4.2 - 5.4.2 frk-07043-07043 12:48:19.141299 [ forkit ] FTL Capability cap_sys_chroot is not set for the loolforkit program.| kit/ForKit.cpp:155 frk-07043-07043 12:48:19.141482 [ forkit ] FTL Capability cap_mknod is not set for the loolforkit program.| kit/ForKit.cpp:155 frk-07043-07043 12:48:19.142047 [ forkit ] FTL Capability cap_fowner is not set for the loolforkit program.| kit/ForKit.cpp:155 FATAL: Capabilities are not set for the loolforkit program. Please make sure that the current partition was *not* mounted with the 'nosuid' option. If you are on SLES11, please set 'file_caps=1' as kernel boot option. frk-07043-07043 12:48:19.142346 [ forkit ] WRN Waking up dead poll thread [delay_poll], started: false, finished: false| net/Socket.hpp:505 frk-07043-07043 12:48:19.142585 [ forkit ] WRN Waking up dead poll thread [delay_poll], started: false, finished: false| net/Socket.hpp:505 wsd-07041-07041 12:49:09.068082 [ loolwsd ] FTL Failed to fork child processes.| wsd/LOOLWSD.cpp:2515 FATAL: Failed to fork child processes. wsd-07041-07041 12:49:09.068942 [ loolwsd ] FTL Failed to fork child processes.| wsd/LOOLWSD.cpp:2661 Failed to fork child processes. wsd-07041-07041 12:49:09.069593 [ loolwsd ] WRN Waking up dead poll thread [admin], started: false, finished: false| ./net/Socket.hpp:505 wsd-07041-07041 12:49:09.069804 [ loolwsd ] WRN Waking up dead poll thread [admin], started: false, finished: false| ./net/Socket.hpp:505 wsd-07041-07041 12:49:09.070056 [ loolwsd ] WRN Waking up dead poll thread [delay_poll], started: false, finished: false| ./net/Socket.hpp:505 wsd-07041-07041 12:49:09.070233 [ loolwsd ] WRN Waking up dead poll thread [delay_poll], started: false, finished: false| ./net/Socket.hpp:505 <shutdown>-07041 12:49:09.077471 [ loolwsd ] WRN Waking up dead poll thread [accept_poll], started: false, finished: false| ./net/Socket.hpp:505 <shutdown>-07041 12:49:09.077730 [ loolwsd ] WRN Waking up dead poll thread [accept_poll], started: false, finished: false| ./net/Socket.hpp:505 <shutdown>-07041 12:49:09.077868 [ loolwsd ] WRN Waking up dead poll thread [websrv_poll], started: false, finished: false| ./net/Socket.hpp:505 <shutdown>-07041 12:49:09.077949 [ loolwsd ] WRN Waking up dead poll thread [websrv_poll], started: false, finished: false| ./net/Socket.hpp:505 <shutdown>-07041 12:49:09.078018 [ loolwsd ] WRN Waking up dead poll thread [accept_poll], started: false, finished: false| ./net/Socket.hpp:505 <shutdown>-07041 12:49:09.078089 [ loolwsd ] WRN Waking up dead poll thread [accept_poll], started: false, finished: false| ./net/Socket.hpp:505 <shutdown>-07041 12:49:09.078730 [ loolwsd ] WRN Waking up dead poll thread [websrv_poll], started: false, finished: false| ./net/Socket.hpp:505 <shutdown>-07041 12:49:09.078828 [ loolwsd ] WRN Waking up dead poll thread [websrv_poll], started: false, finished: false| ./net/Socket.hpp:505 The first line is because I have disable SSL according to the documentation. I have also confirmed that the filesystem supports suid. I have added the suggested option to grub.cfg: linux /boot/vmlinuz root=PARTUUID=ea0b2a87-02 rootfstype=ext4 rootwait acpi_enforce_resources=lax file_caps=1 console=tty0 console=ttyS0,115200n8 noinitrd Any idea what I can do to solve this error?
• Other Clients
  43
  Topics
  217
  Posts

  

  Thanks for the information. I give this to us dev.
• Development

  Section about Kopano development. Home for talk about contributing, plugins and scripting.

  Contributing

  Scripting

  Translating Kopano

  WebApp & Plugins
  46
  Topics
  203
  Posts

  

  Sorry, this was in deed a stupid question. It is simple as that: server = kopano.Server(auth_user='userXY') for f in server.public_store: print(f)
• Legacy software

  Questions about Zarafa software

  31
  Topics
  160
  Posts

  

  HI @Coffee_is_life , I guess you are right :) didn’t noticed it. maybe it is a good idea to use your brain while fiddeling around with something unknown. but thats what testing system are for… In the end I maybe just slapcat the ldif file and afterwards sed ZARAFA and zarafa to kopano/KOPANO. btw. @fbartels I got a little problem the script further down too: grep: /usr/share/doc/packages/zarafa/zarafa.schema: Datei oder Verzeichnis nicht gefunden even more interesting I found the schema here: /usr/share/doc/zarafa/zarafa.schema.gz this is all a bit confusing, since I 've got no decent experience with ldap. But I haven’t broken it it, so there is still hope :) is it possible that there “extra informations” like ZARAFAQUOTAWARN where only used the yaffas and not zarafa itself? like you already said maybe I shouldn’t care so much about these schemas and just migrate and use it :) greetings 1of16