Bug 236598 - net-im/spectral: Empty main window
Summary: net-im/spectral: Empty main window
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: Adriaan de Groot
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-03-17 14:05 UTC by p5B2EA84B3
Modified: 2019-04-16 08:26 UTC (History)
0 users

See Also:
adridg: maintainer-feedback+


Attachments
Screenshot of Spectral main window (1.97 KB, image/png)
2019-03-17 14:05 UTC, p5B2EA84B3
no flags Details
Poudriere build log for Spectral (148.00 KB, text/plain)
2019-03-17 14:06 UTC, p5B2EA84B3
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description p5B2EA84B3 2019-03-17 14:05:09 UTC
Created attachment 202933 [details]
Screenshot of Spectral main window

Spectral main window is empty. See attached screenshot.
Comment 1 p5B2EA84B3 2019-03-17 14:06:43 UTC
Created attachment 202934 [details]
Poudriere build log for Spectral
Comment 2 Adriaan de Groot freebsd_committer freebsd_triage 2019-03-23 21:54:43 UTC
Can you get past the initial login screen? (I can't, it just prints error messages about SSL handshakes to stderr on the konsole where I started it) What environment are you running spectral in?
Comment 3 Adriaan de Groot freebsd_committer freebsd_triage 2019-03-25 22:28:56 UTC
Looks like you can use http://matrix.org as the home server (instead of https which is what spectral defaults to) and it can connect. On the other hand, premium hosting via modular.im will redirect to https and then fail.
Comment 4 p5B2EA84B3 2019-03-26 13:37:46 UTC
(In reply to Adriaan de Groot from comment #3)
Clicking randomly in the "empty window" causes this:

 > spectral &
[1] 872
 > DPI: 1
qt5ct: using qt5ct plugin
qt5ct: D-Bus system tray: no
QSystemTrayIcon::setVisible: No Icon set
QKqueueFileSystemWatcherEngine::addPaths: open: No such file or directory
qrc:/imports/Spectral/Panel/RoomListPanel.qml:255: TypeError: Cannot read property 'id' of null
qrc:/imports/Spectral/Panel/RoomListPanel.qml:286: TypeError: Cannot read property 'name' of null
qrc:/imports/Spectral/Panel/RoomListPanel.qml:317: TypeError: Cannot read property 'avatarMediaId' of null
qrc:/imports/Spectral/Panel/RoomListPanel.qml:348: TypeError: Cannot read property 'accessToken' of null
qrc:/imports/Spectral/Panel/RoomListPanel.qml:379: TypeError: Cannot read property 'deviceId' of null
qrc:/imports/Spectral/Panel/RoomListPanel.qml:410: TypeError: Cannot read property 'accessToken' of null

No packets can be seen when monitoring the net interface.
Comment 5 commit-hook freebsd_committer freebsd_triage 2019-04-14 14:15:56 UTC
A commit references this bug:

Author: adridg
Date: Sun Apr 14 14:15:43 UTC 2019
New revision: 498907
URL: https://svnweb.freebsd.org/changeset/ports/498907

Log:
  Missing dependencies for net-im/spectral.

  These are effectively *run* dependencies, since the build is not
  affected; however, installing just spectral without image support
  or QQC2 into a twm environment gives you one that won't start,
  or won't show everything you might encounter in Matrix.

  Doesn't fix the referenced PR, but is related.

  PR:		236598

Changes:
  head/net-im/spectral/Makefile
  head/net-im/spectral/pkg-descr
Comment 6 Adriaan de Groot freebsd_committer freebsd_triage 2019-04-14 14:24:10 UTC
I just updated the port with some missing runtime dependencies, based on installing xorg, twm, and spectral in an otherwise new 11.2 VM. After that it starts and works normally. I still can't reproduce your problem with the empty window, but hope it goes away with the fixed-up dependencies.
Comment 7 Adriaan de Groot freebsd_committer freebsd_triage 2019-04-16 08:26:28 UTC
Tried again (twm, 11-stable), and no issues. None of the warning messages you show, are printed here. It may have something to do with your environment, but that's just guessing. I'm going to close this as "works in twm and KDE Plasma, can't reproduce".  Please do update the port, now that the dependencies are fixed though.