| Summary: | media-sound/kstreamripper creates kstreamripper.log file in home directory | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | BT <amak79> |
| Component: | [OLD] KDE | Assignee: | Gentoo KDE team <kde> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
kstreamripper.log file
emerge --info |
||
Created attachment 295993 [details]
emerge --info
Fixed in kstreamripper-0.7.100-r1 |
Created attachment 295991 [details] kstreamripper.log file kstreamripper creates a kstreamripper.log file in the root of my home directory every time it starts. It's quite annoying since my home directory is well organised and contains no files at the root. The file mostly contains 'DEBUG' notices, but also some 'WARNING' notices. The debug notices seem to imply that kstreamripper might be built with the debug use enabled, but it's definitely disabled. There is a note on the kstreamripper homepage at kde-apps.org that makes reference to kstreamripper.log with regards to debugging: If reporting a bug, please call "kdebugdialog --fullmode" and set the debug output for kstreamripper for all areas to "Shell". If you can't find kstreamripper in the list, set the debug output for "0 - generic" for all areas to "Shell". This will make you see the debug output when you call KStreamRipper from the console. (In KStreamRipper up to 0.7.91 will instead create a log file "kstreamripper.log" in your home directory.) From this it would seem that kstreamripper.log should only be created when debug is enabled. Can someone please confirm this?