Re: Help with debugging a bug in Konqueror

On luned=C3=AC 13 luglio 2026 21:34:19 Ora legale dell=E2=80=99Europa centr=
ale Zoltan=20
Padrah wrote:
> Stefano Crocco <[email protected]> ezt =C3=ADrta (id=C5=91pont: 202=
6. j=C3=BAl.
>=20
> 13., H, 13:06):
> > > > Given the randomness of the freezes and the fact that the backtrace
> > > > contains
> > > > almost no Konqueror-specific calls, I really have no ideas on how to
> > > > proceed to
> > > > debug the issue, and I really don't even know what to search on the
> > > > web. Do
> > > > you have any advice?
> > > >=20
> > > > Thanks in advance
> > > >=20
> > > > Stefano
> >=20
> > I attach a new backtrace with all threads (compressed because of size).=
 I
> > still can't see anything related to Konqueror. The only thing I can not=
ice
> > is a mention of QDBus in thread 67, but I still don't know what
> > information to get from it. Any other ideas?
> >=20
> > Thanks
> >=20
> > Stefano
>=20
> Hi,
>=20
> just some random ideas, in the hope that they might be useful:
>=20
> (1)
> in the stack traces I see that both the "konqueror" thread and Thread
> 66, "QXcbEventQueue" are waiting on xcb_wait_for_event() .
> I can imagine that somehow these two threads might "steal" X11 events
> from each other, effectively generating some kind of hang.
> This is just a rough theory of mine.
>=20
> (2)
> To verify that a process is really hanging, or it entered some
> low-level looping, you can attach to the process with "strace" and see
> if there is any system call activity.
> If there is activity, then something is happening, but the UI is not
> working as expected;
> If there is no activity at all, then there might be some deadlock or
> infinite waiting happening.
>=20
> Best regards,
>=20
>  Zoltan

Thanks for the hints. Today I won't have time to investigate this issue, bu=
t=20
I'll try them as soon as I have a bit of time.

Stefano