@daniell You are at the wrong AUR page for the zoom-system-qt package.
Search Criteria
Package Details: zoom 6.2.6-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/zoom.git (read-only, click to copy) |
---|---|
Package Base: | zoom |
Description: | Video Conferencing and Web Conferencing Service |
Upstream URL: | https://zoom.us/ |
Keywords: | call conference meeting video |
Licenses: | LicenseRef-zoom |
Submitter: | edh |
Maintainer: | edh |
Last Packager: | edh |
Votes: | 669 |
Popularity: | 7.40 |
First Submitted: | 2015-08-15 13:18 (UTC) |
Last Updated: | 2024-10-28 11:11 (UTC) |
Dependencies (31)
- dbus (dbus-gitAUR, dbus-selinuxAUR)
- fontconfig (fontconfig-gitAUR, fontconfig-ubuntuAUR)
- glib2 (glib2-gitAUR, glib2-selinuxAUR, glib2-patched-thumbnailerAUR)
- gtk3 (gtk3-no_deadkeys_underlineAUR, gtk3-classicAUR, gtk3-classic-xfceAUR, gtk3-patched-filechooser-icon-viewAUR)
- libdrm (libdrm-gitAUR)
- libpulse (pulseaudio-dummyAUR, libpulse-gitAUR)
- libsm
- libx11 (libx11-gitAUR)
- libxcb (libxcb-gitAUR)
- libxcomposite
- libxcursor
- libxfixes
- libxi (libxi-gitAUR)
- libxkbcommon-x11 (libxkbcommon-x11-gitAUR)
- libxrandr (libxrandr-gitAUR)
- libxrender
- libxshmfence
- libxslt (libxslt-gitAUR)
- libxtst
- mesa (mesa-minimal-gitAUR, mesa-gitAUR, mesa-amd-bc250AUR, mesa-wsl2-gitAUR, amdonly-gaming-mesa-gitAUR, mesa-amber)
- Show 11 more dependencies...
Required by (3)
Sources (1)
Latest Comments
« First ‹ Previous 1 .. 44 45 46 47 48 49 50 51 52 53 54 .. 77 Next › Last »
edh commented on 2020-11-17 10:43 (UTC)
uwinkelvos commented on 2020-10-30 10:56 (UTC)
if you have problems with broken autoscaling, this can be disabled: ~/.config/zoomus.conf: autoScale=false
rgambord commented on 2020-10-27 20:28 (UTC)
@je-vv I use jack2 with alsa-plugin and apulse for programs that don't support jack. I can quit jack2 and zoom will work with alsa directly (although alsa does not support my HDMI out, so I only have mic) but it won't work when jack2 is running.
Eothred commented on 2020-10-13 13:25 (UTC)
Regarding SSO, for me it was Firefox containers blocking me (I think). I did not have the "zoom domain" as "always open in work container", however I had our company SSO login page on that list. So by jumping from a "no container" to my work container during log in, I think the app opening feature failed.
nasci commented on 2020-10-10 08:34 (UTC)
@malexan I normally use picom so I installed xcompmgr but it's no different. When opening the whiteboard picom gives a bunch of warnings and errors, like "flags cleared on a destroyed window" and "failed to query info". Not sure if that's related.
MasterOne commented on 2020-10-09 08:53 (UTC)
@caleb, no that's not it. As said, everything was working just a few days ago, but the system update that was performed yesterday obviously broke something, because reverting to a previous system snapshot using Timeshift solved the issue.
alerque commented on 2020-10-09 08:31 (UTC) (edited on 2020-10-09 08:33 (UTC) by alerque)
@MasterOne I've seen a similar crash not just recently but frequently across many versions in the last few months. The easiest way I found to avoid it is to make sure and enter the meeting ID with no spaces. I found copy and pasting the meeting ID from Zoom emails with their space separated groupings frequently caused crashes, but if I either type in or paste in a meeting ID with no spaces it us more stable.
Another one for me (because I frequently type on a non-English keyboard layout and switch layouts to type digits) is that swapping keyboard layouts using a keyboard shortcut (and the resulting momentary switch of input focus) sometimes crashed the join meeting box too. If I switch to a layout that I can type Arabic numerals first, then hit join and enter the meeting ID it is less likely to crash.
Neither of these things are unique to recent Zoom versions. I find the zoom-system-qt
package works better and crashes less frequently, but both are deeply troublesome. The upstream software quality is just abysmal and there isn't a lot the Arch packaging can do to fix it.
MasterOne commented on 2020-10-09 07:19 (UTC)
A system update performed on one of my laptops yesterday causes Zoom to crash after the Meeting ID and Passcode has been entered. Anyone else experiencing such a problem?
P.S. Sorry for being vague with no exact error diagnoses, but the problem was discovered yesterday at the beginning of a Zoom meeting and I had to get it going quickly again, so I just used Timeshift to revert to an earlier snapshot. I'm using GNOME on that laptop, if that matters.
je-vv commented on 2020-10-06 22:50 (UTC)
@rgambord, do you use alsa stand alone without pulse, or do you use pulse. It sounds you're using the former. Alsa stand alone without pulse works fine, and there's really no much to do on such a system. Just make sure your system audio works fine before using zoom, perhaps adjusting its configuration with alsactl. The Arch wiki for alsa is good: "https://wiki.archlinux.org/index.php/Advanced_Linux_Sound_Architecture". There can be some audio channels muted, and then you have to unmute them. Make sure to review capture as well, so you can set things up for the mic. To test sound, prior to using zoom, aplay can help, and to test the mic, then arecord can help, but you can find that on the wiki. If sounds works fine with alsa, then zoom should work great with no particular settings for it...
Pinned Comments
arash-m commented on 2024-09-15 15:56 (UTC)
Tested 6.2.0-1. Sharing works for me, but it still crashes after stopping. The workaround for me is still downgrading pipewire and libpipewire to 1.0.7 before meetings.
a172 commented on 2022-06-13 14:25 (UTC) (edited on 2022-06-13 14:25 (UTC) by a172)
@edh - That's not the answer I was hoping for (I was really hoping we could get it to launch without xwayland), but at least I know I'm not missing something.
Some
~/.config/zoomus.conf
updates:qt5-webengine
installed, and theebeddedBrowserForSSOLogin
line doesn't exist in my configzoomus.conf
. SSO login works just fine (issues with Firefox containers aside).pipewire-pulse
.system.audio.type
defaulted toalsa
for me (or I changed it without realizing it). I probably could have installedpipewire-alsa
and fixed my issues, but I setsystem.autio.type=pulse
(a lucky guess) and this worked. This should work for anyone using straight PulseAudio as well.If anyone finds documentation on
~/.config/zoomus.conf
, please let us know.edh commented on 2016-08-26 11:03 (UTC) (edited on 2017-03-09 10:48 (UTC) by edh)