Bug #5968

Geary doesn't show up in Ubuntu window switcher or Unity dock bar

Added by Daniel Givens 8 months ago. Updated 24 days ago.

Status:Fixed Start date:10/07/2012
Priority:High Due date:
Assignee:Jim Nelson % Done:

0%
Category:client
Target version:0.2.1
Keywords:

Description

I'm running Ubuntu with Unity. If I switch focus off of Geary, I'm unable to use the window switcher to gain focus of it again, unless I click on the window. Additionally, there's no icon in the dock (or whatever they call it).

Related issues

related to geary - Bug #5755: Update icon cache after uninstall Fixed 09/03/2012

History

#1
Updated by Eric Gregory 8 months ago

This is probably a Unity bug. Daniel, could you run:

unity --version

in a terminal and tell us what it returns?

#2
Updated by Jim Nelson 8 months ago

  • Category set to client
  • Priority changed from Normal to High

Also, did you install an older version of Geary before? We changed icons between 0.1 and 0.2, and I'm wondering if that's somehow partially responsible for not seeing the icon in the dock.

#3
Updated by Jim Nelson 8 months ago

Ah, I see that you posted to an earlier ticket (the uid != null assertion). As far as the icon goes, I recommend fully uninstalling Geary and reinstalling. Make sure there's no cruft left over from earlier installs with this command:

$ find /usr -name "*geary*"

#4
Updated by Jim Nelson 8 months ago

I now recall something -- there was a bug in the development builds that wouldn't update the icon cache after an uninstall. This often lead to wrong or missing icons.

As I said before, uninstall Geary and use find to determine if any old Geary cruft is left behind. That should be deleted too. Then do this:

$ sudo gtk-update-icon-cache -t -f /usr/local/share/icons/hicolor

That will remove the old icon from the cache. (If you installed to /usr rather than /usr/local, change the path accordingly.)

Now reinstall Geary. The icon should be visible now.

#5
Updated by Jim Nelson 8 months ago

  • Target version set to 0.2.1

After some testing, I can reproduce this problem even though it was supposed to be fix with #5755. Will re-fix that ticket, which should close this one as well.

#6
Updated by Jim Nelson 8 months ago

  • Assignee set to Jim Nelson

#7
Updated by Jim Nelson 8 months ago

  • Status changed from Open to 5
  • Resolution set to fixed

I believe the latest commit in #5755 will solve this problem in the future. However, the changes will not update the icon cache in old install prefixes. If this problem is still occurring, follow the instructions in #3.

#8
Updated by Charles Lindsay 24 days ago

  • Status changed from 5 to Fixed

Also available in: Atom PDF