Ran into issues installing playonlinux on Fedora 32, was trying to install microsoft excel for school
This thread was helpful
This solution was pretty helpful
Ran into issues installing playonlinux on Fedora 32, was trying to install microsoft excel for school
This thread was helpful
This solution was pretty helpful
Yeah POL uses ancient versions, IMO you’re better off just manually installing it. I use q4wine for windows applications if I need some.
need help with q4wine
wine --version
bash: wine: command not found...
Packages providing this file are:
'wine-core'
'winehq-devel'
'winehq-stable'
'winehq-staging'
followed install instructions from
https://wiki.winehq.org/Fedora
You added the repo, but did you also install the package? I used dnf install winehq-staging
, but that was 2 years ago and at this point the packages are coming directly from the fedora repo.
sudo dnf install winehq-staging
Last metadata expiration check: 0:34:12 ago on Sat 22 Aug 2020 06:43:43 PM CDT.
Error:
Problem: problem with installed package wine-core-5.15-1.fc32.x86_64
- package winehq-staging-1:5.8-2.1.i686 conflicts with wine-core provided by wine-core-5.15-1.fc32.x86_64
- package winehq-staging-1:5.8-2.1.i686 conflicts with wine-core provided by wine-core-5.5-1.fc32.x86_64
- conflicting requests
- package winehq-staging-1:5.9-1.2.i686 conflicts with wine-core provided by wine-core-5.15-1.fc32.x86_64
- package winehq-staging-1:5.9-1.2.i686 conflicts with wine-core provided by wine-core-5.5-1.fc32.x86_64
- package winehq-staging-1:5.10-1.1.i686 conflicts with wine-core provided by wine-core-5.15-1.fc32.x86_64
- package winehq-staging-1:5.10-1.1.i686 conflicts with wine-core provided by wine-core-5.5-1.fc32.x86_64
- package winehq-staging-1:5.11-2.1.i686 conflicts with wine-core provided by wine-core-5.15-1.fc32.x86_64
- package winehq-staging-1:5.11-2.1.i686 conflicts with wine-core provided by wine-core-5.5-1.fc32.x86_64
- package winehq-staging-1:5.12-6.1.i686 conflicts with wine-core provided by wine-core-5.15-1.fc32.x86_64
- package winehq-staging-1:5.12-6.1.i686 conflicts with wine-core provided by wine-core-5.5-1.fc32.x86_64
- package winehq-staging-1:5.13-1.3.i686 conflicts with wine-core provided by wine-core-5.15-1.fc32.x86_64
- package winehq-staging-1:5.13-1.3.i686 conflicts with wine-core provided by wine-core-5.5-1.fc32.x86_64
- package winehq-staging-1:5.14-1.1.i686 conflicts with wine-core provided by wine-core-5.15-1.fc32.x86_64
- package winehq-staging-1:5.14-1.1.i686 conflicts with wine-core provided by wine-core-5.5-1.fc32.x86_64
- package winehq-staging-1:5.15-7.1.i686 conflicts with wine-core provided by wine-core-5.15-1.fc32.x86_64
- package winehq-staging-1:5.15-7.1.i686 conflicts with wine-core provided by wine-core-5.5-1.fc32.x86_64
- package winehq-staging-1:5.8-2.1.x86_64 conflicts with wine-core provided by wine-core-5.15-1.fc32.x86_64
- package winehq-staging-1:5.8-2.1.x86_64 conflicts with wine-core provided by wine-core-5.5-1.fc32.x86_64
- package winehq-staging-1:5.9-1.2.x86_64 conflicts with wine-core provided by wine-core-5.15-1.fc32.x86_64
- package winehq-staging-1:5.9-1.2.x86_64 conflicts with wine-core provided by wine-core-5.5-1.fc32.x86_64
- package winehq-staging-1:5.10-1.1.x86_64 conflicts with wine-core provided by wine-core-5.15-1.fc32.x86_64
- package winehq-staging-1:5.10-1.1.x86_64 conflicts with wine-core provided by wine-core-5.5-1.fc32.x86_64
- package winehq-staging-1:5.11-2.1.x86_64 conflicts with wine-core provided by wine-core-5.15-1.fc32.x86_64
- package winehq-staging-1:5.11-2.1.x86_64 conflicts with wine-core provided by wine-core-5.5-1.fc32.x86_64
- package winehq-staging-1:5.12-6.1.x86_64 conflicts with wine-core provided by wine-core-5.15-1.fc32.x86_64
- package winehq-staging-1:5.12-6.1.x86_64 conflicts with wine-core provided by wine-core-5.5-1.fc32.x86_64
- package winehq-staging-1:5.13-1.3.x86_64 conflicts with wine-core provided by wine-core-5.15-1.fc32.x86_64
- package winehq-staging-1:5.13-1.3.x86_64 conflicts with wine-core provided by wine-core-5.5-1.fc32.x86_64
- package winehq-staging-1:5.14-1.1.x86_64 conflicts with wine-core provided by wine-core-5.15-1.fc32.x86_64
- package winehq-staging-1:5.14-1.1.x86_64 conflicts with wine-core provided by wine-core-5.5-1.fc32.x86_64
- package winehq-staging-1:5.15-7.1.x86_64 conflicts with wine-core provided by wine-core-5.15-1.fc32.x86_64
- package winehq-staging-1:5.15-7.1.x86_64 conflicts with wine-core provided by wine-core-5.5-1.fc32.x86_64
(try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages)
That usually happens when 2 different wine versions were installed.
You can sudo dnf remove wine*
and then try an install again.
I’ve seen that on the Lutris discord a few times, not sure how it happens though.
did that, wine doesn’t show up in the all apps
also q4wine doesn’t show up anymore
WINE itself won’t because there’s nothing to show, it’s just the backend if you will.
q4wine was probably uninstalled along with wine (because wine is a dependecy), just reinstall it.
I never use the application manager thing anymore… I tried it a few times at the start and it failed to install things or even find things so I just gave up on it and went with dnf
. It’s just dnf install q4wine
.
sudo dnf install q4wine
Last metadata expiration check: 0:48:53 ago on Sat 22 Aug 2020 06:43:43 PM CDT.
Error:
Problem: package q4wine-1.3.6-7.fc32.x86_64 requires wine-core, but none of the providers can be installed
- package winehq-staging-1:5.8-2.1.x86_64 conflicts with wine-core provided by wine-core-5.15-1.fc32.i686
- package winehq-staging-1:5.8-2.1.x86_64 conflicts with wine-core provided by wine-core-5.15-1.fc32.x86_64
- package winehq-staging-1:5.8-2.1.x86_64 conflicts with wine-core provided by wine-core-5.5-1.fc32.i686
- package winehq-staging-1:5.8-2.1.x86_64 conflicts with wine-core provided by wine-core-5.5-1.fc32.x86_64
- problem with installed package winehq-staging-1:5.15-7.1.x86_64
- package winehq-staging-1:5.9-1.2.x86_64 conflicts with wine-core provided by wine-core-5.15-1.fc32.i686
- package winehq-staging-1:5.9-1.2.x86_64 conflicts with wine-core provided by wine-core-5.15-1.fc32.x86_64
- package winehq-staging-1:5.9-1.2.x86_64 conflicts with wine-core provided by wine-core-5.5-1.fc32.i686
- package winehq-staging-1:5.9-1.2.x86_64 conflicts with wine-core provided by wine-core-5.5-1.fc32.x86_64
- conflicting requests
- package q4wine-1.3.12-2.fc32.x86_64 requires wine-core, but none of the providers can be installed
- package winehq-staging-1:5.10-1.1.x86_64 conflicts with wine-core provided by wine-core-5.15-1.fc32.i686
- package winehq-staging-1:5.10-1.1.x86_64 conflicts with wine-core provided by wine-core-5.15-1.fc32.x86_64
- package winehq-staging-1:5.10-1.1.x86_64 conflicts with wine-core provided by wine-core-5.5-1.fc32.i686
- package winehq-staging-1:5.10-1.1.x86_64 conflicts with wine-core provided by wine-core-5.5-1.fc32.x86_64
- package winehq-staging-1:5.11-2.1.x86_64 conflicts with wine-core provided by wine-core-5.15-1.fc32.i686
- package winehq-staging-1:5.11-2.1.x86_64 conflicts with wine-core provided by wine-core-5.15-1.fc32.x86_64
- package winehq-staging-1:5.11-2.1.x86_64 conflicts with wine-core provided by wine-core-5.5-1.fc32.i686
- package winehq-staging-1:5.11-2.1.x86_64 conflicts with wine-core provided by wine-core-5.5-1.fc32.x86_64
- package winehq-staging-1:5.12-6.1.x86_64 conflicts with wine-core provided by wine-core-5.15-1.fc32.i686
- package winehq-staging-1:5.12-6.1.x86_64 conflicts with wine-core provided by wine-core-5.15-1.fc32.x86_64
- package winehq-staging-1:5.12-6.1.x86_64 conflicts with wine-core provided by wine-core-5.5-1.fc32.i686
- package winehq-staging-1:5.12-6.1.x86_64 conflicts with wine-core provided by wine-core-5.5-1.fc32.x86_64
- package winehq-staging-1:5.13-1.3.x86_64 conflicts with wine-core provided by wine-core-5.15-1.fc32.i686
- package winehq-staging-1:5.13-1.3.x86_64 conflicts with wine-core provided by wine-core-5.15-1.fc32.x86_64
- package winehq-staging-1:5.13-1.3.x86_64 conflicts with wine-core provided by wine-core-5.5-1.fc32.i686
- package winehq-staging-1:5.13-1.3.x86_64 conflicts with wine-core provided by wine-core-5.5-1.fc32.x86_64
- package winehq-staging-1:5.14-1.1.x86_64 conflicts with wine-core provided by wine-core-5.15-1.fc32.i686
- package winehq-staging-1:5.14-1.1.x86_64 conflicts with wine-core provided by wine-core-5.15-1.fc32.x86_64
- package winehq-staging-1:5.14-1.1.x86_64 conflicts with wine-core provided by wine-core-5.5-1.fc32.i686
- package winehq-staging-1:5.14-1.1.x86_64 conflicts with wine-core provided by wine-core-5.5-1.fc32.x86_64
- package winehq-staging-1:5.15-7.1.x86_64 conflicts with wine-core provided by wine-core-5.15-1.fc32.i686
- package winehq-staging-1:5.15-7.1.x86_64 conflicts with wine-core provided by wine-core-5.15-1.fc32.x86_64
- package winehq-staging-1:5.15-7.1.x86_64 conflicts with wine-core provided by wine-core-5.5-1.fc32.i686
- package winehq-staging-1:5.15-7.1.x86_64 conflicts with wine-core provided by wine-core-5.5-1.fc32.x86_64
(try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages)
should I run --allowerasing
mmhhh OK yeah that’s annoying.
So the issue is that you installed winehq-staging
from the WineHQ repos, but q4wine depends on the wine-core
Fedora package, which is incompatible with the WineHQ repos…
So yeah what you can do is just uninstall winehq-staging
and dnf install wine-staging
(which is the corresponding Fedora package), which is a metapackage that packs everything wine related to get it running.
I honestly don’t know why WineHQ still lists adding that repo manually when WINE is already in the Fedora Core repos.
edit:
what you can also do is just not manually installing wine at all. q4wine already depends on the wine-core package and will install it as a dependency.
Which version of Office are we talking about exactly? Also did you make sure to create a 64 bit prefix? I assume Office won’t really run in a 32 bit prefix anymore.
Looking at the AppDB page it seems it needs a few winetricks to install:
msxml3, msxml6, riched30
, listed under dlls.
In q4wine you’ll find it under Setup. Select the prefix at the top, then double-click “install or update Winetricks script”, then “Refresh Winetricks application list”. That should give you the categories on the left side.
q4wine Interface is not all that intuitive IMO.
tried installing all the winetricks
still getting same issues, when I look at the page you linked, Fedora has a garbage rating
Fedora 30 x86_64 Sep 30 2019 4.16 Yes No No Garbage Lucas
Unhandled exception: 0x012633df in 64-bit code (0x00000001400279f1).
Register dump:
rip:00000001400279f1 rsp:000000000021ead0 rbp:000000000021cc50 eflags:00010246 ( R- -- I Z- -P- )
rax:0000000000000000 rbx:000000000021cbe8 rcx:00000000012633df rdx:0000000000000000
rsi:000000000021cca0 rdi:00000000007af001 r8:000000000021cca0 r9:ffffffffffffffff r10:0000000000000000
r11:0000000000000041 r12:0000000000001000 r13:0000000000000002 r14:00000000ffffffff r15:0000000000000000
Stack dump:
0x000000000021ead0: fffffffffffffffe 0000000000790000
0x000000000021eae0: 00000000007b7438 0000000000010000
0x000000000021eaf0: 000000000000007e 0000000000000000
0x000000000021eb00: 0000000000006574 0000000000000000
0x000000000021eb10: 000000000021dce0 0000000000210004
0x000000000021eb20: 000000000021cc50 0000000140014941
0x000000000021eb30: 00000000012633df 0000000000000000
0x000000000021eb40: 0000000000000001 000000000021cc18
0x000000000021eb50: 0000000000000000 000000007b02b632
0x000000000021eb60: 0000000000010000 0000000000000002
0x000000000021eb70: 0000000000000002 0000000000010000
0x000000000021eb80: 0000000000000002 00000001404902a0
Backtrace:
=>0 0x00000001400279f1 in setup.x64.en-us_o365proplusreta (+0x279f1) (0x000000000021cc50)
1 0x0000000140014941 in setup.x64.en-us_o365proplusreta (+0x14940) (0x000000000021cc50)
2 0x00000001400de371 in setup.x64.en-us_o365proplusreta (+0xde370) (0x000000000021cc50)
3 0x00000001400de666 in setup.x64.en-us_o365proplusreta (+0xde665) (0x000000000021f0d9)
4 0x00000001400c8168 in setup.x64.en-us_o365proplusreta (+0xc8167) (0x000000000021f1a9)
5 0x00000001400c800e in setup.x64.en-us_o365proplusreta (+0xc800d) (0x00000001406ccb70)
6 0x0000000140026ee6 in setup.x64.en-us_o365proplusreta (+0x26ee5) (0x000000000021f610)
7 0x0000000140011fc4 in setup.x64.en-us_o365proplusreta (+0x11fc3) (0x000000000021ffd0)
8 0x00000001403d68f2 in setup.x64.en-us_o365proplusreta (+0x3d68f1) (0x000000000021ffd0)
9 0x000000007b64c6eb in kernel32 (+0x3c6ea) (0x000000000021ffd0)
0x00000001400279f1: movl $0x1,0x0000000000000000
Modules:
Module Address Debug info Name (31 modules)
PE 61340000- 6134e000 Deferred api-ms-win-core-localization-obsolete-l1-2-0
PE 61900000- 619cb000 Deferred sechost
PE 62540000- 62619000 Deferred wintrust
PE 64940000- 64992000 Deferred shcore
PE 65000000- 656ac000 Deferred ole32
PE 65780000- 657a0000 Deferred version
PE 66600000- 6660e000 Deferred api-ms-win-core-datetime-l1-1-1
PE 66780000- 6678e000 Deferred api-ms-win-core-string-l1-1-0
PE 67600000- 676b4000 Deferred combase
PE 68a40000- 68b90000 Deferred shlwapi
PE 6a100000- 6a619000 Deferred oleaut32
PE 6a700000- 6a93d000 Deferred setupapi
PE 6b880000- 6b88e000 Deferred api-ms-win-core-fibers-l1-1-1
PE 6bec0000- 6bf18000 Deferred imm32
PE 6e340000- 6e34f000 Deferred api-ms-win-core-synch-l1-2-0
PE 6e6c0000- 6e6cf000 Deferred api-ms-win-core-localization-l1-2-1
PE 6f480000- 6f7b4000 Deferred gdiplus
PE 6fbc0000- 6fe6e000 Deferred rpcrt4
PE 7b000000- 7b3ea000 Deferred kernelbase
PE 7b610000- 7b7cb000 Export kernel32
PE 7bc00000- 7bfc9000 Deferred ntdll
PE 140000000- 1407e3000 Export setup.x64.en-us_o365proplusretail_046a1422-e99a-4835-b77b-1108
PE 7ff4d2a30000- 7ff4d2a34000 Deferred winex11
PE 7ff4d3290000- 7ff4d3294000 Deferred bcrypt
PE 7ff4d32c0000- 7ff4d3304000 Deferred crypt32
PE 7ff4d33d0000- 7ff4d33d4000 Deferred ws2_32
PE 7ff4d3430000- 7ff4d3518000 Deferred user32
PE 7ff4d36c0000- 7ff4d36c7000 Deferred gdi32
PE 7ff4d3890000- 7ff4d3894000 Deferred ucrtbase
PE 7ff4d39b0000- 7ff4d39b4000 Deferred advapi32
PE 7ff4e12b0000- 7ff4e12b3000 Deferred wow64cpu
Threads:
process tid prio (all id:s are in hex)
00000038 services.exe
["C:\windows\system32\services.exe"]
0000003c 0
00000040 0
00000054 0
00000058 0
00000070 0
00000098 0
00000044 explorer.exe
[C:\windows\system32\explorer.exe /desktop]
00000048 0
000000b0 0
000000b4 0
000000b8 0
0000004c plugplay.exe
[C:\windows\system32\plugplay.exe]
00000050 0
0000005c 0
00000060 0
00000064 0
00000080 0
00000084 0
00000068 winedevice.exe
[C:\windows\system32\winedevice.exe]
0000006c 0
00000074 0
00000078 0
0000007c 0
00000088 0
0000008c 0
00000090 winedevice.exe
[C:\windows\system32\winedevice.exe]
00000094 0
0000009c 0
000000a0 0
000000a4 0
000000c4 (D) Z:\home\bedhedd\Downloads\Setup.X64.en-us_O365ProPlusRetail_046a1422-e99a-4835-b77b-11083cfaa42c_TX_PR_b_32_.exe
["Z:\home\bedhedd\Downloads\Setup.X64.en-us_O365ProPlusRetail_046a1422-e99a-4835-b77b-11083cfaa42c_TX_PR_b_32_.exe"]
000000c8 0 <==
000000d4 0
000000d8 explorer.exe
[C:\windows\system32\explorer.exe /desktop]
000000dc 0
000000e0 0
000000e4 0
000000e8 0
System information:
Wine build: wine-5.15 (Staging)
Platform: x86_64
Version: Windows 10
Host system: Linux
Host version: 5.7.16-200.fc32.x86_64
That didn’t use any workarounds tho. TBH I don’t really give much thought for the ratings, most people don’t even know what they mean anyway tho, did you follow the whole guide there? There seem to be a few more steps. I don’t have an office license tho so I can’t test unfortunately
I am really having trouble getting the installer to launch
guide they talked about
Workarounds
Installed the following: msxml3, msxml6, and riched30 via winetricks.
set WINEARCH variable to win32 for x86 mode.
Download the Office Deployment Tool 2013.
Run the Tool under wine to extract the contents and setup.exe on extracted folder.
Configure foo.xml to install Office365 ProPlus x86. See here near bottom.
Run the following commands in the extracted folder:
wine ./setup.exe /download foo.xml
wine ./setup.exe /configure foo.xml
Then run any Office Application (Word, Excel, or Powerpoint), sign in to activate the product.
I am stuck on this step I don’t know where the WINEARCH variable
set WINEARCH variable to win32 for x86 mode.```
Set it in the prefix settings (right-click the prefix > Configure prefix settings)
Although as far as I know it cannot be changed once the prefix has been created.