Description of problem: disconnected a mapping, ready to then remap Version-Release number of selected component: gvfs-smb-1.14.2-2.fc18 Additional info: backtrace_rating: 4 cmdline: /usr/libexec/gvfsd-smb --spawner :1.3 /org/gtk/gvfs/exec_spaw/2 core_backtrace: crash_function: talloc_abort executable: /usr/libexec/gvfsd-smb kernel: 3.7.6-201.fc18.i686.PAE remote_result: NOTFOUND uid: 1001 var_log_messages: Feb 18 21:45:17 jtosh abrt[2760]: Saved core dump of pid 2742 (/usr/libexec/gvfsd-smb) to /var/spool/abrt/ccpp-2013-02-18-21:45:16-2742 (47243264 bytes) Truncated backtrace: Thread no. 1 (10 frames) #3 talloc_abort at ../talloc.c:338 #4 talloc_abort_access_after_free at ../talloc.c:357 #5 talloc_chunk_from_ptr at ../talloc.c:378 #7 __talloc at ../talloc.c:578 #8 talloc_named at ../talloc.c:1233 #9 smb_iconv_open_ex at ../lib/util/charset/iconv.c:205 #10 get_conv_handle at ../lib/util/charset/codepoints.c:285 #12 convert_string_talloc_handle at ../lib/util/charset/convert_string.c:388 #13 convert_string_talloc at ../lib/util/charset/convert_string.c:541 #14 internal_bytes_push_str at ../source3/libsmb/clifile.c:67
Created attachment 699291 [details] File: backtrace
Created attachment 699292 [details] File: build_ids
Created attachment 699293 [details] File: cgroup
Created attachment 699294 [details] File: dso_list
Created attachment 699295 [details] File: environ
Created attachment 699296 [details] File: limits
Created attachment 699297 [details] File: maps
Created attachment 699298 [details] File: open_fds
Created attachment 699299 [details] File: proc_pid_status
Created attachment 699300 [details] File: smolt_data
I was connected to a samba share over vpn. I was about to dismount the share when the error came up. My VPN connection was still established. backtrace_rating: 4 Package: gvfs-smb-1.14.2-3.fc18 Architecture: x86_64 OS Release: Fedora release 18 (Spherical Cow)
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
opened a smb network folder using nemo reporter: libreport-2.1.5 backtrace_rating: 4 cmdline: /usr/libexec/gvfsd-smb-browse --spawner :1.4 /org/gtk/gvfs/exec_spaw/2 core_backtrace: crash_function: talloc_abort executable: /usr/libexec/gvfsd-smb-browse kernel: 3.9.9-201.fc18.i686.PAE package: gvfs-smb-1.14.2-4.fc18 reason: Process /usr/libexec/gvfsd-smb-browse was killed by signal 6 (SIGABRT) runlevel: N 5 uid: 1000
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 'version' of '18'. 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 prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 to Fedora 18's end of life. 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 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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 bug. Thank you for reporting this bug and we are sorry it could not be fixed.