SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Normally I wouldn't ask this here, but I'm a bit puzzled - and the helpful folks over in the related wine thread, I believe are puzzled as well.
Planetside2 (free to play game) on wine-1.5.15 (i486) ran relatively "fine" when I was using a stock install (patched up enough to use htop) of 13.37 64 (multi-lib using Alien's packages).
After a clean install of 14.0 64 (again, with Alien's nicely done compat packages, thanks Alien), the launchpad ceased to be able to connect. I've tried wine-1.5.15 (i486 & x86_64) and 1.5.18 (i486 & x86_64). New prefixes, suggested tweaks, etc, and no change. Used a brand new ps2 destination folder (lots of large files to re-download, so easier to copy them over, if the Launchpad ever behaves), deleted the libs folder Launchpad uses, to force it to re-download, nothing changed.
I began to wonder if this was something a bit deeper than wine, on my move from 13.37 to 14.0. (Yes, "things did change", but what would cause it to no longer connect?)
I've tried the change here (preloader complaint showed up, in 14.0) https://www.linuxquestions.org/quest...ilable-855667/ and the result is the same, Launchpad won't connect. (I have reverted back, since no change means that wasn't the problem).
So I ask those who might know Slackware's innards a bit better, is this a wine issue I'm running into, or something I need to set in Slackware?
Where should I begin this search?
(NOTE - The program ran as well as it could, when I was using 13.37 - in 14.0 the Launcher doesn't even connect.)
Further Clarification:
Launcher, if it's lib folder is deleted, does successfully re-download & re-install "itself", its when it goes to connect to whatever is next, that it gets lost. A typical "failure" has the launcher attempting to open a browser to a specific page, and it doesn't even get that far. It's as if it completely misplaces the internet (or it seems that way).
Yes. There is not much to say, unless I run with a full debug or snoop, then and only then does the output seem to suggest it's dying on an "awesomium" process - or around that.
I'd post the related logs, except these are huge, I don't think they'd even fit on here.
From what I assume to be happening, that process is attempting to connect to where-ever it needs to, and just ends up not getting an answer back, then reports as such. Only the launchpad client is "connecting" (to where-ever), as if I remove some of the related files it needs to use (those that have to do with awesomium), it re-acquires them. Then attempts to connect, using what it just re-acquired, only to error out (due to the files it re-acquired, being unable to connect out ... ? .. ??).
Sounds like the same issue DDO Online (DDO) and Lord of the Rings Online (LotRO) has with their launcher. "Awesomium" is a customized port of chromium/webkit. Under WINE most can't seem to get it to work even thought the game client should. Part of the problem might be SSL/TLSv1 authentication, the rest is that Awesomium sucks. Looks like the loader first checks the update/patch level and then tries to log in and can't.
See if you get the error "err:secur32:SECUR32_initSchannelSP TLS library not found, SSL connections will fail" in the CLI when running the loader. There were some changes in openSSH/openSSL for 14.0. In that case, you will need the following Slackware 32-bit packages:
n/nettle
n/p11-kit
Use "convertpkg-compat32" from Alien Bob's multilib stuff and then recompile wine by adding "--with-gnutls=yes" to the configure line. Now, WINE should pick up the missing libs, but seems to be hardcoded (depending on patch version) to ignore gnuTLS.
I also create a clean WINEPREFIX for each games I still run via WINE. That way, optimizations etc for one won't bork another.
Then there are the continued rumors re: a linux port now that they have ported to OS X...
See if you get the error "err:secur32:SECUR32_initSchannelSP TLS library not found, SSL connections will fail" in the CLI when running the loader. There were some changes in openSSH/openSSL for 14.0. In that case, you will need the following Slackware 32-bit packages:
n/nettle
n/p11-kit
Thanks for that reminder kingbeowulf. I have added gmp, nettle and p11-kit to the multilib massconvert32.sh script and refreshed the multilib compat32 package set for Slackware 14 and -current. I am uploading all of that now.
Busy, Busy, Busy. Finally had some time to try things out.
Quote:
Originally Posted by kingbeowulf
Sounds like the same issue DDO Online (DDO) and Lord of the Rings Online (LotRO) has with their launcher. "Awesomium" is a customized port of chromium/webkit. Under WINE most can't seem to get it to work even thought the game client should. Part of the problem might be SSL/TLSv1 authentication, the rest is that Awesomium sucks. Looks like the loader first checks the update/patch level and then tries to log in and can't.
See if you get the error "err:secur32:SECUR32_initSchannelSP TLS library not found, SSL connections will fail" in the CLI when running the loader. There were some changes in openSSH/openSSL for 14.0. In that case, you will need the following Slackware 32-bit packages:
n/nettle
n/p11-kit
Use "convertpkg-compat32" from Alien Bob's multilib stuff and then recompile wine by adding "--with-gnutls=yes" to the configure line. Now, WINE should pick up the missing libs, but seems to be hardcoded (depending on patch version) to ignore gnuTLS.
Tried that, and now it loads successfully! Thank you kindly, kingbeowulf.
Quote:
Originally Posted by Alien Bob
Thanks for that reminder kingbeowulf. I have added gmp, nettle and p11-kit to the multilib massconvert32.sh script and refreshed the multilib compat32 package set for Slackware 14 and -current. I am uploading all of that now.
Eric
And as I'm extremely lazy (or well rested), thank you, for this as well, Eric.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.