OK, I did it.
i didn't wait for the freeze to happen randomly because it may take time, i
tried to open zoom which always causes a freeze, It started only in the
past few days and after a full-upgrade, i use zoom regularly and there was
no problem before the last full-upgrade. its debian testing.
I opened zoom with super key, search for zoom and enter. the computer
freezes immediately.

there was nothing in dmesg or /var/log/messages before the freeze,
this is what was in journalctl and top, i don't know how to tell if there
is something suspicious.

journalctl
Jan 30 00:01:49 xps-debian dbus-daemon[3297]: [session uid=1000 pid=3297]
Activating service name='org.gnome.Settings.SearchProvider' requested by
':1.35' (uid=1000 pid=3523 comm="/usr/bin/gnome-shell")
Jan 30 00:01:49 xps-debian dbus-daemon[3297]: [session uid=1000 pid=3297]
Activating service name='org.gnome.Contacts.SearchProvider' requested by
':1.35' (uid=1000 pid=3523 comm="/usr/bin/gnome-shell")
Jan 30 00:01:49 xps-debian dbus-daemon[3297]: [session uid=1000 pid=3297]
Activating service name='org.gnome.Nautilus' requested by ':1.35' (uid=1000
pid=3523 comm="/usr/bin/gnome-shell")
Jan 30 00:01:49 xps-debian dbus-daemon[3297]: [session uid=1000 pid=3297]
Activating service name='org.gnome.Calculator.SearchProvider' requested by
':1.35' (uid=1000 pid=3523 comm="/usr/bin/gnome-shell")
Jan 30 00:01:49 xps-debian dbus-daemon[3297]: [session uid=1000 pid=3297]
Activating service name='org.gnome.Characters' requested by ':1.35'
(uid=1000 pid=3523 comm="/usr/bin/gnome-shell")
Jan 30 00:01:49 xps-debian dbus-daemon[3297]: [session uid=1000 pid=3297]
Activating service name='org.gnome.clocks' requested by ':1.35' (uid=1000
pid=3523 comm="/usr/bin/gnome-shell")
Jan 30 00:01:49 xps-debian dbus-daemon[3297]: [session uid=1000 pid=3297]
Activating service name='org.gnome.seahorse.Application' requested by
':1.35' (uid=1000 pid=3523 comm="/usr/bin/gnome-shell")
Jan 30 00:01:49 xps-debian dbus-daemon[3297]: [session uid=1000 pid=3297]
Activating via systemd: service name='org.gnome.Terminal'
unit='gnome-terminal-server.service' requested by ':1.35' (uid=1000
pid=3523 comm="/usr/bin/gnome-shell")
Jan 30 00:01:49 xps-debian dbus-daemon[3297]: [session uid=1000 pid=3297]
Successfully activated service 'org.gnome.Settings.SearchProvider'
Jan 30 00:01:49 xps-debian dbus-daemon[3297]: [session uid=1000 pid=3297]
Successfully activated service 'org.gnome.Calculator.SearchProvider'
Jan 30 00:01:49 xps-debian dbus-daemon[3297]: [session uid=1000 pid=3297]
Successfully activated service 'org.gnome.clocks'
Jan 30 00:01:49 xps-debian dbus-daemon[3297]: [session uid=1000 pid=3297]
Successfully activated service 'org.gnome.seahorse.Application'
Jan 30 00:01:49 xps-debian nautilus[9317]: Connecting to
org.freedesktop.Tracker3.Miner.Files
Jan 30 00:01:49 xps-debian systemd[3253]: Starting GNOME Terminal Server...
Jan 30 00:01:49 xps-debian dbus-daemon[3297]: [session uid=1000 pid=3297]
Successfully activated service 'org.gnome.Nautilus'
Jan 30 00:01:49 xps-debian dbus-daemon[3297]: [session uid=1000 pid=3297]
Successfully activated service 'org.gnome.Contacts.SearchProvider'
Jan 30 00:01:49 xps-debian dbus-daemon[3297]: [session uid=1000 pid=3297]
Successfully activated service 'org.gnome.Characters'
Jan 30 00:01:49 xps-debian nautilus[9317]: g_hash_table_foreach: assertion
'hash_table != NULL' failed
Jan 30 00:01:49 xps-debian dbus-daemon[3297]: [session uid=1000 pid=3297]
Activating service name='org.gnome.DiskUtility' requested by ':1.170'
(uid=1000 pid=9317 comm="/usr/bin/nautilus --gapplication-service")
Jan 30 00:01:49 xps-debian dbus-daemon[3297]: [session uid=1000 pid=3297]
Successfully activated service 'org.gnome.DiskUtility'
Jan 30 00:01:49 xps-debian gnome-character[9321]: JS LOG: Characters
Application started
Jan 30 00:01:49 xps-debian dbus-daemon[3297]: [session uid=1000 pid=3297]
Successfully activated service 'org.gnome.Terminal'
Jan 30 00:01:49 xps-debian systemd[3253]: Started GNOME Terminal Server.
Jan 30 00:01:49 xps-debian dbus-daemon[3297]: [session uid=1000 pid=3297]
Activating service name='org.gnome.seahorse.Application' requested by
':1.35' (uid=1000 pid=3523 comm="/usr/bin/gnome-shell")
Jan 30 00:01:49 xps-debian gnome-shell[3523]: Received error from D-Bus
search provider org.gnome.Terminal.desktop: Gio.DBusError:
GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Object does not exist
at path “/org/gnome/Terminal/SearchProvider”
Jan 30 00:01:49 xps-debian dbus-daemon[3297]: [session uid=1000 pid=3297]
Successfully activated service 'org.gnome.seahorse.Application'
Jan 30 00:01:50 xps-debian gnome-shell[3523]: Received error from D-Bus
search provider org.gnome.Terminal.desktop: Gio.DBusError:
GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Object does not exist
at path “/org/gnome/Terminal/SearchProvider”
Jan 30 00:01:50 xps-debian PackageKit[2312]: resolve transaction
/32688_aaecaebb from uid 1000 finished with cancelled after 323ms
Jan 30 00:01:50 xps-debian gnome-software[4034]: internal error: failed,
but no error code: cancelled
Jan 30 00:01:50 xps-debian dbus-daemon[3297]: [session uid=1000 pid=3297]
Activating service name='org.gnome.seahorse.Application' requested by
':1.35' (uid=1000 pid=3523 comm="/usr/bin/gnome-shell")
Jan 30 00:01:50 xps-debian gnome-shell[3523]: Received error from D-Bus
search provider org.gnome.Terminal.desktop: Gio.DBusError:
GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Object does not exist
at path “/org/gnome/Terminal/SearchProvider”
Jan 30 00:01:50 xps-debian dbus-daemon[3297]: [session uid=1000 pid=3297]
Successfully activated service 'org.gnome.seahorse.Application'
Jan 30 00:01:50 xps-debian PackageKit[2312]: resolve transaction
/32689_acdbdcac from uid 1000 finished with cancelled after 311ms
Jan 30 00:01:50 xps-debian gnome-software[4034]: internal error: failed,
but no error code: cancelled
Jan 30 00:01:51 xps-debian PackageKit[2312]: resolve transaction
/32690_beddabed from uid 1000 finished with success after 294ms
Jan 30 00:01:52 xps-debian systemd[3253]: Started Application launched by
gnome-shell.

top
9323 shalom    20   0  389416  37848  28308 R  48.8   0.1   0:01.47
gnome-clocks
   2312 root      20   0  377972  54280  18304 S  30.9   0.1   0:33.72
packagekitd
   3523 shalom    20   0 6970776 620328 446956 S  23.3   0.9   1:14.52
gnome-shell
   5466 shalom    20   0 5289772 709372 225944 S  21.9   1.1   4:27.93
firefox-esr
   9321 shalom    20   0 4616308 183336  94060 S  17.3   0.3   0:00.52
gnome-character
   4034 shalom    20   0  730912  83672  49864 S  13.0   0.1   0:08.00
gnome-software
   9315 shalom    20   0  550888  40832  23944 S  12.6   0.1   0:00.38
gnome-contacts-
   8182 shalom    20   0 2620200 219800  98688 S  11.0   0.3   0:56.39
Isolated Web Co
   9402 shalom    20   0  359068  35996  26500 S  10.6   0.1   0:00.32
gnome-disks
   9326 shalom    20   0  398104  36068  28484 S   8.6   0.1   0:00.26
gnome-terminal-
   6114 shalom    20   0 2517920 183140 102408 S   7.3   0.3   1:21.44
Isolated Web Co
   9317 shalom    20   0  899976  49148  35352 S   6.6   0.1   0:00.20
nautilus
   9313 shalom    20   0  342312  30380  22696 S   3.0   0.0   0:00.09
gnome-control-c
   3297 shalom    20   0   11128   6880   4340 S   2.3   0.0   0:00.67
dbus-daemon
   4050 shalom    20   0  699744  78740  58388 S   2.0   0.1   0:06.61
psensor
   4400 shalom    20   0 1784672 123896  58556 S   2.0   0.2   0:20.43
Xwayland
   3486 shalom    20   0  770772  58212  33768 S   1.7   0.1   0:00.57
goa-daemon
   9319 shalom    20   0  413604  24504  19536 S   1.3   0.0   0:00.04
gnome-calculato
   3404 shalom    39  19  701428  32428  19492 S   1.0   0.0   0:00.57
tracker-miner-f
   3881 shalom    20   0  760680  48000  26792 S   1.0   0.1   0:00.16
evolution-addre
   7480 shalom    20   0 2488348 141428  97648 S   1.0   0.2   0:25.34
Isolated Web Co
   7483 shalom    20   0 2469872 117060  90304 S   1.0   0.2   0:10.56
Isolated Web Co
   7985 root      20   0       0      0      0 I   1.0   0.0   0:02.77
kworker/0:1-rcu_gp
   8242 shalom    20   0 2461252 107204  83560 S   1.0   0.2   0:00.39
Isolated Web Co
     81 root      20   0       0      0      0 S   0.7   0.0   0:03.03
ksoftirqd/13
   3925 shalom    20   0  312436  14300   6872 S   0.7   0.0   0:01.44
ibus-daemon
   4026 shalom    20   0 4493304 523692 291540 S   0.7   0.8   0:06.59
quiterss
   4112 shalom    20   0  784084 120324  87532 S   0.7   0.2   0:10.79
terminator
     15 root      20   0       0      0      0 I   0.3   0.0   0:00.55
rcu_preempt
    103 root      20   0       0      0      0 I   0.3   0.0   0:00.76
kworker/u32:9-i915
    127 root      20   0       0      0      0 I   0.3   0.0   0:03.25
kworker/13:1-events
   1203 message+  20   0   12064   7240   4228 S   0.3   0.0   0:01.36
dbus-daemon
   1211 root      20   0  221760   8296   3440 S   0.3   0.0   0:00.20
rsyslogd

On Sun, Jan 29, 2023 at 8:02 PM <rhkra...@gmail.com> wrote:

> On Sunday, January 29, 2023 01:59:51 AM Shalom Ben-Zvii Kazaz wrote:
> > There is no ssh when its frozen
>
> Hmm, I'm a little confused, and maybe you are, also.
>
> I think the intent of the advice was to log into the frozen laptop from
> another computer / device, using ssh *while the frozen laptop is not
> frozen*.
>
> Further, on that other device, run a command like top or journalctrl -f,
> and
> then wait (or cause) the laptop to freeze.
>
> Then examine top or such on the working computer to look for clues as to
> why
> the frozen laptop has frozen.
>
> (I may be confused. ;-)
>
> --
> rhk
>
> (sig revised 20221206)
>
> If you reply: snip, snip, and snip again; leave attributions; avoid HTML;
> avoid top posting; and keep it "on list".  (Oxford comma (and semi-colon)
> included at no charge.)  If you revise the topic, change the Subject:
> line.
> If you change the topic, start a new thread.
>
> Writing is often meant for others to read and understand (legal documents
> excepted?) -- make it easier for your reader by various means, including
> liberal use of whitespace (short paragraphs, separated by whitespace /
> blank
> lines) and minimal use of (obscure?) jargon, abbreviations, acronyms, and
> references.
>
> If someone has already responded to a question, decide whether any
> response
> you add will be helpful or not ...
>
> A picture is worth a thousand words.  A video (or "audio"): not so much --
> divide by 10 for each minute of video (or audio) or create a transcript
> and
> edit it to 10% of the original.
>
> A speaker who uses ahhs, ums, or such may have a real physical or mental
> disability, or may be showing disrespect for his listeners by not properly
> preparing in advance and thinking before speaking.  (Remember Cicero who
> did
> not have enough time to write a short missive.)  (That speaker might have
> been
> "trained" to do this by being interrupted often if he pauses.)
>
> A radio (or TV) station which broadcasts speakers with high pitched voices
> (or
> very low pitched / gravelly voices) (which older people might not be able
> to
> hear properly) disrespects its listeners.   Likewise if it broadcasts
> extraneous or disturbing sounds (like gunfire or crying), or broadcasts
> speakers using their native language (with or without an overdubbed
> translation).
>
> A person who writes a sig this long probably has issues and disrespects
> (and
> offends) a large number of readers. ;-)
> '
>
>

Reply via email to