Since an update a few weeks (or maybe months) ago, the icons in the buttons of the search and replace dialog in Kate (version 15.08.3) went missing. See screenshot here: http://lippuner.ca/files/kate_bug.png The buttons still work (I can click on them and they do what they should), and the tooltips pop up as well if I hover the mouse over them. Just the icons disappeared... Reproducible: Always Steps to Reproduce: 1. Open Kate 2. Open Edit > Replace... Actual Results: Buttons in search and replace dialog don't have any icons Expected Results: Icons shown on buttons in search and replace dialog I'm using xfce on Debian testing with lightdm
I can confirm this on Kate 15.12.3 running under XFCE 4.12 (arch linux)
Hmm, have you installed the "breeze" icons?
installed all the following packages on arch linux, but the icons are still missing on the buttons in kate. breeze-icons breeze breeze-gtk breeze-kde4
Jonas: do you have the breeze icons installed as well?
(In reply to Buovjaga from comment #4) > Jonas: do you have the breeze icons installed as well? No, I did not have them installed. But I just installed them and they did not make a difference for the buttons in Kate. A while ago (must have been within the last couple of months), some of the buttons in the search and replace bar in Kate were restored, but unfortunately, I don't know which upgrade caused them to come back. So I see the "jump to next/previous match" and "search in the selection only" buttons (regardless of whether breeze is installed or not). However, the buttons "switch to incremental search bar" and "match case sensitive" are still missing (i.e. the icons for those buttons are missing, I can toggle the buttons and they work, but they don't have any icons).
Setting to CONFIRMED as we have two independent confirmations.
I confirm as well. I have this bug in kate 15.12.3 running under xfce4 4.12.2 in Ubuntu 16.04.1
See the bug 368184: e.g. for the neon packages all icons are there, if this is an issue, thats a packaging problem. *** This bug has been marked as a duplicate of bug 368184 ***