https://bugs.kde.org/show_bug.cgi?id=504142
Piotr Dobrogost <bugs.kde....@p.dobrogost.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|BACKTRACE |---
Status|NEEDSINFO |REPORTED
--- Comment #3 from Piotr Dobrogost <bugs.kde....@p.dobrogost.net> ---
(In reply to Nate Graham from comment #2)
> Since it's crashing, can you get a backtrace of the crash? We need one in
> order for this to be actionable. See
> https://community.kde.org/Guidelines_and_HOWTOs/Debugging/
> How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl
It crashed eventually but first it had failed to start 7 times in a row. I
guess the final crash was due to some kind of accumulation of… something?
I'm afraid that fixing crash alone won't solve the problem as it will just keep
timing out each time it's started.
It would be much better to investigate why it's unable to start when it does
not crash.
If it's waiting for something I hoped it would have been in the debug log but I
don't see anything like this.
Can some more debug logging be added if kwin_x11 process does indeed wait for
something?
Can you point me to changes in kwin_x11 between 6.3.4 and 6.3.5?
--
You are receiving this mail because:
You are watching all bug changes.
