cisco ise helps safeguard your business. It lets you control access throughout your network, see the user and device details, and stop/contain any threats. You can also use it to enforce security policies throughout your network. As a result, it helps prevent any technical issues and strengthens your cybersecurity measures. In short, you can manage your network security with more ease. Everything can be handled in one place, as opposed to needing multiple different applications open at once.
With the SystemRescueCd I backed up the /dev/sda6 partition in /mnt/backup/ naming "diskimage"
After backing up operation the file has the automatic extension like "diskimage.000".
Is this file ok to restore?
If I name it "diskimage.gz" then it is automatically renamed with this extension "diskimage.gz.000"
But here below
the file is name like this:
Do I have to name with the .pimg extension during backup to restore correctly?
And how can I restore it?
I upgraded to F31 late last week and I am missing the MiscFixed 16 font that I prefer using. Where would I find it?
Important Notice: This mailbox is ignored: e-mails are set to be deleted on receipt. Please respond to the mailing list if appropriate. For those needing to send personal or professional e-mail, please use appropriate addresses.
I am developing a Qt app in Fedora 31 using the default GNOME wayland session and I am very sorry to see the state of Qt in this configuration.
1) qt creator crashes often (https://bugzilla.redhat.com/show_bug.cgi?id=1773356) the crash report tool does not seem to help
2) drag & drop does not work in Qt creator (and in no other Qt app) (https://bugzilla.redhat.com/show_bug.cgi?id=1774762 and https://bugreports.qt.io/browse/QTBUG-80303)
3) main window geometry cannot be restored when the application restarts (https://bugreports.qt.io/browse/QTBUG-80612)
I think GNOME / Wayland / Qt it is just not ready and should not be offered as the default desktop session for Fedora.
If I force Qt to use X11 emulations, things are much better.
Probably Qt is responsible (but in the bug reports someone says that KDE / Wayland works well), and GNOME is not Qt, but there are so many Qt apps, that sending new users to a non working environment re-enforces the fact that "just works" is not true in Linux.
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]
1. Do the 2 files need to be in a specific place to do the install? If
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")?
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.
Hardware/Software basic deets:
Dell XPS 13 L322X laptop, vintage circa 2013.
1TB Samsung Solid state drive
F32 - everything has been updated
In this extended period of Covid-19 isolation, is there a
videoconference package available?
Hosted systems like Zoom are not opensource, do not use a browser as a
client, feed connection data to Facebook, only allow 2 participants for
free, and not available for a local install.
I thought of Webex, but its Cisco. Maybe its just me :-)
I took a quick look at Jitsi, but users say it has a fatal extreme
processor utilization bug, the rpm packages are 3 years out-of-date, and
does not seem to be present in the normal rpm repos.
I also took a quick look at BigBlueButtion, which looks pretty good.
However, it only runs on an ancient version of Ubuntu, and uses a shell
installer for some unknown reason.
This seems like a major application type that appears to be completely
missing from the repos. Is anyone building one, and just hasn't
announced it yet?
DNF failed first try, I ran clean metadata and re-tried, got same result:
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
The downloaded packages were saved in cache until the next successful
You can remove cached packages by executing 'dnf clean packages'.
Error: SQLite error on "/var/lib/dnf/history.sqlite": Reading a row
failed: database disk image is malformed
I have no idea why this happening, have done nothing unusual? *Bob*
Bob Goodwin - Zuni, Virginia, USA
FEDORA-32/64bit LINUX XFCE Fastmail POP3
If you are not interested in Rawhide basics, please hit
the delete button now. This post is aimed at people
who may not know what Rawhide really is, or how it
gets updated, etc.
The link below is a Dropbox link, showing a list of
packages installed on my computer.
My Rawhide computer has been performing nominally, ( without hiccups )
since I installed the unofficial iso.
This list shows that some of the packages come from Anaconda. I assume,
( feel free to correct
me ), that those packages have not changed, since I did the install.
Also note there are two different suffixes in the filenames "fc32," and
"fc33." Obviously, fc33 are the packages that have
been updated and re-labeled to show they are going to be in the upcoming
Version 33 of Fedora. What those suffixes actually
do in the server, meaning as to what repo they are in, I will let someone
else explain all that. I assume those packages with fc32 suffix are
identical to what you have if you are using fc32 Workstation. For
example, the package "bash" is apparently fc32.
As you can see, most of the important packages are updated in someway and
have the fc33 suffix. Meaning lots of hardwork has
been done by people. Thank you to those volunteers, etc.
Note that there is one package "fc31," that being "trousers."
As you can see, the kernel is the latest rc7 available. Since 5.7.0
will go stable in a few days, I assume that the next kernel I
get will be 5.8.0.rc0.git### or something like that, or at least that will
be the kernel on my install, in about two weeks. Feel free to correct
Unfortunately, I have had little access to my computer in the past month,
due to not having a stable place to reside, and that will
likely be the case for me this summer.
I am looking forward to reading about how Fedora performs on the upcoming
Raspberry Pi 4, with 8 GB of RAM.
Another sad note, is that due to my financial situation, I had to downgrade
to a less expensive phone service provider, and in doing
so I ended up with a refurbished iPhone. I have never used an iPhone
before, and now I am doing most of my internet needs on
the iPhone. Actually, I am just using the hotspot on it, and still
doing most of my stuff on my old Android Alcatel 3V.
Novice Rawhide user
P.S. I would like to give a shout out to my buddy, Flannigan. In all
my 25 plus years of using the internet, he is the
first person I have bumped into on the internet, that we knew from other
hobbies, other than Linux. I will let him explain that
if he wants.
Well guys, its time to panic once again.
I just found out my system is vulnerable to the new Crosstalk
vulnerability by running the popular Meltdown OVH script.
More about the vulnerability over here:
These exploits get worse each time, this one affects all cores.
This is how I tested for the vulnerability.
Downloaded spectre-meltdown-checker.sh via :
wget https://meltdown.ovh -O spectre-meltdown-checker.sh
and then just executed with sudo.
This is the output I got:
* SRBDS mitigation control is enabled and active: NO
> STATUS: VULNERABLE (Your CPU microcode may need to be updated to mitigate the vulnerability)
Full output here:
As you can see the tool specifies that my microcode is not the latest.
That being said, where do I find the latest microcode from ?
My OS is fully updated, and the firmware and microcode is also latest
according to DNF:
$ sudo dnf update linux-firmware
Nothing to do.
$ sudo dnf update microcode_ctl
Nothing to do.
So where is the microcode update in Fedora for this ??
Canonical has already published microcode updates for this, as shown here:
It kind of seems frustrating that a bleeding edge distro like Fedora still hasn't
provided updates yet. While Ubuntu a distro that doesn't always use the latest
software already has a fix.
What can I do now ? What is progress for Fedora ?
Will the microcode from Canonical work for Fedora ? Dumb question I know but I
Let me know if any further info is required.
Some more info about my CPU:
What is everyone else in the community doing about this ?