Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at
Bug 2079344 - A new album looks empty until app restart
Summary: A new album looks empty until app restart
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-photos
Version: 36
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: GNOME SIG Unassigned
QA Contact: Fedora Extras Quality Assurance
Whiteboard: AcceptedBlocker
: 2081322 (view as bug list)
Depends On:
Blocks: F36FinalBlocker
TreeView+ depends on / blocked
Reported: 2022-04-27 12:31 UTC by Kamil Páral
Modified: 2022-05-06 17:18 UTC (History)
7 users (show)

Fixed In Version: gnome-photos-42.0-2.fc36
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2022-05-05 18:37:27 UTC
Type: Bug

Attachments (Terms of Use)
bug demonstration video (deleted)
2022-04-27 12:31 UTC, Kamil Páral
no flags Details

System ID Private Priority Status Summary Last Updated
GNOME Gitlab GNOME gnome-photos issues 197 0 None opened A new album looks empty until app restart 2022-04-28 22:44:58 UTC
GNOME Gitlab GNOME gnome-photos merge_requests 238 0 None opened item-manager: Refresh album view when photos are removed from album 2022-05-04 18:33:07 UTC

Description Kamil Páral 2022-04-27 12:31:36 UTC
Created attachment 1875353 [details]
bug demonstration video

Description of problem:
If I select some pictures and add them to a new album, the album only shows three dots as its picture, and is empty when opened ("No photos found"). When I restart gnome-photos, suddenly the album is correctly populated.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. select some photos, add them to a new album
2. go to Albums, see the new album with three dots instead of thumbnails
3. open the new album, see that it's empty
4. restart gnome-photos
5. open the new album, see that it shows the right images this time

Additional info:
In the video you can also see a small glitch - when adding a new album name and confirming with Enter, the album name shows twice in the list.

Comment 2 Kamil Páral 2022-04-27 12:36:52 UTC
Probably the same root cause - when you *remove* a picture from an album (you can do it using the "Add to Album" button, logically), the whole album gets inaccessible (again displaying with three dots) until you restart the app.

Comment 3 Adam Williamson 2022-04-27 16:23:34 UTC
+5 in , marking accepted.

Comment 4 Adam Williamson 2022-04-28 22:44:58 UTC
Confirmed here, reported upstream.

Comment 5 Kamil Páral 2022-05-02 20:20:09 UTC
I retested this with the build from bug 2079308 comment 13, but it has no effect on this bug, still broken.

Comment 6 Adam Williamson 2022-05-02 20:25:55 UTC
Well, for me, the "three dots" problem was still there, but the album did show the photos when I opened it (with the new scratch build).

Comment 7 Kamil Páral 2022-05-02 20:32:32 UTC
For me, it was still empty, until app restart. Tested twice.

Comment 8 Ben Cotton 2022-05-03 14:05:01 UTC
*** Bug 2081322 has been marked as a duplicate of this bug. ***

Comment 9 Ray Strode [halfline] 2022-05-03 17:07:09 UTC
so i have a scratch build here going that I think should make the problem go away:

I don't think it's the right fix...more of a workaround. But maybe good enough for now, until the right fix can get worked out upstream.

Comment 10 Kamil Páral 2022-05-03 22:03:29 UTC
(In reply to Ray Strode [halfline] from comment #9)

Unfortunately I don't see a difference. Still the same behavior. When creating new albums or adding photos to existing ones, I see these messages in the journal:

May 03 23:59:11 fedora gnome-photos[2127]: photos_tracker_collection_view_controller_active_collection_changed: assertion '(PHOTOS_BASE_ITEM (active_collection) && n_items == 0) || (active_collection == NULL && n_items > 0)' failed
May 03 23:59:14 fedora gnome-photos[2127]: Unable to create collection icon: Unable to create collection icon
May 04 00:00:14 fedora gnome-photos[2638]: photos_item_manager_info_updated: assertion 'updated_item == item' failed
May 04 00:00:20 fedora gnome-photos[2638]: photos_view_container_item_activated: assertion '(gpointer) box_item == (gpointer) item' failed

Comment 11 Ray Strode [halfline] 2022-05-04 12:49:45 UTC you also see double items too when creating new albums?

Comment 12 Ray Strode [halfline] 2022-05-04 13:31:01 UTC
ahhh I see, the %prep section doesn't do %autosetup so the patch isn't getting applied.

Comment 13 Ray Strode [halfline] 2022-05-04 13:33:00 UTC
new scratch build:

Comment 14 Kamil Páral 2022-05-04 14:40:58 UTC
(In reply to Ray Strode [halfline] from comment #13)
> new scratch build:

Ooh, shiny! This fixes this bug and bug 2081291 as well! If I create a new album, it is immediately accessible with the right photos. If I remove a photo from an album it stays accessible [1]. I can organize pictures between albums and the checkboxes work as expected. Great job! Can you please submit an update?

[1] There is a minor bug still remaining. If I remove a picture from an already open album, the picture still appears to be present. I have to close the album and open it again, and the picture is finally not there.

Comment 15 Fedora Update System 2022-05-04 17:10:01 UTC
FEDORA-2022-93063b598b has been submitted as an update to Fedora 36.

Comment 16 Ray Strode [halfline] 2022-05-04 18:04:19 UTC
I do have a fix for the minor bug, but I don't think it's a regression or blocker worthy so not sure if we should sneak it in or not.

Comment 17 Adam Williamson 2022-05-04 18:19:41 UTC
I already did the build and the RC is running, so I guess we can fix that one with an update :D

I confirmed the update fixes both this bug and the other one for me. Thanks a lot for the workaround, Ray.

Comment 18 Geraldo Simião 2022-05-04 22:17:44 UTC
Great, confirmed too that this update fixes this bug here and BZ#2081291
Tested it on Fedora-Workstation-Live-x86_64-36-1.4.iso

Comment 19 Geraldo Simião 2022-05-05 03:14:11 UTC
Just tested Fedora-Workstation-Live-x86_64-36-1.5.iso and Fedora-KDE-Live-x86_64-36-1.5.iso, live-sessions and installed at VMs. And in all cases this bug was FIXED.

Comment 20 Fedora Update System 2022-05-05 05:34:15 UTC
FEDORA-2022-93063b598b has been pushed to the Fedora 36 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-93063b598b`
You can provide feedback for this update here:

See also for more information on how to test updates.

Comment 21 Kamil Páral 2022-05-05 07:19:13 UTC
(In reply to Fedora Update System from comment #15)
> FEDORA-2022-93063b598b has been submitted as an update to Fedora 36.

Works fine.

Comment 22 Fedora Update System 2022-05-05 18:37:27 UTC
FEDORA-2022-93063b598b has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 23 Ray Strode [halfline] 2022-05-06 17:18:06 UTC
(In reply to Ray Strode [halfline] from comment #9)
> I don't think it's the right fix...more of a workaround. But maybe good
> enough for now, until the right fix can get worked out upstream.

Just to follow up here for those following along... 

The "right fix" (versus the "right now fix" we did a couple of days ago) has landed upstream now:

Note You need to log in before you can comment on or make changes to this bug.