Upgraded to Ubuntu 14.04 from 13.10--No Continuum

[Werew]

The title should read Upgraded to Ubuntu 14.04 from 13.10--No Continuum.  I edited the title right before I posted and somehow left the important information out, sorry.

 

I updated Lubuntu.  Trying to open Continuum now has Continuum.exe showing up in Task Manager and CPU usage jumping to and staying at 100%, but no Continuum window appears.  Multiple instances of Continuum.exe can be run.  This used to give an error from Wine.  Notepad opens fine using Wine.  My current Wine version is 1.6.2.  Is anyone else having issues after updating?

Edited April 30, 2014 by Werew

[Werew]

Just a little update on this.  I uninstalled and reinstalled Wine and Continuum, and I rereplaced kernel32.dll.so with doc flabby's modified version in case the upgrade fucked it up.  Result?  Continuum doesn't open at all.  It pops up for a moment in Task Manager and then it's gone.  So it changed at least.  That's good?

 

I'm pulling my hair out over this.  Nobody else is having this problem?  Could someone please tell me they're not having this problem with Ubuntu 14.04 so I can only look at changed files pertaining to Lubuntu?

Edited May 10, 2014 by Werew

[Werew]

I'm starting to think this has something to do with LXDE, not Ubuntu.  I'd really appreciate anyone else using Ubuntu just telling me you don't have a problem.  I'm honestly losing my mind over the lack of replies here.

 

Also, is there anyway to let me fix the title to what I meant to put so it doesn't sound so retarded?

Edited May 21, 2014 by Werew

[JoWie]

Is it supposed to work unpatched nowadays? If so I can try on kubuntu trusty

[Werew]

No, it's not supposed to work unpatched.  Thanks for the offer though, JoWie.  I thought there were more SubSpace players on Linux.  If I find anything else about my problem on my own, I'll be sure to post it.   

 

If anyone else wants to give it a go, it was working with Wine 1.6.2 in Lubuntu 13.10 and won't work in 14.04 with this file replaced: http://www.subspace.co/topic/26553-please-someone-update-continuum-40-for-linux-how-to/?p=283626

[JoWie]

Has this issue ever been reported to wine?

This patch seems like a very dirty hack, it prevents any process from using WriteProcessMemory.

[Werew]

Sorry for the slow response, JoWie.  I wanted to do a search through bugs.winehq.org/ rather than say, "I dunno."  Searched for "openprocess", "continuum", and "subspace".  The answer is yes, and no.  The closest report to what you are talking about is here: http://bugs.winehq.org/show_bug.cgi?id=22006 .  It looks as though nobody gives a flying fuck, since the bug has been open for over four years.  It's also mentioned here: http://bugs.winehq.org/show_bug.cgi?id=21702 although that's not about OpenProcess so much as Continuum acting up.

 

I have to also say I don't know what all this "OpenProcess" and "PROCESS_VM_WRITE" stuff is.  My programming knowledge is just enough to get by with computations in Mathematica, MATLAB, LabVIEW, and VBA

 

Edit: Tried to fix the second link, but I can't figure it out.

Edited June 5, 2014 by Werew

[JoWie]

My experience with winapi is limited, but from what I understand is.

 

You can create a process using a security descriptor to provide a DACL:

http://msdn.microsoft.com/en-us/library/windows/desktop/ms682425%28v=vs.85%29.aspx

http://msdn.microsoft.com/en-us/library/windows/desktop/aa379560%28v=vs.85%29.aspx

http://msdn.microsoft.com/en-us/library/windows/desktop/aa379561%28v=vs.85%29.aspx

 

What I am guessing is that continuum does this in such a way that PROCESS_VM_WRITE is not allowed, and it checks for it (if not present,  you experience the never ending spawning of continuum.exe).

If you open a process using PROCESS_VM_WRITE you can use the method WriteProcessMemory to modify the memory of the process. This is a common method for cheats, trainers, etc.

This protection is simply to bypass though, by giving your process (the trainer) SeDebugPrivilege ( http://msdn.microsoft.com/en-us/library/windows/desktop/aa446619%28v=vs.85%29.aspx ).

 

Wine does not check the DACL in OpenProcess, so continuums check fails ( http://source.winehq.org/source/dlls/kernel32/process.c?v=wine-1.7.19#L2930 ).

 

From that test case it looks like Wine implements all those security functions:

http://source.winehq.org/source/dlls/advapi32/security.c?v=wine-1.7.19

http://source.winehq.org/source/dlls/ntdll/sec.c?v=wine-1.7.19

 

and they are also stored when creating the process:

http://source.winehq.org/source/dlls/kernel32/process.c?v=wine-1.7.19#L1925

 

So it seems like resolving http://bugs.winehq.org/show_bug.cgi?id=22006 in a proper way would be that hard, most is already in place.

I *might* give it a shot.

I just worry about getting all the little details right in an identical way to windows, so lots of test cases are needed.

 

Also, cheating in continuum from within Wine would be interesting. Seems much easier to bypass most of the checks.

Edited June 6, 2014 by JoWie

[Werew]

JoWie, I really appreciate you trying to help me with this.  It's taking me a while to reply to your comments because most of the the stuff you're talking about it is way over my head.  I'll try and learn what some of these programs and acronyms are over the next few days so I can give an intelligible response.

 

In the mean time, I think I've found a laptop without Wine or Continuum on it that is running Lubuntu 13.10.  If so, I'll see what I can find out with the extra set of hardware.

[JoWie]

That hack on wine.getcontinuum still works (I just tried it), but you need to compile wine from source yourself.

 

Anyway, what I have figured out so far is that Wine implements SetSecurityInfo and GetSecurityInfo. It ignores the given SECURITY_DESCRIPTOR in CreateProcess though. So that will need to be added first, after that doing the proper check in OpenProcess should fix the issue in a clean way.

[Werew]

OK.  So I drunkenly tried figuring this out with my laptop and PC about two weeks ago, and got so confused I decided it best not to post at the time.  Most of my notes in Leafpad have disappeared, and I'm not posting the terminal file where I tried to download the dependencies for Wine 1.6.1 so I could go back to it.  Likewise, I couldn't figure out how to install Wine 1.5.  Long story short, I was wrong.  I was running Wine 1.6.1 on Lubuntu 13.10.  It automatically upgraded to 1.6.2 when I upgraded to Lubuntu 14.04 LTS.  I can also say that Continuum won't run on Lubuntu 13.10 and Wine 1.7.18, or Lubuntu 14.04 and Wine 1.7.19.  I'll post more when I get time to look into this again.

 

Edit:  I did a little bit more research tonight.  With Lubuntu 14.04, I tried loading Wine 1.7.20.  On my system, the patched kernel32.so.dll file prevents Wine 1.7.20 from running at all.  No Configure Wine.  No Notepad.  Reverting to the stock kernel32.so.dll solves the problem.

Edited June 27, 2014 by Werew

[JoWie]

I managed to get continuum working (the clean way). And at the moment I am busy getting the patches through their submission procedure. (this will probably take a few more days).

 

If this succeeds, you would be able to get continuum to work by just installing the wine beta (I am hoping Wine 1.7.22). You can install the beta from a repository: http://www.winehq.org/download/ubuntu

 

 

If you want that hack to work you need to compile wine yourself, replacing that so file will only work if it exactly matches the correct wine version. The easiest way to compile wine is to set up a virtual machine with a 32 bit linux flavor.

Edited June 29, 2014 by JoWie

[Werew]

I'm about to drive to Florida from Houston right now, so I think I'll wait.  I don't want to sound like a broken record, but thanks again for working on this long standing problem, JoWie.

[Gruntster]

I was wondering why I haven't seen you in game for quite some time Werew. Get windows

[Werew]

Well, you know I've got a Windows 95 PC back in Houston.  Problem being I'm not in Houston at the moment, and to plug it in I have to squirm like a fish under the desk unplugging and plugging in tangled cables.  Apart from visiting my family right now, I'm trying to finish up things to get my masters degree.  Going out of my way to play SubSpace isn't really an opition.

 

What really miffs me though is the fact that, out of all the SubSpace players on Linux, I'm the only one that crawled out of the woodwork on this one.  I'm looking at you, Cool Dad.

Edited July 2, 2014 by Werew

[»Nude For Satan]

What really miffs me though is the fact that, out of all the SubSpace players on Linux, I'm the only one that crawled out of the woodwork on this one.  I'm looking at you, Cool Dad.

Chaos-Obsrvr-Bot> 'cool dad' last seen 2013-12-08 14:45:41

... maybe for this very reason!

[Werew]

 

Chaos-Obsrvr-Bot> 'cool dad' last seen 2013-12-08 14:45:41

... maybe for this very reason!

 

 

Sonofabitch.  He's not one to read the fourms and might never have updated the zone list after everything went down.  I think tommygun might have his e-mail.  I'll see if he can't be contacted.

[JoWie]

I just got back from vacation, but I am going on another vacation tomorrow.

 

A bunch of my patches got in, but not yet enough of them to make continuum work.

 

In the mean time you could try wine-compholio which should have the patches you need to run continuum: https://launchpad.net/~ehoover/+archive/ubuntu/compholio

Edited July 31, 2014 by JoWie

[JoWie]

Here's a guide:

 

 

sudo apt-add-repository ppa:pipelight/stable
sudo apt-get update
sudo apt-get install wine-compholio
wget http://www.getcontinuum.com/downloads/continuum/Continuum040Setup.exe
/opt/wine-compholio/bin/wine Continuum040Setup.exe
    # click cancel on the dialog boxes that complain about mono (.NET) and gecko, they are not needed for continuum
    # Install to C:/Continuum/ so that the path easier to type
/opt/wine-compholio/bin/wine ~/.wine/drive_c/Continuum/Continuum.exe

[X-Demo]

Sweet, thanks Jowie!  So glad I didn't have compile wine this time around, the compilation process for wine (for running win32 binaries) on 64-bit Linux looked particularly annoying .

 

Anyways, works for me on Mint 17.