This is the multi-page printable view of this section. Click here to print.
Good to know
1 - Client Logs
Client Logs
If the client throws up errors, it is often helpful if you can send logs to the support team in which the client perhaps provides a little more information about what exactly went wrong.
By default, the client does not collect any logs. In newer desktop clients, you can configure the logs by pressing the F12 key; this menu also shows where the logs are located, and you can open the corresponding folder.
2 - Expiration and Deletion Dates
| Action | Acoount-Type | Date |
|---|---|---|
| account block | regular | last login date + 12 months |
| account deletion | regular | date of account block + 6 months |
| account block | guest | last login date + 12 months |
| account deletion | guest | date of account block + 30 days |
| account block | project box | last login date + 24 months |
| account deletion | project box | date of account block + 6 months |
3 - Known Bugs
Desktop client auto updater not working
The desktop client has an auto-updater which should ensure that the latest version is always installed. However, in some cases this mechanism does not work, so that older version remain installed. Currently (November 2024), version 5.3.1 should be distributed. If you still have an older version, you should update the client manually by downloading and installing the new version from {< rawhtml >}www.sciebo.de{< /rawhtml >}.
Problems with updates of the desktop client under Linux
Sporadically, there may be problems with the client signatures. If ‘apt update’ says something about ‘invalid signature’, it may be worth following the tips described in {< rawhtml >}this GitHub issue {< /rawhtml >}.
Linux desktop client no longer starts
If the desktop client displays the following error message
qt.qpa.plugin: Could not load the Qt platform plugin “xcb” in “” even though it was found. This application failed to start because no Qt platform plugin could be initialised. Reinstalling the application may fix this problem.
It is possible that the environment variable LD_LIBRARY_PATH=/usr/lib/x86_64-linux-gnu is set. In this case, it may be
helpful to change the environment variable to: env LD_LIBRARY_PATH="/opt/ownCloud/qt-5.15.2/lib/x86_64-linux-gnu/qt5/plugins/platforms" sciebo.
Sharing: An user cannot be found
This is only partially a bug and is therefore difficult to fix. There are several reasons why a person cannot be found when sharing in sciebo:
- The person does not have a sciebo account
- The person has never logged into his sciebo account
- Instead of the sciebo account ID, the email address was entered (these do not have to be identical)
- The syntax ‘surname, first name’ does not work because the person has chosen in the settings not to be found using this syntax or has registered only one day ago
- You made a typo when entering the identifier, waited a moment, triggered the search and corrected the identifier while it was still running. Tip: Enter the identifier using copy&paste
4 - Permissions
We have not yet translated this page. For the german page, click here
5 - Who owns the data?
Generally we differentiate between two types of accounts:
- personal accounts
- project boxes
Personal Accounts
The situation for personal accounts is obvious: The data is owned by the person that owns the account.
When a person shares a file with you from their personal account, you will have access to this file temporarily, but you do not own it. If the person stops sharing their file with you or their account is deleted, access to the data is lost.
In this case we cannot recover your access to the file.
Project Boxes
In project boxes the institution or the registered project owns the data. If the person who created the project box stops working for the project or institution, their collegues can talk to the support and take over the project box.
Handling of business documents
Regulation of the handling of business documents is governend by the participating institutes. There can be made no distinction between the personal space in sciebo and private storage devices. For files which are not allowed to be saved on private devices, but should be accessible in sciebo, project boxes can be used. A good description and attribution to the working group in the project box appliction can here help ease the support of certain issues in the future, e.g. when people leave the institute.