Bug 951574

Summary: [abrt] mc-4.8.7-3.fc18: vfs_path_from_str_uri_parser: Process /usr/bin/mc was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Serge Pavlovsky <pal666>
Component: mcAssignee: Jindrich Novy <novyjindrich>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: dan, dvlasenk, jpokorny, novyjindrich, pahan, slavazanko
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:41094c5a105cf8cf2c655b7d8d9051413dc1a4a5
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1032676 (view as bug list) Environment:
Last Closed: 2015-02-17 14:58:43 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:
Bug Depends On:    
Bug Blocks: 1032676    
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Serge Pavlovsky 2013-04-12 13:51:44 UTC 
Version-Release number of selected component:
mc-4.8.7-3.fc18

Additional info:
backtrace_rating: 4
cmdline:        /usr/bin/mc
crash_function: vfs_path_from_str_uri_parser
executable:     /usr/bin/mc
kernel:         3.8.5-201.fc18.x86_64
uid:            1000
ureports_counter: 2

Truncated backtrace:
Thread no. 1 (6 frames)
 #0 vfs_path_from_str_uri_parser at path.c:509
 #1 vfs_path_from_str_flags at path.c:762
 #2 vfs_path_from_str at path.c:781
 #3 mc_mkstemps at interface.c:796
 #4 mc_tmpdir at interface.c:881
 #5 OS_Setup at main.c:156
Comment 1 Serge Pavlovsky 2013-04-12 13:51:47 UTC 
Created attachment 734744 [details]
File: backtrace
Comment 2 Serge Pavlovsky 2013-04-12 13:51:50 UTC 
Created attachment 734745 [details]
File: cgroup
Comment 3 Serge Pavlovsky 2013-04-12 13:51:52 UTC 
Created attachment 734747 [details]
File: core_backtrace
Comment 4 Serge Pavlovsky 2013-04-12 13:51:54 UTC 
Created attachment 734748 [details]
File: dso_list
Comment 5 Serge Pavlovsky 2013-04-12 13:51:56 UTC 
Created attachment 734749 [details]
File: environ
Comment 6 Serge Pavlovsky 2013-04-12 13:51:58 UTC 
Created attachment 734750 [details]
File: limits
Comment 7 Serge Pavlovsky 2013-04-12 13:52:00 UTC 
Created attachment 734751 [details]
File: maps
Comment 8 Serge Pavlovsky 2013-04-12 13:52:03 UTC 
Created attachment 734752 [details]
File: open_fds
Comment 9 Serge Pavlovsky 2013-04-12 13:52:05 UTC 
Created attachment 734753 [details]
File: proc_pid_status
Comment 10 Serge Pavlovsky 2013-04-12 13:52:07 UTC 
Created attachment 734754 [details]
File: var_log_messages
Comment 11 Jan Pokorný [poki] 2013-11-20 13:47:20 UTC 
I've hit this one too.  It was during pre-reboot "type exit <enter>
to every terminal opened" process, but not sure what exactly triggered
the issue with mc as I was doing it without much attention paid.
Comment 12 Jan Pokorný [poki] 2013-11-20 14:51:34 UTC 
Actually not, abrt matched the issues wrongly; my backtrace:

#0  vfs_s_free_super
    (me=0x390e7b0, super=0x37beb60)
    at direntry.c:358
        No locals.

#1  vfs_gc_done
    at gc.c:296
        stamp = 0x230e0b0
        st = <optimized out>

#2  vfs_shut
    at vfs.c:467
        i = <optimized out>

#3  main
    (argc=1, argv=0x7fffe8395318)
    at main.c:408
        error = 0x0
        config_migrated = 0
        config_migrate_msg = 0x0
        exit_code = 0
Comment 13 Fedora End Of Life 2013-12-21 12:47:43 UTC 
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.
Comment 14 Fedora End Of Life 2014-02-05 20:36:37 UTC 
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.
Comment 15 Dan Horák 2014-04-15 06:31:03 UTC 
happened to me with mc-4.8.7-3.fc19.x86_64, reopening
Comment 16 Fedora End Of Life 2015-01-09 17:53:08 UTC 
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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 19 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 17 Fedora End Of Life 2015-02-17 14:58:43 UTC 
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.