Skip to content
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

(wrong-type-argument stringp mouse-wheel-down-event) on Emacs 27.1, on openSUSE #3784

Closed
mk-parrot opened this issue Aug 20, 2020 · 7 comments
Labels
is:upstream Originates from outside the project and cannot be fully addressed here os:openSUSE Particular to the openSUSE distribution of Linux status:resolved-elsewhere Issue was addressed outside of Doom, needing no action on Doom's part

Comments

@mk-parrot
Copy link

mk-parrot commented Aug 20, 2020

i did a fresh OpenSuse TW install and magit and org are not working. The error message for everything is:

Failed to load magit package incrementally, because: (wrong-type-argument stringp mouse-wheel-down-event)"

Sidenote: starting with emacs-x11 command does not produce the errors so it might be something to do with the Emacs launcher script on Open Suse and dbus but i'm not certain as it goes wayyy over my head. There is a solution which is to alias emacs to emacs-x11 systemwide but i feel like the dbus gymnastics are there for a reason.

@hlissner hlissner added the is:upstream Originates from outside the project and cannot be fully addressed here label Aug 20, 2020
@hlissner hlissner changed the title errors after fresh install with default config (wrong-type-argument stringp mouse-wheel-down-event) on Emacs 27.1, on openSUSE Aug 20, 2020
@hlissner hlissner added the os:openSUSE Particular to the openSUSE distribution of Linux label Aug 20, 2020
@hlissner
Copy link
Member

hlissner commented Aug 20, 2020

This is a known issue with a build of Emacs 27.1 on openSUSE Tumbleweed. I'm not certain of the cause, but it cannot be reproduced anywhere else. I don't know enough about openSUSE and its ecosystem to suggest where to get a working build of 27.1 from. @agraul can you advise?

@agraul
Copy link
Contributor

agraul commented Aug 20, 2020

I've been using this one without any problems for the last months (RCs at first), you can switch to it with

zypper addrepo obs:// home:AndreasSchwab:emacs:27 emacs27
zypper refresh emacs27
zypper dup --allow-vendor-change --from emacs27

Disclaimer: That is a personal repository and I don't know if its maintainer accepts bug reports. Please only use it temporarily until the package in the distribution is fixed.

There is a mailing list thread about this issue with a mail that mentions the /usr/bin/emacs script. There is also a link to a bug report in that mail, but that bug does not contain much information. The bug is marked as fixed, but the update is still in QA before it reaches Tumbleweed. I don't know if that bug is the very same as what you describe, once the update is out you can try again.

Sadly I also don't really grasp the helper script and can't help with that.

@hlissner hlissner added the status:resolved Issue was addressed internally label Aug 20, 2020
@hlissner hlissner reopened this Aug 22, 2020
@hlissner hlissner added workaround Contains a workaround, but no acceptable or final solution (yet) and removed status:resolved Issue was addressed internally labels Aug 22, 2020
@hlissner
Copy link
Member

Please let me know if this issue is resolved upstream. I'll leave this issue open until then.

@mk-parrot
Copy link
Author

They rolled out an update in the main Tumbleweed repositories but it only fixes some of the graphical issues like fonts but it still doesn't fix the plugins not loading properly. So still using the workaround.

@tecosaur
Copy link
Member

As another stopgap measure, running

(assq-delete-all 'mouse-wheel-down-event load-history)

Seems to do the trick.

@tecosaur
Copy link
Member

tecosaur commented Sep 4, 2020

I believe this has been fixed with the latest update 😃

@brejoc
Copy link

brejoc commented Sep 4, 2020

Can confirm that the latest update to emacs in Tumbleweed fixed it. That's version 27.1-3.1.

@hlissner hlissner added status:resolved-elsewhere Issue was addressed outside of Doom, needing no action on Doom's part and removed workaround Contains a workaround, but no acceptable or final solution (yet) labels Sep 4, 2020
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 3, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
is:upstream Originates from outside the project and cannot be fully addressed here os:openSUSE Particular to the openSUSE distribution of Linux status:resolved-elsewhere Issue was addressed outside of Doom, needing no action on Doom's part
Projects
None yet
Development

No branches or pull requests

5 participants