Zoomtopia is here. Unlock the transformative power of generative AI, helping you connect, collaborate, and Work Happy with AI Companion.
Register nowEmpowering you to increase productivity, improve team effectiveness, and enhance skills.
Learn moreKeep your Zoom app up to date to access the latest features.
Download Center Download the Zoom appDownload hi-res images and animations to elevate your next Zoom meeting.
Browse Backgrounds Zoom Virtual BackgroundsEmpowering you to increase productivity, improve team effectiveness, and enhance skills.
Zoom AI CompanionEffective immediately, customers with subscription plans greater than $10 USD/month may receive live chat support. Sign in and visit our contact page to view your support options.
Starting February 1, 2025, Zoom Phone customers must add their phone numbers to an approved 10DLC campaign in order to keep using SMS/MMS capabilities on their numbers.
2022-09-25 10:53 AM
Am I the only one who cannot scroll through all the pages, when in Gallery view?
In my Zoom client installation (Ubuntu 22.04) the arrow buttons (which permit the scroll through all pages in Gallery view) do not show up.
When I resize the window, they briefly appear, and disappear almost immediately.
2022-10-03 12:59 AM
Me too with Mint 20.2. Exactly the same bug of a disappearing triangle but can see it briefly with resizing. Would be handy with a hot key combo though.
Eric
2022-10-03 01:52 AM
An hot key combo would be great!
@EricEarl let's try together to submit a bug or contact an official support. Quite frustrating, since the bug is there since ages, actually.
2022-10-03 02:13 AM
2022-10-03 12:45 PM
They closed my ticket, asking me to migrate to the developer forum, which I did:
https://devforum.zoom.us/t/pagination-buttons-not-showing-in-chrome-for-linux/76875
2023-07-19 04:39 AM
I have the same problem. LinuxMint v 21.1 cinnamon, new install. latest version of zoom. just downloaded & installed the .deb July 19 2023 at 11:30 UTC
2023-08-24 06:21 AM
Same problem here. And it is kind of ridiculous that no one feels responsible for this bug. The ticket that @lolu submitted didn't get very far. Does anyone have a work-around for this?