https://bugs.kde.org/show_bug.cgi?id=440497
--- Comment #11 from Nate Graham <n...@kde.org> --- I get all that, and I'm not totally unsympathetic because I've done user support both informally and professionally for over 20 years. However it seems to me like your suggestion falls in that awkward valley of being so specific that it's easy to shoot down because it has obvious flaws, but not ambitious enough to actually solve the problem. :) So I think we need to re-focus along one of two axes: 1. Be more ambitious so that we actually generically solve the problem or a lack of information. This would be like a supercharged version of the appwrapper project. 2. Do the boring annoying work of investigating and fixing each individual bug encountered that pertains to KDE software or other software within our sphere of influence (e.g. openSUSE packaging) Both of these would actually *solve* a problem. Your suggestion would not, it would simply make it easier for users gather information when directed by a nerd in preparation for solving it, at the cost of cluttering up the UI. Because that UI clutter is the principal objection, how about a compromise: when you launch an app while holding down some combination of modifier keys, it automatically invokes the "launch in terminal" mode. This would be easy for you to tell to users for debugging purposes, while not cluttering up the UI for people who are not experiencing any bugs. What do you think? -- You are receiving this mail because: You are watching all bug changes.
