P: Smart Collections containing Color Label criteria show "No photos in selected smart collection"

I was able to recreate same bug as you with one additional condition: The "colour label set" is not Lightroom default
With colour labels set to default (red, yellow, ....)  the problem did not occur, with a set of photos with colour labels set to those in the "review status" set (to delete, color correction required, ....) then the problem occurred on restart in grid view when it was on either monitor.
From the screenshots it looks like Patrick is also using a custom colour set.

Thanks Rikk,

It seems that "Label Color is none" doesn't trigger the bug. Also, there's no need to have multiple rules to get the problem. The Label Color rule alone is enough.

Thanks for clarifying about preferences, it wasn't clear from the previous posts.

More about this...

For all the affected smart collections, if I remove the Label Color rule, the problem disappears. If I re-add the Label Color rule, the problem is back. This can be reproduced for all smart collections using these two rules.

John, Bruce,

Resetting the Preferences , as stated above, doesn't help.

I have (patiently) checked all my smart collections against this issue and it seems that all affected collections have one thing in common : they are using 2 specific rules. The first rule is the Label Color rule and the second is the Keywords rule.

If I create a new smart collection having such rules, I can immediately reproduce the problem with it.

Could not replicate the same issue on my PC either (Win 7/LR7.3.1), however 'no photo selected' message does show for about 1/2 sec in the primary monitor loupe view then it shows the previously selected photo and the grid shows up on 2nd monitor.

What are the conditions for the Smart collection?
Could it be triggered by a specific combination? Does it affect any smart collection or just ones selecting keywords or other??

I agree that customer support departments often say "reinstall" when they don't know what else to suggest. 

But with LR, user-interface problems like this are not infrequently "solved" by resetting LR's preferences.  It's most unfortunate that sprinkling that magic fairy dust too often corrects the issue, but that's been the long experience on these forums (I'm guessing a 20% success rate on my recommendations to reset preferences). I've worked around mysterious user-interface issues with my own installation a few times over the past decade by resetting preferences. 

Given that resetting preferences has "solved" a wide range of user-interface strangenesses, it sure smells like there is a fundamental design flaw in LR's preferences implementation.  It may be that the original architects of LR are long gone from the team, and subsequent generations haven't wanted to take on what may be serious re-architecting of a facility embedded deep in LR's implementation.  But that's just my informed speculation.

Regardless, doing the reset-preferences test with your configuration would quickly identify whether this is a preferences problem or something else, providing additional information to the engineering team if/when they take a look.

Your comment is insulting. I have been designing, writing and supporting software since the late seventies. Do you have any background in software design and development ? No ? OK, then try to understand what I'm explaining instead of accusing me of ranting.

OK, it's clear you are not really looking for a solution to the problem, but just want to rant. That's fine with me, but I'm not going to participate in that any further.