Package Details: igdm-bin 3.0.4-11

Git Clone URL: https://aur.archlinux.org/igdm-bin.git (read-only, click to copy)
Package Base: igdm-bin
Description: Desktop application for Instagram DMs
Upstream URL: https://github.com/igdmapps/igdm
Keywords: chat direct-message electron instagram instagram-client instagram-dm messenger
Licenses: MIT
Conflicts: igdm
Provides: igdm
Submitter: tjquillan
Maintainer: zxp19821005
Last Packager: zxp19821005
Votes: 0
Popularity: 0.000000
First Submitted: 2019-03-17 19:54 (UTC)
Last Updated: 2025-04-11 05:16 (UTC)

Dependencies (1)

Required by (0)

Sources (3)

Latest Comments

zxp19821005 commented on 2023-11-14 09:20 (UTC)

@asessionguy I've just extracted the app.asar file,and rename dev-app-update.yml to app-update.yml,it run well in my PC,maybe you can have a try.

zxp19821005 commented on 2023-05-04 01:16 (UTC)

@asessionguy Maybe you can find the answer in https://github.com/igdmapps/igdm/issues

asessionguy commented on 2023-05-03 02:17 (UTC)

I got the following error with a NVIDIA RTX 2060:

Error: Error: ENOENT: no such file or directory, open '/opt/IGdm/resources/app-update.yml'
(node:435500) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'webContents' of undefined
at AppImageUpdater.<anonymous> (/opt/IGdm/resources/app.asar/main/autoupdater.js:34:9)
at AppImageUpdater.emit (events.js:322:22)
at /opt/IGdm/resources/app.asar/node_modules/electron-updater/out/AppUpdater.js:360:12
(node:435500) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
(node:435500) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

It was solved by running igdm --disable-gpu-sandbox but I couldn't send messages.

meismarv commented on 2019-09-04 09:13 (UTC)

this depends also on gconf i think, should be in the dependencies