[opensuse-kde3] 15.1/KDE3 .xsession-errors exhausted freespace in /home/
23565M is apparently it's too big for wc -l to process. Attempting requires Ctrl-C to get a shell prompt back. # tail < .xsession-errors QGArray::at: Absolute index 725114896 out of range QGArray::at: Absolute index 725114896 out of range QGArray::at: Absolute index 725114896 out of range QGArray::at: Absolute index 725114896 out of range QGArray::at: Absolute index 725114896 out of range QGArray::at: Absolute index 725114896 out of range QGArray::at: Absolute index 725114896 out of range QGArray::at: Absolute index 725114952 out of range QGArray::at: Absolute index 725114952 out of range QGArray::at: Abs # ls -lrt total 24131212 ... -rw------- 1 ruth users 85 Nov 21 2018 .bash_history drwxr-xr-x 3 ruth users 4096 Nov 21 2018 .mcop -rw------- 1 ruth users 8799 Oct 13 13:28 .xsession-errors-:1 -rw-r--r-- 1 ruth users 56 Jan 12 22:06 .DCOPserver_localhost__0 lrwxrwxrwx 1 ruth users 35 Jan 12 22:06 .DCOPserver_localhost_:0 -> /home/ruth/.DCOPserver_localhost__0 -rw------- 1 ruth users 195 Jan 12 22:06 .ICEauthority drwxr-xr-x 2 ruth users 4096 Jan 12 22:06 .qt drwxr-xr-x 2 ruth users 4096 Jan 12 22:06 .hplip drwxr-xr-x 8 ruth users 4096 Jan 12 22:14 .mozilla -rw------- 1 ruth users 0 Jan 12 22:34 .Xauthority -rw------- 1 ruth users 24710152192 Jan 13 00:24 .xsession-errors Any ideas how to troubleshoot this if it happens again, or why it happened? -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 26/01/2020 08.43, Felix Miata wrote: | 23565M is apparently it's too big for wc -l to process. Attempting | requires Ctrl-C to get a shell prompt back. | | # tail < .xsession-errors Better without redirection. Uses an intermediate "something". | QGArray::at: Absolute index 725114896 out of range QGArray::at: | Absolute index 725114896 out of range QGArray::at: Absolute index | 725114896 out of range QGArray::at: Absolute index 725114896 out of | range QGArray::at: Absolute index 725114896 out of range | QGArray::at: Absolute index 725114896 out of range QGArray::at: | Absolute index 725114896 out of range QGArray::at: Absolute index | 725114952 out of range QGArray::at: Absolute index 725114952 out of | range QGArray::at: Abs # ls -lrt total 24131212 ... -rw------- 1 | ruth users 85 Nov 21 2018 .bash_history drwxr-xr-x 3 ruth | users 4096 Nov 21 2018 .mcop -rw------- 1 ruth users | 8799 Oct 13 13:28 .xsession-errors-:1 -rw-r--r-- 1 ruth users | 56 Jan 12 22:06 .DCOPserver_localhost__0 lrwxrwxrwx 1 ruth users | 35 Jan 12 22:06 .DCOPserver_localhost_:0 -> | /home/ruth/.DCOPserver_localhost__0 -rw------- 1 ruth users | 195 Jan 12 22:06 .ICEauthority drwxr-xr-x 2 ruth users 4096 | Jan 12 22:06 .qt drwxr-xr-x 2 ruth users 4096 Jan 12 22:06 | .hplip drwxr-xr-x 8 ruth users 4096 Jan 12 22:14 .mozilla | -rw------- 1 ruth users 0 Jan 12 22:34 .Xauthority | -rw------- 1 ruth users 24710152192 Jan 13 00:24 .xsession-errors | | Any ideas how to troubleshoot this if it happens again, or why it | happened? Well, you do have to try seeing inside. Maybe with "less". Will try to index, but pressing some key aborts the indexing. Or, use "dd" to copy a chunk of it to another file, then have a look at that one. - -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXi19oAAKCRC1MxgcbY1H 1YmrAJ9LnbRCdu8Hb2LLo9IyRglWN9oyagCfRiaK8hukzAbKVJFsf6gF5XYlHww= =3EtU -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
Carlos E. R. composed on 2020-01-26 11:53 (UTC+0100):
Felix Miata wrote:
| 23565M is apparently it's too big for wc -l to process. Attempting | requires Ctrl-C to get a shell prompt back.
| # tail < .xsession-errors
Better without redirection. Uses an intermediate "something".
You totally lost me. I have no trouble seeing that file's content.
| QGArray::at: Absolute index 725114896 out of range QGArray::at: | Absolute index 725114896 out of range QGArray::at: Absolute index | 725114896 out of range QGArray::at: Absolute index 725114896 out of ... | .hplip drwxr-xr-x 8 ruth users 4096 Jan 12 22:14 .mozilla | -rw------- 1 ruth users 0 Jan 12 22:34 .Xauthority | -rw------- 1 ruth users 24710152192 Jan 13 00:24 .xsession-errors
Nothing was rewrapped. Why did you/TB rewrap it into an incomprehensible mess?
| Any ideas how to troubleshoot this if it happens again, or why it | happened?
Well, you do have to try seeing inside. Maybe with "less". Will try to index, but pressing some key aborts the indexing.
Inside what? What indexing?
Or, use "dd" to copy a chunk of it to another file, then have a look at that one.
The question is what makes .xsession-errors so big that freespace on /home is terminally depleted. What caused/causes a bazillion lines of QGArray::at: Absolute index 725114896 out of range in that file? -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 26/01/2020 17.16, Felix Miata wrote: | Carlos E. R. composed on 2020-01-26 11:53 (UTC+0100): | |> Felix Miata wrote: | |> | 23565M is apparently it's too big for wc -l to process. |> Attempting | requires Ctrl-C to get a shell prompt back. | |> | # tail < .xsession-errors | |> Better without redirection. Uses an intermediate "something". | | You totally lost me. I have no trouble seeing that file's content. I thought you said that tail crashed. I say that you should simply use: tail .xsession-errors | |> | QGArray::at: Absolute index 725114896 out of range |> QGArray::at: | Absolute index 725114896 out of range QGArray::at: |> Absolute index | 725114896 out of range QGArray::at: Absolute |> index 725114896 out of | ... |> | .hplip drwxr-xr-x 8 ruth users 4096 Jan 12 22:14 |> .mozilla | -rw------- 1 ruth users 0 Jan 12 22:34 |> .Xauthority | -rw------- 1 ruth users 24710152192 Jan 13 00:24 |> .xsession-errors | | Nothing was rewrapped. Why did you/TB rewrap it into an | incomprehensible mess? I did not do it. TH bug with enigmail or new bug in this version that caught me by surprise when clicking "send", so not undoable. But that chunk of text is not relevant, it is your own quoted text for content. | |> | Any ideas how to troubleshoot this if it happens again, or why |> it | happened? | |> Well, you do have to try seeing inside. Maybe with "less". Will |> try to index, but pressing some key aborts the indexing. | | Inside what? What indexing? ]> QGArray::at: Absolute index 725114896 out of range I thought that was "tail" indexing error. My mistake. Inside ".xsession-errors", obviously. | |> Or, use "dd" to copy a chunk of it to another file, then have a |> look at that one. | | The question is what makes .xsession-errors so big that freespace | on /home is terminally depleted. What caused/causes a bazillion | lines of QGArray::at: Absolute index 725114896 out of range in that | file? I did not realize that ]> QGArray::at: Absolute index 725114896 out of range was the content of the file. I have no idea why you get that. Maybe browse back in the file to the start of those message, maybe there is some context. - -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXi7ZKwAKCRC1MxgcbY1H 1QXQAKCHBj8Es7LC8E34qExIMinrBVocFgCeNXXmKYht9dgp5cdn3ARYFKzIGJ4= =vQ+f -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
On 01/26/2020 01:43 AM, Felix Miata wrote:
-rw------- 1 ruth users 24710152192 Jan 13 00:24 .xsession-errors
Any ideas how to troubleshoot this if it happens again, or why it happened?
Yeeee Ooouuuccchh! Damn that is a huge file. Can you `head .xsession-errors` to see the first few lines, or `sed -n 300,500p .xsession-errors`. Any other associated errors generate a pop-up? -- 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
David C. Rankin composed on 2020-01-29 00:50 (UTC-0600):
Felix Miata wrote:
-rw------- 1 ruth users 24710152192 Jan 13 00:24 .xsession-errors
Any ideas how to troubleshoot this if it happens again, or why it happened?
Yeeee Ooouuuccchh!
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 -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
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
David C. Rankin composed on 2020-01-29 14:50 (UTC-0600):
Felix, if you like, I can write a short C program to
As should have been inferred from my previous post, that PC is not mine. Owner picked it up a few hours ago. Then I got a call that the screen was getting no signal. Turns out the PC powered up but didn't POST. I talked him through a process that got it on and him logged in and he was happy. Less than an hour later, he called with same problem. He also mentioned that after taking the side cover off as directed for examination of the POST code LED, he somehow was severely shocked, in a room with no carpet and average humidity. When I first got it here several days ago it wouldn't POST. I pulled CPU, repasted it, blew out the dust and tar, put it back together, and had no trouble with it over several days. This 62 month old PC is subjected to very heavy cigarette smoke. Something has probably tired of it, or the PS has gotten flaky, or some other hard to diagnose problem has arisen. I'm expecting it to return here in next day or two, but as to trying to diagnose the original problem, I doubt there is any practical way to duplicate or troubleshoot it. The optional user account where this occurred is there simply as a diagnostic aid of virtually non-zero use to the functionally blind owner. His previous PC only lasted 5 years or a little more before it got flaky. That was ultimately determined after he bought new PS, mobo, cpu, cooler and RAM to be his junk PS expired. -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday, 2020-01-29 at 17:56 -0500, Felix Miata wrote:
David C. Rankin composed on 2020-01-29 14:50 (UTC-0600):
Felix, if you like, I can write a short C program to
As should have been inferred from my previous post, that PC is not mine. Owner picked it up a few hours ago.
Then I got a call that the screen was getting no signal. Turns out the PC powered up but didn't POST.
Huh. Internal clock battery?
I talked him through a process that got it on and him logged in and he was happy. Less than an hour later, he called with same problem. He also mentioned that after taking the side cover off as directed for examination of the POST code LED, he somehow was severely shocked, in a room with no carpet and average humidity.
Whoa! The earthing of that computer is faulty. Revise it, and revise that the building has good earthing. I have seen places where the earth was faked: there was an earth wire, but was not connected to an earth rod. With missing earth, the chasis of the computer can float at a mid voltage of mains. Say, mains is 220, the chasis is at 110. It is a side effect of switching power supplies combined with EMI filtering. Does not happen with all PSUs.
When I first got it here several days ago it wouldn't POST. I pulled CPU, repasted it, blew out the dust and tar, put it back together, and had no trouble with it over several days.
I would go there and check with a voltmeter. - -- Cheers, Carlos E. R. (from openSUSE 15.1 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXjKqFRwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVfZ0AnRerzK+875t5KBQBJEzT n/uyPBYSAJ4wG0gRYEBWCFbTcQ7nPUjiaEdADQ== =fvvf -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
participants (3)
-
Carlos E. R. -
David C. Rankin -
Felix Miata