https://bugs.gpodder.org/show_bug.cgi?id=1289
--- Comment #5 from Thomas Perl <[email protected]> 2011-02-28 23:20:42 GMT --- (In reply to comment #4) > I'm pretty new to this, so would you mind indulging me and telling me > precisely > what to do. > > I've used the terminal a few times of course, but would you mind telling me > what to type in, and what to type in order to give you the log you request. Sure. Basically you open a X Terminal from the menu, then type in the following line: gpodder --verbose 2>&1 | tee gpodder-log.txt This means: start "gpodder" with the "--verbose" option (to turn on debugging), redirect stderr (=2) to stdout (=1) and then pipe (|) stdout to the command "tee" with the argument "gpodder-log.txt" (tee is an application that will show its stdin on its stdout (=the X Terminal in your case) and also save all of stdin into the file gpodder-log.txt (which you can then attach to this bug report after verifying it does not contain personal URLs that you don't want to share - any personal information that you don't want to share can simply be replaced by "XXX" using a text editor [you have to do this yourself before uploading] before attaching the gpodder-log.txt file to this bug report). -- 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
