Version-Release number of selected component: gnome-photos-43~beta-1.fc37 Additional info: reporter: libreport-2.17.1 backtrace_rating: 3 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/dbus-:1.1-org.gnome.Photos cmdline: /usr/bin/gnome-photos --gapplication-service crash_function: _sub_I_65535_0.0 executable: /usr/bin/gnome-photos journald_cursor: s=534f1a1c1d8149a68b27e435fad48929;i=836;b=22a2688dab68484b8a7fed0846b19702;m=5e58547;t=5e5f308a89243;x=398605247d20acac kernel: 5.19.0-65.fc37.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000
Created attachment 1904862 [details] File: backtrace
Created attachment 1904863 [details] File: core_backtrace
Created attachment 1904864 [details] File: cpuinfo
Created attachment 1904865 [details] File: dso_list
Created attachment 1904866 [details] File: environ
Created attachment 1904867 [details] File: limits
Created attachment 1904868 [details] File: maps
Created attachment 1904869 [details] File: mountinfo
Created attachment 1904870 [details] File: open_fds
Created attachment 1904871 [details] File: proc_pid_status
Created attachment 1904872 [details] File: var_log_messages
Similar problem has been detected: The Gnome session has just started when Abrt caught this problem. reporter: libreport-2.17.1 backtrace_rating: 3 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/dbus-:1.2-org.gnome.Photos cmdline: /usr/bin/gnome-photos --gapplication-service crash_function: _sub_I_65535_0.0 executable: /usr/bin/gnome-photos journald_cursor: s=18880b58e4ee49959ca4b047661da75a;i=992;b=5f60b2f5e3b94fbe87594c23a0f48291;m=467faf8;t=5e5f5bd6756f2;x=9c394df02abbffa2 kernel: 5.19.0-65.fc37.x86_64 package: gnome-photos-43~beta-1.fc37 reason: gnome-photos killed by SIGTRAP rootdir: / runlevel: N 5 type: CCpp uid: 1000
Proposed as a Blocker for 37-final by Fedora user lruzicka using the blocker tracking app because: I think this should be a final blocker, becase the basic functionality of gnome-photos is not achieved when the application does not start because of dumped core.
The issue seems to happen because both libsoup2 & libsoup3 are used on the same process. Would you mind running something like `lddtree /usr/bin/gnome-photos` (you need `pax-utils` for that command)
Sure here you go: https://pastebin.com/t8VrePkk
How about: $ lddtree /usr/lib64/grilo-0.3/libgrldaap.so It's dying while dlopening that module, which comes from grilo-plugins.
https://pastebin.com/UTm9KxWC
OK, so the problem is https://gitlab.gnome.org/GNOME/libdmapsharing. For Photos to survive, got to either (a) port it to libsoup 3, or (b) stop loading it.
I backported the upstream fixes in https://src.fedoraproject.org/rpms/gnome-photos/c/2b431d0c3cbd6b92cb0affb791315aa6a6292d51?branch=rawhide
https://bodhi.fedoraproject.org/updates/FEDORA-2022-a772b5234d
*** Bug 2117593 has been marked as a duplicate of this bug. ***
Upstream will fix this later today: Bilal Elmoussaoui abderrahim: i fixed photos by dropping grilo dependency garnacho gick med i rummet Bilal Elmoussaoui i will role a new beta today abderrahim ack, please ping me when done Closing this bug
Please don't do that. We have downstream bugs to track downstream fixes, not upstream ones. Especially for blocker bugs, the bug should only be closed when it is fixed in Fedora.
alright sorry, then i know until next time
Photos now works in Fedora 37 with the latest branched composes, okay to close this now?
Sure, thanks!