https://bugs.gpodder.org/show_bug.cgi?id=1606
--- Comment #4 from PO <[email protected]> 2012-06-09 23:05:08 BST --- REQUEST1: log db filename The deletion of mygpo.queue.sqlite seems to have solved the startup problems - is it possible to enhance the logging to display which database file caused the integrity error? REQUEST2: better logging of gpodder.net synching For further debugging I enabled gpodder.net synching - is it possible to enhance the closeup of gpodder to show a status bar if syncing takes place? I see loads of log messages like: 1339279304.215170 [MygPoClient] INFO: All actions have been uploaded to the server. 1339279304.218321 [MygPoClient] INFO: Starting episode status sync. 1339279307.589679 [UIConfig] INFO: Flushing settings to disk 1339279314.358804 [MygPoClient] INFO: Received 29993 episode actions 1339279322.470318 [MygPoClient] INFO: Received 29993 episode actions and my hdd goes crazy. A more visual feedback would let users be more patient when closing gpodder. Maybe the corrupt database was a result of closing gpodder and shutting down the computer while a gpodder.net sync was taking place. Thanks! -- Configure bugmail: https://bugs.gpodder.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes. _______________________________________________ gPodder-Bugs mailing list [email protected] https://lists.berlios.de/mailman/listinfo/gpodder-bugs
