QtDomTerm doesn't work with no error messages.

Question

QtDomTerm doesn't work with no error messages.

opened this issue 4 years ago · comments

After running qtdomterm, I am getting the following window:

The menus can be opened, but all the buttons have zero effect and zero error messages.

Build configuration:

java -version
Picked up _JAVA_OPTIONS:  -Dsun.java2d.uiScale=1.35 -Dawt.useSystemAAFontSettings=on -Dswing.aatext=true -Dswing.defaultlaf=com.sun.java.swing.plaf.gtk.GTKLookAndFeel -Dswing.crossplatformlaf=com.sun.java.swing.plaf.gtk.GTKLookAndFeel
openjdk version "1.8.0_252"
OpenJDK Runtime Environment (IcedTea 3.16.0) (Slackware)
OpenJDK 64-Bit Server VM (build 25.252-b09, mixed mode)

CFLAGS="$SLKCFLAGS" \
./configure \
  --prefix=/usr \
  --sysconfdir=/etc \
  --libdir=/usr/lib${LIBDIRSUFFIX} \
  --mandir=/usr/man \
  --infodir=/usr/info \
  --with-libwebsockets \
  --with-asciidoctor \
  --with-javafx \
  --with-qtwebengine \
  --build=$ARCH-slackware-linux || exit 1

Typing anything into the window also produces no effect.

Per Bothner · Answer 1 · Mon Aug 31 2020 11:12:05 GMT+0800 (China Standard Time)

Which OS/Platform are you using?
Java is not used by qtdomterm, so java -version shouldn't matter.

I haven't tested those configure options, so it is possible something can't find somethings else :-)
Can you run the build in-place, without install? I.e.

./configure ..whatever...
make
bin/domterm --qt

Deleted user · Answer 2 · Mon Aug 31 2020 11:18:59 GMT+0800 (China Standard Time)

I can run it from the build directory with the same result.

Furthermore, running domterm --firefox also produces a blank page in Firefox.

Deleted user · Answer 3 · Mon Aug 31 2020 11:24:03 GMT+0800 (China Standard Time)

This is the list of files produced by the build:

install/
install/slack-desc
usr/
usr/bin/
usr/bin/domterm
usr/bin/qtdomterm
usr/doc/
usr/doc/domterm-2.1/
usr/doc/domterm-2.1/README
usr/doc/domterm-2.1/domterm.info
usr/doc/domterm-2.1/slack-desc
usr/man/
usr/man/man1/
usr/man/man1/domterm.1
usr/man/man1/qtdomterm.1
usr/share/
usr/share/appdata/
usr/share/appdata/domterm.appdata.xml
usr/share/appdata/qtdomterm.appdata.xml
usr/share/applications/
usr/share/applications/domterm.desktop
usr/share/applications/qtdomterm.desktop
usr/share/domterm/
usr/share/domterm/electron/
usr/share/domterm/electron/main.js
usr/share/domterm/electron/package.json
usr/share/domterm/electron/preload.js
usr/share/domterm/help/
usr/share/domterm/help/domterm-attach.html
usr/share/domterm/help/domterm-attach.txt
usr/share/domterm/help/domterm-browse.html
usr/share/domterm/help/domterm-browse.txt
usr/share/domterm/help/domterm-hcat.html
usr/share/domterm/help/domterm-hcat.txt
usr/share/domterm/help/domterm-imgcat.html
usr/share/domterm/help/domterm-imgcat.txt
usr/share/domterm/help/domterm-is-domterm.html
usr/share/domterm/help/domterm-is-domterm.txt
usr/share/domterm/help/domterm-list.html
usr/share/domterm/help/domterm-list.txt
usr/share/domterm/help/domterm-new.html
usr/share/domterm/help/domterm-new.txt
usr/share/domterm/help/domterm-window-specifier.html
usr/share/domterm/help/domterm-window-specifier.txt
usr/share/domterm/help/domterm.html
usr/share/domterm/help/domterm.txt
usr/share/domterm/help/qtdomterm.html
usr/share/domterm/help/qtdomterm.txt

Deleted user · Answer 4 · Mon Aug 31 2020 11:34:47 GMT+0800 (China Standard Time)

The page displayed in Firefox looks has this code:

<!DOCTYPE html>
<html><head>
<base href='http://localhost:42579/'/>
<meta http-equiv='Content-Type' content='text/html; charset=UTF-8'>
<title>DomTerm</title>
<link type='text/css' rel='stylesheet' href='hlib/domterm-core.css'>
<link type='text/css' rel='stylesheet' href='hlib/domterm-standard.css'>
<link type='text/css' rel='stylesheet' href='hlib/goldenlayout-base.css'>
<link type='text/css' rel='stylesheet' href='hlib/jsMenus.css'>
<link type='text/css' rel='stylesheet' href='hlib/domterm-layout.css'>
<link type='text/css' rel='stylesheet' href='hlib/domterm-default.css'>
<script type='text/javascript' src='hlib/domterm.js'> </script>
<script type='text/javascript' src='hlib/domterm-version.js'> </script>
<script type='module' src='hlib/terminal.js'> </script>
<script type='module' src='hlib/domterm-parser.js'> </script>
<script type='module' src='hlib/sixel/Colors.js'> </script>
<script type='module' src='hlib/sixel/SixelDecoder.js'> </script>
<script type='text/javascript' src='hlib/browserkeymap.js'> </script>
<script type='module' src='hlib/commands.js'> </script>
<script type='text/javascript' src='hlib/wcwidth.js'> </script>
<script type='text/javascript' src='hlib/FileSaver.js'> </script>
<script type='text/javascript' src='hlib/ResizeSensor.js'> </script>
<script type='text/javascript' src='hlib/jquery.min.js'> </script>
<script type='text/javascript' src='hlib/goldenlayout.js'> </script>
<script type='text/javascript' src='hlib/domterm-layout.js'> </script>
<script type='text/javascript' src='hlib/domterm-menus.js'> </script>
<script type='text/javascript' src='hlib/qwebchannel.js'> </script>
<script type='text/javascript' src='hlib/jsMenus.js'> </script>
<script type='text/javascript' src='hlib/screenfull.js'> </script>
<script type='text/javascript' src='hlib/domterm-client.js'> </script>
<script type='text/javascript'>
DomTerm.server_port = 42579;
DomTerm.server_key = 'dyehilLvAH8_fVG-RQYF';
</script>
</head>
<body></body>
</html>

Per Bothner · Answer 5 · Mon Aug 31 2020 11:43:31 GMT+0800 (China Standard Time)

"The page displayed in Firefox looks has this code:"

Yes, that looks correct.

I just did:

cd /tmp; mkdir DT
git clone git@github.com:PerBothner/DomTerm.git
cd DomTerm
autoreconf -i
./configure --prefix=/tmp/DT-root --with-qtwebengine --without-asciidoctor --without-docbook
make
make install

and it ran fine, both using /tmp/DT/DomTerm/bin/domterm and /tmp/DT-root/bin/domterm.

Adding --with-webview to configure also works, but make install is missing a dependency for the bin dir.

However, this is on Fedora 32.

Per Bothner · Answer 6 · Mon Aug 31 2020 11:46:23 GMT+0800 (China Standard Time)

One possibility is you have an old/incompatible version of libwebsockets installed on Slackware. If you run bin/domterm status it should tell you the version it is using. Could you try building libwebsockets following the instructions in "Building libwebsockets, if needed" ?

Deleted user · Answer 7 · Mon Aug 31 2020 11:48:02 GMT+0800 (China Standard Time)

lockywolf@delllaptop:/tmp/DomTerm-2.1$ domterm status
DomTerm version 2.1.0
Copyright 2020 Per Bothner and others
Using Libwebsockets 3.1.0
Reading settings from: /home/lockywolf/.config/domterm/settings.ini
Backend command socket: /home/lockywolf/.domterm/default.socket
session#: 1, pid: -1, tty: /dev/pts/4
  (detached)

Per Bothner · Answer 8 · Mon Aug 31 2020 11:49:25 GMT+0800 (China Standard Time)

Libwebsockets 3.1.0 is rather old.
You might consider adding -DLWS_WITHOUT_EXTENSIONS=0 to the cmake line for libwebsockets. I'm not quite sure why or if that is needed, but I made a note about it and forgot why ...

Deleted user · Answer 9 · Mon Aug 31 2020 11:50:38 GMT+0800 (China Standard Time)

Well, the documentation says that 2.2 should be enough.

Per Bothner · Answer 10 · Mon Aug 31 2020 11:51:14 GMT+0800 (China Standard Time)

As an alternative to building libwebsockets, you could try adding --enable-compiled-in-resources to the domterm configure line.

Per Bothner · Answer 11 · Mon Aug 31 2020 11:52:49 GMT+0800 (China Standard Time)

"Well, the documentation says that 2.2 should be enough."

True, but I haven't tested 2.2 in a while, so I might have broken something ... It is also possible 3.1.0 might just happen to be broken but earlier and later versions might work.

Deleted user · Answer 12 · Mon Aug 31 2020 11:53:20 GMT+0800 (China Standard Time)

you could try adding --enable-compiled-in-resources to the domterm configure line.

lockywolf@delllaptop:/tmp/DomTerm-2.1$ domterm --firefox
Segmentation fault (core dumped)

Per Bothner · Answer 13 · Mon Aug 31 2020 11:58:33 GMT+0800 (China Standard Time)

"you could try adding --enable-compiled-in-resources to the domterm configure line."
"Segmentation fault (core dumped)"

All I can say it works for me.
I guess building libwebsockets is the next thing to try.

Per Bothner · Answer 14 · Mon Aug 31 2020 12:02:45 GMT+0800 (China Standard Time)

Another possibility which doesn't use libwebsockets at all is electron-nodepty. This uses Electron for the server-side (not just the display side) so it is quite a bit simpler. However, as you can see from the webpage it is missing some features and is rather more experimental.