users May 2021

users@lists.fedoraproject.org

100 participants
93 discussions

KDE Desktop Scaling in Xorg
by Stephen Morris 11 May '21

11 May '21

Hi, I am running F34 in a Vmware player VM, and issue with KDE not starting in F33 seems to have been rectified F34, however KDE with Xorg will not scale. I have a file in /etc/X11/xorg.conf.d that supplies an xorg modeline to set the screen resolution to as close to 4K as the vmware player will allow. If I start the vm in the default window size when Gnome starts Xorg starts in 800x600 resolution, then when I maximise the window Gnome scales to the "4K" physical monitor resolution because of the existence of the modeline, which it also did in F33. However when I do the same thing with KDE it remains at 800x600 resolution, whereas in F33 before the issue that stopped KDE from running surfaced, maximising the window scaled the desktop resolution. Does anyone know why this is modeline statement is not working for KDE in F34 any more? regards, Steve

1 0

Gnome 4 in F34 Dash location
by Stephen Morris 11 May '21

11 May '21

Hi, I am running Gnome 4 in F34 after doing a system upgrade from F33. This environment is running in Vmware Player. The Gnome Dash is displaying at the bottom of the screen which I hate with a passion, how do I move it back to the left side of the screen like I had it in F33, I can't find any option in settings or Tweakui to do this? regards, Steve

1 0

nagios and dnf
by Łukasz Posadowski 11 May '21

11 May '21

Hi. Can You recommend a plugin, or a shell/prel/python wrapper for dnf checks in Nagios? Is there a widely accepted one? I'm finding only plugins for older yum versions, which, according to readmes, may not work with dnf. I would really like if it would use cache and do not "dnf update" every time. I wrote my own wrapper, but it rely on a local cron jobs and temp files, which I don't like. thanks -- Łukasz Posadowski

1 0

Restored f33 on new drive from a tarball now a problem
by Robert McBroom 11 May '21

11 May '21

New drive has the same msdos partition structure as the old. Legacy system with boot partition on a separate drive and from the root partition. System boots in mode 3 as specified but entering id and password flashes some text and returns to the login. Edited the grub entry to try a graphical boot but still get textmode. What can be done to get access to f33?

8 17

file associations for OVF files
by Paolo Galtieri 10 May '21

10 May '21

I recently ran into an issue with files with .ovf extension. The issue is that VMware Workstation will not import files that end in .ovf. A file that ends in .ovf shows up as follows of Fedora 34: file *.ovf returns XML 1.0 document, ASCII text What's interesting is that if you have VirtualBox installed and then try to open a .ovf file with VMware workstation it works because according to the VirtualBox documentation: Oracle VM VirtualBox creates file type associations automatically for any OVF and OVA files on your host OS. In fact if I run caja and click my way to the OVF file, right click on the file and look at the properties I get: Type: Open Virtualization Format (application/x-virtualbox-ovf) If I don't have VirtualBox installed I get Type: XML document (application/xml) So who should setup the file association for .ovf files? How do I go about changing the association for .ovf files from XML document to something else so that I can associate it with VMware Workstation? Any help is appreciated. I have reported this issue to VMware also. Thanks, Paolo

2 1

F34: wrong default audio output device
by Sam Varshavchik 10 May '21

10 May '21

After F34 upgrade the default audio output device is wrong after every reboot. After every reboot it is, apparently, a "PCM2902 Audio Codec Analog Stereo", which goes anywhere. It's not much of hassle to go into Volume Control and click on "Built-in Audio Analog Stereo", but it's rather annoying. Does anyone know where and how to set the default?

2 2

automatic updates corrupting grub loader
by John List 10 May '21

10 May '21

Something is updating on my Fedora 33 system and destroying my grub loader on a dual boot system. I have reinstalled a couple times and even tried Fedora 34. Fedora 34 won't install giving an error about not being able to update the /boot/efi directory. Fedora 33 at least starts the first time until the updates run. The first boot I get the grub menu. The second time after updates, I get a grub command line screen. 1. Automatic updates keep installing before I can troubleshoot. The first time I login, I disable and stop packagekit. But either it already sets automatic updates on next boot, or something else is running updates on next boot which is killing the grub menu. 2. I am assuming the grub loader is getting replaced when a kernel is updated. The original Fedora 33 kernel installed with the install media works. But after the updates, it does not work. Any help on disabling the automatic updates and then troubleshooting the dual boot issue would be appreciated. John

3 3

Any way to setup an https connection with Fedora 33 with ISP that blocks ports 80 and 443??
by Michael D. Setzer II 10 May '21

10 May '21

For a long time I've run my web server with no problem on port 8081 with my ISP. Have noticed that browsers are moving to want to only use https or secure connections. Have tired a few options but don't work. Created one setup with self-signed option, but when used it it came back with error about it being self-signed? Just tried and option using certbot, but it requires access on port 80?? Asked on there forum, and got a reponse that they don't work with that. They mentioned another option that works if port 443 is opened, but just checked that also seems to be block. Thanks.

2 1

suspend doesn't lock
by Frank Elsner 09 May '21

09 May '21

Hi, running an full updated Fedora 33 I have the following problem: For a few days I have been observing that the screen isn't locked when the system comes up after suspend. What could I have changed unintentionally or is a general problem? Regards, Frank

8 19

errors and weird touchpad behavior
by Anil F Duggirala 09 May '21

09 May '21

hello, I am running Fedora 33 on a Dell XPS 9550. My touchpad appears to be working ok, except for the fact that doing actual clicks (pressing on the touchpad is not working), but that appears to be a problem with the touchpad (because it also is not working really on Windows). I am getting the following error on startup: [ 2.770865] psmouse serio1: synaptics: device claims to have min coordinates query, but I'm not able to read it. [ 2.770870] psmouse serio1: synaptics: Your touchpad (PNP: DLL06e4 PNP0f13) says it can support a different bus. If i2c-hid and hid-rmi are not used, you might want to try setting psmouse.synaptics_intertouch to 1 and report this to linux-input(a)vger.kernel.org. [ 2.978865] psmouse serio1: synaptics: Unable to initialize device. Can anyone tell me if this might be an actual hardware issue at this point? Is there a possibility this error is telling me why "clicking" is not working? Is there any firmware of software I could install that might fix this problem (for any OS)? thank you,

1 0

← Newer
1
2
3
4
5
6
7
8
9
10
Older →