http://bugzilla.opensuse.org/show_bug.cgi?id=1136300
http://bugzilla.opensuse.org/show_bug.cgi?id=1136300#c17
--- Comment #17 from Wolfgang Bauer
200190616 I still have this bug. You have sent messages to do a triage report. However I do not understand how to do this. I'm not sure what/who you mean here.
As I wrote already, your upstream bug report (https://bugs.kde.org/show_bug.cgi?id=407902) is still in state NEEDSINFO/WAITINGFORINFO, and that triggered an automated response now that the bug report will be closed automatically if you don't provide the requested information. Again, you (as the reporter) need to change the status back to REPORTED. If you don't, it will just be closed without further action. And I'm still not convinced that this is an openSUSE-specific problem, or that we will be able to find the reason... (In reply to Michael Calmer from comment #14)
Created attachment 807161 [details] crash dump
Not sure if it helps, but I have a crash dump with debug symbols.
Unfortunately, that doesn't show much more than the already existing crash dump (without debug symbols) in the upstream bug report. Maybe running it in valgrind would give a clue... Can you please try that? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_usef... for instructions. -- You are receiving this mail because: You are on the CC list for the bug.