The Wayback Machine - https://web.archive.org/web/20201125034247/https://github.com/VSCodium/vscodium/issues/504
Skip to content

/ vscodium

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

enable-crash-reporter is true in 1.49.0 #504

Open
Rondom opened this issue Sep 16, 2020 · 0 comments
Open

enable-crash-reporter is true in 1.49.0 #504

Rondom opened this issue Sep 16, 2020 · 0 comments
Labels
good first issue telemetry

Comments

@Rondom
Copy link

@Rondom Rondom commented Sep 16, 2020

Please confirm that this problem is VSCodium-specific

  • This bug doesn't happen if I use Microsoft's Visual Studio Code. It only happens in VSCodium.

Please confirm that the issue/resolution isn't already documented

  • [ X ] I checked the Docs page and my issue is not mentioned there.

To Reproduce
Steps to reproduce the behavior:

  1. Update to 1.49.0 (via RPM on Fedora 32 in my case)
  2. Open argv.json to check the enable-crash-reporter setting. => It is true

Expected behavior
Crash reporting is still disabled.

Desktop (please complete the following information):

  • OS: Fedora 32
  • Architecture x64
  • Version: 1.49.0

Additional context

See the release notes about the change from telemetry.enableCrashReporter to enable-crash-reporter in argv.json
@Rondom Rondom added the bug label Sep 16, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue telemetry
2 participants
@Rondom @stripedpajamas
You can’t perform that action at this time.