https://bugzilla.redhat.com/show_bug.cgi?id=1823599



--- Comment #19 from Alexander Ploumistos <[email protected]> ---
Hello Bob,

Good job with all the changes!

(In reply to Bob Hepple from comment #16)
> Alexander - I can't replicate your block icon problem on my system. Do you
> have anything in your ~/.gjotsfile ?? What is your locale? Mine is
> LC_ALL=en_AU.utf8 and LANG=C.

I don't have LANG defined, but everything else is en_US.UTF-8 and the
.gjotsfile was empty. In the meantime I've moved to Fedora 32 and with your
latest changes, I didn't get these blocks, so we can chalk it off as gremlins I
guess.

When I tried to launch gjots2 in F32 I noticed that I was getting the generic
executable icon and not the png in /usr/share/pixmaps. In the desktop file you
have "Icon=gjots2", but the file is called gjots.png. According to the
specification, it shouldn't have worked before and I don't know why it did, but
you should rename the image to gjots2.png. When I renamed the file I did get
the right icon. My bad, I didn't think twice about that when I saw it before.

By the way, with HiDPI/4K displays becoming commonplace (I still don't have
one) graphics are growing huge these days. If you ever need any help creating a
higher resolution icon, I'm sure that you can ask on the design team's mailing
list and someone should be able to help you - there are a lot of talented
people working on Fedora.


Just add the trailing slash, rename the icon file and we're good to go.


Thanks again Miro!


-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component
_______________________________________________
package-review mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/[email protected]

Reply via email to