chat window not available

• OS: Artix GNU + Linux (AUR package)

• Jami version: built from head of master (3f27289f)

• What build you are using: AUR - https://aur.archlinux.org/packages/jami-client-qt-git (head of master, currently, 3f27289f)

• Can you reproduce the bug: at will (always)

• Steps:

  1. Just start jami, and I get the image 2. No matter how many times I click on the contacts' at the left, the chat window on the right never shows, up, only the jami advertising window remains. Even if a contact writes to me, or myself (from the phone), I can't get to the chat window to reply... ...

• Actual result: No way to access any contact chat window.

• Expected result: When clicking on a contact, the chat window should be visible, instead of the jami advertising one.

We don't provide packages for arch and it's community managed.

But probably a bugguy Qt version. Logs from client may show an error and should be the first thing to check

From the "get logs" in the "troubleshoot" setting section, I only get:

[1632021435.097| 2141|manager.cpp       :946  ] ############## START MONITORING ##############
[1632021435.097| 2141|manager.cpp       :947  ] Using PJSIP version 2.11 for x86_64-pc-linux-gnu
[1632021435.097| 2141|manager.cpp       :948  ] Using GnuTLS version 3.7.2
[1632021435.098| 2141|manager.cpp       :949  ] Using OpenDHT version 2.2.0
[1632021435.098| 2141|manager.cpp       :955  ] Opened files: 24
[1632021435.098| 2141|jamiaccount.cpp   :4366 ] [Account ed53be20ec32d356] Monitor connections
[1632021435.098| 2141|connectionmanager.cpp:1100 ] ConnectionManager for account ed53be20ec32d356 (jami:je-vv), current status:
[1632021435.098| 2141|connectionmanager.cpp:1107 ] ConnectionManager for account ed53be20ec32d356 (jami:je-vv), end status.
[1632021435.098| 2141|manager.cpp       :964  ] ############## END MONITORING ##############

And running from console with "-d":

% jami-qt -d
"notify server name: lxqt-notificationd, vendor: lxqt.org, version: 0.17.0, spec: 1.2"
No migration required
Can't open file:  "/home/general/.local/share/jami/ed53be20ec32d356/profile.vcf"
Cannot find dbus interface for screen saver
QDBusConnection: name 'cx.ring.Ring' had owner '' but we thought it was ':1.64'
Syncing lrc accounts list with the daemon
NetworkManager client initialized, version:   , daemon running: no , networking enabled: no
no primary network connection detected, check network settings
qrc:/src/mainview/MainView.qml:470:5: QML AboutPopUp: Binding loop detected for property "height"
NewAccountModel::getAccountInfo, can't find dummy ; Using default avatar
NewAccountModel::getAccountInfo, can't find dummy ; Using default avatar

Is there any other way to generate logs (perhaps even the way to get the logs from the "troubleshoot" section is not working fine, since it doesn't keep getting logs, it seems it just gets a snapshot)?

seems working, but the logs for the client are more interesting for this (so jami-qt -d).

not related but libnm seems no there. But yeah if you open the chatview, I guess an error will pop. Else --remote-debugging-port can launch the chatview debug.

Also, is libqt built with webengine support?

libnm is installed from official repos, version 1.32.10. Qt, also from official repos, qt5 version 5.15, is built with webengine support...

Now, with --remote-debugging-port, I can see a couple of extra lines on the console:

% jami-qt -d --remote-debugging-port                                                                                                                                                                                               
"notify server name: lxqt-notificationd, vendor: lxqt.org, version: 0.17.0, spec: 1.2"
No migration required
Can't open file:  "/home/general/.local/share/jami/ed53be20ec32d356/profile.vcf"
Cannot find dbus interface for screen saver
QDBusConnection: name 'cx.ring.Ring' had owner '' but we thought it was ':1.51'
Syncing lrc accounts list with the daemon
NetworkManager client initialized, version:   , daemon running: no , networking enabled: no
no primary network connection detected, check network settings
Invalid port given for the inspector server "". Examples of valid input: "12345" or "192.168.2.14:12345" (with the address of one of this host's network interface).
qrc:/src/mainview/MainView.qml:470:5: QML AboutPopUp: Binding loop detected for property "height"
NewAccountModel::getAccountInfo, can't find dummy ; Using default avatar
NewAccountModel::getAccountInfo, can't find dummy ; Using default avatar
"slotCallStateChanged (call: 7100313643219782), from Searching to Finished"
"slotCallStateChanged (call: 7100313643219782), from Finished to Finished"
Invalid JSON:  ""
js: Uncaught ReferenceError: addMessage is not defined
"slotCallStateChanged (call: 7468383267034186), from Searching to Finished"
"slotCallStateChanged (call: 7468383267034186), from Finished to Finished"
Invalid JSON:  ""
js: Uncaught ReferenceError: addMessage is not defined

But I can't tell if as revealing.

addMessage not defined.

So, lrc not there (https://git.jami.net/savoirfairelinux/jami-libclient/-/blob/master/src/web-chatview/chatview.js#L2271) or not linked

lrc? Should I install/build something, and then rebuild libjamiclient, jami-daemon and jami-client-qt? Thanks !

it's part of libjamiclient. (https://git.jami.net/savoirfairelinux/jami-libclient/-/blob/master/src/web-chatview/chatview.js#L2271)

Ohh, then it's so weird, since libjamiclient is a dependency for jami-client-qt, and it's built before jami-client-qt, :( And the jami-client-qt is built so standard, that's it's weird it wouldn't link against libjamiclient...

build() {
    cd jami-client-qt
    mkdir -p build
    cd build
    # /usr is necessary for Arch; see https://archlinux.org/news/binaries-move-to-usrbin-requiring-update-intervention/
    cmake .. -DCMAKE_INSTALL_PREFIX="${pkgdir}/usr"
    make -j`nproc` # -j`nproc` uses as many cores as possible to speed up the build
}

package() {
    cd jami-client-qt/build
    make install
}

BTW, libjamiclient is also head of master, and right now up to date (bbda1066), and it's also built pretty straight forward:

build() {
  cd build
  cmake ../ring-lrc \
    -DCMAKE_INSTALL_PREFIX=/usr \
    -DCMAKE_BUILD_TYPE=Release
  make
}

package() {
  cd build
  make DESTDIR="${pkgdir}" install
}

So I can't guess why that functionality seems missing from the Qt client...

In the cmake from client-qt, what is the value of LRC_SRC_PATH for

# common executable sources
add_executable(${PROJECT_NAME}
               ${SRC_DIR}/main.cpp
               ${COMMON_HEADERS}
               ${COMMON_SOURCES}
               ${QML_RESOURCES}
               ${QML_RESOURCES_QML}
               ${LRC_SRC_PATH}/webresource.qrc)

and does this path is valid?

But yeah, seems nothing to do from our side, build is ok on all distrib we provide.

I added a meesage line before that piece of code, and besides there's another message line before indicating that path:

    message("Will expect lrc headers in ${LRC_SRC_PATH}")

    include_directories(${LRC_SRC_PATH}
                        ${LIBNM_INCLUDE_DIRS}
                        ${LIBNOTIFY_INCLUDE_DIRS}
                        ${LIBGDKPIXBUF_INCLUDE_DIRS}
                        ${GLIB_INCLUDE_DIRS})
...
# common executable sources
message("Hey:  LRC_SRC_PATH:  ${LRC_SRC_PATH}")
add_executable(${PROJECT_NAME}
               ${SRC_DIR}/main.cpp
               ${COMMON_HEADERS}
               ${COMMON_SOURCES}
               ${QML_RESOURCES}
               ${QML_RESOURCES_QML}
               ${LRC_SRC_PATH}/webresource.qrc)

And here it is the output:

Will expect lrc headers in /usr/include/libringclient
Hey:  LRC_SRC_PATH:  /usr/include/libringclient

And there you can find:

% ls /usr/include/libringclient/
api/                       directrenderer.h   messageslist.h              shmrenderer.h   uri.h    web-chatview/
containerview.h            globalinstances.h  namedirectory.h             smartinfohub.h  vcard.h  webresource.qrc
dbuserrorhandlerdefault.h  interfaces/        pixmapmanipulatordefault.h  typedefs.h      video/

Seems ok to me, so yeah I have no clue. I don't have any problem on 4 other distrib on master.

So yeah, maybe a clean + update + complete rebuild will fix it. AS it's master, maybe when you built it the master was wrong on one repo.

Last possibility if a rebuild is not working is to wait, because somebody is working on removing the webview (for the chatview): https://review.jami.net/q/topic:qml-chatview+-is:abandoned

Thanks a lot @sblin, it seems I have to wait. I'll try when those are merged in master...

But on arch (pinephone) it was working two weeks ago without any issue

Pinephone's CPU, whether manjaro of arch-arm, is ARM, whereas Arch and Artix are X86 only. The other thing is that perhaps it's using the GTK client, not the Qt one, not sure (I have in plan experimenting with pinephone, but I haven't yet)... Arch actually has the GTK client on its official repos, but I prefer and use the Qt client when available (which is the case for jami-client). I prefer even building from the AUR repo, which is what I'm doing, than using official GTK clients...

In brief, I'll wait for the changes you mentioned, to try again...

Yeah but it's the only arch I have. Else, I have a lot of x86_64 desktop on GNU/Linux, and all the versions we are releasing on master don't have this problem.

For the pinephone, I build the client-qt from master, So I confirm it's the client-qt I use.

I see. If you want, you can close this issue for now, since I'm the only one reporting the issue. I subscribed to the corresponding gitlab issues to the 2 topics you mentioned, and hopefully, when they are closed, I'll try again, and whether things work well by then, or there are new issues to follow up, and by then I can see if re-opening this one... Thanks a lot !

Yeah will monitor if I see similar issues and will re-open if needed.

closed

added non-reproducible label