Index | Thread | Search

From:
Ethan <ethan@yonderly.org>
Subject:
Re: moonlight-qt broken in 7.8
To:
Rafael Sadowski <rafael@sizeofvoid.org>
Cc:
ports@openbsd.org
Date:
Fri, 24 Oct 2025 16:22:30 -0400

Download raw body.

Thread
sorry if i sent this twice, i believe my first reply didn't go through.

On Fri, 24 Oct 2025 07:15:04 +0200
Rafael Sadowski <rafael@sizeofvoid.org> wrote:

> On Thu Oct 23, 2025 at 04:46:07PM -0400, Ethan wrote:
> > after updating to 7.8, moonlight-qt crashes when connecting to a
> >  server. i installed a snapshot and built it from ports but the
> > issue persists.
> 
> Could you try starting it with an empty config/cache. It starts
> without issues here.

i deleted the moonlight directories in .config and .cache, and re-paired
to the server. moonlight still crashes when connecting with the
same error.

> > 
> > thanks.
> > 
> > $ sysctl -n kern.version
> > OpenBSD 7.8-current (GENERIC.MP) #66: Tue Oct 21 15:42:41 MDT 2025
> >     deraadt@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> > 
> > 
> > output when running:
> > $ moonlight-qt
> > ...
> > 00:00:05 - Qt Fatal: ASSERT: "m_QtWindow != nullptr" in file
> >  /usr/ports/pobj/moonlight-qt-6.1.0/app/streaming/session.cpp,
> >  line 1269
> > Abort trap (core dumped)
> > 
> > backtrace:
> > ll () at /tmp/-:2
> > #1  0xbb526766e028663d in ?? ()
> > #2  0x000004a4640f3fbb in _libc_abort ()
> >     at /usr/src/lib/libc/stdlib/abort.c:51
> > #3  0x000004a49a8d400d in qAbort () from
> >  /usr/local/lib/libQt6Core.so.6.0
> > #4  0x000004a49a8d99e5 in 
> >  _ZL10qt_message9QtMsgTypeRK18QMessageLogContextPKcP13__va_list_tag
> > () from /usr/local/lib/libQt6Core.so.6.0
> > #5  0x000004a49a8dfa4f in QMessageLogger::fatal ()
> >    from /usr/local/lib/libQt6Core.so.6.0
> > #6  0x000004a49a8d40a9 in qt_assert () from
> >  /usr/local/lib/libQt6Core.so.6.0
> > Segmentation fault (core dumped)
> > 


--