Description of problem: Exactly as it says on the tin (in the summary ;) Looking at the icon (in all size variants) goa-account.png (in our source tarball) has some text info in it, but the rest is zeros. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3.
CC: (none) => laidlaws
(In reply to Barry Jackson from comment #0) > Description of problem: > Exactly as it says on the tin (in the summary ;) > > Looking at the icon (in all size variants) goa-account.png (in our source > tarball) has some text info in it, but the rest is zeros. > So an upstream bug, or do I misunderstand? Gnome's bugzilla chokes on my search for ALL+goa+icon (just goa+icon didn't return anything that I thought matched this issue, so maybe it did already get fixed upstream)
CC: (none) => marja11Assignee: bugsquad => olav
(In reply to Marja van Waes from comment #1) > (In reply to Barry Jackson from comment #0) > > Description of problem: > > Exactly as it says on the tin (in the summary ;) > > > > Looking at the icon (in all size variants) goa-account.png (in our source > > tarball) has some text info in it, but the rest is zeros. > > > > So an upstream bug, or do I misunderstand? Yes looks like it - Fedora has an older package 3.4.1 where ours is 3.20.1 and the icon is OK in there. > > Gnome's bugzilla chokes on my search for ALL+goa+icon (just goa+icon didn't > return anything that I thought matched this issue, so maybe it did already > get fixed upstream) Seems not, unless it's really recent. I just looked in the source tarball for the latest 3.21.3 and it's the same.
Checking the git log, it is meant to be transparent as a fallback icon. There's no desktop file for gnome-online-accounts. Where do you see this desktop icon?
Ah OK that explains it. I was following up this comment https://bugs.mageia.org/show_bug.cgi?id=18837#c3 I have not run the program myself, but looking in Fedora's older version sources, that icon is not blank so I was assuming a problem did exist. Feel free to close as invalid - sorry for the noise - blame Doug ;)
Per comment 4, behaviour is correct.
Status: NEW => RESOLVEDResolution: (none) => WORKSFORME
My shoulders are broad.