Booting the 0.6.1 live ISO on a Surface Book 2 ends every session with an error alert instead of a volume icon in the tray:
Installing AudioMixer in Deskbar failed:
Unknown error -1
The desktop is otherwise up and usable; dismissing the alert leaves the Deskbar without the AudioMixer replicant. It happens on every boot — on a live ISO nothing persists, so every boot is a first login and the installer runs again.
Where the message comes from
The alert is the failure path of InstallInDeskbar() in src/apps/audiomixer/AudioMixerApp.cpp:75, reached when the app is started with --deskbar. That is how data/system/boot/first_login/default_deskbar_items.sh installs it since 50e3233:
install_item /system/apps/AudioMixer --deskbar
strerror() printing "Unknown error -1" means the status is B_ERROR (-1). InstallInDeskbar() passes the status through unchanged, so the -1 comes either from the app's own our_image() / get_ref_for_path() step or from the Deskbar's reply to BDeskbar::AddItem().
Environment
- Version: 0.6.1 (release ISO, booted live — not installed)
- Hardware: Microsoft Surface Book 2
- Reproducibility: every boot, without exception
The other two entries the same script installs (ProcessController and NetworkStatus) do not raise an alert.
I have not reproduced it in QEMU, so it may depend on the hardware or on the timing of the first login.
Booting the 0.6.1 live ISO on a Surface Book 2 ends every session with an error alert instead of a volume icon in the tray:
The desktop is otherwise up and usable; dismissing the alert leaves the Deskbar without the AudioMixer replicant. It happens on every boot — on a live ISO nothing persists, so every boot is a first login and the installer runs again.
Where the message comes from
The alert is the failure path of
InstallInDeskbar()insrc/apps/audiomixer/AudioMixerApp.cpp:75, reached when the app is started with--deskbar. That is howdata/system/boot/first_login/default_deskbar_items.shinstalls it since 50e3233:strerror()printing "Unknown error -1" means the status isB_ERROR(-1).InstallInDeskbar()passes the status through unchanged, so the -1 comes either from the app's ownour_image()/get_ref_for_path()step or from the Deskbar's reply toBDeskbar::AddItem().Environment
The other two entries the same script installs (ProcessController and NetworkStatus) do not raise an alert.
I have not reproduced it in QEMU, so it may depend on the hardware or on the timing of the first login.