users April 2020

users@lists.fedoraproject.org

133 participants
180 discussions

several Rawhide questions
by David 14 Apr '20

14 Apr '20

Is it correct to say Rawhide updated today from version 33-0.3 to 33-0.4, and what does that mean ? Or does that update just mean the repo was renamed or renumbered, or something like that ? Is 33.-0.4 noticeably better than 33-0.3, or are the tiny incremental improvements and regressions nearly impossible to notice without a magnifying glass ? Question 4 & 5: I have only one gtk2 package on my system and it seems to be related to the anaconda installer. gtk2 version 2.24.32-7.fc32 Is this package for those users not installing Gnome ? Will it hurt to delete gtk2 if I am using the Gnome DE, or does GIMP and other things need it ? I am using flatpaks for most of my additional software. Question or observation 6: I assume the reason, that the backgrounds keep updating in Rawhide ( yet remain identical to version 32 ), is simply due to lack of man/woman-power. Right ? David Locklear Live on The Edge - Live in Rawhide on Hardware

2 1

Re: SELinux is blocking hibernate
by sixpack13 14 Apr '20

14 Apr '20

On 14.04.20 12:49, Markus Schönhaber wrote: ... >> >> sudo ausearch -c 'systemd-sleep' --raw | audit2allow -M my-systemdsleep > > That way, ausearch will run with elevated privileges but audit2allow > will not. That's probably not what you intended. > yup, thanks for the hint. -- sixpack13

1 0

Desktop files in F31
by Greg Woods 14 Apr '20

14 Apr '20

I just had to replace the SSD in my laptop, which for reasons that would deserve a discussion thread of their own, I ended up having to do a complete reinstall. Then I restored all my home directory files. So what I have is a clean F31, but my own account from the old F30 system was restored. I am using "GNOME on Xorg" as the desktop environment. The problem I have is with Desktop files (in ~/Desktop). First I didn't see them at all, then found with some Googling that I needed to turn off display of the Trash icon, which now allows me to see the Desktop files. There are two issues: 1) The desktop icons are visible, but the Icons=file line in them seems to be ignored. 2) When I double click one, the Exec=command is executed, but it also opens a full-screen window that I figured out is "gnome-games". For #1, I first did a little research with dnf and discovered that I needed to install the "comps-extras" package to bring back the files in /usr/share/pixmaps/comps . But this did not fix the issue, even after I restarted gnome-shell (with ALT-F2 and "r"). So I logged out and back in again, but no joy. I did check to ensure that my account can read the specified image files. For #2, I would like to know how I can stop the execution of gnome-games. With a little trial and error, I discovered that if I iconify the gnome-games window the first time it comes up, then the Desktop icons double-click-execute properly, but if I instead kill the gnome-games window, then it pops up again next time I double-click an icon. A sample Desktop file is below. Both issues occur whether or not I have the leading "#!" line. #!/usr/bin/env xdg-open [Desktop Entry] Version=1.0 Encoding=UTF-8 Name=cobweb Name[en_US]=cobweb Exec=xterm -sb -T cobweb -bg forestgreen -fg white -e ssh -o 'FallBackToRsh no' -X cobweb -l greg Icon=/usr/share/pixmaps/fedora-logo-sprite.png Terminal=false MultipleArgs=false Type=Application GenericName[en_US]=cobweb Thanks for any pointers. --Greg

2 5

Where is the bootloader installed on GPT formatted disk?
by spike 14 Apr '20

14 Apr '20

Hi, I'm installing Fedora 31 with a kickstart file that contains bootloader --location=mbr #Same when omitting location parameter, mbr is default zerombr clearpart --all part /boot/efi --fstype=efi --size=200 --ondisk=sda part / --fstype=ext4 --size=1 --ondisk=sda --grow According to the documentation (https://docs.fedoraproject.org/en-US/fedora/f31/install-guide/appendixes/Ki…) this should install the bootloader to a BIOS boot partition: "On a GPT-formatted disk, this option will install stage 1.5 of the boot loader into the BIOS boot partition." clearpart seems to create a gpt on a UEFI machine and an mbr on a legacy BIOS machine per default, i.e. when no explicit disklabel parameter is specified. And indeed: # parted /dev/sda print Model: VMware, VMware Virtual S (scsi) Disk /dev/sda: 8590MB Sector size (logical/physical): 512B/512B Partition Table: gpt Disk Flags: Number Start End Size File system Name Flags 1 1049kB 211MB 210MB fat16 EFI System Partition boot, esp 2 211MB 8589MB 8378MB ext4 However, I've not specified a BIOS boot partition in the kickstart file, nor is one created automatically. Does anyone know where the bootloader is installed in this case? Or am I just reading the documentation wrong? Cheers!

3 4

fedora website -- firewall config/setup
by bruce 13 Apr '20

13 Apr '20

Hi. Forgive me! I'm setting up a test webserver/system, and I'm trying to make sure I get the firewall stuff setup correctly. Actually, I'm trying to make sure the firewall/selinux is all setup correctly. For the firewall, I'm trying to find example/samples of what the firewall cmds/services/ports should be to lock the system down. I've seen different sites that say different things, so I figured I'd ask here as well. So, if you have an example config/cmd display I can check out, that would be cool. At the same time, given that I'm new to selinux, if you have pointers/thoughts on how to set this up, I'm ready to "test"!! I don't want to run a test server with selinux turned off. If you also have websites that I should check, let me know. I may very well have missed the exact information I'm searching for. Thanks!

2 1

kickstart installation - DNF error in POSTIN scriplet of flatpak-selinux
by Sreyan Chakravarty 13 Apr '20

13 Apr '20

I am doing a Kickstart installation of Fedora Workstation from the Fedora Server NetInstall ISO. Everything is going as expected until I hit the installation of the package: flatpak-selinux. It fails with the error: DNF error in POSTIN scriplet of flatpak-selinux Well I wish Anaconda would let me continue the installation if one package failed, but no I have to exit the installer and begin downloading 2.13 GB again and again. First question, any way for Anaconda to ignore such errors in the Kickstart file ? Secondly, what should I do about this error ? An open bug already exists here: https://bugzilla.redhat.com/show_bug.cgi?id=1723118 and https://bugzilla.redhat.com/show_bug.cgi?id=1723940 One has a status of CLOSED and one has a status of MODIFIED. Now I can understand CLOSED since it was a duplicate but what does modified mean ? Also there are no solutions so what do I do now? I actually got this bug in VirtualBox once during the testing of my Kickstart file but it got resolved automatically on a next install. This is not the case for my laptop though, it hits the error every time. These are the packages in my Kickstart: %packages @^workstation-product-environment @admin-tools @authoring-and-publishing @c-development @container-management @d-development @development-tools @editors @headless-management @libreoffice @mate-applications @network-server @office @rpm-development-tools @sound-and-video @system-tools @window-managers Should I delete some packages ? flatpak-selinux seems like a mandatory package, is there any way to not install it ? Thanks. -- Regards, Sreyan Chakravarty

2 13

Email notification sound -
by Bob Goodwin 13 Apr '20

13 Apr '20

Something has changed in the last few days to cause the Thunderbird email notification sound to stop. Normally the preferences play button will test the tone but it now remains silent. I this unique to my system? Any ideas? This an up to date Fedora 31, with whatever Thunderbird was provided with the install, 68.6.0. Bob -- Bob Goodwin - Zuni, Virginia, Fedora Linux-31 XFCE

1 0

kf5
by Beartooth 12 Apr '20

12 Apr '20

I run F31 Mate. When I run dnf upgrade, I often get dozens of kf5 entries (23 today, by my count) -- presumably because I install and sometimes use K3B or Konqueror; I don't think I ever launch any other KDE app, at least not knowingly. In particular, I used to use Konqueror mainly for reading man pages, because it was the only way I knew to get a display I could read; but now it doesn't do man pages at all, alas! Also, formerly neither K3B nor Brasero always burned media I wanted; but one or the other always did. I'm wondering a couple things. Does all that kf5 stuff, sitting there almost (?) unused, amount to a security hazard? Does it slow anything down perceptibly? (I inveterately use too many browsers with too many tabs.) Might I ought to bite the bullet, removing K3B and Konqueror?

3 2

Custom ISO won't boot to Fedora
by Sreyan Chakravarty 12 Apr '20

12 Apr '20

I am unable to boot the custom ISO I have created. I have just created a Custom ISO from the Fedora Live ISO using the following command: genisoimage -U -r -v -T -J -joliet-long -V "Fedora-WS-Live-31-1-9" -volset "Fedora-WS-Live-31-1-9" -A "CDLABEL=Fedora-WS-Live-31-1-9" -b isolinux/isolinux.bin -c isolinux/boot.cat -no-emul-boot -boot-load-size 4 -boot-info-table -eltorito-alt-boot -e images/efiboot.img -no-emul-boot -o ../Fedora_Custom.iso . But I can't for the life of me figure out why I can't get the Live ISO to boot. Its stuck at the bootmenu. This is the directory structure for my custom ISO: [sreyan@localhost Fedora_ISO]$ tree . . ├── anaconda-ks.cfg ├── EFI │ └── BOOT │ ├── BOOT.conf │ ├── BOOTIA32.EFI │ ├── BOOTX64.EFI │ ├── fonts │ │ └── unicode.pf2 │ ├── grub.cfg │ ├── grubia32.efi │ ├── grubx64.efi │ ├── mmia32.efi │ └── mmx64.efi ├── images │ ├── efiboot.img │ ├── macboot.img │ └── pxeboot │ ├── initrd.img │ └── vmlinuz ├── isolinux │ ├── boot.cat │ ├── boot.msg │ ├── grub.conf │ ├── initrd.img │ ├── isolinux.bin │ ├── isolinux.cfg │ ├── ldlinux.c32 │ ├── libcom32.c32 │ ├── libutil.c32 │ ├── memtest │ ├── splash.png │ ├── vesamenu.c32 │ └── vmlinuz └── LiveOS └── squashfs.img 7 directories, 28 files And this is for the original: [sreyan@localhost Fedora-WS-Live-31-1-9]$ tree . . ├── EFI │ └── BOOT │ ├── BOOT.conf │ ├── BOOTIA32.EFI │ ├── BOOTX64.EFI │ ├── fonts │ │ └── unicode.pf2 │ ├── grub.cfg │ ├── grubia32.efi │ ├── grubx64.efi │ ├── mmia32.efi │ └── mmx64.efi ├── images │ ├── efiboot.img │ ├── macboot.img │ └── pxeboot │ ├── initrd.img │ └── vmlinuz ├── isolinux │ ├── boot.cat │ ├── boot.msg │ ├── grub.conf │ ├── initrd.img │ ├── isolinux.bin │ ├── isolinux.cfg │ ├── ldlinux.c32 │ ├── libcom32.c32 │ ├── libutil.c32 │ ├── memtest │ ├── splash.png │ ├── vesamenu.c32 │ └── vmlinuz └── LiveOS └── squashfs.img 7 directories, 27 files -- As you can see there is no difference except for the Kickstart file which I am not even using in isolinux.cfg This is the output of isolinux.cfg: default vesamenu.c32 timeout 600 display boot.msg # Clear the screen when exiting the menu, instead of leaving the menu displayed. # For vesamenu, this means the graphical background is still displayed without # the menu itself for as long as the screen remains in graphics mode. menu clear menu background splash.png menu title Fedora-Workstation-Live 31 menu vshift 8 menu rows 18 menu margin 8 #menu hidden menu helpmsgrow 15 menu tabmsgrow 13 # Border Area menu color border * #00000000 #00000000 none # Selected item menu color sel 0 #ffffffff #00000000 none # Title bar menu color title 0 #ff7ba3d0 #00000000 none # Press [Tab] message menu color tabmsg 0 #ff3a6496 #00000000 none # Unselected menu item menu color unsel 0 #84b8ffff #00000000 none # Selected hotkey menu color hotsel 0 #84b8ffff #00000000 none # Unselected hotkey menu color hotkey 0 #ffffffff #00000000 none # Help text menu color help 0 #ffffffff #00000000 none # A scrollbar of some type? Not sure. menu color scrollbar 0 #ffffffff #ff355594 none # Timeout msg menu color timeout 0 #ffffffff #00000000 none menu color timeout_msg 0 #ffffffff #00000000 none # Command prompt text menu color cmdmark 0 #84b8ffff #00000000 none menu color cmdline 0 #ffffffff #00000000 none # Do not display the actual menu unless the user presses a key. All that is displayed is a timeout message. menu tabmsg Press Tab for full configuration options on menu items. menu separator # insert an empty line menu separator # insert an empty line label linux menu label ^Start Fedora-Workstation-Live 31 kernel vmlinuz append initrd=initrd.img root=live:CDLABEL=Fedora-WS-Live-31-1-9 rd.live.image quiet label check menu label Test this ^media & start Fedora-Workstation-Live 31 menu default kernel vmlinuz append initrd=initrd.img root=live:CDLABEL=Fedora-WS-Live-31-1-9 rd.live.image rd.live.check quiet menu separator # insert an empty line # utilities submenu menu begin ^Troubleshooting menu title Troubleshooting label vesa menu indent count 5 menu label Start Fedora-Workstation-Live 31 in ^basic graphics mode text help Try this option out if you're having trouble starting Fedora-Workstation-Live 31. endtext kernel vmlinuz append initrd=initrd.img root=live:CDLABEL=Fedora-WS-Live-31-1-9 rd.live.image nomodeset quiet label memtest menu label Run a ^memory test text help If your system is having issues, a problem with your system's memory may be the cause. Use this utility to see if the memory is working correctly. endtext kernel memtest menu separator # insert an empty line label local menu label Boot from ^local drive localboot 0xffff menu separator # insert an empty line menu separator # insert an empty line label returntomain menu label Return to ^main menu menu exit menu end This is the same as the original ISO, there is no difference. If there is no difference why am I unable to boot into Fedora. These are the command line params from isolinux in both mine and original ISO. Mine: https://imgur.com/a/iV5SlW5 Original: https://imgur.com/a/6sfmiJr For me I am unable to progress any further than the boot screen. Where am I going wrong ? Regards, Sreyan Chakravarty

4 29

usb usb2-port8: Cannot enable. Maybe the USB cable is bad?
by Tom Horsley 12 Apr '20

12 Apr '20

What on earth is this message about? usb usb2-port8: Cannot enable. Maybe the USB cable is bad? earlier in dmesg it says: usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.05 usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 usb usb2: Product: xHCI Host Controller usb usb2: Manufacturer: Linux 5.5.15-200.fc31.x86_64 xhci-hcd usb usb2: SerialNumber: 0000:00:14.0 On the internet I can lookup the vendor and product and it says: USB 1D6B Linux Foundation 0003 3.0 root hub Which makes it sound as if usb2 is some kind of virtual hardware in the kernel, so how do I check this virtual cable that may be bad? DMESG shows this cable bad message once every 5 seconds, which is a bit annoying.

5 8

← Newer
1
...
10
11
12
13
14
15
16
17
18
Older →

Jump to page: