Bug 1899705 Comment 0 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

## Is the content restricted to staff or under embargo (yes or no)? [REQUIRED]

Np

## Product (ensure to select only one product for each ticket. If your request involves multiple products, file an individual Bugzilla for each)

Firefox for Desktop (Linux)

## Select the type of request.

KB content update
In-product link request (maybe, i dont know)

## Please provide a summary of the request and outline any user-facing changes. [REQUIRED]

is this bug 1899516 ?

the content itself to add to SUMO is proposed at https://docs.google.com/document/d/1YCgHVtXEEzA7gqKmW5qwC8mxVD2q42ZKjnfL420zDvo/edit

## Are the user-facing changes mentioned above final? (yes or no)? [REQUIRED]

except wording changes, it should be final but still pending ux review

## Is this an on- or off-train release? Please indicate the product version number, if applicable, and add it to the end of the Summary field using the format of: Summary [Product V123]. [REQUIRED]

it will ride the train, there's no specific targeted release

## What is the anticipated release date? [REQUIRED]

it depends on when it lands

## Does the content need to be published prior to the release date? If so, when? [REQUIRED]

no it should be fine if it is published at the release date

## Does the content need to be localized in any languages outside of EN-US? If yes, please indicate which languages. [REQUIRED]

it might be useful, but i dont think it's a hard requirement (and i can do fr-FR)

## Please include any related JIRA/Github/Bugzilla tickets, documentation, demos or practical use cases. [REQUIRED]

https://mozilla-hub.atlassian.net/browse/UXREQ-219
https://bugzilla.mozilla.org/show_bug.cgi?id=1899516
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2046844

## Please include links to any design assets, visuals, figma files, etc. [REQUIRED]

https://bugzilla.mozilla.org/attachment.cgi?id=9404599

## Please add instructions for testing that will enable us to replicate the expected product behavior. [REQUIRED]

Take a build with bug 1899516 in it, install it as a tarball on a ubuntu 24.04, and:
 - you should see the notification
 - you should see in about:support there's a user namespace entry with `false` (might be localized, it should be under `Sandbox` section)

## Does the content need approval before publishing? If yes, identify the one approver responsible for this task.
**Note: Minor changes such as string updates are directly handled in SUMO, and will not lead to the generation of a pre-publishing draft. [REQUIRED]**

I dont think ti's required
## Is the content restricted to staff or under embargo (yes or no)? [REQUIRED]

No

## Product (ensure to select only one product for each ticket. If your request involves multiple products, file an individual Bugzilla for each)

Firefox for Desktop (Linux)

## Select the type of request.

KB content update
In-product link request (maybe, i dont know)

## Please provide a summary of the request and outline any user-facing changes. [REQUIRED]

is this bug 1899516 ?

the content itself to add to SUMO is proposed at https://docs.google.com/document/d/1YCgHVtXEEzA7gqKmW5qwC8mxVD2q42ZKjnfL420zDvo/edit

## Are the user-facing changes mentioned above final? (yes or no)? [REQUIRED]

except wording changes, it should be final but still pending ux review

## Is this an on- or off-train release? Please indicate the product version number, if applicable, and add it to the end of the Summary field using the format of: Summary [Product V123]. [REQUIRED]

it will ride the train, there's no specific targeted release

## What is the anticipated release date? [REQUIRED]

it depends on when it lands

## Does the content need to be published prior to the release date? If so, when? [REQUIRED]

no it should be fine if it is published at the release date

## Does the content need to be localized in any languages outside of EN-US? If yes, please indicate which languages. [REQUIRED]

it might be useful, but i dont think it's a hard requirement (and i can do fr-FR)

## Please include any related JIRA/Github/Bugzilla tickets, documentation, demos or practical use cases. [REQUIRED]

https://mozilla-hub.atlassian.net/browse/UXREQ-219
https://bugzilla.mozilla.org/show_bug.cgi?id=1899516
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2046844

## Please include links to any design assets, visuals, figma files, etc. [REQUIRED]

https://bugzilla.mozilla.org/attachment.cgi?id=9404599

## Please add instructions for testing that will enable us to replicate the expected product behavior. [REQUIRED]

Take a build with bug 1899516 in it, install it as a tarball on a ubuntu 24.04, and:
 - you should see the notification
 - you should see in about:support there's a user namespace entry with `false` (might be localized, it should be under `Sandbox` section)

## Does the content need approval before publishing? If yes, identify the one approver responsible for this task.
**Note: Minor changes such as string updates are directly handled in SUMO, and will not lead to the generation of a pre-publishing draft. [REQUIRED]**

I dont think ti's required
## Is the content restricted to staff or under embargo (yes or no)? [REQUIRED]

No

## Product (ensure to select only one product for each ticket. If your request involves multiple products, file an individual Bugzilla for each)

Firefox for Desktop (Linux)

## Select the type of request.

KB content update
In-product link request (maybe, i dont know)

## Please provide a summary of the request and outline any user-facing changes. [REQUIRED]

is this bug 1899516 ?

the content itself to add to SUMO is proposed at https://docs.google.com/document/d/1YCgHVtXEEzA7gqKmW5qwC8mxVD2q42ZKjnfL420zDvo/edit

## Are the user-facing changes mentioned above final? (yes or no)? [REQUIRED]

except wording changes, it should be final but still pending ux review

## Is this an on- or off-train release? Please indicate the product version number, if applicable, and add it to the end of the Summary field using the format of: Summary [Product V123]. [REQUIRED]

it will ride the train for 129

## What is the anticipated release date? [REQUIRED]

it depends on when it lands

## Does the content need to be published prior to the release date? If so, when? [REQUIRED]

no it should be fine if it is published at the release date

## Does the content need to be localized in any languages outside of EN-US? If yes, please indicate which languages. [REQUIRED]

it might be useful, but i dont think it's a hard requirement (and i can do fr-FR)

## Please include any related JIRA/Github/Bugzilla tickets, documentation, demos or practical use cases. [REQUIRED]

https://mozilla-hub.atlassian.net/browse/UXREQ-219
https://bugzilla.mozilla.org/show_bug.cgi?id=1899516
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2046844

## Please include links to any design assets, visuals, figma files, etc. [REQUIRED]

https://bugzilla.mozilla.org/attachment.cgi?id=9404599

## Please add instructions for testing that will enable us to replicate the expected product behavior. [REQUIRED]

Take a build with bug 1899516 in it, install it as a tarball on a ubuntu 24.04, and:
 - you should see the notification
 - you should see in about:support there's a user namespace entry with `false` (might be localized, it should be under `Sandbox` section)

## Does the content need approval before publishing? If yes, identify the one approver responsible for this task.
**Note: Minor changes such as string updates are directly handled in SUMO, and will not lead to the generation of a pre-publishing draft. [REQUIRED]**

I dont think ti's required
## Is the content restricted to staff or under embargo (yes or no)? [REQUIRED]

No

## Product (ensure to select only one product for each ticket. If your request involves multiple products, file an individual Bugzilla for each)

Firefox for Desktop (Linux)

## Select the type of request.

KB content update
In-product link request YES

## Please provide a summary of the request and outline any user-facing changes. [REQUIRED]

is this bug 1899516 ?

the content itself to add to SUMO is proposed at https://docs.google.com/document/d/1YCgHVtXEEzA7gqKmW5qwC8mxVD2q42ZKjnfL420zDvo/edit

## Are the user-facing changes mentioned above final? (yes or no)? [REQUIRED]

except wording changes, it should be final but still pending ux review

## Is this an on- or off-train release? Please indicate the product version number, if applicable, and add it to the end of the Summary field using the format of: Summary [Product V123]. [REQUIRED]

it will ride the train for 129

## What is the anticipated release date? [REQUIRED]

it depends on when it lands

## Does the content need to be published prior to the release date? If so, when? [REQUIRED]

no it should be fine if it is published at the release date

## Does the content need to be localized in any languages outside of EN-US? If yes, please indicate which languages. [REQUIRED]

it might be useful, but i dont think it's a hard requirement (and i can do fr-FR)

## Please include any related JIRA/Github/Bugzilla tickets, documentation, demos or practical use cases. [REQUIRED]

https://mozilla-hub.atlassian.net/browse/UXREQ-219
https://bugzilla.mozilla.org/show_bug.cgi?id=1899516
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2046844

## Please include links to any design assets, visuals, figma files, etc. [REQUIRED]

https://bugzilla.mozilla.org/attachment.cgi?id=9404599

## Please add instructions for testing that will enable us to replicate the expected product behavior. [REQUIRED]

Take a build with bug 1899516 in it, install it as a tarball on a ubuntu 24.04, and:
 - you should see the notification
 - you should see in about:support there's a user namespace entry with `false` (might be localized, it should be under `Sandbox` section)

## Does the content need approval before publishing? If yes, identify the one approver responsible for this task.
**Note: Minor changes such as string updates are directly handled in SUMO, and will not lead to the generation of a pre-publishing draft. [REQUIRED]**

I dont think ti's required

Back to Bug 1899705 Comment 0