Missing libxcb-cursor0 causes version 2.9.2 to crash
#378
Comments
|
There hasn't much changed since v2.9.1 except the build system. Can you try if v2.9.1 works fine? It is possible that we need to include additional libraries within the AppImage that are not available on all distributions.
Can you check whether |
|
ProtonUp-Qt-2.9.1-x86_64.AppImage works.
I did a sanity test and re-downloaded v2.9.2 but got the same results in original post. |
|
Okay. Are you running X11 or Wayland? You can check by running: Can you also try installing If that helps, I will check whether we can include the libxcb-cursor0 within the AppImage file |
|
From a quick search, it seems like Linux Mint at least does not include |
|
Installing I'm running X11. |
|
I wonder why it doesn't find your Steam directory. Where is Steam installed on your computer? And does v2.9.1 find your Steam directory? You might have to clear your custom Steam directory from |
Okay, let's see if others report the issue as well. If that is the case, we may need to include it in the AppImage.
Strange, works for me. Is there a case where the stricter checks added with #356 may break something? @Jed28 can you run following commands and upload the output here? Thanks. ls ~/.local/share/Steam
ls ~/.local/share/Steam/config
ls ~/.steam/root
ls ~/.steam/root/config
ls ~/.steam/steam
ls ~/.steam/steam/config
ls ~/.steam/debian-installation
ls ~/.steam/debian-installation/config |
DavidoTek
changed the title
libxcb-cursor0 causes version 2.9.2 to crash
|
v2.9.1 finds it automaticity. I removed the config file |
|
Hm, that all looks correct. Although what is the "real" Steam install from apt? I don't use any distro with apt so it's not clear to me where the default is. If you put an (empty) I'm wondering if maybe some of the changes made in v2.9.1 need to better follow symlinks or something. |
|
Looking at the changes for #356, it may actually be the opposite problem. I just tested with This is probably something to do with how we're using This might be a bit tricky, because we use Maybe we just need to take a look at how we use We use ProtonUp-Qt/pupgui2/constants.py Line 29 in 23b60df We then use Line 213 in 64ec6d0 If we assume When working on #356 I didn't consider symlinks being used in this way. In fact, I'm pretty sure a lot of ProtonUp-Qt doesn't account for symlinks in this way when working with relative directories (for example with Lutris). I think using a symlinked folder for the launcher folder is going to cause problems with other launchers too in different ways (it may find them but it may not install correctly). This needs some consideration on how and if to handle... One solution may be to use See this StackOverflow answer.
Sample snippet: import os
user_dir = os.path.expanduser('~')
# Ensure compatibilitytools.d is a symlink for testing
# For example let's assume it's pointing to `/tmp/compatibilitytools.d`
steam_root = '/.local/share/Steam/compatibilitytools.d'
compat_tools_dir = os.path.join(user_dir, steam_root) # Path might be: '/home/user/.local/share/Steam/compatibilitytools.d'
steam_install_dir_realpath = os.path.realpath(os.path.join(compat_tools_dir, '..')) # Would return '/tmp'
steam_install_dir_abspath = os.path.abspath(os.path.join(compat_tools_dir, '..')) # Would return '/home/user/.local/share/Steam'I just tested and using |
|
#381 should fix it, but there may need to be some discussion with DavidoTek to ensure this is valid (I didn't know how #381 (or a solution along these lines), and including |
Including EDIT: The increase could be caused by the change of the path from |
* AppImage: Include libxcb-cursor0 * AppImage: Update PySide6 paths to clean See #378 (comment)
Describe the bug
Unable to launch ProtonUp-Qt-2.9.2-x86_64.AppImage
To Reproduce
Launch it with any method
Expected behavior
Program opens
Screenshots
Desktop (please complete the following information):
Additional context
2.8.0 work fine, tried to update and latest version doesn't work 2.9.2. I can test other version if you think it would help?
Terminal output
The text was updated successfully, but these errors were encountered: