Community Packages

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#58607 - [wine] office 2010 fails to start

Attached to Project: Community Packages
Opened by Michael Wrzaczek (emmwee) - Tuesday, 15 May 2018, 11:51 GMT
Last edited by Morten Linderud (Foxboron) - Monday, 16 November 2020, 21:12 GMT
Task Type Bug Report
Category Packages: Multilib
Status Closed
Assigned To Felix Yan (felixonmars)
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No


After upgrade of wine from 3.7-1 to 3.8-1 office 2010 apps fail and do not start anymore. Reversion to 3.7-1 fixes this issue. Not sure that information to attach but can provide anything you need to fix this!

Additional info:
* package version(s)
* config and/or log files etc.

Steps to reproduce:
This task depends upon

Closed by  Morten Linderud (Foxboron)
Monday, 16 November 2020, 21:12 GMT
Reason for closing:  Fixed
Comment by Michael Wrzaczek (emmwee) - Tuesday, 15 May 2018, 11:52 GMT
Addon: in the wine bugzilla this was identified as Arch-specific issue as Office 2010 works fine on Opensuse with wine-3.8-1
Comment by Tommy Schmitt (spinka) - Tuesday, 15 May 2018, 14:06 GMT
On my system (Archlinux) it works too. Probably this is yours specific issue.
Comment by Michael Wrzaczek (emmwee) - Tuesday, 15 May 2018, 14:07 GMT
Ok, Interesting, I have the issue on two computers. I'll try to figure out what is going on here. Thanks!
Comment by Eli Schwartz (eschwartz) - Wednesday, 16 May 2018, 17:44 GMT
  • Field changed: Summary ([wine] PLEASE ENTER SUMMARY → [wine] office 2010 fails to start)
Comment by Sven-Hendrik Haase (Svenstaro) - Monday, 04 June 2018, 16:04 GMT
So I guess we'll start compiling wine with -fno-PIC. Any problems with that?
Comment by Felix Yan (felixonmars) - Monday, 25 February 2019, 09:35 GMT
This has been fixed upstream some time ago. Do you still get this issue?