https://bugs.kde.org/show_bug.cgi?id=527312
--- Comment #14 from Fernando Marcelino Muniz <[email protected]> --- (In reply to TraceyC from comment #13) > All of the backtraces look to be the same crash. When including very long > output, please attach it as a text file rather than in the body of the > report. Long comments make the report difficult to read through. Thanks. > > Unfortunately the backtrace is incomplete and missing debug symbols for the > following lines (that have ???) that we need to figure out exactly what's > going wrong: > > #4 0x00007f1282ac8bc8 n/a (libQt6Quick.so.6 + 0x4c8bc8) > #13 0x00007f128052d240 n/a (libQt6Core.so.6 + 0x52d240) > #20 0x0000557551ebeff0 n/a (plasmashell + 0x26ff0) > > Could you please install debug packages and attach a new symbolicated > backtrace generated by using `coredumpctl gdb` in a terminal window? See > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports for details about how to do this. > > After you've attached the new backtrace, set this back to REPORTED. Thanks > again. 1- What debug packages? Can you name them? 2- The site is saying to do the opposite of what you want: "Don't attach the backtrace to the bug report. Instead, simply paste it. This way it is much easier for developers to search for duplicate reports, because attachments can't be searched." -- You are receiving this mail because: You are watching all bug changes.
