Skip to content

Resetting default_kernel using qubes-prefs gives confusing results #10876

@RandyTheOtter

Description

@RandyTheOtter

How to file a helpful issue

Qubes OS release

4.3

Brief summary

Resetting default_kernel using qubes-prefs returns Failed to access 'default_kernel' property error and unsets default_kernel. This is confusing because qubes-prefs has no real issues accessing properties, the error is caused by default_kernel property not having a default by design.

Steps to reproduce

qubes-prefs -D default_kernel

Expected behavior

Not knowing that default_kernel has no default, I would expect it to reset value to the latest stable kernel.

With the lack of default default in mind, keeping default_kernel value untouched feels like a right step. Returning a better error message is also good.

In both cases I'm not sure how reasonable it is to change qubes-prefs just for this one edge case. Perhaps improving documentation around this might be better overall.

Actual behavior

$ qubes-prefs -D default_kernel
qubes-prefs: error: Failed to access 'default_kernel' property
$ qubes-prefs default_kernel

$

Additional information

Metadata

Metadata

Assignees

No one assigned

    Labels

    C: coreThis issue pertains to a Qubes core component.P: defaultPriority: default. Default priority for new issues, to be replaced given sufficient information.affects-4.3This issue affects Qubes OS 4.3.good first issueThis is a recommended issue for first-time contributors.needs diagnosisRequires technical diagnosis from developer. Replace with "diagnosed" or remove if otherwise closed.uxThis issue pertains to the user experience (UX) in Qubes OS.

    Type

    No fields configured for Bug.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions