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. 🙂

                    WetGeek Congratulations are due now, I think.

                    @ReillyBrogan
                    Oh fsck! About as soon as I wrote that, it crashed again. And just now it crashed several times, after running for about 2 seconds each time. I think you were right to suspect it was something else to begin with.

                    This has been a pretty crazy bug. Really hard to get reliable behavior from it, whether consistently working or consistently failing. I'm now officially out of theories.

                      Seems to be a problem that is confined to the desktop version of Telegram. When it happens, I normally switch to my mobile. That never crashed before.

                      Might be a different crashing issue then. I still haven't seen such a crash locally (it was pretty reliable on notifications). If it still happens after the sync tomorrow can you hope on Matrix and we can walk you through providing a crash back trade?

                        Hi,

                        Could it be any of the recent changes / updates to prevent the root login via tty ?
                        I'm able to login as a root via shell with su root , but not directly via tty (CTRL + ALT + F5) ?

                        Cheers,
                        PY

                          presianbg At the risk of sounding like a broken record, could you make an issue for it? Be sure to include your system journal after a such a failed login.

                            Week 46 update is OK as far as I can see now (updated yesterday), except one thing changed:
                            System Settings → Users → Automatic Login seems to have no effect anymore. If it's set to 'On' I'm still asked for my pw after booting (which is inconvenient because I run the machine via Barrier, it doesn't have it's own keyboard).

                            I found a topic from 2019: https://discuss.getsol.us/d/1979-automatic-login-stopped-working-after-solus-updates, followed the advice in it, et voilá: Automatic Login works again.

                            Can this be related to the reworked PAM stack?

                            Besides this: Many many thanks to the team for maintaining this wonderful OS at such high level. Things always just work, and if not in some rare case, there always is a solution. Thats quite an accomplishment!

                              @alfisya thanks for your quick response. Forum search didn't bring this one up (yet). I will follow that issue too.

                              ReillyBrogan If it still happens after the sync tomorrow can you hop

                              I'd be glad to. Meanwhile, I've created a Siduction VM and installed Telegram there. It was much later at night that I'm accustomed to still being awake, so I just started Telegram, answered one comment, and left it running while I went to bed. This morning it hadn't crashed. So I'm hopeful that it will be fixed by the sync. I suspect Qt6 6.6.1 will be the answer,

                                  WetGeek Meanwhile, I've created a Siduction VM and installed Telegram there.

                                  @ReillyBrogan
                                  Siduction ran Telegram okay, but I wanted to build it out as a temporary replacement for Solus if I shoud need it again, and it turned out that it hadn't aged as well as Sparky Linux had. So I replaced it with Sparky, which allowed me to make an exact substitute for my Solus laptop. Same Thunderbird configuration, same Vivaldi configuration, same games, same access to my NAS, same DE, same Latte dock, and so on. And I've been using Telegram there all day now, without an issue. So in case today's sync doesn't fix it for Solus, I can just shift over to Sparky until it is fixed.

                                      WetGeek You know, you can just download the Telegram binaries straight from them right? They build in all their libs into it so it works the same on all distros.