On Wed, Oct 23, 2024 at 2:01 PM Kamil Paral wrote:
> On Wed, Oct 23, 2024 at 1:24 PM Kamil Paral wrote:
>
>> Oh, fun. I can reproduce this when I'm using user-session virtual
>> machines (gnome-boxes or virt-manager). It doesn't happen when
>> system-sessions VMs are used.
>> That's a bummer. I'
On Wed, Oct 23, 2024 at 1:24 PM Kamil Paral wrote:
> Oh, fun. I can reproduce this when I'm using user-session virtual machines
> (gnome-boxes or virt-manager). It doesn't happen when system-sessions VMs
> are used.
> That's a bummer. I'll create a bug report and post it here.
>
Here we go:
http
On Wed, Oct 23, 2024 at 12:52 PM Alessio wrote:
> Indeed, issuing "sudo systemctl thaw user.slice" via ssh, the GDM login
> screen reappears.
>
Oh, fun. I can reproduce this when I'm using user-session virtual machines
(gnome-boxes or virt-manager). It doesn't happen when system-sessions VMs
are
It looks like the issue is here in "frozen" user session
$ systemctl status session-4.scope
● session-4.scope - Session 4 of User alessio
Loaded: loaded (/run/systemd/transient/session-4.scope; transient)
Transient: yes
Active: active (running) (frozen-by-parent) since Wed 2024-10-23
Hi friends.
Fedora 41 fully updated.
If I have running VMs (using virt-manager or GNOME Boxes) and I suspend
the system, when I wake it up, the screen stays black and the keyboard
is unresponsive (the caps lock led doesn't turn on/off).
BTW the system looks somewhat alive, indeed I can ping it and
