Although I do tend to agree that it should not be by default, but it would be
cool for the user who is interested in the bug-report.
Lets take the case of user case A whose application keeps on
failing, some x buggy program, so by default apport would be sending but the
user never comes to know that the report never got sent due to some error or
the other.
User B is a good citizen & religiously files the bug reports but
at times he gets errors (something like 500 Internal Server after trying to
actually send the bug report for 30 mins.) He does not know the reason why it
happened. He then takes recourse of servers like rapidshare.com but that is
insecure, prone to more failure (no way to do some parity-checking) or
something like that.
Reference bug #103604 for use-case scenario B.
Point to be noted :- The crash file therein is only 7 MB, I
am on 246 Kbps/64 Kbps unlimited connection. Tried sending the bug-
report at the very least 5-6 times without no result. Once after 2 hrs.
of apport saying it is uploading I get an Internal Server Error 500. At
the end, had to take recourse of rapidshare.com twice but without any
positive outcome (some parity issue or some other thing probably). User
having -1 experience with the whole bug-reporting experiencing with
apport.
Further as we move to feisty+1 or even a bigger bug-report
lets say an openoffice crash (maybe 15-20 MB) reasonable , shudder to
think how I would do it under the present circumstances.
--
apport should be mini-ftp client with resuming capabilities
https://bugs.launchpad.net/bugs/102868
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
