Crash in g_str_hash

Similar reports
Problem #274399
Component
gvfs
Last affected version
0:1.56.1-1.fc41
Executable
/usr/libexec/gvfsd-google
Error name
SIGSEGV 11
First occurrence
2021-12-02
Last occurrence
2024-11-18
Unique reports
5
Quality
-24

Graphs

Statistics

Operating system Unique / Total count
Fedora 35 11 / 11
Fedora 36 16 / 16
Fedora 37 170 / 198
Show more… (4)
Fedora 38 129 / 173
Fedora 39 102 / 154
Fedora 40 25 / 36
Fedora 41 5 / 5
Operating system Count
Fedora 37 198
Fedora 38 173
Fedora 39 154
Show more… (4)
Fedora 40 36
Fedora 36 16
Fedora 35 11
Fedora 41 5
Architecture Count
x86_64 593
Related packages Count
gvfs-goa 379
 0:1.52.2-1.fc39 101
 0:1.50.6-1.fc38 79
 0:1.50.2-2.fc37 74
 0:1.52.1-1.fc39 48
 0:1.54.0-2.fc40 24
 0:1.48.1-2.fc35 11
 0:1.50.7-1.fc38 10
 0:1.52.0-1.fc39 8
 0:1.54.2-1.fc40 8
 0:1.56.1-1.fc41 4
 0:1.54.3-1.fc40 4
 0:1.50.5-2.fc38 4
 0:1.50.4-1.fc37 2
 0:1.56.0-1.fc41 1
 0:1.50.3-2.fc38 1
opensc 78
 0:0.23.0-5.fc38 21
 0:0.23.0-3.fc38 19
 0:0.22.0-7.fc37 18
 0:0.24.0-1.fc39 8
 0:0.25.0-1.fc39 6
 0:0.25.0-1.fc40 2
 0:0.23.0-5.fc39 1
 0:0.24.0-1.fc38 1
 0:0.25.1-5.fc41 1
 0:0.23.0-2.fc37 1
shared-mime-info 65
 0:2.2-3.fc38 27
 0:2.1-3.fc35 13
 0:2.2-2.fc37 11
 0:2.2-4.fc39 11
 0:2.3-6.fc41 1
 0:2.1-2.fc34 1
 0:2.3-4.fc40 1
Show more… (11)
gnutls 33
 0:3.8.1-1.fc38 9
 0:3.8.4-1.fc39 7
 0:3.8.3-1.fc39 6
 0:3.8.2-2.fc39 4
 0:3.7.7-1.fc37 4
 0:3.8.1-1.fc39 1
 0:3.8.2-2.fc38 1
 0:3.8.5-1.fc39 1
systemd-libs 16
 0:253.10-1.fc38 3
 0:254.5-2.fc39 3
 0:254.10-1.fc39 3
 0:253.7-1.fc38 2
 0:253.12-1.fc38 2
 0:254.7-1.fc39 1
 0:254.8-2.fc39 1
 0:254.9-1.fc39 1
openssl-libs 9
 1:3.1.1-4.fc39 6
 1:3.2.1-2.fc40 2
 1:3.2.2-9.fc41 1
pcsc-lite-libs 7
 0:2.0.1-1.fc39 4
 0:1.9.9-3.fc38 2
 0:2.0.3-1.fc40 1
libunistring 5
 0:1.1-3.fc38 5
nss-mdns 3
 0:0.15.1-2.fc35 2
 0:0.15.1-6.fc37 1
gvfs-client 3
 0:1.50.6-1.fc38 3
libstdc++ 2
 0:13.2.1-1.fc38 2
p11-kit-trust 1
 0:0.23.22-4.fc35 1
gmp 1
 1:6.2.1-2.fc36 1
libicu 1
 0:69.1-2.fc35 1

Packages names with count less than the total count of reports are most probably not the cause of the problem.

History

Daily:

Weekly:

Monthly:

History

Daily:

Weekly:

Monthly:


Backtrace

Frame # Function Binary Source or offset Line
1
g_str_hash
/lib64/libglib-2.0.so.0 0x384b4
Build id: 2b899125cfc5dc91a26a9aef52959c6da0a5445b 		-
2
g_hash_table_remove
/lib64/libglib-2.0.so.0 0x4089a
Build id: 2b899125cfc5dc91a26a9aef52959c6da0a5445b 		-
3
remove_dir
/usr/libexec/gvfsd-google 0xb65a
Build id: fe5cf6d21545f945e5f481e96a3747c9a8a76d66 		-
4
rebuild_dir
/usr/libexec/gvfsd-google 0xb9a5
Build id: fe5cf6d21545f945e5f481e96a3747c9a8a76d66 		-
5
resolve_child
/usr/libexec/gvfsd-google 0xbc89
Build id: fe5cf6d21545f945e5f481e96a3747c9a8a76d66 		-
6
resolve
/usr/libexec/gvfsd-google 0xbee5
Build id: fe5cf6d21545f945e5f481e96a3747c9a8a76d66 		-
7
g_vfs_backend_google_query_info
/usr/libexec/gvfsd-google 0x119fc
Build id: fe5cf6d21545f945e5f481e96a3747c9a8a76d66 		-
8
g_vfs_job_run
/usr/lib64/gvfs/libgvfsdaemon.so 0x1263e
Build id: 3e241e2185d5a7812bebf309031714e54bd199bf 		-
9
g_thread_pool_thread_proxy.lto_priv.0
/lib64/libglib-2.0.so.0 0x87054
Build id: 2b899125cfc5dc91a26a9aef52959c6da0a5445b 		-
10
g_thread_proxy
/lib64/libglib-2.0.so.0 0x84122
Build id: 2b899125cfc5dc91a26a9aef52959c6da0a5445b 		-
11
start_thread
/lib64/libc.so.6 0x8db17
Build id: 148792ddec60e0b15e20655fdc10c35a5c394413 		-
12
__clone3
/lib64/libc.so.6 0x1126c0
Build id: 148792ddec60e0b15e20655fdc10c35a5c394413 		-