Github messages for voidlinux
 help / color / mirror / Atom feed
From: krkk <krkk@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: telegram-desktop crashes
Date: Wed, 21 Jul 2021 09:45:13 +0200	[thread overview]
Message-ID: <20210721074513.91nJiWSsESoX54KP0jJnHsUVZmfgf2w-2VkNoWOT9_Y@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32053@inbox.vuxu.org>

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

New comment by krkk on void-packages repository

https://github.com/void-linux/void-packages/issues/32053#issuecomment-883968158

Comment:
Could you try `unset QT_QPA_PLATFORMTHEME` and then run telegram? It fixed for me.

When I downgraded to the previous version (2.8.4), there was an message in my stdout, which explained to me why I previously had the default qt theme when selecting a file and why the newer version crashes:
> Unfortunately, **GTK integration conflicts with qgtk2 platformtheme and style**. Therefore, QT_QPA_PLATFORMTHEME and QT_STYLE_OVERRIDE will be unset.
> This can be ignored by setting DESKTOP_APP_I_KNOW_ABOUT_GTK_INCOMPATIBILITY environment variable to any value, **however, if qgtk2 theme or style is used, this will lead to a crash**.
> GTK integration can be disabled by setting DESKTOP_APP_DISABLE_GTK_INTEGRATION to any value. Keep in mind that this will lead to some features being unavailable.

It looks like they removed the message and unsetting the enviroments in https://github.com/desktop-app/lib_base/commit/f493a8174f993119de8d9a5170dc89641bfafbef#diff-5d8c1fecd0ee047b9263a26b184089db23769254a398648acc9a2078a58accbeL226-L227

  parent reply	other threads:[~2021-07-21  7:45 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-20 11:33 [ISSUE] " husio
2021-07-20 12:24 ` ericonr
2021-07-20 17:23 ` husio
2021-07-20 17:28 ` husio
2021-07-20 18:23 ` ericonr
2021-07-20 18:28 ` ericonr
2021-07-20 18:40 ` husio
2021-07-20 18:53 ` ericonr
2021-07-20 18:53 ` ericonr
2021-07-20 19:09 ` husio
2021-07-20 19:23 ` ericonr
2021-07-20 19:23 ` ericonr
2021-07-21  7:45 ` krkk [this message]
2021-07-21  9:41 ` husio
2021-07-21  9:42 ` husio
2021-07-21  9:45 ` not-chicken
2021-07-21 10:02 ` husio
2021-07-21 10:16 ` not-chicken
2021-07-21 10:24 ` not-chicken
2021-07-22  7:50 ` slotThe
2021-07-22  9:08 ` ilya-fedin
2021-07-26 18:25 ` husio
2021-07-26 18:29 ` ilya-fedin
2021-07-26 18:30 ` ilya-fedin
2021-07-26 18:32 ` ilya-fedin
2021-08-02 18:11 ` Johnnynator
2021-08-02 18:51 ` husio
2021-08-02 18:53 ` husio
2021-09-12 10:30 ` Kratacoa
2021-09-12 15:39 ` Johnnynator
2021-09-21 15:04 ` Johnnynator
2021-09-21 15:31 ` slotThe
2021-09-21 15:48 ` [ISSUE] [CLOSED] " Johnnynator
2021-09-28 10:53 ` husio

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=20210721074513.91nJiWSsESoX54KP0jJnHsUVZmfgf2w-2VkNoWOT9_Y@z \
    --to=krkk@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).