Bug 570540 - [abrt] crash in mc-1:4.7.1-1.fc12: Process /usr/bin/mc was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in mc-1:4.7.1-1.fc12: Process /usr/bin/mc was killed by signal 1...
Keywords:
Status: CLOSED DUPLICATE of bug 569823
Alias: None
Product: Fedora
Classification: Fedora
Component: mc
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Jindrich Novy
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:4ca628a55530ed87c53001cf074...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-03-04 16:50 UTC by Pavel Roskin
Modified: 2013-07-02 23:42 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-03-05 08:03:06 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (6.50 KB, text/plain)
2010-03-04 16:50 UTC, Pavel Roskin
no flags Details

Description Pavel Roskin 2010-03-04 16:50:29 UTC
abrt 1.0.7 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/mc -P /tmp/mc-proski/mc.pwd.3190
comment: Panelization of search results is crashing every time.
component: mc
executable: /usr/bin/mc
kernel: 2.6.32.9-67.fc12.x86_64
package: mc-1:4.7.1-1.fc12
rating: 4
reason: Process /usr/bin/mc was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

How to reproduce
-----
1. Press Escape-? to request search
2. Press Enter to start search
3. Press L to panelize the search results (before or after the search completes)

Comment 1 Pavel Roskin 2010-03-04 16:50:34 UTC
Created attachment 397859 [details]
File: backtrace

Comment 2 Slava Zanko 2010-03-04 17:57:16 UTC
Hi Pavel, glad to see you. :)

This bug is same as https://bugzilla.redhat.com/show_bug.cgi?id=569823 and was fixed into http://www.midnight-commander.org/ticket/2068
So, Jindrich will release update of mc in near time.

Comment 3 Jindrich Novy 2010-03-05 08:03:06 UTC
Yup, marking as duplicate.

*** This bug has been marked as a duplicate of bug 569823 ***


Note You need to log in before you can comment on or make changes to this bug.