Bug 269882 - kget logs an enormous amount of data to .xsession-errors
Summary: kget logs an enormous amount of data to .xsession-errors
Status: RESOLVED NOT A BUG
Alias: None
Product: kget
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: KGet authors
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-01 16:25 UTC by Diggory Hardy
Modified: 2011-08-04 17:32 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
sample .xsession-errors content (27.06 KB, text/plain)
2011-04-02 11:57 UTC, Diggory Hardy 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Diggory Hardy 2011-04-01 16:25:26 UTC 
Version:           unspecified (using KDE 4.5.3) 
OS:                Linux

Normally I wouldn't complain about error reporting... but in this case the amount of verbosity is (just a little) ridiculous, and makes real errors harder to spot. I have a nearly 200000 line .xsession-errors file, started at bootup 2 days ago, and according to grep over 150000 lines match the PID of the current kget instance.

One torrent is actively uploading.

Didn't see any options to set verbosity level (though I didn't look very far).

Cheers for the great software and support,

Reproducible: Always
Comment 1 Lukas Appelhans 2011-04-01 19:29:33 UTC 
Hey!

Thanks for the report, can you attach the .xsession-errors file? Then we can identify the part of kget where it's coming from :)

Lukas
Comment 2 Matthias Fuchs 2011-04-01 21:43:01 UTC 
I can reproduce this issue with my default account. I think that this might be caused by some old config files or something like that. Because if I create a new and clean account I don't have that problem.

A workaround for you is to open kdebugdialog and disable all "kget" entries there (might be two of them).
Comment 3 Matthias Fuchs 2011-04-01 21:53:25 UTC 
Tried a little more.
On the new account initially there was only "5001 kget" mentioned in kdebugdialog. After a while also "kget" was in there.
"5001 kget" was activated from the beginning, "kget" not.
Also activating "kget" lead to the problem described by the bug reporter. This problem then can only be avoided if both "5001 kget" and "kget" are deactivated.
Comment 4 Diggory Hardy 2011-04-02 11:57:52 UTC 
Created attachment 58516 [details]
sample .xsession-errors content

Hey, sorry, I meant to add this yesterday!
Comment 5 Diggory Hardy 2011-04-02 12:18:58 UTC 
Thanks Matthias. I don't find quite the same though: only "5001 kget" must be disabled to stop the output (after restarting kget).
Comment 6 Matthias Fuchs 2011-08-04 17:32:31 UTC 
I (rather the people on irc ;) ) investigated some more.

The "issue" is that kdebug and kwarning messages go to stderr and that in turn is sent to .xsession-error for X apps.
As such this is not a bug but rather a feature, so I suppose to avoid that you have to turn off debugging for the applications -- via kdebugdialog --you do not want to be informed in the .xsession-error-file.

Probably a good idea would be to report this bug on your distribution bug tracker so that they deactivate the debug output by default for at least KGet.