I'm using KDE on Fedora 35, and I have no applet for choosing an access
point. I believe that should be the Network Manager applet. It's installed
kf5-networkmanager-qt.x86_64 5.89.0-1.fc35 @updates
but I do no see it in the system tray.
I originally installed the XFCE spin and then installed KDE over that.
(This was because of problems with Wayland.)
PS I thought I sent this before, but do not see it in the archives.
I just installed Fedora 35 - KDE Spin on a new "Dell Inspiron 17 2-in-1
QHD+ Touchscreen" laptop.
If I go to system settings ->Input Devices -> Virtual Keyboard
and turn the Virtual Keyboard "on", then every time I click on an input
field the virtual keyboard pops up.
Is there a way to configure the Virtual Keyboard so it only comes up if
I click / touch an input field on the touchscreen, and not pop up if I
click with the mouse?
I'm running KDE/Plasma on Wayland both in my main workstation and in my
development virtual machine. On both machine it looks like Python is
unable to change the system's locale when running a script  in
Konsole, while the same script from a linux terminal runs fine.
I tried to create a new user and logging in as this new user the script
runs fine in Konsole also. I cannot find any setting which may cause
that, I also tried to delete the konsole configuration file under
.config so as to reset from scratch, but with my main user I can't get
to run the script right.
Any idea where I might look to find the cause?
I am considering a purchase of this laptop (see below):
Does anyone see any red flags or hardware that is incompatible with
Fedora 35 / KDE?
Thanks in advance
2021 Newest Dell Inspiron 7000 2-in-1 17 QHD+ Touch Premium Laptop,
Intel Core i7-1165G7,
1TB PCIe SSD,
Webcam, FP Reader, WiFi-6, Thunderbolt 4, Backlit KB, Windows 10 Home
Capacity:64GB RAM | 1TB PCIe SSD
Key Features and Benefits:
CPU:11th Generation Intel® Core™ i7-1165G7 Quad-Core Processor (4 Cores,
8 Threads, 12MB Intel Smart Cache, Base Frequency at 2.80 GHz, Up to
4.70 GHz at Max Turbo Speed)
Memory: 64GB DDR4 SDRAM
Hard Drive: 1TB PCIe NVMe M.2 Solid State Drive
Operating System:Windows 10 Home 64-bit, English
Display: 17.0-inch QHD+ (2560 x 1600) Truelife Touch Narrow Border IPS
Fingerprint Reader: Yes
Screen Resolution: 2560 x 1600
Backlit Keyboard: Yes
Ports: 1 x SD Card Reader, 2 x USB 3.2 Gen 1, 1 x Headphone/Microphone
Combo, 1 x HDMI 1.4b, 1 x Thunderbolt™ 4 with Power Delivery &
DisplayPort, 1 x power-adapter port
Graphics:NVIDIA® GeForce® MX350 with 2GB GDDR5 graphics memory
Media Drive: SD card reader
Audio:Stereo speakers with Waves MaxxAudio Pro, 2 W x 2 Realtek ALC3204
Wireless Connectivity:Intel Wi-Fi 6 2x2 (Gig+) and Bluetooth
Camera:Built-in 720p HD webcam with dual-array microphone
Battery: 4-Cell Battery, 68WHr (Integrated)
I first discovered this issue when a user complained she could not access a file I created on an NFS4 share.
I don't see this issue if I use fish:// to access any directory, local or remote.
We are on fully updated KDE fedora 34 and 35 systems, and this has been a problem for quite awhile, through many Fedora updates, possibly as far back as fedora 18 (arbitrary number). Until now I've usually just run chmod -R g+w on the share on the file server or locally when it matters, then went about my business. I have put it off too long and so did a bit of investigation.
This happens every time on both Konqueror and Dolphin. It never happens in Konsole. Meaning that if I open Konsole and cd to /fs1/work (the nfs share), and create a file or directory, the permissions are set to 664 and 2775 (SGID is set for all directories) as expected, with a umask of 002 for all users. Note that the umask on both servers and clients are set to 002.
So only Dolphin and Konqueror ignore the umask=0002 setting, and only when not accessing a file system via fish. This happen on both remote NFS shares and locally.
I have a logitech mouse that has been working well for a long time. Except that every once in a while it suddenly won't scroll one line at a time and instead requires multiple turns of the wheel to move a page.
I've been putting up with this as I am able to fix it by running solaar and toggling scroll wheel resolution off then on again. Only a couple of mouse clicks.
Now it seems to have gotten worse, or I am finally tired of having to stop my workflow to fix it. It seems to be related to the mouse going to sleep during inactivity, though it is random enough so I cannot be sure.
I am on the latest fedora 34 code, and I have been seeing issue since before 32.
Any ideas where to look for a solution?