--- Comment #3 from ---
(In reply to Harald Sitter from comment #2)
> If that happens in Kubuntu it is not a duplicate really (could not even be
> the same root cause mind you, as the relevant error we fixed isn't there
> [also us fixing this in neon does not fix it for kubuntu anyway]).
> So yeah, if this is a crash we'll need a backtrace, otherwise it's probably
> best to bounce it to the Kubuntu team for investigation.

I reported this issue in kubuntu forums.
Now, I go search info for made the backtrace and attach here.

You are receiving this mail because:
You are watching all bug changes.

Reply via email to