https://bugs.kde.org/show_bug.cgi?id=488713
--- Comment #46 from Dashon <dashonww...@pm.me> --- (In reply to Vlad Zahorodnii from comment #35) > (In reply to Dashon from comment #33) > > (In reply to Vlad Zahorodnii from comment #31) > > > (In reply to Martin from comment #30) > > > > 3) wait 24 hours -+ few minutes > > > > 4) observe the crash > > > > > > If you change the time in system settings, does the crash occur? > > > > So far, I believe this suggestion has worked and allowed me to avoid today's > > crash. It is officially one hour past the 24 hour mark without a crash > > occurring. I manually set the time to be about 10 hours ahead and it hasn't > > crashed yet. I will let you know if kwin crashes sometime in the next couple > > hours to see if it is just delayed. > > > > Does this mean there is something going wrong with setting the date and time > > automatically? > > No idea. To be honest, I asked about changing the system time hoping to find > a reliable-ish way to reproduce the crash. Today tried changing just the date and unfortunately that did not stop the crash either. So I'm all out of options regarding that route. All we know so far is that it happens at least for me every 24 hours give or take some amount of minutes and that the crash report references some type of Qtimer. Unfortunately, although Arch now supports debuginfod. I still regularly end up with missing debug symbols in any kind of backtrace that I try to create. Whether it be manually or through dr konqi. -- You are receiving this mail because: You are watching all bug changes.
