Bug 55856

Summary:

xfce4 not returning properly after suspension, black screen

Product:

Sisyphus

Reporter:

Δημητριος <Phenomii>

Component:

xfce4-session

Assignee:

Mikhail Efremov <sem>

Status:

NEW ---

QA Contact:

qa-sisyphus

Severity:

major

Priority:

CC:

andy, cas, mozhaevame, novopoltsevdv, oddity, sem

Version:

unstable

Hardware:

x86_64

OS:

Linux

Attachments:

Description	Flags
journalctl -b после перехода в suspend	none

Description

Δημητριος 2025-09-03 19:08:44 MSK

The SL P11 distribution normally goes into suspension but you don't come back properly , in fact you come back with a black screen ,sometimes it only shows the mouse cursor .. 

I give you some results.
##########
journalctl -xe | grep -i power
Σεπ 03 17:00:42 user-PC cpufreq-simple[2287]: cpupower set operation was not performed on them
Σεπ 03 17:00:53 user-PC kernel: usb usb1: root hub lost power or was reset
Σεπ 03 17:00:53 user-PC kernel: usb usb2: root hub lost power or was reset
Σεπ 03 17:02:13 user-PC pkexec[2879]: hp: Executing command [USER=root] [TTY=unknown] [CWD=/home/hp] [COMMAND=/usr/sbin/xfpm-power-backlight-helper --set-brightness-switch 0]
############
journalctl -xe | grep -i acpi
Σεπ 03 17:00:53 user-PC kernel: ACPI: EC: interrupt blocked
Σεπ 03 17:00:53 user-PC kernel: ACPI: PM: Preparing to enter system sleep state S3
Σεπ 03 17:00:53 user-PC kernel: ACPI: EC: event blocked
Σεπ 03 17:00:53 user-PC kernel: ACPI: EC: EC stopped
Σεπ 03 17:00:53 user-PC kernel: ACPI: PM: Saving platform NVS memory
Σεπ 03 17:00:53 user-PC kernel: ACPI: PM: Low-level resume complete
Σεπ 03 17:00:53 user-PC kernel: ACPI: EC: EC started
Σεπ 03 17:00:53 user-PC kernel: ACPI: PM: Restoring platform NVS memory
Σεπ 03 17:00:53 user-PC kernel: ACPI: PM: Waking up from system sleep state S3
Σεπ 03 17:00:53 user-PC kernel: ACPI: EC: interrupt unblocked
Σεπ 03 17:00:53 user-PC kernel: ACPI: EC: event unblocked
Σεπ 03 17:02:14 user-PC kernel: ACPI BIOS Error (bug): Failure creating named object [\_GPE._E4C.SPRT], AE_ALREADY_EXISTS (20240827/dswload2-326)
Σεπ 03 17:02:14 user-PC kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20240827/psobject-220)
Σεπ 03 17:02:14 user-PC kernel: ACPI Error: Aborting method \_GPE._E4C due to previous error (AE_ALREADY_EXISTS) (20240827/psparse-529)
Σεπ 03 17:02:14 user-PC kernel: ACPI Error: Aborting method \_GPE._E4C due to previous error (AE_ALREADY_EXISTS) (20240827/psparse-529)
Σεπ 03 17:02:14 user-PC kernel: ACPI Error: AE_ALREADY_EXISTS, while evaluating GPE method [_E4C] (20240827/evgpe-511)
###############

cat /var/log/Xorg.0.log | grep -i "EE"
[   125.925] Current Operating System: Linux user-PC 6.12.42-6.12-alt1 #1 SMP PREEMPT_DYNAMIC Tue Aug 26 13:33:43 UTC 2025 x86_64
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[   125.925] (==) No screen section available. Using defaults.
[   125.925] (**) |-->Screen "Default Screen Section" (0)
[   125.926] (==) No monitor specified for screen "Default Screen Section".
[   125.926] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[   125.928] (II) xfree86: Adding drm device (/dev/dri/card1)
[   125.957] (EE) Failed to load module "nouveau" (module does not exist, 0)
[   125.958] (EE) Failed to load module "nv" (module does not exist, 0)
[   125.979] (EE) open /dev/dri/card0: No such file or directory
[   125.980] (II) NVIDIA(0): Creating default Display subsection in Screen section
	"Default Screen Section" for depth/fbbpp 24/32
[   125.980] (**) Option "AllowNVIDIAGpuScreens"
[   126.254] (II) NVIDIA(0): Virtual screen size determined to be 1920 x 1080
[   126.257] (--) NVIDIA(0): DPI set to (139, 144); computed from "UseEdidDpi" X config
[   126.262] (II) NVIDIA(0):     details, please see the "ConnectToAcpid" and
[   127.208] (II) Initializing extension MIT-SCREEN-SAVER
[   127.209] (II) GLX: Another vendor is already registered for screen 0
[   127.209] (II) Initializing extension XFree86-VidModeExtension
[   127.210] (II) Initializing extension XFree86-DGA
[   127.210] (II) Initializing extension XFree86-DRI
[   127.295] (II) This device may have been added with another device file.
[   127.295] (II) config/udev: Adding input device Sleep Button (/dev/input/event3)
[   127.295] (**) Sleep Button: Applying InputClass "evdev keyboard catchall"
[   127.295] (**) Sleep Button: Applying InputClass "system-keyboard"
[   127.295] (**) Sleep Button: Applying InputClass "evdev keyboard catchall"
[   127.295] (**) Sleep Button: Applying InputClass "libinput keyboard catchall"
[   127.295] (**) Sleep Button: Applying InputClass "keyboard"
[   127.295] (II) Using input driver 'evdev' for 'Sleep Button'
[   127.295] (**) Sleep Button: always reports core events
[   127.295] (**) evdev: Sleep Button: Device: "/dev/input/event3"
[   127.295] (--) evdev: Sleep Button: Vendor 0 Product 0x3
[   127.295] (--) evdev: Sleep Button: Found keys
[   127.295] (II) evdev: Sleep Button: Configuring as keyboard
[   127.295] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 8)
[   127.297] (II) This device may have been added with another device file.
[   127.298] (II) This device may have been added with another device file.
[   127.298] (II) This device may have been added with another device file.
[   127.299] (II) This device may have been added with another device file.
[   127.322] (II) This device may have been added with another device file.
[   127.323] (II) config/udev: Adding input device HDA Digital PCBeep (/dev/input/event13)
[   127.323] (II) This device may have been added with another device file.
[   127.323] (II) This device may have been added with another device file.
[   127.324] (II) This device may have been added with another device file.
[   127.346] (II) This device may have been added with another device file.
[   127.390] (EE) libinput: SynPS/2 Synaptics TouchPad: Failed to create a device for /dev/input/mouse2
[   127.390] (EE) PreInit returned 2 for "SynPS/2 Synaptics TouchPad"
[   127.390] (II) This device may have been added with another device file.
[   127.391] (II) This device may have been added with another device file.
[   127.392] (II) This device may have been added with another device file.
################################
sudo dmesg | grep -i nvidia
[sudo] password for hp:
[    0.014690] ACPI: SSDT 0x000000003DEBE000 0021F4 (v01 HP     NVIDIAGF 00001000 INTL 20121018)
[    4.590731] nvidia_modeset: loading out-of-tree module taints kernel.
[    4.590738] nvidia_modeset: module license 'NVIDIA' taints kernel.
[    4.590742] nvidia_modeset: module verification failed: signature and/or required key missing - tainting kernel
[    4.590743] nvidia_modeset: module license taints kernel.
[    4.590817] nvidia_modeset: Unknown symbol nvidia_get_rm_ops (err -2)
[    4.723332] nvidia_modeset: Unknown symbol nvidia_get_rm_ops (err -2)
[   38.626126] input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input15
[   38.626176] input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input16
[   38.626221] input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input17
[   38.626264] input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input18
[   39.004762] nvidia-nvlink: Nvlink Core is being initialized, major device number 240
[   39.024702] nvidia 0000:01:00.0: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=none:owns=none
[   39.251539] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  570.169  Thu Jun 12 20:04:34 UTC 2025
[   39.271751] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms  570.169  Thu Jun 12 19:28:42 UTC 2025
[   39.287594] [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver
[   39.571670] [drm] Initialized nvidia-drm 0.0.0 for 0000:01:00.0 on minor 1
[   39.588007] nvidia 0000:01:00.0: vgaarb: deactivate vga console
[   39.591862] fbcon: nvidia-drmdrmfb (fb0) is primary device
[   39.591867] nvidia 0000:01:00.0: [drm] fb0: nvidia-drmdrmfb frame buffer device
[   52.892173] nvidia_uvm: module uses symbols nvUvmInterfaceDisableAccessCntr from proprietary module nvidia, inheriting taint.
###################

Comment 1

Δημητριος 2025-09-03 19:38:46 MSK

  video 
https://disk.yandex.com/i/s7SSYJCzHrRXoQ

Comment 2

Можаева Марина Евгеньевна 2025-10-06 15:18:09 MSK

Additional information is required. Please provide the output of the following commands
$ inxi -F
$ lsblk
$ cat /etc/os-release
$ rpm -q xfce4

Comment 3

Δημητριος 2025-10-06 18:37:32 MSK

(In reply to Можаева Марина Евгеньевна from comment #2)
> Additional information is required. Please provide the output of the
> following commands
> $ inxi -F
> $ lsblk
> $ cat /etc/os-release
> $ rpm -q xfce4

inxi -F
System:
  Host: user-PC Kernel: 6.12.41-6.12-alt1 arch: x86_64 bits: 64
  Desktop: Xfce v: 4.20.1 Distro: Simply Linux 11.0 (Giuseppe)
Machine:
  Type: Laptop System: HP product: HP ZBook 15 G3 v: N/A
    serial: <superuser required>
  Mobo: HP model: 80D5 v: KBC Version 10.75 serial: <superuser required>
    UEFI: HP v: N81 Ver. 01.62 date: 03/15/2024
Battery:
  ID-1: BAT0 charge: 37.0 Wh (50.7%) condition: 73.0/90.1 Wh (81.0%)
    volts: 10.7 min: 11.4
CPU:
  Info: quad core model: Intel Core i7-6820HQ bits: 64 type: MCP cache:
    L2: 1024 KiB
  Speed (MHz): avg: 800 min/max: 800/2700 cores: 1: 800 2: 800 3: 800 4: 800
Graphics:
  Device-1: NVIDIA GM206GLM [Quadro M2200 Mobile] driver: nvidia v: 570.169
  Device-2: Lite-On HP HD Camera driver: uvcvideo type: USB
  Display: x11 server: X.Org v: 1.21.1.18 driver: X: loaded: nvidia
    unloaded: fbdev,modesetting,vesa gpu: nvidia,nvidia-nvswitch
    resolution: 1920x1080~60Hz
  API: EGL v: 1.5 drivers: nvidia,swrast
    platforms: gbm,x11,surfaceless,device
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 570.169
    renderer: Quadro M2200/PCIe/SSE2
  API: Vulkan v: 1.4.321 drivers: N/A surfaces: N/A
Audio:
  Device-1: Intel 100 Series/C230 Series Family HD Audio driver: snd_hda_intel
  Device-2: NVIDIA GM206 High Definition Audio driver: snd_hda_intel
  API: ALSA v: k6.12.41-6.12-alt1 status: kernel-api
  Server-1: PipeWire v: 1.4.7 status: active
Network:
  Device-1: Intel Ethernet I219-LM driver: e1000e
  IF: enp0s31f6 state: down mac: 48:ba:4e:af:85:5d
  Device-2: Intel Wireless 8260 driver: iwlwifi
  IF: wlp3s0 state: down mac: ce:f7:cf:0c:2f:59
  Device-3: Realtek RTL8153 Gigabit Ethernet Adapter driver: r8152 type: USB
  IF: enp59s0u1 state: up speed: 100 Mbps duplex: full
    mac: 36:cb:98:57:de:6b
Bluetooth:
  Device-1: Intel Bluetooth wireless interface driver: btusb type: USB
  Report: hciconfig ID: hci0 rfk-id: 1 state: down
    bt-service: enabled,running rfk-block: hardware: no software: yes
    address: 28:16:AD:03:5D:17
Drives:
  Local Storage: total: 476.94 GiB used: 27.22 GiB (5.7%)
  ID-1: /dev/nvme0n1 vendor: Samsung model: MZVKW512HMJP-000H1
    size: 476.94 GiB
Partition:
  ID-1: / size: 24.42 GiB used: 13.86 GiB (56.8%) fs: ext4 dev: /dev/dm-1
  ID-2: /home size: 203.25 GiB used: 13.36 GiB (6.6%) fs: ext4
    dev: /dev/dm-2
Swap:
  ID-1: swap-1 type: partition size: 3.98 GiB used: 0 KiB (0.0%)
    dev: /dev/dm-0
Sensors:
  System Temperatures: cpu: 42.0 C pch: 42.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 16 GiB available: 15.54 GiB used: 2.31 GiB (14.9%)
  Processes: 260 Uptime: 7m Shell: Bash inxi: 3.3.34
########################################

$ cat /etc/os-release
NAME="Simply Linux"
VERSION="11.0 (Giuseppe)"
ID=altlinux
VERSION_ID=11.0
PRETTY_NAME="Simply Linux 11.0 (Giuseppe)"
ANSI_COLOR="1;36"
CPE_NAME="cpe:/o:alt:slinux:11.0"
BUILD_ID="Simply Linux 11.0"
HOME_URL="https://www.basealt.ru/simplylinux"
BUG_REPORT_URL="https://bugs.altlinux.org/"
###############################################
$ rpm -q xfce4
package xfce4 is not installed
###############################################

$ lsblk
NAME                                  MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINTS
nvme0n1                               259:0    0 476,9G  0 disk  
├─nvme0n1p1                           259:1    0   100M  0 part  
├─nvme0n1p2                           259:2    0    16M  0 part  
├─nvme0n1p3                           259:3    0 237,4G  0 part  
├─nvme0n1p4                           259:4    0   733M  0 part  
├─nvme0n1p5                           259:5    0   544M  0 part  /boot/efi
├─nvme0n1p6                           259:6    0   996M  0 part  /var/lib/docker
├─nvme0n1p7                           259:7    0     4G  0 part  
│ └─luks-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
│                                     253:0    0     4G  0 crypt [SWAP]
├─nvme0n1p8                           259:8    0    25G  0 part  
│ └─luks-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
│                                     253:1    0    25G  0 crypt /
└─nvme0n1p9                           259:9    0 207,6G  0 part  
  └─luks-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
                                      253:2    0 207,6G  0 crypt /home

*** I have put the symbols with the letter x
##################################################

Comment 4

Новопольцев Дмитрий 2025-10-14 20:16:26 MSK

Created attachment 19778 [details]
journalctl -b после перехода в suspend

Comment 5

Новопольцев Дмитрий 2025-10-14 20:16:39 MSK

xfce4-session-4.20.3-alt1
Alt Education XFCE x86_64 (Актуальный P11)

Воспроизводится на системе с GPU Nvidia, драйвер — «автоматический».
При попытке перехода в ждущий режим в большинстве случаев изображение на tty1 отсутствует либо виден только курсор (в том числе после переключения на tty2 и обратно). Если экран разблокировки всё же появляется, после ввода пароля система часто возвращается в состояние с одним курсором.

При вызове systemctl suspend из tty2 система пытается перейти в ожидание, но почти сразу выходит из него. В логах указано, что systemd-suspend не успевает отработать. Перед этим система жалуется на невозможность suspend wifi адаптера mt7925e.

На системе без дискретного выхода и доп. адаптеров переход в ждущий режим проходит успешно, после возобновления работы проблема не наблюдается.

Не совсем понятно, связанна ли ошибка XFCE с проблемой перехода в режим ожидания или с видеодрайвером. LightDM после выхода из ждущего режима иногда показывает чёрный экран, но продолжает работать — изображение восстанавливается после переключения на tty2 и обратно.

Comment 6

Новопольцев Дмитрий 2025-10-14 20:21:46 MSK

(Ответ для Новопольцев Дмитрий на комментарий #5)
Дополнительно: после очередноо свича между TTY оказалось, что в середине экрана курсор меняетс на вертикальный (в месте поля ввода пароля). После ввода пароля и нажатия enter, судя по всему, прошла авторизация, но экран остался черным с обычным курсором

Comment 7

Δημητριος 2025-10-14 20:29:51 MSK

I must inform you that the suspend function worked in the distribution that p10, however, presenting another error, after some time the laptop's cooling system stopped working .... then I went to restart the laptop to fix it .... This was presented after suspending the function in p10 ....

Comment 8

Новопольцев Дмитрий 2025-10-15 14:43:03 MSK

Воспроизводится в P11 и Sisyphus

Comment 9

Δημητριος 2025-10-15 15:46:35 MSK

https://forum.altlinux.org/index.php?topic=49367.msg400018#msg400018

Comment 10

Andrew Vasilyev 2025-10-15 19:44:55 MSK

  А если уходить в сон через кнопку Power -> Ждущий режим,
  есть такая проблема при пробуждении?

Comment 11

Δημητριος 2025-10-15 21:28:40 MSK

(In reply to Andrew Vasilyev from comment #10)
>   А если уходить в сон через кнопку Power -> Ждущий режим,
>   есть такая проблема при пробуждении?

В XFCE P11 функция приостановки работы ведет себя аналогично и работает некорректно. Однако, для справки, в дистрибутиве XFCE P10 приостановку можно было активировать с помощью соответствующей кнопки в меню Whisker. Тем не менее, после возобновления работы через определённое время система охлаждения устройства останавливалась, что приводило к повышению температуры и термальному троттлингу машины. В таких случаях перезагрузка устройства восстанавливала нормальную работу.


In XFCE P11, the suspend function exhibits the same behavior and does not operate correctly. However, for informational purposes, in the XFCE P10 distribution, suspension could be activated via the corresponding button in the Whisker menu. Nevertheless, resuming after a certain period caused the device's cooling system to stop, resulting in increased temperature and thermal throttling of the machine. In such cases, restarting the device restored normal operation.

Comment 12

Δημητριος 2025-10-15 21:35:08 MSK

o provide more detail: in the XFCE P11 distribution, the suspend function does not operate correctly; the system enters suspend mode but never resumes, regardless of which buttons are used. In the XFCE P10 distribution, suspension worked normally and the system resumed, but various “freezes” were observed, culminating in the cooling system ceasing to operate.


Для более подробного описания: в дистрибутиве XFCE P11 функция приостановки работы работает некорректно; система входит в режим приостановки, но никогда не возобновляется, независимо от используемых кнопок. В дистрибутиве XFCE P10 приостановка работала нормально, и система возобновляла работу, однако наблюдались различные «зависания», кульминацией которых было прекращение работы системы охлаждения.