Bug 447720 - Update packaging log doesn't decode ANSI colours as introduced by Garuda Linux
Summary: Update packaging log doesn't decode ANSI colours as introduced by Garuda Linux
Status: REPORTED
Alias: None
Product: Discover
Classification: Applications
Component: Updates (interactive) (show other bugs)
Version: 5.23.4
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Dan Leinir Turthra Jensen
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-12-31 06:56 UTC by Magnus Anderson
Modified: 2022-01-12 19:24 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Magnus Anderson 2021-12-31 06:56:17 UTC 
SUMMARY
***
When displaying escape sequences, it looks like `□[431;Some Text□[42;` instead of displaying text in color (I'm going off memory here for what the numbers are, as I don't actually know how to force discover to open the terminal)
***


STEPS TO REPRODUCE
I'm actually not sure what the best way to do this is. I noticed the problem because Garuda Linux prints any `.pacnew` files you have in color to get you to notice it.
1. ???
2. Get Discover's terminal to print color
3. It doesn't

EXPECTED RESULT
Prints color according to which escape sequence is seen

SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.23.4
KDE Frameworks Version: 5.89.0
Qt Version: 5.15.2
Comment 1 Aleix Pol 2022-01-03 02:58:57 UTC 
It's not an integrated terminal, we are reading /var/log/pacman.log. I find it quite odd that there's ANSI color codes in files...

I guess we could drop them or just find another way to go about it...