Page MenuHomePureOS Tracker

matrix-mirage fails to start in PureOS Byzantium arm (L5), but not Byzantium amd64
Closed, ResolvedPublic


This is the output on an L5, with:


And matrix-mirage version:

purism@pureos:~/projetos/debian/output$ dpkg -l | grep "matrix-mirage"
ii  matrix-mirage                            0.6.4~dfsg+~hsluv1.0.0-4                  arm64        desktop IM client for the Matrix protocol


purism@pureos:~/projetos/debian/output$ export DISPLAY=:0
purism@pureos:~/projetos/debian/output$ matrix-mirage 
~ 15:15:40 | Got library name:  "/usr/lib/aarch64-linux-gnu/qt5/qml/io/thp/pyotherside/"
! 15:15:42 | QSystemTrayIcon::setVisible: No Icon set
! 15:15:42 | QObject::connect: No such signal QPlatformNativeInterface::systemTrayWindowChanged(QScreen*)
! 15:15:42 | QWaylandGLContext: failed to create EGLContext, error=3009
F 15:15:42 | Failed to create OpenGL context for format QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(), depthBufferSize 24, redBufferSize -1, greenBufferSize -1, blueBufferSize -1, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 1, colorSpace QSurfaceFormat::DefaultColorSpace, profile  QSurfaceFormat::NoProfile) 
Aborted (core dumped)

On amd64 it just works. and it is the same version:

amd64 version:

joao@librem:~$ dpkg -l | grep "matrix-mirage"
ii  matrix-mirage                                 0.6.4~dfsg+~hsluv1.0.0-4                 amd64        desktop IM client for the Matrix protocol

Event Timeline

joao.azevedo updated the task description. (Show Details)Apr 15 2021, 06:33
joao.azevedo updated the task description. (Show Details)

@jonas.smedegaard since you packaged matrix-mirage you might be curious about this "bug".

In the field of voodoo magic:

If you run the command: QT_QPA_PLATFORM=xcb before launching matrix mirage, then it works.

to me that sounds like there is no bug in the matrix-mirage package but instead a bug in the setup of the environment.

...or arguably not really a bug but your Librem 5 environment is not optimally configured for Qt-based based applications.

Thanks for bringing it to my attention, but sorry: I dont know how to proceed with this maybe-a-bug issue, and will remove myself from the conversation.

maybe-a-bug issue

As for issues I would consider the same version application behaving differently depending only if it is in arch A or B an issue. If that difference in behaviour is due to environment configuration I would also consider a bug. But that is a meta debate.

As for this ticket I'll submit it in the L5 OS issues repo, and close this one here.

joao.azevedo closed this task as Resolved.Apr 15 2021, 10:00