users June 2024

users@lists.fedoraproject.org

73 participants
65 discussions

NetworkManager fights selinux
by Robert McBroom 27 Jun '24

27 Jun '24

Fedora 40 system cold boot shows 10 selinux errors from NeworkManager on files in /run/NeworkManager. The contents of this directory seem to be created during the boot process. They are owned by root and writeable, but apparently not in the correct selinux context. My attempt to submit a bug to bugzilla failed for some reason. This status has persisted through several of the latest kernels. The connection to the network ethernet and wifi worked. SELinux is preventing NetworkManager from 'create' accesses on the directory devices. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that NetworkManager should be allowed create access on the devices directory by default. Then you should report this as a bug. You can generate a local policy module to allow this access. Do allow this access for now by executing: # ausearch -c 'NetworkManager' --raw | audit2allow -M my-NetworkManager # semodule -X 300 -i my-NetworkManager.pp Additional Information: Source Context system_u:system_r:NetworkManager_t:s0 Target Context system_u:object_r:init_var_run_t:s0 Target Objects devices [ dir ] Source NetworkManager Source Path NetworkManager Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages SELinux Policy RPM selinux-policy-targeted-40.22-1.fc40.noarch Local Policy RPM selinux-policy-targeted-40.22-1.fc40.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Permissive Host Name (removed) Platform Linux (removed) 6.9.4-200.fc40.x86_64 #1 SMP PREEMPT_DYNAMIC Wed Jun 12 13:33:34 UTC 2024 x86_64 Alert Count 21 First Seen 2024-05-28 00:04:33 EDT Last Seen 2024-06-27 10:24:55 EDT Local ID 63afcb5d-e83d-4a9e-8a3a-8d3abdac3b16 Raw Audit Messages type=AVC msg=audit(1719498295.202:132): avc: denied { create } for pid=7409 comm="NetworkManager" name="devices" scontext=system_u:system_r:NetworkManager_t:s0 tcontext=system_u:object_r:init_var_run_t:s0 tclass=dir permissive=1 Hash: NetworkManager,NetworkManager_t,init_var_run_t,dir,create SELinux is preventing NetworkManager from open access on the file /run/NetworkManager/conf.d/10-globally-managed-devices.conf. Plugin: restorecon SELinux denied access requested by NetworkManager. /run/NetworkManager/conf.d/10-globally-managed-devices.conf may be mislabeled. /run/NetworkManager/conf.d/10-globally-managed-devices.conf default SELinux type is NetworkManager_var_run_t, but its current type is init_var_run_t. Changing this file back to the default type may fix your problem. File contexts can be assigned to a file in the following ways. Files created in a directory receive the file context of the parent directory by default. The SELinux policy might override the default label inherited from the parent directory by specifying a process running in context A which creates a file in a directory labeled B will instead create the file with label C. An example of this would be the dhcp client running with the dhcpc_t type and creating a file in the directory /etc. This file would normally receive the etc_t type due to parental inheritance but instead the file is labeled with the net_conf_t type because the SELinux policy specifies this. Users can change the file context on a file using tools such as chcon, or restorecon. This file could have been mislabeled either by user error, or if an normally confined application was run under the wrong domain. However, this might also indicate a bug in SELinux because the file should not have been labeled with this type. If you believe this is a bug, please file a bug report against this package. SELinux is preventing NetworkManager from 'setattr' accesses on the file lo.nmconnection. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that NetworkManager should be allowed setattr access on the lo.nmconnection file by default. Then you should report this as a bug. You can generate a local policy module to allow this access. Do allow this access for now by executing: # ausearch -c 'NetworkManager' --raw | audit2allow -M my-NetworkManager # semodule -X 300 -i my-NetworkManager.pp Additional Information: Source Context system_u:system_r:NetworkManager_t:s0 Target Context system_u:object_r:init_var_run_t:s0 Target Objects lo.nmconnection [ file ] Source NetworkManager Source Path NetworkManager Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages SELinux Policy RPM selinux-policy-targeted-40.22-1.fc40.noarch Local Policy RPM selinux-policy-targeted-40.22-1.fc40.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Permissive Host Name (removed) Platform Linux (removed) 6.9.4-200.fc40.x86_64 #1 SMP PREEMPT_DYNAMIC Wed Jun 12 13:33:34 UTC 2024 x86_64 Alert Count 40 First Seen 2024-05-28 00:04:36 EDT Last Seen 2024-06-27 10:24:55 EDT Local ID 93e082cc-423c-4a80-96d7-58e62cf9f527 Raw Audit Messages type=AVC msg=audit(1719498295.857:143): avc: denied { setattr } for pid=7409 comm="NetworkManager" name="lo.nmconnection" dev="tmpfs" ino=2901 scontext=system_u:system_r:NetworkManager_t:s0 tcontext=system_u:object_r:init_var_run_t:s0 tclass=file permissive=1 Hash: NetworkManager,NetworkManager_t,init_var_run_t,file,setattr

1 0

F40 kernel 6.9.* and VMware 17.5.* question
by Mark C. Allman 27 Jun '24

27 Jun '24

Anyone have VMware Workstation or Player 17.5.1 or 17.5.2 working on the 6.9.* kernels? The kernel modules from VMware haven't worked in quite a while. They don't compile for the 6.9.* kernels, and, if I'm remembering correctly, they don't compile when running the 6.8.* kernels either. I have the code for vmnet and vmmon from https://github.com/mkubecek/vmware-host-modules/tree/workstation-17.5.1. There are all kinds of exceptions when the kernel modules are loaded at boot time. I tried running vmplayer as a test -- it "ran" but trashed the kernel and required hard reboots. One of the tests totally bricked my laptop (that was fun to recover). I'm currently running kernel 6.9.5-200.fc40.x86_64and all packages are up to date. The laptop is a Dell Inspiron 7591, Core i7-10510U CPU, 16GB of ram. -- Mark

5 6

update
by Patrick Dupre 27 Jun '24

27 Jun '24

Hello, When I make dnf system-upgrade download --releasever=40 --allowerasing Numerous packages are going to be removed. How can I get the list of these packages? Thanks =========================================================================== Patrick DUPRÉ | | email: pdupre(a)gmx.com ===========================================================================

2 1

Cannot enable extensions after upgrade from F39 to F40
by Jacek Pliszka 26 Jun '24

26 Jun '24

Hi! I have upgraded from F39 to F40 and my gnome shell extensions stopped working. e.g. $ gnome-extensions list | grep dock dash-to-dock(a)micxgx.gmail.com $ gnome-extensions enable dash-to-dock(a)micxgx.gmail.com $ gnome-extensions list --enabled returns nothing. Any hints? I have some deja vu that it is flat/snap related somehow...

1 0

password issue with f40
by Michael Hennebry 26 Jun '24

26 Jun '24

I recently installed F40 from DVD. F40 and I are having a difference of opinion regarding what password I gave the initial user. F40 is winning. I find it hard to believe I typed in the same wrong password twice, but it's F40's opinion that counts. I try to login: click on the user and type in my password. F40 just goes back to the select a user screen. There is only one user. My usual strategy is to boot a live disk and to edit the passwd and shadow files directly. It did not work. Now F40 no longer even gives me a chance to type in a password. It just blinks at me and goes right back to the select a user screen. What is going on? How do I fix it? I would much prefer not to reinstall. Even if I have to reinstall, I would like to know what is going on. My line from /etc/passwd : hennebry::1000:1000:The Michael:/home/hennebry:/bin/bash My line from /etc/shadow : hennebry::19893:0:99999:7::: -- Michael hennebry(a)mail.cs.ndsu.NoDak.edu "SCSI is NOT magic. There are *fundamental technical reasons* why it is necessary to sacrifice a young goat to your SCSI chain now and then." -- John Woods

14 35

Interesting mount problem - F40
by Frank Bures 24 Jun '24

24 Jun '24

Hi, I have a small SSD that I use for /boot and /boot/efi partitions - /dev/sda I boot from /dev/sda I have another small SSD that I use as a dd backup of /dev/sda - /dev/sdg After update to a new kernel, I dd the /dev/sda to /dev/sdg so that in case of a failure I could boot from /dev/sdg. This scenario worked perfectly till several weeks ago. What is happening now is that the machine boots from /dev/sda, but then mounts /dev/sdg for its /boot and /boot/efi. So in df I see /dev/sdg instead of /dev/sda that the machine booted from. I solved the problem by editing /etc/fstab and pointing /boot and /boot/efi to the relevant /dev/sda[1-2] instead of the original UUID. Question: is this solution OK or have I done something wrong? Is there a better way of solving this? Thanks Frank -- <listfrank1(a)gmail.com>

9 12

Risc-v computer with Fedora on it?
by Ryan Bach 23 Jun '24

23 Jun '24

I can't wait until this is real.

4 10

Firefox foul ups
by Steve Underwood 22 Jun '24

22 Jun '24

Is anyone else having problems with Firefox on FC39 with XFCE recently? After rock solid operation for a long time, in the last 2 or 3 weeks the UI has been fouling up every day or two when I do some seemingly mundane operation in Firefox. A couple of times Firefox has crashed after a few seconds. The foul ups sometimes only affect the Firefox windows, and other windows still work OK. Sometimes the whole desktop fouls up, and I have to switch to a text only screen and kill Firefox. That restores normal desktop operation for all the other windows. Steve

6 6

crond
by Patrick Dupre 22 Jun '24

22 Jun '24

Hello, I have a backup launched by cron.weekly However, since F40, after it has run a first time and ended, another backup is started. This messed up the backup. When starting, the first crond sent (ps -aux | grep -i backup | mail -s Backup root(a)localhost.localdomain) root 19672 0.0 0.0 228476 3136 ? S 12:29 0:00 /bin/sh /etc/cron.weekly/backup.cron root 19673 0.0 0.0 227904 2248 ? S 12:29 0:00 sed 1i\ /etc/cron.weekly/backup.cron:\ root 19683 0.0 0.0 227752 2276 ? S 12:30 0:00 grep -i backup root 19684 0.0 0.0 238028 5352 ? S 12:30 0:00 mail -s Backup root(a)localhost.localdomain and at thz end backup ended at Sat Jun 22 02:55:58 PM CEST 2024 /dev/sda10, /dev/sdb8 and /dev/sdc6 OK and the second one root 29787 0.0 0.0 228476 3260 ? S 14:55 0:00 /bin/sh /etc/cron.weekly/backup.cron.saved root 29788 0.0 0.0 227904 2176 ? S 14:55 0:00 sed 1i\ /etc/cron.weekly/backup.cron.saved:\ root 29798 0.0 0.0 227752 2208 ? S 14:55 0:00 grep -i backup root 29799 0.0 0.0 238028 5428 ? S 14:55 0:00 mail -s Backup root(a)localhost.localdomain Here is the /etc/crontab SHELL=/bin/bash PATH=/sbin:/bin:/usr/sbin:/usr/bin MAILTO=root # For details see man 4 crontabs # Example of job definition: # .---------------- minute (0 - 59) # | .------------- hour (0 - 23) # | | .---------- day of month (1 - 31) # | | | .------- month (1 - 12) OR jan,feb,mar,apr ... # | | | | .---- day of week (0 - 6) (Sunday=0 or 7) OR sun,mon,tue,wed,thu,fri,sat # | | | | | # * * * * * user-name command to be executed #22 23 * * * root run-parts /etc/cron.daily #30 12 * * 3,6 root run-parts /etc/cron.weekly 30 12 * * 6 root run-parts /etc/cron.weekly # cron.weekly is actually run by anacron #*/12 * * * * /home/root/bin/periodic.sh and the /etc/anacrontab # See anacron(8) and anacrontab(5) for details. SHELL=/bin/sh PATH=/sbin:/bin:/usr/sbin:/usr/bin MAILTO=root # the maximal random delay added to the base delay of the jobs RANDOM_DELAY=35 # the jobs will be started during the following hours only START_HOURS_RANGE=3-22 #period in days delay in minutes job-identifier command 1 5 cron.daily nice run-parts /etc/cron.daily #7 25 cron.weekly nice run-parts /etc/cron.weekly @monthly 45 cron.monthly nice run-parts /etc/cron.monthly Is there a conflict between cron and anacron ? This machine is turned on and off usually on a daily basis, but not necessary. Thank for your lights =========================================================================== Patrick DUPRÉ | | email: pdupre(a)gmx.com ===========================================================================

5 6

Touch Screen and WiFi cards
by ToddAndMargo 21 Jun '24

21 Jun '24

Hi All, I customer gave me a laptop he inherited to see what could be done with it. It works really nicely, so I need to send him over recommendations. 1) does these really thin laptops have their wifi cards soldered in or can they be replace? (I can usually replace regular laptop WiFi cards.) I presume Intel's WiFi cards have good Fedora support? 2) does Fedora support touch screens? Many thanks, -T -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Computers are like air conditioners. They malfunction when you open windows ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

4 4