On 01/29/2020 01:32 AM, Felix Miata wrote:
Damn that is a huge file. Can you `head .xsession-errors` to see the first few lines, or `sed -n 300,500p .xsession-errors`. 176 line head before the first of the out of range reps: http://fm.no-ip.com/Tmp/Linux/KDE/bobs-xsessionerrors.txt
wc -l .xsession-errors caused an oops, core-dump, PC lockup, BUG: unable to handle kernel NULL pointer dereference at 0000000000000000 (16 0s).
Any other associated errors generate a pop-up? None noted. They appeared in a very very rarely used user account. Owner doesn't remember why he logged into it or what he might have been doing at the time
I'm scratching my head at what a user could to do screw something up to the point of generating gigabyte size .xsession-errors. Wow. In the output at http://fm.no-ip.com/Tmp/Linux/KDE/bobs-xsessionerrors.txt nothing really stands out up top. The HP device status and Displays is a bit hard to explain, but harmless. All the repetitive: KNotify::playTimeout KNotify::playTimeout X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x2000006 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x2000006 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x2000006 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x2000006 libpng warning: iCCP: known incorrect sRGB profile kbuildsycoca running... X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x20001d6 WeaverThreadLogger: thread (ID: 4) suspended. WeaverThreadLogger: thread (ID: 2) suspended. WeaverThreadLogger: thread (ID: 3) suspended. WeaverThreadLogger: thread (ID: 1) suspended. Weaver dtor: destroying inventory. WeaverThreadLogger: thread (ID: 1) destroyed. WeaverThreadLogger: thread (ID: 2) destroyed. WeaverThreadLogger: thread (ID: 3) destroyed. WeaverThreadLogger: thread (ID: 4) destroyed. Weaver dtor: done jack_client_new: deprecated Cannot connect to server socket err = No such file or directory Cannot connect to server request channel jack server is not running or cannot be started JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock akode: Guessed format: xiph <...snip...> Aside from the WeaverThreadLogger: stuff looks like the normal repetitive spew that jack produces -- that should never reach the 1M size in the normal login time of a week or so. Now, I can see if this session was started in September 2019 and some how was not closed on exit, that between then and now it could accumulate a fairly large log, but I can't see even that being gigabytes. Felix, if you like, I can write a short C program to scan the lines in the file for the unique lines (or say first 10,000 unique lines) in such a way that doesn't require reading the entire file. I can see utilities like `wc` or others that may scan the entire file choking on the size. But a basic C program that simply opens the file (and doesn't mmap the whole thing), but instead just relies on the underlying BUF_SIZE to read the file in 8K chunks, can read as far as you want to go in the file pulling out unique lines. Let me know -- probably wouldn't take 20 minutes to put something reasonable together. `sed` and `dd` are two other options for scanning though the file in a way that shouldn't scan the entire thing first. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org