# Dumb question

**URL:** <https://forums.suse.com/t/dumb-question/35404>\
**Category:** SUSE Linux Enterprise Desktop\
**Created:** [December 2, 2020, 8:49am UTC](https://forums.suse.com/t/dumb-question/35404 "2020-12-02T08:49:24Z")\
**Posts on this page:** 10\
**Page:** 4

<div class="post-metadata">

**Author:** ![jtlong](https://avatars.discourse-cdn.com/v4/letter/j/ccd318/32.png) [@jtlong](https://forums.suse.com/u/jtlong)\
**Post date:** [January 6, 2021, 9:38pm UTC](https://forums.suse.com/t/dumb-question/35404/61 "2021-01-06T21:38:17Z")

</div>

In the systemd journal viewer I’m seeing multiple coredumps of two specific types:

```auto
Time: Jan 06 06:35:31
Source: systemd-coredum[26176]
Message: Process 21337 (gnome-shell) of user 1000 dumped core.

Stack trace of thread 21337:
#0 0x00007f30a0643170 raise (libpthread.so.0)
#1 0x000055e218a85c6b n/a (gnome-shell)
#2 0x00007f30a06432d0 __restore_rt (libpthread.so.0)
#3 0x00007f30a02ae520 raise (libc.so.6)
#4 0x00007f30a02afb01 abort (libc.so.6)
#5 0x00007f30a2409d1d g_assertion_message (libglib-2.0.so.0)
#6 0x00007f30a2409daa g_assertion_message_expr (libglib-2.0.so.0)
#7 0x00007f309fe2e53c n/a (libst-1.0.so)
#8 0x00007f30a26c432c g_object_run_dispose (libgobject-2.0.so.0)
#9 0x00007f30a104d076 clutter_actor_destroy (libmutter-clutter-1.so)
#10 0x00007f309c2cf6bd n/a (libffi.so.7)
#11 0x00007f309c2cebcf n/a (libffi.so.7)
#12 0x00007f30a1390490 n/a (libgjs.so.0)
#13 0x00007f30a1391c64 n/a (libgjs.so.0)
#14 0x00007f309910fd7c n/a (libmozjs-52.so)
#15 0x00007f309910a466 n/a (libmozjs-52.so)
#16 0x00007f309910f81e n/a (libmozjs-52.so)
#17 0x00007f309910fb82 n/a (libmozjs-52.so)
#18 0x00007f30993600b2 n/a (libmozjs-52.so)
#19 0x000002aa97af2a96 n/a (n/a)

```

The other is a two-part sequence as so:

```auto
Time: Jan 05 21:31:07
Source: kernel
Message: traps: appstreamcli[1087] trap int3 ip:7f7856f27bd1 sp:7ffc706af570 error:0 in libglib-2.0.so.0.5400.3[7f7856ed4000+116000]

TIme: Jan 05 21:31:07
Source: systemd-coredum[1089]
Message: Process 1087 (appstreamcli) of user 0 dumped core.

Stack trace of thread 1087:
#0 0x00007f7856f27bd1 n/a (libglib-2.0.so.0)
#1 0x00007f7856f28c6c g_log_default_handler (libglib-2.0.so.0)
#2 0x00007f7856f28ef2 g_logv (libglib-2.0.so.0)
#3 0x00007f7856f2904f g_log (libglib-2.0.so.0)
#4 0x00007f7856f62c73 g_variant_new_parsed_va (libglib-2.0.so.0)
#5 0x00007f7856f62e1b g_variant_builder_add_parsed (libglib-2.0.so.0)
#6 0x00007f785721d3a8 n/a (libappstream.so.4)
#7 0x00007f785720e3b9 n/a (libappstream.so.4)
#8 0x00007f78572131de as_cache_file_save (libappstream.so.4)
#9 0x00007f78572134e4 as_pool_save_cache_file (libappstream.so.4)
#10 0x00007f78572136cd as_pool_refresh_cache (libappstream.so.4)
#11 0x0000555d5dc2d1d6 n/a (appstreamcli)
#12 0x0000555d5dc2af0c n/a (appstreamcli)
#13 0x00007f785654a34a __libc_start_main (libc.so.6)
#14 0x0000555d5dc2a47a n/a (appstreamcli)

```

I’m PRETTY SURE this is OpenGL, and directly related to my issue! 😃

---

<div class="post-metadata">

**Author:** ![jtlong](https://avatars.discourse-cdn.com/v4/letter/j/ccd318/32.png) [@jtlong](https://forums.suse.com/u/jtlong)\
**Post date:** [January 6, 2021, 9:58pm UTC](https://forums.suse.com/t/dumb-question/35404/62 "2021-01-06T21:58:20Z")

</div>

I found SOME Xorg log stuff, not sure this is what you want, but I was happy I found it anyway:

```auto
linux-gx1p:/home/james # grep nvidia /var/log/Xorg.0.log
[17.510] (==) Matched nvidia as autoconfigured driver 0
[17.511] (II) LoadModule: "nvidia"
[17.511] (II) Loading /usr/lib64/xorg/modules/drivers/nvidia_drv.so
[17.519] (II) Module nvidia: vendor="NVIDIA Corporation"
[17.532] (WW) NVIDIA(0): visit http://www.nvidia.com/object/unix.html for more
linux-gx1p:/home/james # grep nv /var/log/Xorg.0.log
[17.510] (==) Matched nvidia as autoconfigured driver 0
[17.510] (==) Matched nv as autoconfigured driver 2
[17.511] (II) LoadModule: "nvidia"
[17.511] (II) Loading /usr/lib64/xorg/modules/drivers/nvidia_drv.so
[17.519] (II) Module nvidia: vendor="NVIDIA Corporation"
[17.525] (II) LoadModule: "nv"
[17.526] (WW) Warning, couldn't open module nv
[17.526] (EE) Failed to load module "nv" (module does not exist, 0)
[17.532] (WW) NVIDIA(0): visit http://www.nvidia.com/object/unix.html for more
[17.658] (II) FBDEV(0): FBIOBLANK: Invalid argument (Screen blanking not supported by kernel - disabling)
linux-gx1p:/home/james # grep opengl /var/log/Xorg.0.log
linux-gx1p:/home/james # grep libgl /var/log/Xorg.0.log
[17.499] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so
linux-gx1p:/home/james # grep Failed /var/log/Xorg.0.log
[17.526] (EE) Failed to load module "nv" (module does not exist, 0)
[17.656] (EE) [drm] Failed to open DRM device for pci:0000:01:00.0: -19
linux-gx1p:/home/james # grep Warning /var/log/Xorg.0.log
[17.526] (WW) Warning, couldn't open module nv
linux-gx1p:/home/james # grep Error /var/log/Xorg.0.log
linux-gx1p:/home/james # 

```

---

<div class="post-metadata">

**Author:** ![jtlong](https://avatars.discourse-cdn.com/v4/letter/j/ccd318/32.png) [@jtlong](https://forums.suse.com/u/jtlong)\
**Post date:** [January 6, 2021, 10:41pm UTC](https://forums.suse.com/t/dumb-question/35404/63 "2021-01-06T22:41:52Z")

</div>

I found /var/log/gdm/greeter.log …it looks terribly relevant, but I don’t know what to make of it. I would guess that those ‘failed to set screen’ errors is when my desktop locks up. It has some shadow error listed a few hundred times. No, seriously. Everywhere you see:

```auto
(gnome-shell:2488): St-CRITICAL **: _st_paint_shadow_with_opacity: assertion 'shadow_pipeline != NULL' failed

```

…assume it was listed a few hundred times. because it was:  
[https://cryptpad.fr/code/#/2/code/edit/pyhQRg2E0Bcmm6Y7mYKtO7Pj/](https://cryptpad.fr/code/#/2/code/edit/pyhQRg2E0Bcmm6Y7mYKtO7Pj/)

---

<div class="post-metadata">

**Author:** ![jtlong](https://avatars.discourse-cdn.com/v4/letter/j/ccd318/32.png) [@jtlong](https://forums.suse.com/u/jtlong)\
**Post date:** [January 7, 2021, 4:21am UTC](https://forums.suse.com/t/dumb-question/35404/64 "2021-01-07T04:21:58Z")

</div>

Again, not sure if this is what you wanted, but it looks important. 😃

```auto
linux-gx1p:/home/james # cat .xsession-errors
gpg-connect-agent: no gpg-agent running in this session
gpg-connect-agent: no gpg-agent running in this session
IceWM: reboot... (/bin/sh -c 'systemctl reboot ||:')
XIO: fatal IO error 0 (Success) on X server ":0"
      after 1261 requests (1261 known processed) with 12 events remaining.
icewmbg: Can't open display: :0. X must be running and $DISPLAY set.
linux-gx1p:/home/james # 

```

---

<div class="post-metadata">

**Author:** ![jtlong](https://avatars.discourse-cdn.com/v4/letter/j/ccd318/32.png) [@jtlong](https://forums.suse.com/u/jtlong)\
**Post date:** [January 7, 2021, 4:23am UTC](https://forums.suse.com/t/dumb-question/35404/65 "2021-01-07T04:23:33Z")

</div>

I actually searched and found where you instructed a different user to do this… not sure if it’s helpful here, but I tried. 🙂

```auto
linux-gx1p:/home/james # journalctl -f
-- Logs begin at Sun 2021-01-03 02:41:40 MST. --
Jan 06 21:20:21 linux-gx1p systemd[29960]: Received SIGRTMIN+24 from PID 30003 (kill).
Jan 06 21:20:21 linux-gx1p systemd[29961]: pam_unix(systemd-user:session): session closed for user munin
Jan 06 21:20:21 linux-gx1p systemd[1]: user-runtime-dir@461.service: Unit not needed anymore. Stopping.
Jan 06 21:20:21 linux-gx1p systemd[1]: Stopped User Manager for UID 461.
Jan 06 21:20:21 linux-gx1p systemd[1]: user-runtime-dir@461.service: Unit not needed anymore. Stopping.
Jan 06 21:20:21 linux-gx1p systemd[1]: user-461.slice: Unit not needed anymore. Stopping.
Jan 06 21:20:21 linux-gx1p systemd[1]: Stopping User Runtime Directory /run/user/461...
Jan 06 21:20:22 linux-gx1p systemd[1]: Stopped User Runtime Directory /run/user/461.
Jan 06 21:20:22 linux-gx1p systemd[1]: user-461.slice: Unit not needed anymore. Stopping.
Jan 06 21:20:22 linux-gx1p systemd[1]: Removed slice User Slice of UID 461.
^C
linux-gx1p:/home/james # 

```

---

<div class="post-metadata">

**Author:** ![malcolmlewis](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/malcolmlewis/32/11375_2.png) [@malcolmlewis](https://forums.suse.com/u/malcolmlewis)\
**Post date:** [January 7, 2021, 2:17pm UTC](https://forums.suse.com/t/dumb-question/35404/66 "2021-01-07T14:17:12Z")

</div>

@“[jtlong@gmx.com](mailto:jtlong@gmx.com)” Hi, you have been busy 😉 It such a mixture (openSUSE+SLE), I’m not really sure what to do ☹ I honestly suggest backup all your important data and verify it, re-install either SLED or openSUSE…

---

<div class="post-metadata">

**Author:** ![jtlong](https://avatars.discourse-cdn.com/v4/letter/j/ccd318/32.png) [@jtlong](https://forums.suse.com/u/jtlong)\
**Post date:** [January 7, 2021, 6:36pm UTC](https://forums.suse.com/t/dumb-question/35404/67 "2021-01-07T18:36:13Z")

</div>

I have more terribly interesting datum. This morning my desktop was crashed AND logged out, which doesn’t happen often. The end of my /var/log/gdm/greeter.log looks like this:

```auto
(gnome-shell:2488): St-CRITICAL **: _st_paint_shadow_with_opacity: assertion 'shadow_pipeline != NULL' failed

(gnome-shell:2488): St-CRITICAL **: _st_paint_shadow_with_opacity: assertion 'shadow_pipeline != NULL' failed

(gnome-shell:2488): St-CRITICAL **: _st_paint_shadow_with_opacity: assertion 'shadow_pipeline != NULL' failed

(gsd-color:2618): color-plugin-WARNING **: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/xrandr_AU_Optronics_james_1000
(II) systemd-logind: got resume for 13:78
(--) NVIDIA(GPU-0): CRT-0: disconnected
(--) NVIDIA(GPU-0): CRT-0: 400.0 MHz maximum pixel clock
(--) NVIDIA(GPU-0): 
(--) NVIDIA(GPU-0): AU Optronics Corporation (DFP-0): connected
(--) NVIDIA(GPU-0): AU Optronics Corporation (DFP-0): Internal LVDS
(--) NVIDIA(GPU-0): AU Optronics Corporation (DFP-0): 330.0 MHz maximum pixel clock
(--) NVIDIA(GPU-0): 
(--) NVIDIA(GPU-0): DFP-1: disconnected
(--) NVIDIA(GPU-0): DFP-1: Internal TMDS
(--) NVIDIA(GPU-0): DFP-1: 165.0 MHz maximum pixel clock
(--) NVIDIA(GPU-0): 
(--) NVIDIA(GPU-0): DFP-2: disconnected
(--) NVIDIA(GPU-0): DFP-2: Internal TMDS
(--) NVIDIA(GPU-0): DFP-2: 165.0 MHz maximum pixel clock
(--) NVIDIA(GPU-0): 
(--) NVIDIA(GPU-0): DFP-3: disconnected
(--) NVIDIA(GPU-0): DFP-3: Internal TMDS
(--) NVIDIA(GPU-0): DFP-3: 165.0 MHz maximum pixel clock
(--) NVIDIA(GPU-0): 
(--) NVIDIA(GPU-0): DFP-4: disconnected
(--) NVIDIA(GPU-0): DFP-4: Internal DisplayPort
(--) NVIDIA(GPU-0): DFP-4: 480.0 MHz maximum pixel clock
(--) NVIDIA(GPU-0): 
(--) NVIDIA(GPU-0): DFP-5: disconnected
(--) NVIDIA(GPU-0): DFP-5: Internal DisplayPort
(--) NVIDIA(GPU-0): DFP-5: 480.0 MHz maximum pixel clock
(--) NVIDIA(GPU-0): 
(--) NVIDIA(GPU-0): DFP-6: disconnected
(--) NVIDIA(GPU-0): DFP-6: Internal DisplayPort
(--) NVIDIA(GPU-0): DFP-6: 480.0 MHz maximum pixel clock
(--) NVIDIA(GPU-0): 
(--) NVIDIA(GPU-0): DFP-7: disconnected
(--) NVIDIA(GPU-0): DFP-7: Internal DisplayPort
(--) NVIDIA(GPU-0): DFP-7: 480.0 MHz maximum pixel clock
(--) NVIDIA(GPU-0): 
(II) NVIDIA(0): Setting mode "DFP-0:nvidia-auto-select"
(II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
(II) NVIDIA(0): may not be running or the "AcpidSocketPath" X
(II) NVIDIA(0): configuration option may not be set correctly. When the
(II) NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will
(II) NVIDIA(0): try to use it to receive ACPI event notifications. For
(II) NVIDIA(0): details, please see the "ConnectToAcpid" and
(II) NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X
(II) NVIDIA(0): Config Options in the README.
(II) event14 - HP WMI hotkeys: is tagged by udev as: Keyboard Switch
(II) event14 - HP WMI hotkeys: device is a keyboard
(II) event14 - HP WMI hotkeys: device is a switch device
(II) systemd-logind: got resume for 13:70
(II) event6 - Power Button: is tagged by udev as: Keyboard
(II) event6 - Power Button: device is a keyboard
(II) systemd-logind: got resume for 13:65
(II) event1 - PS/2 Generic Mouse: is tagged by udev as: Mouse
(II) event1 - PS/2 Generic Mouse: device is a pointer
(II) systemd-logind: got resume for 13:66
(--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Internal error: Could not resolve keysym XF86WWAN
> Internal error: Could not resolve keysym XF86RFKill
Errors from xkbcomp are not fatal to the X server
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Internal error: Could not resolve keysym XF86WWAN
> Internal error: Could not resolve keysym XF86RFKill
Errors from xkbcomp are not fatal to the X server
(II) systemd-logind: got resume for 13:67
(II) event3 - Logitech M570: is tagged by udev as: Mouse Trackball
(II) event3 - Logitech M570: device set to 540 DPI
(II) event3 - Logitech M570: device is a pointer
(II) systemd-logind: got resume for 13:84
(II) event20 - HP HD Webcam [Fixed]: is tagged by udev as: Keyboard
(II) event20 - HP HD Webcam [Fixed]: device is a keyboard
(II) systemd-logind: got resume for 13:64
(II) event0 - AT Translated Set 2 keyboard: is tagged by udev as: Keyboard
(II) event0 - AT Translated Set 2 keyboard: device is a keyboard
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Internal error: Could not resolve keysym XF86WWAN
> Internal error: Could not resolve keysym XF86RFKill
Errors from xkbcomp are not fatal to the X server
(II) systemd-logind: got resume for 13:68
(II) event4 - Sleep Button: is tagged by udev as: Keyboard
(II) event4 - Sleep Button: device is a keyboard
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Internal error: Could not resolve keysym XF86WWAN
> Internal error: Could not resolve keysym XF86RFKill
Errors from xkbcomp are not fatal to the X server
(II) systemd-logind: got resume for 13:71
(II) event7 - Video Bus: is tagged by udev as: Keyboard
(II) event7 - Video Bus: device is a keyboard
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Internal error: Could not resolve keysym XF86WWAN
> Internal error: Could not resolve keysym XF86RFKill
Errors from xkbcomp are not fatal to the X server
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Internal error: Could not resolve keysym XF86WWAN
> Internal error: Could not resolve keysym XF86RFKill
Errors from xkbcomp are not fatal to the X server
(**) Option "fd" "41"
(II) event6 - Power Button: device removed
(**) Option "fd" "55"
(II) event7 - Video Bus: device removed
(**) Option "fd" "45"
(II) event4 - Sleep Button: device removed
(**) Option "fd" "42"
(II) event3 - Logitech M570: device removed
(**) Option "fd" "43"
(II) event20 - HP HD Webcam [Fixed]: device removed
(**) Option "fd" "44"
(II) event0 - AT Translated Set 2 keyboard: device removed
(**) Option "fd" "22"
(II) event1 - PS/2 Generic Mouse: device removed
(**) Option "fd" "23"
(II) event14 - HP WMI hotkeys: device removed
(II) systemd-logind: got pause for 13:78
(II) systemd-logind: got pause for 13:70
(II) systemd-logind: got pause for 13:65
(II) systemd-logind: got pause for 13:66
(II) systemd-logind: got pause for 13:67
(II) systemd-logind: got pause for 13:84
(II) systemd-logind: got pause for 13:64
(II) systemd-logind: got pause for 13:68
(II) systemd-logind: got pause for 13:71

(gsd-color:2618): color-plugin-WARNING **: failed to set screen _ICC_PROFILE: Failed to open file Â/home/james/.local/share/icc/edid-495796445433b44b3e4ea01c88d1dcf1.iccÂ: Permission denied

(gsd-color:2618): color-plugin-WARNING **: failed to set screen _ICC_PROFILE: Failed to open file Â/home/james/.local/share/icc/edid-495796445433b44b3e4ea01c88d1dcf1.iccÂ: Permission denied

```

---

<div class="post-metadata">

**Author:** ![jtlong](https://avatars.discourse-cdn.com/v4/letter/j/ccd318/32.png) [@jtlong](https://forums.suse.com/u/jtlong)\
**Post date:** [January 7, 2021, 6:50pm UTC](https://forums.suse.com/t/dumb-question/35404/68 "2021-01-07T18:50:20Z")

</div>

I found a file named /var/log/warn that has a disturbing amout of warnings since I just logged in like two minutes ago. There was a disturbing number of this trio listed:

```auto
2021-01-07T06:12:25.232572-07:00 linux-gx1p gnome-software[3190]: json_object_has_member: assertion 'member_name != NULL' failed
2021-01-07T06:12:25.232708-07:00 linux-gx1p gnome-software[3190]: g_strsplit: assertion 'string != NULL' failed
2021-01-07T06:12:25.232840-07:00 linux-gx1p gnome-software[3190]: g_strv_length: assertion 'str_array != NULL' failed

```

…directly before the occurance:  
[https://cryptpad.fr/code/#/2/code/edit/yvDw1IYmFGqmc00WwaWpbcVI/](https://cryptpad.fr/code/#/2/code/edit/yvDw1IYmFGqmc00WwaWpbcVI/)

I WOULD like to clean up whatever is hitting my log hundreds and thousands of times. I spent a lot of money on this SSD drive, I’m not very fond of the idea of killing it off with error logs.

---

<div class="post-metadata">

**Author:** ![jtlong](https://avatars.discourse-cdn.com/v4/letter/j/ccd318/32.png) [@jtlong](https://forums.suse.com/u/jtlong)\
**Post date:** [January 7, 2021, 6:57pm UTC](https://forums.suse.com/t/dumb-question/35404/69 "2021-01-07T18:57:47Z")

</div>

Found this in messages… apparently my suspend never suspends until I wake the machine back up?? Check out the time stamps:

```auto
2021-01-07T06:26:05.699797-07:00 linux-gx1p kernel: [191857.957315] PM: Preparing system for sleep (mem)
2021-01-07T06:26:05.720525-07:00 linux-gx1p systemd-coredump[3419]: Process 31773 (gnome-shell) of user 1000 dumped core.#012#012Stack trace of thread 31773:#012#0 0x00007fe203df6170 raise (libpthread.so.0)#012#1 0x000055a0675d1c6b n/a (gnome-shell)#012#2 0x00007fe203df62d0 __restore_rt (libpthread.so.0)#012#3 0x00007fe203a61520 raise (libc.so.6)#012#4 0x00007fe203a62b01 abort (libc.so.6)#012#5 0x00007fe205bbcd1d g_assertion_message (libglib-2.0.so.0)#012#6 0x00007fe205bbcdaa g_assertion_message_expr (libglib-2.0.so.0)#012#7 0x00007fe2035e153c n/a (libst-1.0.so)#012#8 0x00007fe205e7732c g_object_run_dispose (libgobject-2.0.so.0)#012#9 0x00007fe204800076 clutter_actor_destroy (libmutter-clutter-1.so)#012#10 0x00007fe1ffa826bd n/a (libffi.so.7)#012#11 0x00007fe1ffa81bcf n/a (libffi.so.7)#012#12 0x00007fe204b43490 n/a (libgjs.so.0)#012#13 0x00007fe204b44c64 n/a (libgjs.so.0)#012#14 0x00007fe1fc8c2d7c n/a (libmozjs-52.so)#012#15 0x00007fe1fc8bd466 n/a (libmozjs-52.so)#012#16 0x00007fe1fc8c281e n/a (libmozjs-52.so)#012#17 0x00007fe1fc8c2b82 n/a (libmozjs-52.so)#012#18 0x00007fe1fcb130b2 n/a (libmozjs-52.so)#012#19 0x00003074822b6a96 n/a (n/a)
2021-01-07T11:29:54.678611-07:00 linux-gx1p kernel: [191859.348300] Freezing user space processes ... (elapsed 0.448 seconds) done.
2021-01-07T11:29:54.678630-07:00 linux-gx1p kernel: [191859.797291] OOM killer disabled.
2021-01-07T11:29:54.678632-07:00 linux-gx1p kernel: [191859.797291] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
2021-01-07T11:29:54.678633-07:00 linux-gx1p kernel: [191859.798979] PM: Suspending system (mem)
2021-01-07T11:29:54.678635-07:00 linux-gx1p kernel: [191859.799007] Suspending console(s) (use no_console_suspend to debug)
2021-01-07T11:29:54.678636-07:00 linux-gx1p kernel: [191859.821678] sd 0:0:0:0: [sda] Synchronizing SCSI cache
2021-01-07T11:29:54.678637-07:00 linux-gx1p kernel: [191859.824027] sd 0:0:0:0: [sda] Stopping disk
2021-01-07T11:29:54.678638-07:00 linux-gx1p kernel: [191859.923398] e1000e: EEE TX LPI TIMER: 00000011
2021-01-07T11:29:54.678639-07:00 linux-gx1p kernel: [191861.124221] PM: suspend of devices complete after 1325.031 msecs
2021-01-07T11:29:54.678640-07:00 linux-gx1p kernel: [191861.124800] PM: late suspend of devices complete after 0.575 msecs
2021-01-07T11:29:54.678642-07:00 linux-gx1p kernel: [191861.149688] PM: noirq suspend of devices complete after 24.885 msecs
2021-01-07T11:29:54.678643-07:00 linux-gx1p kernel: [191861.149982] ACPI: Preparing to enter system sleep state S3

```

It goes on and completes the suspend, immediately waking it back up the same second that it completes it’s ‘suspend’ regiment.

---

<div class="post-metadata">

**Author:** ![jtlong](https://avatars.discourse-cdn.com/v4/letter/j/ccd318/32.png) [@jtlong](https://forums.suse.com/u/jtlong)\
**Post date:** [January 7, 2021, 7:11pm UTC](https://forums.suse.com/t/dumb-question/35404/70 "2021-01-07T19:11:00Z")

</div>

I’m sure this is relevant, but I’m not sure if it is helpful, from the the systemd journal:

```auto
Time: Jan 07 06:26:05
Source: systemd-coredum[3419]
Message: Process 31773 (gnome-shell) of user 1000 dumped core.

Stack trace of thread 31773:
#0 0x00007fe203df6170 raise (libpthread.so.0)
#1 0x000055a0675d1c6b n/a (gnome-shell)
#2 0x00007fe203df62d0 __restore_rt (libpthread.so.0)
#3 0x00007fe203a61520 raise (libc.so.6)
#4 0x00007fe203a62b01 abort (libc.so.6)
#5 0x00007fe205bbcd1d g_assertion_message (libglib-2.0.so.0)
#6 0x00007fe205bbcdaa g_assertion_message_expr (libglib-2.0.so.0)
#7 0x00007fe2035e153c n/a (libst-1.0.so)
#8 0x00007fe205e7732c g_object_run_dispose (libgobject-2.0.so.0)
#9 0x00007fe204800076 clutter_actor_destroy (libmutter-clutter-1.so)
#10 0x00007fe1ffa826bd n/a (libffi.so.7)
#11 0x00007fe1ffa81bcf n/a (libffi.so.7)
#12 0x00007fe204b43490 n/a (libgjs.so.0)
#13 0x00007fe204b44c64 n/a (libgjs.so.0)
#14 0x00007fe1fc8c2d7c n/a (libmozjs-52.so)
#15 0x00007fe1fc8bd466 n/a (libmozjs-52.so)
#16 0x00007fe1fc8c281e n/a (libmozjs-52.so)
#17 0x00007fe1fc8c2b82 n/a (libmozjs-52.so)
#18 0x00007fe1fcb130b2 n/a (libmozjs-52.so)
#19 0x00003074822b6a96 n/a (n/a)

```

[Previous page](https://forums.suse.com/t/dumb-question/35404.md?page=3)
