Re: Wrestling with UEFI
On Tue, 2023-08-22 at 17:15 +0100, Patrick O'Callaghan wrote: > AFAIK this is at least partly controlled by GDM, so using a different > login manager such as SDDM is likely to fix it without having to edit > anything. I use SDDM and have never had to put up with this. Wondering... Does having GDM installed, but not being used, also cause this problem? -- uname -rsvp Linux 3.10.0-1160.95.1.el7.x86_64 #1 SMP Mon Jul 24 13:59:37 UTC 2023 x86_64 Boilerplate: All unexpected mail to my mailbox is automatically deleted. I will only get to see the messages that are posted to the mailing list. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: GNU Emacs 29.1 in the repos?
On Mon, Aug 21, 2023 at 7:35 PM Jonathan Billings wrote: > On Aug 21, 2023, at 11:44, Gábor Papp wrote: > > Good morning/afternoon/evening/night! > > I was just wondering when will Emacs 29.1 be available in the Fedora 38 > repos? > > > Looks like it has only been built for Fedora 39 at this point. > > https://bodhi.fedoraproject.org/updates/FEDORA-2023-07e6003761 > > https://download.copr.fedorainfracloud.org/results/bhavin192/emacs-pretest/ ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: docker firewall?
On 8/20/23 10:05, Oleg Cherkasov wrote: On 19.08.2023 16:48, Alex wrote: Hi, I'm a long-time Linux sysadmin but haven't done much with docker and containers or firewalls beyond iptables. I have inherited a fedora38 system where another admin has installed python3-docker, but port 8080 is now exposed to the Internet. I have a basic iptables firewall that I set up some time ago (when the system was probably fedora35), but iptables also shows some docker rules: # iptables -nvL|grep ^Chain|grep DOCKER Chain DOCKER (2 references) Chain DOCKER-ISOLATION-STAGE-1 (1 references) Chain DOCKER-ISOLATION-STAGE-2 (2 references) Where do these chains/policies come from? Is it also an iptables firewall or is it using ufw? Why wouldn't it use firewall-cmd? Isn't that the default desktop firewall app now for fedora? The docker doesn't play well with ufw or firewalld, in my experience. It customizes rules directly, which makes it difficult to control with publicly available networks. The simplest way to do firewall customization is to turn off firewall customization in the docker and do it manually. Firstly, update docker.service to include the following option (--iptables=false): /etc/systemd/system/docker.service.d/override.conf [Service] ExecStart= ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock --iptables=false Restart the Docker service and verify the existence of the Docker zone if using firewalld: docker (active) target: ACCEPT icmp-block-inversion: no interfaces: br-custom1 br-custom2 docker0 sources: services: ports: protocols: masquerade: no forward-ports: source-ports: icmp-blocks: rich rules: Add the available docker bridge interfaces (br-custom* and docker0) to the docker zone. Check if the target zone is ACCEPT instead of default. I hope that helps. You could always switch to using Podman, which will not open the port on the host by default. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Last kernel update leads to emergency mode
On 8/22/23 03:37, Paul Smith wrote: On Tue, Aug 22, 2023 at 4:31 AM Samuel Sieb wrote: Are other also experience that with the new kernel: 6.4.10-200.fc38.x86_64 I have already file a bug but no answer: https://bugzilla.redhat.com/show_bug.cgi?id=2232838 You didn't really provide any info that would help. Can you get any journal output or the sos file? Is there any indication of what is going wrong? Thanks, Samuel and Geoffrey. I have meanwhile uploaded the log file corresponding to journalctl -xb That's not the log from the failed boot. It looks like you booted to the previous kernel and ran that from the running system. The log won't be written to disk, so you have to look at it right then and possibly save it to some external storage if possible. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Wrestling with UEFI
On Tue, 2023-08-22 at 06:46 -0700, stan via users wrote: > On Tue, 22 Aug 2023 08:11:02 -0400 > Robert McBroom via users wrote: > > > looked in system settings, screensaver settings, powermanager > > settings and did not find the magic button. Using LXDE. > > I had this happen to me at one point because the XFCE screensaver > started automatically, even if XFCE wasn't running. I have all the > desktops installed so I can use their programs even if I'm not > running > them directly, and boot them if I choose. So, if you have any other > desktop installed, or even other desktop applications, this might be > the case for you as well. It seems that Gnome has a default to go to > sleep automatically after 15 minutes of idle time, regardless of any > other settings. The thread Tim pointed to has tips on how to turn > that off. AFAIK this is at least partly controlled by GDM, so using a different login manager such as SDDM is likely to fix it without having to edit anything. I use SDDM and have never had to put up with this. poc ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Last kernel update leads to emergency mode
On Tue, Aug 22, 2023 at 2:26 PM Ranjan Maitra wrote: > > > > > Are other also experience that with the new kernel: > > > > > > > > 6.4.10-200.fc38.x86_64 > > > > > > > > I have already file a bug but no answer: > > > > > > > > https://bugzilla.redhat.com/show_bug.cgi?id=2232838 > > > > > > I didn't have any problems, but I updated to 6.4.11 this morning so > > > maybe try that. > > > > Thanks, Patrick: My bad: the problematic kernel is: > > > > kernel-6.4.11-200.fc38.x86_64 > > Can you boot into the older kernel? Yes, Ranjan, I can boot into an older kernel. Thanks! Paul ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Automount using LDAP on Fedora Core 5
Hi. On Tue, 22 Aug 2023 15:44:22 +0200 Souji Thenria wrote: > I compared the status output from both versions and noticed that the map > type displayed by the 4.1.4 version is "yp" (NIS). It seems that it does > not recognise that these maps are distributed via LDAP. I hope you have only in /etc/nsswitch.conf: automount: ldap > I looked at both init.d scripts and noticed that in version 4.1.4 the > maptype cannot be set to LDAP. There is this if-else statement that > determines the map type and it always defaults to "yp". There does not > even seem to be an option for the LDAP type: Except if "$maptype" = "$map", but I think it's better to patch this script as follows, instead of understanding it fully (what is for example the output of autofs-ldap-auto-master), in order to gain time to upgrade (or far far better re-install those 2 machines). Replace: - elif [ -f "/etc/$map" ]; then maptype=file map=`echo /etc/$map | sed 's^//^/^g'` else maptype=yp if [ "$UNDERSCORETODOT" = "1" ] ; then map=`basename $map | sed -e s/^auto_/auto./` else map=`basename $map | sed 's^//^/^g'` fi fi - by: - else maptype=ldap if [ "$UNDERSCORETODOT" = "1" ] ; then map=`basename $map | sed -e s/^auto_/auto./` else map=`basename $map | sed 's^//^/^g'` fi fi - I think it should work since this maptype=yp is the only occurrence of yp in this script (ignoring the output of autofs-ldap-auto-master). -- francis ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Wrestling with UEFI
On Tue, 22 Aug 2023 08:11:02 -0400 Robert McBroom via users wrote: > looked in system settings, screensaver settings, powermanager > settings and did not find the magic button. Using LXDE. I had this happen to me at one point because the XFCE screensaver started automatically, even if XFCE wasn't running. I have all the desktops installed so I can use their programs even if I'm not running them directly, and boot them if I choose. So, if you have any other desktop installed, or even other desktop applications, this might be the case for you as well. It seems that Gnome has a default to go to sleep automatically after 15 minutes of idle time, regardless of any other settings. The thread Tim pointed to has tips on how to turn that off. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Automount using LDAP on Fedora Core 5
On 19.08.2023 17:49, francis.montag...@inria.fr wrote: I looked at the 4.1.4-33 version of /etc/init.d/autofs. It uses autofs-ldap-auto-master to get the master map, and then calls an automount process with each map found. This list of automount commands is shown by "/etc/init.d/autofs status". Can you compare this status on the two boxes (4.1.3 and 4.1.4) ? Since you don't see requests for those maps in the LDAP server logs, those commands are perhaps wrongly generated. You can also add verbose and debug options in /etc/sysconfig/autofs: DAEMONOPTIONS="--timeout=60 --verbose --debug" Hi Francis, Thanks for your reply and sorry it took me a while to reply. I compared the status output from both versions and noticed that the map type displayed by the 4.1.4 version is "yp" (NIS). It seems that it does not recognise that these maps are distributed via LDAP. I looked at both init.d scripts and noticed that in version 4.1.4 the maptype cannot be set to LDAP. There is this if-else statement that determines the map type and it always defaults to "yp". There does not even seem to be an option for the LDAP type: # Handle degenerate map specifiers if [ "$maptype" = "$map" ] ; then if [ "$map" = "hesiod" -o "$map" = "userhome" ] ; then maptype=$map map= elif [ "$map" = "multi" ] ; then maptype=$map map= # elif echo "$map" | grep -q '^!'; then # map=`echo "$map"| sed -e 's/^!//g'` elif `echo $map | grep -q "^/"` && [ -x "$map" ]; then maptype=program elif [ -x "/etc/$map" ]; then maptype=program map=`echo /etc/$map | sed 's^//^/^g'` elif `echo $map | grep -q "^/"` && [ -f "$map" ]; then maptype=file elif [ -f "/etc/$map" ]; then maptype=file map=`echo /etc/$map | sed 's^//^/^g'` else maptype=yp if [ "$UNDERSCORETODOT" = "1" ] ; then map=`basename $map | sed -e s/^auto_/auto./` else map=`basename $map | sed 's^//^/^g'` fi fi fi map=`echo $map | cut -f2- -d:` For comparison, version 4.1.3 uses "/usr/lib/autofs/nsswitch" to determine the location of the maps, but this binary does not exist in the newer version. -- Souji Thenria ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Last kernel update leads to emergency mode
On Mon Aug21'23 05:13:34PM, Paul Smith wrote: > From: Paul Smith > Date: Mon, 21 Aug 2023 17:13:34 +0100 > To: Community support for Fedora users > Reply-To: Community support for Fedora users > Subject: Re: Last kernel update leads to emergency mode > > On Mon, Aug 21, 2023 at 5:10 PM Patrick O'Callaghan > wrote: > > > > > Are other also experience that with the new kernel: > > > > > > 6.4.10-200.fc38.x86_64 > > > > > > I have already file a bug but no answer: > > > > > > https://bugzilla.redhat.com/show_bug.cgi?id=2232838 > > > > I didn't have any problems, but I updated to 6.4.11 this morning so > > maybe try that. > > Thanks, Patrick: My bad: the problematic kernel is: > > kernel-6.4.11-200.fc38.x86_64 > Can you boot into the older kernel? Ranjan ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Wrestling with UEFI
On 8/22/23 01:04, Samuel Sieb wrote: On 8/21/23 21:06, Robert McBroom via users wrote: Added a Fedora 37 and Fedora 38 installations on separate drives to a Windows system. Default boot is the Windows 10 system. Using the boot menu gets me to grub which can boot the system of my choice. When the Fedora 38 install goes to sleep it doesn't come back to Fedora but boots to the Windows install. Keeps going to sleep in a frustratingly short time. The screensaver time setting don't seem to interact with the powermanagement settings. Never doesn't seem to be never. It's not the screensaver time, it's the sleep time setting. But also, if it's booting again, then the sleep isn't even working. What will make fedora stay in its own neighborhood? If the default boot is windows, then any time it reboots, it will go there. You either need to disable the sleeping or figure out why it's not working properly. looked in system settings, screensaver settings, powermanager settings and did not find the magic button. Using LXDE. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Last kernel update leads to emergency mode
On Tue, Aug 22, 2023 at 4:31 AM Samuel Sieb wrote: > > > Are other also experience that with the new kernel: > > > > 6.4.10-200.fc38.x86_64 > > > > I have already file a bug but no answer: > > > > https://bugzilla.redhat.com/show_bug.cgi?id=2232838 > > You didn't really provide any info that would help. Can you get any > journal output or the sos file? Is there any indication of what is > going wrong? Thanks, Samuel and Geoffrey. I have meanwhile uploaded the log file corresponding to journalctl -xb at: https://bugzilla.redhat.com/attachment.cgi?id=1984571 Paul ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Wrestling with UEFI
On Tue, 2023-08-22 at 00:06 -0400, Robert McBroom via users wrote: > Added a Fedora 37 and Fedora 38 installations on separate drives to a > Windows system. Default boot is the Windows 10 system. Using the boot > menu gets me to grub which can boot the system of my choice. > When the Fedora 38 install goes to sleep it doesn't come back to > Fedora but boots to the Windows install. I don't know if it holds true, still. But the old answer to that quandary was to: (a) Make sure that GRUB controls your entire boot process (you see it first, no matter what, and you boot to Windows through it). (b) Use the "save default" GRUB options so that GRUB records which option you chose to boot from, and that choice will become the default choice the next time you boot up. (c) You set GRUB options for where your hibernate file is, so it knows where to un-hibernate from. > Keeps going to sleep in a frustratingly short time. The screensaver > time setting don't seem to interact with the powermanagement > settings. Never doesn't seem to be never. That's being debated right now, and over the last week or so. The regime has decided that to save power (and the planet) a PC must shut down if it's been left idle for 15 minutes. All unproductive workers must be sacked, and their PCs put to sleep. *Your* power management settings only apply to the PC while you're logged into it. If someone else logs in, they need to set their power management options, separately. And if no-one is logged in, the login manager's settings (GDM on Gnome) are in charge, and there's some gconf (or is it dconf) voodoo to set it's settings - which I can't remember, but it's on this list somewhere, and here's a link that Todd provided about it earlier: https://discussion.fedoraproject.org/t/gnome-suspends-after-15-minutes-of-user-inactivity-even-on-ac-power/79801 Otherwise search the last week's messages for "suspending" in the subject. -- uname -rsvp Linux 3.10.0-1160.95.1.el7.x86_64 #1 SMP Mon Jul 24 13:59:37 UTC 2023 x86_64 Boilerplate: All unexpected mail to my mailbox is automatically deleted. I will only get to see the messages that are posted to the mailing list. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
