Patrice my Evolution won't connect to my mail server now. Just hangs on "Scanning folders in IMAP server..." and keeps prompting me for my password. I even changed the password just to make sure, but no luck. I can get to it via Thunderbird with the same config and credentials so I think this is specifically an Evolution problem.

    mbevks I feel same way. Many of us depend on the Solus OS for their work, and/or important daily work/chores at home. Can't afford to have a broken system. Always keep my fingers and toes crossed when updates arrive. 😃

      ReillyBrogan Sometimes when it says it "aborted" I find that it's still running in the status bar.

      I'm not sure that's true in my case, but I've never looked in the status bar to check. I've always restarted it from Latte, as I mentioned in my earlier post. But I'll check that the next time it happens to me. Anything I can do to help with debugging this, please just ask.

      EDIT: Yup, I just checked, and it's not present in my Plasma status bar. I checked the hidden icons, as well.
      MORE: To be clear, I don't use a task manager, just the Latte dock. What I checked was the system tray.

          mbevks Not being able to login is not a common problem. The sole affected user who reported that was using a custom compiled shell and had not added it to their /etc/shells file. Really it should have never worked in the first place, and the fact that it did is reflective of the prior poor state of our PAM stack (which is now corrected).

          As long as you do not have any of the following it should be safe to update:

          • A custom user shell (like xonsh) that is not packaged in the repos. If you do have one (like oil or xonsh) it can still work you just need to make sure to add it to /etc/shells.
          • A /etc/environment or /etc/environment.d/* file that uses export VARIABLE=VALUE syntax. You just need to change it to VARIABLE=VALUE syntax instead.
          • Custom files in /etc/pam.d (if you have a /etc/pam.d/vlock that one is fine and expected).

          I totally get the reluctance to update, but keep in mind that people with problems are much more likely to post about it than people who aren't having any problems.

            WetGeek Yeah, I've confirmed that it's actually crashing. Qt6 6.6.1 is releasing tomorrow which I'm going to update to and I hope that will help fix the issues, otherwise I'll keep debugging it. The official binaries are built against 6.6.0 and they don't crash so I'm hopeful that that is the issue. If you need non-crashy Telegram for now you could always switch back to the official binaries, they work just fine besides not using the system package manager for updates (and duplication of system libs).

            Unfortunately I can't really downgrade Telegram back to the prior version since it doesn't like opening up user data from new versions, I had that corrupt my local data during testing (or it might have been an ill-timed crash, hard to say) and I had to re-connect my account from scratch.

                ReillyBrogan Qt6 6.6.1 is releasing tomorrow which I'm going to update to and I hope that will help fix the issues

                I'll be really glad if that works. Now it seems to be worsening. I just now had to restart three times in order to finish a 1-line answer to someone. Thanks for continuing to help with this.

                    mbevks I would be nervous at 90% (see poll) too with 0% able to DIY their problem (see poll). these hiccups are always temporary and there is other stuff to spend your anxiety on.

                    mbevks I really cannot deal with not being able to login, if that's a common problem

                    it's going to happen to everybody in any distro at least once in a lifetime--this fear is not solus-related. there's a trillion factors. if you have booted successfully 499 times out of 500--anywhere-- I'd say this is par across the linux spectrum any way. The Win BSOD was part of day-to-day life for a while.

                    short version: play the odds

                          brent The Win BSOD was part of day-to-day life for a while

                          Lucky for me, or unlucky, I never used Windows. So, I totally missed out on that BSOD experience.

                              This is one of the reasons i still wait a few days before i update.
                              Living and deal more than 30 years with this win crap left its marks.
                              Yep win 3.1 was my first one and i hated it from day one but there was no alternative.

                              elfprince you missed a ton of misery 🤮 ! you managed to elude WIN for a long time...from the beginning of your computing life. That's tenacious and the coolest thing I heard this year. You must've had some kind of gut instinct way back when. I know I did, but besides mac I did not know what my options were. I thought it was WIN or die back then.
                              you have been with this project from the beginning! kudos!

                                  brent With Solus since 2019. Apple got me from the early 80s on, then FreeBSD, and then Linux.

                                    Ha mac updates were hit and miss too! I would ask you if you remember having to load 0S7/8/9 without extensions to figure out why it wouldn't launch normally after a major update (glad that option was there) but we will be branched out in new-thread land or warned! over and out😉/

                                    Update for gamescope cherry-picked that fixes a crashing issue.

                                    WetGeek Now it seems to be worsening.

                                    And this morning, just the opposite. I woke up after four hours of sleep, and needed the bathroom. When I got back to bed, I lay there for an hour, wide awake, and then decided to get up and start on my day. I can put the extra hours to good use, with housekeeping to do before family members arrive for Thanksgiving, a turkey to roast, and so on.

                                    So, very early in the morning, I wrote fairly lengthy messages to four friends that I correspond with using Telegram, explaining why I wouldn't be chatting with them much today, and it hasn't crashed once. In fact, it still hasn't crashed. It's still quite happy in its own workspace. I can remember needing to restart it three times in order to write a 1-line response, on one day reently, so this is quite a pleasant surprise.

                                    I know better than to expect 6.6.1 until later today, at the earliest, so I know I'm still on 6.6. And I saw one of those notices like the one I put in an earlier message. But this part of the world is still mostly asleep at this hour, and it makes me wonder if that has something to do with it.

                                    I've spent decades trying to discover the root cause of software issues, so I couldn't help trying to figure out what's responsible for these crashes. And wondering whether a reduction of traffic on the Internet might have something to do with how well it's been working this morning. I know that some mysteries are never solved, so I'm going to stop trying to figure it out now, and get started on the work that's ahead of me this Thanksgiving.

                                    I'll check back from time to time, to see if 6.6.1 has been released finally. I assume that if we don't have a full sync today, you'll probably cherry-pick that one. I expect the gremlins will be back later in the day, so I still want to upgrade Telegram as soon as it's available. So long for now ...

                                        WetGeek Hmmm maybe the Telegram crashing was caused by libwebkitgtk too. It does link against it. I haven't seen any crashes in the 10 minutes I've been using it since I woke up either. The backtrace had nothing to do with libwebkitgtk which is why I didn't think of it as a potential issue in the first place.

                                            ReillyBrogan maybe the Telegram crashing was caused by libwebkitgtk

                                            I've been really busy today, but I did download that webkit library and install it. Assuming that it would be like updating a DLL for Windows, I also rebooted to make sure the new version was loaded.

                                            At first I thought it had fixed the problem, as I chatted with several friends with no crashes, but just about the time I was going to log on here and congratulate you, is crashed. But after restarting it once, it's been a very long time now without another crash, so I'm still at a loss. If it hasn't been crash-less for a full half-hour of correspondence, it's been very close to that. I don't think it's ever lasted this long for me since the Telegram Troubles started.

                                            It seems to be really close to being fixed, except for that one crash. Maybe that was caused by something in a cache? What's you experience been like? Have you had time to check it out yet?

                                                WetGeek It seems to be really close to being fixed

                                                @ReillyBrogan:
                                                In fact, it may very well be fixed. It's been 40 minutes since I wrote that last post, and I'm sure I was using Telegram for at least 20 minutes before that, so it's been a good hour since that one crash I had. The only answer I can think of is a cache entry that was subsequently replaced. It seems like we get just one last crash, and after that it plays nice.

                                                Congratulations are due now, I think. Thanks for getting rid of that gremlin for us. 🙂