Hi everyone. I have a small problem.
I don’t know if it was or after the last update, I just noticed.
When my computer locks, I enter my password, the computer unlocks, and I see my desktop with all my open apps, and then bam, it locks again.
May be an issue with suspend/resume actions
Is there a way to fix this?
Thanks.
@Simon63r Hi you might need to look through the logs to see what is occurring. I don’t use it here with Nvidia, but tested on Intel UHD and Intel ARC and it’s fine (super+L).
nvidia-powerd[1005]: ERROR! JPAC is not created/already destroyed, ignoring request.
févr. 25 13:12:26 suspend[132728]: nvidia-suspend.service
févr. 25 13:12:26 geeko logger[132728]: <13>Feb 25 13:12:26 suspend: nvidia-suspend.service
févr. 25 13:12:29 geeko systemd[1]: nvidia-suspend.service: Deactivated successfully.
févr. 25 13:12:29 geeko systemd[1]: nvidia-suspend.service: Consumed 1.639s CPU time.
févr. 25 14:19:58 geeko nvidia-powerd[1005]: ERROR! JPAC is not created/already destroyed, ignoring request.
févr. 25 14:19:58 geeko suspend[133032]: nvidia-resume.service
févr. 25 14:19:58 geeko logger[133032]: <13>Feb 25 14:19:58 suspend: nvidia-resume.service
févr. 25 14:19:58 geeko systemd[1]: nvidia-resume.service: Deactivated successfully.
févr. 25 14:20:09 geeko nvidia-powerd[1005]: ERROR! JPAC is not created/already destroyed, ignoring request.
févr. 25 14:20:25 geeko suspend[133587]: nvidia-suspend.service
févr. 25 14:20:25 geeko logger[133587]: <13>Feb 25 14:20:25 suspend: nvidia-suspend.service
févr. 25 14:20:27 geeko systemd[1]: nvidia-suspend.service: Deactivated successfully.
févr. 25 14:20:27 geeko systemd[1]: nvidia-suspend.service: Consumed 1.645s CPU time.
févr. 25 14:20:37 geeko nvidia-powerd[1005]: ERROR! JPAC is not created/already destroyed, ignoring request.
févr. 25 14:20:37 geeko suspend[133691]: nvidia-resume.service
févr. 25 14:20:37 geeko logger[133691]: <13>Feb 25 14:20:37 suspend: nvidia-resume.service
févr. 25 14:20:37 geeko systemd[1]: nvidia-resume.service: Deactivated successfully.
févr. 25 14:20:48 geeko nvidia-powerd[1005]: ERROR! JPAC is not created/already destroyed, ignoring request.
févr. 25 14:28:41 geeko nvidia-powerd[1005]: ERROR! JPAC is not created/already destroyed, ignoring request.
févr. 25 14:28:52 geeko nvidia-powerd[1005]: ERROR! JPAC is not created/already destroyed, ignoring request.
févr. 25 14:55:03 geeko nvidia-powerd[1005]: ERROR! JPAC is not created/already destroyed, ignoring request.
févr. 25 14:55:13 geeko nvidia-powerd[1005]: ERROR! JPAC is not created/already destroyed, ignoring request.
févr. 25 14:57:27 geeko nvidia-powerd[1005]: ERROR! JPAC is not created/already destroyed, ignoring request.
févr. 25 14:57:38 geeko nvidia-powerd[1005]: ERROR! JPAC is not created/already destroyed, ignoring request.
Here is a similar topic.
So is this a dual gpu setup? If you stop the service and test, what happens, systemctl stop nvidia-powerd.service.
It’s disable here…
févr. 25 15:45:40 geeko systemd[1]: Stopping nvidia-powerd service...
févr. 25 15:45:40 geeko nvidia-powerd[1005]: Quit successfully
févr. 25 15:45:40 geeko systemd[1]: nvidia-powerd.service: Deactivated successfully.
févr. 25 15:45:40 geeko systemd[1]: Stopped nvidia-powerd service.
févr. 25 15:45:40 geeko systemd[1]: nvidia-powerd.service: Consumed 4min 30.124s CPU time.
Yes intel and nvidia
I’ll be watching.
Can you show the output from inxi -GSaz and are you running the open driver?
inxi -GSaz
System:
Kernel: 6.19.3-1-default arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
clocksource: tsc avail: acpi_pm
parameters: BOOT_IMAGE=/boot/vmlinuz-6.19.3-1-default
root=UUID=a8b1eea8-b21a-4b84-8ed6-248d7dbfcbef splash=silent
resume=/dev/disk/by-uuid/6355ecd8-38e8-4536-9504-c74569f6e5fe quiet
security=selinux selinux=1 loglevel=3 mitigations=auto
rd.driver.blacklist=nouveau
Desktop: GNOME v: 49.4 tk: GTK v: 3.24.51 wm: gnome-shell
tools: gsd-screensaver-proxy dm: GDM v: 49.2 Distro: openSUSE Tumbleweed
20260223
Graphics:
Device-1: Intel Alder Lake-P GT2 [Iris Xe Graphics] vendor: Hewlett-Packard
driver: i915 v: kernel alternate: xe arch: Xe process: Intel 10nm
built: 2021-22+ ports: active: eDP-1 empty: DP-1,DP-2 bus-ID: 00:02.0
chip-ID: 8086:46a6 class-ID: 0300
Device-2: NVIDIA GA106M [GeForce RTX 3060 Mobile / Max-Q]
vendor: Hewlett-Packard driver: nvidia v: 580.126.18
alternate: nouveau,nvidia_drm non-free: 550-580.xx+ status: current (as
of 2025-11; EOL~2026-12-xx) arch: Ampere code: GAxxx
process: TSMC n7 (7nm) built: 2020-2023 pcie: gen: 4 speed: 16 GT/s
lanes: 8 link-max: lanes: 16 ports: active: none empty: DP-3,HDMI-A-1
bus-ID: 01:00.0 chip-ID: 10de:2520 class-ID: 0300
Device-3: Luxvisions Innotech HP Wide Vision HD Camera driver: uvcvideo
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-6:3
chip-ID: 30c9:0065 class-ID: 0e02 serial: <filter>
Display: wayland server: Xwayland v: 24.1.9 compositor: gnome-shell
driver: gpu: i915 display-ID: 0
Monitor-1: eDP-1 model: BOE Display 0x09bf built: 2020 res: 2560x1440
dpi: 170 gamma: 1.2 size: 382x215mm (15.04x8.46") diag: 438mm (17.3")
ratio: 16:9 modes: 2560x1440
API: OpenGL v: 4.6 vendor: intel mesa v: 26.0.0 glx-v: 1.4 es-v: 3.2
direct-render: yes renderer: Mesa Intel Iris Xe Graphics (ADL GT2)
device-ID: 8086:46a6 memory: 14.93 GiB unified: yes display-ID: :0.0
API: EGL Message: EGL data requires eglinfo. Check --recommends.
Info: Tools: api: glxinfo gpu: nvidia-settings,nvidia-smi
x11: xprop,xrandr
nvidia-powerd is enabled by default here, but not supported by SBIOS (?) and so exited; nvidia-suspend and nvidia-resume work as expected (on dual graphics Intel+Nvidia).
Disabling nvidia-powerd looks worth a shot, indeed.
bruno@LT-B:~> systemctl status nvidia-powerd
○ nvidia-powerd.service - nvidia-powerd service
Loaded: loaded (/usr/lib/systemd/system/nvidia-powerd.service; enabled; preset: enabled)
Active: inactive (dead) since Wed 2026-02-25 09:24:24 CET; 7h ago
Duration: 32ms
Invocation: 09631fd57a644deba786bc0a0f45e5d5
Process: 1389 ExecStart=/usr/bin/nvidia-powerd (code=exited, status=0/SUCCESS)
Main PID: 1389 (code=exited, status=0/SUCCESS)
CPU: 19ms
feb 25 09:24:24 LT-B systemd[1]: Started nvidia-powerd service.
feb 25 09:24:24 LT-B nvidia-powerd[1389]: nvidia-powerd version:2.0 (build 1)
feb 25 09:24:24 LT-B nvidia-powerd[1389]: DBus Connection is established
feb 25 09:24:24 LT-B nvidia-powerd[1389]: ERROR! SBIOS support not found for NVPCF GET_SUPPORTED function, exiting !!
feb 25 09:24:24 LT-B nvidia-powerd[1389]: ERROR! Error in getting the NvPCF static configuration
feb 25 09:24:24 LT-B nvidia-powerd[1389]: Quit successfully
feb 25 09:24:24 LT-B systemd[1]: nvidia-powerd.service: Deactivated successfully.
bruno@LT-B:~>
As I understand it, this is a bug in Nvidia and systemd.
Hi All.
So, this bug seems to have been fixed today in Fedora 43.
Can anyone tell me when I can expect a fix for this?
This error is really annoying.
Merci.
I’ve asked the GNOME folks about it, I’m busy today else I’d look at it. Normally one should check openSUSE bug reports.
@Simon63r GNOME 50 is almost out, that gsd version is already in staging, so it will be out in few weeks, so no backporting will be done.
Thank you. Then I’ll wait.