I'm having an issue running Fedora 33 and an external monitor
connected to an HDMI KVM switch. Here is the way it's connected:
Laptop thunderbolt 3 connector -> 4 port USB c to USB 3.0 hub -> USB to
HDMI adapter -> HDMI KVM switch.
The mouse and keyboard work, however Fedora 33 does not detect the
Even if I take the KVM switch out of the equation Fedora 33 still does
not find the external monitor.
This laptop also boots to Windows 10 and everything works fine there.
I have an older laptop running Fedora 31 connected as follows:
laptop HDMI port -> HDMI KVM switch.
This works fine.
Any help is appreciated.
The KVM switch is a 4 port AV Access HDMI 2.0 KVM Switch
I recently switched from a wireless USB mouse to a wired USB mouse.
I cannot reliably right click links in Firefox because the click interval
on the mouse isn't set up right.
How does one modify the mouse click parameters in Fedora and/or Plasma ?
I've looked in System->Settings but can't find anything for click intervals.
After re-installing f33 following a disk crash, I was having problems
that I believe were caused by nouveau trying to run on my gpgpu nvidia
2080 ti. I don't need or want a display manager running on it. How
can I tell if wayland and/or X is configured to run on that card, and
how can I disable it for that card? I also have a built-in vga that
runs a display.
I used this tutorial to build the Krita from sources: https://docs.krita.org/en/untranslatable_pages/building_krita.html#prepar....
This is the result of the rpmlint tool:
rpmlint krita.spec ../SRPMS/krita* ../RPMS/*/krita*
(none): E: no installed packages by name ../SRPMS/krita*
(none): E: no installed packages by name ../RPMS/*/krita*
0 packages and 1 specfiles checked; 0 errors, 0 warnings.
the krita.spec has this content:
Summary: Krita software version 4.2.2
Krita software version 4.2.2
cmake ../krita \
rm -rf $RPM_BUILD_ROOT
* Sat Jan 23 2021 catafest <catafest(a)yahoo.com>
Any idea what is wrong ?
I've been running F32 on a shiny new amd dual epyc workstation for
about 1 year. The system is now remote to me and not convenient to
About 1 week ago the system became unresponsive. I noticed errors
logged about I/O errors, so I guessed it was an issue with the SSD. I
went there and replaced the SSD with a shiny new samsung 1tb.
Reinstalled F33 and got my vpns going so I could access again from
But things are acting very strangely. Install was lightning fast.
But after a while the machine becomes unusable. Any command takes
minutes to react. I am unable to reboot it. sudo reboot after a very
long time does nothing.
I don't see anything interesting in /var/log/messages (I installed rsyslog).
When I can eventually get top to run, I see systemd is in D state.
There is plenty of free memory, and the machine has 64GB.
I'm going to visit again and this time yank out the nvidia gpu. This
is just a wild guess based on 1) it isn't critical for use right now
2) it places a load on the power supply just in case that's the issue
3) it's the only thing I can think to try.
Just wondering if anyone has any thoughts on how to troubleshoot this.
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 today's updates I saw these messages:
Not setting net/ipv4/conf/all/rp_filter (explicit setting exists).
Not setting net/ipv4/conf/default/rp_filter (explicit setting exists).
Not setting net/ipv4/conf/all/accept_source_route (explicit setting exists).
Not setting net/ipv4/conf/default/accept_source_route (explicit setting
Not setting net/ipv4/conf/all/promote_secondaries (explicit setting exists).
Not setting net/ipv4/conf/default/promote_secondaries (explicit setting
Should I care?
*Those who don't understand recursion are doomed to repeat it*
I just did an update to my F33 Workstation install and now I can log in. I
can't move the mouse pointer on the login screen. The keyboard doesn't
appear to work either. Both are USB devices.
My login manager is GDM. I'm running Plasma as my desktop manager.
I don't think I have ssh enabled on that computer. How do I resolve this ?