Github messages for voidlinux
 help / color / mirror / Atom feed
From: lschmelting <lschmelting@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: No tray icons for Electron apps
Date: Mon, 25 May 2020 18:27:25 +0200	[thread overview]
Message-ID: <20200525162725.3G4417Ycvb9sDP2SX_aXTxQu4mtJ_UcAmKh12Yfyo5w@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-11624@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 768 bytes --]

New comment by lschmelting on void-packages repository

https://github.com/void-linux/void-packages/issues/11624#issuecomment-633643172

Comment:
As @ProjectMoon suggested in the issue referenced above, i am now using dbus-run-session. The icon of riot-desktop is still missing. i want to note that the icon of telegram-desktop works fine (is that application also electron based?) 
Terminal Output launching riot-desktop:
```
node[7908]: pthread_create: Invalid argument
No update_base_url is defined: auto update is disabled
(electron) The default value of app.allowRendererProcessReuse is deprecated, it is currently "false".  It will change to be "true" in Electron 9.  For more information please check https://github.com/electron/electron/issues/18397
```

  parent reply	other threads:[~2020-05-25 16:27 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-11624@inbox.vuxu.org>
2019-06-11  9:09 ` voidlinux-github
2019-06-25 14:26 ` voidlinux-github
2019-07-07 15:53 ` voidlinux-github
2019-07-15 20:39 ` voidlinux-github
2020-04-05 17:04 ` ProjectMoon
2020-04-09 20:03 ` ProjectMoon
2020-05-25 16:27 ` lschmelting [this message]
2020-05-25 17:23 ` ProjectMoon
2020-05-25 20:33 ` ProjectMoon
2020-05-26 10:45 ` ProjectMoon
2020-05-26 13:58 ` Johnnynator
2020-05-26 13:58 ` Johnnynator
2020-12-13 21:46 ` ericonr
2020-12-13 21:51 ` [ISSUE] [CLOSED] " Johnnynator
2020-12-13 21:51 ` Johnnynator

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200525162725.3G4417Ycvb9sDP2SX_aXTxQu4mtJ_UcAmKh12Yfyo5w@z \
    --to=lschmelting@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).