Re: Tor killed my other browsers; Name or service not known; uninstalling does not help
On 26/06/2021 14:18, ToddAndMargo via users wrote: On 6/25/21 5:39 PM, Eyal Lebedinsky wrote: After a (late May update) I had problems with name resolution and tracked it down to this line on the name server host: hosts: files myhostname resolve [!UNAVAIL=return] dns and this fixed it for me hosts: files myhostname resolve dns YMMV Hmmm What does `[!UNAVAIL=return]` do? It means that if name resolution via systemd-resolved is not unavailable then return the result you have and stop. So, if it is available but let's say returns "nothing/not-found" then that would be the result returned for the query. If one could replicate the failure it would be helpful in debugging. -- Remind me to ignore comments which aren't germane to the thread. ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: Tor killed my other browsers; Name or service not known; uninstalling does not help
On 6/25/21 5:39 PM, Eyal Lebedinsky wrote: After a (late May update) I had problems with name resolution and tracked it down to this line on the name server host: hosts: files myhostname resolve [!UNAVAIL=return] dns and this fixed it for me hosts: files myhostname resolve dns YMMV Hmmm What does `[!UNAVAIL=return]` do? ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: Fedora-34 breaks KDE pager
On 6/25/21 11:42 PM, Jonathan Ryshpan wrote: In versions up to Fedora-34, dragging a window icon in the pager from one desktop to another used to move the related window from that desktop to the other. This no longer works. Has the function been removed or is there some option that needs to be set (or whatever)? Platform: Fedora-34 KDE Plasma: 5.22.2 KDE Framework: 5.83.0 Graphics: Wayland As this looks to be a KDE issue you may have better luck on a KDE 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 on the list, report it: https://pagure.io/fedora-infrastructure
Fedora-34 breaks KDE pager
In versions up to Fedora-34, dragging a window icon in the pager from one desktop to another used to move the related window from that desktop to the other. This no longer works. Has the function been removed or is there some option that needs to be set (or whatever)? Platform: Fedora-34 KDE Plasma: 5.22.2 KDE Framework: 5.83.0 Graphics: Wayland -- Thanks Jonathan Ryshpan The world is so full of a number of things That we should all be as happy as kings. -- Robert Lewis Stevenson ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: Verifying Fedora-34
I wrote: > As an aside, we (the royal we, as in folks in the Fedora > community who maintain the website) should change the > verification step to recommend gpgv rather than the gpg > command. It would require making the fedora.gpg a > de-armored file, but then it the instructions would be > simpler. I made that suggestion in patch form to the websites team: https://pagure.io/fedora-web/websites/pull-request/189 -- Todd signature.asc Description: PGP signature ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: Verifying Fedora-34
Jonathan Ryshpan wrote: > On Fri, 2021-06-25 at 22:25 -0400, Todd Zullinger wrote: >> There's nothing wrong with that output. The warning is >> simply telling you that the Fedora key isn't signed by a key >> you've marked as trusted. ... > > Just as I thought. So... > > How do I mark a key as trusted? One way is to add a local signature to the Fedora keys, assuming you have a gpg key yourself. However, I would simply take the warning for what it is and not sign the Fedora keys. > What precautions are needed to be sure that the key should > actually be trusted? From https://getfedora.org/en/security/, you can view the fingerprints of the currently active keys Fedora uses for signing the CHECKSUM files. To check the fingerprint for the Fedora 34 key, for example: $ gpg --list-key --with-fingerprint 45719A39 pub rsa4096 2020-08-06 [SCE] 8C5B A699 0BDB 26E1 9F2A 1A80 1161 AE69 4571 9A39 uid [ unknown] Fedora (34) It's worth noting that you're effectively trusting the TLS certificate of getfedora.org in this process. And if you're doing that to get the signatures, you can just as well trust it when you download the fedora.gpg file. It's not bad to check the fingerprints, it's just good to be aware of how much (or how little) additional security it gets you. -- Todd signature.asc Description: PGP signature ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: Tor killed my other browsers; Name or service not known; uninstalling does not help
On 26/06/2021 08:39, Eyal Lebedinsky wrote: After a (late May update) I had problems with name resolution and tracked it down to this line on the name server host: hosts: files myhostname resolve [!UNAVAIL=return] dns and this fixed it for me hosts: files myhostname resolve dns Thanks for pointing that out. I did some searches on that and found that other users have also had issues with that after a kernel update. Being Saturday, I didn't do too much to see if a root cause was identified or a fix is pending. :-) -- Remind me to ignore comments which aren't germane to the thread. ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: Verifying Fedora-34
On Fri, 2021-06-25 at 22:25 -0400, Todd Zullinger wrote: > Jonathan Ryshpan wrote: > > While verifying my download of Fedora-34, I encounter this message: > > $ gpg --verify-files *-CHECKSUM > > gpg: Signature made Fri 23 Apr 2021 12:36:44 PM PDT > > gpg: using RSA key > > 8C5BA6990BDB26E19F2A1A801161AE6945719A39 > > gpg: Good signature from "Fedora (34) > > " [unknown] > > gpg: WARNING: This key is not certified with a trusted signature! > > gpg: There is no indication that the signature belongs to > > the owner. > > Primary key fingerprint: 8C5B A699 0BDB 26E1 9F2A 1A80 1161 AE69 > > 4571 9A39 > > I surmise this means that my computer's list of trusted signatures > > needs to be brought up to date (actually it may not even exist). > > How > > can this be done? A link to info would suffice. > > There's nothing wrong with that output. The warning is > simply telling you that the Fedora key isn't signed by a key > you've marked as trusted. > > As an aside, we (the royal we, as in folks in the Fedora > community who maintain the website) should change the > verification step to recommend gpgv rather than the gpg > command. It would require making the fedora.gpg a > de-armored file, but then it the instructions would be > simpler. Just as I thought. So... How do I mark a key as trusted? What precautions are needed to be sure that the key should actually be trusted? -- Thanks - Jonathan Ryshpan Those who have put out the eyes of the people reproach them for their blindness. -- Milton ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: Verifying Fedora-34
Hi, Jonathan Ryshpan wrote: > While verifying my download of Fedora-34, I encounter this message: >$ gpg --verify-files *-CHECKSUM > gpg: Signature made Fri 23 Apr 2021 12:36:44 PM PDT > gpg: using RSA key > 8C5BA6990BDB26E19F2A1A801161AE6945719A39 > gpg: Good signature from "Fedora (34) > " [unknown] > gpg: WARNING: This key is not certified with a trusted signature! > gpg: There is no indication that the signature belongs to the > owner. > Primary key fingerprint: 8C5B A699 0BDB 26E1 9F2A 1A80 1161 AE69 4571 > 9A39 > I surmise this means that my computer's list of trusted signatures > needs to be brought up to date (actually it may not even exist). How > can this be done? A link to info would suffice. There's nothing wrong with that output. The warning is simply telling you that the Fedora key isn't signed by a key you've marked as trusted. As an aside, we (the royal we, as in folks in the Fedora community who maintain the website) should change the verification step to recommend gpgv rather than the gpg command. It would require making the fedora.gpg a de-armored file, but then it the instructions would be simpler. -- Todd signature.asc Description: PGP signature ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: Tor killed my other browsers; Name or service not known; uninstalling does not help
On 26/06/2021 10.31, Ed Greshko wrote: On 26/06/2021 08:24, ToddAndMargo via users wrote: On 6/25/21 5:00 PM, Ed Greshko wrote: I don't know were that snippet comes from. But, the "Not found" may be due to dig using the system's resolver to first get the IP of resolver1.opendns.com. So, I would have used the IP of that instead. I would still check the nsswitch.conf files. After a (late May update) I had problems with name resolution and tracked it down to this line on the name server host: hosts: files myhostname resolve [!UNAVAIL=return] dns and this fixed it for me hosts: files myhostname resolve dns YMMV My computer is functioning perfect under the prior kernel. I am not sure why you want the /etc/nsswitch.conf, but it is anyway. Kernels should not affect it. I try not to discount anything when I have no idea where the problem lies. FC34 VM: $ uname -r 5.11.16-300.fc34.x86_64 So, the nsswitch.conf files are the same. But you've not updated your VM. So, to just state you VM's are working didn't disclose that bit. Since you can take snapshots of VM's. Why not take a snapshot before an upgrade, then upgrade to the latest kernel and see if you can reproduce the error? -- Eyal Lebedinsky (fed...@eyal.emu.id.au) ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: Tor killed my other browsers; Name or service not known; uninstalling does not help
On 26/06/2021 08:24, ToddAndMargo via users wrote: On 6/25/21 5:00 PM, Ed Greshko wrote: I don't know were that snippet comes from. But, the "Not found" may be due to dig using the system's resolver to first get the IP of resolver1.opendns.com. So, I would have used the IP of that instead. I would still check the nsswitch.conf files. My computer is functioning perfect under the prior kernel. I am not sure why you want the /etc/nsswitch.conf, but it is anyway. Kernels should not affect it. I try not to discount anything when I have no idea where the problem lies. FC34 VM: $ uname -r 5.11.16-300.fc34.x86_64 So, the nsswitch.conf files are the same. But you've not updated your VM. So, to just state you VM's are working didn't disclose that bit. Since you can take snapshots of VM's. Why not take a snapshot before an upgrade, then upgrade to the latest kernel and see if you can reproduce the error? -- Remind me to ignore comments which aren't germane to the thread. ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: Tor killed my other browsers; Name or service not known; uninstalling does not help
On 6/25/21 5:00 PM, Ed Greshko wrote:
On 26/06/2021 07:25, ToddAndMargo via users wrote:
On 6/25/21 3:33 PM, Ed Greshko wrote:
On 26/06/2021 06:23, ToddAndMargo via users wrote:
On 6/25/21 2:45 PM, Ed Greshko wrote:
On 26/06/2021 05:33, Tom Horsley wrote:
On Fri, 25 Jun 2021 14:20:30 -0700
ToddAndMargo via users wrote:
Kernel 5.12.12-300 breaks host resolution
https://bugzilla.redhat.com/show_bug.cgi?id=1976371
Very weird that the kernel could break name resolution since that
all works at library level. Maybe some "deprecated" interface
is being used by 99% of the lookup code, and they got rid of
it completely in the new kernel?
What I find equally weird is that in the BZ he states that his qemu
VM's are working just fine.
If the VM's are working and they have been updated to the same
kernel then what would
be the difference? A proxy setting perhaps?
More funny! The VM's are using my caching name server
ON MY HOST
Sure, that's pretty much the default if your VM's are using DHCP.
The one thing to recall is, and this is from memory, is that "host"
and "dig" don't make use of the
system's resolver library. They query dns servers directly. So,
another thing to check is if the
/etc/nsswitch.conf on the VM's are the same as the host.
Dig did not work either.
function GetPublicIP () {
local WIP=$(dig +short myip.opendns.com @resolver1.opendns.com)
# echo "WIP = <$WIP>" > "/dev/tty"
if [[ "$WIP" == *"not found"* || "$WIP" == *"no servers could be
reached"* ]]; then
WIP="Not Found"
fi
echo $WIP
}
___
I don't know were that snippet comes from. But, the "Not found" may be
due to dig using the system's
resolver to first get the IP of resolver1.opendns.com. So, I would have
used the IP of that instead.
I would still check the nsswitch.conf files.
My computer is functioning perfect under the prior kernel.
I am not sure why you want the /etc/nsswitch.conf, but
it is anyway. Kernels should not affect it.
Host:
passwd: sss files systemd
shadow: files sss
group: sss files systemd
hosts: files myhostname mdns4_minimal [NOTFOUND=return] resolve
[!UNAVAIL=return] dns
bootparams: nisplus [NOTFOUND=return] files
ethers: files
netmasks: files
networks: files
protocols: files
rpc:files
services: files sss
netgroup: nisplus sss
publickey: nisplus
automount: files nisplus
aliases:files nisplus
FC34 VM:
$ uname -r
5.11.16-300.fc34.x86_64
passwd: sss files systemd
shadow: files sss
group: sss files systemd
hosts: files myhostname mdns4_minimal [NOTFOUND=return] resolve
[!UNAVAIL=return] dns
bootparams: nisplus [NOTFOUND=return] files
ethers: files
netmasks: files
networks: files
protocols: files
rpc:files
services: files sss
netgroup: nisplus sss
publickey: nisplus
automount: files nisplus
aliases:files nisplus
___
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 on the list, report it:
https://pagure.io/fedora-infrastructure
Re: Tor killed my other browsers; Name or service not known; uninstalling does not help
On 26/06/2021 07:25, ToddAndMargo via users wrote:
On 6/25/21 3:33 PM, Ed Greshko wrote:
On 26/06/2021 06:23, ToddAndMargo via users wrote:
On 6/25/21 2:45 PM, Ed Greshko wrote:
On 26/06/2021 05:33, Tom Horsley wrote:
On Fri, 25 Jun 2021 14:20:30 -0700
ToddAndMargo via users wrote:
Kernel 5.12.12-300 breaks host resolution
https://bugzilla.redhat.com/show_bug.cgi?id=1976371
Very weird that the kernel could break name resolution since that
all works at library level. Maybe some "deprecated" interface
is being used by 99% of the lookup code, and they got rid of
it completely in the new kernel?
What I find equally weird is that in the BZ he states that his qemu VM's are
working just fine.
If the VM's are working and they have been updated to the same kernel then what
would
be the difference? A proxy setting perhaps?
More funny! The VM's are using my caching name server
ON MY HOST
Sure, that's pretty much the default if your VM's are using DHCP.
The one thing to recall is, and this is from memory, is that "host" and "dig"
don't make use of the
system's resolver library. They query dns servers directly. So, another thing
to check is if the
/etc/nsswitch.conf on the VM's are the same as the host.
Dig did not work either.
function GetPublicIP () {
local WIP=$(dig +short myip.opendns.com @resolver1.opendns.com)
# echo "WIP = <$WIP>" > "/dev/tty"
if [[ "$WIP" == *"not found"* || "$WIP" == *"no servers could be reached"*
]]; then
WIP="Not Found"
fi
echo $WIP
}
___
I don't know were that snippet comes from. But, the "Not found" may be due to
dig using the system's
resolver to first get the IP of resolver1.opendns.com. So, I would have used
the IP of that instead.
I would still check the nsswitch.conf files.
--
Remind me to ignore comments which aren't germane to the thread.
___
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 on the list, report it:
https://pagure.io/fedora-infrastructure
Re: Tor killed my other browsers; Name or service not known; uninstalling does not help
On 6/25/21 3:33 PM, Ed Greshko wrote:
On 26/06/2021 06:23, ToddAndMargo via users wrote:
On 6/25/21 2:45 PM, Ed Greshko wrote:
On 26/06/2021 05:33, Tom Horsley wrote:
On Fri, 25 Jun 2021 14:20:30 -0700
ToddAndMargo via users wrote:
Kernel 5.12.12-300 breaks host resolution
https://bugzilla.redhat.com/show_bug.cgi?id=1976371
Very weird that the kernel could break name resolution since that
all works at library level. Maybe some "deprecated" interface
is being used by 99% of the lookup code, and they got rid of
it completely in the new kernel?
What I find equally weird is that in the BZ he states that his qemu
VM's are working just fine.
If the VM's are working and they have been updated to the same kernel
then what would
be the difference? A proxy setting perhaps?
More funny! The VM's are using my caching name server
ON MY HOST
Sure, that's pretty much the default if your VM's are using DHCP.
The one thing to recall is, and this is from memory, is that "host" and
"dig" don't make use of the
system's resolver library. They query dns servers directly. So,
another thing to check is if the
/etc/nsswitch.conf on the VM's are the same as the host.
Dig did not work either.
function GetPublicIP () {
local WIP=$(dig +short myip.opendns.com @resolver1.opendns.com)
# echo "WIP = <$WIP>" > "/dev/tty"
if [[ "$WIP" == *"not found"* || "$WIP" == *"no servers could be
reached"* ]]; then
WIP="Not Found"
fi
echo $WIP
}
___
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 on the list, report it:
https://pagure.io/fedora-infrastructure
Re: Learning ipv6 quirks
On 6/25/21 4:02 PM, Ed Greshko wrote: On 24/06/2021 01:58, Gordon Messmer wrote: On 6/22/21 11:54 PM, Ed Greshko wrote: [root@meimei ~]# nmap -sS -6 -p 2049 2001:b030:112f:2::53 Starting Nmap 7.80 ( https://nmap.org ) at 2021-06-23 14:47 CST Nmap scan report for 2001:b030:112f:2::53 Host is up (0.00018s latency). PORT STATE SERVICE 2049/tcp closed nfs Means the firewall is not blocking the port but no service is listening on that port That's not entirely accurate. If the firewall action is REJECT rather than DROP, you'll see the same output from nmap. "closed" can mean either that the port is not open, or that the firewall is blocking access with a REJECT action. OK, good to know, thanks. I don't think I've encountered that which may explain my ignorance. It's very rare. In almost all cases, DROP is the default. So the "closed" result can be assumed to mean what you said it means. ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: Learning ipv6 quirks
On 24/06/2021 01:58, Gordon Messmer wrote: On 6/22/21 11:54 PM, Ed Greshko wrote: [root@meimei ~]# nmap -sS -6 -p 2049 2001:b030:112f:2::53 Starting Nmap 7.80 ( https://nmap.org ) at 2021-06-23 14:47 CST Nmap scan report for 2001:b030:112f:2::53 Host is up (0.00018s latency). PORT STATE SERVICE 2049/tcp closed nfs Means the firewall is not blocking the port but no service is listening on that port That's not entirely accurate. If the firewall action is REJECT rather than DROP, you'll see the same output from nmap. "closed" can mean either that the port is not open, or that the firewall is blocking access with a REJECT action. OK, good to know, thanks. I don't think I've encountered that which may explain my ignorance. And nmap isn't necessary to establish this, since the logs already provided included a "connection refused" response to the IPv6 mount attempt. Sure. But it couldn't hurt. :-) -- Remind me to ignore comments which aren't germane to the thread. ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: Tor killed my other browsers; Name or service not known; uninstalling does not help
On 26/06/2021 06:23, ToddAndMargo via users wrote: On 6/25/21 2:45 PM, Ed Greshko wrote: On 26/06/2021 05:33, Tom Horsley wrote: On Fri, 25 Jun 2021 14:20:30 -0700 ToddAndMargo via users wrote: Kernel 5.12.12-300 breaks host resolution https://bugzilla.redhat.com/show_bug.cgi?id=1976371 Very weird that the kernel could break name resolution since that all works at library level. Maybe some "deprecated" interface is being used by 99% of the lookup code, and they got rid of it completely in the new kernel? What I find equally weird is that in the BZ he states that his qemu VM's are working just fine. If the VM's are working and they have been updated to the same kernel then what would be the difference? A proxy setting perhaps? More funny! The VM's are using my caching name server ON MY HOST Sure, that's pretty much the default if your VM's are using DHCP. The one thing to recall is, and this is from memory, is that "host" and "dig" don't make use of the system's resolver library. They query dns servers directly. So, another thing to check is if the /etc/nsswitch.conf on the VM's are the same as the host. -- Remind me to ignore comments which aren't germane to the thread. ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: Tor killed my other browsers; Name or service not known; uninstalling does not help
On 6/25/21 2:45 PM, Ed Greshko wrote: On 26/06/2021 05:33, Tom Horsley wrote: On Fri, 25 Jun 2021 14:20:30 -0700 ToddAndMargo via users wrote: Kernel 5.12.12-300 breaks host resolution https://bugzilla.redhat.com/show_bug.cgi?id=1976371 Very weird that the kernel could break name resolution since that all works at library level. Maybe some "deprecated" interface is being used by 99% of the lookup code, and they got rid of it completely in the new kernel? What I find equally weird is that in the BZ he states that his qemu VM's are working just fine. If the VM's are working and they have been updated to the same kernel then what would be the difference? A proxy setting perhaps? More funny! The VM's are using my caching name server ON MY HOST ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: Tor killed my other browsers; Name or service not known; uninstalling does not help
On 26/06/2021 05:33, Tom Horsley wrote: On Fri, 25 Jun 2021 14:20:30 -0700 ToddAndMargo via users wrote: Kernel 5.12.12-300 breaks host resolution https://bugzilla.redhat.com/show_bug.cgi?id=1976371 Very weird that the kernel could break name resolution since that all works at library level. Maybe some "deprecated" interface is being used by 99% of the lookup code, and they got rid of it completely in the new kernel? What I find equally weird is that in the BZ he states that his qemu VM's are working just fine. If the VM's are working and they have been updated to the same kernel then what would be the difference? A proxy setting perhaps? -- Remind me to ignore comments which aren't germane to the thread. ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: Tor killed my other browsers; Name or service not known; uninstalling does not help
On Fri, 25 Jun 2021 14:20:30 -0700 ToddAndMargo via users wrote: > Kernel 5.12.12-300 breaks host resolution > https://bugzilla.redhat.com/show_bug.cgi?id=1976371 Very weird that the kernel could break name resolution since that all works at library level. Maybe some "deprecated" interface is being used by 99% of the lookup code, and they got rid of it completely in the new kernel? ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: Tor killed my other browsers; Name or service not known; uninstalling does not help
On 6/25/21 2:07 PM, ToddAndMargo via users wrote: On 6/25/21 1:50 PM, Gabriel Ramirez wrote: On 6/25/21 3:20 PM, toddandmargo via users wrote: `host ` worked. $ host gbis.com gbis.com has address 207.228.37.200 gbis.com mail is handled by 0 mx.greatbasin.net. `ping host-name` did not $ ping gbis.com ping: gbis.com: Name or service not known hi, I don't use tor nor brave, but try booting with the previous kernel. I updated to kernel 5.12.12 and has the same symptoms, booting with the old kernel fixed the problems regards Hi Gabriel, That did the trick. Tor was falsely accused! Thank you -T I removed 5.12.12-300 and am running on perfectly on 5.12.11-300 I just posted: Kernel 5.12.12-300 breaks host resolution https://bugzilla.redhat.com/show_bug.cgi?id=1976371 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: Tor killed my other browsers; Name or service not known; uninstalling does not help
On 6/25/21 1:50 PM, Gabriel Ramirez wrote: On 6/25/21 3:20 PM, toddandmargo via users wrote: Hi All, Fedora 34 Xfce 4.14 I am in real trouble here. My business is most shutdown over this. My browsers, Thunderbird, and ping won't work. Nothing that used the Internet worked. Well, almost. I can not find anything about this issue on Google or Duck Duck Go. After installing Tor yesterday, all was well. Tor Browser worked well and all my other browsers and eMail continued to work along side it. I was happy. But that was about to change. After booting up this morning, only Tor Browser and Brave in Tor mode worked. ALL my qemu-kvm virtual machines work perfectly (I am writing this from one of them and I despise web mail). `host ` worked. $ host gbis.com gbis.com has address 207.228.37.200 gbis.com mail is handled by 0 mx.greatbasin.net. `ping host-name` did not $ ping gbis.com ping: gbis.com: Name or service not known hi, I don't use tor nor brave, but try booting with the previous kernel. I updated to kernel 5.12.12 and has the same symptoms, booting with the old kernel fixed the problems regards Hi Gabriel, That did the trick. Tor was falsely accused! Thank you -T I removed 5.12.12-300 and am running on perfectly on 5.12.11-300 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: Tor killed my other browsers; Name or service not known; uninstalling does not help
On 6/25/21 3:20 PM, toddandmargo via users wrote: Hi All, Fedora 34 Xfce 4.14 I am in real trouble here. My business is most shutdown over this. My browsers, Thunderbird, and ping won't work. Nothing that used the Internet worked. Well, almost. I can not find anything about this issue on Google or Duck Duck Go. After installing Tor yesterday, all was well. Tor Browser worked well and all my other browsers and eMail continued to work along side it. I was happy. But that was about to change. After booting up this morning, only Tor Browser and Brave in Tor mode worked. ALL my qemu-kvm virtual machines work perfectly (I am writing this from one of them and I despise web mail). `host ` worked. $ host gbis.com gbis.com has address 207.228.37.200 gbis.com mail is handled by 0 mx.greatbasin.net. `ping host-name` did not $ ping gbis.com ping: gbis.com: Name or service not known hi, I don't use tor nor brave, but try booting with the previous kernel. I updated to kernel 5.12.12 and has the same symptoms, booting with the old kernel fixed the problems regards ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
fc34: no power up on reboot after kernel upgrade
FC34 on a headless server. If I upgrade the kernel and reboot, the machine will not power up. I can manually power it up without a problem. Also, no problem rebooting without a kernel upgrade. Any help appreciated. sean ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: RedShift
On Fri, 25 Jun 2021 02:21:07 -0700 Patrick O'Callaghan wrote > On Fri, 2021-06-25 at 16:50 +0930, Tim via users wrote: > > On Thu, 2021-06-24 at 20:19 -0700, ToddAndMargo via users wrote: > > > Hi All, > > > > > > Fedora 34 > > > Xfce 4.14 > > > redshift-1.12-11.fc34.x86_64 > > > redshift-gtk-1.12-11.fc34.x86_64 > > > > > > Hi All, > > > > > > Red Shift is all screwed up again: > > > > > > > > > Unable to connect to GeoClue. Unable to get location from provider: > > > > Supposedly you can manually configure your location. Would that > > suffice? Obviously this would be a nuisance for jetsetters. > > > > Just gleaned from looking at an example configuration file: > > http://jonls.dk/redshift/ > > > > > > > > Personally I haven't bothered with these kinds of things, I tend to > > find they adjust things too extremely. And a daylight blue screen at > > midday indoors is too blue, anyway. I adjust the normal colour > > temperature of screens to not be so cold, at all times. > > I think there's been some cold water thrown recently on the idea that > this kind of tweak has any actual effect on insomnia, but I'm no > expert. > > poc Does not affect my sleeping at all. It does keep my eyes from burning after working a lot of night hours. ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Tor killed my other browsers; Name or service not known; uninstalling does not help
Hi All, Fedora 34 Xfce 4.14 I am in real trouble here. My business is most shutdown over this. My browsers, Thunderbird, and ping won't work. Nothing that used the Internet worked. Well, almost. I can not find anything about this issue on Google or Duck Duck Go. After installing Tor yesterday, all was well. Tor Browser worked well and all my other browsers and eMail continued to work along side it. I was happy. But that was about to change. After booting up this morning, only Tor Browser and Brave in Tor mode worked. ALL my qemu-kvm virtual machines work perfectly (I am writing this from one of them and I despise web mail). `host ` worked. $ host gbis.com gbis.com has address 207.228.37.200 gbis.com mail is handled by 0 mx.greatbasin.net. `ping host-name` did not $ ping gbis.com ping: gbis.com: Name or service not known If I look up the IP address with "host" and used that instead, `ping IP` worked. All my browser also worked with the IP address. "traceroute" only works with IP as well. So I removed Tor: $ rm -rf ./.local/share/torbrowser/tbb/x86_64/tor-browser_en-US # dnf remove tor torbrowser-launcher torsocks $ rm -rf ./.local/share/torbrowser $ rm -rf ./.cache/torbrowser $ rm -rf ./.config/torbrowser # rm -rf /etc/tor Reboot. No change. What the is going on? And how do I recover my machine? Many thanks, -T ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Verifying Fedora-34
While verifying my download of Fedora-34, I encounter this message: $ gpg --verify-files *-CHECKSUM gpg: Signature made Fri 23 Apr 2021 12:36:44 PM PDT gpg: using RSA key 8C5BA6990BDB26E19F2A1A801161AE6945719A39 gpg: Good signature from "Fedora (34) " [unknown] gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: 8C5B A699 0BDB 26E1 9F2A 1A80 1161 AE69 4571 9A39 I surmise this means that my computer's list of trusted signatures needs to be brought up to date (actually it may not even exist). How can this be done? A link to info would suffice. -- Thanks - jon "Never try to teach a pig to sing. It wastes time and annoys the pig." ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
GNOME 40 mouse lag
Has anyone else been seeing some GNOME 40 animation freezes and lags? I have a Dell 9310 XPS (11th Gen i7/16GB of RAM) and with animations enabled the mouse cursor will sometimes freeze and lag. Strangely I have access to a Dell 9300 (10th Gen i7) running FL34 and it's fine. I'm not running TLP on mine and I've wiped it to make sure I didn't have some weird old config in place. The mouse will just quit responding and suddenly "jump" to catch up at times, it even does this when the machine is not under load. The 9300 has a 4K screen and the 9310 has a 1200p screen so if anything I think the 9310 should be more lag-free with the faster CPU/GPU and less pixels to push around. I don't think it's a hardware problem since it's fine in GNOME 3.38 when I tried Debian and FL33 on here. I've been running Linux on this machine exclusively. I thought about leaving it on Debian but I'd like to use Fedora due to PipeWire and the better BT audio codec support. I know there are some forth coming performance enhancements for the GNOME 40 series too. Just wondering if anyone else has similar hardware and has seen similar quirks. Thanks! Leander -- --- Leander Hutton lean...@one-button.org www.one-button.org ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: RedShift
On 6/25/21 5:19 AM, ToddAndMargo via users wrote: Hi All, Fedora 34 Xfce 4.14 redshift-1.12-11.fc34.x86_64 redshift-gtk-1.12-11.fc34.x86_64 Hi All, Red Shift is all screwed up again: Unable to connect to GeoClue. Unable to get location from provider: https://github.com/jonls/redshift/issues/318#issuecomment-865667340 is back in full force. Is there an alternatives to Red Shift? Gnome integrated this in its own settings as a "Night Light" couple of years back and I am using that to satisfaction. But I assume it will not solve your issues on xfce ... https://www.addictivetips.com/ubuntu-linux-tips/gnome-night-light-mode/ Regards, -- Jakub Jelen Crypto Team, Security Engineering Red Hat, Inc. ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: Learning ipv6 quirks
On 25/06/2021 11:51, Robert McBroom via users wrote: mount.nfs: requested NFS version or transport protocol is not supported Is this your server? https://documents.westerndigital.com/content/dam/doc-library/en_gb/assets/public/wd/product/nas/my_cloud/ex2_ultra/user-manual-my-cloud-expert-series-ex2-ultra.pdf I couldn't find any "advanced" settings for NFS. Is there a /etc/nfs.conf on the device? If so, post that too. -- Remind me to ignore comments which aren't germane to the thread. ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: RedShift
On Fri, 2021-06-25 at 10:21 +0100, Patrick O'Callaghan wrote: > I think there's been some cold water thrown recently on the idea that > this kind of tweak has any actual effect on insomnia, but I'm no > expert. I place no faith in that kind of thing helping insomnia, at all. But taking out the extreme blue can be easier on the eyes, in general. For me, at least, blue is the hardest colour for my eyes to focus on, so I get less chromatic aberrations when it's reduced. But I don't like making things look abnormally amber. I work in video production, and I still find most monitors are way too blue. The monitors look nothing like the thing in front of the camera, even when lit with daylight. -- uname -rsvp Linux 3.10.0-1160.31.1.el7.x86_64 #1 SMP Thu Jun 10 13:32:12 UTC 2021 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: RedShift
On Fri, 2021-06-25 at 16:50 +0930, Tim via users wrote: > On Thu, 2021-06-24 at 20:19 -0700, ToddAndMargo via users wrote: > > Hi All, > > > > Fedora 34 > > Xfce 4.14 > > redshift-1.12-11.fc34.x86_64 > > redshift-gtk-1.12-11.fc34.x86_64 > > > > Hi All, > > > > Red Shift is all screwed up again: > > > > > > Unable to connect to GeoClue. Unable to get location from provider: > > Supposedly you can manually configure your location. Would that > suffice? Obviously this would be a nuisance for jetsetters. > > Just gleaned from looking at an example configuration file: > http://jonls.dk/redshift/ > > > > Personally I haven't bothered with these kinds of things, I tend to > find they adjust things too extremely. And a daylight blue screen at > midday indoors is too blue, anyway. I adjust the normal colour > temperature of screens to not be so cold, at all times. I think there's been some cold water thrown recently on the idea that this kind of tweak has any actual effect on insomnia, but I'm no expert. 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: Learning ipv6 quirks
On 25/06/2021 11:51, Robert McBroom via users wrote: tcp6 0 0 :::111 :::*LISTEN @RobertPC ~]# mount -v -t nfs -o vers=3,proto=tcp6 [2600:1702:4860:9dd0::2d]:/mnt/HD/HD_a2/mcstuffy /mnt/mcstuffy mount.nfs: timeout set for Thu Jun 24 23:30:20 2021 Created symlink /run/systemd/system/remote-fs.target.wants/rpc-statd.service → /usr/lib/systemd/system/rpc-statd.service. mount.nfs: trying text-based options 'vers=3,proto=tcp6,addr=2600:1702:4860:9dd0::2d' mount.nfs: prog 13, trying vers=3, prot=6 mount.nfs: portmap query failed: RPC: Program not registered mount.nfs: trying text-based options 'vers=3,proto=tcp6,addr=2600:1702:4860:9dd0::2d' mount.nfs: prog 13, trying vers=3, prot=6 mount.nfs: portmap query failed: RPC: Program not registered mount.nfs: trying text-based options 'vers=3,proto=tcp6,addr=2600:1702:4860:9dd0::2d' mount.nfs: prog 13, trying vers=3, prot=6 mount.nfs: portmap query failed: RPC: Program not registered mount.nfs: requested NFS version or transport protocol is not supported This tells me the problem is a configuration or limitation on the NFS Server side. The output of the netstat command showed that port 111 has a listen. That is the first contact your client makes with the server. The server then tells your client what ports to contact to complete the request. You can see this when I connect to NFS server via IPv6 after the mount process tells me to use mount.nfs: trying 2001:b030:112f:2::53 prog 15 vers 3 prot TCP port 20048. On the server And I can see that mountd is listening on the port for both tcp6 and tcp. [root@f33k ~]# netstat -tlnp | grep mountd tcp 0 0 0.0.0.0:20048 0.0.0.0:* LISTEN 824/rpc.mountd tcp6 0 0 :::20048 :::* LISTEN 824/rpc.mountd When you client used the port it was told to it fails. A server side issue. You may want to try with mount -v -t nfs -o vers=3,proto=udp6 [2600:1702:4860:9dd0::2d]:/mnt/HD/HD_a2/mcstuffy /mnt/mcstuffy To see if it fails/works. I would also be interested in the output of rpcinfo 2600:1702:4860:9dd0::2d -- Remind me to ignore comments which aren't germane to the thread. ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: bind-chroot not duplicating my forward and reverse tables
On Thu, 2021-06-24 at 21:04 -0700, ToddAndMargo via users wrote: > I am trying to clean up my bind-chroot forward and reverse files. > > The goal is to have bind-chroot do its thing by duplicating > these two files over into > /var/named/chroot/var/named/slaves/ > with the identical inodes like it does with named.root and > named.root.key: Hang on... If you're wanting it to bring things from outside of the chroot into it, what's the point of chrooting? You're breaking the jail by doing that. The old approach was you created all the files in the chroot, where bind-chroot makes use of them. And, you have a link outside of the chroot into it, so that *you* can edit /etc/named.something without thinking about it. But, ultimately, you shouldn't need any files outside of the chroot, at all. And there's probably some advantage in just having one set (less confusing for you, at the very least). -- uname -rsvp Linux 3.10.0-1160.31.1.el7.x86_64 #1 SMP Thu Jun 10 13:32:12 UTC 2021 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: RedShift
On Thu, 2021-06-24 at 20:19 -0700, ToddAndMargo via users wrote: > Hi All, > > Fedora 34 > Xfce 4.14 > redshift-1.12-11.fc34.x86_64 > redshift-gtk-1.12-11.fc34.x86_64 > > Hi All, > > Red Shift is all screwed up again: > > > Unable to connect to GeoClue. Unable to get location from provider: Supposedly you can manually configure your location. Would that suffice? Obviously this would be a nuisance for jetsetters. Just gleaned from looking at an example configuration file: http://jonls.dk/redshift/ Personally I haven't bothered with these kinds of things, I tend to find they adjust things too extremely. And a daylight blue screen at midday indoors is too blue, anyway. I adjust the normal colour temperature of screens to not be so cold, at all times. -- uname -rsvp Linux 3.10.0-1160.31.1.el7.x86_64 #1 SMP Thu Jun 10 13:32:12 UTC 2021 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 on the list, report it: https://pagure.io/fedora-infrastructure
