-
Notifications
You must be signed in to change notification settings - Fork 13
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
Can't run pgtk channel on wayland #58
Comments
Thanks for reporting this issue - unfortunately this is likely due to an incompatibility between the various libraries shipped in the emacs snap compared to the ones used on your host system - basically, emacs uses a version of libgdk that expects to be able to lookup a particular gsettings value, but your host system has a newer gsettings schema for this that does not include this key - which results in this error. I am not sure there is a lot that can be done in the emacs snap itself to avoid this since we need to use libgdk from the snap to ensure the libraries are all self-consistent and compatible within the snap. This is also not specific to the emacs snap - see say Ultimaker/Cura#12776 which is for an application packaged as an appimage which has the same issue. |
I see. Wasn't the snap tested on 23.04? I'm guessing this affects everyone running the latest version right? |
Yes I tested it on 23.04 but released it anyway due to popular demand. But this is why there is no stable release, it's only published to the edge channel which is not expected to be stable. |
Yes of course I understand the unstable nature of the edge channel. Just find it strange it works on your system since we both have the same release. Should have encountered the same issue I have since the host libraries should be the same, right? |
Apologies I wasn't clear above - I meant I tested it on 23.04 and found the same issue but released it anyway due to popular demand. |
Oh OK. Now it makes sense 😄. Guess I'll have to wait until the quirks are ironed out... Keep up the great work. |
This issue is still ongoing (Nov/23). @alexmurray since Ubuntu defaulted to Wayland since 21.04 and since we already have more than a year since the last LTS which is also wayland by default, shouldn't this default to the pgtk version and the x11 version be a different channel? IMHO this will make the out-of-the-box experience using the snap better for most people. The difference in rendering is quite apparent (for example, the height of doom-modeline is dramatically different). The pgtk will also work in an x11 session though that is not recommended and a warning message (from Emacs itself) shows up. In any case, thanks for this package :) |
@victoronascimento I am a bit confused by your comment - this issue is about how the pgtk channel doesn't work as expected when run under Wayland on Ubuntu 23.04 etc - but from your comment you seem to indicate that pgtk should be the default channel and hence I assume that it is working for you. Can you please provide more details / clarification? Thanks. |
Sorry @alexmurray for not being precise!
Maybe the update of the library is not possible and then my comment makes no sense at all! Sorry for the noise if that is the case... |
Add gnome-settings-daemon-common which includes the antialiasing key from the org.gnome.settings-daemon.plugins.xsettings schema and compile this during the build and finally ensure we add this path to XDG_DATA_DIRS so it can be found at runtime to fix crash when running pgtk on newer Ubuntu releases under Wayland. Signed-off-by: Alex Murray <murray.alex@gmail.com>
Hopefully this should be fixed with bb8ec99 - if someone else could please test this once new builds are available on the pgtk/edge channel soon that would be great. |
I was trying out the
pgtk/edge
channel but emacs won't start on Wayland. I get this error:GLib-GIO-ERROR **: 19:59:44.612: Settings schema 'org.gnome.settings-daemon.plugins.xsettings' does not contain a key named 'antialiasing'
On Xorg emacs starts although I get a warning saying
pgtk
is unsupported under X.I'm running 23.04.
Don't know if it's useful or not but here is the backtrace:
The text was updated successfully, but these errors were encountered: