Skip to content
This repository has been archived by the owner on May 22, 2023. It is now read-only.

Empty UI #55

Open
OlegHahm opened this issue Jul 4, 2022 · 2 comments
Open

Empty UI #55

OlegHahm opened this issue Jul 4, 2022 · 2 comments

Comments

@OlegHahm
Copy link

OlegHahm commented Jul 4, 2022

When I start siggo, I just get an empty UI without any further messages. I used siggo link to link the device and can retrieve the JSON data successfully.
I'm running Arch Linux:

$ java --version
openjdk 18.0.1.1 2022-04-22
OpenJDK Runtime Environment (build 18.0.1.1+2)
OpenJDK 64-Bit Server VM (build 18.0.1.1+2, mixed mode)
$ uname -a
Linux applecore 5.18.8-arch1-1 #1 SMP PREEMPT_DYNAMIC Wed, 29 Jun 2022 23:03:08 +0000 x86_64 GNU/Linux
@jspraul
Copy link

jspraul commented Aug 15, 2022

Turn on the log file at the end of ~/.config/siggo/config.yml

The first command it runs seems to be: signal-cli -o json -u [s.uname (full phone number)] daemon but in my case it doesn't detect a failure accessing dbus... it just logs the following over & over:

time="2022-08-15T00:33:44-04:00" level=info msg="starting dbus daemon..."
time="2022-08-15T00:33:44-04:00" level=info msg="scanning stdout"
time="2022-08-15T00:33:44-04:00" level=info msg="starting dbus daemon..."
time="2022-08-15T00:33:44-04:00" level=info msg="scanning stdout"

@derricw
Copy link
Owner

derricw commented Sep 27, 2022

Hey everyone. Sorry I have had a third kid and unfortunately haven't maintained this project very well. I think that many problems can be solved by using signal-cli version 0.9.2. This is the last version of signal-cli that I have had the opportunity to test with.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants