Another systemd-resolved problem in 17.04

[Xen]

Tom H schreef op 21-06-2017 18:05:

> This list is for "technical support" so it's correct to assume that
> Chris is asking for help!

What if you're wrong?

What if it's a combined effort of making aware and asking for help?

What if this is the info he had, and he chose to share it, instead of 
doing nothing and also being stuck in it?

To keep moving is to find solutions, and this may be the moving that was 
possible for him.

So it's not useless at all.

For instance, it informs me once more to stay away from the thing.


> Anyway, whether it's for help or not, it's a useless email. It's like
> saying "I installed 17.04 and it doesn't boot." It's unhelpful to the
> OP, to anyone receiving the email, and to Ubuntu (as well as to
> whatever upstream's concerned).

If I was a developer (and I am, but I mean in the position of being 
responsible for a certain creation of mine) and someone told me that my 
DNS resolver would stop working it would tell me at least three things:

- I released a broken product
- The user doesn't know where to find logs
- The same user in a default configuration already personally ran into 2 
bugs.

And the error condition is something to do with a "REFUSED" return.

Now in the other email and this one you say that:

- the user is at fault for sending in a lacking failure report
- the user is at fault for not knowing where to find information in 
order to send in a more complete report

Both things can and could be resolved by the developer prior to the 
thing even happening.

Most commercial applications (and non-commercial, but mainstream) 
collect error information themselves and offer to send a report to the 
originator of the software.

Of course you can hardly do so when DNS is down ;-). But still.

If you prepare this ground-work in advance as a developer you can save a 
whole lot of people a whole lot of time and it probably would cost you 
much less time than it would save the users.

We have the apport system.

However the apport system first asks the user to install an unspecified 
list of debug packages before it will allow the user to send in 
anything.

Instead of a 2 second job, it often turns into 15 minutes.

When you search online (I just did) 4 of the 5 first answers (in Google) 
are about disabling the thing.

It comes nowhere near being a functional system.

This just wastes endless amounts of time because the plumbing is not 
there.

If then, in the space of this, users send in incomplete reports, you 
cannot really blame the users for that.

Instead we get more new systems that create more new problems without 
getting systems that would help wasting less time on existing problems.

-- 
ubuntu-users mailing list
ubuntu-users at lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users