Description of problem: I wastrying to open smb://servername/sharename Version-Release number of selected component: Thunar-1.6.2-1.fc18 Additional info: backtrace_rating: 4 cmdline: Thunar --daemon crash_function: thunar_file_get_display_name executable: /usr/bin/thunar kernel: 3.7.2-201.fc18.x86_64 remote_result: NOTFOUND uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 thunar_file_get_display_name at thunar-file.c:2942 #1 thunar_window_poke_file_finish at thunar-window.c:2222 #2 thunar_browser_poke_location_file_finish at thunar-browser.c:687 #3 thunar_file_get_async_finish at thunar-file.c:1007 #4 g_simple_async_result_complete at gsimpleasyncresult.c:775 #5 _g_simple_async_result_complete_with_cancellable at gvfsdaemondbus.c:736 #6 async_got_mount_info at gdaemonfile.c:626 #7 async_get_mount_info_response at gdaemonvfs.c:880 #8 g_simple_async_result_complete at gsimpleasyncresult.c:775 #9 reply_cb at gdbusproxy.c:2632
Created attachment 685729 [details] File: backtrace
Created attachment 685730 [details] File: cgroup
Created attachment 685731 [details] File: core_backtrace
Created attachment 685732 [details] File: dso_list
Created attachment 685733 [details] File: environ
Created attachment 685734 [details] File: limits
Created attachment 685735 [details] File: maps
Created attachment 685736 [details] File: open_fds
Created attachment 685737 [details] File: proc_pid_status
Created attachment 685738 [details] File: var_log_messages
I was trying to open smb://servername/sharename backtrace_rating: 4 Package: Thunar-1.6.2-1.fc18 OS Release: Fedora release 18 (Spherical Cow)
It seems Thunar is crashing when gvfs-smb package isn't installed and 'smb://servername/sharename' location is opened. When I installed gvfs-smb package it correctly asked for a password and then a share was mounted.
Yeah, crashing when gvfs-smb isn't installed doesn't seem ideal. ;( Would you be willing to file this upstream on bugzilla.xfce.org? Or would you like me to?
Filled upstream: https://bugzilla.xfce.org/show_bug.cgi?id=9811
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.