# Remove iBus dependency from Debian package **URL:** \ **Category:** Showcase\ **Created:** [August 25, 2024, 5:54pm UTC](https://devforum.zoom.us/t/remove-ibus-dependency-from-debian-package/116347 "2024-08-25T17:54:30Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![jakint0sh](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/jakint0sh/32/62756_2.png) [@jakint0sh](https://devforum.zoom.us/u/jakint0sh)\ **Post date:** [August 25, 2024, 5:54pm UTC](https://devforum.zoom.us/t/remove-ibus-dependency-from-debian-package/116347/1 "2024-08-25T17:54:30Z")
So. `ibus` is a package in the Depends category for the Debian package for Zoom. This causes problems on many people’s systems, especially if they have already picked another input method manager with which `ibus` conflicts. You have known about this issue since April 2022. You have been informed that it would be a trivial change to move the package to the Recommends category (or, better yet, the Suggests category), and that this trivial change would alleviate the issue for most users. There has been a good deal of discussion on this on this forum already, a well written summary of which was prepared back on January 23 by the user `scar`. I’d provide a link, but apparently I can’t put links in my posts. But, despite discussion and outreach, there has been no movement on this for about two and a half **years** now. This is a simple, trivial thing that could be done to alleviate a real issue. The issue was even initially raised **by the developers of iBus** , and it was explicitly stated that “This should be considered a demand by the GNU/Linux distributions to ZOOM.”! This flagrant disregard for your paying customers is appalling. Must we really repackage your application ourselves in order to make it function on our computers? And what about the people who don’t have the know-how for that? This whole ordeal is a complete embarrassment, as are a few other things, like the fact that you guys ignored OpenSSL vulnerabilities for 6 months. Now, this, unlike the iBus problem, is an issue that legitimately affected a large portion of your install base. So, at this point, I must ask, do you not fix problems with your product because you don’t want to, or because you can’t due to being mired in bureaucracy and pressure from the higher-ups to add features? Because something tells me that if both of those things were false, you wouldn’t have distributed your application with known security vulnerabilities in it for so long. ---
**Author:** ![tbaumeister](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/tbaumeister/32/63776_2.png) [@tbaumeister](https://devforum.zoom.us/u/tbaumeister)\ **Post date:** [October 1, 2024, 4:13am UTC](https://devforum.zoom.us/t/remove-ibus-dependency-from-debian-package/116347/2 "2024-10-01T04:13:09Z")
Who would have thought that installing zoom on Linux messes up the configured keyboard layouts? I ran into this issue today and wasted a lot of time till I figured out what the problems was. Thanks for that Zoom! I am amazed that this issue remains unfixed now for over two years. ---
**Author:** ![Max7](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/max7/32/68223_2.png) [@Max7](https://devforum.zoom.us/u/Max7)\ **Post date:** [March 27, 2025, 1:57pm UTC](https://devforum.zoom.us/t/remove-ibus-dependency-from-debian-package/116347/3 "2025-03-27T13:57:05Z")
First thing I do when downloading Zoom is this: hashman.ca/zoom/ ---
**Author:** ![scar](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/scar/32/55523_2.png) [@scar](https://devforum.zoom.us/u/scar)\ **Post date:** [November 21, 2025, 1:42am UTC](https://devforum.zoom.us/t/remove-ibus-dependency-from-debian-package/116347/4 "2025-11-21T01:42:06Z")
lol this has been a problem going on at least six years now since hashman discovered it. I’m surprised my post wasn’t deleted. I followed thru with an official bug report to Zoom thru our CIO, like I said I would. I estimated at least $10,000 in lost work due to the effects of this improper config Zoom refuses to correct. You know, Zoom, Policies are legal instruments? Violating them is illegal and actionable. I think Debian should take action against you, however that all works… In my bug report I also asked, for Accessibility reasons, for a proper dark mode like the Windows and Mac versions get, but what do we get? Team Chat sidebar only? If you can apply it there, you can apply it everywhere else in the app 🙄 Let’s see if I can post a link, to the reply I was given by Zoom staff @donte.zoom … > [@Latest Victim of IBus dependency in Debian Linux package & Hopefully Among The Last](https://devforum.zoom.us/t/latest-victim-of-ibus-dependency-in-debian-linux-package-hopefully-among-the-last/102386/2): > > @scar , Thank you for taking the time to share your feedback on this matter. We are aware of this behavior and our engineering team is actively working on a solution. This fix is expected to be included in the upcoming release of the Zoom Client. For the most recent updates, please refer to the following post: Sweet, how about an image? ![image](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/9/7/9780c0a5758f59e4fd79810ee64e3d056df672fe.jpeg)