[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#57364: 28.1.91; asynchronous X server error when creating a second f
From: |
andrés ramírez |
Subject: |
bug#57364: 28.1.91; asynchronous X server error when creating a second frame on alternate DISPLAY |
Date: |
Fri, 26 Aug 2022 03:43:41 +0000 |
Hi. Po.
>>>>> "Po" == Po Lu <luangruo@yahoo.com> writes:
[...]
Po> Ah, that explains it. x-command-line-resources doesn't take effect if
you run with "-Q",
Po> try "-q" instead.
As tested before. after s/Q/q the error does NOT show.
>> And also take in account, that the error is not reproducible in this
condition.
Po> I think I've seen this somewhere. Does the error still happen if you
build
Po> "--without-cairo"?
It does NOT happen If You use --without-cairo. Perhaps this could be a
workaround for my case. But I still think We should try to find the
offending line. WDYT?
>> I have had a question on my mind? Inspecting the last backtrace I have
published on this bug
>> report.
>>
>> I see the error is recovered in a call on the function x_frame_highlight
(within the call to
>> x_catch_error). Why If I am calling close-display-connection. Some
functions need to be
>> called?
Po> Functions can be called on the display being closed while handling
async input from that
Po> display, or when performing cleanup tasks. Unless, of course, the
display is down, but that
Po> is rarely the case when you manually call
close-display-connection/delete-terminal.
for cleanup tasks it's ok. But for x_frame_highlight. I am getting rid
of all the X-frames on this display. Is there a way of avoiding calling
that function in case of close-display-connections.
Best Regards
- bug#57364: 28.1.91; asynchronous X server error when creating a second frame on alternate DISPLAY, Andrés Ramírez, 2022/08/23
- bug#57364: 28.1.91; asynchronous X server error when creating a second frame on alternate DISPLAY, Po Lu, 2022/08/23
- bug#57364: 28.1.91; asynchronous X server error when creating a second frame on alternate DISPLAY, andrés ramírez, 2022/08/25
- bug#57364: 28.1.91; asynchronous X server error when creating a second frame on alternate DISPLAY, andrés ramírez, 2022/08/25
- bug#57364: 28.1.91; asynchronous X server error when creating a second frame on alternate DISPLAY, Po Lu, 2022/08/25
- bug#57364: 28.1.91; asynchronous X server error when creating a second frame on alternate DISPLAY, andrés ramírez, 2022/08/25
- bug#57364: 28.1.91; asynchronous X server error when creating a second frame on alternate DISPLAY, Po Lu, 2022/08/25
- bug#57364: 28.1.91; asynchronous X server error when creating a second frame on alternate DISPLAY,
andrés ramírez <=
- bug#57364: 28.1.91; asynchronous X server error when creating a second frame on alternate DISPLAY, Po Lu, 2022/08/26
- bug#57364: 28.1.91; asynchronous X server error when creating a second frame on alternate DISPLAY, andrés ramírez, 2022/08/26
- bug#57364: 28.1.91; asynchronous X server error when creating a second frame on alternate DISPLAY, Po Lu, 2022/08/26
- bug#57364: 28.1.91; asynchronous X server error when creating a second frame on alternate DISPLAY, andrés ramírez, 2022/08/29
- bug#57364: 28.1.91; asynchronous X server error when creating a second frame on alternate DISPLAY, Po Lu, 2022/08/29
- bug#57364: 28.1.91; asynchronous X server error when creating a second frame on alternate DISPLAY, andrés ramírez, 2022/08/30
- bug#57364: 28.1.91; asynchronous X server error when creating a second frame on alternate DISPLAY, Po Lu, 2022/08/30
- bug#57364: [PATCH] (was: bug#57364: 28.1.91; asynchronous X server error when creating a second frame on alternate DISPLAY), andrés ramírez, 2022/08/30
- bug#57364: [PATCH], Po Lu, 2022/08/30
bug#57364: 28.1; emacs segfaulted when debugging emacs form within emacs for bug#57364, Andrés Ramírez, 2022/08/30