Microsoft office fails to install.
DuttaAB-dev opened this issue · 8 comments
Expected behavior
The install setup in completed all the way through.
Actual behavior
The installer hangs at about 60% mark and then gives out a crash report.
Steps to reproduce
Try installing office 2010 or office 2013 using the available scripts and a local setup file.
System information
- software version (git revision) of phoenicis and scripts repositories
*scripts repos:
-
used operating system
-
NAME="Pop!_OS"
VERSION="21.04"
ID=pop
ID_LIKE="ubuntu debian"
PRETTY_NAME="Pop!_OS 21.04"
VERSION_ID="21.04"
HOME_URL="https://pop.system76.com"
SUPPORT_URL="https://support.system76.com"
BUG_REPORT_URL="https://github.com/pop-os/pop/issues"
PRIVACY_POLICY_URL="https://system76.com/privacy"
VERSION_CODENAME=hirsute
UBUNTU_CODENAME=hirsute
LOGO=distributor-logo-pop-os -
used Java version
flatpak default
Is this flatpak specific or does it also happen outside of flatpak? Does Phoenicis report any errors (e.g. if your run it from command line)?
I haven't tested it through the terminal yet so will inform after doing that.
Is this flatpak specific or does it also happen outside of flatpak? Does Phoenicis report any errors (e.g. if your run it from command line)?
running it from the command line didn't produce much of an useful output. It was all about fonts not rendering that one usually gets.
tried installing office 2013 using Phoenicis installed using the deb file and got this error
`
Unhandled exception: page fault on execute access to 0x7d44e8b0 in 32-bit code (0x7d44e8b0).
Register dump:
CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:006b
EIP:7d44e8b0 ESP:00327dbc EBP:7df4b670 EFLAGS:00010216( R- -- I -A-P- )
EAX:7d44e8b0 EBX:00000000 ECX:7df4b674 EDX:00000000
ESI:00000002 EDI:00327f0c
Stack dump:
0x00327dbc: 7e6a4de5 7dee6910 00000002 7df4b674
0x00327dcc: 00327f0c 00002000 00002000 00000000
0x00327ddc: 00000000 00000000 7dee6910 7e7d6000
0x00327dec: 00000000 00000000 00320000 00000000
0x00327dfc: 00000000 00000000 00000000 00000000
0x00327e0c: 00000000 00000000 00000000 00000000
Backtrace:
=>0 0x7d44e8b0 (0x7df4b670)
1 0x00000009 (0x7df3b4e0)
2 0x00000008 (0x7df08520)
3 0x00000007 (0x7df05cc0)
4 0x00000006 (0x7defaec0)
5 0x00000005 (0x7defab20)
6 0x00000004 (0x7def9a20)
7 0x00000003 (0x7def8e80)
8 0x00000002 (0x7def9260)
9 0x00000001 (0x7dee4ae0)
0x7d44e8b0: -- no code accessible --
Modules:
Module Address Debug info Name (42 modules)
PE 400000- 434000 Deferred setup
PE 890000- cab000 Deferred gdi32
PE 1270000- 193a000 Deferred osetup
PE 1a50000- 1a7f000 Deferred osetupui
PE 1a90000- 1b85000 Deferred hhctrl
PE 10000000-100d3000 Deferred setup
PE 61740000-617ee000 Deferred advapi32
PE 62fc0000-63154000 Deferred rpcrt4
PE 63480000-63496000 Deferred version
PE 637c0000-63898000 Deferred oleacc
PE 63bc0000-63bf2000 Deferred shcore
PE 64a40000-64b2b000 Deferred shlwapi
PE 64ec0000-651a5000 Deferred oleaut32
PE 65580000-6559e000 Deferred wtsapi32
PE 66240000-66275000 Deferred bcrypt
PE 666c0000-666df000 Deferred hid
PE 68100000-68116000 Deferred wer
PE 68500000-68600000 Deferred combase
PE 68700000-6876b000 Deferred uxtheme
PE 68e00000-68e1d000 Deferred aclui
PE 6a400000-6a76d000 Deferred ole32
PE 6bc00000-6bc74000 Deferred sechost
PE 6bcc0000-6be16000 Deferred setupapi
PE 6cc40000-6cf3f000 Deferred comctl32
PE 6db40000-6db6a000 Deferred imagehlp
PE 6e8c0000-6eaa2000 Deferred crypt32
PE 6ed00000-6f24c000 Deferred user32
PE 6f280000-6f2ed000 Deferred hlink
PE 6f4c0000-6f537000 Deferred wintrust
PE 6fa80000-6fc41000 Deferred dbghelp
PE 6fe40000-6feae000 Deferred rsaenh
PE 70b40000-70d2b000 Deferred ucrtbase
PE 71200000-71239000 Deferred imm32
PE 7a840000-7a844000 Deferred opengl32
PE 7b000000-7b23a000 Deferred kernelbase
PE 7b600000-7b8d3000 Deferred kernel32
PE 7bc00000-7bde6000 Deferred ntdll
PE 7ce50000-7ce54000 Deferred wined3d
PE 7d4d0000-7ddc6000 Deferred shell32
PE 7e120000-7e124000 Deferred dxgi
PE 7e160000-7e163000 Deferred dwrite
PE 7e810000-7e814000 Deferred winex11
Threads:
process tid prio (all id:s are in hex)
00000038 services.exe
["C:\windows\system32\services.exe"]
0000003c 0
00000040 0
00000054 0
00000070 0
00000088 0
000000b0 0
000000cc 0
00000044 winedevice.exe
[C:\windows\system32\winedevice.exe]
00000048 0
0000005c 0
00000060 0
00000064 0
00000068 plugplay.exe
[C:\windows\system32\plugplay.exe]
0000006c 0
00000074 0
00000078 0
0000007c 0
00000098 0
00000080 winedevice.exe
[C:\windows\system32\winedevice.exe]
00000084 0
0000008c 0
00000090 0
00000094 0
000000a0 0
000000a4 svchost.exe
[C:\windows\system32\svchost.exe -k LocalServiceNetworkRestricted]
000000a8 0
000000b4 0
000000b8 0
000000c4 rpcss.exe
[C:\windows\system32\rpcss.exe]
000000c8 0
000000d4 0
000000d8 0
000000dc 0
000000e0 0
0000011c 0
00000168 0
0000010c explorer.exe
[C:\windows\system32\explorer.exe /desktop]
00000110 0
00000114 0
00000118 0
00000158 explorer.exe
[C:\windows\system32\explorer.exe /desktop]
0000015c 0
00000160 0
00000164 0
00000178 (D) Z:\home\devops\Downloads\Microsoft Office 2013 - www.MySoftwareFree.com\Software Files\setup.exe
["Z:\home\devops\Downloads\Microsoft Office 2013 - www.MySoftwareFree.com\Software Files\setup.exe"]
0000017c 0 <==
00000180 0
0000018c 0
System information:
Wine build: wine-6.5 (Staging)
Platform: i386
Version: Windows 7
Host system: Linux
Host version: 5.11.0-7614-generic
`
This looks more like an issue in Wine to me. Can you verify that it's really caused by PlayOnLinux (i.e. does it work if you run the installation in plain Wine)? Also: did you check winehq for bug reports which might be related?
Small hint: code blocks are with 3 backticks.
This looks more like an issue in Wine to me. Can you verify that it's really caused by PlayOnLinux (i.e. does it work if you run the installation in plain Wine)? Also: did you check winehq for bug reports which might be related?
Small hint: code blocks are with 3 backticks.
On it and thanks for the hint! And a small question, is it a good idea to use proton as a compatibility layer instead of wine?
This looks more like an issue in Wine to me. Can you verify that it's really caused by PlayOnLinux (i.e. does it work if you run the installation in plain Wine)? Also: did you check winehq for bug reports which might be related?
Small hint: code blocks are with 3 backticks.
Ran it using playonlinux 4. Works just fine, installs and adds all the shortcuts. Is there any way to use my system wine installation to use as the default runner for phoenicis?
is it a good idea to use proton as a compatibility layer instead of wine?
I don't think it's possible to answer this generally. Certain programs definitely work better with Proton.
Ran it using playonlinux 4. Works just fine, installs and adds all the shortcuts.
In this case we should probably compare the installation procedures from PlayOnLinux 5 and 4. Maybe @ImperatorS79 has some idea as he wrote the script originally.
Is there any way to use my system wine installation to use as the default runner for phoenicis?
Currently not.