Post #1496819
2026-04-21 12:45 UTC
Replies (2)
-
@Alkaris@meow.social 2026-04-21 12:58
The second thing that should also be addressed is crash handling of applications. Often when an application crashes there is no user feedback as to what happened when nothing shows up on the users screen after clicking on it to launch the application. What should happen instead is have a Crash Log window popup showing all the same information as if you ran it inside Terminal. Print out what happened in the backend to the Crash Log window. This would make it easier for people to identify why their application couldn't run with this little bit of user feedback and be able to copy that output or save it to a text file should they need to report their issue they're having.
-
@starsider@valenciapa.ws 2026-04-21 14:48
@Alkaris@meow.social What do you need it for, specifically? In KDE for example, to browse files there's already an "open as administrator" context menu option when a folder is not owned by the user, and all apps I know that require admin permissions (e.g. KDE partition manager, kdiskmark for some partitions, rustdesk when enabling or disabling the service, steam when setting up VR the first time, etc.) pops up a password dialog for admin access. For some other things (like access to a serial port), people shouldn't use sudo, but should add themselves to the appropriate group (uucp in the case of serial ports). That should probably be a feature of applications like Arduino IDE (to ask for admin access to add yourself to the group). Just running stuff as root can be problematic, not just because of security issues, but also because of littering the home directory with files that the user can't read.