Version-Release number of selected component: epiphany-runtime-1:43.0-1.fc37 Additional info: reporter: libreport-2.17.4 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-gnome-timeshift\x2dgtk-8202.scope cmdline: epiphany /run/timeshift/backup crash_function: __strlen_avx2 executable: /usr/bin/epiphany journald_cursor: s=a250c3450336455f97dc4db830f69a21;i=842c;b=d81a30bba956409184cc06d7df82aa05;m=103423bdd;t=5f0e2dbce0bb2;x=f7fca769dca3527a kernel: 6.0.15-300.fc37.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (8 frames) #0 __strlen_avx2 at ../sysdeps/x86_64/multiarch/strlen-avx2.S:76 #1 g_strdup at ../glib/gstrfuncs.c:362 #2 xdp_portal_init at ../libportal/portal.c:263 #3 g_type_create_instance at ../gobject/gtype.c:1931 #4 g_object_new_internal at ../gobject/gobject.c:2228 #5 g_object_new_with_properties at ../gobject/gobject.c:2391 #7 xdp_portal_new at ../libportal/portal.c:279 #8 ephy_file_helpers_init at ../lib/ephy-file-helpers.c:493
Created attachment 1934726 [details] File: backtrace
Created attachment 1934728 [details] File: core_backtrace
Created attachment 1934730 [details] File: cpuinfo
Created attachment 1934733 [details] File: dso_list
Created attachment 1934735 [details] File: environ
Created attachment 1934736 [details] File: exploitable
Created attachment 1934737 [details] File: limits
Created attachment 1934738 [details] File: maps
Created attachment 1934739 [details] File: mountinfo
Created attachment 1934740 [details] File: open_fds
Created attachment 1934741 [details] File: proc_pid_status
Created attachment 1934742 [details] File: var_log_messages
I don't know how it happens, but this line is making epiphany crash: portal->sender = g_strdup (g_dbus_connection_get_unique_name (portal->bus) + 1); The only way this crash is if the bus isn't set, and the unique name is NULL. The upstream code has changed a bit, and will now show an error and assert if there's a problem with D-Bus. Can you reproduce the problem, or did this only happen once? If it happens repeatedly, I can cherry-pick parts of upstream commit c4735251029f1a30c41f6d0ea37f245bef270445 so we see what the D-Bus error is. Otherwise I'll just leave it until there's a new upstream version of libportal to rebase.
dont remember ever using epiphany....maybe something else was using it in the background
(In reply to sime.thompson from comment #14) > dont remember ever using epiphany....maybe something else was using it in > the background You used gnome-timeshift which uses epiphany.
thanks...as I now remember, Timeshift worked perfectly using both rsync and btrfs then it just crashed when it finished. The backups/snapshots were perfect.
(In reply to sime.thompson from comment #16) > thanks...as I now remember, Timeshift worked perfectly using both rsync and > btrfs then it just crashed when it finished. The backups/snapshots were > perfect. My question was: Can you reproduce the problem, or did this only happen once?
I tried it a few times...same result each time. There wasn't one time when it didn't crash on completion of backup.
Can you please update to the version of libportal built here, and test this again? This should give a slightly different output if the problem still happens.
(In reply to Bastien Nocera from comment #19) > Can you please update to the version of libportal built here, and test this > again? Here: https://koji.fedoraproject.org/koji/taskinfo?taskID=96287760 > This should give a slightly different output if the problem still happens.
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.
This message is a reminder that Fedora Linux 37 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 37 on 2023-12-05. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '37'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 37 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 37 entered end-of-life (EOL) status on None. Fedora Linux 37 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days