Failed to initialize Crashpad

Installation & Packaging
1

Every time I run a mojo file below error appear, although file run fine.

Failed to initialize Crashpad. Crash reporting will not be available.  Cause: while locating crashpad handler: unable to locate crashpad handler executable

I’m running this on google firebase studio with following info by pixi info

mojo-63629855:~/mojo/example-project{main}$ pixi info
System
------------
       Pixi version: 0.51.0
           Platform: linux-64
   Virtual packages: __unix=0=0
                   : __linux=6.6.97=0
                   : __glibc=2.39=0
                   : __archspec=1=broadwell
          Cache dir: /home/user/.cache/rattler/cache
       Auth storage: /home/user/.rattler/credentials.json
   Config locations: No config files found

Global
------------
            Bin dir: /home/user/.pixi/bin
    Environment dir: /home/user/.pixi/envs
       Manifest dir: /home/user/.pixi/manifests/pixi-global.toml

Workspace
------------
               Name: example-project
            Version: 0.1.0
      Manifest file: /home/user/mojo/example-project/pixi.toml
       Last updated: 12-08-2025 16:03:16

Environments
------------
        Environment: default
           Features: default
           Channels: https://conda.modular.com/max-nightly, conda-forge
   Dependency count: 1
       Dependencies: modular
   Target platforms: linux-64
    Prefix location: /home/user/mojo/example-project/.pixi/envs/default
2

I tried editing modular.cfg file as

[crash_reporting]
enabled = false

also following command not found
modular config-set crash_reporting.enabled=false

3

Hey @Anil,

I ran into a crashpad issue before but on Windows 10 Pro/WSL (Ubuntu) months ago. Afaik Crashpad is Google’s stack for reporting bugs - maybe kernel/compiler bugs. But it has been some time: Crashpad bugs

Brief Google search: Link

My understanding is that Pixi would be looking for the binary executable - Crashpad program, but Pixi is unable to locate the stack/program. Usually these are found in common directories like usr/bin/<binary excutable here> or for Pixi shell environments this would most likely be under /.pixi/* hope that helps clear up some confusion for community dev :+1: