Messages echoed to the status bar do get logged; but only in debug mode I believe; otherwise there's too much generated and they're all stored in memory in a pretty simplistic fashion so presents memory issues while tagging large libraries.
FWIW, as of Picard 0.14 the network request layer was rewritten to properly handle request timeouts and be able to log them, rather than have Picard hang; which will help with one aspect of this. As of Picard 0.16, web request failures are now echoed to the log at a higher level; as opposed to the debug level they were before, so should be visible to all users. It's still a bit primitive, but better than before, and maybe sufficient to finally close this in preference for some more specific suggestions on enhancing the reporting/notification of errors to users; preferably reported and discussed upstream. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/277943 Title: No Error Messages when Server Uncontactable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/picard/+bug/277943/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
