Scrivener/Scapple for Windows Activation under Wine

User avatar
tiho_d
Posts: 908
Joined: Tue Sep 13, 2011 1:14 pm
Platform: Linux + Windows

Thu Sep 26, 2019 9:58 am Post

Wine 4.0.2 comes with Mono, which does not allow the license activation to
work. Mono apparently has problems with TLS 1.2, which is required for the
license activation component to connect to the server.
The following steps have resolved the problem for some users:

1. Open the terminal window (Ctrl+Alt+T)
2. wine uninstaller
3. Add/remove programs window will open. Uninstall Mono and close the window
4. sudo apt-get install winetricks
5. winetricks --force dotnet452
Installing a newer dotnet version is a good option and even recommended.

When you start Scrivener or Scapple after this, the license activation
component should work.

User avatar
garpu
Posts: 2016
Joined: Mon Oct 25, 2010 9:38 pm
Platform: Linux

Thu Sep 26, 2019 1:11 pm Post

Can we sticky this? :)
Slackware-current 64-bit, XFCE

User avatar
AmberV
Posts: 23796
Joined: Sun Jun 18, 2006 4:30 am
Platform: Mac + Linux
Location: Ourense, Galiza
Contact:

Wed Oct 02, 2019 11:25 am Post

Good idea!
.:.
Ioa Petra'ka
“Whole sight, or all the rest is desolation.” —John Fowles

Se
Sensei
Posts: 1
Joined: Tue Sep 24, 2019 1:29 pm
Platform: Windows

Mon Oct 07, 2019 8:36 pm Post

It worked for me! Thanks for sharing the good tip. I thought I could never get to the end of my story that is maybe too long to tell :-). This trick saved me many headaches. Thank you so much!

User avatar
rburkej
Posts: 1
Joined: Sun Oct 20, 2019 3:27 pm
Platform: Mac + Windows
Location: Near Orlando, FL
Contact:

Sun Oct 20, 2019 3:45 pm Post

Excellent. Thank you. Worked for me on Manjaro with the appropriate pacman commands.

User avatar
MrBeardie
Posts: 12
Joined: Tue Nov 12, 2019 6:50 pm
Platform: Mac + Linux
Location: The hills east of Melbourne, Australia

Tue Nov 12, 2019 7:10 pm Post

Having tried the method described above and finding it did not work for me, I started searching for a possible solution on winehq.org. I ended up coming up with a simple process that was successful and repeatable when used again on a freshly set up laptop. In order to avoid the potential for interfering with other software I had installed under Wine, I did all this in a new Wine prefix.

I tried to create a script for this but discovered that it was executing steps before prior steps had completed. I therefore suggest each command is run separately once the preceding step has fully finished. Those steps are:

env WINEARCH=win64
env WINEPREFIX=$HOME/wine_scrivener wineboot --init
env WINEPREFIX=$HOME/wine_scrivener winetricks dotnet40 corefonts
env WINEPREFIX=$HOME/wine_scrivener winetricks win7
env WINEPREFIX=$HOME/wine_scrivener winetricks dotnet462
env WINEPREFIX=$HOME/wine_scrivener wine Scrivener-1.9.15.exe

The same process also worked for the latest V3 beta.
Running Scrivener for Windows on Linux Mint 18.3

User avatar
MrBeardie
Posts: 12
Joined: Tue Nov 12, 2019 6:50 pm
Platform: Mac + Linux
Location: The hills east of Melbourne, Australia

Tue Nov 12, 2019 8:32 pm Post

Just for clarity; Scrivener itself worked just fine using the originally posted procedure but the new Paddle activation didn't.
Running Scrivener for Windows on Linux Mint 18.3

tp
tpletcher
Posts: 6
Joined: Mon Dec 02, 2019 3:46 pm
Platform: Mac + Windows

Mon Dec 02, 2019 4:27 pm Post

I've used Scrivener on Mac from the beginning, and I've also been running the Windows 3 betas under Wine since Linux support was discontinued. There were always minor issues with this but in general the betas were good enough to do useful work, and I was able to go back and forth between Linux and Mac fairly smoothly. Now though, with Beta 30, Scrivener will not run under Wine with my setup. I'm running Ubuntu bionic (18.0.4 LTS). I've upgraded Wine to 4.0.3 and, following a tip on this forum, I updated dotnet to 4.5.2.

I note that the Beta 30 release states dotnet 4.6.2 is required. I have not been able to install that on my LTS version. For what it's worth, Scapple runs fine, as do a variety of other Windows programs which I also run on my Mac, such as Aeon Timeline 2 and Postbox.

I do realize Linux is no longer supported, but I have been consistently impressed by how well the Scrivener 3.0 betas have run under Wine. In fact, I wrote a very popular Medium post about this: https://medium.com/@tpletcher/scrivener ... 35c710e413.

But now I'm at a standstill with Scrivener on Ubuntu. I'm not sure why Beta 30 would up the dotnet requirements to the point of breaking compatibility, if indeed that's what happened. Needless to say, though, after so many successful beta versions this is a huge disappointment.

If anyone has any suggestions on how to get this beta working under Wine, I'd be grateful. Meanwhile, for the developers, I'm attaching the backtrace which details the unhandled exception and other errors.

Many thanks.
Attachments
backtrace.txt
(18.54 KiB) Downloaded 5 times

User avatar
devinganger
Posts: 1791
Joined: Sat Nov 06, 2010 1:55 pm
Platform: Mac, Win + iOS
Location: Monroe, WA 98272 (CN97au)
Contact:

Mon Dec 02, 2019 6:44 pm Post

tpletcher wrote:I note that the Beta 30 release states dotnet 4.6.2 is required. I have not been able to install that on my LTS version.


Are you using Winetricks? That should help you get 4.6.2 (or later) installed, ass mentioned just a few posts up-thread.
--
Devin L. Ganger, WA7DLG
Not a L&L employee; opinions are those of my cat
Winner "Best in Class", 2018 My First Supervillain Photo Shoot

User avatar
MrBeardie
Posts: 12
Joined: Tue Nov 12, 2019 6:50 pm
Platform: Mac + Linux
Location: The hills east of Melbourne, Australia

Mon Dec 02, 2019 7:09 pm Post

tpletcher wrote:I note that the Beta 30 release states dotnet 4.6.2 is required.

I had the same issue initially with Linux Mint but it worked perfectly when I started with a new Wine prefix. Since writing my earlier post in this topic, I've been able to reproduce my success on other distros at work, where each of us in the IT department have our own Linux preferences.
Running Scrivener for Windows on Linux Mint 18.3

tp
tpletcher
Posts: 6
Joined: Mon Dec 02, 2019 3:46 pm
Platform: Mac + Windows

Mon Dec 02, 2019 7:48 pm Post

devinganger wrote:
tpletcher wrote:I note that the Beta 30 release states dotnet 4.6.2 is required. I have not been able to install that on my LTS version.


Are you using Winetricks? That should help you get 4.6.2 (or later) installed, ass mentioned just a few posts up-thread.


I used winetricks to install 4.5.2; it fails with 4.6.2.

tp
tpletcher
Posts: 6
Joined: Mon Dec 02, 2019 3:46 pm
Platform: Mac + Windows

Mon Dec 02, 2019 7:48 pm Post

MrBeardie wrote:
tpletcher wrote:I note that the Beta 30 release states dotnet 4.6.2 is required.

I had the same issue initially with Linux Mint but it worked perfectly when I started with a new Wine prefix. Since writing my earlier post in this topic, I've been able to reproduce my success on other distros at work, where each of us in the IT department have our own Linux preferences.


I'll give this a try; thanks.

tp
tpletcher
Posts: 6
Joined: Mon Dec 02, 2019 3:46 pm
Platform: Mac + Windows

Mon Dec 02, 2019 8:49 pm Post

tpletcher wrote:
MrBeardie wrote:
tpletcher wrote:I note that the Beta 30 release states dotnet 4.6.2 is required.

I had the same issue initially with Linux Mint but it worked perfectly when I started with a new Wine prefix. Since writing my earlier post in this topic, I've been able to reproduce my success on other distros at work, where each of us in the IT department have our own Linux preferences.


I'll give this a try; thanks.


Unfortunately, I'm getting the same result using a new [Windows 7] prefix. Are there any particular configuration settings I might be missing? I suspect the fact I'm not running dotnet 4.6.2 may be at the root of the problem here, I'm wondering what changed between beta 29 and beta 30 to necessitate breaking Wine compatibility.

User avatar
MrBeardie
Posts: 12
Joined: Tue Nov 12, 2019 6:50 pm
Platform: Mac + Linux
Location: The hills east of Melbourne, Australia

Mon Dec 02, 2019 8:55 pm Post

tpletcher wrote:Unfortunately, I'm getting the same result using a new [Windows 7] prefix.

64 or 32 bit? I don't think dotnet 4.6.2 will install in 32 bit.

I was out of ideas so I thought I'd redo this process a bunch of times to see if I could get it to fail and eventualy it did. On the failed run I noticed that switched the environment to Server 2003 for dotnet 4.5 but failed to switch it back. I also found that after the point of failure, by re-running "env WINEPREFIX=$HOME/wine_scrivener winetricks win7" and then rerunning "env WINEPREFIX=$HOME/wine_scrivener winetricks dotnet462" the install was successful.

Good luck.
Running Scrivener for Windows on Linux Mint 18.3

User avatar
devinganger
Posts: 1791
Joined: Sat Nov 06, 2010 1:55 pm
Platform: Mac, Win + iOS
Location: Monroe, WA 98272 (CN97au)
Contact:

Mon Dec 02, 2019 11:11 pm Post

MrBeardie wrote:
tpletcher wrote:Unfortunately, I'm getting the same result using a new [Windows 7] prefix.

64 or 32 bit? I don't think dotnet 4.6.2 will install in 32 bit.


It's supposed to be compatible with 7-10 x86 or x64 according to Microsoft.

Is there any way to clear the cached downloads and try it again with a freshly downloaded copy of the installer? I'm not familiar with Winetricks...
--
Devin L. Ganger, WA7DLG
Not a L&L employee; opinions are those of my cat
Winner "Best in Class", 2018 My First Supervillain Photo Shoot