Open Seneral opened 1 year ago
In my attempts to debug this, I have tried to build the flatpak from scratch. However I encountered two issues:
flatpak run org.flatpak.Builder --repo=lutris --force-clean --install-deps-from=flathub build-dir net.lutris.Lutris.yml
Starting build of net.lutris.Lutris
========================================================================
Building module qt5-qtbase in /mnt/data/DEVELOPMENT/BUILD/net.lutris.Lutris/.flatpak-builder/build/qt5-qtbase-1
========================================================================
Updated Git hooks.
Git LFS initialized.
Updating files: 100% (23228/23228), done.
Note: switching to 'e894b8945c607b4c188a178ae0554139f877a061'.
You are in 'detached HEAD' state. You can look around, make experimental changes and commit them, and you can discard any commits you make in this state without impacting any branches by switching back to a branch.
If you want to create a new branch to retain commits you create, you may do so (now or later) by using -c with the switch command. Example:
git switch -c
Or undo this operation with:
git switch -
Turn off this advice by setting config variable advice.detachedHead to false
HEAD is now at e894b894 Update bundled zlib to version 1.2.12
Checking out LFS objects: 100% (170/170), 0 B | 0 B/s, done.
Applying patch qtbase-avoid-hardcoding-kernel-version.patch
patching file src/corelib/configure.json
Hunk #1 succeeded at 636 (offset 135 lines).
Hunk #2 succeeded at 778 (offset 149 lines).
Hunk #3 succeeded at 788 (offset 149 lines).
Applying patch qtbase-use-wayland-on-gnome.patch
patching file src/gui/kernel/qguiapplication.cpp
Hunk #1 succeeded at 1409 (offset 33 lines).
Applying patch qtbase-revert-qstandardpaths-dont-change-permissions-on-xdg-runtime-dir.patch
patching file src/corelib/io/qstandardpaths_unix.cpp
patching file tests/auto/corelib/io/qstandardpaths/tst_qstandardpaths.cpp
Applying patch qtbase-filechooser-portal-send-window-id-in-hex.patch
patching file src/plugins/platformthemes/xdgdesktopportal/qxdgdesktopportalfiledialog.cpp
If you want to test a build, you shoud be able to remove the Qt5 dependency (but runners such as Dolphin and MAME will not work).
I've never seen the build process fail on Qt5 so there is maybe something wrong with your local flatpak-builder
Well I'm using the flatpak version of flatpak-builder, which according to the first bug I faced, is a sort of "reference", the most up to date one. I've never dabbled in anything flatpak beyond flatseal before, could you tell me how to remove the QT5 dependency? (nvm just removing - modules/qt5-15.yaml might be working, usually removing a dependency isn't that easy)
In net.lutris.Lutris.yml remove the line pointing to the qt5 libraries:
- modules/qt5-15.yaml
This really isn't easy.
Now I get Error: module gtk2: Child process exited with code 137
, tried multiple times again.
Not OOM, closed all apps and only used ~2.5GB/(8+16GB) of memory+swap
Not timeout/background killed, made sure org.flatpak.Builder is allowed to run in the background, AND constantly interacted with it so that no background warning popped up, still died like this.
Not sure what kills it tbh, but something does. Tested if org.flatpak.Builder suffers from the same exit-after-dozens-of-seconds bug I want to debug in the first place, and so far, no indication of that either.
There's some weird stuff going on for sure.... Do you have another system to test this on? Even a VM would do.
Will have to do it on the weekend on another PC, where I want to set up Lutris for retro gaming anyway. Just to make sure my understanding is correct, installing lutris and gamescope flatpaks together should in theory work and it should detect gamescope, correct? Will try different distros if it happens to not work on a fresh install of my current distro (KDE Neon).
I'm not sure Gamescope will work... The only case where I run the Lutris Flatpak is on the Steam Deck and this already runs Gamescope as its base compositor.
I have yet to find the documentation that explains Flatpak extensions...
Oh great, getting the flatpak to work is my only hope for gamescope. Trying to compile it on ubuntu 22.04 is almost impossible, tried a while back, apart from plenty of dependency problems I had to compile meson myself, and even after all that there are more problems. Never had this much trouble trying to compile anything, and I'm a programmer.
There's a PPA available: https://launchpad.net/~ar-lex/+archive/ubuntu/gamescope
I also attempted to build it on Pop 22.04 and abandoned...
Ok so flatpak gamescope+lutris works technically on a fresh Manjaro+KDE install, same hardware. Not sure what caused it to not work on my system. Flatpak lutris does recognise flatpak gamescope, which is nice. Unfortunately I always get a black screen (at best a flickering screen with a squashed, single frame of the game, when using a lutris GE proton backend instead of a normal wine one). But I do know the game is running, sound and interaction work fine. Saving grace is that the games do go properly fullscreen even without gamescope for some reason, so I don't necessarily need gamescope, where on my current system I need it because the games occupy a tiny, unscaled corner of the screen only. Weird stuff....
Will try the gamescope PPA on this system, thanks for the help
Tried PPA, and it seems I did before, but I cannot install it (I remember trying with aptitude to fix problems, no luck).
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Starting pkgProblemResolver with broken count: 1
Starting 2 pkgProblemResolver with broken count: 1
Investigating (0) libwlroots11:amd64 < none -> 0.16.1-2~jammy @un puN Ib >
Broken libwlroots11:amd64 Depends on libseat1:amd64 < none | 0.6.4-1 @un uH > (>= 0.5.0)
Considering libseat1:amd64 0 as a solution to libwlroots11:amd64 0
Re-Instated libseat1:amd64
Broken libwlroots11:amd64 Depends on libwayland-server0:amd64 < 1.20.0-1ubuntu0.1 @ii pK > (>= 1.20.92)
Considering libwayland-server0:amd64 44 as a solution to libwlroots11:amd64 0
Considering libwayland-server0:amd64 44 as a solution to libwlroots11:amd64 0
Considering libwayland-server0:amd64 44 as a solution to libwlroots11:amd64 0
Considering libwayland-server0:amd64 44 as a solution to libwlroots11:amd64 0
Considering libwayland-server0:amd64 44 as a solution to libwlroots11:amd64 0
Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies.
libwlroots11 : Depends: libwayland-server0 (>= 1.20.92) but 1.20.0-1ubuntu0.1 is to be installed
E: Unable to correct problems, you have held broken packages.
Bug description
WARNING: I found evidence that this also happens with other packages, but not necessarily the same for each user: https://discourse.flathub.org/t/debugging-flatpak-early-exit-issues/4345/4 So this might not be related to Lutris at all. But it only happens for lutris for me, so here I am. I also opened a flatpak issue since this might be a more widespread problem.
This flatpak exits after several dozen seconds, with or without interaction. Trying to debug it with flatpak reveals that the whole flatpak environment exits, without the lutris binary within even running.
How to Reproduce
Steps to reproduce the behavior:
flatpak run --command=sh --devel net.lutris.Lutris
(install required dependencies)Or:
flatpak run net.lutris.Lutris
and wait several dozen secondsLog output
Nothing relevant, without any interaction it exits without further logs after the initial three:
System Information