Version-Release number of selected component: zsh-5.0.8-5.fc22 Additional info: reporter: libreport-2.6.2 backtrace_rating: 4 cmdline: /usr/bin/zsh crash_function: charrefinc executable: /usr/bin/zsh global_pid: 4383 kernel: 4.2.3-200.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 charrefinc at pattern.c:1909 #1 patmatch at pattern.c:2546 #2 pattryrefs at pattern.c:2286 #3 pattry at pattern.c:2005 #4 execcase at loop.c:612 #5 execcmd at exec.c:3405 #6 execpline2 at exec.c:1717 #7 execpline at exec.c:1500 #8 execlist at exec.c:1276 #9 execif at loop.c:530 Potential duplicate: bug 1245116
Created attachment 1087234 [details] File: backtrace
Created attachment 1087235 [details] File: cgroup
Created attachment 1087236 [details] File: core_backtrace
Created attachment 1087237 [details] File: dso_list
Created attachment 1087238 [details] File: environ
Created attachment 1087239 [details] File: limits
Created attachment 1087240 [details] File: maps
Created attachment 1087241 [details] File: mountinfo
Created attachment 1087242 [details] File: namespaces
Created attachment 1087243 [details] File: open_fds
Created attachment 1087244 [details] File: proc_pid_status
Created attachment 1087245 [details] File: var_log_messages
Another user experienced a similar problem: Trying to run ls in gvfs dir reporter: libreport-2.6.2 backtrace_rating: 4 cmdline: zsh crash_function: charrefinc executable: /usr/bin/zsh global_pid: 5047 kernel: 4.2.3-200.fc22.x86_64 package: zsh-5.0.8-5.fc22 reason: zsh killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
(In reply to Matthias Scholz from comment #0) > Potential duplicate: bug 1245116 According to the bakctrace it is the same issue, already reported upstream: http://www.zsh.org/mla/workers/2015/msg01769.html (In reply to Matt Wheeler from comment #13) > Trying to run ls in gvfs dir How can one access a gvfs dir with zsh? Please provide a sequence of commands to run.
*** This bug has been marked as a duplicate of bug 1245116 ***
The sequence of steps is: Open SMB share using Nautilus Right click in share in Nautilus -> Open in Terminal Unfortunately I can't remember what else I was doing to trigger the crash... I sent this reply by email but apparently redhat bugzilla can't cope with email bug comments.