ktorrent filling ~/.local/share/sddm/xorg-session.log

[morgano]

system: Mgeia 6, 64 bit, Plasma

Suddenly my home was full, and i found my ~/.local/share/sddm/xorg-session.log was 16 gigabyte...

One large contributor is ktorrent which i see puts in about 30 lines per second, like this

Spoiler:

Code: Select all

 
ons aug. 16 16:35:44 2017: PEX: found 5 peers
ons aug. 16 16:35:44 2017: Authentication(S) to 114.254.55.88 : failure
ons aug. 16 16:35:44 2017: Connection closed
ons aug. 16 16:35:44 2017: PEX: found 3 peers
ons aug. 16 16:35:44 2017: Connection closed
ons aug. 16 16:35:45 2017: Accepted connection from 125.111.197.56
ons aug. 16 16:35:45 2017: Connection closed
ons aug. 16 16:35:45 2017: Connection closed
ons aug. 16 16:35:45 2017: Connection closed
ons aug. 16 16:35:45 2017: Timeout occurred
ons aug. 16 16:35:45 2017: Authentication to 109.197.193.160 : failure
ons aug. 16 16:35:45 2017: Initiating connection to 109.197.193.160 via (UTP)
ons aug. 16 16:35:45 2017: Timeout occurred
ons aug. 16 16:35:45 2017: Authentication to 79.137.64.201 : failure
ons aug. 16 16:35:45 2017: Initiating connection to 79.137.64.201 via (UTP)
ons aug. 16 16:35:45 2017: Doing tracker request to url : udp://open.demonii.com:1337
ons aug. 16 16:35:45 2017: Doing tracker request to url : udp://open.demonii.com:1337
ons aug. 16 16:35:45 2017: Doing tracker request to url : udp://open.demonii.com:1337
ons aug. 16 16:35:45 2017: Doing tracker request to url : udp://open.demonii.com:1337
ons aug. 16 16:35:45 2017: Doing tracker request to url : udp://open.demonii.com:1337
ons aug. 16 16:35:45 2017: Timeout occurred
ons aug. 16 16:35:45 2017: Authentication to 78.209.66.6 : failure
ons aug. 16 16:35:45 2017: Initiating connection to 83.42.168.232 via (TCP)
ons aug. 16 16:35:45 2017: Timeout occurred
ons aug. 16 16:35:45 2017: Authentication to 78.193.229.67 : failure


Is this really normal? Can I limit the logging? - Searched the settings and internet but did not find anything...
I guess easiest is to change to use another program.

EDIT: what really tipped it over is a bug filling up the log file if camera is detached when using guvcview. But the high log rate of ktorrent is a real problem too. /EDIT

[doktor5000]

Is that an upgraded installation and/or using some old settings, or are that the default ktorrent settings in a new /home?
Can you please also run kdebugdialog and check whether you have some debug logging for ktorrent enabled maybe ?

[morgano]

kdebugdialog have the check mark set to disable all debug output.
The system got upgraded from mga5 over a year ago and followed cauldron, then switched to mga6, always same home except i once deleted most configuration manually to refresh it.
SO i was running cauldron in production for over a year
Time to fresh install i guess...

[doktor5000]

Well, you could try if this happens the same way with a freshly created user. Also, are there any advanced options in ktorrent to control log verbosity or to disable it?
I've not found any options or other topics regarding ktorrent writing to xorg session log (I believe that is what before had been ~/.xsession-errors)
You may also want to check your sddm config /etc/sddm.conf to see if you maybe did any changes to this ...

Apart from that, it might make more sense to ask upstream at https://forum.kde.org/ if they have other hints about this.

[jiml8]

Why not log out the user and then, as root, delete the file? It will be recreated when that user logs back in and may or may not go nuts again.

You also could delete the file while logged in. It won't actually go away until all handles to it close, but this should happen when you log out, or at worst it will happen when you reboot.

[morgano]

Thanks for the replies.
I will see what happens after a reinstall (have a couple other quirks, this system have been a rolling mga6/cauldron since upgrade from mga5 soon one and a half year ago)