Wine/Fedora blocking TCP ports?

[DigitalMan]

I'm trying to install 3ds Max 2009, which is supposed to just work after a couple extra components are installed and a bit of a workaround to access the .msi directly.

I get to the point where it asks whether I want to install mental ray services, which of course I uncheck because that is known to have problems (and I don't need it anyways). But, it still pops up a dialog, claiming, "The TCP port you selected to configure the mental ray Satellite service is already in use." This has two obvious issues - one, I told it not to do that, so it shouldn't even be trying, and two, the port is definitely not in use. This warning comes up regardless of which port I type in.

Since this has never been recorded in the multiple tests documented, and it behaves the same with various versions of Wine as far back as 1.3 and as new as 1.7.15, I can only assume the issue lies with my system specifically, quite possibly with Fedora's recently introduced firewalld service. Though I've certainly done everything in my power to obliterate firewalld, so it may even be something else.

Mind you, I can't say I'm necessarily looking for a solution that allows it to access the port. The installer has simply derped, and the thing it's aiming to do will never benefit me in any way. I would be perfectly happy with tricking the program into believing it is actually listening on a port, but that doesn't seem to be something that's been tried before, either.

Really, any sort of solution to get past this one step would be appreciated.

[dimesio]

Post terminal output from 1.7.15.

[DigitalMan]

Well, if you insist:

Code: Select all

fixme:process:SetProcessShutdownParameters (00000380, 00000000): partial stub.
fixme:wtsapi:WTSQuerySessionInformationW Stub (nil) 0xffffffff 4 0x86e654 0x86e644
fixme:storage:create_storagefile Storage share mode not implemented.
fixme:wtsapi:WTSQuerySessionInformationW Stub (nil) 0xffffffff 4 0x86e650 0x86e640
fixme:wtsapi:WTSQuerySessionInformationW Stub (nil) 0xffffffff 4 0x86e650 0x86e640
fixme:wtsapi:WTSQuerySessionInformationW Stub (nil) 0xffffffff 4 0x86e694 0x86e684
fixme:ole:RemUnknown_QueryInterface No interface for iid {00000019-0000-0000-c000-000000000046}
fixme:ole:RemUnknown_QueryInterface No interface for iid {00000019-0000-0000-c000-000000000046}
err:ole:CoReleaseMarshalData IMarshal::ReleaseMarshalData failed with error 0x8001011d
fixme:ole:RemUnknown_QueryInterface No interface for iid {00000019-0000-0000-c000-000000000046}
err:ole:CoReleaseMarshalData IMarshal::ReleaseMarshalData failed with error 0x8001011d
fixme:wtsapi:WTSQuerySessionInformationW Stub (nil) 0xffffffff 4 0x86e654 0x86e644
err:richedit:ReadStyleSheet skipping optional destination
err:richedit:ReadStyleSheet skipping optional destination
((Times a few hundred...))
err:richedit:ReadStyleSheet skipping optional destination
fixme:msi:event_spawn_wait_dialog doing nothing
err:msi:ITERATE_Actions Execution halted, action L"Welcome_Dialog" returned 1602
fixme:wtsapi:WTSQuerySessionInformationW Stub (nil) 0xffffffff 4 0x86e650 0x86e640

The only thing of note is that, if I go back to the previous installation step, and then forward, it will give the "event_spawn_wait_dialog doing nothing" line each time. Everything before that line is from a previous step, and everything after it is from cancelling the installation. The actual act of trying to proceed doesn't produce any output by default.

[oiaohm]

DigitalMan is the port under less than 1025. Under 1025 is for root/services only. I have had a few people where the case was typing in too small of port number.

[DigitalMan]

DigitalMan is the port under less than 1025. Under 1025 is for root/services only. I have had a few people where the case was typing in too small of port number.

No, both the program and the person running it are smarter than that It defaults to 7509, and I've tried a suitable amount of different ports to safely declare that none work.

[DigitalMan]

The issue has been "resolved" by spinning up an Ubuntu 12.04 LTS LiveCD, mounting my desired prefix folder, and running the installation there (plus a few little steps to make Wine stop whining). Even with Wine 1.4, it worked quite nicely, effectively proving that this is not a Wine issue, but an issue with either my specific setup, or Fedora in general.