Package Details: deemix-gui-git r222.5d447b6035-2

Git Clone URL: (read-only, click to copy)
Package Base: deemix-gui-git
Description: A gui electron app for the deemix lib
Upstream URL:
Licenses: GPL3
Provides: deemix-gui
Submitter: remixdev
Maintainer: C0rn3j
Last Packager: C0rn3j
Votes: 8
Popularity: 0.000000
First Submitted: 2021-06-27 20:20 (UTC)
Last Updated: 2023-05-17 20:00 (UTC)

Pinned Comments

Latest Comments

1 2 Next › Last »

remixdev commented on 2024-02-21 06:43 (UTC)

This package is no longer maintained and hasn't been for about a year. It could be that some dependencies have been updated and its breaking something.

Currently I have no time to look into it and try to fix it.

silt commented on 2024-02-21 03:59 (UTC) (edited on 2024-02-21 03:59 (UTC) by silt)

@fdz I'm having the same issue as you.

Maybe deemix-gui tries to open the port twice and then crashes ?

This appears to be the case. From strace -e trace=network deemix-gui:

setsockopt(44, SOL_SOCKET, SO_REUSEADDR, [1], 4) = 0
bind(44, {sa_family=AF_INET, sin_port=htons(6595), sin_addr=inet_addr("")}, 16) = 0
listen(44, 511)                         = 0
setsockopt(45, SOL_SOCKET, SO_REUSEADDR, [1], 4) = 0
bind(45, {sa_family=AF_INET, sin_port=htons(6595), sin_addr=inet_addr("")}, 16) = -1 EADDRINUSE (Address already in use)

I don't see immediately see anything in the deemix-gui source that would cause this, but TypeScript is luckily far outside my area of expertise.
@remixdev any suggestions for either fixing this or more precisely tracking down the problem?

fdz commented on 2024-02-03 13:52 (UTC)

@remixdev thanks for the tip (I tried -h instead of --help…), but in the meantime found this option. Unfortunately, this does not solve anything : whatever port I set, I get the same message.

The ports are not in use, but deemix-gui still fails even if I'm able to open them and listen / send simple text on them afterwards.

Maybe deemix-gui tries to open the port twice and then crashes ?

Checking the last release date I think I used deemix-gui sucessfully since a few months ago, so it's probably something else interfering, but what ? A friend talked of apparmor but I don't understand this well, I'll try to dive into this. If you have any ideas, feel free to share.

remixdev commented on 2024-02-02 20:14 (UTC)

@fdz You need to use the --port option or the DEEMIX_SERVER_PORT env variable

fdz commented on 2024-02-02 16:38 (UTC)

Hi, I'm experiencing a strange error when starting deemix-gui

[info] Listening on
[error] Port 6595 is already in use

I checked the open ports with ss -lntup but nothing seems related to that port, anyone experiencing the same issue ?

Following I tried to set the PORT env variable to something else but that doesn't work, deemix-gui still tries to use 6595.

esche commented on 2022-11-17 14:34 (UTC) (edited on 2022-11-17 14:39 (UTC) by esche)

Installing is possible like this:

  1. Download snapshot
  2. replace "git submodul update" in the PKGBUILD with "git -c protocol.file.allow=always submodule update --init --recursive"
  3. add 'nodejs-lts-gallium' to the makedepends in the PKGBUILD
  4. Use the following commands in your terminal:
  5. "export NODE_OPTIONS=--openssl-legacy-provider"
  6. "makepkg -i"

Further information about git submoduls: - -

Deemix-gui-git still depends on an old version of node.js. Further information about this: - -

Trying to build the package without the node.js dependency and the environment variabel produces this error:

        if(isError) throw e;

Error: error:0308010C:digital envelope routines::unsupported
    at new Hash (node:internal/crypto/hash:71:19)
    at Object.createHash (node:crypto:140:10)
    at BulkUpdateDecorator.hashFactory (deemix-gui-git/src/deemix-gui/server/node_modules/webpack/lib/util/createHash.js:145:18)
    at BulkUpdateDecorator.update (deemix-gui-git/src/deemix-gui/server/node_modules/webpack/lib/util/createHash.js:46:50)
    at RawSource.updateHash (deemix-gui-git/src/deemix-gui/server/node_modules/webpack-sources/lib/RawSource.js:64:8)
    at NormalModule._initBuildHash (deemix-gui-git/src/deemix-gui/server/node_modules/webpack/lib/NormalModule.js:868:17)
    at handleParseResult (deemix-gui-git/src/deemix-gui/server/node_modules/webpack/lib/NormalModule.js:934:10)
    at deemix-gui-git/src/deemix-gui/server/node_modules/webpack/lib/NormalModule.js:1026:4
    at processResult (deemix-gui-git/src/deemix-gui/server/node_modules/webpack/lib/NormalModule.js:743:11)
    at deemix-gui-git/src/deemix-gui/server/node_modules/webpack/lib/NormalModule.js:807:5 {
  opensslErrorStack: [ 'error:03000086:digital envelope routines::initialization error' ],
  library: 'digital envelope routines',
  reason: 'unsupported',

Node.js v19.1.0
error Command failed with exit code 1.
info Visit for documentation about this command.

sekret commented on 2022-11-06 21:10 (UTC)

Doesn't build right now, the prepare() function stops with this message:

==> Starting prepare()...
Submodule 'webui' (/srcdest/deemix-webui) registered for path 'webui'
Cloning into '/build/deemix-gui-git/src/deemix-gui/webui'...
fatal: transport 'file' not allowed
fatal: clone of '/build/deemix-gui-git/src/deemix-webui' into submodule path '/build/deemix-gui-git/src/deemix-gui/webui' failed
Failed to clone 'webui'. Retry scheduled
Cloning into '/build/deemix-gui-git/src/deemix-gui/webui'...
fatal: transport 'file' not allowed
fatal: clone of '/build/deemix-gui-git/src/deemix-webui' into submodule path '/build/deemix-gui-git/src/deemix-gui/webui' failed
Failed to clone 'webui' a second time, aborting
==> ERROR: A failure occurred in prepare().
==> ERROR: Build failed, check /mnt/chroot/sekret/build

I'm building in a clean chroot with

makechrootpkg -c -n -r $CHROOT

and am not sure if it builds outside of it with makepkg.

sekret commented on 2022-02-05 10:21 (UTC)

Please add python to makedepends. Doesn't build without it. I don't know if it's also required at runtime.

s0nspark commented on 2022-01-20 10:58 (UTC)

I had issues building this - both paru and makepkg were unable to find npm, which was installed both as a system package and locally in my home dir. I worked around this by adding PATH=/usr/sbin:$PATH to the build section of the PKGBUILD.

Just wanted to mention it in case this wasn't something peculiar to my system.