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.

                                EbonJaeger unstickied the discussion .

                                ReillyBrogan you can just download the Telegram binaries straight from them right?

                                I never thought of that as an option, because I normally choose packages from the Solus repository. I've always believed that getting software externally might not update it reliably. If that's not the case here, I might consider it as a last resort, but I'm pretty comfortable right now. Thanks for pointing that out.

                                  Harvey locked the discussion .