Basically when I hit "Play Vendetta" on the update utility, it just crashes. I'm using Linux Mint. Any solutions? I initially posted on the linux board, but it doesnt seem to get a lot of traffic, so i reposted here.

Graphics card: GTX 750 TI
CPU: Intel(R) Core(TM) i3-4150 CPU @ 3.50GHz
OS: Linux Mint 21 Mate

Error log from terminal;

tk-Message: 21:56:36.319: Failed to load module "atk-bridge"

(update.rlb:2427): Gtk-WARNING **: 21:56:36.324: Unable to locate theme engine in module_path: "pixmap",

(update.rlb:2427): Gtk-WARNING **: 21:56:36.324: Unable to locate theme engine in module_path: "adwaita",

(update.rlb:2427): Gtk-WARNING **: 21:56:36.324: Unable to locate theme engine in module_path: "pixmap",

(update.rlb:2427): Gtk-WARNING **: 21:56:36.325: Unable to locate theme engine in module_path: "pixmap",

(update.rlb:2427): Gtk-WARNING **: 21:56:36.325: Unable to locate theme engine in module_path: "pixmap",

(update.rlb:2427): Gtk-WARNING **: 21:56:36.325: Unable to locate theme engine in module_path: "pixmap",

(update.rlb:2427): Gtk-WARNING **: 21:56:36.325: Unable to locate theme engine in module_path: "pixmap",

(update.rlb:2427): Gtk-WARNING **: 21:56:36.325: Unable to locate theme engine in module_path: "pixmap",

(update.rlb:2427): Gtk-WARNING **: 21:56:36.325: Unable to locate theme engine in module_path: "pixmap",

(update.rlb:2427): Gtk-WARNING **: 21:56:36.325: Unable to locate theme engine in module_path: "pixmap",

(update.rlb:2427): Gtk-WARNING **: 21:56:36.326: Unable to locate theme engine in module_path: "pixmap",

(update.rlb:2427): Gtk-WARNING **: 21:56:36.326: Unable to locate theme engine in module_path: "pixmap",

(update.rlb:2427): Gtk-WARNING **: 21:56:36.326: Unable to locate theme engine in module_path: "pixmap",

(update.rlb:2427): Gtk-WARNING **: 21:56:36.326: Unable to locate theme engine in module_path: "pixmap",

(update.rlb:2427): Gtk-WARNING **: 21:56:36.326: Unable to locate theme engine in module_path: "pixmap",

(update.rlb:2427): Gtk-WARNING **: 21:56:36.326: Unable to locate theme engine in module_path: "pixmap",

(update.rlb:2427): Gtk-WARNING **: 21:56:36.327: Unable to locate theme engine in module_path: "pixmap",

(update.rlb:2427): Gtk-WARNING **: 21:56:36.327: Unable to locate theme engine in module_path: "pixmap",

(update.rlb:2427): Gtk-WARNING **: 21:56:36.327: Unable to locate theme engine in module_path: "pixmap",

(update.rlb:2427): Gtk-WARNING **: 21:56:36.327: Unable to locate theme engine in module_path: "pixmap",

(update.rlb:2427): Gtk-WARNING **: 21:56:36.327: Unable to locate theme engine in module_path: "pixmap",

(update.rlb:2427): Gtk-WARNING **: 21:56:36.327: Unable to locate theme engine in module_path: "pixmap",

(update.rlb:2427): Gtk-WARNING **: 21:56:36.327: Unable to locate theme engine in module_path: "pixmap",

(update.rlb:2427): Gtk-WARNING **: 21:56:36.327: Unable to locate theme engine in module_path: "pixmap",

(update.rlb:2427): Gtk-WARNING **: 21:56:36.327: Unable to locate theme engine in module_path: "pixmap",

(update.rlb:2427): Gtk-WARNING **: 21:56:36.328: Unable to locate theme engine in module_path: "pixmap",

(update.rlb:2427): Gtk-WARNING **: 21:56:36.328: Unable to locate theme engine in module_path: "pixmap",

(update.rlb:2427): Gtk-WARNING **: 21:56:36.328: Unable to locate theme engine in module_path: "murrine",

(update.rlb:2427): Gtk-WARNING **: 21:56:36.328: Unable to locate theme engine in module_path: "murrine",

(update.rlb:2427): Gtk-WARNING **: 21:56:36.328: Unable to locate theme engine in module_path: "pixmap",

(update.rlb:2427): Gtk-WARNING **: 21:56:36.329: Unable to locate theme engine in module_path: "murrine",

(update.rlb:2427): Gtk-WARNING **: 21:56:36.329: Unable to locate theme engine in module_path: "murrine",

(update.rlb:2427): Gtk-WARNING **: 21:56:36.329: Unable to locate theme engine in module_path: "murrine",

(update.rlb:2427): Gtk-WARNING **: 21:56:36.329: Unable to locate theme engine in module_path: "murrine",

(update.rlb:2427): Gtk-WARNING **: 21:56:36.330: Unable to locate theme engine in module_path: "pixmap",

(update.rlb:2427): Gtk-WARNING **: 21:56:36.330: Unable to locate theme engine in module_path: "pixmap",

(update.rlb:2427): Gtk-WARNING **: 21:56:36.330: Unable to locate theme engine in module_path: "pixmap",

(update.rlb:2427): Gtk-WARNING **: 21:56:36.330: Unable to locate theme engine in module_path: "murrine",

(update.rlb:2427): Gtk-WARNING **: 21:56:36.330: Unable to locate theme engine in module_path: "pixmap",

(update.rlb:2427): Gtk-WARNING **: 21:56:36.330: Unable to locate theme engine in module_path: "pixmap",
vendetta: error while loading shared libraries: libssp.so.0: cannot open shared object file: No such file or directory

Basically, GTK is a library that handles things like windows and styling, to make apps fit within a desktop environment. It does some of the basic functionality that on other platforms is handled by some kind of long-term "OS standard" (on Android, MacOS, Windows, etc).

The game currently links against the older GTK2, rather than 3 or 4. This recently came up on a Suggestions thread. We weren't aware that GTK 2.x was "end-of-lifed" in 2021, but I imagine some aggressive distros have dropped it as a result.

We aren't the only app still using it, a lot of people do, which is why Debian hasn't dropped support (Ubuntu is our test-case for the game). Even Mozilla was still using it until relatively recently.

Anyway, I'm not that familiar with Mint, but you'll likely need to install some kind of gtk2 library package.

We have it marked on our TODO to at least update to gtk3, but it hasn't happened yet (we weren't aware of this issue until last week).

Unfortunately, gtk has been kind of terrible about maintaining compatibility between versions, and Linux has no "unified" OS standard, so people have to recompile their apps periodically for shifting library preferences, or kind of "guess" at which distributions are still shipping what libraries, and so on.

Eventually we intend to dump GTK entirely and move to some other internal system that don't require us to rely on any outside Linux distribution capabilities. But, that's a more significant undertaking.

okay. I did as you suggested and installed gtk2 (i think) via the command

sudo apt-get install gtk2.0

and it didnt seem to make any difference. it still crashed after hitting "play vendetta". I think that this line:

vendetta: error while loading shared libraries: libssp.so.0: cannot open shared object file: No such file or directory

has to do with the game crashing because it shows up in the log after i hit "play vendetta" and the game crashes.

not sure what to do.

Are you running the 32bit game for Linux, or the 64bit game for Linux?

Do you have 32bit Linux or 64bit Linux installed?

There does not appear to be a Linux mint package named "gtk2.0":

http://packages.linuxmint.com/search.php?release=any§ion=any&keyword=gtk2.0

It appears there is a package in the extended "Community" repository, called libgtk2.0-0

https://community.linuxmint.com/software/view/libgtk2.0-0

I am using the Linux IA32 version of the linux client. my architecture is x86_64.

Basically, this:

vendetta: error while loading shared libraries: libssp.so.0: cannot open shared object file: No such file or directory

Means you are missing a library, which is GTK. The game itself isn't exhibiting a bug, but rather, from the game's perspective, the OS is incomplete.

Dealing with "dependencies" of this kind are part of the challenge of using Linux.

I am using the Linux IA32 version of the linux client. my architecture is x86_64.

If you have an x86_64 machine, you want to run x86_64 software. I would suggest installing the 64bit version for starters.

It's a little confusing in the download section because it says that IA32 is also known as x86. So, I should be using the AMD64 version of the client? I did try using that version of the client, but it gave me another set of completely different errors, also failing to boot.

I would suggest using AMD64, yes. The information on the download page uses some dated terminology (64bit was called "AMD64" before it was called "x86-64").

However, neither version of the game is going to load without you installing GTK2 libraries.

You may be able to do something like:

sudo apt-get install libgtk2.0-0

To install GTK. But, I'm not sure, because you may need to expand your repository settings to beyond the defaults to get community-compiled content.

Again, I don't know much about Mint.

according to my package manager, I have libgtk2.0-0 installed. I installed the AMD64 version of the client just now, and here is the error that I got after clicking "play vendetta" (the client crashed after I clicked the button);

X Error of failed request: BadRRCrtc (invalid Crtc parameter)
Major opcode of failed request: 140 (RANDR)
Minor opcode of failed request: 20 (RRGetCrtcInfo)
Crtc id in failed request: 0x0
Serial number of failed request: 18
Current serial number in output stream: 18

So, to be clear.. which of these is happening?

1) You run the game, you see the "Game Launcher" start up and check the game state and perhaps patch the game, and then you click "Play" and after that it exits with these errors?

OR

2) From the very first moment you attempt to run the game, you see this set of errors? No game launcher, no patching, no nothing.

I launched the client, which shows the launcher, it checks for update, I click "play vendetta" and it immediately crashes, showing me the errors that I posted. So in other words, option 1.

Okay. Next questions:

1) Is there anything unusual about your monitor setup? Like do you have an external monitor, but it's disabled? Or you're playing on a laptop with an internal monitor that's turned off, but using an external monitor? Or just.. several monitors of different sizes?

2) Have you tried running anything else that uses 3D, like other games? Tux racer.. whatever?

1: No, I have one monitor directly connected to my graphics card via HDMI, there's nothing unusual about my setup.

2: Yes, I've played Eldritch which is a steam game, I had no issues running it.

Okay, this issue sounds more like a legitimate bug that we can look into.

I'll have to get back to you. I don't have a solution now, we'll need to investigate further.

We implemented the XRandR support relatively recently, at player request, as it better supports modern displays and resolutions. I thought it was pretty robust, as of the last update, but.. I dunno, we have to investigate.

Sorry for the delay.

no problem, I appreciate you looking into my issue. I'll wait for the bug to be fixed.

Okay, I'll need you to try getting us some debugging information first:

- There's an important game config file, located in:

~/.vendetta/config.ini

(that's your home directory, in ".vendetta").

- The file is generated on first runtime, so it may or may-not exist on your machine. Either edit it (if it exists) or create it (if it doesn't already exist) and add this:

[refgl]
do_logging=1
xrandr=1

[gl4]
do_logging=1
xrandr=1

- If the file already exists, you'll find pre-existing sections that are labeled like the above entries, but have more configuration parameters. Just add the above "xrandr" and "do_logging" parameters into the existing [refgl] and [gl4] entries.

- If the file doesn't exist, you can completely use the above as the entire config.ini.

- Then run the game again. It should still crash, but it will generate some log files:

openglerr.log

OR

opengl4err.log

Please paste the output of those files (either one) into this forum thread.