Jami-qt built with QT6 has some problem on NixOS

I'm packaging the new version of jami-qt with QT6. I got some problems.

1. The window's titlebar doesn't follow system theme.
2. The window can't be resized.
3. The wnclass of the window is net.jami..

Could you please help?

which commits and Qt version do you use? X11 or Wayland?

1. May be normal, I think it's a Qt 6 issue.

2/3 are not normal, 3, the code is in main.cpp:

    QApplication::setApplicationName("Jami");
    QApplication::setOrganizationDomain("jami.net");

What backend is used and if you want, in jami-project, we compile our own Qt for .deb and .rpm if you want to compare.

But those issues seems more related to Qt than Jami (we do not really manage those aspects, it's rendered by Qt)

The jami version is 20220503.1550.0f35faa, qt version is 6.3.0, on Gnome wayland.

It uses wayland backend by default. With xcb backend it crashes on NixOS.

3, the code is in main.cpp:

I'll do some tests.

On Fedora (GNOME Wayland) with Qt 6.2.3 (we use this version for jami-libqt), OpenGL backend and both "QT_QPA_PLATFORM=wayland" and "QT_QPA_PLATFORM=xcb" there is no issue (no crash, no resize issue).

0f35faa should be ok, as we disabled Vulkan on this release so it should uses OpenGL (as Qt with vulkan doesn't have any window decoration on Wayland)

The wmclass should be net.jami.Jami but only the net.jami. part is set. Any idea what's the problem?

none, I don't see anything that can generate this, in the sources there is always net.jami.Jami (same in the appdata)

I thought the crash on xcb is a NixOS related issue. On wayland here is the log

Using Qt runtime version: 6.3.0
"notify server name: gnome-shell, vendor: GNOME, version: 42.1, spec: 1.2"
qt.webenginecontext: 

GL Type: desktop
Surface Type: OpenGL
Surface Profile: CompatibilityProfile
Surface Version: 4.6
QSG RHI Backend: OpenGL
Using Supported QSG Backend: yes
Using Software Dynamic GL: no
Using Multithreaded OpenGL: yes

Init Parameters:
  *  application-name Jami 
  *  browser-subprocess-path /nix/store/r3q12jpvq15rf9gcxrpyns1x183brnbw-qtwebengine-6.3.0-dev/libexec/ 
  *  create-default-gl-context  
  *  disable-features ConsolidatedMovementXY,InstalledApp,BackgroundFetch,WebOTP,WebPayments,WebUSB,PictureInPicture 
  *  disable-setuid-sandbox  
  *  disable-speech-api  
  *  disable-web-security  
  *  enable-features NetworkServiceInProcess,TracingServiceInProcess 
  *  enable-threaded-compositing  
  *  in-process-gpu  
  *  single-process  
  *  use-gl desktop 

"Using locale: zh_CN"
No migration required
could not update message status for not existing conversation
Screen saver dbus interface:  "org.freedesktop.ScreenSaver"
Binding on contentItem is not deferred as requested by the DeferredPropertyNames class info because one or more of its sub-objects contain an id.
Binding on contentItem is not deferred as requested by the DeferredPropertyNames class info because one or more of its sub-objects contain an id.
Main window loaded using OpenGLRhi
qt.core.qobject.connect: QObject::connect: No such signal QPlatformNativeInterface::systemTrayWindowChanged(QScreen*)
Binding on contentItem is not deferred as requested by the DeferredPropertyNames class info because one or more of its sub-objects contain an id.
Binding on contentItem is not deferred as requested by the DeferredPropertyNames class info because one or more of its sub-objects contain an id.
Binding on background is not deferred as requested by the DeferredPropertyNames class info because one or more of its sub-objects contain an id.
Binding on background is not deferred as requested by the DeferredPropertyNames class info because one or more of its sub-objects contain an id.
Binding on background is not deferred as requested by the DeferredPropertyNames class info because one or more of its sub-objects contain an id.
Binding on background is not deferred as requested by the DeferredPropertyNames class info because one or more of its sub-objects contain an id.
Binding on background is not deferred as requested by the DeferredPropertyNames class info because one or more of its sub-objects contain an id.
Binding on contentItem is not deferred as requested by the DeferredPropertyNames class info because one or more of its sub-objects contain an id.
Syncing lrc accounts list with the daemon
NetworkManager client initialized, version:  1.36.4 , daemon running: yes , networking enabled: yes
primary network connection: c8319e7b-0462-4ea1-9dc2-95605fa6848a default:  yes
Binding on contentItem is not deferred as requested by the DeferredPropertyNames class info because one or more of its sub-objects contain an id.
Binding on contentItem is not deferred as requested by the DeferredPropertyNames class info because one or more of its sub-objects contain an id.
Binding on background is not deferred as requested by the DeferredPropertyNames class info because one or more of its sub-objects contain an id.
Binding on background is not deferred as requested by the DeferredPropertyNames class info because one or more of its sub-objects contain an id.
Binding on contentItem is not deferred as requested by the DeferredPropertyNames class info because one or more of its sub-objects contain an id.
Binding on popup is not deferred as requested by the DeferredPropertyNames class info because one or more of its sub-objects contain an id.
Binding on indicator is not deferred as requested by the DeferredPropertyNames class info because one or more of its sub-objects contain an id.
Binding on indicator is not deferred as requested by the DeferredPropertyNames class info because one or more of its sub-objects contain an id.
Binding on background is not deferred as requested by the DeferredPropertyNames class info because one or more of its sub-objects contain an id.
Binding on background is not deferred as requested by the DeferredPropertyNames class info because one or more of its sub-objects contain an id.
Binding on contentItem is not deferred as requested by the DeferredPropertyNames class info because one or more of its sub-objects contain an id.
Binding on popup is not deferred as requested by the DeferredPropertyNames class info because one or more of its sub-objects contain an id.
Binding on contentItem is not deferred as requested by the DeferredPropertyNames class info because one or more of its sub-objects contain an id.
Binding on popup is not deferred as requested by the DeferredPropertyNames class info because one or more of its sub-objects contain an id.
Binding on contentItem is not deferred as requested by the DeferredPropertyNames class info because one or more of its sub-objects contain an id.
qrc:/src/mainview/components/AboutPopUp.qml:57:13: QML MaterialLineEdit: Binding loop detected for property "implicitWidth"
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Destroying connectivity monitor

I just found that the window can be resized. The cursor doesn't change on the edge so I thought that the window can't be resized. It seems related to the Gnome wayland issue. I still have no idea why setApplicationName doesn't work.

Yeah to be honest, I'm not sure we can help as the 3 issues seems more related to Qt6 or NixOs than Jami

I guess with a minimal Qt application just changing the title, the bug will be the same

After update on Arch Linux I got this:

Is it Qt6 or Jami related?

If I'm not mistaken this is managed by jami-qt.desktop icon=jami should search in

%{_datadir}/icons/hicolor/scalable/apps/jami.*

So if the .desktop file is installed and the icon, it should be correct.

Also, I'm not sure why the application at the left got the icon.

The icon on the left is the right icon representing the /usr/share/applications/jami-qt.desktop. But after I click on it, gnome-shell for some reason can't determine that the Jami main window belongs to this desktop file, and creates a separate icon for it (on the right).

In your case the wmclass is net.jami.jami-qt and in my case it's net.jami. . I doube that the QApplication::setApplicationName("Jami"); doesn't work and the name fallbacks to something else.

All these commands give empty results, so Qt6 generates this string dynamically. Looks like a Qt6 issue.

$ fgrep -ri 'net.jami.jami-qt' ~/jami-client-qt/
$ fgrep -ri 'net.jami.jami-qt' ~/lrc/
$ strings /usr/bin/jami-qt |fgrep -i 'net.jami.jami-qt'
$ strings /usr/lib/libringclient.so |fgrep -i 'net.jami.jami-qt'

the weird thing is that I never saw that for our packages (opensuse, fedora, debian, ubuntu, etc), it's weird.

On Fedora (GNOME Wayland) with Qt 6.2.3

Have you tried with Qt 6.3.0?

6.2 is the LTS and got patches from 6.3.0 (6.2.5 is our next target) ; But no I didn't test 6.3 yet

Init Parameters:
  *  application-name Jami 

It seems the application-name is set correctly.

There is no issue with QT_QPA_PLATFORM=xcb jami-qt, only with QT_QPA_PLATFORM=wayland jami-qt. So I will force to use XWayland until it will be fixed.

QT_QPA_PLATFORM=xcb will not work on NixOS if I understand, but it's interesting. I know the Wayland backend is still not ready for Qt. Vulkan's backend for example on wayland doesn't work

The xcb problem is fixed in https://github.com/NixOS/nixpkgs/pull/174287. With xcb the wmclass is correct.

This is the code from QWaylandWindow::initWindow() which generates this string:

        mShellSurface = mDisplay->shellIntegration()->createShellSurface(this);
        if (mShellSurface) {
            // Set initial surface title
            setWindowTitle(window()->title());

            // The appId is the desktop entry identifier that should follow the
            // reverse DNS convention (see http://standards.freedesktop.org/desktop-entry-spec/latest/ar01s02.html).
            // According to xdg-shell the appId is only the name, without
            // the .desktop suffix.
            //
            // If the application specifies the desktop file name use that
            // removing the ".desktop" suffix, otherwise fall back to the
            // executable name and prepend the reversed organization domain
            // when available.
            if (!QGuiApplication::desktopFileName().isEmpty()) {
                QString name = QGuiApplication::desktopFileName();
                if (name.endsWith(QLatin1String(".desktop")))
                    name.chop(8);
                mShellSurface->setAppId(name);
            } else {
                QFileInfo fi = QFileInfo(QCoreApplication::instance()->applicationFilePath());
                QStringList domainName =
                        QCoreApplication::instance()->organizationDomain().split(QLatin1Char('.'),
                                                                                 Qt::SkipEmptyParts);

                if (domainName.isEmpty()) {
                    mShellSurface->setAppId(fi.baseName());
                } else {
                    QString appId;
                    for (int i = 0; i < domainName.count(); ++i)
                        appId.prepend(QLatin1Char('.')).prepend(domainName.at(i));
                    appId.append(fi.baseName());
                    mShellSurface->setAppId(appId);
                }
            }
            // the user may have already set some window properties, so make sure to send them out
            for (auto it = m_properties.cbegin(); it != m_properties.cend(); ++it)
                mShellSurface->sendProperty(it.key(), it.value());
        } else {
            qWarning("Could not create a shell surface object.");
        }

Setting QGuiApplication::desktopFileName manually (it is empty for both QT_QPA_PLATFORM=xcb jami-qt and QT_QPA_PLATFORM=wayland jami-qt by default) solves the issue with a separate icon on Wayland.

Patch: https://review.jami.net/c/jami-client-qt/+/21828 .

But I don't understand how it works with X11. If the shell provides information about the desktop file with some environment variable, Qt on Wayland should also use this automatically.

Qt on Wayland should also use this automatically.

And seems ok on most platform, I don't have such an issue on Fedora on Ubuntu Wayland :/

One of the weird Qt bugs... cause "Jami" is converted into a QString...

cause "Jami" is converted into a QString

This conversion can be disabled with QT_NO_CAST_FROM_ASCII.

maybe it's disabled on NixOS? But only on wayland?

I guess not, at least I didn't find this string in the nixpkgs repo.

mentioned in commit 8100cf56

The window's titlebar doesn't follow system theme.

@linsui See the solution on ArchWiki. For Qt6 the package is named qgnomeplatform-qt6.

I thought this is enabled on NixOS gnome by default for QT5. Maybe the problem is only about QT6. I'll check that. Thanks!

@linsui on current master, there is now some code to change the theme of the app between dark/white following the color-scheme preference (or the gtk-theme if found). However the header bar is not managed by us.

For the rest of the issues, I think we discussed all the points? Seems un-related to Jami but mainly Qt/Wayland, so bugs should be opened on Qt's bugtracker if there is still some un-resolved issues.

I think we can close

Yes, thanks!

closed