dashy icon indicating copy to clipboard operation
dashy copied to clipboard

[BUG] Icons, getting it wrong

Open Nivin37 opened this issue 1 year ago • 3 comments

Environment

Self-Hosted (Docker)

System

CASA OS V0.4.4.1

Version

2.2.1

Describe the problem

When I add an icon name and I get it wrong, after saving the Item you get to see the broken icon symbol.

However when I then go back to fix the broken icon, I can never fix it. I have tried to incert the correct name, remove all reference and save, use another correct icon name, all fail. The only way I have found to fix this issue is to remove the item and start again.

My current build is on CASA OS, however I did have the same issue with a previous build I did on a Debian VM.

Additional info

No response

Please tick the boxes

Nivin37 avatar Aug 17 '23 06:08 Nivin37

If you're enjoying Dashy, consider dropping us a ⭐
🤖 I'm a bot, and this message was automated

liss-bot avatar Aug 17 '23 06:08 liss-bot

I do have the same problem, actually. I would also add the fact that plenty of icons (even when I seem to get them right on the first) do not « work » - I get a broken icon. No icons from font awesome works, actually. I can make some icons work from SimpleIcon or others.

I can’t say the problems don’t come from me, though… (I mean… I’m very new to Dashy and I may do something wrong). But that bug sure looks like what I’m experiencing.

On a side note, great, great, great app !

TKinslayer avatar Aug 19 '23 05:08 TKinslayer

I also experience this. I've seen the icon work, then break, and I could then never get an icon to show again using local or hosted icons like dashboard-icons. Switching to favicon I saw the exact behavior again where notifiarr icon worked, then broke and never came back.

PooreOne avatar Oct 01 '23 03:10 PooreOne

This issue has gone 3 months without an update. To keep the ticket open, please indicate that it is still relevant in a comment below. Otherwise it will be closed in 5 working days.

liss-bot avatar Dec 31 '23 01:12 liss-bot

This issue was automatically closed because it has been stalled for over 1 year with no activity.

liss-bot avatar Jan 06 '24 01:01 liss-bot

This is absolutely still a thing that happens, and the solution is to recreate the docker image.

Looks like you're caching the remote icons locally, and so long as you're switching between valid icons it works. If you put in something which yields no icon, like a fontawesome you don't have access to, and swap back, that also works.

But if you ever end up with the broken icon icon, that never gets cleared from the cache.

What's the location in question so I can clear it, either by mounting it with a bind and wiping when needed, or with a quick rm inside the docker?

Taverius avatar Jul 29 '24 03:07 Taverius