WetGeek

Here is a link detailing what's new in Thunderbird v.115:
https://www.thunderbird.net/en-US/thunderbird/115.0/whatsnew/

NB. Please note that some extensions are no longer operational, as expected, on this new version, for example:

  • Auto Select Latest Message
  • ImportExportTools NG
  • Manage Emails/ Nostalgy++
  • Manually sort folders
  • Thunderbird Conversations
    Some of them will probably be updated later to be compatible with it.

    BTW, we did fix the Pipewire issue causing duplicate devices to appear and for Bluetooth profiles not to switch. If you still have this issue after an update delete your ~/.local/state/wireplumber folder and restart. You may need to re-select your default audio devices and set your volume but it should work after that.

    Hey after update and login into budgie, white screen appears and shows message "oh no! something has gone wrong. please log out and try again". Swapping into terminal I installed gnome, and gnome works fully, so it must be some budgie issue.

      ReillyBrogan

      So, our thanks to @Harvey for bringing us this Thunderbird version upgrade so quickly, which will be much appreciated by the Solus community. 😃

        kubasama Can you get journalctl logs from a failed login? That's the only way we can narrow down what part is failing.

            kubasama This has happened to me several times. It was always a mesalib error. I would suggest:

            1. Go to TTY Ctrl+Alt+F2 or other function key.
            2. Log in to your account. Enter your name and password (it will not be visible).
            3. Execute sudo eopkg it --reinstall mesalib and reboot.
              If this does not help then do steps 1 and 2, write sudo eopkg check | grep Broken | awk '{print $4}' | xargs sudo eopkg it --reinstall and reboot

                pomon nope, Budgie remains broken.

                Also tried to rollback update, but:
                System error. Program terminated.
                Repo item perl-net-smtp-ssl not found

                    Same thing happened to me yesterday. I solved it by creating a new user and copying all files from the new user directory in my own home dir (also chown'ed it). Now login into Budgie works again, except of course, I now have to re-create all my desktop settings.

                      kubasama
                      sudo eopkg it https://packages.getsol.us/shannon/p/perl-net-smtp-ssl/perl-net-smtp-ssl-1.04-14-1-x86_64.eopkg
                      and then try rollback again.

                        pillmuncher Thanks for the tip. Removing all config files fixes the problem. Also, it's possible that Budgie screenshot applet was at fault here, because whenever I try to add it now, it causes a crash.

                          I just wanted to add the WeatherShow applet to the panel and now the Budgie Desktop Settings program hangs and also the panel. Rebooting fixed that.

                            After startup I get the notification that the Network Connection was established. Clicking on "Don't show this message again" in the notification popup has no effect, the next time I log in the notification reappears.

                              Contrary to what I wrote before the WeatherShow applet wasn't installed, and whenever I try to install it, it immediately hangs. That is, already the "Choose a plugin" dialog window hangs, and with it the "Budgie Desktop Settings" window, and the panel.

                              BTW, I had already uninstalled the budgie-screenshot-applet.

                              EbonJaeger I turned the notification off by switching on org / gnome / nm-applet / disable-connected-notifications in the dconf-editor.

                                Just adding my Budgie experience here (already wrote on reddit)
                                Synced, borked, rolled back, fine.
                                Uninstalled budgie screenshot applet, rebooted, and budgie runs smoother and faster than ever.
                                Synced, rebooted, system is perfectly fine.
                                Thank you @algent !