Michael wrote: > On Sunday, 21 September 2025 13:42:36 British Summer Time Dale wrote: >> Dale wrote: >>> Howdy, >>> >>> I was doing my backups which includes config files. I noticed one file >>> was shall we say, large. The better term might be HUGE. This is the >>> culprit. >>> >>> >>> >>> root@Gentoo-1 / # ls /home/dale/.local/share/sddm/xorg-session.log >>> -rw-r--r-- 1 dale users 13,905,915,860 Sep 14 03:33 >>> /home/dale/.local/share/sddm/xorg-session.log >>> root@Gentoo-1 / # >>> >>> >>> <<< SNIP >>> >>> >>> Thanks. >>> >>> Dale >>> >>> :-) :-) >> OK. I finished my updates and logged out and back in. In no time the >> file was almost a gigbyte. Or is that Gigabyte??? Anyway, this is a >> few lines of what is in it. >> >> >> [mov,mp4,m4a,3gp,3g2,mj2 @ 0x562f1ed43940] STSC entry 64556 is invalid >> (first=1 count=1 id=1) >> [mov,mp4,m4a,3gp,3g2,mj2 @ 0x562f1ed43940] STSC entry 64555 is invalid >> (first=1 count=1 id=1) >> [mov,mp4,m4a,3gp,3g2,mj2 @ 0x562f1ed43940] STSC entry 64554 is invalid >> (first=1 count=1 id=1) >> [mov,mp4,m4a,3gp,3g2,mj2 @ 0x562f1ed43940] STSC entry 64553 is invalid >> (first=1 count=1 id=1) >> [mov,mp4,m4a,3gp,3g2,mj2 @ 0x562f1ed43940] STSC entry 64552 is invalid >> (first=1 count=1 id=1) >> [mov,mp4,m4a,3gp,3g2,mj2 @ 0x562f1ed43940] STSC entry 64551 is invalid >> (first=1 count=1 id=1) >> [mov,mp4,m4a,3gp,3g2,mj2 @ 0x562f1ed43940] STSC entry 64550 is invalid >> (first=1 count=1 id=1) >> [mov,mp4,m4a,3gp,3g2,mj2 @ 0x562f1ed43940] STSC entry 64549 is invalid >> (first=1 count=1 id=1) >> [mov,mp4,m4a,3gp,3g2,mj2 @ 0x562f1ed43940] STSC entry 64548 is invalid >> (first=1 count=1 id=1) >> [mov,mp4,m4a,3gp,3g2,mj2 @ 0x562f1ed43940] STSC entry 64547 is invalid >> (first=1 count=1 id=1) >> [mov,mp4,m4a,3gp,3g2,mj2 @ 0x562f1ed43940] STSC entry 64546 is invalid >> (first=1 count=1 id=1) >> [mov,mp4,m4a,3gp,3g2,mj2 @ 0x562f1ed43940] STSC entry 64545 is invalid >> (first=1 count=1 id=1) >> [mov,mp4,m4a,3gp,3g2,mj2 @ 0x562f1ed43940] STSC entry 64544 is invalid >> (first=1 count=1 id=1) >> >> >> >> I did a search but the matches the search returns are different. I use >> Smplayer and I have it set to use mpv. It seems Mplayer isn't as good >> as it used to be. >> >> Anyone seen that error before? Is there something I can do to fix what >> it is complaining about? If it can't be fixed, should I just delete the >> file and if needed delete the file and then lock it as someone else >> suggested? I'd rather fix what it is complaining about but it may be >> that I can't do that. Given the wide range of videos I watch, all of >> them can't be broken tho. >> >> Open to ideas. >> >> Dale >> >> :-) :-) > 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 :-) :-)
