Last post by gripped -
I'm pretty sure venv's shouldn't be used in PKGBUILD's ? Instead you should be creating extra packages, where dependencies cannot be met from current repo's (or the AUR).
As the package is fairly up to date and claims a requirement for older python versions that suggest to me it's likely that it (or an AUR dep) doesn't work with 3.12. Which seems to be what you are encountering ?
Last post by replabrobin -
I used latest lxqt-runit iso and made a vm. After that lxqt opened in X11 mode. I updated packages in the vm and latest lxqt was installed ie version 2.1.
After reboot the 2.1 version was working fine and I was able to configure it mostly. Thei is X11 version. I was able to get the panel almost like I prefer. Seems lxqt-panel always leaves a small window height in place even when autohiding. I was able to remove the grey line by using my standard background colur and setting opacity==1. I was not able (as yet) to change the tasks background to match so my buttons still have a grep bg.
To get a wayland session I had to install labwc from AUR and the arch linux package lxqt-wayland-session. Neither of these require systemd, but build from aur rquires that base-devel is present.
After this I rebooted and see that the sddm login now has extra sessions labwc and LXQt (wayland).
The labwc session is completely minimal it just has a primitive right button menu with options Reconfigure and Exit. I imagine it can be used to setup an openbox style configuration.
The LXQt (Wayland) session works pretty well and seemed to be identical in layout and operation of the panel/taskbar and styling.
It seems that the lxqt-panel can show the gvim icon etc in wayland, I suppose that's because of gtk3, but I am not an expert.
This is the best experience I've had so far with wayland. However, I imagine it will be hard to duplicate my openbox setup as it's using older gtk styles.
I forgot to say that intially the wayland session would not start, I think that's because the autostart was trying to iuse connman which I don't think is installed in lxqt-runit by default. At login there was a session configuration window shown.
I made initial package with makedeps from requirements.txt no idea about the deps. A script "install-linux-edl-drivers.sh" installs a bunch of udev rules. I noticed that setup.py installs conflicting files with the one makedep from the AUR:
Searching for pylzma Reading https://pypi.org/simple/pylzma/ Downloading https://files.pythonhosted.org/packages/03/d8/10ef072c3cd4301a65a1b762b09eefa02baf8da23b9ea77ebe9546499975/pylzma-0.5.0.tar.gz#sha256=b874172afbf37770e643bf2dc9d9b6b03eb95d8f8162e157145b3fe9e1b68a1c Best match: pylzma 0.5.0 Processing pylzma-0.5.0.tar.gz Writing /tmp/easy_install-i0wxkd6a/pylzma-0.5.0/setup.cfg Running pylzma-0.5.0/setup.py -q bdist_egg --dist-dir /tmp/easy_install-i0wxkd6a/pylzma-0.5.0/egg-dist-tmp-ifbtgykb /usr/lib/python3.12/site-packages/setuptools/_distutils/dist.py:261: UserWarning: Unknown distribution option: 'tests_require' warnings.warn(msg) /usr/lib/python3.12/site-packages/setuptools/_distutils/dist.py:261: UserWarning: Unknown distribution option: 'test_suite' warnings.warn(msg) no previously-included directories found matching 'src/sdk.orig' /usr/lib/python3.12/site-packages/setuptools/_distutils/cmd.py:66: SetuptoolsDeprecationWarning: setup.py install is deprecated. !!
******************************************************************************** Please avoid running ``setup.py`` directly. Instead, use pypa/build, pypa/installer or other standards-based tools.
See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html for details. ********************************************************************************
!! self.initialize_options() /tmp/easy_install-i0wxkd6a/pylzma-0.5.0/setup.py:105: UnsupportedPlatformWarning: Multithreading is not supported on the platform "linux", please contact [email protected] for more informations. warn("""\ src/pylzma/pylzma.c: In function ‘PyInit_pylzma’: src/pylzma/pylzma.c:296:5: warning: ‘PyEval_InitThreads’ is deprecated [-Wdeprecated-declarations] 296 | PyEval_InitThreads(); | ^~~~~~~~~~~~~~~~~~ In file included from /usr/include/python3.12/Python.h:95, from src/pylzma/pylzma.c:26: /usr/include/python3.12/ceval.h:132:37: note: declared here 132 | Py_DEPRECATED(3.9) PyAPI_FUNC(void) PyEval_InitThreads(void); | ^~~~~~~~~~~~~~~~~~ src/pylzma/pylzma_aes.c:158:5: error: initialization of ‘long int’ from ‘void *’ makes integer from pointer without a cast [-Wint-conversion] 158 | NULL, /* printfunc tp_print; */ | ^~~~ src/pylzma/pylzma_aes.c:158:5: note: (near initialization for ‘CAESDecrypt_Type.tp_vectorcall_offset’) error: Setup script exited with error: command '/usr/bin/gcc' failed with exit code 1
Hmmm, at this point this seems like more of an GSP <-> nvidia-open issue, could you try installing full proprietary package and disable GSP by creating a file:
It's just for a test if it changes anything, you can switch back to nvidia-open and delete that file, because that'd mean it's just wayland shenanigans, and if it is actually a wayland issue then I'm out of ideas...
Also I'm not sure what 18 as a value means here, and from the what I got on reddit it seems like it forces GSP firmware to be always active in this mode on nvidia-open, so that's why I recommend trying going with nvidia-dkms instead.
Marking this one as offtopic, because it's performance related and just what I noticed on my GTX 1060: Spoiler (click to show/hide)
I'm getting around 5-10 FPS more in Tekken 8 and framepacing is a lot more stable with those settings:
options nvidia NVreg_EnableGpuFirmware=0 # Turing and above options nvidia NVreg_EnableGpuFirmwareLogs=0 # Disable this for Pascal and Maxwell options nvidia NVreg_UsePageAttributeTable=1 options nvidia NVreg_EnablePCIeGen3=1 options nvidia NVreg_EnableStreamMemOPs=1 options nvidia NVreg_RegistryDwords="PeerMappingOverride=1;" options nvidia NVreg_EnableResizableBar=1 # Doesn't work on Pascal for some reason... options nvidia NVreg_EnablePCIERelaxedOrderingMode=1 options nvidia NVreg_InitializeSystemMemoryAllocations=0
I swapped to nvidia-dkms instead of nvidia-open-dkms and added the nvidia.conf file with "options nvidia NVreg_EnableGpuFirmware=0" in the /etc/modprobe.d/ directory and the issue still persists, Thanks for trying at least.
Last post by Shoun2137 -
Hmmm, at this point this seems like more of an GSP <-> nvidia-open issue, could you try installing full proprietary package and disable GSP by creating a file:
It's just for a test if it changes anything, you can switch back to nvidia-open and delete that file, because that'd mean it's just wayland shenanigans, and if it is actually a wayland issue then I'm out of ideas...
Also I'm not sure what 18 as a value means here, and from the what I got on reddit it seems like it forces GSP firmware to be always active in this mode on nvidia-open, so that's why I recommend trying going with nvidia-dkms instead.
Marking this one as offtopic, because it's performance related and just what I noticed on my GTX 1060: Spoiler (click to show/hide)
I'm getting around 5-10 FPS more in Tekken 8 and framepacing is a lot more stable with those settings:
This is enabled by default on any ryzen platform, so it's redundant. You didn't provided: cat /proc/driver/nvidia/params and I assume you don't have anything nvidia related in /etc/modprobe.d/? If you run pure wayland, you should route every game through valve's gamescope compositor.
I would like this issue fixed without having to use gamescope since when I don't screenshare games work perfectly fine without gamescope and I get around a 20% performance loss when using gamescope.
