Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

System freeze in Debian 12

If none of the specific sub-forums seem right for your thread, ask here.
Post Reply
Message
Author
User avatar
alienspy
Posts: 159
Joined: 2023-02-12 15:37
Has thanked: 97 times
Been thanked: 5 times

Re: System freeze in Debian 12

#21 Post by alienspy »

I had another freeze. Little bit in other fashion, it didn't happen suddenly, at first i couldn't open apps, then to move windows, then only it get stuck completely.

Unfortunately i can't find the place where exactly freeze happened in journal (i mean i can't find a place where i had to push a reset button). But there are a lot of errors for Telegram app suddenly, but i don't know if they could lead to a freeze.

Please watch the log (i have deleted a lot of repeating lines)

Code: Select all

Jun 19 19:53:21 debian gnome-shell[1237]: GNOME Shell started at Mon Jun 19 2023 19:53:18 GMT+0300 
Jun 19 19:53:21 debian gnome-shell[1237]: Registering session with GDM
Jun 19 19:53:21 debian gnome-shell[1237]: Error registering session with GDM: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.Displ>
Jun 19 19:53:21 debian kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC=8c:b8:7e:f8:23:48:74:9d:79:27:d5:78:08:00 SRC=192.168.1.254 DST=192.168.1.66 LEN=341 TOS=0x00 P>
Jun 19 19:53:21 debian kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC=8c:b8:7e:f8:23:48:74:9d:79:27:d5:78:08:00 SRC=192.168.1.254 DST=192.168.1.66 LEN=341 TOS=0x00 P>
Jun 19 19:53:21 debian kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC= SRC=192.168.1.66 DST=239.192.152.143 LEN=165 TOS=0x00 PREC=0x00 TTL=32 ID=47688 DF PROTO=UDP S>
Jun 19 19:53:22 debian PackageKit[1332]: refresh-cache transaction /1161_abcadebc from uid 1000 finished with success after 1111ms
Jun 19 19:53:23 debian PackageKit[1332]: resolve transaction /1162_abbeaecc from uid 1000 finished with success after 632ms
Jun 19 19:53:24 debian PackageKit[1332]: resolve transaction /1163_ddbdcdac from uid 1000 finished with success after 171ms
Jun 19 19:53:25 debian kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC=8c:b8:7e:f8:23:48:74:9d:79:27:d5:78:08:00 SRC=192.168.1.254 DST=192.168.1.66 LEN=341 TOS=0x00 P>
Jun 19 19:53:25 debian kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC=8c:b8:7e:f8:23:48:74:9d:79:27:d5:78:08:00 SRC=192.168.1.254 DST=192.168.1.66 LEN=341 TOS=0x00 P>
Jun 19 19:53:25 debian kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC= SRC=192.168.1.66 DST=239.192.152.143 LEN=165 TOS=0x00 PREC=0x00 TTL=32 ID=48667 DF PROTO=UDP S>
Jun 19 19:53:29 debian dbus-daemon[946]: [session uid=1000 pid=946] Activating via systemd: service name='ca.desrt.dconf' unit='dconf.service' requested by '>
Jun 19 19:53:29 debian systemd[923]: Starting dconf.service - User preferences database...
Jun 19 19:53:29 debian dbus-daemon[946]: [session uid=1000 pid=946] Successfully activated service 'ca.desrt.dconf'
Jun 19 19:53:29 debian systemd[923]: Started dconf.service - User preferences database.
Jun 19 19:53:29 debian dbus-daemon[946]: [session uid=1000 pid=946] Activating via systemd: service name='org.freedesktop.Tracker3.Miner.Extract' unit='track>
Jun 19 19:53:29 debian systemd[923]: Starting tracker-extract-3.service - Tracker metadata extractor...
Jun 19 19:53:29 debian dbus-daemon[946]: [session uid=1000 pid=946] Successfully activated service 'org.freedesktop.Tracker3.Miner.Extract'
Jun 19 19:53:29 debian systemd[923]: Started tracker-extract-3.service - Tracker metadata extractor.
Jun 19 19:53:30 debian chromium.desktop[1992]: find: ‘/home/ja/.config/chromium/Crash Reports/pending/’: No such file or directory
Jun 19 19:53:30 debian chromium.desktop[2034]: [2034:2034:0619/195330.882194:ERROR:gbm_wrapper.cc(258)] Failed to export buffer to dma_buf: No such file or d>
Jun 19 19:53:30 debian chromium.desktop[2034]: [2034:2034:0619/195330.882363:ERROR:gbm_wrapper.cc(258)] Failed to export buffer to dma_buf: No such file or d>
Jun 19 19:53:30 debian chromium.desktop[2034]: [2034:2034:0619/195330.882465:ERROR:gbm_wrapper.cc(258)] Failed to export buffer to dma_buf: No such file or d>
Jun 19 19:53:30 debian chromium.desktop[2034]: [2034:2034:0619/195330.884962:ERROR:gbm_wrapper.cc(258)] Failed to export buffer to dma_buf: No such file or d>
Jun 19 19:53:30 debian chromium.desktop[2034]: [2034:2034:0619/195330.885033:ERROR:gbm_wrapper.cc(258)] Failed to export buffer to dma_buf: No such file or d>
Jun 19 19:53:30 debian chromium.desktop[2034]: [2034:2034:0619/195330.885097:ERROR:gbm_wrapper.cc(258)] Failed to export buffer to dma_buf: No such file or d>
Jun 19 19:53:36 debian systemd-timesyncd[674]: Contacted time server [2a00:ab00:203:9::1000:6]:123 (2.debian.pool.ntp.org).
Jun 19 19:53:36 debian systemd-timesyncd[674]: Initial clock synchronization to Mon 2023-06-19 19:53:36.187527 MSK.
Jun 19 19:53:36 debian systemd[1]: systemd-fsckd.service: Deactivated successfully.
Jun 19 19:53:39 debian gnome-keyring-daemon[1231]: asked to register item /org/freedesktop/secrets/collection/login/2, but it's already registered
Jun 19 19:53:39 debian gnome-keyring-d[1231]: asked to register item /org/freedesktop/secrets/collection/login/2, but it's already registered
Jun 19 19:53:39 debian chromium.desktop[1988]: [1988:1988:0619/195339.807354:ERROR:chrome_browser_cloud_management_controller.cc(162)] Cloud management contr>
Jun 19 19:53:44 debian kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC=8c:b8:7e:f8:23:48:74:9d:79:27:d5:78:08:00 SRC=173.194.221.138 DST=192.168.1.66 LEN=125 TOS=0x08>
Jun 19 19:53:52 debian systemd[1]: systemd-hostnamed.service: Deactivated successfully.
Jun 19 19:53:52 debian systemd[1]: systemd-localed.service: Deactivated successfully.
Jun 19 19:53:54 debian kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC=8c:b8:7e:f8:23:48:74:9d:79:27:d5:78:08:00 SRC=64.233.161.84 DST=192.168.1.66 LEN=181 TOS=0x08 P>
Jun 19 19:53:55 debian kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC=8c:b8:7e:f8:23:48:74:9d:79:27:d5:78:86:dd SRC=2806:02f0:5021:c1fd:751f:bc7e:2ab1:e205 DST=2a00:>
Jun 19 19:53:59 debian dbus-daemon[694]: [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service' >
Jun 19 19:53:59 debian systemd[1]: Starting systemd-localed.service - Locale Service...
Jun 19 19:53:59 debian dbus-daemon[694]: [system] Successfully activated service 'org.freedesktop.locale1'
Jun 19 19:53:59 debian systemd[1]: Started systemd-localed.service - Locale Service.
Jun 19 19:54:00 debian PackageKit[1332]: resolve transaction /1164_deddcceb from uid 1000 finished with success after 170ms
Jun 19 19:54:00 debian PackageKit[1332]: search-file transaction /1165_beeaeeab from uid 1000 finished with success after 550ms
Jun 19 19:54:01 debian PackageKit[1332]: search-file transaction /1170_cabaeacd from uid 1000 finished with success after 210ms
Jun 19 19:54:01 debian PackageKit[1332]: search-file transaction /1171_bccedeee from uid 1000 finished with success after 222ms
Jun 19 19:54:02 debian kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC=8c:b8:7e:f8:23:48:74:9d:79:27:d5:78:08:00 SRC=64.233.161.84 DST=192.168.1.66 LEN=181 TOS=0x08 P>

Jun 19 19:54:08 debian PackageKit[1332]: search-file transaction /1200_cedadcde from uid 1000 finished with success after 204ms
Jun 19 19:54:08 debian PackageKit[1332]: search-file transaction /1201_acbebbce from uid 1000 finished with success after 206ms
Jun 19 19:54:08 debian PackageKit[1332]: search-file transaction /1202_ddbcabab from uid 1000 finished with success after 206ms
Jun 19 19:54:08 debian PackageKit[1332]: search-file transaction /1203_aabcecbb from uid 1000 finished with success after 206ms
Jun 19 19:54:09 debian PackageKit[1332]: get-updates transaction /1204_bacdcccc from uid 1000 finished with success after 221ms
Jun 19 19:54:09 debian kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC=01:00:5e:00:00:01:74:9d:79:27:d5:78:08:00 SRC=192.168.1.254 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=>
Jun 19 19:54:13 debian kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC=8c:b8:7e:f8:23:48:74:9d:79:27:d5:78:08:00 SRC=173.194.221.138 DST=192.168.1.66 LEN=181 TOS=0x08>
Jun 19 19:54:14 debian kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC=8c:b8:7e:f8:23:48:74:9d:79:27:d5:78:08:00 SRC=173.194.177.100 DST=192.168.1.66 LEN=52 TOS=0x08 >
Jun 19 19:54:14 debian kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC=8c:b8:7e:f8:23:48:74:9d:79:27:d5:78:08:00 SRC=173.194.177.100 
Jun 19 19:54:16 debian kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC=8c:b8:7e:f8:23:48:74:9d:79:27:d5:78:08:00 SRC=64.233.161.84 DST=192.168.1.66 LEN=181 TOS=0x08 P>
Jun 19 19:54:18 debian kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC=8c:b8:7e:f8:23:48:74:9d:79:27:d5:78:08:00 SRC=173.194.177.100 DST=192.168.1.66 LEN=52 TOS=0x08 >
Jun 19 19:54:22 debian dbus-daemon[946]: [session uid=1000 pid=946] Activating via systemd: service name='org.gtk.vfs.Metadata' unit='gvfs-metadata.service' >
Jun 19 19:54:22 debian systemd[923]: Starting gvfs-metadata.service - Virtual filesystem metadata service...
Jun 19 19:54:22 debian dbus-daemon[946]: [session uid=1000 pid=946] Successfully activated service 'org.gtk.vfs.Metadata'
Jun 19 19:54:22 debian systemd[923]: Started gvfs-metadata.service - Virtual filesystem metadata service.
Jun 19 19:54:22 debian geoclue[1320]: Service not used for 60 seconds. Shutting down..
Jun 19 19:54:22 debian systemd[1]: geoclue.service: Deactivated successfully.
Jun 19 19:54:28 debian kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC=8c:b8:7e:f8:23:48:74:9d:79:27:d5:78:86:dd SRC=2001:b011:3814:7d7e:246b:9bcc:a34f:2422 DST=2a00:>
Jun 19 19:54:28 debian kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC=8c:b8:7e:f8:23:48:74:9d:79:27:d5:78:08:00 SRC=173.194.177.100 DST=192.168.1.66 LEN=52 TOS=0x08 >
Jun 19 19:54:29 debian systemd[1]: systemd-localed.service: Deactivated successfully.
Jun 19 19:54:31 debian kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC=8c:b8:7e:f8:23:48:74:9d:79:27:d5:78:08:00 SRC=192.168.1.254 DST=192.168.1.66 LEN=341 TOS=0x00 P>
Jun 19 19:54:31 debian chromium.desktop[2034]: [2034:2034:0619/195431.618565:ERROR:context_group.cc(146)] ContextResult::kFatalFailure: WebGL1 blocklisted
Jun 19 19:54:31 debian kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC=8c:b8:7e:f8:23:48:74:9d:79:27:d5:78:86:dd SRC=2001:b011:7003:39c6:e112:59bd:1b61:c1bf DST=2a00:>
Jun 19 19:54:38 debian chromium.desktop[2034]: [2034:2034:0619/195438.537390:ERROR:context_group.cc(146)] ContextResult::kFatalFailure: WebGL1 blocklisted
Jun 19 19:54:42 debian kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC=8c:b8:7e:f8:23:48:74:9d:79:27:d5:78:08:00 SRC=173.194.221.138 DST=192.168.1.66 LEN=181 TOS=0x08>
Jun 19 19:54:49 debian kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC=8c:b8:7e:f8:23:48:74:9d:79:27:d5:78:08:00 SRC=192.168.1.254 DST=192.168.1.66 LEN=341 TOS=0x00 P>
Jun 19 19:56:08 debian kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC=8c:b8:7e:f8:23:48:74:9d:79:27:d5:78:08:00 SRC=89.178.18.125 DST=192.168.1.66 LEN=61 TOS=0x08 PR>
Jun 19 19:56:10 debian kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC=8c:b8:7e:f8:23:48:74:9d:79:27:d5:78:08:00 SRC=89.178.18.125 DST=192.168.1.66 LEN=61 TOS=0x08 PR>
Jun 19 19:56:12 debian chromium.desktop[2034]: [2034:2034:0619/195612.584305:ERROR:context_group.cc(146)] ContextResult::kFatalFailure: WebGL1 blocklisted
Jun 19 19:56:13 debian gnome-shell[1237]: Can't update stage views actor <unnamed>[<MetaWindowActorX11>:0x557a92bed1c0] is on because it needs an allocation.
Jun 19 19:56:13 debian gnome-shell[1237]: Can't update stage views actor <unnamed>[<MetaSurfaceActorX11>:0x557a944e2bc0] is on because it needs an allocation.
Jun 19 19:56:13 debian gnome-shell[1237]: Can't update stage views actor <unnamed>[<MetaWindowActorX11>:0x557a92bed1c0] is on because it needs an allocation.
Jun 19 19:56:13 debian gnome-shell[1237]: Can't update stage views actor <unnamed>[<MetaSurfaceActorX11>:0x557a944e2bc0] is on because it needs an allocation.
Jun 19 19:56:13 debian gnome-shell[1237]: Can't update stage views actor <unnamed>[<MetaWindowActorX11>:0x557a92bed1c0] is on because it needs an allocation.
Jun 19 19:56:13 debian gnome-shell[1237]: Can't update stage views actor <unnamed>[<MetaSurfaceActorX11>:0x557a944e2bc0] is on because it needs an allocation.
Jun 19 19:56:13 debian gnome-shell[1237]: Can't update stage views actor <unnamed>[<MetaWindowActorX11>:0x557a92bed1c0] is on because it needs an allocation.
Jun 19 19:56:13 debian gnome-shell[1237]: Can't update stage views actor <unnamed>[<MetaSurfaceActorX11>:0x557a944e2bc0] is on because it needs an allocation.
Jun 19 19:56:14 debian kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC=8c:b8:7e:f8:23:48:74:9d:79:27:d5:78:86:dd SRC=2404:4402:3a14:7b00:ff18:5a4e:cfdb:7809 DST=2a00:>
Jun 19 19:56:23 debian dbus-daemon[946]: [session uid=1000 pid=946] Activating via systemd: service name='org.freedesktop.Flatpak' unit='flatpak-session-help>
Jun 19 19:56:23 debian systemd[923]: Starting flatpak-session-helper.service - flatpak session helper...
Jun 19 19:56:23 debian dbus-daemon[946]: [session uid=1000 pid=946] Successfully activated service 'org.freedesktop.Flatpak'
Jun 19 19:56:23 debian systemd[923]: Started flatpak-session-helper.service - flatpak session helper.
Jun 19 19:56:23 debian systemd[923]: Started app-flatpak-org.telegram.desktop-2462.scope.
Jun 19 19:56:23 debian telegram-deskto[2482]: Failed to load module "canberra-gtk-module"
Jun 19 19:56:23 debian telegram-deskto[2482]: Failed to load module "canberra-gtk-module"
Jun 19 19:56:24 debian org.telegram.desktop.desktop[2482]: QPainter::begin: Paint device returned engine == 0, type: 2
Jun 19 19:56:24 debian org.telegram.desktop.desktop[2482]: QWidget::render: Cannot render with an inactive painter
Jun 19 19:56:25 debian org.telegram.desktop.desktop[2482]: qt.svg: Error while inflating gzip file: SVG format check failed
Jun 19 19:56:25 debian org.telegram.desktop.desktop[2482]: qt.svg: Error while inflating gzip file: SVG format check failed
Jun 19 19:56:25 debian org.telegram.desktop.desktop[2482]: qt.svg: Error while inflating gzip file: SVG format check failed
Jun 19 19:56:27 debian org.telegram.desktop.desktop[2482]: qt.svg: Error while inflating gzip file: SVG format check failed
Jun 19 19:56:27 debian org.telegram.desktop.desktop[2482]: qt.svg: Error while inflating gzip file: SVG format check failed
Jun 19 19:56:27 debian org.telegram.desktop.desktop[2482]: qt.svg: Error while inflating gzip file: SVG format check failed
Jun 19 19:56:27 debian org.telegram.desktop.desktop[2482]: qt.svg: Error while inflating gzip file: SVG format check failed
Jun 19 19:56:27 debian org.telegram.desktop.desktop[2482]: qt.svg: Error while inflating gzip file: SVG format check failed
Jun 19 19:56:27 debian org.telegram.desktop.desktop[2482]: qt.gui.imageio.jpeg: Corrupt JPEG data: premature end of data segment
Jun 19 19:56:27 debian org.telegram.desktop.desktop[2482]: qt.gui.imageio.jpeg: Corrupt JPEG data: premature end of data segment
Jun 19 19:56:28 debian telegram-deskto[2482]: Theme parsing error: <data>:1:0: Expected a valid selector
Jun 19 19:56:33 debian kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC=8c:b8:7e:f8:23:48:74:9d:79:27:d5:78:86:dd SRC=2409:8a00:79a2:9e30:19e5:7cd8:fe54:f096 DST=2a00:>
Jun 19 19:56:45 debian kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC=8c:b8:7e:f8:23:48:74:9d:79:27:d5:78:86:dd SRC=2409:8a00:79a2:9e30:19e5:7cd8:fe54:f096 DST=2a00:>
Jun 19 19:56:57 debian org.gnome.Shell.desktop[1237]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x3e00009 specified for 0x3e00046.
Jun 19 19:57:05 debian org.telegram.desktop.desktop[2482]: qt.svg: Error while inflating gzip file: SVG format check failed
Jun 19 19:57:05 debian org.telegram.desktop.desktop[2482]: [libvpx-vp9 @ 0x7f937e669400] v1.12.0
Jun 19 19:57:05 debian org.telegram.desktop.desktop[2482]: [libvpx-vp9 @ 0x7f9378c50400] v1.12.0
Jun 19 19:57:05 debian org.telegram.desktop.desktop[2482]: [libvpx-vp9 @ 0x7f937e669400] v1.12.0
Jun 19 19:57:05 debian org.telegram.desktop.desktop[2482]: [libvpx-vp9 @ 0x7f9378c50400] v1.12.0
Jun 19 19:57:11 debian kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC=8c:b8:7e:f8:23:48:74:9d:79:27:d5:78:86:dd SRC=2a02:2f07:4707:1300:9a42:d835:3c49:c938 DST=2a00:>
Jun 19 19:57:22 debian org.gnome.Shell.desktop[1237]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x3e00009 specified for 0x3e0004c.
Jun 19 19:57:32 debian kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC=8c:b8:7e:f8:23:48:74:9d:79:27:d5:78:86:dd SRC=2600:1f16:01a1:fc00:36fd:3d5c:cbd1:0287 DST=2a00:>
Jun 19 19:57:41 debian kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC=8c:b8:7e:f8:23:48:74:9d:79:27:d5:78:08:00 SRC=89.178.18.125 DST=192.168.1.66 LEN=95 TOS=0x08 PR>
Jun 19 19:57:48 debian kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC=8c:b8:7e:f8:23:48:74:9d:79:27:d5:78:08:00 SRC=89.178.18.125 DST=192.168.1.66 LEN=61 TOS=0x08 PR>
Jun 19 19:57:51 debian kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC=8c:b8:7e:f8:23:48:74:9d:79:27:d5:78:08:00 SRC=89.178.18.125 DST=192.168.1.66 LEN=61 TOS=0x08 PR>
Jun 19 19:57:57 debian kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC=8c:b8:7e:f8:23:48:74:9d:79:27:d5:78:86:dd SRC=2402:0800:63ad:cbaa:0000:0000:0000:0001 DST=2a00:>
Jun 19 19:58:06 debian gnome-shell[1237]: Object .Gjs_ui_messageTray_Notification (0x557a930a8d60), has been already disposed — impossible to emit any signal>
Jun 19 19:58:06 debian org.gnome.Shell.desktop[1237]: == Stack trace for context 0x557a92c11170 ==
Jun 19 19:58:06 debian org.gnome.Shell.desktop[1237]: #0   557a949507f8 i   resource:///org/gnome/shell/ui/messageTray.js:493 (1da2fd121a10 @ 69)
Jun 19 19:58:06 debian org.gnome.Shell.desktop[1237]: #1   557a94950750 i   resource:///org/gnome/shell/ui/messageTray.js:489 (1da2fd1219c0 @ 56)
Jun 19 19:58:06 debian org.gnome.Shell.desktop[1237]: #2   557a949506c8 i   resource:///org/gnome/shell/ui/calendar.js:796 (1da2fd128ba0 @ 22)
Jun 19 19:58:06 debian org.gnome.Shell.desktop[1237]: == Stack trace for context 0x557a92c11170 ==
Jun 19 19:58:06 debian org.gnome.Shell.desktop[1237]: #0   557a949507f8 i   resource:///org/gnome/shell/ui/messageTray.js:494 (1da2fd121a10 @ 84)
Jun 19 19:58:06 debian org.gnome.Shell.desktop[1237]: #1   557a94950750 i   resource:///org/gnome/shell/ui/messageTray.js:489 (1da2fd1219c0 @ 56)
Jun 19 19:58:06 debian org.gnome.Shell.desktop[1237]: #2   557a949506c8 i   resource:///org/gnome/shell/ui/calendar.js:796 (1da2fd128ba0 @ 22)
Jun 19 19:58:06 debian gnome-shell[1237]: Object .Gjs_ui_messageTray_Notification (0x557a930a8d60), has been already disposed — impossible to access it. This>
Jun 19 19:58:15 debian kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC=8c:b8:7e:f8:23:48:74:9d:79:27:d5:78:86:dd SRC=2a03:1b20:0003:f011:0000:0000:0000:a01e DST=2a00:>
Jun 19 19:58:19 debian kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC= SRC=192.168.1.66 DST=239.192.152.143 LEN=165 TOS=0x00 PREC=0x00 TTL=32 ID=58474 DF PROTO=UDP S>
Jun 19 19:58:19 debian kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC=01:00:5e:00:00:01:74:9d:79:27:d5:78:08:00 SRC=192.168.1.254 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=>
Jun 19 19:58:21 debian kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC= SRC=192.168.1.66 DST=239.192.152.143 LEN=165 TOS=0x00 PREC=0x00 TTL=32 ID=58915 DF PROTO=UDP S>
 IN=wlp3s0 OUT= MAC=8c:b8:7e:f8:23:48:74:9d:79:27:d5:78:08:00 SRC=67.193.185.134 DST=192.168.1.66 LEN=131 TOS=0x08 >
Jun 19 20:00:49 debian kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC= SRC=192.168.1.66 DST=239.192.152.143 LEN=165 TOS=0x00 PREC=0x00 TTL=32 ID=64895 DF PROTO=UDP S>
Jun 19 20:00:49 debian kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC= SRC=2a00:1370:81a2:1cad:a777:749d:26bd:332d DST=ff15:0000:0000:0000:0000:0000:efc0:988f LEN=18>
Jun 19 20:00:51 debian kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC= SRC=192.168.1.66 DST=239.192.152.143 LEN=165 TOS=0x00 PREC=0x00 TTL=32 ID=64930 DF PROTO=UDP S>
Jun 19 20:00:55 debian kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC= SRC=192.168.1.66 DST=239.192.152.143 LEN=165 TOS=0x00 PREC=0x00 TTL=32 ID=339 DF PROTO=UDP SPT>
Jun 19 20:01:05 debian kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC=8c:b8:7e:f8:23:48:74:9d:79:27:d5:78:86:dd SRC=2a03:d000:8487:ee40:bd38:67ce:02f4:3966 DST=2a00:>
Jun 19 20:02:09 debian epiphany[2726]: Failed to scan extensions directory: Error opening directory '/home/ja/.local/share/epiphany/web_extensions': No such >
Jun 19 20:02:10 debian xdg-desktop-por[1188]: Realtime error: Could not map pid: Could not determine pid namespace: Could not find instance-id in process's />
Jun 19 20:02:10 debian xdg-desktop-por[1188]: Realtime error: Could not map pid: Could not determine pid namespace: Could not find instance-id in process's />
Jun 19 20:02:21 debian kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC=8c:b8:7e:f8:23:48:74:9d:79:27:d5:78:86:dd SRC=2401:4900:1c09:ed89:0d52:36ec:80e8:69ba DST=2a00:>
Jun 19 20:02:21 debian kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC=8c:b8:7e:f8:23:48:74:9d:79:27:d5:78:86:dd SRC=2409:8a00:79a2:9e30:19e5:7cd8:fe54:f096 DST=2a00:>
Jun 19 20:02:26 debian kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC=8c:b8:7e:f8:23:48:74:9d:79:27:d5:78:86:dd SRC=2a00:23c8:5d95:5b01:c695:00ff:fe78:edf9 DST=2a00:>
Jun 19 20:02:26 debian kernel: [UFW BLOCK] IN=wlp3s0 OUT= MAC=8c:b8:7e:f8:23:48:74:9d:79:27:d5:78:08:00 SRC=89.178.18.125 DST=192.168.1.66 LEN=61 TOS=0x08 PR>
Jun 19 20:02:27 debian gnome-shell[1237]: Object St.Button (0x557a94a69a40), has been already disposed — impossible to get any property from it. This might b>
Jun 19 20:02:27 debian org.gnome.Shell.desktop[1237]: == Stack trace for context 0x557a92c11170 ==
Jun 19 20:02:27 debian org.gnome.Shell.desktop[1237]: #0   557a949506c8 i   resource:///org/gnome/shell/ui/windowPreview.js:566 (1da2fd1c43d0 @ 10)
(5ffe0a9c1f0 @ 23)

Jun 19 20:02:27 debian org.gnome.Shell.desktop[1237]: #7   557a949506c8 i   resource:///org/gnome/shell/ui/windowPreview.js:571 (1da2fd1c43d0 @ 105)
Jun 19 20:02:27 debian org.gnome.Shell.desktop[1237]: == Stack trace for context 0x557a92c11170 ==
Jun 19 20:02:27 debian org.gnome.Shell.desktop[1237]: == Stack trace for context 0x557a92c11170 ==
Jun 19 20:02:27 debian org.gnome.Shell.desktop[1237]: #0   7ffcde0c82b0 b   resource:///org/gnome/shell/ui/environment.js:356 (5ffe0a9c150 @ 43)

Jun 19 20:02:27 debian org.gnome.Shell.desktop[1237]: #5   557a949506c8 i   resource:///org/gnome/shell/ui/windowPreview.js:571 (1da2fd1c43d0 @ 105)
Jun 19 20:02:27 debian org.gnome.Shell.desktop[1237]: == Stack trace for context 0x557a92c11170 ==
Jun 19 20:02:27 debian org.gnome.Shell.desktop[1237]: #0   7ffcde0c8190 b   resource:///org/gnome/shell/ui/environment.js:226 (5ffe0a8cbf0 @ 15)
Jun 19 20:02:27 debian org.gnome.Shell.desktop[1237]: #1   7ffcde0c82b0 b   self-hosted:180 (5ffe0a6d420 @ 294)
Jun 19 20:02:27 debian gnome-shell[1237]: Object St.Label (0x557a94b178e0), has been already disposed — impossible to access it. This might be caused by the >
Jun 19 20:02:27 debian org.gnome.Shell.desktop[1237]: #2   7ffcde0c83a0 b   resource:///org/gnome/shell/ui/environment.js:226 (5ffe0a8ca60 @ 607)
Jun 19 20:02:27 debian org.gnome.Shell.desktop[1237]: #3   7ffcde0c8470 b   resource:///org/gnome/shell/ui/environment.js:364 (5ffe0a9c1f0 @ 23)
Jun 19 20:02:27 debian org.gnome.Shell.desktop[1237]: #4   7ffcde0c8530 b   resource:///org/gnome/shell/ui/windowPreview.js:365 (1da2fd1c3d30 @ 108)
Jun 19 20:02:27 debian org.gnome.Shell.desktop[1237]: #5   7ffcde0c85a0 I   self-hosted:164 (2d0df70281f0 @ 272)
Jun 19 20:02:27 debian org.gnome.Shell.desktop[1237]: #6   7ffcde0c8670 b   resource:///org/gnome/shell/ui/windowPreview.js:363 (1da2fd1c3ce0 @ 221)
Jun 19 20:02:27 debian org.gnome.Shell.desktop[1237]: #7   557a949506c8 i   resource:///org/gnome/shell/ui/windowPreview.js:571 (1da2fd1c43d0 @ 105)

Jun 19 20:02:27 debian gnome-shell[1237]: Object St.Label (0x557a94b178e0), has been already disposed — impossible to access it. This might be caused by the >
Jun 19 20:02:27 debian gnome-shell[1237]: Object St.Label (0x557a94b178e0), has been already disposed — impossible to access it. This might be caused by the >

Jun 19 20:02:27 debian gnome-shell[1237]: Object St.Button (0x557a94a69a40), has been already disposed — impossible to access it. This might be caused by the>
Jun 19 20:02:27 debian gnome-shell[1237]: Object St.Button (0x557a94a69a40), has been already disposed — impossible to set any property on it. This might be >
Jun 19 20:02:27 debian gnome-shell[1237]: Object St.Button (0x557a94a69a40), has been already disposed — impossible to access it. This might be caused by the>
Jun 19 20:02:27 debian gnome-shell[1237]: Object St.Button (0x557a94a69a40), has been already disposed — impossible to access it. This might be caused by the>
Jun 19 20:02:27 debian gnome-shell[1237]: Object St.Button (0x557a94a69a40), has been already disposed — impossible to access it. This might be caused by the>
Jun 19 20:02:27 debian gnome-shell[1237]: Object .Gjs_ui_windowPreview_WindowPreview (0x557a94bc4fa0), has been already disposed — impossible to get any prop>
Jun 19 20:02:27 debian gnome-shell[1237]: JS ERROR: TypeError: this.window_container is null
                                          hideOverlay@resource:///org/gnome/shell/ui/windowPreview.js:373:9
                                          vfunc_leave_event/this._idleHideOverlayId<@resource:///org/gnome/shell/ui/windowPreview.js:571:26
There was a lot of

debian org.telegram.desktop.desktop[2482]: qt.svg: Error while inflating gzip file: SVG format check failed

I had to delete A LOT of lines for a post to be readable

---
As i have started to have such freezes while using MX Linux, after i switched to nouveau, i think, that all this must be somehow connected to NVIDIA (god damn) driver
Top
Aki
Global Moderator
Global Moderator
Posts: 2979
Joined: 2014-07-20 18:12
Location: Europe
Has thanked: 75 times
Been thanked: 407 times

Re: System freeze in Debian 12

#22 Post by Aki »

Hello,

They seem to be all javascript errors

Have you installed gnome-shell extensions ?

Do you think that this bug report [1] resembles what is happening to you ?

When the computer is crippled:
  • a) can you try to activate a virtual console (CTRL+ALT+F3) ?
  • b) can you try to connect to the crippled computer via ssh (ssh package must be already installed) ? if yes:
    • b.1) can you dump systemd journal ?
    • b.2) can you obtain the output of

      Code: Select all

      ps aux
What are the foreign packages you have installed ? You can check with [2]:

Code: Select all

apt list '?narrow(?installed, ?not(?origin(Debian)))'
---
[1] https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6023
[2] https://www.debian.org/releases/bookwor ... n-packages
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄⠀
Top
User avatar
alienspy
Posts: 159
Joined: 2023-02-12 15:37
Has thanked: 97 times
Been thanked: 5 times

Re: System freeze in Debian 12

#23 Post by alienspy »

Aki wrote: ↑2023-06-19 17:41 They seem to be all javascript errors
Telegram errors or others also? I heard that Telegram app is rather buggy and snap (yeah yeah) version is better.
Have you installed gnome-shell extensions ?
I use only preinstalled ones.
Do you think that this bug report [1] resembles what is happening to you ?
No, not really. I am on Xorg, i don't use kb shortcuts, and freezes happen not after workspace switching.

But now i am starting to think if the problem can be in Gnome also..? But i had these freezes in MX too, there was older version of GNOME.
When the computer is crippled:
  • a) can you try to activate a virtual console (CTRL+ALT+F3) ?
I will try, didn't come to mind. Or i forgot about the result.
  • b) can you try to connect to the crippled computer via ssh (ssh package must be already installed) ? if yes:
Unfortunately no, not in the nearest week or two.
What are the foreign packages you have installed ?
Only one and i used it like once.

Code: Select all

root@debian:~# apt list '?narrow(?installed, ?not(?origin(Debian)))'
Listing... Done
lantern/now 7.4.0 amd64 [installed,local]
Top
User avatar
alienspy
Posts: 159
Joined: 2023-02-12 15:37
Has thanked: 97 times
Been thanked: 5 times

Re: System freeze in Debian 12

#24 Post by alienspy »

I had a freeze again. Now i am almost sure that the thing in THIS case is Telegram App.

Journal is overloaded with these lines

Code: Select all

Jun 22 14:04:29 debian org.telegram.desktop.desktop[1997]: qt.svg: Error while inflating gzip file: SVG format check failed
Jun 22 14:04:29 debian org.telegram.desktop.desktop[1997]: qt.svg: Error while inflating gzip file: SVG format check failed
Jun 22 14:04:29 debian org.telegram.desktop.desktop[1997]: qt.svg: Error while inflating gzip file: SVG format check failed
Jun 22 14:04:30 debian org.telegram.desktop.desktop[1997]: qt.gui.imageio.jpeg: Corrupt JPEG data: premature end of data segment
and

Code: Select all

Jun 22 14:04:39 debian kernel: pcieport 0000:00:1b.0: AER: Corrected error received: 0000:02:00.0
Jun 22 14:04:39 debian kernel: nvme 0000:02:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Jun 22 14:04:39 debian kernel: nvme 0000:02:00.0:   device [c0a9:2263] error status/mask=00000001/0000e000
Jun 22 14:04:39 debian kernel: nvme 0000:02:00.0:    [ 0] RxErr                  (First)
But what is the problem with nvme..?

As for other possible candidates for the problem: nvidia-driver and Firefox, i have installed 470-nvidia driver and it works, and switched from Firefox from Chromium, will see how it will behave.

UPD. If nothing NEW will happen, i will close this topic in the nearest days. As my problems are probably caused by 1) nvidia-driver 2) firefox (?) 3) Telegram 4) NVME (?).

UPD2. SEE THIS POST
Top
pierreleon
Posts: 1
Joined: 2023-07-13 22:57

Re: System freeze in Debian 12

#25 Post by pierreleon »

alienspy wrote: ↑2023-06-15 17:22 Yes, i am. Is it that bad? I tried to install proprietary driver, but failed. I will make a different topic for that.
I'd like to see this different topic, I can't install nvidia-driver either ... Could you provide us with the link to this new topic plz ?
Top
User avatar
alienspy
Posts: 159
Joined: 2023-02-12 15:37
Has thanked: 97 times
Been thanked: 5 times

Re: System freeze in Debian 12

#26 Post by alienspy »

pierreleon wrote: ↑2023-07-13 23:02
alienspy wrote: ↑2023-06-15 17:22 Yes, i am. Is it that bad? I tried to install proprietary driver, but failed. I will make a different topic for that.
I'd like to see this different topic, I can't install nvidia-driver either ... Could you provide us with the link to this new topic plz ?
viewtopic.php?t=154925&start=20
Top
User avatar
eor2004
Posts: 251
Joined: 2013-10-01 22:49
Location: Puerto Rico
Has thanked: 9 times
Been thanked: 5 times

Re: System freeze in Debian 12

#27 Post by eor2004 »

I have recently upgraded to debian 12 x64 gnome and my laptop, an HP EliteBook 8540p is suffering the same issue as the OP, constant freezes, even when I had debian 11 I suffered from the same issue although it was ocuring rarely, not as many times as of Now with debian 12, my pc does have an Nvidia NVA5 graphics card (NVIDIA Corporation GT216M NVS 5100M rev. a2) and yes, using the Open Source Drivers with Xorg, it freezed using Wayland too, so I don't think the issue is with Xorg or Wayland, I think it has to do with something else, both the cpu and gpu have almost new Artic MX4 thermal compound applied, so I don't think is overheat & the cpu fan is working fine, maybe is one of the Ram memory module went bad or the gold contacts are dirty? Hard Drive is 100% Health BTW...

P.S. @ OP, can you tell what laptop or PC brand and model you're having this issue with?
Debian 12 Gnome on a MSI H61M-P25 (B3) PC & on a Dell Latitude E6410 & HP EliteBook 8540p Laptops.
LMDE 6 on a Panasonic ToughBook CF-C1 Laptop.
Bodhi Linux 7 on a HP Compaq DC5750 Small Form Factor PC.
Windows 11 on a Intel DH55TC PC.
Top
User avatar
alienspy
Posts: 159
Joined: 2023-02-12 15:37
Has thanked: 97 times
Been thanked: 5 times

Re: System freeze in Debian 12

#28 Post by alienspy »

eor2004 wrote: ↑2024-02-23 15:59 P.S. @ OP, can you tell what laptop or PC brand and model you're having this issue with?
It is a second-hand desktop PC.

Code: Select all

System:
  Host: debian Kernel: 6.1.0-9-amd64 arch: x86_64 bits: 64 Desktop: GNOME
    v: 43.4 Distro: Debian GNU/Linux 12 (bookworm)
Machine:
  Type: Desktop System: Gigabyte product: B360 HD3 v: N/A
    serial: <superuser required>
  Mobo: Gigabyte model: B360HD3 v: x.x serial: <superuser required>
    UEFI: American Megatrends v: F11 date: 09/17/2018
CPU:
  Info: 6-core Intel Core i5-8400 [MCP] speed (MHz): avg: 800
    min/max: 800/4000
Graphics:
  Device-1: NVIDIA GP107 [GeForce GTX 1050] driver: nouveau v: kernel
  Display: wayland server: X.Org v: 1.22.1.9 with: Xwayland v: 22.1.9
    compositor: gnome-shell driver: X: loaded: nvidia
    unloaded: fbdev,modesetting,nouveau,vesa dri: nouveau gpu: nouveau
    resolution: 1920x1080~75Hz
  API: OpenGL v: 4.3 Mesa 22.3.6 renderer: NV137
Network:
  Device-1: Intel Wi-Fi 6 AX210/AX211/AX411 160MHz driver: iwlwifi
  Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    driver: r8169
Drives:
  Local Storage: total: 1.64 TiB used: 40.67 GiB (2.4%)
Info:
  Processes: 271 Uptime: 29m Memory: 15.55 GiB used: 3.01 GiB (19.4%)
  Shell: Bash inxi: 3.3.26
In my case solution was - https://forums.debian.net/viewtopic.ph ... 48#p781848

Have you checked journalctl and dmesg commands in terminal?
Top
User avatar
eor2004
Posts: 251
Joined: 2013-10-01 22:49
Location: Puerto Rico
Has thanked: 9 times
Been thanked: 5 times

Re: System freeze in Debian 12

#29 Post by eor2004 »

Hi alienspy, thanks for your reply, the thing that baffles me is that I have Debian 12 on my main PC too, that is a desktop with an MSI Mobo with Intel graphics, is the same operative system and desktop environment on both, the same packages installed and that PC doesn't have this kind of issue, the common thing is that your hardware and mine has the Nvidia graphics, although they aren't the same model, but the same brand, so I think the issue must be with the Nvidia open source drivers, I'm pretty sure of that, when my laptop froze I had a music video running on Brave browser and the music was playing normally as nothing has happened, but I could do nothing on it since it was frozen, only thing I could do was keep pressing the power button until it turned off and then restart again, so the video or graphics system crashed, but everything else was working? will look at your recommendations and post again if I deem it necesary!
Debian 12 Gnome on a MSI H61M-P25 (B3) PC & on a Dell Latitude E6410 & HP EliteBook 8540p Laptops.
LMDE 6 on a Panasonic ToughBook CF-C1 Laptop.
Bodhi Linux 7 on a HP Compaq DC5750 Small Form Factor PC.
Windows 11 on a Intel DH55TC PC.
Top
jwn
Posts: 2
Joined: 2024-01-29 11:16

Re: System freeze in Debian 12

#30 Post by jwn »

Hi! I'd like to dig up that thread because I'm trying to battle this freeze issues for a while now with no luck.

The symptoms are the same as described above: complete freeze, no action possible other than hard reset, no communication (can't ssh into the system).

This has been happening since Debian 11, that is why I still use Debian 10 to work, but the security updates stop at June, so something has to be done. I'm certain though that this is NOT a hardware nor Nvidia related problem.

I observe the same behaviour on two different laptops:
1. Thinkpad T61p T9500 core2duo 4GB ram with Intel graphics
2. Thinkpad P52 i7-8850H 64GB ram with GP107GLM [Quadro P1000 Mobile] (rev ff) graphics

Both running Debian 12 and additionally #2 laptop still has Debian 10 on a separate partition. Both systems experience these random freezes. I tried #2 with nvidia, nouveau drivers and blacklisting both and using cpu graphics, so this is not nvidia related. This happens both on Xorg and Wayland sessions. I've tested memory numerous times on both laptops. I'm convinced that this is not a hardware issue because the Debian 10 system is running flawlessly. I sometimes do some data processing for work an I leave Debian 10 running on almost full cpu load for a week or so, with no issues.

On my own I can't find any errors in logs (some are probably overwritten on restart). I will gladly paste any logs you wish but please tell me where to look, because I'm all out of ideas at this point.

Thanks
Top
User avatar
sunrat
Administrator
Administrator
Posts: 6511
Joined: 2006-08-29 09:12
Location: Melbourne, Australia
Has thanked: 119 times
Been thanked: 489 times

Re: System freeze in Debian 12

#31 Post by sunrat »

@jwn as your system and hardware will be different from OP, you should treat this as a different issue and open your own topic.
“ computer users can be divided into 2 categories:
Those who have lost data
...and those who have not lost data YET ” Remember to BACKUP!
Top
jwn
Posts: 2
Joined: 2024-01-29 11:16

Re: System freeze in Debian 12

#32 Post by jwn »

@sunrat The hardware is in fact different, but the system is the same (Debian 12). I believe this issue is related, and I did not want to start a new topic about the same issue. In the last couple of years there have been numerous reports on the Internet about such freezes, not exclusively in Debian but also in Arch and others. Sadly, no solution yet.
Top
User avatar
sunrat
Administrator
Administrator
Posts: 6511
Joined: 2006-08-29 09:12
Location: Melbourne, Australia
Has thanked: 119 times
Been thanked: 489 times

Re: System freeze in Debian 12

#33 Post by sunrat »

jwn wrote: ↑2024-03-09 10:31 @sunrat The hardware is in fact different, but the system is the same (Debian 12). I believe this issue is related, and I did not want to start a new topic about the same issue. In the last couple of years there have been numerous reports on the Internet about such freezes, not exclusively in Debian but also in Arch and others. Sadly, no solution yet.
I run Debian 12 too and don't have freezes. It's usually hardware or a combination of hardware and software.
Start a new topic for your issue please. You will need to show complete hardware specs and logs from when the freezes occur.
“ computer users can be divided into 2 categories:
Those who have lost data
...and those who have not lost data YET ” Remember to BACKUP!
Top
Post Reply

Return to “General Questions”