On 11/05/2021 12:52, Robert McBroom via users wrote:
Installed Arch Linux on my Goflex Home NAS. I see it on the router from my ISP. It is
connected through an access point to have a sufficient number of ethernet ports. I can't
ping it using the ipv4 address I see on the router. There are two i
On 5/10/21 8:58 PM, Robert McBroom via users wrote:
On 5/4/21 12:43 AM, Samuel Sieb wrote:
On 2021-05-03 9:33 p.m., Robert McBroom via users wrote:
To happy to soon, Did an update to get current and on reboot and
login the entire system is read only. Looking at directories with
emacs and all p
Installed Arch Linux on my Goflex Home NAS. I see it on the router from
my ISP. It is connected through an access point to have a sufficient
number of ethernet ports. I can't ping it using the ipv4 address I see
on the router. There are two ipv6 addresses shown. One declares a
lifetime of 3600s
On 5/4/21 12:43 AM, Samuel Sieb wrote:
On 2021-05-03 9:33 p.m., Robert McBroom via users wrote:
To happy to soon, Did an update to get current and on reboot and
login the entire system is read only. Looking at directories with
emacs and all permissions look fine but any attempt to write fails.
On 2021-05-10 5:05 p.m., Paolo Galtieri wrote:
I recently ran into an issue with files with .ovf extension. The issue
is that VMware Workstation will not import files that end in .ovf. A
file that ends in .ovf shows up as follows of Fedora 34:
file *.ovf returns
XML 1.0 document, ASCII text
I recently ran into an issue with files with .ovf extension. The issue
is that VMware Workstation will not import files that end in .ovf. A
file that ends in .ovf shows up as follows of Fedora 34:
file *.ovf returns
XML 1.0 document, ASCII text
What's interesting is that if you have Virtual
jarmo writes:
Just, when PULSEAUDIO started working somehow,
brilliant idea, change to pipewire in F34...
I'm still trying to analyze the situation. Another reboot did seem to have
concluded with audio working by default.
Rooting around in $HOME I see some promising noises coming out of
Mon, 10 May 2021 09:19:50 -0400
Sam Varshavchik kirjoitti:
> After F34 upgrade the default audio output device is wrong after
> every reboot.
>
> After every reboot it is, apparently, a "PCM2902 Audio Codec Analog
> Stereo", which goes anywhere.
>
> It's not much of hassle to go into Volume Con
After F34 upgrade the default audio output device is wrong after every
reboot.
After every reboot it is, apparently, a "PCM2902 Audio Codec Analog Stereo",
which goes anywhere.
It's not much of hassle to go into Volume Control and click on "Built-in
Audio Analog Stereo", but it's rather a
yes this method. However, I always have to add --allowerasing.
___
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/projec
10 matches
Mail list logo
