Lightroom Classic 7.3.1: Smart Collections containing Color Label criteria show "No photos in selected smart collection" on second display grid

  • 3
  • Problem
  • Updated 4 months ago
  • Acknowledged
  • (Edited)
Hi,

This one, I can reproduce at will. Using a dual monitor configuration under Windows.

1. Launch LR. Go to the Library module. Main screen in Loupe mode, secondary display in Grid mode.
2. Select a smart collection.
3. Select an image.
4. Exit LR.
5. Relaunch
6. The main display shows again the lastly selected image. The secondary display says "No photos in selected smart collection".
7. Now if you select another smart collection and go back to the previously selected one, all the images of the smart collection are shown on the secondary display.

Sigh! Yet another bug introduced with version 7.3.
Photo of Patrick Philippot

Patrick Philippot

  • 443 Posts
  • 115 Reply Likes
  • fed up with this alpha update

Posted 9 months ago

  • 3
Photo of Johan Elzenga

Johan Elzenga, Champion

  • 1711 Posts
  • 698 Reply Likes
I can't reproduce this on my Mac.
Photo of Mohit Goyal

Mohit Goyal, Community & Social Support Consultant - Digital Imaging

  • 10 Posts
  • 8 Reply Likes
Hi Patrick,

Could you please share your system info here? Go to Lightroom > help menu > system info and provide the dialogue information.

Regards,
Mohit
Photo of Patrick Philippot

Patrick Philippot

  • 440 Posts
  • 114 Reply Likes
Hi Mohit,

Here it is :

Lightroom Classic version: 7.3.1 [ 1167660 ]
License: Creative Cloud
Language setting: en
Operating system: Windows 10 - Business Edition
Version: 10.0.16299
Application architecture: x64
System architecture: x64
Logical processor count: 8
Processor speed: 3,4 GHz
Built-in memory: 12255,1 MB
Real memory available to Lightroom: 12255,1 MB
Real memory used by Lightroom: 732,1 MB (5,9%)
Virtual memory used by Lightroom: 881,6 MB
GDI objects count: 684
USER objects count: 2175
Process handles count: 1689
Memory cache size: 100,2MB
Internal Camera Raw revision: 933
Maximum thread count used by Camera Raw: 5
Camera Raw SIMD optimization: SSE2,AVX
Camera Raw virtual memory: 196MB / 6127MB (3%)
Camera Raw real memory: 198MB / 12255MB (1%)
System DPI setting: 96 DPI
Desktop composition enabled: Yes
Displays: 1) 1920x1200, 2) 1600x1200
Input types: Multitouch: No, Integrated touch: No, Integrated pen: No, External touch: No, External pen: No, Keyboard: No

Graphics Processor Info:
DirectX: NVIDIA Quadro K620 (23.21.13.9133)



Application folder: C:\Program Files\Adobe\Adobe Lightroom Classic CC
Library Path: D:\Catalogs\PPPhoto\PPPhoto.lrcat
Settings Folder: C:\Users\PatDev\AppData\Roaming\Adobe\Lightroom

Installed Plugins:
1) Any Filter
2) DxO PhotoLab
3) DxO PhotoLab Importer
4) Iridient X-Transformer
5) jf Metadata Viewer
6) John's big note
7) Keyboard Tamer
8) Merge to 32-bit HDR
9) Publisher, By The Turning Gate
10) Qimage Ultimate
11) Show Catalog Metadata
12) SoftProof

Config.lua flags:

Adapter #1: Vendor : 10de
    Device : 13bb
    Subsystem : 109810de
    Revision : a2
    Video Memory : 2007
Adapter #2: Vendor : 1414
    Device : 8c
    Subsystem : 0
    Revision : 0
    Video Memory : 0
AudioDeviceIOBlockSize: 1024
AudioDeviceName: Speakers (Realtek High Definition Audio)
AudioDeviceNumberOfChannels: 2
AudioDeviceSampleRate: 44100
Build: Uninitialized
Direct2DEnabled: false
GL_ACCUM_ALPHA_BITS: 16
GL_ACCUM_BLUE_BITS: 16
GL_ACCUM_GREEN_BITS: 16
GL_ACCUM_RED_BITS: 16
GL_ALPHA_BITS: 0
GL_BLUE_BITS: 8
GL_DEPTH_BITS: 24
GL_GREEN_BITS: 8
GL_MAX_3D_TEXTURE_SIZE: 4096
GL_MAX_TEXTURE_SIZE: 16384
GL_MAX_TEXTURE_UNITS: 4
GL_MAX_VIEWPORT_DIMS: 16384,16384
GL_RED_BITS: 8
GL_RENDERER: Quadro K620/PCIe/SSE2
GL_SHADING_LANGUAGE_VERSION: 4.60 NVIDIA
GL_STENCIL_BITS: 8
GL_VENDOR: NVIDIA Corporation
GL_VERSION: 4.6.0 NVIDIA 391.33
GPUDeviceEnabled: false
OGLEnabled: true
GL_EXTENSIONS: GL_AMD_multi_draw_indirect GL_AMD_seamless_cubemap_per_texture GL_ARB_arrays_of_arrays GL_ARB_base_instance GL_ARB_bindless_texture GL_ARB_blend_func_extended GL_ARB_buffer_storage GL_ARB_cl_event GL_ARB_clear_buffer_object GL_ARB_clear_texture GL_ARB_clip_control GL_ARB_color_buffer_float GL_ARB_compatibility GL_ARB_compressed_texture_pixel_storage GL_ARB_conservative_depth GL_ARB_compute_shader GL_ARB_compute_variable_group_size GL_ARB_conditional_render_inverted GL_ARB_copy_buffer GL_ARB_copy_image GL_ARB_cull_distance GL_ARB_debug_output GL_ARB_depth_buffer_float GL_ARB_depth_clamp GL_ARB_depth_texture GL_ARB_derivative_control GL_ARB_direct_state_access GL_ARB_draw_buffers GL_ARB_draw_buffers_blend GL_ARB_draw_indirect GL_ARB_draw_elements_base_vertex GL_ARB_draw_instanced GL_ARB_enhanced_layouts GL_ARB_ES2_compatibility GL_ARB_ES3_compatibility GL_ARB_ES3_1_compatibility GL_ARB_ES3_2_compatibility GL_ARB_explicit_attrib_location GL_ARB_explicit_uniform_location GL_ARB_fragment_coord_conventions GL_ARB_fragment_layer_viewport GL_ARB_fragment_program GL_ARB_fragment_program_shadow GL_ARB_fragment_shader GL_ARB_framebuffer_no_attachments GL_ARB_framebuffer_object GL_ARB_framebuffer_sRGB GL_ARB_geometry_shader4 GL_ARB_get_program_binary GL_ARB_get_texture_sub_image GL_ARB_gl_spirv GL_ARB_gpu_shader5 GL_ARB_gpu_shader_fp64 GL_ARB_gpu_shader_int64 GL_ARB_half_float_pixel GL_ARB_half_float_vertex GL_ARB_imaging GL_ARB_indirect_parameters GL_ARB_instanced_arrays GL_ARB_internalformat_query GL_ARB_internalformat_query2 GL_ARB_invalidate_subdata GL_ARB_map_buffer_alignment GL_ARB_map_buffer_range GL_ARB_multi_bind GL_ARB_multi_draw_indirect GL_ARB_multisample GL_ARB_multitexture GL_ARB_occlusion_query GL_ARB_occlusion_query2 GL_ARB_parallel_shader_compile GL_ARB_pipeline_statistics_query GL_ARB_pixel_buffer_object GL_ARB_point_parameters GL_ARB_point_sprite GL_ARB_polygon_offset_clamp GL_ARB_program_interface_query GL_ARB_provoking_vertex GL_ARB_query_buffer_object GL_ARB_robust_buffer_access_behavior GL_ARB_robustness GL_ARB_sample_shading GL_ARB_sampler_objects GL_ARB_seamless_cube_map GL_ARB_seamless_cubemap_per_texture GL_ARB_separate_shader_objects GL_ARB_shader_atomic_counter_ops GL_ARB_shader_atomic_counters GL_ARB_shader_ballot GL_ARB_shader_bit_encoding GL_ARB_shader_clock GL_ARB_shader_draw_parameters GL_ARB_shader_group_vote GL_ARB_shader_image_load_store GL_ARB_shader_image_size GL_ARB_shader_objects GL_ARB_shader_precision GL_ARB_shader_storage_buffer_object GL_ARB_shader_subroutine GL_ARB_shader_texture_image_samples GL_ARB_shader_texture_lod GL_ARB_shading_language_100 GL_ARB_shading_language_420pack GL_ARB_shading_language_include GL_ARB_shading_language_packing GL_ARB_shadow GL_ARB_sparse_buffer GL_ARB_sparse_texture GL_ARB_spirv_extensions GL_ARB_stencil_texturing GL_ARB_sync GL_ARB_tessellation_shader GL_ARB_texture_barrier GL_ARB_texture_border_clamp GL_ARB_texture_buffer_object GL_ARB_texture_buffer_object_rgb32 GL_ARB_texture_buffer_range GL_ARB_texture_compression GL_ARB_texture_compression_bptc GL_ARB_texture_compression_rgtc GL_ARB_texture_cube_map GL_ARB_texture_cube_map_array GL_ARB_texture_env_add GL_ARB_texture_env_combine GL_ARB_texture_env_crossbar GL_ARB_texture_env_dot3 GL_ARB_texture_filter_anisotropic GL_ARB_texture_float GL_ARB_texture_gather GL_ARB_texture_mirror_clamp_to_edge GL_ARB_texture_mirrored_repeat GL_ARB_texture_multisample GL_ARB_texture_non_power_of_two GL_ARB_texture_query_levels GL_ARB_texture_query_lod GL_ARB_texture_rectangle GL_ARB_texture_rg GL_ARB_texture_rgb10_a2ui GL_ARB_texture_stencil8 GL_ARB_texture_storage GL_ARB_texture_storage_multisample GL_ARB_texture_swizzle GL_ARB_texture_view GL_ARB_timer_query GL_ARB_transform_feedback2 GL_ARB_transform_feedback3 GL_ARB_transform_feedback_instanced GL_ARB_transform_feedback_overflow_query GL_ARB_transpose_matrix GL_ARB_uniform_buffer_object GL_ARB_vertex_array_bgra GL_ARB_vertex_array_object GL_ARB_vertex_attrib_64bit GL_ARB_vertex_attrib_binding GL_ARB_vertex_buffer_object GL_ARB_vertex_program GL_ARB_vertex_shader GL_ARB_vertex_type_10f_11f_11f_rev GL_ARB_vertex_type_2_10_10_10_rev GL_ARB_viewport_array GL_ARB_window_pos GL_ATI_draw_buffers GL_ATI_texture_float GL_ATI_texture_mirror_once GL_S3_s3tc GL_EXT_texture_env_add GL_EXT_abgr GL_EXT_bgra GL_EXT_bindable_uniform GL_EXT_blend_color GL_EXT_blend_equation_separate GL_EXT_blend_func_separate GL_EXT_blend_minmax GL_EXT_blend_subtract GL_EXT_compiled_vertex_array GL_EXT_Cg_shader GL_EXT_depth_bounds_test GL_EXT_direct_state_access GL_EXT_draw_buffers2 GL_EXT_draw_instanced GL_EXT_draw_range_elements GL_EXT_fog_coord GL_EXT_framebuffer_blit GL_EXT_framebuffer_multisample GL_EXTX_framebuffer_mixed_formats GL_EXT_framebuffer_multisample_blit_scaled GL_EXT_framebuffer_object GL_EXT_framebuffer_sRGB GL_EXT_geometry_shader4 GL_EXT_gpu_program_parameters GL_EXT_gpu_shader4 GL_EXT_multi_draw_arrays GL_EXT_packed_depth_stencil GL_EXT_packed_float GL_EXT_packed_pixels GL_EXT_pixel_buffer_object GL_EXT_point_parameters GL_EXT_polygon_offset_clamp GL_EXT_provoking_vertex GL_EXT_rescale_normal GL_EXT_secondary_color GL_EXT_separate_shader_objects GL_EXT_separate_specular_color GL_EXT_shader_image_load_formatted GL_EXT_shader_image_load_store GL_EXT_shader_integer_mix GL_EXT_shadow_funcs GL_EXT_stencil_two_side GL_EXT_stencil_wrap GL_EXT_texture3D GL_EXT_texture_array GL_EXT_texture_buffer_object GL_EXT_texture_compression_dxt1 GL_EXT_texture_compression_latc GL_EXT_texture_compression_rgtc GL_EXT_texture_compression_s3tc GL_EXT_texture_cube_map GL_EXT_texture_edge_clamp GL_EXT_texture_env_combine GL_EXT_texture_env_dot3 GL_EXT_texture_filter_anisotropic GL_EXT_texture_integer GL_EXT_texture_lod GL_EXT_texture_lod_bias GL_EXT_texture_mirror_clamp GL_EXT_texture_object GL_EXT_texture_shared_exponent GL_EXT_texture_sRGB GL_EXT_texture_sRGB_decode GL_EXT_texture_storage GL_EXT_texture_swizzle GL_EXT_timer_query GL_EXT_transform_feedback2 GL_EXT_vertex_array GL_EXT_vertex_array_bgra GL_EXT_vertex_attrib_64bit GL_EXT_window_rectangles GL_EXT_import_sync_object GL_IBM_rasterpos_clip GL_IBM_texture_mirrored_repeat GL_KHR_context_flush_control GL_KHR_debug GL_EXT_memory_object GL_EXT_memory_object_win32 GL_EXT_win32_keyed_mutex GL_KHR_parallel_shader_compile GL_KHR_no_error GL_KHR_robust_buffer_access_behavior GL_KHR_robustness GL_EXT_semaphore GL_EXT_semaphore_win32 GL_KTX_buffer_region GL_NV_alpha_to_coverage_dither_control GL_NV_bindless_multi_draw_indirect GL_NV_bindless_multi_draw_indirect_count GL_NV_bindless_texture GL_NV_blend_equation_advanced GL_NV_blend_equation_advanced_coherent GL_NV_blend_minmax_factor GL_NV_blend_square GL_NV_command_list GL_NV_compute_program5 GL_NV_conditional_render GL_NV_copy_depth_to_color GL_NV_copy_image GL_NV_deep_texture3D GL_NV_depth_buffer_float GL_NV_depth_clamp GL_NV_draw_texture GL_NV_draw_vulkan_image GL_NV_ES1_1_compatibility GL_NV_ES3_1_compatibility GL_NV_explicit_multisample GL_NV_fence GL_NV_float_buffer GL_NV_fog_distance GL_NV_fragment_program GL_NV_fragment_program_option GL_NV_fragment_program2 GL_NV_framebuffer_multisample_coverage GL_NV_geometry_shader4 GL_NV_gpu_program4 GL_NV_internalformat_sample_query GL_NV_gpu_program4_1 GL_NV_gpu_program5 GL_NV_gpu_program5_mem_extended GL_NV_gpu_program_fp64 GL_NV_gpu_shader5 GL_NV_half_float GL_NV_light_max_exponent GL_NV_multisample_coverage GL_NV_multisample_filter_hint GL_NV_occlusion_query GL_NV_packed_depth_stencil GL_NV_parameter_buffer_object GL_NV_parameter_buffer_object2 GL_NV_path_rendering GL_NV_pixel_data_range GL_NV_point_sprite GL_NV_primitive_restart GL_NV_query_resource GL_NV_query_resource_tag GL_NV_register_combiners GL_NV_register_combiners2 GL_NV_shader_atomic_counters GL_NV_shader_atomic_float GL_NV_shader_atomic_int64 GL_NV_shader_buffer_load GL_NV_shader_storage_buffer_object GL_NV_texgen_reflection GL_NV_texture_barrier GL_NV_texture_compression_vtc GL_NV_texture_env_combine4 GL_NV_texture_multisample GL_NV_texture_rectangle GL_NV_texture_rectangle_compressed GL_NV_texture_shader GL_NV_texture_shader2 GL_NV_texture_shader3 GL_NV_transform_feedback GL_NV_transform_feedback2 GL_NV_uniform_buffer_unified_memory GL_NV_vertex_array_range GL_NV_vertex_array_range2 GL_NV_vertex_attrib_integer_64bit GL_NV_vertex_buffer_unified_memory GL_NV_vertex_program GL_NV_vertex_program1_1 GL_NV_vertex_program2 GL_NV_vertex_program2_option GL_NV_vertex_program3 GL_NVX_conditional_render GL_NVX_gpu_memory_info GL_NVX_multigpu_info GL_NVX_nvenc_interop GL_NV_shader_thread_group GL_NV_shader_thread_shuffle GL_KHR_blend_equation_advanced GL_KHR_blend_equation_advanced_coherent GL_SGIS_generate_mipmap GL_SGIS_texture_lod GL_SGIX_depth_texture GL_SGIX_shadow GL_SUN_slice_accum GL_WIN_swap_hint WGL_EXT_swap_control
Photo of Tom Mickow

Tom Mickow

  • 344 Posts
  • 120 Reply Likes
Sorry, but I can't reproduce it either on my laptop or desktop, both running Win10, Lr Classic CC 7.3.1 with multiple monitors.
Photo of Patrick Philippot

Patrick Philippot

  • 443 Posts
  • 115 Reply Likes
Photo of Patrick Philippot

Patrick Philippot

  • 443 Posts
  • 115 Reply Likes
The image above shows the problem. Look on the left at the number of images in the smart collection : 133. LR doesn't see any although it is showing one anyway.
Photo of Patrick Philippot

Patrick Philippot

  • 443 Posts
  • 115 Reply Likes
Another example with another collection.

Photo of Johan Elzenga

Johan Elzenga, Champion

  • 1711 Posts
  • 698 Reply Likes
Nobody says we don’t believe you, we just don’t see this problem on our own systems. You have quite a few plugins installed. Maybe one of them is the culprit. Temporarily uninstall them and see if that solves it.
Photo of Patrick Philippot

Patrick Philippot

  • 443 Posts
  • 115 Reply Likes
Nobody says that I thought that you didn't believe me. Just wanted to give an example.
Photo of Patrick Philippot

Patrick Philippot

  • 443 Posts
  • 115 Reply Likes
> You have quite a few plugins installed. Maybe one of them is the culprit.

I have these plugins since a long time. Never had this problem before 7.3.
Photo of Johan Elzenga

Johan Elzenga, Champion

  • 1711 Posts
  • 698 Reply Likes
So? A plugin that was compatible up to version 7.2 is not necessarily also compatible with version 7.3.
Photo of Patrick Philippot

Patrick Philippot

  • 443 Posts
  • 115 Reply Likes
That would be bothering, to say the least. Changes in LR that make plugins incompatible should be advertised, especially in a minor release where they are unexpected. Anyway, disabling all plugins doesn't change anything.
(Edited)
Photo of Johan Elzenga

Johan Elzenga, Champion

  • 1711 Posts
  • 698 Reply Likes
Adobe can’t possibly know what all plugins do or don’t do. The changes of version 7.3 in the develop module for Dehaze and camera profiles could very well break a plugin, and it’s up to the plugin author to check that and do something about it.
(Edited)
Photo of Patrick Philippot

Patrick Philippot

  • 443 Posts
  • 115 Reply Likes
OK. Question answered anyway. The problem is elsewhere.
Photo of Johan Elzenga

Johan Elzenga, Champion

  • 1711 Posts
  • 698 Reply Likes
Two other suggestions:
1: Reset the preferences. It’s amazing how many different issues seem to be related to that.
2: Disable the use of the GPU in Preferences - Performance. The GPU is now used for other things than just the develop module, so it just might be the problem.
Photo of Patrick Philippot

Patrick Philippot

  • 443 Posts
  • 115 Reply Likes
Doesn't help.

As a former software engineer, I use to diagnose problems in a logical way. I can't do much since I don't have access to the source code. But...

What I see here is that LR is not able to properly count the number of items in a dynamic collection. That is, the Grid View has a problem with this. On the other hand, the Collections panel displays the correct number of images for that collection. So the Grid View obviously has a problem in this case (by the way, by far not the only problem with Grid View on a dual display configuration).
Photo of Johan Elzenga

Johan Elzenga, Champion

  • 1711 Posts
  • 698 Reply Likes
But the problem is that I can't reproduce the issue on my Mac, and somebody else can't reproduce it on their Windows PC. That means it has to be something that is somehow related to your particular setup, not a general bug that we all would see. 
Photo of Patrick Philippot

Patrick Philippot

  • 443 Posts
  • 115 Reply Likes
A bug is always general. On the same platform and for the same version, we are all running the very same code. Just, the bug may or may not appear depending on the way the software is used, depending on the system configuration, etc. So, it doesn't make sense to blame the user by saying that since others don't see the bug, the affected user must have a very specific configuration or have done something strange. That's the usual easy answer from lazy customer support departments. Hence the usual recommendations : reset your preferences, re-install the software, re-install your OS, etc. Which usually is a just a loss of time. What has to be done is to really diagnose the problem by finding what in the way the customer is using and configuring LR makes the bug appear. That would be useful.

Again, the bug appeared after installing version 7.3 (something I should have avoided). Nothing (hardware or software) had changed on my system. So, there's something new that must be spotted in LR, not in my system.
Photo of Johan Elzenga

Johan Elzenga, Champion

  • 1711 Posts
  • 698 Reply Likes
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.
Photo of Patrick Philippot

Patrick Philippot

  • 443 Posts
  • 115 Reply Likes
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.
(Edited)
Photo of John R. Ellis

John R. Ellis, Champion

  • 4053 Posts
  • 1067 Reply Likes
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.
Photo of Bruce Houstoun

Bruce Houstoun

  • 88 Posts
  • 25 Reply Likes
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??
Photo of Patrick Philippot

Patrick Philippot

  • 443 Posts
  • 115 Reply Likes
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.
Photo of John R. Ellis

John R. Ellis, Champion

  • 4050 Posts
  • 1067 Reply Likes
Thanks for clarifying about preferences, it wasn't clear from the previous posts.
Photo of Patrick Philippot

Patrick Philippot

  • 443 Posts
  • 115 Reply Likes
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.
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 4868 Posts
  • 989 Reply Likes
Official Response
I can duplicate what you are seeing here Patrick on Mac 10.13.4.
When I have Color Label selected as a Smart Collection criteria I get the the message. When I remove Color Label I get a normal grid in the second display view. 

I will log a bug on it. 

Thanks for reporting and providing the additional detail. 
Photo of Patrick Philippot

Patrick Philippot

  • 443 Posts
  • 115 Reply Likes
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.
Photo of Bruce Houstoun

Bruce Houstoun

  • 88 Posts
  • 25 Reply Likes
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.
Photo of Patrick Philippot

Patrick Philippot

  • 443 Posts
  • 114 Reply Likes
> From the screenshots it looks like Patrick is also using a custom colour set.

Correct.

By the way, thanks for your initial post. It led me to start the systematic check of all my smart collections.
Photo of Patrick Philippot

Patrick Philippot

  • 443 Posts
  • 115 Reply Likes
Problem not fixed in version 7.4. Is that so difficult ?
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 4868 Posts
  • 989 Reply Likes
Correct. As it says at the top of the page the issue is still in Acknowledged - meaning a bug has been filed but the issue is not yet fixed. 
Photo of Patrick Philippot

Patrick Philippot

  • 443 Posts
  • 115 Reply Likes
Rikk,
I think it's now time for the LR users to have access to some bug tracking system (in read-only mode, of course) that would allow us to exactly know if and when a problem has been taken into account. Or maybe I missed something ?

There are too many problems that are lasting since years and that are still not fixed. Nobody knows if these problems are taken into account, ignored, still under investigation,... Giving (sometimes) this information via forum threads is obviously not satisfactory.

I have some examples of severe bugs reported and documented here since years and nobody seems to care. This affects the confidence we have in the ability and/or willingness of Adobe to fix these bugs. I'm really tired of regularly reporting and documenting problems that are obviously ignored, I repeat, since years.

Some would say this is only annoying, but annoyance is the open door to repudiation. If this attitude doesn't change, I'll bite the bullet and switch to another solution. Adobe now have credible competition but don't seem to care.
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 4868 Posts
  • 989 Reply Likes
Patrick,

This forum is your conduit and there will likely be no other.  Loosely, this is how things are defined:

If an item is truly a bug its type will be "Problem" not Question, Idea, Praise or Announcement

If its status is:
  • No Status - it means it either hasn't been looked at or it is not reproducible by Adobe Staff or Prerelease testers.
  • Needs a solution - is not identifiable as a bug (against known design and has repeatable steps) or is a partner issue ((OS manufacturer, Video Card Driver, etc.)
  • Acknowledged - it means we have verified the behavior, agreed it is a bug or a partner issue and have filed said bug or reported it to our partner.
  • In-progress - it means we have identified an issue and are working with a user or users or partners to obtain more information to create a final fix. A bug is possibly open on the issue.
  • Solved - means we have either fixed the bug, or another partner  has released an update which has caused the behavior to go off the rails.
  • Not a problem - means that, upon review, it was discovered this is not an Adobe bug or a partner bug and has been resolved in another fashion.
By looking at the top of this or any thread you can tell generally where a bug is in the process. And, if someone asks, I will look up the bug and report back - as I've just done for you.  Do you have another bug you would like to ask about?
Photo of Patrick Philippot

Patrick Philippot

  • 443 Posts
  • 115 Reply Likes
> Do you have another bug you would like to ask about?

One of the most annoying and irritating problem (for me and for those who have a similar workflow making use of the metadata status flag) is this one. It's there since the first versions of LR.

https://feedback.photoshop.com/photoshop_family/topics/wrong-timestamp-stored-in-lightroom-catalog-c...

With John Ellis, we have spent a lot of time characterizing this bug. We have determined what was wrong in the database. Given this information, any developer should be able to spot the problem in the code and fix this odd behavior within a few hours (to be generous). If this is still not fixed after all these years, this means that nobody looked at it. We never had any feedback about the detailed reports that we have posted here.

Which leads to another problem in the way bugs are managed and that's why the current "conduit" is from far not satisfactory. I don't know exactly how the maintenance team is organized but one things is for sure : the longer a bug has been there, the lower the probability to get it fixed. The bug priority list obviously doesn't work as a FIFO stack. Of course, there is a need to assign a priority level  but there are problems that never had a chance to reach the top of the list. If a bug is marked as minor (who decides this ?) and lasts over about one year, it will never be fixed even if it could actually be fixed within minutes. The whole system is not working well (understatement).
(Edited)
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 4868 Posts
  • 989 Reply Likes
I have updated that one. Status was missing. A bug is still open against that issue.  I've bumped it on priority for the team to review. 
Photo of Patrick Philippot

Patrick Philippot

  • 443 Posts
  • 115 Reply Likes
Thanks.
While we are at it... This very old one sometimes causes some hair pulling sessions and processing mistakes in my workflow :
https://feedback.photoshop.com/photoshop_family/topics/lightroom-selected-published-folder-or-collec...
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 4868 Posts
  • 989 Reply Likes
I checked and it is still in process. 
Photo of Patrick Philippot

Patrick Philippot

  • 443 Posts
  • 115 Reply Likes
Still not fixed in LR 8. Is it that difficult ?