On Nov 13, 2013, at 09:57 AM, Vincent Ladeuil wrote:
>Note that the 7 minutes without feedback almost triggered a "bah, broken
>somehow, let's reboot" which get delayed because I was typing this
>comment ;)
Yeah, -vv would have spewed much more logging output to your console :).
The problem here is that s-i really isn't doing much at this point. It's
asked udm to download a bunch of files and all it's doing is passing through
the progress signals it gets from udm's D-Bus API. -vv shows you all those
progress signals. -v does not, but then it's also not showing much progress
on the command line.
I've thought about trying to do some occasional progress output when a single
-v is used, but haven't come up with a good idea yet. If you have thoughts,
or even a wish list, please open a new bug just for this.
P.S. The "ui wait for 10 minutes" will be solved with s-i 2.0.
On Nov 13, 2013, at 09:57 AM, Vincent Ladeuil wrote:
>Note that the 7 minutes without feedback almost triggered a "bah, broken
>somehow, let's reboot" which get delayed because I was typing this
>comment ;)
Yeah, -vv would have spewed much more logging output to your console :).
The problem here is that s-i really isn't doing much at this point. It's
asked udm to download a bunch of files and all it's doing is passing through
the progress signals it gets from udm's D-Bus API. -vv shows you all those
progress signals. -v does not, but then it's also not showing much progress
on the command line.
I've thought about trying to do some occasional progress output when a single
-v is used, but haven't come up with a good idea yet. If you have thoughts,
or even a wish list, please open a new bug just for this.
P.S. The "ui wait for 10 minutes" will be solved with s-i 2.0.