Quote:
Originally Posted by Nille_kungen
Did you get Dues Ex working?
|
No and I have almost given up, at least on this system as it is. After years of multi-booting, I'd really like to have just one OpSys that does everything I need and although I have been very close for over a decade with Slackware uptimes of over 6 months, a few minor items still require a reboot to a different system. This has recently increased with the combination of pulseaudio and especially devs who build 64bit only apps. 32bit is straightforward and easy while multilib adds a layer of complexity. I still have a Slackware 14.0 32 bit system upon which everything works exactly as I want it to except, just lately, for 64 bit only apps.
The two areas that cause me grief are DAW work and gaming. Currently Jack Connection Kit, an absolute requirement for DAWs, is limited with pulseaudio, making that more complex and difficult. As for gaming, Wine has become really very good but I'd like to support Steam for a variety of reasons yet there are enough variables that are much more difficult to troubleshoot it has led to this floundering around.
My plan at this time is to install an alternate Slackware64 with an untouched pulseaudio and the bare minimum for Steam and see if that changes anything. I may also try an alternate install where Bluetooth and Pulse are entirely ruled out and see how far "apulse" gets me.
Only a month ago I was almost decided to go back to 32bit but now there are not just one but several 64bit-only apps important to me that lead me to believe the "writing is on the wall" and that I have little choice but to work with multilib. I'm not as certain about Pulse so I need to sort that out. I think it is pretty much inevitable but if there's a window of a year or two before that becomes inescapable I'll go with that.
Specific to this thread: I can't sort why or exactly how I discovered krb5 was an issue and if that implies there was something broken in Steam-Runtime. This thread has given me enough answers that I can narrow down my approach and cease the far less effective (often confusing) "shotgun approach" so while it's a bit of a pita I think I need to pare down and bite the bullet for one or more multilib testing installs. That will have to wait for the weekend but that's not long so I will post back what I learn then.