[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Gnome shell freezes randomly



I get the same thing, every now and then default gnome desktop
freezes. For me the mouse also freezes. About 20 minutes ago I
discovered when I physically disconnected my tethered mobile phone,
the desktop unfroze.

I've also achieved the unfreeze with disconnecting my laptop from the
thunderbolt docking station, then reconnecting it. This requires much
more substantial delays than just disconnecting/reconnecting the
mobile phone. The dock is obviously more complex and attaches to 2
external monitors.

I've also experienced the freeze at the login screen.

I do not know how we can further test this.

(I also get the whole desktop session die often when a video (using
mpv) ends - see other thread. For me at the moment it appears that
gnome/wayland is not yet sufficiently stable for my hardware
configuration (no gpu, just an Intel cpu, and the dock).)

On Wed, Nov 29, 2023 at 6:31 AM Marlin <marlinpetre@gmail.com> wrote:
>
> I have been experiencing random lockups of gnome-shell ever since I did
> a new install of bookworm sometime in July. When I say lockup/freeze, I
> mean that the mouse cursor still moves on the display, but I can not
> click anything. The rest of the system is not frozen. I can ssh into it.
> Yesterday morning I found gnome frozen with the clock showing 4:21 AM. I
> could not find anything in the logs that correlated to that time, but it
> may be that I am not searching at the right spot. I was using journalctl.
>
>
>
> Below are some commands I ran while gnome was frozen.
>
> ps shows normal system usage while top shows the cpu load at 100%. Maybe
> that is just one core?
>
> marlin@RRE:~$ ps -aux | grep gnome-shell
> marlin      3289  4.8  2.9 4977044 971368 ?      Ssl  Nov24 207:00
> /usr/bin/gnome-shell
> marlin      3330  0.0  0.0 581188 17496 ?        Sl   Nov24   0:00
> /usr/libexec/gnome-shell-calendar-server
> marlin      3404  0.0  0.0 2850056 28740 ?       Sl   Nov24   0:00
> /usr/bin/gjs /usr/share/gnome-shell/org.gnome.Shell.Notifications
> marlin      3587  0.0  0.0 2661648 27468 ?       Sl   Nov24   0:00
> /usr/bin/gjs /usr/share/gnome-shell/org.gnome.ScreenSaver
> marlin    434729  0.0  0.0   6332  2116 pts/0    S+   06:58   0:00 grep
> gnome-shell
> marlin@RRE:~$
>
> marlin@RRE:~$ top
> top - 07:01:32 up 2 days, 22:45,  2 users,  load average: 1.19, 1.24, 1.25
> Tasks: 413 total,   1 running, 412 sleeping,   0 stopped,   0 zombie
> %Cpu(s):  6.3 us,  1.8 sy,  0.2 ni, 91.5 id,  0.0 wa,  0.0 hi,  0.2 si,
> 0.0 st
> MiB Mem :  31903.9 total,    365.4 free,  19651.1 used,  12489.9 buff/cache
> MiB Swap:  38264.0 total,  37913.7 free,    350.2 used.  12252.8 avail Mem
>
>        PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM
> TIME+ COMMAND
>       3289 marlin    20   0 4977044 971536 107480 S 100.0   3.0
> 209:54.08 gnome-shell
>
>
>
> marlin@RRE:~$ free
>                   total        used        free      shared  buff/cache
> available
> Mem:        32669588    20130636      366032      142932    12789816
> 12538952
> Swap:       39182332      358656    38823676
> marlin@RRE:~$
>
>
> marlin@RRE:~$ inxi -Gaz
> Graphics:
>      Device-1: NVIDIA GK208B [GeForce GT 710] vendor: Gigabyte driver:
> nvidia v: 470.199.02 non-free:
>        series: 470.xx+ status: legacy-active (EOL~2023/24) arch: Fermi 2
> code: GF119/GK208
>        process: TSMC 28nm built: 2010-16 pcie: gen: 1 speed: 2.5 GT/s
> lanes: 8 link-max: gen: 2
>        speed: 5 GT/s bus-ID: 01:00.0 chip-ID: 10de:128b class-ID: 0300
>      Display: x11 server: X.org v: 1.21.1.7 with: Xwayland v: 22.1.9
> compositor: gnome-shell
>        v: 43.6 driver: X: loaded: nvidia unloaded:
> fbdev,modesetting,nouveau,vesa alternate: nv
>        gpu: nvidia tty: 120x30
>      API: OpenGL Message: GL data unavailable in console and glxinfo
> missing.
> marlin@RRE:~$
>
> marlin@RRE:~$ uname -a
> Linux RRE 6.1.0-13-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.55-1
> (2023-09-29) x86_64 GNU/Linux
> marlin@RRE:~$
>
> If anyone has any suggestions, I will be glad for them. I know this kind
> of an issue is hard to debug because I do not know how to cause it to
> freeze.
>
> --
> Regards,
> Marlin
> Pennsylvania, United States


Reply to: