Signal-Desktop causes error "/usr/bin/xdg-mime: line 885: qtpaths: command not found"

Hello together,

I try to set up Signal-Desktop on a freshly installed EOS.

Unfortunately, the app is loading, but all the buttons are missing, so I cannot link my device or do anything else. Also the window settings are completely unresponsive.

Does anybody here have a similar problem?

I am using KDE-Plasma.

Thank you very much for your help! :smiley:

I’ve checked my signal on EOS. It’s running as expected, no missing buttons.

Running: signal-desktop 7.78.0-1

Edit: I’m also on KDE/Plasma:

Operating System: EndeavourOS
KDE Plasma Version: 6.5.2
KDE Frameworks Version: 6.19.0
Qt Version: 6.10.0
Kernel Version: 6.12.57-1-lts (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5825U with Radeon Graphics
Memory: 16 GiB of RAM (15.0 GiB usable)
Graphics Processor: AMD Radeon Graphics

That is interesting. On my work laptop it is also working fine, but not on my (much older) home laptop. :thinking: It has been working until I logged out, then I installed my system again and now the error is the same as before new installation.

Anything if you run something like
journalctl | grep 'signal-desktop'

in cli?

Thank you for your support! Does this help?

$ journalctl | grep ‘signal-desktop’
Nov 09 19:08:01 machine sudo[2557]: user : TTY=pts/0 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/pacman -Syyu signal-desktop
Nov 09 19:37:30 machine signal-desktop[6424]: NODE_ENV production
Nov 09 19:37:30 machine signal-desktop[6424]: NODE_CONFIG_DIR /usr/lib/signal-desktop/resources/app.asar/config
Nov 09 19:37:30 machine signal-desktop[6424]: NODE_CONFIG {}
Nov 09 19:37:30 machine signal-desktop[6424]: ALLOW_CONFIG_MUTATIONS undefined
Nov 09 19:37:30 machine signal-desktop[6424]: HOSTNAME machine
Nov 09 19:37:30 machine signal-desktop[6424]: NODE_APP_INSTANCE undefined
Nov 09 19:37:30 machine signal-desktop[6424]: SUPPRESS_NO_CONFIG_WARNING undefined
Nov 09 19:37:30 machine signal-desktop[6424]: SIGNAL_ENABLE_HTTP undefined
Nov 09 19:37:30 machine signal-desktop[6424]: userData: /home/user/.config/Signal
Nov 09 19:37:31 machine signal-desktop[6504]: /usr/bin/xdg-mime: line 885: qtpaths: command not found
Nov 09 19:37:31 machine signal-desktop[6564]: /usr/bin/xdg-mime: line 885: qtpaths: command not found
Nov 09 19:37:32 machine signal-desktop[6624]: /usr/bin/xdg-mime: line 885: qtpaths: command not found
Nov 09 19:37:32 machine signal-desktop[6683]: /usr/bin/xdg-mime: line 885: qtpaths: command not found
Nov 09 19:37:35 machine signal-desktop[6424]: (node:6424) [DEP0180] DeprecationWarning: fs.Stats constructor is deprecated.
Nov 09 19:37:35 machine signal-desktop[6424]: (Use signal-desktop --trace-deprecation ... to show where the warning was created)
Nov 09 19:38:54 machine signal-desktop[6799]: NODE_ENV production
Nov 09 19:38:54 machine signal-desktop[6799]: NODE_CONFIG_DIR /usr/lib/signal-desktop/resources/app.asar/config
Nov 09 19:38:54 machine signal-desktop[6799]: NODE_CONFIG {}
Nov 09 19:38:54 machine signal-desktop[6799]: ALLOW_CONFIG_MUTATIONS undefined
Nov 09 19:38:54 machine signal-desktop[6799]: HOSTNAME machine
Nov 09 19:38:54 machine signal-desktop[6799]: NODE_APP_INSTANCE undefined
Nov 09 19:38:54 machine signal-desktop[6799]: SUPPRESS_NO_CONFIG_WARNING undefined
Nov 09 19:38:54 machine signal-desktop[6799]: SIGNAL_ENABLE_HTTP undefined
Nov 09 19:38:54 machine signal-desktop[6799]: userData: /home/user/.config/Signal
Nov 09 19:38:55 machine signal-desktop[6845]: /usr/bin/xdg-mime: line 885: qtpaths: command not found
Nov 09 19:38:55 machine signal-desktop[6904]: /usr/bin/xdg-mime: line 885: qtpaths: command not found
Nov 09 19:38:55 machine signal-desktop[6927]: /usr/bin/xdg-mime: line 885: qtpaths: command not found
Nov 09 19:38:56 machine signal-desktop[6986]: /usr/bin/xdg-mime: line 885: qtpaths: command not found
Nov 09 19:38:56 machine signal-desktop[6799]: (node:6799) [DEP0180] DeprecationWarning: fs.Stats constructor is deprecated.
Nov 09 19:38:56 machine signal-desktop[6799]: (Use signal-desktop --trace-deprecation ... to show where the warning was created)
Nov 09 19:41:34 machine signal-desktop[7658]: NODE_ENV production
Nov 09 19:41:34 machine signal-desktop[7658]: NODE_CONFIG_DIR /usr/lib/signal-desktop/resources/app.asar/config
Nov 09 19:41:34 machine signal-desktop[7658]: NODE_CONFIG {}
Nov 09 19:41:34 machine signal-desktop[7658]: ALLOW_CONFIG_MUTATIONS undefined
Nov 09 19:41:34 machine signal-desktop[7658]: HOSTNAME machine
Nov 09 19:41:34 machine signal-desktop[7658]: NODE_APP_INSTANCE undefined
Nov 09 19:41:34 machine signal-desktop[7658]: SUPPRESS_NO_CONFIG_WARNING undefined
Nov 09 19:41:34 machine signal-desktop[7658]: SIGNAL_ENABLE_HTTP undefined
Nov 09 19:41:34 machine signal-desktop[7658]: userData: /home/user/.config/Signal
Nov 09 19:41:35 machine signal-desktop[7714]: /usr/bin/xdg-mime: line 885: qtpaths: command not found
Nov 09 19:41:36 machine signal-desktop[7773]: /usr/bin/xdg-mime: line 885: qtpaths: command not found
Nov 09 19:41:36 machine signal-desktop[7796]: /usr/bin/xdg-mime: line 885: qtpaths: command not found
Nov 09 19:41:37 machine signal-desktop[7857]: /usr/bin/xdg-mime: line 885: qtpaths: command not found
Nov 09 19:41:38 machine signal-desktop[7658]: (node:7658) [DEP0180] DeprecationWarning: fs.Stats constructor is deprecated.
Nov 09 19:41:38 machine signal-desktop[7658]: (Use signal-desktop --trace-deprecation ... to show where the warning was created)
Nov 09 19:42:49 machine signal-desktop[8885]: NODE_ENV production
Nov 09 19:42:49 machine signal-desktop[8885]: NODE_CONFIG_DIR /usr/lib/signal-desktop/resources/app.asar/config
Nov 09 19:42:49 machine signal-desktop[8885]: NODE_CONFIG {}
Nov 09 19:42:49 machine signal-desktop[8885]: ALLOW_CONFIG_MUTATIONS undefined
Nov 09 19:42:49 machine signal-desktop[8885]: HOSTNAME machine
Nov 09 19:42:49 machine signal-desktop[8885]: NODE_APP_INSTANCE undefined
Nov 09 19:42:49 machine signal-desktop[8885]: SUPPRESS_NO_CONFIG_WARNING undefined
Nov 09 19:42:49 machine signal-desktop[8885]: SIGNAL_ENABLE_HTTP undefined
Nov 09 19:42:49 machine signal-desktop[8885]: userData: /home/user/.config/Signal
Nov 09 19:42:50 machine signal-desktop[8941]: /usr/bin/xdg-mime: line 885: qtpaths: command not found
Nov 09 19:42:50 machine signal-desktop[9000]: /usr/bin/xdg-mime: line 885: qtpaths: command not found
Nov 09 19:42:51 machine signal-desktop[9027]: /usr/bin/xdg-mime: line 885: qtpaths: command not found
Nov 09 19:42:51 machine signal-desktop[9086]: /usr/bin/xdg-mime: line 885: qtpaths: command not found
Nov 09 19:42:51 machine signal-desktop[8885]: (node:8885) [DEP0180] DeprecationWarning: fs.Stats constructor is deprecated.
Nov 09 19:42:51 machine signal-desktop[8885]: (Use signal-desktop --trace-deprecation ... to show where the warning was created)
Nov 09 19:48:47 machine signal-desktop[11034]: NODE_ENV production
Nov 09 19:48:47 machine signal-desktop[11034]: NODE_CONFIG_DIR /usr/lib/signal-desktop/resources/app.asar/config
Nov 09 19:48:47 machine signal-desktop[11034]: NODE_CONFIG {}
Nov 09 19:48:47 machine signal-desktop[11034]: ALLOW_CONFIG_MUTATIONS undefined
Nov 09 19:48:47 machine signal-desktop[11034]: HOSTNAME machine
Nov 09 19:48:47 machine signal-desktop[11034]: NODE_APP_INSTANCE undefined
Nov 09 19:48:47 machine signal-desktop[11034]: SUPPRESS_NO_CONFIG_WARNING undefined
Nov 09 19:48:47 machine signal-desktop[11034]: SIGNAL_ENABLE_HTTP undefined
Nov 09 19:48:47 machine signal-desktop[11034]: userData: /home/user/.config/Signal
Nov 09 19:48:48 machine signal-desktop[11078]: /usr/bin/xdg-mime: line 885: qtpaths: command not found
Nov 09 19:48:48 machine signal-desktop[11137]: /usr/bin/xdg-mime: line 885: qtpaths: command not found
Nov 09 19:48:49 machine signal-desktop[11160]: /usr/bin/xdg-mime: line 885: qtpaths: command not found
Nov 09 19:48:49 machine signal-desktop[11219]: /usr/bin/xdg-mime: line 885: qtpaths: command not found
Nov 09 19:48:49 machine signal-desktop[11034]: (node:11034) [DEP0180] DeprecationWarning: fs.Stats constructor is deprecated.
Nov 09 19:48:49 machine signal-desktop[11034]: (Use signal-desktop --trace-deprecation ... to show where the warning was created)
Nov 09 19:55:30 machine signal-desktop[12409]: NODE_ENV production
Nov 09 19:55:30 machine signal-desktop[12409]: NODE_CONFIG_DIR /usr/lib/signal-desktop/resources/app.asar/config
Nov 09 19:55:30 machine signal-desktop[12409]: NODE_CONFIG {}
Nov 09 19:55:30 machine signal-desktop[12409]: ALLOW_CONFIG_MUTATIONS undefined
Nov 09 19:55:30 machine signal-desktop[12409]: HOSTNAME machine
Nov 09 19:55:30 machine signal-desktop[12409]: NODE_APP_INSTANCE undefined
Nov 09 19:55:30 machine signal-desktop[12409]: SUPPRESS_NO_CONFIG_WARNING undefined
Nov 09 19:55:30 machine signal-desktop[12409]: SIGNAL_ENABLE_HTTP undefined
Nov 09 19:55:30 machine signal-desktop[12409]: userData: /home/user/.config/Signal
Nov 09 19:55:30 machine signal-desktop[12453]: /usr/bin/xdg-mime: line 885: qtpaths: command not found
Nov 09 19:55:31 machine signal-desktop[12512]: /usr/bin/xdg-mime: line 885: qtpaths: command not found
Nov 09 19:55:31 machine signal-desktop[12535]: /usr/bin/xdg-mime: line 885: qtpaths: command not found
Nov 09 19:55:31 machine signal-desktop[12594]: /usr/bin/xdg-mime: line 885: qtpaths: command not found
Nov 09 19:55:32 machine signal-desktop[12409]: (node:12409) [DEP0180] DeprecationWarning: fs.Stats constructor is deprecated.
Nov 09 19:55:32 machine signal-desktop[12409]: (Use signal-desktop --trace-deprecation ... to show where the warning was created)
Nov 09 19:55:50 machine signal-desktop[12687]: NODE_ENV production
Nov 09 19:55:50 machine signal-desktop[12687]: NODE_CONFIG_DIR /usr/lib/signal-desktop/resources/app.asar/config
Nov 09 19:55:50 machine signal-desktop[12687]: NODE_CONFIG {}
Nov 09 19:55:50 machine signal-desktop[12687]: ALLOW_CONFIG_MUTATIONS undefined
Nov 09 19:55:50 machine signal-desktop[12687]: HOSTNAME machine
Nov 09 19:55:50 machine signal-desktop[12687]: NODE_APP_INSTANCE undefined
Nov 09 19:55:50 machine signal-desktop[12687]: SUPPRESS_NO_CONFIG_WARNING undefined
Nov 09 19:55:50 machine signal-desktop[12687]: SIGNAL_ENABLE_HTTP undefined
Nov 09 19:55:50 machine signal-desktop[12687]: userData: /home/user/.config/Signal
Nov 09 19:55:50 machine signal-desktop[12731]: /usr/bin/xdg-mime: line 885: qtpaths: command not found
Nov 09 19:55:51 machine signal-desktop[12790]: /usr/bin/xdg-mime: line 885: qtpaths: command not found
Nov 09 19:55:51 machine signal-desktop[12813]: /usr/bin/xdg-mime: line 885: qtpaths: command not found
Nov 09 19:55:52 machine signal-desktop[12873]: /usr/bin/xdg-mime: line 885: qtpaths: command not found
Nov 09 19:55:52 machine signal-desktop[12687]: (node:12687) [DEP0180] DeprecationWarning: fs.Stats constructor is deprecated.
Nov 09 19:55:52 machine signal-desktop[12687]: (Use signal-desktop --trace-deprecation ... to show where the warning was created)
Nov 09 19:57:06 machine signal-desktop[13945]: NODE_ENV production
Nov 09 19:57:06 machine signal-desktop[13945]: NODE_CONFIG_DIR /usr/lib/signal-desktop/resources/app.asar/config
Nov 09 19:57:06 machine signal-desktop[13945]: NODE_CONFIG {}
Nov 09 19:57:06 machine signal-desktop[13945]: ALLOW_CONFIG_MUTATIONS undefined
Nov 09 19:57:06 machine signal-desktop[13945]: HOSTNAME machine
Nov 09 19:57:06 machine signal-desktop[13945]: NODE_APP_INSTANCE undefined
Nov 09 19:57:06 machine signal-desktop[13945]: SUPPRESS_NO_CONFIG_WARNING undefined
Nov 09 19:57:06 machine signal-desktop[13945]: SIGNAL_ENABLE_HTTP undefined
Nov 09 19:57:06 machine signal-desktop[13945]: userData: /home/user/.config/Signal
Nov 09 19:57:07 machine signal-desktop[13990]: /usr/bin/xdg-mime: line 885: qtpaths: command not found
Nov 09 19:57:07 machine signal-desktop[14049]: /usr/bin/xdg-mime: line 885: qtpaths: command not found
Nov 09 19:57:07 machine signal-desktop[14072]: /usr/bin/xdg-mime: line 885: qtpaths: command not found
Nov 09 19:57:08 machine signal-desktop[14131]: /usr/bin/xdg-mime: line 885: qtpaths: command not found
Nov 09 19:57:08 machine signal-desktop[13945]: (node:13945) [DEP0180] DeprecationWarning: fs.Stats constructor is deprecated.
Nov 09 19:57:08 machine signal-desktop[13945]: (Use signal-desktop --trace-deprecation ... to show where the warning was created)
Nov 09 19:57:33 machine signal-desktop[14232]: NODE_ENV production
Nov 09 19:57:33 machine signal-desktop[14232]: NODE_CONFIG_DIR /usr/lib/signal-desktop/resources/app.asar/config
Nov 09 19:57:33 machine signal-desktop[14232]: NODE_CONFIG {}
Nov 09 19:57:33 machine signal-desktop[14232]: ALLOW_CONFIG_MUTATIONS undefined
Nov 09 19:57:33 machine signal-desktop[14232]: HOSTNAME machine
Nov 09 19:57:33 machine signal-desktop[14232]: NODE_APP_INSTANCE undefined
Nov 09 19:57:33 machine signal-desktop[14232]: SUPPRESS_NO_CONFIG_WARNING undefined
Nov 09 19:57:33 machine signal-desktop[14232]: SIGNAL_ENABLE_HTTP undefined
Nov 09 19:57:33 machine signal-desktop[14232]: userData: /home/user/.config/Signal
Nov 09 19:57:33 machine signal-desktop[14276]: /usr/bin/xdg-mime: line 885: qtpaths: command not found
Nov 09 19:57:34 machine signal-desktop[14335]: /usr/bin/xdg-mime: line 885: qtpaths: command not found
Nov 09 19:57:34 machine signal-desktop[14358]: /usr/bin/xdg-mime: line 885: qtpaths: command not found
Nov 09 19:57:34 machine signal-desktop[14417]: /usr/bin/xdg-mime: line 885: qtpaths: command not found
Nov 09 19:57:35 machine signal-desktop[14232]: (node:14232) [DEP0180] DeprecationWarning: fs.Stats constructor is deprecated.
Nov 09 19:57:35 machine signal-desktop[14232]: (Use signal-desktop --trace-deprecation ... to show where the warning was created)

Update: Starting Signal-Desktop with…

signal-desktop --disable-gpu

… workes so far. But if I close it and start it the usual way, it does not work anymore (again).

Nevertheless, also starting without gpu throws an error:

$ signal-desktop --disable-gpu
NODE_ENV production
NODE_CONFIG_DIR /usr/lib/signal-desktop/resources/app.asar/config
NODE_CONFIG {}
ALLOW_CONFIG_MUTATIONS undefined
HOSTNAME dave-pc-8560
NODE_APP_INSTANCE undefined
SUPPRESS_NO_CONFIG_WARNING undefined
SIGNAL_ENABLE_HTTP undefined
userData: /home/david/.config/Signal
(node:21998) [DEP0180] DeprecationWarning: fs.Stats constructor is deprecated.
(Use `signal-desktop --trace-deprecation …` to show where the warning was created)

I think this should not appear in your Log. Something QT-related may be missing. I’m not near my PC at the moment, so can’t look into it just now.

1 Like

The binary /usr/bin/xdg-mime comes from the package xdg-utils.

warning: xdg-utils-1.2.1-1 is up to date – reinstalling

xdg-utils was successfully installed already, but this issue appears nevertheless. :confused:

1 Like

Had a look at my journal, the qtpaths-message is a red herring, it seems:

signal-desktop[4177]: NODE_ENV production
signal-desktop[4177]: NODE_CONFIG_DIR /usr/lib/signal-desktop/resources/app.asar/config
signal-desktop[4177]: NODE_CONFIG {}
signal-desktop[4177]: ALLOW_CONFIG_MUTATIONS undefined
signal-desktop[4177]: HOSTNAME >
signal-desktop[4177]: NODE_APP_INSTANCE undefined
signal-desktop[4177]: SUPPRESS_NO_CONFIG_WARNING undefined
signal-desktop[4177]: SIGNAL_ENABLE_HTTP undefined
signal-desktop[4177]: userData: /home/>/.config/Signal
signal-desktop[4812]: /usr/bin/xdg-mime: regel 885: qtpaths: opdracht niet gevonden
signal-desktop[5033]: /usr/bin/xdg-mime: regel 885: qtpaths: opdracht niet gevonden
signal-desktop[5074]: /usr/bin/xdg-mime: regel 885: qtpaths: opdracht niet gevonden
signal-desktop[5145]: /usr/bin/xdg-mime: regel 885: qtpaths: opdracht niet gevonden
signal-desktop[5728]: MESA-INTEL: warning: Haswell Vulkan support is incomplete
signal-desktop[4177]: (node:4177) [DEP0180] DeprecationWarning: fs.Stats constructor is deprecated.
signal-desktop[4177]: (Use signal-desktop --trace-deprecation … to show where the warning was created)

I can’t suggest what to try next, sorry.

No problem! Thank you for looking into it! :smiley:

I also did some more research. On Gitlab the user Robin D’Haese wrote:

So one solution might be to create this symlink as mentioned:

sudo ln -s /usr/bin/qtpaths6 /usr/local/bin/qtpaths

However, I guess after the next update this workaround will be useless.

Another thing I found was a posting from user Hot-Macaroon-8190 on Reddit:

Do I damage my system when installing qt5-tools beside of the already installed qtpaths6?

@SemLraug Could you please check on your system if qt5-tools is installed there? :wink: That might be the reason why `Signal-Desktop is working fine on your machine.

Here you are:

sudo pacman -Q qt5-tools
error: package 'qt5-tools' was not found

sudo pacman -Q qt6-tools
qt6-tools 6.10.0-2

ill see if i can find something about this

signal desktop.pdf (165.5 KB) here for more detail try this sudo ln -sf /usr/lib/qt6/bin/qtpaths /usr/bin/qtpaths

Please do not post PDFs on external sites. ALWAYS post error messages as described in the article. Thank you!

https://discovery.endeavouros.com/forum-log-tool-options/how-to-include-systemlogs-in-your-post/2021/03/

its posted directly here i uploaded it but ok

Is this actually safe to do?

its a symbolic link you can just unlink it if it does cause issues your linking qt6 path to the one its asking in theory it should work here is a better explanation by ai.

yes — usually it’s safe, but do the checks below first and use a safer method than ln -sf if you care about package management or SELinux.

Why it’s usually fine

qtpaths is a small Qt utility (part of Qt6) used to query/install Qt-specific paths. Pointing /usr/bin/qtpaths to the real binary in /usr/lib/qt6/bin/qtpaths just makes it easier for programs/scripts that expect it on $PATH. If the file you link to is the same binary for your system/architecture and you’re not overwriting an important non-Qt program, it won’t break anything.

Risks

  • ln -sf will overwrite whatever is currently at /usr/bin/qtpaths without warning. That could replace a package-managed file or a wrapper script.
  • If a package owns /usr/bin/qtpaths, a future package upgrade may replace or remove your symlink (or your symlink may prevent the package from installing its file correctly).
  • On SELinux-enabled systems you may need to restore contexts after creating the symlink.
  • If the target binary is incompatible (wrong Qt version), some programs may behave unexpectedly.

Safer workflow (recommended)

  1. Inspect what currently exists:

ls -l /usr/bin/qtpaths # see if something is already there
readlink -f /usr/bin/qtpaths # if it’s a symlink, see target
/usr/lib/qt6/bin/qtpaths --version || /usr/lib/qt6/bin/qtpaths --help

  1. Check package ownership (Debian/Ubuntu or Fedora/RPM):

Debian/Ubuntu:

dpkg -S /usr/bin/qtpaths 2>/dev/null || echo “not owned by any package”

Fedora/RHEL:

rpm -qf /usr/bin/qtpaths 2>/dev/null || echo “not owned by any package”

If a package owns it, prefer to fix via package (reinstall/fix alternatives) rather than overwriting.

  1. Make a safe backup before changing:

sudo cp -a /usr/bin/qtpaths /usr/bin/qtpaths.bak 2>/dev/null || true

  1. Create the symlink without force if you want to avoid accidental overwrite:

sudo ln -s /usr/lib/qt6/bin/qtpaths /usr/bin/qtpaths

if it fails because a file exists, you can decide whether to remove/replace it

  1. (Debian-only) If you want your change to survive package updates:

sudo dpkg-divert --add --rename /usr/bin/qtpaths
sudo ln -s /usr/lib/qt6/bin/qtpaths /usr/bin/qtpaths

  1. If SELinux is active, restore context:

sudo restorecon -v /usr/bin/qtpaths

recommendation

If /usr/bin/qtpaths does not exist and /usr/lib/qt6/bin/qtpaths is the correct binary for your distro, creating a symlink is an acceptable and common quick fix. But prefer to:

  • check package ownership first,
  • back up the existing file if present,
  • and avoid -f unless you intentionally want to overwrite.

Please just don’t copy and paste answers provided by an AI search. You could at least provide the link, provide what prompt you used as reference.

The general sentiment of this forum is (as I have understood it) that, even though AI can be useful in some scenarios, one needs always be vigilant and verify the answers.

4 Likes

true