Wednesday, October 16, 2024

Re: 7.6 - pinentry-qt* crashes my X session (looks rather like a xenocara problem)

On Sun, Oct 13, 2024 at 04:44:52PM +0200, Piotr K. Isajew wrote:

> On Sun, Oct 13, 2024 at 01:42:54PM +0200, Rafael Sadowski
> wrote:
>
> > Successfully tested without any crashes, but I have to mention
> > that I tested it with an upcoming version of Qt6 and KDE
> > Frameworks which will committed hopefully next week.
>
> Thanks. Good to know. I'll give it another try once those are
> available.

Turns out this was not a pinentry-qt* problem (although
pinentry-qt6 was a way to trigger this issue in 100% reproducible
way for my setup). I have just got the same X crash when
switching to anther desktop in fvwm. Xsession just dies,
returning to xenodm login screen, and here's what I see in the
.xsession-errors:

assertion "ret != inval_id" failed: file "/usr/xenocara/lib/libX11/src/xcb_io.c"
, line 626, function "_XAllocID"
[30680:10069431718976:1017/075647.154756:FATAL:bus.cc(1246)] D-Bus connection wa
s disconnected. Aborting.
[30680:10069431713856:1017/075647.154808:FATAL:bus.cc(1246)] D-Bus connection wa
s disconnected. Aborting.
xterm: fatal IO error 35 (Resource temporarily unavailable) or KillClient on X s
erver ":0"
X connection to :0 broken (explicit kill or server shutdown).
X connection to :0 broken (explicit kill or server shutdown).
[58955:6085286975368:1017/075647.215445:ERROR:connection.cc(61)] X connection error received.
xterm: fatal IO error 35 (Resource temporarily unavailable) or KillClient on X server ":0"
X IO Error
Trace/BPT trap (core dumped)

No comments:

Post a Comment