WetGeek I've noticed some similar behavior and I think it might have to do with having Telegram autostart or start minimized to the tray. I'm hoping that an update to qt6 that I'm planning to do in the next week or so might help.

It's just annoying, it's not like it's not usable though which is why I decided to keep the update. We'd been stuck on 4.8.4 for so long due to dependency issues that I figured more users would appreciate the new version.

      I too noticed that for a while now, Telegram (installed from repo) aborts from time to time without any notice. Attempts to restart fail, as it aborts right after I access chats. If I wait a few hours and restart again, it seems to stop this behaviour. Puzzling.

      ReillyBrogan It's just annoying, it's not like it's not usable

      I agree, and said as much in my post. I wish you luck with finding the solution.

      After I reinstalled, it seems to last longer before it closes. That's just a subjective impression, not a measurement. I've gone off to do things in other workspaces, and noticed that it's stil up and running in its own. But eventually it disappears again.

        Sometimes when it says it "aborted" I find that it's still running in the status bar. Seems to be that Plasma might be confused with the user clicking on the icon and it not starting up (because it's already running minimized).

          @"Harvey"#p87358on first glance this change link was interesting. some cosmetic only 'improved' tracking stuff including the fingerprint implemented..I got this covered and back in :config...so neglibible for me.

          Some moves regarding a new German law and the trust anchors....at small writing at the bottom of that page it says "view security fixes"--

          now that was the money page. of 10 CVE warnings, 5 were marked 'high' impact. 10 is plenty of CVE's. thanks for getting on 120.00.

          Thunderbird 115.5.0 cherry-picked.

          Sebastian , thanks, it works.
          I'll wait for the next update to see if problem is solved.

            I normally wait a couple of days after an update to see if there is much chatter in the forum. This update has me nervous. I am a non-technical user. Am I better off waiting until next week so there are less issues? I really cannot deal with not being able to login, if that's a common problem. When I do update, is there anything I should do first to avoid serious issues?

              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!