Bug 1862454 - resume a suspended session crash X
Summary: resume a suspended session crash X
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11
Version: 32
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-07-31 13:33 UTC by Dario Lesca
Modified: 2020-07-31 13:33 UTC (History)
0 users

Fixed In Version:
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug


Attachments (Terms of Use)
journal and Xlog log (51.47 KB, application/gzip)
2020-07-31 13:33 UTC, Dario Lesca
no flags Details

Description Dario Lesca 2020-07-31 13:33:40 UTC
Created attachment 1703102 [details]
journal and Xlog log

Description of problem:

Many time when I resume a suspended section of my notebook, the X session crash and I must reboot or re-login from gdm with my account and reopen all suspended applications.

This is my notebook:

[lesca@dodo ~]$ sudo inxi -F --no-host
System:    Kernel: 5.7.10-201.fc32.x86_64 x86_64 bits: 64 Desktop: Gnome 3.36.4 Distro: Fedora release 32 (Thirty Two) 
Machine:   Type: Laptop System: Dell product: G5 5590 v: N/A serial: G267HX2 
           Mobo: Dell model: 0CNDTP v: A01 serial: /G267HX2/CNPEC0002O00OZ/ UEFI: Dell v: 1.11.1 date: 11/11/2019 
Battery:   ID-1: BAT0 charge: 53.6 Wh condition: 53.6/60.0 Wh (89%) 
CPU:       Topology: 6-Core model: Intel Core i7-9750H bits: 64 type: MT MCP L2 cache: 12.0 MiB 
           Speed: 900 MHz min/max: 800/4500 MHz Core speeds (MHz): 1: 900 2: 894 3: 888 4: 870 5: 841 6: 894 7: 868 8: 897 
           9: 883 10: 885 11: 898 12: 891 
Graphics:  Device-1: Intel UHD Graphics 630 driver: i915 v: kernel 
           Device-2: NVIDIA TU106M [GeForce RTX 2060 Mobile] driver: nvidia v: 440.100 
           Device-3: Realtek Integrated_Webcam_HD type: USB driver: uvcvideo 
           Display: server: Fedora Project X.org 1.20.8 driver: modesetting,nvidia unloaded: fbdev,nouveau,vesa 
           resolution: 1600x900 
           OpenGL: renderer: GeForce RTX 2060/PCIe/SSE2 v: 4.6.0 NVIDIA 440.100 
Audio:     Device-1: Intel Cannon Lake PCH cAVS driver: snd_hda_intel 
           Device-2: NVIDIA TU106 High Definition Audio driver: snd_hda_intel 
           Sound Server: ALSA v: k5.7.10-201.fc32.x86_64 
Network:   Device-1: Intel Wireless-AC 9560 [Jefferson Peak] driver: iwlwifi 
           IF: wlo1 state: up mac: 0c:7a:15:ca:3c:0d 
           Device-2: Realtek driver: r8169 
           IF: enp60s0 state: up speed: 100 Mbps duplex: full mac: 8c:04:ba:a1:57:6b 
           IF-ID-1: virbr0 state: down mac: 52:54:00:e8:2d:5c 
           IF-ID-2: virbr0-nic state: down mac: 52:54:00:e8:2d:5c 
Drives:    Local Storage: total: 1.38 TiB used: 781.11 GiB (55.5%) 
           ID-1: /dev/nvme0n1 vendor: SK Hynix model: PC601 NVMe 512GB size: 476.94 GiB 
           ID-2: /dev/sda type: USB vendor: Western Digital model: WD10TMVV-11TK7S1 size: 931.51 GiB 
Partition: ID-1: / size: 31.98 GiB used: 14.81 GiB (46.3%) fs: xfs dev: /dev/dm-1 
           ID-2: /boot size: 1014.0 MiB used: 291.9 MiB (28.8%) fs: xfs dev: /dev/nvme0n1p2 
           ID-3: /home size: 50.19 GiB used: 42.87 GiB (85.4%) fs: xfs dev: /dev/dm-3 
Swap:      ID-1: swap-1 type: partition size: 7.79 GiB used: 0 KiB (0.0%) dev: /dev/dm-2 
Sensors:   System Temperatures: cpu: 53.0 C mobo: N/A gpu: nvidia temp: 50 C 
           Fan Speeds (RPM): N/A 
Info:      Processes: 427 Uptime: 46m Memory: 15.45 GiB used: 2.99 GiB (19.4%) Shell: bash inxi: 3.1.03 


Version-Release number of selected component (if applicable):

Fedora 32 + GNOME + Nvidia up to date.

How reproducible:


Steps to Reproduce:
1. run "sudo systemctl suspend -i"
2. wait
3. press power button

Actual results:
Session crash and I get on tty used by previous session, a character login prompt and I must switch with CTRL+ALT+F1 to gdi and re-login with my user

Expected results:

Not crash and enter screen lock password.

Additional info:
Attach last session crash log


Note You need to log in before you can comment on or make changes to this bug.