Hi.
On Sat, 11 Jun 2022 15:48:56 -0400 Jeffrey Ross via users wrote:
> /usr/share/crypto-policies/DEFAULT/opensshserver.txt and add ^ssh-rsa at
> the beginning of the PubkeyAcceptedAlgorithms list will allow users to
> login again, however anytime there is an update to the crypto stuff on
> t
On Sat, 2022-06-11 at 15:48 -0400, Jeffrey Ross via users wrote:
> I keep running into an issue with PuTTy users logging into the
> system (Fedora 35), I found that if I edit:
>
> /usr/share/crypto-policies/DEFAULT/opensshserver.txt and add ^ssh-rsa
> at the beginning of the PubkeyAcceptedAlgorit
On Sat, 2022-06-11 at 19:50 -0600, home user wrote:
> Multiple times over 4-5 hours I
> - powered down and powered up the modem;
> - reset the modem;
> - disconnected and reconnected the yellow ethernet cable; and
> - rebooted the work station, trying both OSs.
> So I switched back and forth multip
On 6/11/22 8:56 PM, Joe Zeff wrote:
On 6/11/22 19:50, home user wrote:
Multiple times over 4-5 hours I
- powered down and powered up the modem;
- reset the modem;
- disconnected and reconnected the yellow ethernet cable; and
- rebooted the work station, trying both OSs.
So I switched back and fo
On 6/11/22 19:50, home user wrote:
Multiple times over 4-5 hours I
- powered down and powered up the modem;
- reset the modem;
- disconnected and reconnected the yellow ethernet cable; and
- rebooted the work station, trying both OSs.
So I switched back and forth multiple times. There also were
home user writes:
Another question...
It took multiple minutes for dnf, Firefox, and Thunderbird to decide to give
up on connecting. What is a reasonable time that should be allowed, and how
do I permanently customize those for that time?
Connection timeouts are determined by some combina
On 6/11/22 5:40 PM, Samuel Sieb wrote:
On 6/11/22 16:26, home user wrote:
On 6/11/22 2:44 PM, Samuel Sieb wrote:
Having now rebooted into Fedora, I see that everything now appears and
behaves normally.
When I started this thread, being able to connect to websites in
windows-7 but not being
On 6/11/22 16:26, home user wrote:
On 6/11/22 2:44 PM, Samuel Sieb wrote:
Having now rebooted into Fedora, I see that everything now appears and
behaves normally.
When I started this thread, being able to connect to websites in
windows-7 but not being able to connect to the same URLs in Fedo
On 6/11/22 2:44 PM, Samuel Sieb wrote:
Having now rebooted into Fedora, I see that everything now appears and
behaves normally.
When I started this thread, being able to connect to websites in
windows-7 but not being able to connect to the same URLs in Fedora had
me suspecting trouble in Fed
On 6/11/22 11:42, home user wrote:
- In the corner of the display (gnome), there's usually a little
fork-like symbol next to the little symbol that I click to log off or
shutdown. That symbol is not showing.
I assume you're referring to the wired network symbol. If you go into
the setting,
I keep running into an issue with PuTTy users logging into the system
(Fedora 35), I found that if I edit:
/usr/share/crypto-policies/DEFAULT/opensshserver.txt and add ^ssh-rsa at
the beginning of the PubkeyAcceptedAlgorithms list will allow users to
login again, however anytime there is an up
(sent from Thunderbird running in windows-7)
From Fedora-35, I cannot reach the internet at all.
- Firefox and Thunderbird each take several minutes trying before
notifying me of time-out.
- If, as root, I do "dnf info firefox", it takes several minutes trying
before giving me curl errors.
> On 10 Jun 2022, at 23:09, Gordon Messmer wrote:
>
> On 6/10/22 11:29, Barry Scott wrote:
>> What logs do I need to collect?
>
>
> I'd start by looking at "journalctl -b0"
>
> You might be able to find clevis information in there.
Already did that and there is nothing that stands out.
>
If you take a look at plocate.spec [1], you'll see on line 101 that
this file is declared with %ghost. So the file itself is not shipped
with the plocate package, but if you create it, then the package will
assume ownership of it; i.e., if you remove the plocate package, then
/etc/updatedb.conf wi
The plocate rpm appears to include an /etc/updatedb.conf file
(shows up in rpm -q --list plocate).
But my system doesn't have an /etc/updatedb.conf file, and judging
from the backups, it has never had one on fedora36.
Anyone on fedora 36 that does have an /etc/updatedb.conf file?
15 matches
Mail list logo
