Signal app doesn't start (Fedora)

[Crowphale]

Within the fedora-31 template, I installed Signal[1] messaging app, using Copr:

sudo dnf copr enable luminoso/Signal-Desktop

sudo dnf install signal-desktop

Then, I enabled Signal in "personal" domain, and restarted. However, when I try to start Signal using the GUI, nothing happens.

Is there a way to start an app using commandline or somehow so that I can see some sort of debug log so that I can figure out what's going on?

Thank you very much for any tips.

-Crowphale

Sent with ProtonMail Secure Email.

[Qubes]

> Sent with [ProtonMail](https://protonmail.com) Secure Email.
>
You should be able to start Signal from a terminal in your AppVM which
should provide output if there is any.

[Crowphale]

Sorry for stupid question, but how do I start Signal (or any app) from terminal? Is there some qvm-* command? Or how do I find the Signal binary?

Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

On Thursday, August 20, 2020 2:11 PM, Qubes <qube...@ak47.co.za> wrote:

> On 8/20/20 7:50 PM, 'Crowphale' via qubes-users wrote:
>
> > Within the fedora-31 template, I installed Signal[1] messaging app, using Copr:
> > sudo dnf copr enable luminoso/Signal-Desktop
> > sudo dnf install signal-desktop
> > Then, I enabled Signal in "personal" domain, and restarted. However, when I try to start Signal using the GUI, nothing happens.
> > Is there a way to start an app using commandline or somehow so that I can see some sort of debug log so that I can figure out what's going on?
> > Thank you very much for any tips.
> > -Crowphale

> > Sent with ProtonMail Secure Email.

>
> You should be able to start Signal from a terminal in your AppVM which
> should provide output if there is any.
>

> --------------------------------------------------------------------------------------------------------------
>
> You received this message because you are subscribed to the Google Groups "qubes-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/7d2342eb-d7de-4a88-b385-9dd905dfa76d%40ak47.co.za.

[Steve Coleman]

On Sat, Aug 22, 2020 at 10:50 PM 'Crowphale' via qubes-users <qubes...@googlegroups.com> wrote:

Sorry for stupid question, but how do I start Signal (or any app) from terminal? Is there some qvm-* command? Or how do I find the Signal binary?

I have not installed signal but I'll at least try to help.

Open a terminal in your AppVM.

At the prompt type "signal" then press enter. 

If it doesn't start then try:

   "whereis signal"

   or

   "man -k signal" for help.  

If it installed normally in your template it is likely installed and mounted as /usr/bin/signal

If you find it, then you can start the app from dom0 with the qvm-run command:

dom0> qvm-run -a <AppVM> </path/to/signal>

Just replace the <> in the above with the appropriate info.

[Crowphale]

Making progress...

Found the Signal binary:

[user@crowphale ~]$ ls -l /usr/bin/signal-desktop

lrwxrwxrwx 1 root root 40 Aug  6 11:17 /usr/bin/signal-desktop -> /usr/lib64/signal-desktop/signal-desktop

[user@crowphale ~]$ ls -l /usr/lib64/signal-desktop/signal-desktop

-rwxr-xr-x 1 root root 116480632 Aug  6 11:17 /usr/lib64/signal-desktop/signal-desktop

But trying to run it gives me 127:

[user@dom0 ~]$ qvm-run -a crowphale /usr/lib64/signal-desktop/signal-desktop

Running '/usr/lib64/signal-desktop/signal-desktop' on crowphale

crowphale: command failed with code: 127

Trying to run it directly in the AppVM terminal (probably wrong thing to do), gives me:

[user@crowphale ~]$ signal-desktop

signal-desktop: error while loading shared libraries: libXss.so.1: cannot open shared object file: No such file or directory

I'm stuck. Any ideas?

Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

[Steve Coleman]

On Wed, Aug 26, 2020, 5:53 PM Crowphale <crow...@protonmail.com> wrote:

Making progress...

Found the Signal binary:

[user@crowphale ~]$ ls -l /usr/bin/signal-desktop

lrwxrwxrwx 1 root root 40 Aug  6 11:17 /usr/bin/signal-desktop -> /usr/lib64/signal-desktop/signal-desktop

[user@crowphale ~]$ ls -l /usr/lib64/signal-desktop/signal-desktop

-rwxr-xr-x 1 root root 116480632 Aug  6 11:17 /usr/lib64/signal-desktop/signal-desktop

But trying to run it gives me 127:

[user@dom0 ~]$ qvm-run -a crowphale /usr/lib64/signal-desktop/signal-desktop

Running '/usr/lib64/signal-desktop/signal-desktop' on crowphale

crowphale: command failed with code: 127

Trying to run it directly in the AppVM terminal (probably wrong thing to do), gives me:

[user@crowphale ~]$ signal-desktop

signal-desktop: error while loading shared libraries: libXss.so.1: cannot open shared object file: No such file or directory

I'm stuck. Any ideas?

You need to install libXss

$ sudo dnf what provides '*/libXss.so.1'

Will tell you what package is required.

[Crowphale]

Thank you so much! It's working. Installing libXScrnSaver fixed the issue. (Sent a PR to fix the issue:

https://github.com/luminoso/fedora-copr-signal-desktop/pull/4)

I'm puzzled though, does anyone know why did running the `qvm-run` command in dom0 terminal gave me 127, instead of the missing dependency?

Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

[Steve Coleman]

On Wed, Aug 26, 2020, 11:00 PM Crowphale <crow...@protonmail.com> wrote:

Thank you so much! It's working. Installing libXScrnSaver fixed the issue. (Sent a PR to fix the issue:

https://github.com/luminoso/fedora-copr-signal-desktop/pull/4)

I'm puzzled though, does anyone know why did running the `qvm-run` command in dom0 terminal gave me 127, instead of the missing dependency?

qvm-run basically only knows the error code from the command line executed in the vm. It knows nothing about what the command is supposed to do or any specifics on why it failed. The return code itself can be looked up or googled to get an idea, but even that won't tell you which resource. 

Note: When you use the -p option with qvm-run you can see whatever text and errors the command being run generated. Thats a quick way to see what might be wrong.

[Crowphale]

Thank you!

Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐