https://bugs.kde.org/show_bug.cgi?id=457779
--- Comment #2 from nssz4...@anonaddy.me --- I know how to use my OS just fine, kde is a GUI and is meant to make linux easier, maybe you guys need to learn how to make better documentation that gives step by step instructions, since Im only grabbing logs? For example the debuginfod documents say: "For packages in the official repositories that support it [1], debug information can be retrieved directly over HTTP with debuginfod." So this isnt the main debug program, this program needs another program to function? Why is your KDE wiki https://community.kde.org/Guidelines_and_HOWTOs/Debugging only giving me debuginfod as the program needed since debuginfod doesnt even seem like the main program, the arch wiki says: "When looking at debug messages, such as by using gdb on a core dump: " What is gdp? Is it pertainable to what you guys need for me to get a backtrace? how do I use that program combined with debuginfod, cant your wiki explain what debuginfod is, why Im using it, what other programs are needed? You just pasted a wiki and a program with no explanation on how its pertainable to this situation. "Debuggers like gdb can download them automatically." Once again Is gdp what I use for crash debugging plasmashell? GDBs web page says it "allows you to see what is going on `inside' another program while it executes -- or what another program was doing at the moment it crashed." Well that sounds what I need yet its not on your wiki? Im not going through the trouble of looking up how to use that if I dont know that is what I need for kde backtraces specifially. The KDE wiki didnt refer me to gdp only debuginfod. "If one wants to retrieve the debug symbols for zstd, along with some source files, one can utilize debuginfod-find:" I dont know what debug symbols are or zstd because Im not a pro at debugging, seems like that info isn't pertainable? This is an example of how all this is hard to sift through a wiki and what is pertainable for just basic backtrace grabbing? All you need are logs? Why does this have to be so complex? Its not good to intimidate people who are trying to learn more about something by saying, well its not right for you. I want how to get you debug info and thats all I want to have to look up, the info provided only says details to those who already know whats going on, which means its poorly written, Wikis are known to be a rabbit hole of looking up one thing after another and all you need are logs from me? In any case Im sorry for ranting and Im not blaming you specifically for the documentation or even KDE because it may be partly due to Archs wiki but it all seems out of context, all you need are logs from users, so where are the simple step by step instructions, instructions that say get this program, get that program, do this and that, and there you have the logs. In any case the "coredumpctl --reverse list plasmashell" says: TIME PID UID GID SIG COREFILE EXE SIZE Thu 2022-08-11 16:03:57 EDT 7672 1000 1000 SIGSEGV present /usr/bin/plasmashell 61.8M Thu 2022-08-11 12:14:26 EDT 111726 1000 1000 SIGSEGV present /usr/bin/plasmashell 60.8M Tue 2022-08-09 12:31:15 EDT 50043 1000 1000 SIGSEGV missing /usr/bin/plasmashell n/a Mon 2022-08-08 21:48:50 EDT 25938 1000 1000 SIGSEGV missing /usr/bin/plasmashell n/a Sun 2022-08-07 12:25:54 EDT 113652 1000 1000 SIGSEGV missing /usr/bin/plasmashell n/a Sat 2022-08-06 20:19:24 EDT 63653 1000 1000 SIGSEGV missing /usr/bin/plasmashell n/a Sat 2022-08-06 16:00:51 EDT 1323 1000 1000 SIGSEGV missing /usr/bin/plasmashell n/a Sat 2022-08-06 10:29:42 EDT 26168 1000 1000 SIGSEGV missing /usr/bin/plasmashell n/a Fri 2022-08-05 10:17:17 EDT 19812 1000 1000 SIGSEGV missing /usr/bin/plasmashell n/a Thu 2022-08-04 23:12:59 EDT 17712 1000 1000 SIGSEGV missing /usr/bin/plasmashell n/a Thu 2022-08-04 22:45:08 EDT 1317 1000 1000 SIGSEGV missing /usr/bin/plasmashell n/a Thu 2022-08-04 07:17:01 EDT 1339 1000 1000 SIGSEGV missing /usr/bin/plasmashell n/a Thu 2022-08-04 06:40:17 EDT 11541 1000 1000 SIGSEGV missing /usr/bin/plasmashell n/a Wed 2022-08-03 22:36:31 EDT 9208 1000 1000 SIGSEGV missing /usr/bin/plasmashell n/a Sun 2022-07-31 23:47:06 EDT 218562 1000 1000 SIGSEGV missing /usr/bin/plasmashell n/a Sun 2022-07-31 06:06:49 EDT 144625 1000 1000 SIGSEGV missing /usr/bin/plasmashell n/a Wed 2022-07-27 16:04:33 EDT 53387 1000 1000 SIGSEGV missing /usr/bin/plasmashell n/a Wed 2022-07-27 14:49:30 EDT 43952 1000 1000 SIGSEGV missing /usr/bin/plasmashell n/a Wed 2022-07-27 12:43:49 EDT 34287 1000 1000 SIGSEGV missing /usr/bin/plasmashell n/a Tue 2022-07-26 20:48:41 EDT 9187 1000 1000 SIGSEGV missing /usr/bin/plasmashell n/a Tue 2022-07-26 19:17:30 EDT 9317 1000 1000 SIGSEGV missing /usr/bin/plasmashell n/a Mon 2022-07-25 01:11:49 EDT 486414 1000 1000 SIGSEGV missing /usr/bin/plasmashell n/a Sun 2022-07-24 21:22:34 EDT 137258 1000 1000 SIGSEGV missing /usr/bin/plasmashell n/a Wed 2022-07-20 21:21:30 EDT 18397 1000 1000 SIGSEGV missing /usr/bin/plasmashell n/a Wed 2022-07-20 08:35:08 EDT 1386 1000 1000 SIGSEGV missing /usr/bin/plasmashell n/a Wed 2022-07-20 03:07:54 EDT 42221 1000 1000 SIGSEGV missing /usr/bin/plasmashell n/a Mon 2022-07-18 13:13:22 EDT 1357 1000 1000 SIGSEGV missing /usr/bin/plasmashell n/a Sat 2022-07-09 19:53:07 EDT 116642 1000 1000 SIGSEGV missing /usr/bin/plasmashell n/a Sat 2022-07-09 19:29:04 EDT 115297 1000 1000 SIGSEGV missing /usr/bin/plasmashell n/a Fri 2022-07-08 22:05:38 EDT 95959 1000 1000 SIGSEGV missing /usr/bin/plasmashell n/a Thu 2022-07-07 22:48:16 EDT 71862 1000 1000 SIGSEGV missing /usr/bin/plasmashell n/a Thu 2022-07-07 21:00:01 EDT 70440 1000 1000 SIGSEGV missing /usr/bin/plasmashell n/a Thu 2022-07-07 18:04:13 EDT 65509 1000 1000 SIGSEGV missing /usr/bin/plasmashell n/a Wed 2022-07-06 22:07:26 EDT 51473 1000 1000 SIGSEGV missing /usr/bin/plasmashell n/a Wed 2022-07-06 19:44:57 EDT 45809 1000 1000 SIGSEGV missing /usr/bin/plasmashell n/a Mon 2022-07-04 21:33:48 EDT 16760 1000 1000 SIGSEGV missing /usr/bin/plasmashell n/a Wed 2022-06-29 21:29:28 EDT 1415 1000 1000 SIGSEGV missing /usr/bin/plasmashell n/a -- You are receiving this mail because: You are watching all bug changes.
