Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Stuck on "making app single instance" in Linux Mint #3576

Closed
IF-Adin opened this issue Sep 8, 2019 · 14 comments
Closed

Stuck on "making app single instance" in Linux Mint #3576

IF-Adin opened this issue Sep 8, 2019 · 14 comments

Comments

@IF-Adin
Copy link

IF-Adin commented Sep 8, 2019

Bug Description

Since the last update, Signal fails to start:

Set Windows Application User Model ID (AUMID) { appUserModelId: 'org.whispersystems.signal-desktop' }

NODE_ENV production

NODE_CONFIG_DIR /opt/Signal/resources/app.asar/config

NODE_CONFIG {}

ALLOW_CONFIG_MUTATIONS undefined

HOSTNAME undefined

NODE_APP_INSTANCE undefined

SUPPRESS_NO_CONFIG_WARNING undefined

userData: /home/redacted/.config/Signal

config/get: Did not find user config file, cache is now empty object

config/get: Did not find ephemeral config file, cache is now empty object

making app single instance

I tried starting it with sudo, same result.

Steps to Reproduce

Start signal

Actual Result:

Signal fails to start

Expected Result:

Signal starts normally

Platform Info

Signal Version:

I can not start the app, so i can't know for sure, but i installed the latest update yesterday.
apt-cache reports:

signal-desktop:
Installed: 1.27.2
Candidate: 1.27.2

Operating System:
Linux Mint 19.2 Cinnamon
Kernel 5.1.3-050103-generic

@kibrovic
Copy link

kibrovic commented Sep 9, 2019

I have the same issue on Debian 10 Buster. Checked /var/log/syslog and found:

debian kernel: [  234.040302] traps: signal-desktop[2684] trap int3 ip:557292d658c5 sp:7ffe61708550 error:0 in signal-desktop[557290de8000+531e000]

After downgrading to 1.26.2 Signal worked without any problems. Tried the Beta version too, same issue happened

@IF-Adin
Copy link
Author

IF-Adin commented Sep 11, 2019

@kibrovic Sadly i can't even begin to imagine what that would mean. Is there a way to start it more verbosely or debug it?

@kibrovic
Copy link

kibrovic commented Sep 13, 2019

I managed to solve my problem.

Steps

~$ signal-desktop --verbose
[16488:0913/165205.767249:FATAL:setuid_sandbox_host.cc(157)] The SUID sandbox helper binary was found, but is not configured correctly. Rather than run without sandboxing I'm aborting now. You need to make sure that /opt/Signal/chrome-sandbox is owned by root and has mode 4755.
Trace/breakpoint trap

Turns out, my /opt/Signal/chrome-sandbox was owned by root, but had 755 permissions (-rwxr-xr-x). Changed it, now works OK.

~$ sudo chmod 4755 /opt/Signal/chrome-sandbox

Hope it helps. Don't know why I didn't try verbose earlier -_-

@scottnonnenberg-signal
Copy link
Contributor

Okay, so this is a duplicate to #3536

@IF-Adin
Copy link
Author

IF-Adin commented Sep 14, 2019

Okay, so this is a duplicate to #3536

I'm sorry, but i tried both --no-sandbox and --verbose and i tried the fix suggested by @kibrovic but neither of these yielded any result. I have nothing in my syslog either.

The output of --verbose is precisely the same as in my first post.

@scottnonnenberg-signal
Copy link
Contributor

@IF-Adin Okay, so it seems you do have a different issue than some of the folks who have commented here. My recommendation would be to use strace to figure out what Signal Desktop was trying to do when it stopped.

@IF-Adin
Copy link
Author

IF-Adin commented Sep 25, 2019

socket(AF_UNIX, SOCK_STREAM, 0)         = 53
fcntl(53, F_GETFD)                      = 0
fcntl(53, F_SETFD, FD_CLOEXEC)          = 0
bind(53, {sa_family=AF_UNIX, sun_path="/tmp/.org.chromium.Chromium.grJSnJ/SS"}, 110) = 0
listen(53, 5)                           = 0
mprotect(0x21e2f8542000, 249856, PROT_READ|PROT_WRITE) = 0
mprotect(0x21e2f8542000, 249856, PROT_READ|PROT_EXEC) = 0
pread64(49, "const path = require('path');\nco"..., 1459, 11138669) = 1459
openat(AT_FDCWD, "/dev/null", O_RDONLY) = 54
rt_sigprocmask(SIG_SETMASK, ~[RTMIN RT_1], [], 8) = 0
clone(child_stack=NULL, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, child_tidptr=0x7f13cdffc2d0) = 12099
rt_sigprocmask(SIG_SETMASK, [], ~[KILL STOP RTMIN RT_1], 8) = 0
close(54)                               = 0
getpid()                                = 11349
openat(AT_FDCWD, "/proc/12099/stat", O_RDONLY|O_CLOEXEC) = 54
stat("/proc/12099/stat", {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
fstat(54, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
read(54, "12099 (signal-desktop) R 11349 1"..., 65536) = 323
read(54, "", 64512)                     = 0
close(54)                               = 0
madvise(0x1935e0e9d000, 69632, MADV_DONTNEED) = 0
wait4(12099,

That's when it stops. It just seems to wait for something?

@scottnonnenberg-signal
Copy link
Contributor

What it's trying to do at that point is look for other instances of Signal Desktop currently running. If it finds any, it will stop initializing and send a message to that other instance to focus itself.

It appears that the underlying mechanism used to find that other instance is causing problems?

@IF-Adin
Copy link
Author

IF-Adin commented Sep 26, 2019

@scottnonnenberg I wish i could help more with this, but frankly i do not know what could possibly be causing this.

@IF-Adin
Copy link
Author

IF-Adin commented Sep 26, 2019

Update: The snap version of signal-desktop seems to work just fine, even at the newest version.

@scottnonnenberg-signal
Copy link
Contributor

Going back to your strace output - is that complete output? Is more than just Signal Desktop going into a hang there?

@IF-Adin
Copy link
Author

IF-Adin commented Sep 26, 2019

@scottnonnenberg-signal The complete output was around 5000 lines.

@stale
Copy link

stale bot commented Sep 27, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Sep 27, 2021
@stale
Copy link

stale bot commented Oct 4, 2021

This issue has been closed due to inactivity.

@stale stale bot closed this as completed Oct 4, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

3 participants