Package Details: softmaker-office-2018-bin 2018.982-1

Git Clone URL: https://aur.archlinux.org/softmaker-office-2018-bin.git (read-only, click to copy)
Package Base: softmaker-office-2018-bin
Description: Proprietary office suite; word processing, spreadsheets, presentations
Upstream URL: https://www.softmaker.com
Licenses: custom
Submitter: WorMzy
Maintainer: WorMzy
Last Packager: WorMzy
Votes: 15
Popularity: 0.000000
First Submitted: 2017-12-08 14:36 (UTC)
Last Updated: 2021-02-15 14:26 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 Next › Last »

111qqq commented on 2018-11-09 16:48 (UTC) (edited on 2018-11-09 16:48 (UTC) by 111qqq)

2018-11-07: Revision 940 | TextMaker no longer needs libidn.so.11 which is not provided by some Linux distributions anymore.

simona commented on 2018-10-17 08:23 (UTC)

Houston, we have a problem: libidn-133-compat used by softmaker-office-2018-bin conflict with libidn11 used by yesterday's steam-native-runtime. Change deps?

WorMzy commented on 2018-10-06 11:18 (UTC)

Typically, if there is an update out, and I become aware of it (marking the package out-of-date is the best way to do this), then I will update the package when I get chance. At the moment though, there are no 938 downloads available -- the website currently only offers 936: https://www.softmaker.com/en/tips-linux

a-bostaurus commented on 2018-10-06 06:04 (UTC)

Hello, I'd like to know whether there is an aim to publish revision 938 in the AUR. If not I would refresh my version in another way. Hallo, ich würde gern wissen, ob geplant ist, die Revision 938 für Arch Linux-User in das AUR zu stellen. Wenn das nicht geplant sein sollte, würde ich es händisch installieren, allerdings ist mir der Weg über das AUR lieber. Mit freundlichen Grüßen, Michael Zywek

WorMzy commented on 2018-10-04 17:17 (UTC) (edited on 2018-10-04 17:18 (UTC) by WorMzy)

As you can see from the previous few comments, SoftMaker Office seems to be having issues with some non-standard fonts. If you want to identify if this is the cause of your problem, you'll need to provide more information, particularly the output of LC_ALL=C strace -f textmaker18 2> debug.txt seems to provide enough information to find the problematic file (whichever file is addressed before the first SEGV signal has been the culprit so far. Post the output here (using a pastebin) if you want help reading the output.

As for your other question, the easiest way to monitor for updates to your AUR packages is to use an AUR helper.

Francus commented on 2018-10-04 16:15 (UTC)

Everything worked fine for some time, but the last pacman updated broke it. Got errors related to libidn, So installed libidn-133-compat 1.33-1 and it improved, at least textmaker starts, opens a recovered file, but crashes immediately after. Here what I get on the terminal, every time the error is a little bit different: f@F: ~>$ textmaker18 /usr/bin/textmaker18: line 3: 1078 Segmentation fault (core dumped) /usr/share/smoffice2018/textmaker "$@" f@F: ~>$ textmaker18 corrupted size vs. prev_size /usr/bin/textmaker18: line 3: 1585 Aborted (core dumped) /usr/share/smoffice2018/textmaker "$@" f@F: ~>$ textmaker18 /usr/bin/textmaker18: line 3: 2083 Segmentation fault (core dumped) /usr/share/smoffice2018/textmaker "$@"

Also, how may I know that the version I keep installed is the last you produced?

simona commented on 2018-09-28 19:46 (UTC) (edited on 2018-09-28 19:53 (UTC) by simona)

/usr/share/fonts/TTF/LIVEWIRE.ttf is owned by ttf-thelinuxbox-fonts 1.0-1 Uninstalled. Problem solved. Another problem was cause by it: Libreoffice had problem with Times New roman fonts. Thanks for patience.

WorMzy commented on 2018-09-27 21:52 (UTC)

The problem seems to be /usr/share/fonts/TTF/LIVEWIRE.ttf on your system. Is it owned by a package? If so, check the package's integrity using pacman -Qkk. Failing that, try moving that file out of that dir.

simona commented on 2018-09-25 20:18 (UTC)

My debug file: https://www106.zippyshare.com/v/mrLfoGE6/file.html

WorMzy commented on 2018-09-24 10:29 (UTC)

Great! Sorry it took so long to get around to looking at the logs.

@simona, it's unlikely your issue is caused by the same file, so I'll need logs from you if you need help debugging it.