users May 2021

users@lists.fedoraproject.org

100 participants
97 discussions

Maybe pipewire is better.
by Tom Horsley 18 May '21

18 May '21

If I paused a youtube video in chrome and came back to it later and pressed play, I almost always lost a few seconds of sound on f33 using pulseaudio. I don't have a large sample set yet, but it seems like that doesn't happen with the new pipewire audio.

2 1

WTF?! Gimp wants root password???
by Tom Horsley 18 May '21

18 May '21

Just started gimp for the very first time on fedora 34 and it pops up a authenticate dialog asking for root password. What in the great googly-moogly is this about? (Stderr has some message about xsane so maybe it wants to configure a scanner which I do not have on the system). How do I make it stop forever and never ask again?

2 2

Issues installing Fedora 34 on Mac Mini 2018 (w/ Kernel Panic Logs)
by Jorge Castello 18 May '21

18 May '21

Hi Folks, Thanks in advance to those who read this email to help me out! I'm super excited to try out Fedora 34 - please note that this is my first time installing Linux. I'm eager to get things working but I've run into a roadblock that I'm having tremendous difficulty figuring out. Please let me know if you can help. System Specs: - Mac Mini 2018 - macOS Big Sur Version 11.3.1 - Note: I replaced the original Mac Mini RAM with 32GB of Crucial RAM <https://www.amazon.com/gp/product/B071H38422/ref=ppx_yo_dt_b_search_asin_ti…> Installing Fedora: - I obtained a USB stick from my local Walgreens (16GB Infinitiv) - I downloaded the Fedora Media Writer, & proceeded to follow the instructions to write Fedora 34 to the USB - I also disabled secure boot & enabled the ability to boot from an external USB The problem: - When I restart my computer holding the options key, I see an orange option titled "EFI Boot" - When I click it, everything immediately becomes black and it's very clear that the Mac is restarting - When it restarts, it mentions that "A problem occurred that necessitated the reboot" - I've attached the full Kernel panic log to this email Some details from the Kernel Panic Log: - caused_by: "macos" - "os_version": "Bridge OS 5.3" - "kernel" : "Darwin Kernel Version 20.4.0: Thu Mar 4 23:34:36 PST 2021; root:xnu-7195.101.1~1\/RELEASE_ARM64_T8010", - "macOSPanicString" : "panic(EFI): Exception 6 occurred: Invalid Opcode\r\n\n - EFI Version: 1554.100.64.0.0 Thanks again for your input. I'd love to buy coffee, beer, or whatever you prefer if you can help me out. Looking forward to hearing from you! Best, Jorge -- *Jorge Castello* Phone: (323) 775-7523 Email <jorgio.castello(a)gmail.com> / LinkedIn <https://www.linkedin.com/in/jorge-castello-779002b2/>

2 1

Xbox 360 controller on Fedora 32
by Greg Woods 16 May '21

16 May '21

It has been a couple of years (which means 4 or 5 Fedora releases ago) since I did this, but I used to be able to play Xonotic using my Xbox 360 Wireless controller. Now I cannot get the controller to work properly in F32 (it works in Windows 10 so I know the hardware is OK). This most likely has something to do with the move from xboxdrv (which is no longer available in Fedora) to xpad kernel driver, and/or the move from the old js driver to evdev. The xpad driver comes with the current kernel, but what I cannot figure out is how to calibrate the controller. If I run Xontic with the controller connected, the game world just spins counterclockwise. This is a symptom of the controller needing to be calibrated, but I don't know how to do it. I tried using "jscal", but if I run "jscal -c" to calibrate it, it appears to work but doesn't. I can immediately run "jscal -t" and it will say it is not calibrated, and running "jstest" also shows it is not calibrated (several of the axes are not centered, i.e. show nonzero values in jstest). I attempted to download and compile xboxdrv, but it does not work due to Python 2 vs. 3 incompatibilities, and it doesn't look like any work has been done on xboxdrv in quite some time. If I try to make it, I get this: root@snowcrash xboxdrv-linux-0.8.8]# make scons scons: Reading SConscript files ... File "/local/src/xboxdrv-linux-0.8.8/SConstruct", line 34 print target ^ SyntaxError: Missing parentheses in call to 'print'. Did you mean print(target)? make: *** [Makefile:24: xboxdrv] Error 2 Certainly looks like Python version incompatibility. Can anybody point me to information on how to use an Xbox 360 controller on F32, or how to calibrate it when using the xpad driver? I have done a lot of Googling, but most of the articles I found mention things like "apt-get install xboxdrv", showing they were written for Ubuntu rather than Fedora and are wanting to use the xboxdrv driver. Thank you, --Greg

6 5

Gnome 4 F34 Startup Anomaly
by Stephen Morris 15 May '21

15 May '21

Hi, I am running Fedora in a Vmware Player VM. Having upgraded to F34 from F33, which installed Gnome 4, I have found that when I start "Gnome in Xorg" with the VM window maximised to full screen size (3840x2161) that it starts with the Gnome Dash open as if I had clicked on "Activities", which did not happen in F33 and earlier versions of Fedora. Is this standard functionality in Gnome 4, like the removal of extensions from tweakui into a separate application, that cannot be changed or is there a configuration option to change that behaviour? regards, Steve

2 4

F34 Wayland Resoluton Issues
by Stephen Morris 15 May '21

15 May '21

Hi, With running F34 in a Vmware Player VM, with whatever video driver Wayland is using (I've forgotten the commands to find out), xrandr is reporting that Wayland is not running at the correct resolutions. With the Vmware Player maximised to 3840x2075 resolution running Plasma, xrandr reports the connected resolution as being 2560x1383 even though the desktop seems to have scaled to 3840x2075. Under Gnome 4 with the Vmware Player maximised to 3840x2075, xrandr reports the connected resolution as 2560x1600 which seems to be correct based on the size the desktop is actually showing as, and it also refused to scale to the 3840x2075 resolution. When using xorg with both Gnome and Plasma, and having an xorg configuration file, specifying modelines statements as provided by CVT for all resolutions xrandr says is supported by whatever driver xorg is using (which from the xorg log seems to be a vesa driver) is connecting at 3840x2075. Given these situations is Wayland not working correctly, or is Wayland not coping properly with a VM, or does there need to be a configuration file specified somewhere for Wayland to fully support resolutions up to 4K? regards, Steve

1 0

dns glue or duct tape??
by Jack Craig 15 May '21

15 May '21

Hi folks With help from this list I recently updated my DNS configuration to provide for a primary and secondary DNS server where the primary DNS server is my host inside my domain and the secondary server is provided by AT&T I discovered that the secondary server on file with my registrar was wrong so I got the right data and they claim to have created a glue record but I'm still getting that host is not responding *primary dns ws.linuxlighthouse.com <http://ws.linuxlighthouse.com>* *Secondary server ns2.swbell.net <http://ns2.swbell.net>* would some kind soul direct me to a coherent glue (or duct tape) record test? also, given some domain name how do you know which top level domain name servers should be the first set that you query to locate your domain in question?? tia...

5 5

Network entanglement
by Robert McBroom 14 May '21

14 May '21

Installed Arch Linux on my Goflex Home NAS. I see it on the router from my ISP. It is connected through an access point to have a sufficient number of ethernet ports. I can't ping it using the ipv4 address I see on the router. There are two ipv6 addresses shown. One declares a lifetime of 3600s and the other says forever. ping and ssh work using the ipv6 address with a declared lifetime but not the "forever" Using a system that is connected to the wireless on the ISP router can ping the Arch system with the ipv4 address. ping 192.168.1.112 PING 192.168.1.112 (192.168.1.112) 56(84) bytes of data. From 192.168.1.185 icmp_seq=1 Destination Host Unreachable From 192.168.1.185 icmp_seq=2 Destination Host Unreachable From 192.168.1.185 icmp_seq=3 Destination Host Unreachable From 192.168.1.185 icmp_seq=4 Destination Host Unreachable From 192.168.1.185 icmp_seq=5 Destination Host Unreachable From 192.168.1.185 icmp_seq=6 Destination Host Unreachable ^ PING 2600:1702:4860:9dd0:210:75ff:fe28:5e30(2600:1702:4860:9dd0:210:75ff:fe28:5e30) 56 data bytes 64 bytes from 2600:1702:4860:9dd0:210:75ff:fe28:5e30: icmp_seq=1 ttl=64 time=0.301 ms 64 bytes from 2600:1702:4860:9dd0:210:75ff:fe28:5e30: icmp_seq=2 ttl=64 time=0.292 ms 64 bytes from 2600:1702:4860:9dd0:210:75ff:fe28:5e30: icmp_seq=3 ttl=64 time=0.298 ms 64 bytes from 2600:1702:4860:9dd0:210:75ff:fe28:5e30: icmp_seq=4 ttl=64 time=0.288 ms Knew just enough of ipv4 to almost get around but this is beating me.

4 15

How do I create an entry in the boot menu for an UEFI system?
by Lester Petrie 14 May '21

14 May '21

Hi all, The subject says what I want to do. The why is as follows. About a year and a half ago I bought a new machine with a 2 Tb SSD and a 2 Tb hard drive. It came with Windows on it, which I wanted to keep, so I found a Windows program that let me shrink the Windows partitions on both the SSD and the HD to 1 Tb, and tried to install Fedora on the free 1Tb SSD. But at the time the installer would not recognize the SSD, so I ended up installing on the HD, with a new EFI partition there. I was then able to select between Windows and Fedora from the boot menu. About the time F33 came out, I learned I needed to disable Raid in the Bios, and then I installed F33 on the free 1Tb SSD. This added Fedora to the Windows EFI partition, and replaced Fedora in the boot menu with the new version, so I was still able to select either Windows or Fedora 33 when I booted. And grub conveniently found my old HD installation and included it in the grub menu. Then something happened about a week ago, and the Fedora entry in the boot menu reverted to the HD entry (which is F31). I can do a rescue boot and chroot to F33, and then run efibootmgr, but I can't figure out how to create a legitimate, bootable entry for F33. The files all seem to still be in the right place, and I can create an entry in the menu, but it is not a valid entry. Any help will be greatly appreciated. -- Lester M Petrie

5 7

Re: How do I create an entry in the boot menu for an UEFI system?
by Lester Petrie 14 May '21

14 May '21

On 5/14/2021 6:40 AM, George N. White III wrote: > On Thu, 13 May 2021 at 17:40, Lester Petrie <lmpetrie(a)bellsouth.net > <mailto:lmpetrie@bellsouth.net>> wrote: > > On 5/13/2021 4:17 PM, George N. White III wrote: > > On Thu, 13 May 2021 at 16:56, Lester Petrie > <lmpetrie(a)bellsouth.net <mailto:lmpetrie@bellsouth.net> > > <mailto:lmpetrie@bellsouth.net <mailto:lmpetrie@bellsouth.net>>> > wrote: > > > > Hi all, > > > > The subject says what I want to do. The why is as follows. > About a > > year > > and a half ago I bought a new machine with a 2 Tb SSD and a > 2 Tb hard > > drive. It came with Windows on it, which I wanted to keep, so I > > found a > > Windows program that let me shrink the Windows partitions on > both the > > SSD and the HD to 1 Tb, and tried to install Fedora on the free > > 1Tb SSD. > > But at the time the installer would not recognize the SSD, so I > > ended up > > installing on the HD, with a new EFI partition there. I was then > > able to > > select between Windows and Fedora from the boot menu. About the > > time F33 > > came out, I learned I needed to disable Raid in the Bios, > and then I > > installed F33 on the free 1Tb SSD. This added Fedora to the > > Windows EFI > > partition, and replaced Fedora in the boot menu with the new > > version, so > > I was still able to select either Windows or Fedora 33 when > I booted. > > > > > > Did you also disable Windows "fastboot"? > > I am able to get to the boot menu the same as always, so I am pretty > sure Windows "fastboot" is not the problem. > > > > > And grub conveniently found my old HD installation and > included it in > > the grub menu. Then something happened about a week ago, and the > > Fedora entry in the boot menu reverted to the HD entry > (which is F31). > > Did the problem start with a kernel update? If I remember correctly, I had done an update, then shutdown and left for the weekend. When I booted back up, I came up in Fedora 31 (which I did not recognize immediately). I do believe there was a kernel in the update, but I can't be sure. > > > I can do > > a rescue boot and chroot to F33, and then run efibootmgr, > but I can't > > figure out how to create a legitimate, bootable entry for > F33. The > > files > > all seem to still be in the right place, and I can create an > entry in > > the menu, but it is not a valid entry. Any help will be greatly > > appreciated. > > > How did you create the entry? If the procedures in: > https://docs.fedoraproject.org/en-US/fedora/f33/system-administrators-guide… > <https://docs.fedoraproject.org/en-US/fedora/f33/system-administrators-guide…> > are messing up a bug report may be in order. The problem is not in the Grub menu, its in the basic UEFI boot menu. I currently can' bring up the correct Grub menu. > > You could experiment by making temporary changes to the grub menu > to work out the reason for the "not valid". You may get ideas by > comparing > the entries for the SSD Fedora with the entry for the HD Fedora, both > for | > | > |/etc/default/grub and in| /boot/efi/EFI/fedora/grub.cfg. The latter file > combines sections from various scripts but has comments that identify the > scripts for most entries. > > || > > > > > > > How do define "not valid"? Do you get an error, do you end up in > Windows, > > or ...? Did the problem occur after using Windows? Have you > checked the > > BIOS settings? > > Not valid means that if I select the entry I made from the boot > menu, I > get an error message saying it is not valid. I can still select > Windows, > or the HD version of Fedora successfully. > > > I've never encountered "not valid" from grub. You should have small > partitions for /boot and /boot/efi. Are they on the SSD or the HD? > Is either one full? Again I can't get to the correct grub menu. The entry in the UEFI menu that I have added is the one that give not valid when it is selected. /EFI on the SSD has entries fore both Fedora 33 and Windows 10, while /EFI on the HD has entries for Fedora 31. Something happened that caused the initial boot menu to regress to showing the HD Fedora instead of the SSD Fedora. I don't understand what efibootmgr is doing well enough to add a correct entry that points to /EFI/fedora/shimx64.efi. > > -- > George N. White III > -- Lester M Petrie

1 0

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