Package Details: onlyoffice-bin 8.0.1-1

Git Clone URL: https://aur.archlinux.org/onlyoffice-bin.git (read-only, click to copy)
Package Base: onlyoffice-bin
Description: An office suite that combines text, spreadsheet and presentation editors
Upstream URL: https://www.onlyoffice.com/
Licenses: AGPL-3.0-only
Conflicts: onlyoffice
Provides: onlyoffice
Submitter: mikalair
Maintainer: dbermond (Antiz)
Last Packager: dbermond
Votes: 206
Popularity: 8.25
First Submitted: 2016-11-17 12:33 (UTC)
Last Updated: 2024-02-26 15:55 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 .. 13 Next › Last »

dbermond commented on 2022-09-24 14:22 (UTC)

@YHNdnzj No, sorry. Configuring the Qt Platform Abstraction (QPA) is a user task, not a package task. We should not force a QPA plugin for all users, as this may not be suitable to everyone. See the Qt library part of the Wayland article on the ArchWiki.

YHNdnzj commented on 2022-09-24 12:21 (UTC)

Could you set QT_QPA_PLATFORM=xcb in /usr/bin/onlyoffice-desktopeditors? Currently it doesn't start under (X)Wayland when $QT_QPA_PLATFORM is globally set to "wayland".

sed -i '/exec $DIR\/DesktopEditors/iexport QT_QPA_PLATFORM=xcb' "${srcdir}/usr/bin/onlyoffice-desktopeditors"

dbermond commented on 2022-05-22 16:28 (UTC)

@simplepad The font dependencies are taken from upstream packaging. We better use it here in the exact way provided by upstream to avoid any problems.

simplepad commented on 2022-05-21 00:36 (UTC) (edited on 2022-05-21 00:39 (UTC) by simplepad)

Are all the ttf font dependecies really necessary? Could you please make them optional or replace them with one general ttf-font?

AERY commented on 2022-01-14 15:45 (UTC)

Is there someone else who gets "Segmentation fault (core dumped)"? I don't know why I am getting this error, it won't let me launch the program. Is there a way to fix this, or should the package itself be fixed?

MithicSpirit commented on 2021-10-02 20:09 (UTC)

@dbermond huh I didn't know that; you live and you learn ig. Thank you.

dbermond commented on 2021-10-02 19:39 (UTC)

@MithicSpirit symbolic links on a package should use relative paths, unless some exception applies. Change the symlinks to absolute paths and you will see that namcap warns about it.

MithicSpirit commented on 2021-10-02 19:28 (UTC)

It would be preferable to have the symlinks in lines 40 and 46 use absolute paths rather than relative paths (i.e. start with / rather than a series of ../s).

torculus commented on 2021-09-11 10:55 (UTC)

The "out of date" flag is incorrect - there is no version 6.4 release yet on Github

« First ‹ Previous 1 2 3 4 5 6 7 8 .. 13 Next › Last »