X server erroring out

RandomTroll · 09-01-2020, 07:31 AM

My X server has quit, reporting the below error, a few times in the last few weeks. I'm not doing anything unusual either in or out of X. Has anyone else seen such behavior?

Quote:

free(): double free detected in tcache 2
(EE)
(EE) Backtrace:
(EE) 0: /usr/libexec/Xorg (OsLookupColor+0x138) [0x58b5c8]
(EE) 1: /lib64/libpthread.so.0 (funlockfile+0x50) [0x7f5a3b6d76df]
(EE) 2: /lib64/libc.so.6 (gsignal+0x9b) [0x7f5a3b520d6b]
(EE) 3: /lib64/libc.so.6 (abort+0x114) [0x7f5a3b501548]
(EE) 4: /lib64/libc.so.6 (__libc_message+0x2ae) [0x7f5a3b567e3e]
(EE) 5: /lib64/libc.so.6 (malloc_printerr+0x1a) [0x7f5a3b56faca]
(EE) 6: /lib64/libc.so.6 (_int_free+0x6fd) [0x7f5a3b5716dd]
(EE) 7: /usr/libexec/Xorg (FreeCursor+0x7d) [0x4334ad]
(EE) 8: /usr/libexec/Xorg (ChangeWindowAttributes+0xa11) [0x46afd1]
(EE) 9: /usr/libexec/Xorg (ProcBadRequest+0x1ec) [0x4397dc]
(EE) 10: /usr/libexec/Xorg (SendErrorToClient+0x334) [0x43f274]
(EE) 11: /usr/libexec/Xorg (InitFonts+0x3a4) [0x443144]
(EE) 12: /lib64/libc.so.6 (__libc_start_main+0xeb) [0x7f5a3b502e5b]
(EE) 13: /usr/libexec/Xorg (_start+0x2a) [0x42deca]
(EE)
(EE)
Fatal server error:
(EE) Caught signal 6 (Aborted). Server aborting

pan64 · 09-01-2020, 07:50 AM

(EE) Caught signal 6 (Aborted). Server aborting

check line 45, I was logged into your box....

berndbausch · 09-01-2020, 09:34 AM

A bug?

RandomTroll · 09-02-2020, 03:12 AM

Quote:

Originally Posted by pan64

check line 45, I was logged into your box....

?

Quote:

Originally Posted by berndbausch

A bug?

That's an old bug but their reports have similarities.

pan64 · 09-02-2020, 03:20 AM

http://www.catb.org/~esr/faqs/smart-...html#beprecise

henderson · 09-02-2020, 02:37 PM

Please post your Xorg log. It's usually /var/log

RandomTroll · 09-03-2020, 07:27 AM

log attached

pan64 · 09-03-2020, 07:32 AM

I still can't see anything more. It was aborted. There is no usable information....

mrmazda · 09-03-2020, 07:42 AM

Quote:

Originally Posted by RandomTroll

log attached

Wrong file type "log" will not open in web browser. If you append ".txt" when attaching then it should open. Better to upload to http://pastebin.com/ or equivalent, where it won't be preserved for eternity.

boughtonp · 09-03-2020, 08:20 AM

Quote:

Originally Posted by mrmazda

Wrong file type "log" will not open in web browser.

Not true - prefix the attachment URL with "view-source:" and Firefox will display it as plain text.

mrmazda · 09-03-2020, 04:33 PM

You think eternity is an appropriate length of time for retaining a troubleshooting log?

What if using something other than Firefox?

boughtonp · 09-04-2020, 06:48 AM

Quote:

Originally Posted by mrmazda

What if using something other than Firefox?

It'll either work, have a close alternative, or should be raised in the other something's issue tracker - it's a useful feature.

RandomTroll · 09-05-2020, 12:41 AM

Quote:

Originally Posted by mrmazda

What if using something other than Firefox?

Opera has worked so far. It's different. I started using Mosaic in the '90s, have gotten used to it.

.log is one of the extensions LQ allows for attachments. It is silly that Firefox treats it as needing a special app.

mrmazda · 09-05-2020, 03:54 AM

Quote:

Originally Posted by RandomTroll

It is silly that Firefox treats it as needing a special app.

There are multiple ancient open bugs about this, and lots of dupes to them, e.g.:

RandomTroll · 09-09-2020, 06:49 PM

I finally crashed in Opera the other day, so it isn't just Firefox.