On Fri, 15 Apr 2016 20:31:27 -0400, [email protected] wrote: >always any log files are looked over by myself prior to posting
That's what I tried to point out. Even using a command line tool to report a bug would be ok, assumed it's absolutely clear for the user, what exactly the command line tool does and assumed it should send a log file, if the user of this tool is aware that there is the need to look over such a file. IMHO such a tool stops carefulness and transparency. I'm running Arch at the moment, so uname makes no sense and anything else needs to run in a container: A bug report, if possible, needs information similar to [root@archlinux moonstudio]# uname -rm 4.4.5-1-ARCH x86_64 [root@archlinux moonstudio]# systemd-nspawn -q lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 15.10 Release: 15.10 Codename: wily [root@archlinux moonstudio]# systemd-nspawn -q dpkg -l qjackctl | grep ii ii qjackctl 0.4.0-29-g45508a354d-1 amd64 JACK Audio Connection Kit Qt GUI Interface. + a description of the bug + an explanation how to reproduce the issue + possibly relevant output of log files + possible strace + possible gdb + what so ever debugging It depends on the bug and it requires interaction with the maintainer/developer what files are really required/useful. -- ubuntu-studio-devel mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
