Issues displaying album-art x86

Help and Support
1

Hi

no graphic elements and album art in the web version ui

image
image2545×1259 84.2 KB

image
image2553×1265 86.7 KB

In the local version (hdmi connection) all graphics are displayed correctly.

image
image1272×968 64 KB

image

х86

this problem with a new installation, immediately

log http://logs.volumio.org/volumio/b8SoKE0.html

2

Have you tried to reset the album cache, under source?

image
image1109×242 41.9 KB

3

Yes, of course

ps
the problem with the display of any graphic elements, immediately after a new installation

4

Incorrect links are generated

image
image2508×1150 362 KB

1 Like
5

can you run and post the results of: (ssh to your x86)

volumio endpointstest
6

image
image681×653 59.8 KB

7

the only thing i can think of is that something went wrong during the flash of the install medium.
As the …/Undefind/api… is weird.

Please try to reflash the installation medium with raspberry pi imager or win32diskimager.

8

I have the x86 version.
I have created an installation usb stick several times. And did the installation from 0
I used Balena Etcher for MAC

9

Maybe the problem is in the x86 image

10

We have multiple reports with issues using Balena. Please use rufus since your on a MAC.
i am using the same image on a x86, without issues. So I don’t think it’s an image issue.

11

image
image2548×1321 102 KB

I burned the image to a usb flash drive, on win using rufus.
Loaded it from the usb stick.
No change - problem with images

12

Also refresh the stored cache on your browser?

@gkkpch ,

Do you have any suggestion, I ran out :slight_smile:

13

even more, tried opening the web on the win machine :slight_smile:
The same problem in apps for ios

image
image1242×2688 147 KB

15

Just did a fresh install of image: Volumio-3.378-2022-09-30-x86_amd64.img
And all is working as it should.

image
image586×607 81 KB

image
image1707×766 94.9 KB

17

Not really, image 3.378 itself is OK. Running it on various x86 machines…

Except when it is resolution related: could you try a 1920x1080 monitor?
If that works, then try this in /opt/volumiokiosk
There is a section which looks like this:

# in case we want to cap hires monitors (e.g. 4K) to HD (1920x1080)
#CAPPEDRES="1920x1080"
#SUPPORTEDRES="$(xrandr | grep $CAPPEDRES)"
#if [ -z "$SUPPORTEDRES" ]; then
#  echo "Resolution $CAPPEDRES not found, skipping"
#else
#  echo "Capping resolution to $CAPPEDRES"
#  xrandr -s "$CAPPEDRES"
#fi

uncomment it to look like this:

# in case we want to cap hires monitors (e.g. 4K) to HD (1920x1080)
CAPPEDRES="1920x1080"
SUPPORTEDRES="$(xrandr | grep $CAPPEDRES)"
if [ -z "$SUPPORTEDRES" ]; then
  echo "Resolution $CAPPEDRES not found, skipping"
else
  echo "Capping resolution to $CAPPEDRES"
  xrandr -s "$CAPPEDRES"
fi
18

To avoid support via PM: (from dend)

Hi
the forum doesn’t allow you to post anymore today :frowning:

hdmi

image
image1920×1440 253 KB

http

image
image2539×1321 100 KB

19

Sorry, no clue. This is something for the core developers, does not seem x86-related at all.

20

Developer on github , helped solve the problem .
I have 2 eth ports in my system, and the cable was connected in eth1.
The problem was solved after switching the cable to eth0 :slight_smile:

Not the most obvious reason :slight_smile:

21

Now I read it, ow yes offcoarse… (not) :grinning: