Red Hat Bugzilla – Bug 1308468
[abrt] gvfs-smb: g_malloc(): gvfsd-smb-browse killed by SIGSEGV
Last modified: 2016-12-20 13:44:27 EST
Version-Release number of selected component:
cmdline: /usr/libexec/gvfsd-smb-browse --spawner :1.9 /org/gtk/gvfs/exec_spaw/2
runlevel: N 5
Thread no. 1 (10 frames)
#2 g_malloc at gmem.c:94
#3 g_variant_format_string_scan_type at gvariant.c:4421
#4 valid_format_string at gvariant.c:4441
#5 g_variant_new at gvariant.c:5188
#6 _g_dbus_append_file_attribute at gvfsdaemonprotocol.c:183
#7 _g_dbus_append_file_info at gvfsdaemonprotocol.c:206
#8 g_vfs_job_enumerate_add_info at gvfsjobenumerate.c:204
#9 g_vfs_job_enumerate_add_infos at gvfsjobenumerate.c:222
#10 run_enumerate at gvfsbackendsmbbrowse.c:1491
#11 g_vfs_job_run at gvfsjob.c:197
Created attachment 1127208 [details]
Created attachment 1127209 [details]
Created attachment 1127210 [details]
Created attachment 1127211 [details]
Created attachment 1127212 [details]
Created attachment 1127213 [details]
Created attachment 1127214 [details]
Created attachment 1127215 [details]
Created attachment 1127216 [details]
Created attachment 1127217 [details]
Created attachment 1127218 [details]
Created attachment 1127219 [details]
Created attachment 1127220 [details]
Thanks for your bug report. Could you please provide more info, how the crash happened?
After accessing a shared folder on my vbox Windows 8.1 with the smb command: smb://192.168.1.14/public and the crash occurred just one time when opening "files > "+ other locations" > "Windows Network"
But after having restarted my fedora, this problem complete disappeared.
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. 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 Fedora 'version'
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 23 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, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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 please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.