Have a bug on Gnome:
Sometimes(about once a day with no special trigger) all pictures(icons in slack, indicators in bar) disappear, apps become unresponsive, overall looks like a severe de bug.
Timeshifting to previous version didn’t help, issue still there. Only reboot helps
Usually I had sublime, slack and chrome opened at the time of issue.
Once sublime window was active and it started spamming incorrect input errors before de crushed
It’s always a good troubleshooting practice with gnome to disable extensions and see if that fixes the problem. What you are describing sounds like a problem with an extension. Especially since the recent move to gnome 40 drastically changed the way extensions work. If the system works fine without extensions running re-enable them and make a note of all the extensions you are running and then turn them all off but one and slowly introduce the extensions back one at a time until you find the culprit.
Since bugs can be present for years, it could very well be that a fix somewhere in your specific situation triggered a failure that made the system hang. Since there is no specific culprit to identify except that is happens in your situation, provide some system logging and your active extensions.
List active extensions: $ gsettings get org.gnome.shell enabled-extensions | tr "," "\n" |tr -d "^ ' [ ] " | sort
errors in the journal from current session: $ journalctl --boot -0 --priority=err
I uninstalled them from gnome extension interface and don’t have related folders in ~/.local/share/gnome-shell/extensions/ or /usr/share/gnome-shell/extensions
It’s still happening even after another stable update.
Problem seems to be deeper then just ui, because it also turns off the internet when it happens.
It’s my working machine and it will take lots of effort to recreate the environment, so any help appreciated.
No idea whatsoever, I was hoping someone would spot something in the journal you posted.
Do you have the output of this command after the problems occur, eg right after, save it somewhere and post it.
Another way would be to open a terminal and run journalctl --follow --priority=err and watch what is happening when the behavior occurs.
Could you add info about your hardware/drivers to the post. It might have nothing to do with gnome at all.
Unfortunately I can’t do anything meaningful whe issue appears, because it doesn’t allow even to change directory or run the command properly. Everything just goes broken.
After one of those hang / crush events and you have rebooted, the command below will print al the errors from the previous session. This will probably show some relevant data to troubleshoot the issue you have: $ journalctl --boot -1 --priority=err
-- Journal begins at Fri 2021-05-14 02:09:43 EEST, ends at Mon 2021-09-27 21:27:37 EEST. --
Sep 27 18:22:25 lds kernel: x86/cpu: SGX disabled by BIOS.
Sep 27 18:22:25 lds systemd-udevd[297]: vboxdrv: /usr/lib/udev/rules.d/60-vboxdrv.rules:1 Only network interfaces can be renamed, ignoring NAME="vboxdrv".
Sep 27 18:22:25 lds systemd-udevd[296]: vboxdrvu: /usr/lib/udev/rules.d/60-vboxdrv.rules:2 Only network interfaces can be renamed, ignoring NAME="vboxdrvu".
Sep 27 18:22:25 lds systemd-udevd[297]: vboxnetctl: /usr/lib/udev/rules.d/60-vboxdrv.rules:3 Only network interfaces can be renamed, ignoring NAME="vboxnetctl".
Sep 27 18:22:25 lds kernel: ioremap error for 0x65eb3000-0x65eb4000, requested 0x2, got 0x0
Sep 27 18:22:26 lds systemd-udevd[265]: vboxdrv: /usr/lib/udev/rules.d/60-vboxdrv.rules:1 Only network interfaces can be renamed, ignoring NAME="vboxdrv".
Sep 27 18:22:26 lds systemd-udevd[266]: vboxdrvu: /usr/lib/udev/rules.d/60-vboxdrv.rules:2 Only network interfaces can be renamed, ignoring NAME="vboxdrvu".
Sep 27 18:22:26 lds kernel: psmouse serio1: elantech: elantech_send_cmd query 0x02 failed.
Sep 27 18:22:26 lds kernel: psmouse serio1: elantech: failed to query capabilities.
Sep 27 18:22:30 lds NetworkManager[452]: <error> [1632756150.5093] device (wlp0s20f3): Couldn't initialize supplicant interface: Failed to D-Bus activate wpa_supplicant service
Sep 27 18:22:32 lds bluetoothd[598]: Failed to set mode: Blocked through rfkill (0x12)
Sep 27 18:22:36 lds gdm-password][1841]: gkr-pam: unable to locate daemon control file
Sep 27 18:22:37 lds gdm-launch-environment][553]: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Sep 27 18:22:40 lds pulseaudio[2029]: module-rescue-stream is obsolete and should no longer be loaded. Please remove it from your configuration.
Sep 27 18:22:41 lds wpa_supplicant[651]: nl80211: kernel reports: Attribute failed policy validation
Sep 27 18:22:41 lds wpa_supplicant[651]: Failed to create interface p2p-dev-wlp0s20f3: -22 (Invalid argument)
Sep 27 18:22:41 lds wpa_supplicant[651]: nl80211: Failed to create a P2P Device interface p2p-dev-wlp0s20f3
Sep 27 18:24:03 lds pulseaudio[2029]: ALSA woke us up to write new data to the device, but there was actually nothing to write.
Sep 27 18:24:03 lds pulseaudio[2029]: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA developers.
Sep 27 18:24:03 lds pulseaudio[2029]: We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.
Sep 27 18:25:20 lds pulseaudio[2029]: ALSA woke us up to read new data from the device, but there was actually nothing to read.
Sep 27 18:25:20 lds pulseaudio[2029]: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA developers.
Sep 27 18:25:20 lds pulseaudio[2029]: We were woken up with POLLIN set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.
No apparent issues in the log that I would further investigate for crash related problems. The screenshot could point to a disk problem, one of those problems that do not write anything to disk so it does not end up in the log… Still no clue and not sure where to begin.
you could try to open a terminal and follow the log with this command: journalctl --follow --priority=err
This will print the errors when they occur, thus circumventing the problem in the terminal and have them on screen when it happens to copy or of no netwerk and saving fails a photo.