Gtk Incompatible issue in vtune-gui. How to solve it ? Thx.

[nmeng]

[SJLim_intel]

We've reached out to our development team about this vtune-gui issue.

Meanwhile, please check environment variables for GTK conflicts. Make sure you are not setting any environment variables (like LD_LIBRARY_PATH) that might cause the wrong GTK libraries to be loaded.

Also, we recommend try using "Remote Linux Target" or "VTune Profiler Server" features from host system rather than vtune-gui from the Linux target system.

User Guide:

VTune Profiler Server

https://www.intel.com/content/www/us/en/docs/vtune-profiler/user-guide/2025-4/use-vtune-profiler-server.html

Remote Linux Target

https://www.intel.com/content/www/us/en/docs/vtune-profiler/user-guide/2025-4/remote-linux-target-setup.html

[WiserOrb]

Any news on this front? It's still broken as of 26/08/2025

[NR_qs]

An issue for me, as well.

I'm on Fedora 42, using GNOME 48.4 on Wayland.

❯ ./vtune-gui

(process:97648): Gtk-ERROR **: 17:13:12.449: GTK 2/3 symbols detected. Using GTK 2/3 and GTK 4 in the same process is not supported
fish: Job 1, './vtune-gui' terminated by signal SIGTRAP (Trace or breakpoint trap)

Yet, running ./vtune-gui --help does work - as does running vtune-self-checker.sh

I'm attaching the output of running it with strace.

[optimizergal]

It seems like it might be trying to use a library related to Gnome that uses GTK 4. Can you try adding --gtk-version=3 after vtune-gui? It would be nice if there was more documentation related to the Linux GUI.

[WiserOrb]

I get an error:

Unknown arguments: gtk-version, gtkVersion

Furthermore this is an option used for electron apps. I don't know if vtune is one.

If true, developers should expose the option. Btw the issue is fixed in more recent electron version, so they could update it.

[NR_qs]

Linking the Electron 36 issue for posterity

[optimizergal]

Thanks for the response - I generally use VTune in CLI or web server on Linux, and last I remember it used wxWidgets. Since there was no Intel answer, I thought maybe a solution for the error in a different app might work.

From what I can tell of the logs from the other person, it loads GTK 3, then later connects to X11/X0, then loads mutter/wayland, and then GTK 4. Maybe somewhere there is a workaround; I'm not familiar enough with X11 or Linux GUI to know.

Otherwise I generally set up the web server for profiling on Linux, since I tend to use a remote server where setting up VNC is a pain. You can try that as a workaround. 

https://www.intel.com/content/www/us/en/docs/vtune-profiler/cookbook/2025-4/profiling-applications-in-aws-ec2-instances.html

If you're not running on AWS, you can skip to the Run VTune Profiler as a Web Service section:

1. Run the VTune Profiler Web Service:

   <vtune_install_dir>/latest/bin64/vtune-backend –-allow-remote-access –-enable-server-profiling –-web-port=8080

   The vtune-backend command returns a URL with the private IP for the instance as well as a one-time token.

2. Replace the private IP with the public IP or DNS for the instance. For example, https://172.29.129.54:8080/?one-time-token=b8cafc89721e781161aba4ddcef5a718 becomes https://18.236.194.236:8080/?one-time-token=b8cafc89721e781161aba4ddcef5a718.

3. Copy the URL into your browser.

[KyleCascade]

I had the same problem on my Ubuntu machine.

Downgrading vtune to 2025.3.0-15 allowed me to go back to a version that worked.

sudo apt install intel-oneapi-vtune=2025.3.0-15

(Using the APT method of installation)

[cristian64]

GTK 2/3 symbols detected. Using GTK 2/3 and GTK 4 in the same process is not supported

Reproducible on Linux Mint 22.x (MATE) too with current latest VTune version:

$ vtune --version
Intel(R) VTune(TM) Profiler 2025.8.0 (build 631311) Command Line Tool
Copyright (C) 2009 Intel Corporation. All rights reserved.

Any update on this? Is it possible to find links to old offline installers to work around this?

[cristian64]

I was able to find the offline installer of a working build: intel-vtune-2025.3.0.18_offline.sh

(It seems the regression was introduced in 2025.4.0.xx; older builds appear to work.)