https://bugs.kde.org/show_bug.cgi?id=505177
--- Comment #7 from Roke Julian Lockhart Beedell <4wy78...@rokejulianlockhart.addy.io> --- Created attachment 182366 --> https://bugs.kde.org/attachment.cgi?id=182366&action=edit Comparison: issuetracker.google.com I've since located a much better reason, although this solely applies to attachments: When I report an issue with a KDE package for AOSP, I cannot submit an `adb bugreport` without exposing personal information to the world. You can see at https://issuetracker.google.com/issues/425896312#comment2:~:text=bugreport%2DFP5%2DUKQ1.230924.001%2D2025%2D06%2D18%2D16%2D52%2D11%2Ddumpstate_log%2D24299.txt-,Restricted,-85%20KB%20View&text=bugreport%2DFP5%2DUKQ1.230924.001%2D2025%2D06%2D18%2D16%2D52%2D11.zip-,Restricted,-17%20MB%20Download&text=dumpstate%2Dstats.txt-,Restricted,-8%20B%20View that users are expected to set these attachments as "Restricted" (which limits access to developers) due to this. There is little other way to submit a complete `logcat` (even merely `--buffer=crash`) and environment information, for an AOSP device. -- You are receiving this mail because: You are watching all bug changes.
