Open Philzen opened 10 months ago
This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment, and we'll keep it open. If you have any new additional information, please include it with your comment!
Bump.
In settings, is set Telemetry to off.
However, in the processes, I still see cli args --enable-crash-reporter
.
It looks like crash reporter
is still enabled, wtf.
/opt/vscodium-bin/codium
\_ /opt/vscodium-bin/codium --type=zygote --no-zygote-sandbox
| \_ /opt/vscodium-bin/codium --type=gpu-process --enable-crash-reporter=a66bxxxx-xxxx-xxx-xxxx-xxxxc6210,no_channel ...
\_ /opt/vscodium-bin/codium --type=zygote
| \_ /opt/vscodium-bin/codium --type=zygote
| \_ /opt/vscodium-bin/codium --type=renderer --enable-crash-reporter=a66bxxxx-xxxx-xxx-xxxx-xxxxc6210,no_channel ...
\_ /opt/vscodium-bin/codium --type=utility --utility-sub-type=network.mojom.NetworkService --lang=en-US --service-sandbox-type=none --enable-crash-reporter=a66bxxxx-xxxx-xxx-xxxx-xxxxc6210,no_channel ...
\_ /opt/vscodium-bin/codium --type=utility --utility-sub-type=node.mojom.NodeService --lang=en-US --service-sandbox-type=none --enable-crash-reporter=a66bxxxx-xxxx-xxx-xxxx-xxxxc6210,no_channel ...
\_ /opt/vscodium-bin/codium --type=utility --utility-sub-type=node.mojom.NodeService --lang=en-US --service-sandbox-type=none --dns-result-order=ipv4first --inspect-port=0 --enable-crash-reporter=a66bxxxx-xxxx-xxx-xxxx-xxxxc6210,no_channel ...
\_ /opt/vscodium-bin/codium --type=utility --utility-sub-type=node.mojom.NodeService --lang=en-US --service-sandbox-type=none --enable-crash-reporter=a66bxxxx-xxxx-xxx-xxxx-xxxxc6210,no_channel ...
Describe the bug When looking at my process list, it transpires there are explicit flags set to enable the crash-reporter, which otherwise should be clearly disabled from looking at the
argv.json
in my config directory.Please confirm that this problem is VSCodium-specific
I don't have MS VSCode installed, so i cannot test that. This issue is purely to check why these CLI options are the case here.
Please confirm that the issue/resolution isn't already documented
To Reproduce Steps to reproduce the behavior:
codium
orvscodium
commands to start up vscodiumExpected behavior
None of these processes should have the
--enable-crash-reporter
flag.Sidenote: the UUID shown in the flag is not the same as i see in
argv.json
.Desktop (please complete the following information):
Additional context I disabled all extensions to make sure they are not causing that. Also i've checked the scripts in
/usr/bin/codium
and/usr/bin/vscodium
andprintenv
but i was unable to identify the source of these CLI options.