Bogus error message when working with service beginning with numeral #9274
Labels
affects-4.2
This issue affects Qubes OS 4.2.
C: core
diagnosed
Technical diagnosis has been performed (see issue comments).
P: default
Priority: default. Default priority for new issues, to be replaced given sufficient information.
pr submitted
A pull request has been submitted for this issue.
r4.2-host-stable
r4.3-host-cur-test
T: bug
Type: bug report. A problem or defect resulting in unintended behavior in something that exists.
Comments
andrewdavidwong
added
T: bug
marmarek
added a commit
to marmarek/qubes-core-admin
that referenced
this issue
Jun 12, 2024
This applies to '.', '..' and anything with a slash. Technically those services can still be accessible via qubesdb, but that's not really intuitive and may look like a silent failure. But since technically those can be seen by a VM, do not exclude them from qubesdb, if somebody already set some of those names. Refuse only new values. QubesOS/qubes-issues#9274
marmarek
added a commit
to QubesOS/qubes-core-admin
that referenced
this issue
Jun 25, 2024
Conditions checked here are bogus (the only relevant one is length). Furthermore it's done in wrong place (should be pre- event). This reverts commit a3aea50. Fixes QubesOS/qubes-issues#9274 (cherry picked from commit 0ec452e)
marmarek
added a commit
to QubesOS/qubes-core-admin
that referenced
this issue
Jun 25, 2024
This applies to '.', '..' and anything with a slash. Technically those services can still be accessible via qubesdb, but that's not really intuitive and may look like a silent failure. But since technically those can be seen by a VM, do not exclude them from qubesdb, if somebody already set some of those names. Refuse only new values. QubesOS/qubes-issues#9274 (cherry picked from commit 1ff10c9)
qubesos-bot
added
r4.2-host-cur-test
r4.2-host-stable
and removed
r4.2-host-cur-test
labels
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
How to file a helpful issue
Qubes OS release
4.2
Brief summary
Reported by jbb in Forum:
When I enable the service in dom0 terminal or through the Qube Manager gui, I get an error message saying "service name must start with an ASCII character".
It appears the service is still running on the vm, but the message pops up again any time I apply edits to the VM settings in Qube Manager.
Steps to reproduce
Expected behavior
Service will be enabled without issue.
Actual behavior
Service IS enabled but Error Message appears:
"service name must start with an ASCII character"
AFAIK there is no restriction on beginning service names with numeral.
The error message is obviously bogus, and should not appear at all, since the service is correctly enabled/disabled.
The text was updated successfully, but these errors were encountered: