On 3/15/23 09:49, home user wrote:
On 3/15/23 10:16 AM, home user wrote:
"xv" does not handle "webp" images. I do not see "xv" in the Redhat
bugzilla menu of components. Where do I submit a bug against xv?
(Luna)
For compilation help, bug reports, or other technical matters, contact
xvt...@
On 3/12/23 08:57, lejeczek via users wrote:
Sometimes - way way too often - I cannot suspend my Fedora.
Whether with power button or GUI or command line, system would not go to
sleep.
I have an external Dell p2418d always connected but whether that monitor
is connected or not, seems to make no
I use an old F30 version that's the newest one that works on all my BIOS
machines, namely memtest86+-5.01-25.fc30.x86_64.rpm. It's in the archive at
https://dl.fedoraproject.org/pub/archive/fedora/linux/releases/30/Everything/x86_64/os/Packages/m/memtest86+-5.01-25.fc30.x86_64.rpm
. Adjust the p
On 3/15/23 9:56 AM, home user wrote:
Good morning,
When booting up, I select the grub menu entry
"Fedora Memtest memtest86+-5.31".
The screen blanks, the cursor goes to the upper left corner of the display, and
blinks.
That's it.
I waited about 10 minutes. Cursor still blinking in the same pla
On 3/16/23 09:22, Jeffrey Walton wrote:
That's interesting. Is the presence (or absence) of /sys/firmware/uefi
related to 'UEFI is supported' from dmidecode?
$ sudo dmidecode | grep -i -E 'uefi|bios'
Getting SMBIOS data from sysfs.
SMBIOS 3.1.0 present.
BIOS Information
On 3/16/23 04:09, Tim via users wrote:
In /etc/named.conf you'd specify a zone file for the records. I'm
showing an example from something else on my BIND server:
Good advice, you can just create a zone in your named.conf.
Then in that zone you have two options:
1. just declare that forward
On Thu, Mar 16, 2023 at 11:48 AM Tim via users
wrote:
> On Thu, 2023-03-16 at 09:17 -0600, home user wrote:
> > How do I determine the answer to Richard's first question?
> [...]
> "The easiest way to find out if you are running UEFI or BIOS is to look
> for a folder /sys/firmware/efi. The folder
On 3/16/23 9:43 AM, Michael D. Setzer II wrote:
On 16 Mar 2023 at 9:17, home user wrote:
Does your computer use UEFI to boot? If so, is the image you're using for
memtest86+ correct?
How do I determine the answer to Richard's first question? I can't do what
Todd suggested without knowing
On 3/16/23 9:48 AM, Tim via users wrote:
On Thu, 2023-03-16 at 09:17 -0600, home user wrote:
How do I determine the answer to Richard's first question?
https://www.google.com/search?q=did+my+linux+pc+boot+uefi+or+bios
"The easiest way to find out if you are running UEFI or BIOS is to look
for
On 2023-03-15 10:40, Michael D. Setzer II via users wrote:
The Fedora memtest86+-5.31 is broken and they have
been informed of how to get the newer 6.10 version to
work, but have done nothing.
I don't think that's fair to the maintainers. There hasn't been a
memory test application (neither
On Thu, 2023-03-16 at 09:17 -0600, home user wrote:
> How do I determine the answer to Richard's first question?
https://www.google.com/search?q=did+my+linux+pc+boot+uefi+or+bios
"The easiest way to find out if you are running UEFI or BIOS is to look
for a folder /sys/firmware/efi. The folder wil
On 16 Mar 2023 at 9:17, home user wrote:
Date sent: Thu, 16 Mar 2023 09:17:17 -0600
Subject:Re: memtest86+ seems to do nothing.
To: users@lists.fedoraproject.org
From: home user
Send reply to: Community support for Fedora
On Thu, 16 Mar 2023 10:32:27 +0100
Patrick Dupre wrote:
> I get the following SELinux security alert which seems to be difficult
> to fix because of the number of things to do.
There is really only one thing to do, just run the two commands with
the proper selinux context selected as filetype.
On 3/15/23 11:21 AM, Richard Shaw wrote:
On Wed, Mar 15, 2023 at 10:58 AM home user mailto:mattis...@comcast.net>> wrote:
Good morning,
When booting up, I select the grub menu entry
"Fedora Memtest memtest86+-5.31".
The screen blanks, the cursor goes to the upper left corner of
On Wed, 2023-03-15 at 20:41 -0700, ToddAndMargo via users wrote:
> I actually have an /etc/hosts. I was in
> the wrong directory. :'(
>
> After adding tor to my /etc/hosts,
>
> # override OpenDNS's block of tor.bravesoftware.com
> 146.112.61.106 tor.bravesoftware.com
>
>
> host lights up lik
Hello,
I get the following SELinux security alert which seems to be difficult
to fix because of the number of things to do.
Is there a simple thing that I could do?
Thanks
SELinux is preventing systemd from open access on the file
/var/usermin/miniserv.pid.
* Plugin catchall_labels (83.8
ToddAndMargo via users wrote:
>> I actually have an /etc/hosts. I was in the wrong directory. :'(
Joe Zeff:
> Oh, good. If you look at what's in there by default, you'll see how
> much your system depends on it being there.
I was of the impression that the localhost lines were presumed, anyw
17 matches
Mail list logo
