mechvibes
mechvibes copied to clipboard
Ubuntu Desktop or GNOME don't support sound in terminal or other desktop.
To reproduce:
- Install Mechvibes Install Mechvibes in a linux distro running the GNOME desktop manager or Ubuntu-Desktop (Customized GNOME for Ubuntu)
- Start typing in the file manager or menu or terminal. No sound will be heard
- Start typing in any other apps that are not closely related to system or GNOME. Sound is heard.
Possible Cause: Conflict with system configuration or any other internal issues with mechvibes & GNOME
Possible fix: Investigation required.
This issue has been automatically marked as stale because it has not had any activity in the last 60 days. It will be closed in 7 days if no further activity occurs. Please feel free to leave a comment if you believe the issue is still relevant.
!unstale
Thanks for letting us know about this issue, however I believe this is an upstream bug with one of our dependencies and unfortunately we use a package that is no longer maintained, so it's unlikely a fix will exist.
I hope to continue to update electron moving forward, to add support for arm cpus which will allow us to update to a maintained version of the package, which will hopefully fix this issue, and if it doesn't we can file an issue with them to have it fixed.
!unstale
This issue has been automatically marked as stale because it has not had any activity in the last 60 days. It will be closed in 7 days if no further activity occurs. Please feel free to leave a comment if you believe the issue is still relevant.
Hi 👋 I just installed Mechvibes and experienced issues related to GNOME / Wayland. I found out about this issue a few hours ago. I'm sending this comment because the issue is going to be closed by github-action, so I'm just doing what's suggested above (leaving a comment since I believe the issue is still relevant).
Just for the record, I just switched to X11 and did some adjustments to make it work for me (I have a touchpad/touchscreen, so... you know) and I must say that Mechvibes is sooooooooooo satisfying to use. To be honest, after the Wayland incident I didn't expected it to work so well (it even works on GNOME's search and the display manager, everywhere I can type !), so thanks for this awesome piece of software ^^. But it would be nice if this issue gets fixed one day since a lot of distros pick Wayland as their default nowadays.
Any update on this particular issue since February ? It was said the issue was due to a now unmaintained version of a package, and updating Electron could possibly allow to fix this issue. What about this ? 👀
Currently, Electron still does not natively support Wayland, so as an interim solution, I suggest using XWayland which allows X11 applications to run on a Wayland desktop without modification.
Hi, thanks for the answer ! I read about XWayland, and tried to install it but I realised I already have it. Now that I read your comment again, I guess there's a misunderstanding : this issue isn't about Mechvibes not running on Wayland, but it doesn't work on Wayland apps. We are able to run Mechvibes on our (X)Wayland desktops, and it does produce keyboard sounds on every X11 apps (Electron such as Visual Studio Code, Discord ; Native, like Edge...), but not on Wayland apps (the whole GNOME Desktop as well as libadwaita apps, Firefox...).
Oh my bad, since Im not very familiar with Linux so yeah I misunderstood your comment. So in this situation, there is nothing we can do at the moment since this version of Mechvibes heavily depends on Electron
Yeah... :/
Since I saw in another issue that one of the maintainers (maybe you, idk) thought about moving Mechvibes to Tauri, I tried to do a bit of research about Tauri's compatibility with Wayland, but I don't know much about that. I'm not sure it would fix the issue either.
I guess our last hope is what NotLazy's previous answer was mentioning...
Thanks for letting us know about this issue, however I believe this is an upstream bug with one of our dependencies and unfortunately we use a package that is no longer maintained, so it's unlikely a fix will exist.
I hope to continue to update electron moving forward, to add support for arm cpus which will allow us to update to a maintained version of the package, which will hopefully fix this issue, and if it doesn't we can file an issue with them to have it fixed.
Although, it been a long time.. did it got any solutions or if anything was discovered, is it an internal issue with electron, if so please reference the electron's issue if not let's investigate it. @NotLazy @SpicyWasab @hainguyents13
Hi, thanks for the answer ! I read about XWayland, and tried to install it but I realised I already have it. Now that I read your comment again, I guess there's a misunderstanding : this issue isn't about Mechvibes not running on Wayland, but it doesn't work on Wayland apps. We are able to run Mechvibes on our (X)Wayland desktops, and it does produce keyboard sounds on every X11 apps (Electron such as Visual Studio Code, Discord ; Native, like Edge...), but not on Wayland apps (the whole GNOME Desktop as well as libadwaita apps, Firefox...).
Is there any solution or work-around regarding this?
Although, it been a long time.. did it got any solutions or if anything was discovered, is it an internal issue with electron, if so please reference the electron's issue if not let's investigate it.
I am personally curious about which package NotLazy was talking about specifically, I guess it would be a good starting point for us to investigate.
@SpicyWasab Im trying to build the app in other languages, csharp seem promising as MS says .net core is now has better crossplatform support
any fix?
I use Neptune, and it works fine...it is the same thing as a mechavibes
Is there any non-wayland terminal for ubuntu?
Is there any non-wayland terminal for ubuntu?
I'm not sure whetever it's really important that it is Wayland or not, but if you mean "Any terminal that work with Mechvibes?", then yes, I use Warp and I still have Mechvibe working.
Is there any non-wayland terminal for ubuntu?
You can run any terminal as an x11 process and xwayland will handle the rest for its working in wayland session. Might have to tweak the scaling as that tends to change when switching between them.