1) Using gdb, I found that evince is not in the SwitcherModel._inner vector. It has only 5 entries, which correspond to the desktop icon and 4 other applications I had running. It seems that evince is not in LauncherModel either, but there is one unity::launcher::BamfLauncherIcon with empty tooltip so I cannot be sure. This unknown icon persists after killing all evince processes.
It seems that the new evince window doesn't trigger the LauncherController::RegisterIcon like it should. I don't have a second computer at the moment so I can only debug with core files (i.e. no breakpoints).
2) There were some background evince processes running:
30251 pts/1 00:00:15 evince
30255 ? 00:00:00 evinced
After I ran 'killall evince', those processes disappeared. Restarting evince after that made the icon appear normally on both launcher and switcher.
Found out two things:
1) Using gdb, I found that evince is not in the SwitcherModel. _inner vector. It has only 5 entries, which correspond to the desktop icon and 4 other applications I had running. It seems that evince is not in LauncherModel either, but there is one unity:: launcher: :BamfLauncherIc on with empty tooltip so I cannot be sure. This unknown icon persists after killing all evince processes.
It seems that the new evince window doesn't trigger the LauncherControl ler::RegisterIc on like it should. I don't have a second computer at the moment so I can only debug with core files (i.e. no breakpoints).
2) There were some background evince processes running:
30251 pts/1 00:00:15 evince
30255 ? 00:00:00 evinced
After I ran 'killall evince', those processes disappeared. Restarting evince after that made the icon appear normally on both launcher and switcher.