signal-desktop dies when run in background

harridu commented 1 month ago

Using a supported version?

[X] I have searched searched open and closed issues for duplicates.
[X] I am using Signal-Desktop as provided by the Signal team, not a 3rd-party package.

Overall summary

If I run signal-desktop in the background, then there is a popup saying

Unhandled Error

Error: write EIO
    at afterWriteDispatched (node:internal/stream_base_commons:161:15)
    at writeGeneric (node:internal/stream_base_commons:152:3)
    at Socket._writeGeneric (node:net:954:11)
    at Socket._write (node:net:966:8)
    at writeOrBuffer (node:internal/streams/writable:570:12)
    at _write (node:internal/streams/writable:499:10)
    at Writable.write (node:internal/streams/writable:508:10)
    at Object.write ([REDACTED]/node_modules/pino/lib/multistream.js:71:16)
    at Pino.write ([REDACTED]/node_modules/pino/lib/proto.js:210:10)
    at Pino.LOG [as warn] ([REDACTED]/node_modules/pino/lib/tools.js:56:21)

App Version: 7.28.0
OS: linux

Next it dies.

Steps to reproduce

start signal-desktop using "signal-desktop &".
select a chat

Expected result

Signal should work.

Actual result

There are several popups indicating an internal error. See above for the first popup.

Screenshots

No response

Signal version

7.28.0

Operating system

Debian Sid

Version of Signal on your phone

7.32.1 (389)

Link to debug log

No response

npt commented 1 month ago

I often get this same error when I run Signal from the application menu, but not when I run it from the command line in the foreground. Run from the CLI in the background, AFAIK it

works until I disown and close the terminal
crashes sometime after I do so
unless I redirected stdout/stderr to /dev/null when I started it, in which case it keeps working

but I may be wrong about some of that (I only recently installed the app and haven't made many observations yet).

I'm running Signal 7.29.0 from the apt repository (same thing happened in 7.28.0) on Kubuntu 24.04.

npt commented 1 month ago

This looks like the same as the still-open #5057.

brjsp commented 1 month ago

signal-desktop &

This is expected when running graphical applications like that. If you run them from a .desktop file as intended, your environment should take care of piping stdout/stderr into the system journal.

npt commented 4 weeks ago

This is expected when running graphical applications like that.

This isn't what I observe of most graphical applications — I've only noticed Signal and Discord doing it. Most, even if they log to stdout, can survive it going away.

harridu commented 3 weeks ago

signal-desktop &

This is expected when running graphical applications like that. If you run them from a .desktop file as intended, your environment should take care of piping stdout/stderr into the system journal.

I am not using KDE or Gnome or others, just good ol plain X. No .desktop files involved.

signalapp / Signal-Desktop