Sudden Session Log Out while using MATE - Why it happens?

[cxbignekoc]

Hi, i want to share an issue i got the first time.

Release 22.04.1 LTS (Jammy Jellyfish) 64-bit
Kernel Linux 5.15.0-52-generic x86_64
MATE 1.26.0
Intel® Core™ i7-4790 CPU @ 3.60GHz × 8 
AMD HAWAII (LLVM 13.0.1, DRM 2.50, 5.15.0-52-generic)
LUKS encrypted
2 Displays

Session:

What i was doing before in this session:

• update upgrade
• backup
• auto updater
• uninstall shotwell install xnview
• try remove the zrythm daw from the system
• open discord, firefox/yt
• open Signal Messenger
• open bitwig and close it because weird sounding samples
• open renoise (checking jackd, alsa stuff to get sound out)

So i got some Apps open before this happens:

• firefox (youtube is run vids )
• discord (noting special)
• renoise (tracker daw is just in focus)

i was in renoise and starting to build some sounds into the tracker,
suddly i got a short black screen and was kicked out of the session into login view.
i logged in and all apps are closed. no errors no warnings or popups.

xsession-errors:

Summary

(caja:564297): Gtk-WARNING **: 03:26:17.055: Creating a portal monitor failed: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._g_2dio_2derror_2dquark.Code24: Error calling StartServiceByName for org.freedesktop.impl.portal.desktop.gtk: Timeout was reached
[2022-10-27T01:26:17Z ERROR mp4parse] Found 2 nul bytes in "\0\0"
[2022-10-27T01:26:17Z ERROR mp4parse] Found 2 nul bytes in "\0\0"
[2022-10-27T01:26:17Z ERROR mp4parse] Found 2 nul bytes in "\0\0"
[2022-10-27T01:26:17Z ERROR mp4parse] Found 2 nul bytes in "\0\0"
[2022-10-27T01:26:19Z ERROR mp4parse] Found 2 nul bytes in "\0\0"
[2022-10-27T01:26:19Z ERROR mp4parse] Found 2 nul bytes in "\0\0"
[2022-10-27T01:26:19Z ERROR mp4parse] Found 2 nul bytes in "\0\0"
[2022-10-27T01:26:19Z ERROR mp4parse] Found 2 nul bytes in "\0\0"
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2e00007 (System Mon)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2200007 (Authentica)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Warning: failed to launch javaldx - java may not function correctly

(soffice:566192): dbind-WARNING **: 03:40:59.464: Couldn't connect to accessibility bus: Failed to connect to socket /root/.cache/at-spi/bus_0: Permission denied
RuntimeError: object at 0x7f690ccd1ec0 of type FolderColorMenu is not initialized
RuntimeError: object at 0x7f690ccd1ec0 of type FolderColorMenu is not initialized

** (caja:564297): CRITICAL **: 03:55:02.224: caja_bookmark_get_location: assertion 'CAJA_IS_BOOKMARK (bookmark)' failed

(caja:564297): GLib-GIO-CRITICAL **: 03:55:02.224: g_file_get_uri: assertion 'G_IS_FILE (file)' failed
sys:1: Warning: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
RuntimeError: object at 0x7f690ccd1ec0 of type FolderColorMenu is not initialized

** (caja:564297): CRITICAL **: 03:55:05.064: caja_bookmark_get_location: assertion 'CAJA_IS_BOOKMARK (bookmark)' failed

(caja:564297): GLib-GIO-CRITICAL **: 03:55:05.064: g_file_get_uri: assertion 'G_IS_FILE (file)' failed
RuntimeError: object at 0x7f690ccd1ec0 of type FolderColorMenu is not initialized

** (caja:564297): CRITICAL **: 03:55:13.706: caja_bookmark_get_location: assertion 'CAJA_IS_BOOKMARK (bookmark)' failed

(caja:564297): GLib-GIO-CRITICAL **: 03:55:13.706: g_file_get_uri: assertion 'G_IS_FILE (file)' failed
sys:1: Warning: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
RuntimeError: object at 0x7f690ccd1ec0 of type FolderColorMenu is not initialized

** (caja:564297): CRITICAL **: 03:55:22.881: caja_bookmark_get_location: assertion 'CAJA_IS_BOOKMARK (bookmark)' failed

(caja:564297): GLib-GIO-CRITICAL **: 03:55:22.881: g_file_get_uri: assertion 'G_IS_FILE (file)' failed
RuntimeError: object at 0x7f690ccd1ec0 of type FolderColorMenu is not initialized

** (caja:564297): CRITICAL **: 03:55:25.855: caja_bookmark_get_location: assertion 'CAJA_IS_BOOKMARK (bookmark)' failed

(caja:564297): GLib-GIO-CRITICAL **: 03:55:25.855: g_file_get_uri: assertion 'G_IS_FILE (file)' failed
sys:1: Warning: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
RuntimeError: object at 0x7f690ccd1ec0 of type FolderColorMenu is not initialized

** (caja:564297): CRITICAL **: 03:55:27.143: caja_bookmark_get_location: assertion 'CAJA_IS_BOOKMARK (bookmark)' failed

(caja:564297): GLib-GIO-CRITICAL **: 03:55:27.143: g_file_get_uri: assertion 'G_IS_FILE (file)' failed
sys:1: Warning: g_object_unref: assertion 'G_IS_OBJECT (object)' failed

(pluma:566909): dbind-WARNING **: 03:55:37.906: Couldn't connect to accessibility bus: Failed to connect to socket /root/.cache/at-spi/bus_0: Permission denied

kern.log:

Summary

Oct 27 03:25:38 box kernel: [35917.348548] ------------[ cut here ]------------
Oct 27 03:25:38 box kernel: [35917.348550] WARNING: CPU: 2 PID: 1811 at drivers/gpu/drm/ttm/ttm_bo.c:409 ttm_bo_release+0x323/0x350 [ttm]
Oct 27 03:25:38 box kernel: [35917.348559] Modules linked in: snd_seq_dummy snd_hrtimer ntfs3 vboxnetadp(O) vboxnetflt(O) vboxdrv(O) binfmt_misc nls_iso8859_1 joydev input_leds snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi snd_hda_intel intel_rapl_msr snd_intel_dspcfg snd_intel_sdw_acpi mei_hdcp snd_hda_codec snd_hda_core snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event intel_rapl_common snd_rawmidi x86_pkg_temp_thermal snd_seq intel_powerclamp snd_seq_device coretemp snd_timer rapl intel_cstate snd eeepc_wmi wmi_bmof mei_me at24 soundcore mei mac_hid sch_fq_codel ipmi_devintf ipmi_msghandler msr parport_pc ppdev lp parport ramoops pstore_blk reed_solomon pstore_zone efi_pstore ip_tables x_tables autofs4 dm_crypt dm_mirror dm_region_hash dm_log uas usb_storage amdgpu iommu_v2 gpu_sched hid_generic usbhid hid radeon mfd_aaeon i2c_algo_bit asus_wmi drm_ttm_helper sparse_keymap ttm platform_profile mxm_wmi crct10dif_pclmul drm_kms_helper crc32_pclmul ghash_clmulni_intel aesni_intel
Oct 27 03:25:38 box kernel: [35917.348597] syscopyarea crypto_simd sysfillrect cryptd sysimgblt fb_sys_fops cec e1000e rc_core lpc_ich i2c_i801 drm ahci xhci_pci libahci i2c_smbus xhci_pci_renesas wmi video
Oct 27 03:25:38 box kernel: [35917.348607] CPU: 2 PID: 1811 Comm: Xorg Tainted: G O 5.15.0-52-generic #58-Ubuntu
Oct 27 03:25:38 box kernel: [35917.348609] Hardware name: ASUS All Series/MAXIMUS VI GENE, BIOS 1603 08/15/2014
Oct 27 03:25:38 box kernel: [35917.348610] RIP: 0010:ttm_bo_release+0x323/0x350 [ttm]
Oct 27 03:25:38 box kernel: [35917.348614] Code: b8 fe ff ff e8 fe 74 12 00 49 8b 74 24 08 4c 89 ef e8 51 2a 00 00 49 8b 7c 24 98 e9 2f fd ff ff e8 02 57 5a d4 e9 63 fd ff ff <0f> 0b e9 01 fd ff ff e8 11 55 5a d4 e9 e2 fe ff ff be 03 00 00 00
Oct 27 03:25:38 box kernel: [35917.348616] RSP: 0018:ffffbac9027dbba0 EFLAGS: 00010202
Oct 27 03:25:38 box kernel: [35917.348617] RAX: 0000000000000001 RBX: ffffbac9027dbc00 RCX: 0000000000000000
Oct 27 03:25:38 box kernel: [35917.348619] RDX: 0000000000000002 RSI: ffff96e102248138 RDI: ffff96e11803b1d8
Oct 27 03:25:38 box kernel: [35917.348619] RBP: ffffbac9027dbbc8 R08: ffff96e11803b1d8 R09: 0000000000000064
Oct 27 03:25:38 box kernel: [35917.348620] R10: 0000000000000010 R11: 0000000000000000 R12: ffff96e11803b1d8
Oct 27 03:25:38 box kernel: [35917.348621] R13: ffff96e1014106f0 R14: ffff96e11803b078 R15: ffff96e10b663f00
Oct 27 03:25:38 box kernel: [35917.348623] FS: 0000000000000000(0000) GS:ffff96e40ec80000(0000) knlGS:0000000000000000
Oct 27 03:25:38 box kernel: [35917.348624] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Oct 27 03:25:38 box kernel: [35917.348625] CR2: 000000c000080000 CR3: 0000000372610001 CR4: 00000000001706e0
Oct 27 03:25:38 box kernel: [35917.348626] Call Trace:
Oct 27 03:25:38 box kernel: [35917.348627]
Oct 27 03:25:38 box kernel: [35917.348629] ttm_bo_put+0x34/0x50 [ttm]
Oct 27 03:25:38 box kernel: [35917.348634] radeon_bo_unref+0x1e/0x30 [radeon]
Oct 27 03:25:38 box kernel: [35917.348667] radeon_gem_object_free+0x34/0x50 [radeon]
Oct 27 03:25:38 box kernel: [35917.348689] drm_gem_object_free+0x1d/0x30 [drm]
Oct 27 03:25:38 box kernel: [35917.348710] drm_gem_dmabuf_release+0x44/0x70 [drm]
Oct 27 03:25:38 box kernel: [35917.348728] dma_buf_release+0x46/0xa0
Oct 27 03:25:38 box kernel: [35917.348731] __dentry_kill+0x10e/0x190
Oct 27 03:25:38 box kernel: [35917.348734] dentry_kill+0x52/0x1c0
Oct 27 03:25:38 box kernel: [35917.348735] dput+0x137/0x180
Oct 27 03:25:38 box kernel: [35917.348737] __fput+0xf0/0x260
Oct 27 03:25:38 box kernel: [35917.348739] ____fput+0xe/0x20
Oct 27 03:25:38 box kernel: [35917.348741] task_work_run+0x6d/0xb0
Oct 27 03:25:38 box kernel: [35917.348743] do_exit+0x217/0x3c0
Oct 27 03:25:38 box kernel: [35917.348746] do_group_exit+0x3b/0xb0
Oct 27 03:25:38 box kernel: [35917.348748] get_signal+0x150/0x900
Oct 27 03:25:38 box kernel: [35917.348749] ? send_signal+0xe9/0x130
Oct 27 03:25:38 box kernel: [35917.348752] arch_do_signal_or_restart+0xde/0x100
Oct 27 03:25:38 box kernel: [35917.348754] ? do_send_specific+0x61/0xa0
Oct 27 03:25:38 box kernel: [35917.348757] exit_to_user_mode_loop+0xc4/0x160
Oct 27 03:25:38 box kernel: [35917.348760] exit_to_user_mode_prepare+0xa0/0xb0
Oct 27 03:25:38 box kernel: [35917.348762] syscall_exit_to_user_mode+0x27/0x50
Oct 27 03:25:38 box kernel: [35917.348764] ? __x64_sys_tgkill+0x29/0x40
Oct 27 03:25:38 box kernel: [35917.348767] do_syscall_64+0x69/0xc0
Oct 27 03:25:38 box kernel: [35917.348769] ? exit_to_user_mode_prepare+0x37/0xb0
Oct 27 03:25:38 box kernel: [35917.348771] ? syscall_exit_to_user_mode+0x27/0x50
Oct 27 03:25:38 box kernel: [35917.348773] ? do_syscall_64+0x69/0xc0
Oct 27 03:25:38 box kernel: [35917.348774] ? do_syscall_64+0x69/0xc0
Oct 27 03:25:38 box kernel: [35917.348776] entry_SYSCALL_64_after_hwframe+0x61/0xcb
Oct 27 03:25:38 box kernel: [35917.348779] RIP: 0033:0x7fd5a704aa7c
Oct 27 03:25:38 box kernel: [35917.348781] Code: Unable to access opcode bytes at RIP 0x7fd5a704aa52.
Oct 27 03:25:38 box kernel: [35917.348781] RSP: 002b:00007fff03000de0 EFLAGS: 00000246 ORIG_RAX: 00000000000000ea
Oct 27 03:25:38 box kernel: [35917.348783] RAX: 0000000000000000 RBX: 00007fd5a6c43a80 RCX: 00007fd5a704aa7c
Oct 27 03:25:38 box kernel: [35917.348784] RDX: 0000000000000006 RSI: 0000000000000713 RDI: 0000000000000713
Oct 27 03:25:38 box kernel: [35917.348785] RBP: 0000000000000713 R08: 00007fff03000eb0 R09: 0000000000000000
Oct 27 03:25:38 box kernel: [35917.348786] R10: 0000000000000008 R11: 0000000000000246 R12: 0000000000000006
Oct 27 03:25:38 box kernel: [35917.348787] R13: 0000000000000016 R14: 0000556c20ec99d0 R15: 0000000000000000
Oct 27 03:25:38 box kernel: [35917.348788]
Oct 27 03:25:38 box kernel: [35917.348789] ---[ end trace 61c9e6a930420e0e ]---
Oct 27 03:25:38 box kernel: [35917.399250] Lockdown: Xorg: raw io port access is restricted; see man kernel_lockdown.7
Oct 27 03:25:39 box kernel: [35918.783666] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Oct 27 03:25:39 box kernel: [35918.787938] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7

[jymm]

While I have no answer, I have had this happen on Ubuntu Mate, Mint Mate and Parrot Mate. Also that is three different computers,two different brands and models. It does not happen often, but is annoying when it does. If you solve it, let us know.

[tkn]

It might be this:

Ubuntu Mate 22.04 auto ending Sessions when I do something specific

@Ygor6889, Igor, is your video card also from intel? I just solved the problem on the Latitude E6410. I created the /etc/X11/xorg.conf.d/20-intel.conf file with the following content: $ cat /etc/X11/xorg.conf.d/20-intel.conf Section "Device" Identifier "Intel Graphics" Driver "intel" Option "TearFree" "true" EndSection Then I restarted the system and Ubuntu Mate stopped crashing! I saw someone on this post reporting a similar problem: And then I followed what was in the 6.1 section of …

[DLS]

Minus the Mint and Parrot references I second. It happened to me on both laptops and desktops.

From my end I suspect this has something to do with the video/resolution but yes fairly annoying, thankfully we have Startup applications.

[cxbignekoc]

i dont know if TEARING is the Problem...but it can maybe come together with this issue, but i dont check this.
i dont want to try it yet.

[6ya2kd2nb]

I tried this and was stuck in the CLI login screen. So I shredded 20-intel.conf file, restarted, and I'm good now. I still have sudden log out problems, but now at least I can log in, in the first place.