I looked into this. The current situation is complicated.
* The KDE frontend properly installs 'ubiquity' icons into the icon theme. But that icon is KDE-specific.
* The GTK frontend installs its icon to the pixmaps directory and directly references it.
* The Mythbuntu frontend also installs its visually-distinct icon to the same place and, in dpkg terms, diverts it.
What really should be happening here is that each frontend installs namespaced icons into the theme. 'ubiquity-kde', 'ubiquity-gtk', 'ubiquity-myth' for example.
Until that is fixed, the current code is doing the best it can.
I looked into this. The current situation is complicated.
* The KDE frontend properly installs 'ubiquity' icons into the icon theme. But that icon is KDE-specific.
* The GTK frontend installs its icon to the pixmaps directory and directly references it.
* The Mythbuntu frontend also installs its visually-distinct icon to the same place and, in dpkg terms, diverts it.
What really should be happening here is that each frontend installs namespaced icons into the theme. 'ubiquity-kde', 'ubiquity-gtk', 'ubiquity-myth' for example.
Until that is fixed, the current code is doing the best it can.