search

Dpeta / pesterchum-alt-servers

Instant messaging client copying the look and feel of clients from Andrew Hussie's webcomic Homestuck.
https://pesterchum.xyz
GNU General Public License v3.0
78 stars 20 forks source link

Unable to open pesterchum Linux #75

Closed GamzeeRakoon closed 2 years ago

GamzeeRakoon commented 2 years ago

Hello i am unable to use pesterchum because it wont open and only throws a few errors.

output of the error: https://hastebin.skyra.pw/ixohohatof.pgsql

i am on fedora 35

Dpeta commented 2 years ago

Which release is this? :?c Or are you running from source? :0c

GamzeeRakoon commented 2 years ago

Pesterchum Alt. Builds 2022-03-26 PesterchumAlt.-2.2.1-linux64-glibc2.27+.tar.gz

Dpeta commented 2 years ago

Tried to reproduce this and the build didn't work on Fedora 35 for me either, though I got a pretty different error: (Pesterchum:4726): GLib-GIO-ERROR **: 10:39:42.443: Settings schema 'org.gnome.settings-daemon.plugins.xsettings' does not contain a key named 'antialiasing

That might be a Wayland-related error? That'd explain why it's only affecting Fedora, since it seems to be one of the few distros that's already started using Wayland by default for gnome instead of X. And it seems like PyInstaller has only recently started supporting Wayland with PyQt: https://pyinstaller.org/en/stable/CHANGES.html#id4, old binaries don't seem to support it: https://github.com/pyinstaller/pyinstaller/issues/6483

Since the 2.27+ build was made using a slightly outdated release of PyInstaller, it might not have build with Wayland support. The 2.35 build does, but that one only runs on Fedora 36 because of the glibc version.

I put up a release build on Fedora 35 specifically, so that might be worth trying for now: https://github.com/Dpeta/pesterchum-alt-servers/releases/tag/v2.2.2-rc1, I'm not certain the Wayland issue is the same issue as the one you're having, but it could fix a dynamic linking issue too if that was the cause after all.

GamzeeRakoon commented 2 years ago

hello! the new release didnt work for me but the running the pesterchum executable gives a new error this time Usage: pesterchum.py [OPTIONS] Use -h/--help to see the available options. Logging is configured in logging.ini /home/niki/Videos/Pesterchum/Pesterchum: symbol lookup error: /lib64/libEGL_mesa.so.0: undefined symbol: wl_proxy_marshal_flags and then it just hands there i get this error in x11 and wayland

i have also tested from source and everything works there except the window is very small

Dpeta commented 2 years ago

Running from source is probably better than running a build anyway, so if that works then that's good :3 👍, it's tiny because Pesterchum currently doesn't scale with resolution.

Pretty sure that's another wayland-related error though, judging from https://github.com/kovidgoyal/kitty/issues/4760, there might also be some relevant info on https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005268;msg=19.

I'm not able to reproduce it though, I made a new build on fedora & tested it on an arch+gnome+wayland VM and fedora35's liveiso, and it seems to work on both, even seems to run without qt5-wayland, so presumably the QtWaylandClient-related plugins were collected successfully during build: Screenshot_20220413_160422

Maybe there's something unique about your setup? :"3 If running from source works it might be a non-issue though.

GamzeeRakoon commented 2 years ago

well im using the KDE spin of fedora maybe thats affecting something? i tested the new release on x11 and it seems to work now, its only broken on wayland now it seems which already an improvement! image

GamzeeRakoon commented 2 years ago

ill close down this issue open a new issue thats specificly for wayland with all the info we gathered here

GamzeeRakoon commented 2 years ago

Running from source is probably better than running a build anyway, so if that works then that's good :3 +1, it's tiny because Pesterchum ~currently~ doesn't scale with resolution.

Pretty sure that's another wayland-related error though, judging from kovidgoyal/kitty#4760, there might also be some relevant info on https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005268;msg=19.

I'm not able to reproduce it though, I made a new build on fedora & tested it on an arch+gnome+wayland VM and fedora35's liveiso, and it seems to work on both, even seems to run without qt5-wayland, so presumably the QtWaylandClient-related plugins were collected successfully during build: Screenshot_20220413_160422

Maybe there's something unique about your setup? :"3 If running from source works it might be a non-issue though.

is this tested gnomes implentation of wayland or x11?