how to install zoom client.
by home user
Good morning,
(f-29)
(background)
Last week, I was to participate in a "Zoom" meeting for a charity that
I'm involved in. I have the needed software on my rarely-used windows-7
box. But I could not complete the windows-7 login (some problem with a
windows-7 service). I've since found there is a "Zoom" client for
Fedora. "dnfdragora" does not find anything for it. But I found a web
page that I hope has what I need. I've downloaded the package
("zoom_x86_64.rpm"), and I've downloaded a "Public Key"
("package-signing-key.pub"). The web site from which I've downloaded
these also has a line:
Key fingerprint: [some 40 hex digit number]
(4 questions)
1. Do the 2 files need to be in a specific place to do the install? If
yes, where?
2. Do I need to be "root" to do the install?
3. What do I do with the "Key fingerprint"?
4. How do I do the install (preferably using "dnf")?
thanks,
Bill.
3 years, 5 months
Firefox stability?
by Max Pyziur
Greetings,
Lately, I've noticed that different tabs that I have open in Firefox are
crashing. This seems to have started recently. They can be restored
easily, but there's a nuisance factor here.
Anyone else?
Hardware/Software basic deets:
Dell XPS 13 L322X laptop, vintage circa 2013.
1TB Samsung Solid state drive
8GB RAM
F32 - everything has been updated
Max Pyziur
pyz(a)brama.com
3 years, 6 months
dnfdragora not making all updates available
by Temlakos
Everyone:
The reform of dnfdragora to put all available updates into groups is not
updating everything, and not updating many things it used to update
without fail.
The only reliable thing my system will update, are applications and
various desktop relevant things. And not all applications, either.
Basically, if it is not in a group, dnfdragora will not update it and I
have to fall back on the traditional Software Management application to
do these updates.
The following packages typically fail of update and even of selection on
dnfdragora:
* The kernel and related packages.
* Browsers other than Firefox.
* Application packages from repositories foreign to the Fedora
community, such as "bunkus.org" (mkvtoolsnix), google (for chrome), and
Adobe Systems Incorporated.
* System packages that run background processes that normally load
themselves at startup and stay resident.
I've checked for all possible settings I can make to solve this problem.
No joy.
I've tried refreshing metadata (which, by the way, takes fifteen minutes
every time). No joy.
I tried selecting "not showing the groups." No joy.
Suggestions?
Have any of you noticed the same issue?
My desktop is KDE.
"Check for updates" counts all packages that need an update. But again:
if they're not in a group, they're not available for a selection.
(Note: if you're going to tell me to report this as a bug, I need to
know exactly where and how. I've filed bugs in the wrong place and they
get no action.)
Temlakos
3 years, 7 months
Virtual terminals - no VISIBLE I/O
by Jon LaBadie
On Fedora 32 Workstation.
My VTs are functional but there is not visible indication
of I/O. By that I mean, I get no login or password prompt.
But I can blindly login. I get no shell prompt. But I
can blindly enter commands that run but they show no output
in the VT.
The VT system is controlled by systemD. After a boot and upon
graphical login this is the status:
$ systemctl | grep getty
system-getty.slice loaded active active system-getty.slice
getty.target loaded active active Login Prompts
A "ps -ef | grep getty" gives no output
After I try to access VT #3 (<Ctl><Alt><Fn3>) without logging in,
I get an additional line from the above command:
getty(a)tty3.service loaded active running Getty on tty3
And the ps pipe gives this:
root 4237 1 0 13:23 tty4 00:00:00 /sbin/agetty -o -p -- \u --noclear tty3 linux
I didn't think the display manager would affect the VT system, but
just in case I tried gdm, sddm, lightdm. No differences.
Any clue as to why there seems to be no video connection to the VTs?
Jon
--
Jon H. LaBadie jonfu(a)jgcomp.com
3 years, 7 months
gnome-terminal
by Patrick Dupre
Hello,
When I lauch gnome-terminal, I get
Maximum number of clients reachedUnable to init server: Could not connect: Connection refused
# Failed to parse arguments: Cannot open display:
Why that?
===========================================================================
Patrick DUPRÉ | | email: pdupre(a)gmx.com
Laboratoire interdisciplinaire Carnot de Bourgogne
9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE
Tel: +33 (0)380395988
===========================================================================
3 years, 7 months
Questions for the hard disk recovery gurus
by Philip Rhoades
People,
I know this is not strictly a Fedora issue but I only use Fedora so I am
hoping people here can help - maybe we should have a separate mailing
list or forum topic for this sort of hard disk stuff?
Just after a full backup (fortunately) the 7.2TB /home partition
(/dev/sda5) on my email server somehow got corrupted. After I realised
there was a problem, I unmounted the partition and tried:
e2fsck -y /dev/sda5
but the process hangs after “Clone multiply-claimed blocks<y>?” and the
disk goes quiet - I could still break out with CTRL-C but I can't get
past this point in the attempted fix process. So I thought I would just
produce a list of the affected files and then just delete the inodes or
just restore from backup but when I tried:
debugfs -R "ncheck 187536544" /dev/sda5
it took hours to find nothing but printed screenfulls of:
ncheck: "Directory block checksum" does not match directory block
while calling ext2_dir_iterate
and there are 1069 inodes to check!
I am guessing that if I just try to delete each of the inodes with:
debugfs -R "clri <inode>" /dev/sda5
that it would take weeks! So unless someone can suggest a faster method
of fixing the partition (mainly just as an exercise now) or at least
just working out what is wrong with it, I guess I will just have to
re-create the partition?
Thanks,
Phil.
--
Philip Rhoades
PO Box 896
Cowra NSW 2794
Australia
E-mail: phil(a)pricom.com.au
3 years, 7 months
Grub2 entanglement
by Robert McBroom
What does one do in the new environment to run different versions of
linux on different drives of a system. One system has f31 on sda and
centos7 on sdb. With legacy grub I could call the boot of one system
from the other and vice versa. No more. Switching drives in the bios no
longer works. I can kludge things by putting the boot files from the
centos7 system in the f31 boot and putting the boot stanza in the as a
custom entry in grub.d along with the stanza for Windows. All the
entries in /boot/1oader point to the f31 system. grubenv is only
appropriate for f31.
Second system has f32 on sda and f31 on sdb. The f32 system is the only
one that will boot. There are entries in /boot/loader for both. but only
f32 will boot. Seems to be an issue on boot in the root versus boot in
a boot partition.
Robert McBroom
3 years, 7 months
Update to F32 remotely
by Neal Becker
I've been holding off on updating my server at a remote site from F31 ->
F32 because I hate to risk something going wrong at this time of covid,
when I have no access to the remote. At some point I guess I will have to
take the risk. I believe the update can be done entirely remotely.
Thoughts?
--
*Those who don't understand recursion are doomed to repeat it*
3 years, 7 months
resume from suspend to RAM not working properly with / on btrfs
by Lukas Middendorf
Hi,
TL,DR: I have problems with resuming from suspend to RAM on my new Ryzen
computer. I have only seen this happen if I put root onto a btrfs
subvolume, not on ext4. The proprietary nvidia driver seems to be one
additional factor, but I have also seen this with the nvidia driver
removed. Experienced something similar?
I have upgraded my PC with a Ryzen 7 3700X, Asus ROG STRIX x570-E Gaming
and a Samsung 970 EVO PLUS NVMe SSD.
The existing Fedora 32 system from my old SATA SSD worked flawlessly
(with suspend to RAM).
For the last years I have always used ext4 (previously ext3) on
monolithic root partitions (no separate /boot or /home, but separate
data partitions) on mbr partitioned SATA disks, booting in legacy BIOS mode.
With the new drive I wanted to make the switch to GPT, UEFI boot and
btrfs (ext4 /boot). I didn't want to install a new system (with those
months of finding programs you have not yet installed) but opted to just
copy over my old F32 system.
So I used gparted to set up the GPT and a 200MiB EFI System partition,
three 500MiB boot partitions (for different distributions or Fedora
versions), a 16GiB swap partition and the rest of the drive as btrfs. In
the btrfs volume I created a fedora32 subvolume with a nested home
subvolume. I then mounted everything (/, /boot, /boot/efi) on my old f30
system and copied over everything from my f32 partition. After bind
mounting /sys, /proc and /dev I chrooted into the new copy, adjusted the
fstab, installed all efi related packages, ran grub2-mkconfig and made
sure the kernel paths in /boot/loader/entries were correct. I then
switched to the system rescue mode of a f32 netinstall USB drive booted
in UEFI mode (to get access to the efivars) to install grub with target
x86_64-efi and regenerate the initrds.
After that everything booted up and seemed to work until I tried suspend
to RAM. It went to sleep properly, but resuming did not complete. After
waking up it just continued to display the last four kernel messages of
the suspend action (suspending processes, ..., suspending terminal). It
reacted to emergency sync sysrq (HDD LED blinking) but the other sysrq
keys did not seem to work ("u" also provoked a blinking LED sometimes).
This happened from within KDE as well as from text terminal with
systemctl suspend. Log files after reboot just had entries until shortly
before suspend (processes suspended, all except the last CPU core
disabled, unneeded drives stopped) but not from the attempt to resume.
I assumed this to be caused by the NVMe-SSD and unsuccessfully tried
some suggested solutions that have worked for others with suspend
problems with NVMe-SSDs (disabling acpiphp, disabling d3cold_allowed).
Since I had too many variables I trashed the content of the new SSD and
started anew with a mbr partition table to boot in legacy BIOS mode. I
just plain cloned the original f32 partition to the NVMe SSD, adjusted
the fstab, updated grub.cfg, recreated the initrds installed grub to the
mbr and everything worked, including suspend.
I then again did another copy with btrfs root (and ext4 /boot), this
time on MBR with BIOS boot and it again showed the previous suspend
problem. No swap space this time.
I also did a new install of F32 (from Everything Netinstall with Plasma
Workspace profile) with btrfs root and ext4 /boot, which suspended
correctly at the beginning but failed to resume after I installed the
proprietary nvidia driver for my graphics card. Removing the nvidia
driver (and updating grub.cfg and the initrds) returned that install to
a working state.
I then removed the nvidia driver also on the second non-working copy of
my old system (checked that "lsmod | grep nvidia" does not show
anything), but suspend still did not work. It did not show the kernel
messages but just a black screen with frozen mouse pointer. So the
nvidia driver seems to be one way to trigger it but there apparently are
other ways to reach the non-working state.
I have now trashed everything again and settled for GPT, UEFI and root
on ext4 (no separate /boot) with /home on a btrfs subvolume as a
compromise. This seems to be working fine. As I now have a btrfs /home
my problem is also likely not caused by having files open on a btrfs
partition.
The problems were with kernels 5.7.9-200.fc32 and 5.7.10-201.fc32 . I
should likely also have tried an older kernel, but have not yet done so
(might try to get a new non-working test setup tomorrow).
Nvidia driver packages were version 440.100 from rpmfusion on the new
install and a rebuild of the f33 packages of 450.57 for the existing
install.
My hardware:
- AMD Ryzen 7 3700X
- Asus ROG STRIX x570-E Gaming (latest BIOS version 2407)
- Samsung 970 EVO PLUS NVMe SSD
- Geforce GTX960
Tested setups:
Old Ext4 on MBR, SATA: working
copy of old Ext4 on MBR, NVMe: working
copy to BTRFS (Ext4 /boot, with nvidia) on GPT, UEFI, NVMe: not working
copy to BTRFS (Ext4 /boot, with nvidia) on MBR, BIOS, NVMe: not working
copy BTRFS (Ext4 /boot; nvidia removed) on MBR, BIOS, NVMe: not working
new on BTRFS (Ext4 /boot, w/o nvidia) on MBR, BIOS, NVMe: working
new on BTRFS (Ext4 /boot, with nvidia) on MBR, BIOS, NVMe: not working
copy on Ext4 (btrfs /home, with nvidia) on MBR, BIOS, NVMe: working
copy on Ext4 (btrfs /home, with nvidia) on GPT, UEFI, NVMe: working
So this seems to be unrelated to the partition table type and the boot
mode. If it is related to NVMe this is just one factor. I have just
observed it with / on BTRFS. On a new install the proprietary nvidia
driver is also needed to trigger this, but on my old install it also
occurred with the nvidia driver removed.
Things I have not tried yet (might try when I find the time again):
- older kernel version
- ext4 root but with separate boot partition (unlikely cause)
- non-nvidia graphics card (don't have one)
- logging kernel messages on different device using some serial output
(there is a way, right?) to see what really is failing
Has anybody else experienced something similar? Is there something I
might have missed in the btrfs conversion process?
This might become interesting with F33 with lots of new btrfs systems.
Best regards,
Lukas
3 years, 7 months
