Re: QT program (dock) crashed after screen turn-off

Viet Dang <[email protected]> Fri, 15 Nov 2024 01:19:40 +0000
Newsgroups gmane.comp.kde.devel.kwin
Message-ID <CAO-rTSEtE2Ob1XVtcoHpHc-8krDRFdnL2nrDhobaBotkbCcqyg@mail.gmail.com>
--000000000000270caa0626e95d4c
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Thanks David.

The weird thing is the dock did not crash, per se.
Gdb said "process exited normally" and I did not get any core dump nor
stack trace.
It feels as if when the screen turned off, QScreen object got destroyed and
the dock exited with it.

Anyway I'll create an account on Qt bug report and post it there.

Viet


On Wed, Nov 13, 2024 at 11:18=E2=80=AFPM David Edmundson <david@davidedmund=
son.co.uk>
wrote:

> That code is doing what it says, which is not crashing. If you have a
> crash, you have something else.
> You need to get a backtrace. Please run it in gdb and reproduce.
>
> If you get that, lets see where the issue is. It will probably be Qt,
> which will still be dealing with me, but lets move this to Qt's bug
> tracker.
>
> David
>

--000000000000270caa0626e95d4c
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Thanks David.<br><div><br></div><div>The weird thing is th=
e dock did not crash, per se.=C2=A0</div><div>Gdb said &quot;process exited=
 normally&quot; and I did not get any core dump nor stack trace.</div><div>=
It feels as if when the screen turned off, QScreen object got destroyed and=
 the dock exited with it.</div><div><br></div><div>Anyway I&#39;ll create a=
n account on Qt bug report and post it there.</div><div><br></div><div>Viet=
</div><div><br></div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" =
class=3D"gmail_attr">On Wed, Nov 13, 2024 at 11:18=E2=80=AFPM David Edmunds=
on &lt;<a href=3D"mailto:[email protected]" target=3D"_blank">davi=
[email protected]</a>&gt; wrote:<br></div><blockquote class=3D"gmail_q=
uote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,2=
04);padding-left:1ex">That code is doing what it says, which is not crashin=
g. If you have a<br>
crash, you have something else.<br>
You need to get a backtrace. Please run it in gdb and reproduce.<br>
<br>
If you get that, lets see where the issue is. It will probably be Qt,<br>
which will still be dealing with me, but lets move this to Qt&#39;s bug<br>
tracker.<br>
<br>
David<br>
</blockquote></div>

--000000000000270caa0626e95d4c--