Github messages for voidlinux
 help / color / mirror / Atom feed
From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: telegram-desktop: Segmentation fault
Date: Fri, 06 Sep 2019 20:59:38 +0200	[thread overview]
Message-ID: <20190906185938.t3KNRQZfMHKr20fJQ3albtpTb7NRdbFwOmrs1CajSOQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-14251@inbox.vuxu.org>

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

New comment by Johnnynator on void-packages repository

https://github.com/void-linux/void-packages/issues/14251#issuecomment-528974982

Comment:
~~~@whoizit the issue is that you let Telegram run in X11 env but seem to force GDK to use Wayland, mixing x11 and Wayland in one application can result in incompatibilities. I would recommend to just set `XDG_SESSION_TYPE=wayland` or `QT_QPA_PLATFORM=wayland`~~~
Can you check if not unseting QT_QPA_PLATFORM results in the same back trace.

  parent reply	other threads:[~2019-09-06 18:59 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-06 13:24 [ISSUE] " voidlinux-github
2019-09-06 17:16 ` voidlinux-github
2019-09-06 18:29 ` voidlinux-github
2019-09-06 18:59 ` voidlinux-github [this message]
2019-09-06 18:59 ` voidlinux-github
2019-09-06 19:00 ` voidlinux-github
2019-09-06 19:01 ` voidlinux-github
2019-09-06 19:02 ` voidlinux-github
2019-09-06 19:08 ` voidlinux-github
2019-09-06 19:38 ` voidlinux-github
2019-09-07 18:27 ` voidlinux-github
2019-09-07 23:26 ` voidlinux-github
2019-09-07 23:40 ` voidlinux-github
2019-09-08  0:33 ` voidlinux-github
2019-09-08  0:38 ` voidlinux-github
2019-09-08  3:53 ` voidlinux-github
2019-09-08  6:37 ` voidlinux-github
2019-09-09 14:57 ` [ISSUE] [CLOSED] " voidlinux-github
2020-07-16  0:15 ` el-leopardo
2020-09-16 12:47 ` Marc3275

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=20190906185938.t3KNRQZfMHKr20fJQ3albtpTb7NRdbFwOmrs1CajSOQ@z \
    --to=voidlinux-github@inbox.vuxu.org \
    --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).