Version-Release number of selected component: gvfs-goa-1.50.4-1.fc38 Additional info: reporter: libreport-2.17.10 type: CCpp reason: gvfsd-google killed by SIGSEGV journald_cursor: s=0207468385ae47d7942c675d124abeda;i=235645;b=00139453050f432e8599ec6d4f9c8e78;m=1f4487556;t=5ff0b2e144ecb;x=ede601958900d18c executable: /usr/libexec/gvfsd-google cmdline: /usr/libexec/gvfsd-google --spawner :1.7 /org/gtk/gvfs/exec_spaw/3 cgroup: 0::/user.slice/user-1000.slice/user/session.slice/gvfs-daemon.service rootdir: / uid: 1000 kernel: 6.3.8-200.fc38.x86_64 package: gvfs-goa-1.50.4-1.fc38 runlevel: N 5 dso_list: /usr/libexec/gvfsd-google gvfs-goa-1.50.4-1.fc38.x86_64 (Fedora Project) 1682039761 backtrace_rating: 4 crash_function: g_str_hash Truncated backtrace: Thread no. 1 (12 frames) #0 g_str_hash at ../glib/ghash.c:2521 #1 g_hash_table_lookup_node at ../glib/ghash.c:474 #2 g_hash_table_remove_internal at ../glib/ghash.c:1770 #3 g_hash_table_remove at ../glib/ghash.c:1803 #4 remove_dir at ../daemon/gvfsbackendgoogle.c:862 #5 rebuild_dir at ../daemon/gvfsbackendgoogle.c:1027 #6 resolve_child at ../daemon/gvfsbackendgoogle.c:1082 #7 resolve at ../daemon/gvfsbackendgoogle.c:1139 #8 g_vfs_backend_google_query_info at ../daemon/gvfsbackendgoogle.c:3432 #9 g_vfs_job_run at ../daemon/gvfsjob.c:195 #11 g_thread_proxy at ../glib/gthread.c:831 #13 clone3 at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 Potential duplicate: bug 2120092
Created attachment 1972744 [details] File: proc_pid_status
Created attachment 1972745 [details] File: maps
Created attachment 1972746 [details] File: limits
Created attachment 1972747 [details] File: environ
Created attachment 1972748 [details] File: open_fds
Created attachment 1972749 [details] File: mountinfo
Created attachment 1972750 [details] File: os_info
Created attachment 1972751 [details] File: cpuinfo
Created attachment 1972752 [details] File: core_backtrace
Created attachment 1972753 [details] File: exploitable
Created attachment 1972754 [details] File: backtrace
I'm not 100% sure what I did/ run before, but it should have been that I started to mount/ activate two Google Drive Connection in the Files window on the left hand-side. I think after that the problem accured. reporter: libreport-2.17.11 crash_function: g_str_hash rootdir: / runlevel: N 5 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/session.slice/gvfs-daemon.service dso_list: /usr/libexec/gvfsd-google gvfs-goa-1.50.5-2.fc38.x86_64 (Fedora Project) 1689525407 executable: /usr/libexec/gvfsd-google cmdline: /usr/libexec/gvfsd-google --spawner :1.9 /org/gtk/gvfs/exec_spaw/2 reason: gvfsd-google killed by SIGSEGV comment: I'm not 100% sure what I did/ run before, but it should have been that I started to mount/ activate two Google Drive Connection in the Files window on the left hand-side. I think after that the problem accured. type: CCpp package: gvfs-goa-1.50.5-2.fc38 journald_cursor: s=52669f6cb06a4f6491df829cc0399b57;i=1308f;b=c65dd967f54b4f3ea0229e3570aa3769;m=2bef615c;t=601b2e0df4c3f;x=bfbd4ab23f6390bc uid: 1000 kernel: 6.3.12-200.fc38.x86_64
I was about to open a .pdf file from the google drive that is located in the Fedora's other location. I am using Fedora and it is updated to the latest version. I am using stable network and no much issues when I opened other files in the google drive. reporter: libreport-2.17.11 type: CCpp reason: gvfsd-google killed by SIGSEGV journald_cursor: s=e4dd2ca778ee43779d67c1590cd17c81;i=19c8e5;b=360e9366a1e04e21b4ecb7ff0aa73314;m=7166790b;t=607b77acd53c3;x=dd57d7b62f7ff40 executable: /usr/libexec/gvfsd-google cmdline: /usr/libexec/gvfsd-google --spawner :1.11 /org/gtk/gvfs/exec_spaw/4 cgroup: 0::/user.slice/user-4209692.slice/user/session.slice/gvfs-daemon.service rootdir: / uid: 4209692 kernel: 6.5.5-200.fc38.x86_64 package: gvfs-goa-1.50.6-1.fc38 runlevel: N 5 backtrace_rating: 4 crash_function: g_str_hash
Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21. Fedora Linux 38 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.