the installer stop on latest ubuntu throwing some messages

[dmsumon]

Whenever I try to use the script I found the following errors

According to the @officermeraz the command "echo 0 | sudo tee /proc/sys/kernel/yama/ptrace_scope" didn't make any magic ...

According to the Troubleshooting page if I run the following two commands

sudo setcap cap_sys_ptrace=eip ~/.PlayOnLinux/wine/linux-x86/2.17-staging/bin/wineserver sudo setcap cap_sys_ptrace=eip ~/.PlayOnLinux/wine/linux-x86/2.17-staging/bin/wine-preloader

I get the following error outputs

Please help @corbindavenport

[corbindavenport]

Can you verify the /root/.PlayOnLinux/wine/linux-x86/2.17-staging/bin/wineserver file is actually there?

[dmsumon]

@corbindavenport Thanks for your kind reply ...

Nope the file isn't there, I'm 100% sure about it. On PlayOnLinux when I go to tools> manage wine versions, I can see that 2.20-staging is installed instead of 2.17-staging

First I thought I made some mistake then I deleted all versions of wine and re-tried but again I see that 2.20-staging is installed

Then I checked your creativecloud.sh and on line number 15, I can see that

WINEVERSION="2.20-staging"

In order to become more sure I ran the below codes to check the existence of the file

test -e ~/.PlayOnLinux/wine/linux-x86/2.17-staging/bin/wineserver && echo file exists || echo file not found

I got output "file not found"

test -e ~/.PlayOnLinux/wine/linux-x86/2.20-staging/bin/wineserver && echo file exists || echo file not found

I got output "file exists"

So I think you are mistaken at that point ... Then I fixed those two command lines as following

sudo setcap cap_sys_ptrace=eip ~/.PlayOnLinux/wine/linux-x86/2.20-staging/bin/wineserver
sudo setcap cap_sys_ptrace=eip ~/.PlayOnLinux/wine/linux-x86/2.20-staging/bin/wine-preloader

This time I do not see any error message on my terminal but still no luck. After giving the modified commands in my terminal, I re-ran the script on POL and came up with the following error codes

I re-tried by deleting the 2.20-staging from tools> manage wine versions but again got the above errors.

Please help me @corbindavenport, I' ll be very grateful to you coz as I'm a UX/ Web Designer, as a result I can't live without Photoshop. On the other hand I really want to kick out Windows from my machine permanently.

Thanks in advance Sir.

[corbindavenport]

Ah yeah, I overlooked that the commands are outdated (the script used to use 2.17-staging), I'll fix that in the wiki.

Try running the installer again, and select the option to completely wipe the existing Creative Cloud drive/prefix. That should do the trick.

[dmsumon]

I tried using the option erase (virtual drive content will be lost)

then again got the following error

@corbindavenport Sir, please help me to fix the issue. Thanks a lot in advance

[solracfirst]

Hi I'm getting the same error.

[theman99]

Hey, got exactly the same error. Here the backtrace-file:

backtrace.txt

@corbindavenport thanks for your work and support!

[streambinder]

The same error here on Solus, too. The maximum I reached is 26% on CreativeCloud download.

[corbindavenport]

I've been trying a ton of different tweaks to get Creative Cloud working on 64-bit Wine (or even a newer 32-bit Wine), and one of the things I tried was using the offline Creative Cloud installer from Adobe's website.

I could try changing the master branch script to do that as well, maybe it would fix these download errors (since all the downloading would be done by the host system).

[temofey1989]

Hello. The installation of Adobe Creative Cloud was successful on my desktop (OS: Kubuntu 18.04 x64). However, updates are not working for it. It ends up with this error: Also, installation of some application (Lightroom 5 in my case) is stuck on 42%.

[corbindavenport]

@dmsumon @solracfirst @theman99 @streambinder Try the latest version of the installer and let me know if y'all still have download issues. It now uses the offline installer package, so all the downloading is done by Linux instead of through Wine.

@temofey1989 Please file a separate GitHub issue for that, it's unrelated to this specific bug.

[streambinder]

@corbindavenport the issue seems to be fixed now. I would suggest an addition to the script, which I will be creating a pull request for. Thank you anyway.

[corbindavenport]

I'll mark this as resolved then, If anyone still has issues, feel free to re-open or make a new issue.