releng/tickets

Untag bash-color-prompt-0.96-1.fc46 #13493

New issue

Closed

opened 2026-08-23 22:35:07 +00:00 by adamwill · 1 comment

adamwill commented

2026-08-23 22:35:07 +00:00

Member

Describe the issue

Please untag bash-color-prompt-0.96-1.fc46 ( https://bodhi.fedoraproject.org/updates/FEDORA-2026-45b7507080 ). @juhp told me on matrix that "the default system prompt should be pixel identical (at least on GNOME)" but it definitely is not, at least on VTs. Attaching screenshots. The user prompt changed only a little - it seems like colored characters are now bolder? - but the root prompt changed significantly - previously it was a different color from the user prompt and included the # character (as is conventional), now it is the same color as the user prompt and includes a $ character (which usually indicates non-root user).

I could adjust the openQA tests to accept the new prompts, but since it seems like the changes are not intentional, it seems better to untag the build.

When do you need this? (YYYY/MM/DD)

ASAP

When is this no longer needed or useful? (YYYY/MM/DD)

When a fixed build is done

If we cannot complete this, what is the impact? [Dependencies/Blocker]

openQA tests for all updates will fail and they will be gated, unless I add new needles to workaround it. root prompts will not look as they should.

Checklist

I have checked existing issues for duplicates
I have filled out all the fields above
I have provided relevant links or references (if applicable)

## Describe the issue Please untag bash-color-prompt-0.96-1.fc46 ( https://bodhi.fedoraproject.org/updates/FEDORA-2026-45b7507080 ). @juhp told me on matrix that "the default system prompt should be pixel identical (at least on GNOME)" but it definitely is not, at least on VTs. Attaching screenshots. The user prompt changed only a little - it seems like colored characters are now bolder? - but the root prompt changed significantly - previously it was a different color from the user prompt and included the `#` character (as is conventional), now it is the same color as the user prompt and includes a `$` character (which usually indicates non-root user). I could adjust the openQA tests to accept the new prompts, but since it seems like the changes are not intentional, it seems better to untag the build. ## When do you need this? (YYYY/MM/DD) ASAP ## When is this no longer needed or useful? (YYYY/MM/DD) When a fixed build is done ## If we cannot complete this, what is the impact? [Dependencies/Blocker] openQA tests for all updates will fail and they will be gated, unless I add new needles to workaround it. root prompts will not look as they should. --- ## Checklist - [X] I have checked existing issues for duplicates - [X] I have filled out all the fields above - [X] I have provided relevant links or references (if applicable)

userafter.png

8.3 KiB

userbefore.png

8.3 KiB

rootbefore.png

8.2 KiB

rootafter.png

8.2 KiB

kevin added the

labels

2026-08-23 23:36:46 +00:00

kevin added this to the Sprint ( 2026-08-10 to 2026-08-23 ) project

2026-08-23 23:36:52 +00:00

kevin self-assigned this

2026-08-23 23:36:55 +00:00

kevin commented

2026-08-23 23:44:39 +00:00

Owner

done

done

kevin closed this issue

2026-08-23 23:44:39 +00:00

Sign in to join this conversation.

No labels

change-noreleng

Fixed with Explanation

Insufficient data

mini-initiative

waiting on external

release-process

No milestone

No project

No assignees

2 participants

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

releng/tickets#13493

No description provided.