Describe the bug

r.shade, when run from the console, assigns the viridis color map to the final output map.

To reproduce

Run the code below from the console (or using the r.shade dialog):

r.shade shade=shaded_relief@PERMANENT color=eudem@PERMANENT output=test_shaded

This will give as output on the console:

r.shade shade=cop_relief color=cop90 output=Atest2 brighten=30                  
Color table for raster map <tmp__rshade_93369_relief> set to 'grey255'
Creating color table for output raster map...
Writing raster map <Atest2>...
r.composite complete. Raster map <Atest2> created.
Color table for raster map <Atest2> set to 'viridis'

The problem is with the last line, when the viridis color map is assigned to the output map. See the screenshots of eudem and test_shaded below.

Running the same from the terminal or Python console gives the correct output.

Expected behavior

A map that takes the colors of the color map (eudem) as a base.

Screenshots

Screenshot of eudem:

A screenshot of the test_shaded map:

For comparison, screenshot of the map created with r.shade from the console.

System description

OS: Ubuntu 24.04
GRASS version: 8.5.0dev and 8.4.1
Platform: Linux-6.14.0-37-generic-x86_64-with-glibc2.39

Additional context

Since the viridis color table is only assigned in the last step when r.shade is run from the console or the r.shade dialog, I guess the problem is not with r.shade itself?