[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
Signal Application is not opening anymore. I am unable to use it on my KDE Linux machine. But I Need signal in my daily work.
Steps to reproduce
It crashed after I attached an Audio file in a chat to send someone. The extension was: ".m4a".
After I attached the file, My crash handler started reporting a crash report. At a time signal App crashed. and I am unable to open it now.
Expected result
The signal App should be on. I have reinstalled it 2 times. but it isn't working.
I Have the latest Virson cause I installed it 5 days before. and I reinstalled 2 times this day.
Uninstall Commands :
alif@sardar:~$ sudo apt install -f
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Starting pkgProblemResolver with broken count: 0
Starting 2 pkgProblemResolver with broken count: 0
Done
The following packages were automatically installed and are no longer required:
libkf6pulseaudioqt4 libpresage-data libpresage1v5 libtinyxml2.6.2v5 linux-headers-5.15.0-105
linux-headers-5.15.0-105-generic linux-headers-5.15.0-106 linux-headers-5.15.0-106-generic
linux-headers-5.15.0-107 linux-headers-5.15.0-107-generic linux-headers-6.5.0-27-generic
linux-hwe-6.5-headers-6.5.0-27 linux-image-5.15.0-105-generic linux-image-5.15.0-106-generic
linux-image-5.15.0-107-generic linux-image-6.5.0-27-generic linux-modules-5.15.0-105-generic
linux-modules-5.15.0-106-generic linux-modules-5.15.0-107-generic linux-modules-6.5.0-27-generic
linux-modules-extra-5.15.0-105-generic linux-modules-extra-5.15.0-106-generic
linux-modules-extra-5.15.0-107-generic linux-modules-extra-6.5.0-27-generic presage
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
alif@sardar:~$ journalctl -f | grep signal
Jun 16 09:25:03 sardar plasmashell[14114]: Set Windows Application User Model ID (AUMID) { AUMID: 'org.whispersystems.signal-desktop' }
Jun 16 09:25:03 sardar dbus-daemon[781]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.109' (uid=1000 pid=14114 comm="/opt/Signal/signal-desktop --no-sandbox " label="unconfined")
Jun 16 09:25:03 sardar kernel: traps: VizCompositorTh[14446] trap invalid opcode ip:5c2cb24fd19e sp:7e51761ef430 error:0 in signal-desktop[5c2cad840000+837d000]
Jun 16 09:25:04 sardar kernel: traps: VizCompositorTh[14494] trap invalid opcode ip:5c2cb24fd19e sp:7e51761ef430 error:0 in signal-desktop[5c2cad840000+837d000]
Jun 16 09:25:04 sardar kernel: traps: VizCompositorTh[14529] trap invalid opcode ip:5c2cb24fd19e sp:7e51761ef430 error:0 in signal-desktop[5c2cad840000+837d000]
Jun 16 09:25:04 sardar kernel: traps: VizCompositorTh[14547] trap invalid opcode ip:5c2cb24fd19e sp:7e517f0af430 error:0 in signal-desktop[5c2cad840000+837d000]
Jun 16 09:25:04 sardar kernel: traps: VizCompositorTh[14569] trap invalid opcode ip:5c2cb24fd19e sp:7e517f0af430 error:0 in signal-desktop[5c2cad840000+837d000]
Jun 16 09:25:04 sardar kernel: traps: VizCompositorTh[14586] trap invalid opcode ip:5c2cb24fd19e sp:7e517f0af430 error:0 in signal-desktop[5c2cad840000+837d000]
Jun 16 09:25:04 sardar kernel: traps: signal-desktop[14114] trap int3 ip:5ea7afe5d70a sp:7ffcc3f5bf20 error:0 in signal-desktop[5ea7ac1c6000+837d000]
Jun 16 09:25:04 sardar systemd[1686]: app-signal\x2ddesktop-97d093c0fccc453ebd32cfeb55b2d44e.scope: Consumed 2.437s CPU time.
Some extra [added later ]
After installing from flatpack (1 hour ago), I got this error :
Unhandled Error
Error: write EIO
at afterWriteDispatched (node:internal/stream_base_commons:160:15)
at writeGeneric (node:internal/stream_base_commons:151:3)
at Socket._writeGeneric (node:net:952:11)
at Socket._write (node:net:964:8)
at writeOrBuffer (node:internal/streams/writable:564:12)
at _write (node:internal/streams/writable:493:10)
at Writable.write (node:internal/streams/writable:502: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 error] ([REDACTED]/node_modules/pino/lib/tools.js:56:21)
Screenshots
No response
Signal version
I am Unable to see, cause it isn't opening . But i installed it 2 days ago.
Using a supported version?
Overall summary
Signal Application is not opening anymore. I am unable to use it on my KDE Linux machine. But I Need signal in my daily work.
Steps to reproduce
It crashed after I attached an Audio file in a chat to send someone. The extension was: ".m4a". After I attached the file, My crash handler started reporting a crash report. At a time signal App crashed. and I am unable to open it now.
Expected result
The signal App should be on. I have reinstalled it 2 times. but it isn't working. I Have the latest Virson cause I installed it 5 days before. and I reinstalled 2 times this day. Uninstall Commands :
And I install the app again by following official process :
Linux (Debian-based) Install Instructions
NOTE: These instructions only work for 64-bit Debian-based
Linux distributions such as Ubuntu, Mint etc.
1. Install our official public software signing key:
wget -O- https://updates.signal.org/desktop/apt/keys.asc | gpg --dearmor > signal-desktop-keyring.gpg cat signal-desktop-keyring.gpg | sudo tee /usr/share/keyrings/signal-desktop-keyring.gpg > /dev/null
2. Add our repository to your list of repositories:
echo 'deb [arch=amd64 signed-by=/usr/share/keyrings/signal-desktop-keyring.gpg] https://updates.signal.org/desktop/apt xenial main' |\ sudo tee /etc/apt/sources.list.d/signal-xenial.list
3. Update your package database and install Signal:
sudo apt update && sudo apt install signal-desktop
Actual result
This may be helpful
Some extra [added later ]
After installing from flatpack (1 hour ago), I got this error :
Screenshots
No response
Signal version
I am Unable to see, cause it isn't opening . But i installed it 2 days ago.
Operating system
Debian
Version of Signal on your phone
No response
Link to debug log
No response