Finally found this bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2254986
Create empty file /etc/default/wsdd and it is happy (sheesh!)
On Sun, Feb 11, 2024 at 7:11 PM Tom Horsley wrote:
>
> What on earth does that mean? Is there a contest to see who can
> generate the least useful error
On Feb 11, 2024, at 12:38, Robert McBroom via users wrote:
On 2/11/24 10:30, Jonathan Billings
wrote:
On Feb 10, 2024, at 19:05, Robert McBroom via users wrote:
I typically boot in mode 3 to a terminal. Fedora f39 going to lxde as the desktop. Today with
What on earth does that mean? Is there a contest to see who can
generate the least useful error message? :-).
My best guess is that it is trying to use ipv6 and I have ipv6
turned off? Or is it trying to use a bridge I have that isn't
normally connected to anything?
--
On 2/11/24 10:30, Jonathan Billings wrote:
On Feb 10, 2024, at 19:05, Robert McBroom via
users wrote:
I typically boot in mode 3 to a terminal. Fedora f39 going to lxde as the
desktop. Today with a cold boot and entering the user login the following
message showed
--
System is going dow
On 2/11/24 05:19, Barry wrote:
On 11 Feb 2024, at 04:07, Robert McBroom via users
wrote:
There was plenty of time after the update. Are you saying that dnf update is
not done when it is finished?
Some installs trigger building kernel modules, which can only happen after dnf
is finished.
On Feb 10, 2024, at 19:05, Robert McBroom via users
wrote:
>
> I typically boot in mode 3 to a terminal. Fedora f39 going to lxde as the
> desktop. Today with a cold boot and entering the user login the following
> message showed
>
> --
>
> System is going down. Unprivileged users are not
On Sat, Feb 10, 2024 at 8:05 PM Robert McBroom via users <
users@lists.fedoraproject.org> wrote:
> I typically boot in mode 3 to a terminal. Fedora f39 going to lxde as
> the desktop. Today with a cold boot and entering the user login the
> following message showed
>
> --
>
> System is going down
> On 11 Feb 2024, at 04:07, Robert McBroom via users
> wrote:
>
> There was plenty of time after the update. Are you saying that dnf update is
> not done when it is finished?
Some installs trigger building kernel modules, which can only happen after dnf
is finished.
For example the rpmfusio
