Dale wrote: > Michael wrote: >> >> I'll guess mpv is trying to play a stream and it finds some inconsistency in >> the data chunks of the stored stream. I can think of two ways to ask it to >> shut up and not bother you. Check the man page for mpv, it mentions: >> >> --msg-level=<module1=level1,module2=level2,...> >> >> where you can set the level as "no" to silence it completely, or specify the >> module which is causing all these STSC messages and just silence that alone. >> >> The second potential entry is the path to store its log. Perhaps if you set >> this to /dev/null it will not print anything out. >> >> --log-file=<path> >> >> Once you find something which works on a terminal, try modifying your >> ~/.config/mpv/mpv.conf file options to achieve the same. >> >> You may find this useful: >> >> https://deepwiki.com/hooke007/mpv_doc-CN/2.1-configuration-options > I'm going to try the /dev/null option. If I can't fix what it is > complaining about, I'll just shut it up. ROFL > > Works for me. ;-) > > Thanks. > > Dale > > :-) :-) >
I tried the /dev/null option for mpv and the file is back and already north of 1Gbs. Either it isn't mpv, seems to me it is, then what else can I do to stop this file from getting so large? I might add, I have other options in the mpv file and they work. So, I'm dealing with the right file at least. Any other ideas? I'm thinking I need to do something with sddm itself. It does seem to be the one writing to this file. My google searches turned up nothing like this. Is this a Gentoo thing? And maybe just affecting me for some reason???? Thanks. Dale :-) :-)
