From: brxken128 <brxken128@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: vscode closes (or crashes?) when clicking the "File" tab
Date: Tue, 12 Jul 2022 10:24:39 +0200 [thread overview]
Message-ID: <20220712082439.i-F30x0aTdoqVWta1znlN5SEqUiCJiI8fDExRlDyQH0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38005@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 790 bytes --]
New comment by brxken128 on void-packages repository
https://github.com/void-linux/void-packages/issues/38005#issuecomment-1181470077
Comment:
This is quite an odd issue, maybe it's something regarding the electron version jump?
> However, i use the binary package directly from microsoft
I don't agree that this would be a good solution for the long-term, although it'd be enough to get people on their feet I suppose. Provided VSCodium itself (from their repo) still runs fine, I'll probably end up using that (and recommending it to others).
For more information about my setup:
* Proprietary Nvidia drivers
* glibc
* Kernel `5.18.9_1`
* X11
* Vscode 1.66 works fine (but rust-analyzer requires 1.67 or above)
* gnome 42
I can provide logs or anything if required.
next prev parent reply other threads:[~2022-07-12 8:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-11 14:19 [ISSUE] " RicArch97
2022-07-11 14:48 ` Johnnynator
2022-07-11 17:47 ` brxken128
2022-07-11 21:35 ` RicArch97
2022-07-12 0:47 ` negativeExponent
2022-07-12 1:04 ` negativeExponent
2022-07-12 8:24 ` brxken128 [this message]
2022-07-12 13:59 ` sink666
2022-07-12 19:18 ` atk
2022-07-12 20:47 ` shizonic
2022-07-12 21:48 ` RicArch97
2022-07-12 22:09 ` [ISSUE] [CLOSED] " Johnnynator
2022-07-13 6:24 ` shizonic
2022-07-13 6:26 ` shizonic
2022-07-13 6:48 ` shizonic
2022-07-13 7:00 ` negativeExponent
2022-07-13 7:48 ` shizonic
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=20220712082439.i-F30x0aTdoqVWta1znlN5SEqUiCJiI8fDExRlDyQH0@z \
--to=brxken128@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).