Bug 1068859

Summary: [abrt] mc: vfs_get_current_dir(): mc killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Petr Berka <maxtractor>
Component: mcAssignee: Jindrich Novy <novyjindrich>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: dvlasenk, jezekus, novyjindrich, pahan, slavazanko, ssabcew
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/d7ee156b108518ce62f0d7aef831d7f4ffff1e79
Whiteboard: abrt_hash:d3b1746a4dd76af342ddc23042ec88415d23e62d
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 15:22:44 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Petr Berka 2014-02-22 13:57:21 UTC 
Description of problem:
The mc crashed during the startup when my Internet connection was down. Once the Internet connection was reestablished, the mc started successfully.

Version-Release number of selected component:
mc-4.8.11-1.fc20

Additional info:
reporter:       libreport-2.1.12
backtrace_rating: 4
cmdline:        /usr/bin/mc -P /tmp/mc-berkap/mc.pwd.3286
crash_function: vfs_get_current_dir
executable:     /usr/bin/mc
kernel:         3.13.3-201.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (6 frames)
 #0 vfs_get_current_dir at vfs.c:370
 #1 vfs_canon at path.c:158
 #2 vfs_path_from_str_flags at path.c:734
 #3 vfs_path_from_str at path.c:764
 #4 vfs_setup_cwd at vfs.c:539
 #5 vfs_setup_work_dir at vfs.c:445
Comment 1 Petr Berka 2014-02-22 13:57:26 UTC 
Created attachment 866393 [details]
File: backtrace
Comment 2 Petr Berka 2014-02-22 13:57:28 UTC 
Created attachment 866394 [details]
File: cgroup
Comment 3 Petr Berka 2014-02-22 13:57:31 UTC 
Created attachment 866395 [details]
File: core_backtrace
Comment 4 Petr Berka 2014-02-22 13:57:33 UTC 
Created attachment 866396 [details]
File: dso_list
Comment 5 Petr Berka 2014-02-22 13:57:35 UTC 
Created attachment 866397 [details]
File: environ
Comment 6 Petr Berka 2014-02-22 13:57:37 UTC 
Created attachment 866398 [details]
File: exploitable
Comment 7 Petr Berka 2014-02-22 13:57:40 UTC 
Created attachment 866399 [details]
File: limits
Comment 8 Petr Berka 2014-02-22 13:57:42 UTC 
Created attachment 866400 [details]
File: maps
Comment 9 Petr Berka 2014-02-22 13:57:45 UTC 
Created attachment 866401 [details]
File: open_fds
Comment 10 Petr Berka 2014-02-22 13:57:47 UTC 
Created attachment 866402 [details]
File: proc_pid_status
Comment 11 Petr Berka 2014-02-22 13:57:49 UTC 
Created attachment 866403 [details]
File: var_log_messages
Comment 12 Fedora End Of Life 2015-05-29 11:01:07 UTC 
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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'
of '20'.

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 20 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.
Comment 13 Fedora End Of Life 2015-06-29 15:22:44 UTC 
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.