I signed in to zoom a short while ago to schedule a meeting, and found the following three notices:
Our latest release went live on April 12th. Please subscribe to our blog and visit our release notes to stay up-to-date on all the latest enhancements to your account. To update to the latest version of Zoom, visit our download page.
Please begin updating all your clients to Zoom 5.0 now. After May 30, 2020, all Zoom clients on older versions will receive a forced upgrade when trying to join meetings as GCM Encryption will be fully enabled across the Zoom platform. Click here for more information.
Our latest release went live on April 7th. Check out our blog to review the new enhancements for ensuring the security and privacy of your account. To update to the latest version of Zoom, visit our download page.
Some time ago, at the suggestion of someone in this list, I used dnf to install zoom on my work station. I just checked with dnf to see what I currently have:
-bash.3[~]: dnf info zoom
Last metadata expiration check: 0:38:48 ago on Thu 14 May 2020 06:49:20 PM MDT.
Name : zoom
Version : 2.8.252201.0616
Release : 1
Architecture : x86_64
Size : 235 M
Source : zoom-2.8.252201.0616-1.src.rpm
Repository : @System
From repo : @commandline
No updates are available:
-bash.4[~]: dnf upgrade zoom
Fedora Modular 31 - x86_64 - Updates 59 kB/s | 17 kB 00:00
Fedora 31 - x86_64 - Updates 36 kB/s | 11 kB 00:00
Fedora 31 - x86_64 - Updates 909 kB/s | 3.0 MB 00:03
Nothing to do.
Will an update be available via dnf before zoom starts rejecting the release that I currently have?
Recently practically every website I visit makes me fill out a captcha,
and to make it worse they all seem busted, I click all the trains and
get a "try again", click all the buses "try again" usually I get into
the site after 4 or 5 attempts if I havent already given up...
Anyone else seeing this, or am I just "that guy"?
Anything I can do about it? Is it related to Linux / Firefox? I'm
running Fedora 31 and Firefox 76.0.1
Thanks in advance
`When you say "I wrote a program that crashed Windows", people just stare at you blankly and say "Hey, I got those with the system, *for free*".' (By Linus Torvalds)
I have computer which I build for 13 years ago. I have just replaced the battery on the motherboard and could restart
the computer and everything worked OK. The I needed to restart the the computer again and it did not boot from
the hard drive. I could start it from SystemRescueCD and the file systems where OK, fsck on them all where OK.
From that I conclude that it must be the boot partition that is corrupted.
How can I fix the boot partition?
I am editing a doc from others and can't find where to enable my name
for my edits and comments. It is coming up Unknown Author.
I looked in Tools > Options but they only have address info there, not
Appreciate help. This should be obvious, but it seems I am being oblivious?
On 5/14/20 11:32 PM, Joe Zeff wrote:
> On 05/14/2020 11:45 AM, Sreyan Chakravarty wrote:
>>> Why? Just for asking a question about a potential problem you've
>>> discovered on your machine?
>> Have you seen how Linus and others responds to n00b mails ?
> I don't follow such things, but I bet that how he answers depends on
> how the question's asked. Just describe the issue as you did here,
> ask if there's anything you need to do and don't sound like you're
Well, I went to the Fedora Kernel IRC, there the guys told me I can
ignore it and enjoy the performance benefits of a vulnerable SMT or
disable SMT and suffer the performance penalty.
I am just wondering if I have hit the zenith, you know, is there really
anything to be done anymore ?
In Xfce, I was looking at the settings for the mouse and clicked the
button to turn it off. Now the cursor sits in the middle of the screen
and I have very few options for control. A few pop ups with the
function keys but logout is the only useful one. Is there a key
combination that will activate the arrow keys to move the cursor so I
can pull down the menus and switch the mouse back on?
The Gnome update tool classifies updates as things that can be
immediately installed, and things that require a reboot to install. I
have never seen an update requiring users to login again, but that
should obviously be a state transition that the Gnome updater should
occasionally need as well. Someone pointed me to the tracer package for
CLI use, and it seems to work well in detecting these missing dependency
issues. However, no such mechanism exists as part of a GUI update.
Much as I disagree with the Gnome devs about the incorrect rationale for
reboots on an inode-based system, I can see the need to do this without
the functionality of something like tracer, for badly-designed apps that
do not correctly identify their run-time dependencies that need
restarting to maintain system integrity.
Its relatively difficult to find packages that can be immediately
installed, and it only seems to be seen in actual practice in maybe
1-in-50 updates. Since (say) 80% of updates are not "system" updates,
this seems intuitively very wrong. Reboots due to updating should be
very rare. Instead, they are 95% of the updates in practice. Clearly,
something is wrong.
This morning I ran the GUI updater. There were updates available for
the vim-filesystem and vim minimal packages. However, they are for some
weird reason marked as requiring a system restart in order to install.
That just stumps me. How can Vim possibly be an update requiring a
So, is there a problem in the dependencies lists of the packages, or is
it a bug in the Gnome updater app?
What could cause this issue?
When I open a terminal in FC 32 I see bleed through of my wallpaper as
See the line right up under the password prompt?
It will go away if you highlight the line with your mouse or type in
your password and hit enter. Its just kind of annoying to see.
I just had this start happening after I got this new monitor.
I didnt have this problem with the 17" monitor.
I download updates to the cache on cron at night.
I wanted to apply some updates, but not have to reboot
because I got a new kernel or something, so I did:
dnf update 'libre*'
That updated all the libreoffice packages.
Then I look at the cache, and it deleted *everything*,
not just the libreoffice packages it installed.
Should it really work that way?