After 2023-12-01 I can not get in to a timed out session

Support
1

After 2023-12-01 I can not get in to a timed out session.
I updated 2023-12-01 and 23-12-10 and the problem persists.
When I work on the computer after boot all is fine. Then when I take a break and let the screen time out and come back to the computer I can log in as usual but instead of my desktop I get a black screen with a mouse pointer that follows my mouse movements normally.
I had linux 6.5 before the update.
currently with the problem I have:
linux 6.6.5-1
xfce 4.18
linux66-nvidia
hardware:
Nvida gtx 960

2

Did you already try kernel 6.1 ?

Welcome to Manjaro! :smiling_face_with_three_hearts:

  1. Please read the information behind this link. It will help you to post necessary information.
  1. Please press the three dots … below your post and then press the :pencil2:
  • If you give us information about your system, we can see what we’re talking about and make better suggestions.
  • You can do this by using inxi in a terminal or in console.
sudo inxi --admin --verbosity=7 --filter --no-host --width
  • Personally identifiable information such as serial numbers and MAC addresses are filtered out by this command
  • Presenting the information in this way allows everyone to be familiar with the format and quickly find the items they need without missing anything.
  1. Copy the output from inxi (including the command) and paste it into your post.
  • To make it more readable, add 3 backticks ``` on an extra line before and after the pasted text.

Have you already :mag: for your problem in the forum ? (Wisdom lies in asking → listening → reading :wink: )

3

I just tried kernel 6.1 and the problem presists.
here is the total infromation abolut my system:

$  sudo inxi --admin --verbosity=7 --filter --no-host --width

System:
  Kernel: 6.6.5-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
    clocksource: tsc available: hpet,acpi_pm
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-6.6-x86_64
    root=UUID=909de77d-4ec3-450b-b418-1d7112d5f352 rw rootflags=subvol=@
    sysrq_always_enabled=1 quiet splash apparmor=1 security=apparmor
    udev.log_priority=3
  Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 info: xfce4-panel wm: xfwm
    v: 4.18.0 dm: LightDM v: 1.32.0 Distro: Manjaro Linux base: Arch Linux
Machine:
  Type: Desktop Mobo: ASUSTeK model: MAXIMUS VIII GENE v: Rev 1.xx
    serial: <filter> UEFI: American Megatrends v: 3007 date: 11/29/2016
Battery:
  Message: No system battery data found. Is one present?
Memory:
  System RAM: total: 32 GiB available: 31.29 GiB used: 2.32 GiB (7.4%)
  Array-1: capacity: 64 GiB slots: 4 modules: 2 EC: None
    max-module-size: 16 GiB note: est.
  Device-1: ChannelA-DIMM1 type: no module installed
  Device-2: ChannelA-DIMM2 type: DDR4 detail: synchronous size: 16 GiB
    speed: 2400 MT/s volts: curr: 1.2 min: 1.2 max: 1.2 width (bits): data: 64
    total: 64 manufacturer: CRUCIAL part-no: BLS16G4D240FSE.16FAD
    serial: <filter>
  Device-3: ChannelB-DIMM1 type: no module installed
  Device-4: ChannelB-DIMM2 type: DDR4 detail: synchronous size: 16 GiB
    speed: 2400 MT/s volts: curr: 1.2 min: 1.2 max: 1.2 width (bits): data: 64
    total: 64 manufacturer: CRUCIAL part-no: BLS16G4D240FSE.16FAD
    serial: <filter>
CPU:
  Info: model: Intel Core i5-6600K socket: LGA1151 bits: 64 type: MCP
    arch: Skylake-S gen: core 6 level: v3 note: check built: 2015
    process: Intel 14nm family: 6 model-id: 0x5E (94) stepping: 3
    microcode: 0xF0
  Topology: cpus: 1x cores: 4 smt: <unsupported> cache: L1: 256 KiB
    desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB L3: 6 MiB
    desc: 1x6 MiB
  Speed (MHz): avg: 800 min/max: 800/3900 base/boost: 3500/8300 scaling:
    driver: intel_pstate governor: powersave volts: 1.1 V ext-clock: 100 MHz
    cores: 1: 800 2: 800 3: 800 4: 800 bogomips: 28009
  Flags: 3dnowprefetch abm acpi adx aes aperfmperf apic arat
    arch_capabilities arch_perfmon art avx avx2 bmi1 bmi2 bts clflush
    clflushopt cmov constant_tsc cpuid cpuid_fault cx16 cx8 de ds_cpl dtes64
    dtherm dts epb ept ept_ad erms est f16c flexpriority flush_l1d fma fpu
    fsgsbase fxsr ht hwp hwp_act_window hwp_epp hwp_notify ibpb ibrs ida
    intel_pt invpcid lahf_lm lm mca mce md_clear mmx monitor movbe mpx msr
    mtrr nonstop_tsc nopl nx pae pat pbe pcid pclmulqdq pdcm pdpe1gb pebs pge
    pln pni popcnt pse pse36 pti pts rdrand rdseed rdtscp rep_good sdbg sep
    smap smep ss ssbd sse sse2 sse4_1 sse4_2 ssse3 stibp syscall tm tm2
    tpr_shadow tsc tsc_adjust tsc_deadline_timer vme vmx vnmi vpid x2apic
    xgetbv1 xsave xsavec xsaveopt xsaves xtopology xtpr
  Vulnerabilities:
  Type: gather_data_sampling status: Vulnerable: No microcode
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT
    disabled
  Type: mds mitigation: Clear CPU buffers; SMT disabled
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data mitigation: Clear CPU buffers; SMT disabled
  Type: retbleed mitigation: IBRS
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: IBRS, IBPB: conditional, STIBP: disabled, RSB
    filling, PBRSB-eIBRS: Not affected
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort mitigation: TSX disabled
Graphics:
  Device-1: NVIDIA GM206 [GeForce GTX 960] vendor: Gigabyte driver: nvidia
    v: 545.29.06 alternate: nouveau,nvidia_drm non-free: 545.xx+ status: current
    (as of 2023-11; EOL~2026-12-xx) arch: Maxwell code: GMxxx
    process: TSMC 28nm built: 2014-2019 pcie: gen: 1 speed: 2.5 GT/s lanes: 16
    link-max: gen: 3 speed: 8 GT/s bus-ID: 01:00.0 chip-ID: 10de:1401
    class-ID: 0300
  Display: x11 server: X.Org v: 21.1.9 compositor: xfwm v: 4.18.0 driver: X:
    loaded: nvidia gpu: nvidia display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 3840x2160 s-dpi: 96 s-size: 1016x572mm (40.00x22.52")
    s-diag: 1166mm (45.9")
  Monitor-1: Unknown-1 mapped: DP-0 res: 3840x2160 hz: 60 dpi: 111
    size: 878x485mm (34.57x19.09") modes: 1024x768
  API: OpenGL Message: Unable to show GL data. glxinfo is missing.
Audio:
  Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel alternate: snd_soc_avs bus-ID: 00:1f.3
    chip-ID: 8086:a170 class-ID: 0403
  Device-2: NVIDIA GM206 High Definition Audio vendor: Gigabyte
    driver: snd_hda_intel v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 16
    link-max: gen: 3 speed: 8 GT/s bus-ID: 01:00.1 chip-ID: 10de:0fba
    class-ID: 0403
  API: ALSA v: k6.6.5-1-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
  Server-2: JACK v: 1.9.22 status: off tools: N/A
  Server-3: PipeWire v: 1.0.0 status: n/a (root, process) tools: pw-cli
  Server-4: PulseAudio v: 16.1 status: active (root, process)
    with: pulseaudio-alsa type: plugin tools: pacat,pactl,pavucontrol
Network:
  Device-1: Intel Ethernet I219-V vendor: ASUSTeK driver: e1000e v: kernel
    port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15b8 class-ID: 0200
  IF: enp0s31f6 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IP v4: <filter> type: dynamic noprefixroute scope: global
    broadcast: <filter>
  IP v6: <filter> type: noprefixroute scope: link
  WAN IP: <filter>
Bluetooth:
  Message: No bluetooth data found.
Logical:
  Message: No logical block device data found.
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 2.17 TiB used: 281.97 GiB (12.7%)
  ID-1: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD PM871b M.2 2280
    128GB size: 119.24 GiB block-size: physical: 512 B logical: 512 B sata: 3.1
    speed: 6.0 Gb/s tech: SSD serial: <filter> fw-rev: 3D0Q temp: 28 C
    scheme: GPT
  SMART: yes state: enabled health: PASSED on: 86d 2h cycles: 2028
    read: 7.96 TiB written: 4.06 TiB
  ID-2: /dev/sdb maj-min: 8:16 vendor: Samsung model: SSD 870 EVO 2TB
    family: based SSDs size: 1.82 TiB block-size: physical: 512 B logical: 512 B
    sata: 3.3 speed: 6.0 Gb/s tech: SSD serial: <filter> fw-rev: 3B6Q
    temp: 24 C scheme: GPT
  SMART: yes state: enabled health: PASSED on: 36d 17h cycles: 161
    written: 920.23 GiB
  ID-3: /dev/sdc maj-min: 8:32 vendor: Samsung model: SSD 850 PRO 256GB
    family: based SSDs size: 238.47 GiB block-size: physical: 512 B
    logical: 512 B sata: 3.1 speed: 6.0 Gb/s tech: SSD serial: <filter>
    fw-rev: 2B6Q temp: 24 C scheme: GPT
  SMART: yes state: enabled health: PASSED on: 1y 352d 5h cycles: 2617
    written: 12.67 TiB
  Message: No optical or floppy data found.
Partition:
  ID-1: / raw-size: 238.18 GiB size: 238.18 GiB (100.00%)
    used: 56.01 GiB (23.5%) fs: btrfs block-size: 4096 B dev: /dev/sdc3
    maj-min: 8:35 label: sys_btrfs uuid: 909de77d-4ec3-450b-b418-1d7112d5f352
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 892 KiB (0.3%) fs: vfat block-size: 512 B dev: /dev/sdc1 maj-min: 8:33
    label: EFI uuid: E5D2-90FE
  ID-3: /home raw-size: 1.59 TiB size: 1.59 TiB (100.00%)
    used: 225.97 GiB (13.9%) fs: btrfs block-size: 4096 B dev: /dev/sdb1
    maj-min: 8:17 label: home uuid: eb7e4138-2ef7-4cc0-8170-3986cda296b9
  ID-4: /var/cache raw-size: 238.18 GiB size: 238.18 GiB (100.00%)
    used: 56.01 GiB (23.5%) fs: btrfs block-size: 4096 B dev: /dev/sdc3
    maj-min: 8:35 label: sys_btrfs uuid: 909de77d-4ec3-450b-b418-1d7112d5f352
  ID-5: /var/log raw-size: 238.18 GiB size: 238.18 GiB (100.00%)
    used: 56.01 GiB (23.5%) fs: btrfs block-size: 4096 B dev: /dev/sdc3
    maj-min: 8:35 label: sys_btrfs uuid: 909de77d-4ec3-450b-b418-1d7112d5f352
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: yes
    compressor: zstd max-pool: 20%
  ID-1: swap-1 type: partition size: 38 GiB used: 0 KiB (0.0%) priority: -2
    dev: /dev/sda1 maj-min: 8:1 label: N/A
    uuid: 7d141dbd-7701-440e-9dc6-130373069807
Unmounted:
  ID-1: /dev/sda2 maj-min: 8:2 size: 81.24 GiB fs: btrfs label: m.2_btrfs
    uuid: fe32acaf-9af7-4c47-9cbc-386ec0b17edd
  ID-2: /dev/sdb2 maj-min: 8:18 size: 238.47 GiB fs: ext4 label: N/A
    uuid: 276cfaf2-2bda-4298-bf8d-ae575c074b8a
USB:
  Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 16 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Device-1: 1-5:2 info: Corsair HARPOON RGB PRO Gaming Mouse type: mouse,HID
    driver: hid-generic,usbhid interfaces: 2 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s)
    lanes: 1 mode: 1.1 power: 300mA chip-ID: 1b1c:1b75 class-ID: 0300
    serial: <filter>
  Hub-2: 2-0:1 info: super-speed hub ports: 10 rev: 3.0
    speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 chip-ID: 1d6b:0003
    class-ID: 0900
  Hub-3: 3-0:1 info: hi-speed hub with single TT ports: 2 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-4: 4-0:1 info: super-speed hub ports: 2 rev: 3.1
    speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
    class-ID: 0900
Sensors:
  System Temperatures: cpu: 32.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Processes: 253 Uptime: 3m wakeups: 0 Init: systemd v: 254 default: graphical
  tool: systemctl Compilers: gcc: 13.2.1 clang: 16.0.6 Packages: pm: pacman
  pkgs: 1961 libs: 445 tools: pamac,yay pm: flatpak pkgs: 0 Shell: Sudo (sudo)
  v: 1.9.15p2 default: Bash v: 5.2.21 running-in: xfce4-terminal inxi: 3.3.31

I will read through the posts about posting but it’s getting late so I have no time today.
Anyone with more suggestions feel free to chip in.
Good Night all :slight_smile:

4

I am experiencing the same issue, (XFCE, Nvidia GPU (driver 545.29.06), Kernel 6.1.66-2)
Updated to this update from 2023-11-06 (Nvidia 535.129.03-2, Kernel 6.1.60-1)

Inxi output: 
System:
  Kernel: 6.1.66-2-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
    clocksource: tsc available: hpet,acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.1-x86_64
    root=UUID=c97ff330-c0a4-40da-8132-300531094070 rw quiet splash apparmor=1
    security=apparmor udev.log_priority=3
  Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 info: xfce4-panel wm: xfwm
    v: 4.18.0 dm: LightDM v: 1.32.0 Distro: Manjaro Linux base: Arch Linux
CPU:
  Info: 2x 6-core Intel Xeon X5675 [MT MCP SMP] arch: Nehalem speed (MHz):
    avg: 1756 min/max: 1596/3060
Graphics:
  Device-1: NVIDIA GA102GL [RTX A4500] driver: nvidia v: 545.29.06
    alternate: nouveau,nvidia_drm non-free: 545.xx+ status: current (as of
    2023-11; EOL~2026-12-xx) arch: Ampere code: GAxxx process: TSMC n7 (7nm)
    built: 2020-2023 pcie: gen: 1 speed: 2.5 GT/s lanes: 16 link-max: gen: 4
    speed: 16 GT/s bus-ID: 03:00.0 chip-ID: 10de:2232 class-ID: 0300
  Display: x11 server: X.Org v: 21.1.9 compositor: xfwm v: 4.18.0 driver: X:
    loaded: nvidia unloaded: modesetting,nouveau alternate: fbdev,nv,vesa
    gpu: nvidia resolution: 1: 1680x1050~60Hz 2: 1280x1024~60Hz
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 545.29.06
    glx-v: 1.4 direct-render: yes renderer: NVIDIA RTX A4500/PCIe/SSE2
    memory: 18.3 GiB

after the screen locker activates, when logging back in, only a (still moveable) cursor is displayed on a black background.

Some things I found out:

  • Waiting a long, long time has had the desktop reappear one of the times I tested it.
  • It seems there is a grace period to press a key-combination to re-lock the session and return to the lock screen.
  • Logging in as another user still works, but will have the same problem on session locking.

I had a quick look through the output of journalctl,
I can see that shortly after locking the session

Process 1679 (panel-8-whisker) of user 1000 dumped core.

followed ~5 minutes later by

Process 2344 (xfdesktop) of user 1000 dumped core.

Core dumps stack traces copied from journalctl:

panel-8-whisker 
Process 1679 (panel-8-whisker) of user 1000 dumped core.

Stack trace of thread 1679:
#0  0x00007fe139e69f41 g_type_check_instance_is_fundamentally_a (libgobject-2.0.so.0 + 0x3af41)
#1  0x00007fe139e5169e g_object_unref (libgobject-2.0.so.0 + 0x2269e)
#2  0x00007fe139ee8d77 n/a (libwhiskermenu.so + 0x28d77)
#3  0x00007fe139ee45fa n/a (libwhiskermenu.so + 0x245fa)
#4  0x00007fe139e436c0 g_closure_invoke (libgobject-2.0.so.0 + 0x146c0)
#5  0x00007fe139e71a36 n/a (libgobject-2.0.so.0 + 0x42a36)
#6  0x00007fe139e62a42 n/a (libgobject-2.0.so.0 + 0x33a42)
#7  0x00007fe139e62c77 g_signal_emit_valist (libgobject-2.0.so.0 + 0x33c77)
#8  0x00007fe139e62d34 g_signal_emit (libgobject-2.0.so.0 + 0x33d34)
#9  0x00007fe139e97f29 n/a (libxfce4panel-2.0.so.4 + 0x6f29)
#10 0x00007fe139e51900 g_object_run_dispose (libgobject-2.0.so.0 + 0x22900)
#11 0x00007fe13995f1aa n/a (libgtk-3.so.0 + 0x35f1aa)
#12 0x00007fe13970741e n/a (libgtk-3.so.0 + 0x10741e)
#13 0x00007fe139e436c0 g_closure_invoke (libgobject-2.0.so.0 + 0x146c0)
#14 0x00007fe139e72056 n/a (libgobject-2.0.so.0 + 0x43056)
#15 0x00007fe139e62a42 n/a (libgobject-2.0.so.0 + 0x33a42)
#16 0x00007fe139e62c77 g_signal_emit_valist (libgobject-2.0.so.0 + 0x33c77)
#17 0x00007fe139e62d34 g_signal_emit (libgobject-2.0.so.0 + 0x33d34)
#18 0x00007fe13994ed4e n/a (libgtk-3.so.0 + 0x34ed4e)
#19 0x00007fe13995a841 n/a (libgtk-3.so.0 + 0x35a841)
#20 0x00007fe139e51900 g_object_run_dispose (libgobject-2.0.so.0 + 0x22900)
#21 0x000055e6cde00305 main (wrapper-2.0 + 0x3305)
#22 0x00007fe139027cd0 n/a (libc.so.6 + 0x27cd0)
#23 0x00007fe139027d8a __libc_start_main (libc.so.6 + 0x27d8a)
#24 0x000055e6cde004a5 _start (wrapper-2.0 + 0x34a5)

Stack trace of thread 1682:
#0  0x00007fe139102f6f __poll (libc.so.6 + 0x102f6f)
#1  0x00007fe13929a2b6 n/a (libglib-2.0.so.0 + 0xb82b6)
#2  0x00007fe13923cb97 g_main_loop_run (libglib-2.0.so.0 + 0x5ab97)
#3  0x00007fe13944019c n/a (libgio-2.0.so.0 + 0x11219c)
#4  0x00007fe13926da05 n/a (libglib-2.0.so.0 + 0x8ba05)
#5  0x00007fe13908c9eb n/a (libc.so.6 + 0x8c9eb)
#6  0x00007fe1391107cc n/a (libc.so.6 + 0x1107cc)

Stack trace of thread 1680:
#0  0x00007fe13910e73d syscall (libc.so.6 + 0x10e73d)
#1  0x00007fe1392952f7 g_cond_wait (libglib-2.0.so.0 + 0xb32f7)
#2  0x00007fe1392071b4 n/a (libglib-2.0.so.0 + 0x251b4)
#3  0x00007fe13926fa8e n/a (libglib-2.0.so.0 + 0x8da8e)
#4  0x00007fe13926da05 n/a (libglib-2.0.so.0 + 0x8ba05)
#5  0x00007fe13908c9eb n/a (libc.so.6 + 0x8c9eb)
#6  0x00007fe1391107cc n/a (libc.so.6 + 0x1107cc)

Stack trace of thread 1681:
#0  0x00007fe139102f6f __poll (libc.so.6 + 0x102f6f)
#1  0x00007fe13929a2b6 n/a (libglib-2.0.so.0 + 0xb82b6)
#2  0x00007fe13923a162 g_main_context_iteration (libglib-2.0.so.0 + 0x58162)
#3  0x00007fe13923a1b2 n/a (libglib-2.0.so.0 + 0x581b2)
#4  0x00007fe13926da05 n/a (libglib-2.0.so.0 + 0x8ba05)
#5  0x00007fe13908c9eb n/a (libc.so.6 + 0x8c9eb)
#6  0x00007fe1391107cc n/a (libc.so.6 + 0x1107cc)
ELF object binary architecture: AMD x86-64
xfdesktop 
Process 2344 (xfdesktop) of user 1000 dumped core.

Stack trace of thread 2344:

#0  0x00007f6a22d1dea8 g_type_check_instance_is_a (libgobject-2.0.so.0 + 0x3aea8)
#1  0x0000565291ae9bdb n/a (xfdesktop + 0x3cbdb)
#2  0x00007f6a22bf0f69 n/a (libglib-2.0.so.0 + 0x59f69)
#3  0x00007f6a22c4f367 n/a (libglib-2.0.so.0 + 0xb8367)
#4  0x00007f6a22bf1b97 g_main_loop_run (libglib-2.0.so.0 + 0x5ab97)
#5  0x00007f6a233ecf6f gtk_main (libgtk-3.so.0 + 0x1ecf6f)
#6  0x0000565291ade27d n/a (xfdesktop + 0x3127d)
#7  0x0000565291ade524 n/a (xfdesktop + 0x31524)
#8  0x00007f6a22beb97d n/a (libglib-2.0.so.0 + 0x5497d)
#9  0x00007f6a22beffa0 n/a (libglib-2.0.so.0 + 0x58fa0)
#10 0x00007f6a22bf1071 n/a (libglib-2.0.so.0 + 0x5a071)
#11 0x00007f6a22c4f367 n/a (libglib-2.0.so.0 + 0xb8367)
#12 0x00007f6a22bef162 g_main_context_iteration (libglib-2.0.so.0 + 0x58162)
#13 0x00007f6a22e24b66 g_application_run (libgio-2.0.so.0 + 0xdfb66)
#14 0x0000565291ac805f main (xfdesktop + 0x1b05f)
#15 0x00007f6a229dccd0 n/a (libc.so.6 + 0x27cd0)
#16 0x00007f6a229dcd8a __libc_start_main (libc.so.6 + 0x27d8a)
#17 0x0000565291ac80a5 _start (xfdesktop + 0x1b0a5)

Stack trace of thread 3722:
#0  0x00007f6a22ab39cb access (libc.so.6 + 0xfe9cb)
#1  0x00007f6a22e7b94e n/a (libgio-2.0.so.0 + 0x13694e)
#2  0x00007f6a22e7556f n/a (libgio-2.0.so.0 + 0x13056f)
#3  0x00007f6a22dac701 n/a (libgio-2.0.so.0 + 0x67701)
#4  0x00007f6a22df2db8 n/a (libgio-2.0.so.0 + 0xaddb8)
#5  0x00007f6a22c254e3 n/a (libglib-2.0.so.0 + 0x8e4e3)
#6  0x00007f6a22c22a05 n/a (libglib-2.0.so.0 + 0x8ba05)
#7  0x00007f6a22a419eb n/a (libc.so.6 + 0x8c9eb)
#8  0x00007f6a22ac57cc n/a (libc.so.6 + 0x1107cc)

Stack trace of thread 2350:
#0  0x00007f6a22ab7f6f __poll (libc.so.6 + 0x102f6f)
#1  0x00007f6a22c4f2b6 n/a (libglib-2.0.so.0 + 0xb82b6)
#2  0x00007f6a22bf1b97 g_main_loop_run (libglib-2.0.so.0 + 0x5ab97)
#3  0x00007f6a22e5719c n/a (libgio-2.0.so.0 + 0x11219c)
#4  0x00007f6a22c22a05 n/a (libglib-2.0.so.0 + 0x8ba05)
#5  0x00007f6a22a419eb n/a (libc.so.6 + 0x8c9eb)
#6  0x00007f6a22ac57cc n/a (libc.so.6 + 0x1107cc)

Stack trace of thread 2348:
#0  0x00007f6a22ac373d syscall (libc.so.6 + 0x10e73d)
#1  0x00007f6a22c4a2f7 g_cond_wait (libglib-2.0.so.0 + 0xb32f7)
#2  0x00007f6a22bbc1b4 n/a (libglib-2.0.so.0 + 0x251b4)
#3  0x00007f6a22c24a8e n/a (libglib-2.0.so.0 + 0x8da8e)
#4  0x00007f6a22c22a05 n/a (libglib-2.0.so.0 + 0x8ba05)
#5  0x00007f6a22a419eb n/a (libc.so.6 + 0x8c9eb)
#6  0x00007f6a22ac57cc n/a (libc.so.6 + 0x1107cc)

Stack trace of thread 2349:
#0  0x00007f6a22ab7f6f __poll (libc.so.6 + 0x102f6f)
#1  0x00007f6a22c4f2b6 n/a (libglib-2.0.so.0 + 0xb82b6)
#2  0x00007f6a22bef162 g_main_context_iteration (libglib-2.0.so.0 + 0x58162)
#3  0x00007f6a22bef1b2 n/a (libglib-2.0.so.0 + 0x581b2)
#4  0x00007f6a22c22a05 n/a (libglib-2.0.so.0 + 0x8ba05)
#5  0x00007f6a22a419eb n/a (libc.so.6 + 0x8c9eb)
#6  0x00007f6a22ac57cc n/a (libc.so.6 + 0x1107cc)
ELF object binary architecture: AMD x86-64

Is anyone else seeing XFCE-related crashes/core dumps in the system journal?

EDIT:
Some more test results and observations:

  • Issue still persists when switching to Kernels 5.15.142-1 and 6.6.5-3
  • Issue still persists with xfdesktop-devel 4.19.1 (AUR) (switched it back to 4.18 after testing)
  • Switching to a Virtual Console/Terminal is still possible, you can kill xfce4-session from there to avoid rebooting
  • Switching to a logged-in Virtual Console/Terminal also causes the same issue (black screen + cursor) when attempting to go back via Ctrl-Alt-F7
  • tested a fresh install of manjaro manjaro-xfce-23.0.4-231015-linux65.iso in a qemu VM, it is unaffected (and running non-proprietary graphics drivers)

EDIT 2:
I’ve looked at the list of all updated packages between this update and the last not-bugged one, and with all this and Xfce4 black screen with cursor when switching between users, I suspect something might be up with the Nvidia 545 drivers interacting with XFCE, as I see no other thing that could cause those symptoms, and the timing fits with the update from 535.

EDIT 3:
Did some more testing,
and it seems that something with the XFCE window manager, xfwm, causes the black screen problem

since by installing the openbox package/window manager, opening a terminal and

$> openbox --replace

there is no longer a problem on session locking

still, not particularly viable as a solution on its own without a ton of configuration.

Current Solutions:

  • Install and use an other desktop environment / window manager (see here for more details)
  • Disabling automatic screen locking (settings > power manager > security tab > Automatically lock the session: never); you also might want to disable any keyboard shortcut to lock session to avoid accidental session locking
5

I also have the same issue. Very good troubleshooting, disable screen locking works :slightly_smiling_face:.
Have you reported the bug to xfwm so the problem can be fixed? (I am not allowed to link to it)

6

Not yet. I may do that, if time permits
I’ll probably look through the bug reports and merge requests of the XFCE projects in the coming days first, to see if someone already encountered something similar.

I also have a few extra tests to do to make sure if it is only xfwm, if it is a complicated interaction between other programs and it, or if maybe it is something in the libraries xfwm uses.

If anyone has already filed a bug report for that bug or has done some more troubleshooting on their side, please do leave a post here :slight_smile:

7

What’s also interesting is that if you use XFCE there is no way to not make it not lock. As I explained in my other post I disabled (using each apps settings and preventing them from auto-start) LightLocker, screen savers (all of them, just in case), XFCE power manager, XFCE session locking, xflock4 … even tried various setting using xset dpms… Sooner or later some code tries to lock the screen and triggers the bug.

If would be really nice to be able to select a different nvidia driver - like we can do with linux kernels… by installing a specific version.