hakimjonas well if you boot with the USB it should be possible to get the journal logs off of it using journalctl in the boot USB. Basically there's nothing we can do to help you figure this out without the logs, but the good news is they should still be written even when the system is unresponsive. I'm not in front of my computer rn so I can't give you the specific commands to use, but they should be possible to find with an internet search.

Also, try the lts kernel. It may work instead since this sounds like it's most likely a kernel issue of some kind.

      penny-farthing , Salut, j'ai fait quelques corrections. N'hésitez pas à me les signaler "précisément", c'est plus facile ensuite de les corriger. Elles seront sans doute prises en compte lors de la prochaine version de Budgie.

      Hi, I have made some corrections. Don't hesitate to "precisely" point them out, it is then easier to correct. They will be taken into account with the publishing of the next Budgie version.

      Regards.

        Everyting went well
        I found out why I couldn't boot Gnome Wayland since previous sync: Pixel Saver extention. My bad...

        Hi, thanks for the awesome update!
        Am I the only one suffering from keyboard focus issues ?
        What I mean is that can't just type in Ulauncher or guake after pressing the shortcut to visualize them.
        Instead now I have to focus the application, which is counter productive 🙁

        Anyone else having the same problems ?

        EDIT: SOLVED by reinstalling the problematic apps and rebooting the OS.

        Cheers,
        PY

        JoshStrobl The one app that I noticed this on was VeraCrypt. Normally there's an icon in the tray but there isn't. When I go to open the app again, I get a "VeraCrypt is already running" message.

            Today this problem appeared with digikam on Budgie Solus, i don't know if it is related with the latest update:

            ~ $ digikam

(digikam:49628): GLib-GObject-CRITICAL **: 22:38:28.301: cannot register existing type 'GdkDisplayManager'

(digikam:49628): GLib-CRITICAL **: 22:38:28.301: g_once_init_leave: assertion 'result != 0' failed

(digikam:49628): GLib-GObject-CRITICAL **: 22:38:28.301: g_object_new_with_properties: assertion 'G_TYPE_IS_OBJECT (object_type)' failed

(digikam:49628): GLib-GObject-CRITICAL **: 22:38:28.301: invalid (NULL) pointer instance

(digikam:49628): GLib-GObject-CRITICAL **: 22:38:28.301: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(digikam:49628): GLib-GObject-CRITICAL **: 22:38:28.301: invalid (NULL) pointer instance

(digikam:49628): GLib-GObject-CRITICAL **: 22:38:28.301: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(digikam:49628): GLib-GObject-CRITICAL **: 22:38:28.306: cannot register existing type 'GdkDisplay'

(digikam:49628): GLib-CRITICAL **: 22:38:28.306: g_once_init_leave: assertion 'result != 0' failed

(digikam:49628): GLib-GObject-CRITICAL **: 22:38:28.306: g_type_register_static: assertion 'parent_type > 0' failed

(digikam:49628): GLib-CRITICAL **: 22:38:28.306: g_once_init_leave: assertion 'result != 0' failed

(digikam:49628): GLib-GObject-CRITICAL **: 22:38:28.306: g_object_new_with_properties: assertion 'G_TYPE_IS_OBJECT (object_type)' failed
Errore di segmentazione (core dump creato)

            Anyone else having the same problem?

              @ReillyBrogan

              So unfortunately I have not been able to produce a log. But what I have done is reinstalled 4.4, switched to the lts-kernel and then done the system update. This turns out the same, which leads we to think that the issue is not a kernel issue. At least not solely. And as long as I dont update, the system works fine, which suggest that its not just a hardware issue either.

              I did see some chatter in the arch forums about the 6.4.11 kernel and even an issue related to the SD card reader but for me following the steps there to blacklist the device did not help either and in that case using the lts kernel should also have helped. I'll see if it is at all possible to get a log of what is happening.

                Does anyone else have issues with brave browser? Sites keep crashing, and browser itself keeps crashing.

                  mbevks , same for me.
                  Also the tray icon for this nice widget - https://github.com/tsmetana/spotify-tray just disappeared.
                  The try icon for one obsolete application (gnome-pie) is now visible all the time, no matter that app is configured to disable the panel icon.

                    hakimjonas the next sync will include kernel 6.4.13 so hopefully that helps. But really a log is the most useful thing that you could provide.

                      FAb7D Well, after uninstalling and deleting digikam files and directories I reinstalled it (digikam) and now it work fine.

                        elfprince Well, then there must be something wrong with my installation. I not only had brave crashes, but also encountered a crash of fsearch, multiple crashes of GNOME session and multiple system freezes.
                        I'll try lts kernel for a start.