-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
libwebkit2gtk-4.0 not available in Ubuntu 24 & Debian 13 repositories #9662
Comments
This comment was marked as duplicate.
This comment was marked as duplicate.
Have you already solved this bug? |
see Ubuntu 24.04 LTS: error while loading shared libraries: libwebkit2gtk-4.0.so.37 sudo nano /etc/apt/sources.list.d/ubuntu.sources add this as it shows: then
for my development env, this woks |
for end user, use |
This is a bit dirty. It is recommended to restore /etc/apt/sources.list.d/ubuntu.sources to its original state after installing libwebkit2gtk-4.0-dev. Otherwise there will be weird errors, this is the one I'm currently experiencing: on kububtu,when Double-click the deb package, will install the deb using the QApt graphical interface by default (i.e. qapt-deb-installer) Double-click google-chrome-stable_current_amd64.deb 125.0.6422.112. It will originally prompt a dependency unsatisfied error in the QApt interface, but it can actually be installed using apt or dpkg after changing /etc/apt/sources.list.d/ubuntu.sources and apt update Double-clicking google-chrome-stable_current_amd64.deb 125.0.6422.112 does not prompt a dependency not satisfied error in the QApt interface, but displays that many dependencies need to be deleted. These dependencies are necessary for the system, including the desktop environment, desktop keyboard and mouse input devices, input methods, etc. Many contents and some installed software will be deleted. According to actual test, using apt to install this deb will automatically change to use the package in the server without causing problems. In addition, dpkg -i has not been tested. I don’t know whether apt install -f is required and whether it will cause problems. |
Your workaround doesn't work:
I tested also on Kali and there is a conflict with libjpegturbo0. So now, it is unable to use tauri on latest Ubuntu LTS / Kali |
The workaround in the OP worked on a clean Ubuntu 24.04. |
might who “Packaging these dependencies from ubuntu22.04 for installation on ubuntu24.04, and distinguishing between non-dev and dev versions “ can solve this problem? |
Not functional on Debian Testing (Trixie) / Unstable (sid), the package is not added to the repositories. Installing It's pretty much a show-stopper, there's no workaround atm. |
I'm thinking of switching my project to Tauri 2.0 beta right now so that it uses |
That will depend on the value of switching to you. I've switched because I want to try some the new features and it seems good but I'm aware some issues I have could be with v2 beta, especially as I'm pushing she boundaries. But finding issues is the point of a beta, and my using it. No better time to get things fixed fast! My app is though a demo not production so it won't be a disaster if I hit bugs, but so far it seems stable. The docs are a bit patchy and fluid, but the support I've had more than make up for that. |
I don't see 4.1 in my Ubuntu 20.04 VM. Does that mean it's not possible for the same binary to support both 20.04 and 24.04? I'm trying to think of workarounds I could do... maybe a shim script that launches either a 4.0-linked binary or a 4.1-linked binary after probing for libraries? It might work with Tauri's deb bundler, with some creativity, or I could hack around it. But if that means simultaneously building for both Tauri 1.x and 2.x it would be too much effort. Unless 2.x has a compromise between deb and AppImage where I can install systemd services and have post-install and pre-remove scripts, but also bundle WebKit. |
@ReactorScram I built on Ubuntu 24 after using the fix from the OP and in very early testing people found that the following worked:
The following did not work:
|
If you built your app on 24.04 none of what you wrote is supposed to actually work due to glib not being backword compatible like this (basically the reason for "build on the oldest system you want to support"), so i'd be very careful with that approach. |
@FabianLars that's exactly what I expected yet those are the facts! 🤷♂️ ... so far. |
This comment was marked as duplicate.
This comment was marked as duplicate.
After updating to tauri v2, I no longer have any issues on ubuntu 24. So we have resorted to updating our app fully from V1 to V2 |
Had the same issue, installed libwebkit2gtk-4.1-dev with |
This issue most probably no longer applies since tauri v2 is now table |
Is v1 officially deprecated and out of support? In this case the issue would be irrelevant. |
deprecated? yes with the general state of linux support (in tauri etc) i have to say though that i doubt this issue will get properly solved. |
Okay, maybe then this issue needs to be acknowledged in the Docs and the only solution to be is to upgrade to v2. And we can close this issue. |
Any docs change should also mention the reverse issue (dropping support for CentOS etc). Something like Tauri v1 requires
Tauri v2 requires
|
I thought tauri (in future) would actually move to verso instead of libwebkitgtk on linux at least |
Also, what are the real possible alternatives of webkitgtk2 for linux I also think webkitgtk2 in itself, isn't that great either (good performance issues in my app + unfired events etc) |
Yes, we want an alternative to webkitgtk but this is irrelevant for this issue because a) it needs a lot of time and b) it would not be backported to v1 (and probably not to v2 either) |
(Posting in case someone else ran into the same problem and needed a quick "No it's impossible") There's no way to get a v1 and a v2 project into the same workspace, right? We're looking at keeping Ubuntu 20.04 support for another few months so it Would Be Nice if the v1 project could stay in our workspace, but it might just be dropped |
It's indeed not directly possible to mix v1 and v2 in the same workspace without feature flags (at which point i'd personally just remove it from the workspace) |
And How to build tauri2.0 in Debian 11? |
Debian 11 doesn't have webkitgtk 4.1 so you can only build it inside docker or something like this but that built app will likely not run on debian 11. |
@alicard What's the distro version you're trying to install it on? Like we said above, Debian 11 and below and Ubuntu 20.04 and below do not have the webkitgtk version we need for Tauri v2. |
hey, are you thinking to release an fix for this or we still have to play with an workarounds? :) |
Most probably there will be no fix, because tauri v1 is kinda like deprecated now |
Deprecated may be a bit harsh (or maybe not since I said the same above...) but I also don't expect us to fix this / add a workaround at this point tbh. We wouldn't turn down any community contributions of course but I don't expect to see any. I still don't know if it is even technically possible to reasonably solve this (not talking about completely replacing 4.0 with 4.1 in v1 because that makes no sense). |
Describe the bug
The Tauri v1 pre-requisite
libwebkit2gtk-4.0-dev
is not available in Ubuntu 24 repositories. This causes an error when installing the pre-requisites specified here, and when runningcargo tauri dev
on Ubuntu 24.Note:
libwebkit2gtk-4.1-dev
is available but doesn't help with Tauri 1.Reproduction
Run:
reports:
And
cargo tauri dev
:Workaround
I worked around this by adding the following line to /etc/apt/sources.list:
deb http://gb.archive.ubuntu.com/ubuntu jammy main
Then doing:
IMPORTANT: it was recommended in this comment to undo the change to
sources.list
after installing to prevent problems with dependencies being deleted.Expected behavior
no errors
Full
tauri info
outputStack trace
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: