On 15/04/16 18:20, Ralf Mardorf wrote:
On Fri, 15 Apr 2016 19:08:21 +0200, Ralf Mardorf wrote:
On Fri, 15 Apr 2016 10:01:56 -0700 (PDT), Len Ovens wrote:
On Fri, 15 Apr 2016, Ralf Mardorf wrote:
But the OP should care what is send by this command line tool, most
likely the OP dislike to send credit card information and
passwords.
Creditcard info? passwords? Testing should be done on a clean install.
I suggest a clean install, user name "Joe Blow" password "testing" for
an install to test things with. Sending bug reports from a daily use
system may mean some change you have made is the problem rather than
the SW itself. Making the bug happen on a clean install is best and
easiest to debug. It is unfortunate that ubiquity does not have an
install option that creates a 20G partition for test installs. (but
then it would probably confuse to many people <sigh>)
That's something completely different ;). However, instead of "Joe
Blow" IMHO "Deep Thought" is appropriate. Don't confuse it with "Deep
Throat" :D
42
PS:
There are still issues regarding log files. Assumed somebody doesn't
use DHCP, but e.g. PPPoE, the password could be provided in plain text
by a log file and even if you don't dial up, be careful when filing a
bug against a MUA.
Just so you know - bugs reported by ubuntu-bug, that could possibly
contain personal information - get marked Private, the only people able
to access such bugs are the one reporting and bug control
Of course if someone manually reported a bug containing that - and
didn't know - a likely scenario considering the people attracted to
*buntu - would leave their personal information free for anyone to read.
Your choice - you report manually if you want, I've not the time to
read, nor try to find out how to read all of the many files that help to
narrow down the cause of a bug.
I'll use the tool.
--
ubuntu-studio-devel mailing list
[email protected]
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
