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

Ubuntu Desktop or GNOME don't support sound in terminal or other desktop. #238

Open
hariacharya80 opened this issue Jul 2, 2023 · 14 comments
Labels
bug/upstream Something isn’t working and it’s not our fault. dependencies/electron This issue is related to electron dependencies/iohook This issue is related to iohook stale This issue is stale and will be closed soon !stale Prevent bot from marking as stale

Comments

@hariacharya80
Copy link

To reproduce:

  1. Install Mechvibes
    Install Mechvibes in a linux distro running the GNOME desktop manager or Ubuntu-Desktop (Customized GNOME for Ubuntu)
  2. Start typing in the file manager or menu or terminal.
    No sound will be heard
  3. 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.

Copy link

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.

@github-actions github-actions bot added the stale This issue is stale and will be closed soon label Feb 18, 2024
@hariacharya80
Copy link
Author

!unstale

@NotLazy NotLazy added bug Something isn't working dependencies Pull requests that update a dependency file and removed stale This issue is stale and will be closed soon labels Feb 19, 2024
@NotLazy
Copy link
Collaborator

NotLazy commented Feb 19, 2024

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.

@NotLazy NotLazy added bug/upstream Something isn’t working and it’s not our fault. dependencies/electron This issue is related to electron dependencies/iohook This issue is related to iohook !stale Prevent bot from marking as stale and removed bug Something isn't working dependencies Pull requests that update a dependency file labels Feb 19, 2024
@NotLazy NotLazy mentioned this issue Mar 4, 2024
@Redoxahmii
Copy link

!unstale

Copy link

github-actions bot commented May 6, 2024

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.

@github-actions github-actions bot added the stale This issue is stale and will be closed soon label May 6, 2024
@SpicyWasab
Copy link

SpicyWasab commented May 12, 2024

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 ? 👀

@hainguyents13
Copy link
Owner

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.

@SpicyWasab
Copy link

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...).

@hainguyents13
Copy link
Owner

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

@SpicyWasab
Copy link

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.

@hariacharya80
Copy link
Author

hariacharya80 commented May 20, 2024

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

@hariacharya80
Copy link
Author

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?

@SpicyWasab
Copy link

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.

@hainguyents13
Copy link
Owner

@SpicyWasab Im trying to build the app in other languages, csharp seem promising as MS says .net core is now has better crossplatform support

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug/upstream Something isn’t working and it’s not our fault. dependencies/electron This issue is related to electron dependencies/iohook This issue is related to iohook stale This issue is stale and will be closed soon !stale Prevent bot from marking as stale
Projects
None yet
Development

No branches or pull requests

5 participants