GNOME Bugzilla – Bug 516293
Add log viewer
Last modified: 2018-07-11 23:20:29 UTC
From Brent Gueth: > Logging - Well can I say someone at some point needs to put in an > event log into the preferences of the GUI to give someone a shot at > figuring out why something failed? Something like an "event log" that > can track every file read/write/transform/transcode/sync point open > close/etc?
The Event log is a terrific idea, but it could become too technical if there is no care for what is reported. The Event Log would be great to display the current progress (how many items synced, what item is currently being synced, even what item is currently giving an error), but we shouldn't expose too much details. Reporting that an exception occured would also be great (especially for bug reports) but it might be confusing for users without technical knowledge. So, while I like the idea of a Event Log, we probably shouldn't abuse it. It definitely shouldnt have the same contents as the console. Maybe it`s a good first step into a better UI, but it's definitely something we should follow closely into how much confusion it can create and how it might make the interface even more clumsy. With that said, implementing a logging output to an event logger is not very hard. But we should choose carefully what messages go there, probably selecting a few very important events.
Conduit is not under active development anymore, has not seen code changes for eight years, and saw its last tarball release in 2010. Its codebase has been archived: https://gitlab.gnome.org/Archive/conduit/commits/master Closing this report as WONTFIX as part of Bugzilla Housekeeping to reflect reality. Please feel free to reopen this ticket (or rather transfer the project to GNOME Gitlab, as GNOME Bugzilla is deprecated) if anyone takes the responsibility for active development again.