Bug 787711 - [abrt] gnome-commander-1.2.8.15-1.fc16: has_parent_dir: Process /usr/libexec/gnome-commander/gnome-commander was killed by signal 11 (SIGSEGV)
Summary: [abrt] gnome-commander-1.2.8.15-1.fc16: has_parent_dir: Process /usr/libexec/...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-commander
Version: 16
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Mamoru TASAKA
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:21c4fc65bc2e4dc7b86e689d20d...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-06 15:23 UTC by Mrchal
Modified: 2013-02-13 19:20 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-13 19:20:09 UTC
Type: ---


Attachments (Terms of Use)
File: dso_list (12.62 KB, text/plain)
2012-02-06 15:23 UTC, Mrchal
no flags Details
File: build_ids (4.64 KB, text/plain)
2012-02-06 15:23 UTC, Mrchal
no flags Details
File: maps (51.33 KB, text/plain)
2012-02-06 15:23 UTC, Mrchal
no flags Details
File: backtrace (20.84 KB, text/plain)
2012-02-06 15:23 UTC, Mrchal
no flags Details
File: backtrace (20.47 KB, text/plain)
2012-03-07 23:05 UTC, DaWinChi
no flags Details

Description Mrchal 2012-02-06 15:23:32 UTC
libreport version: 2.0.8
abrt_version:   2.0.7
backtrace_rating: 4
cmdline:        gnome-commander
crash_function: has_parent_dir
executable:     /usr/libexec/gnome-commander/gnome-commander
kernel:         3.2.1-3.fc16.x86_64
pid:            1515
pwd:            /home/michal
reason:         Process /usr/libexec/gnome-commander/gnome-commander was killed by signal 11 (SIGSEGV)
time:           So 28. leden 2012, 10:21:15 CET
uid:            1000
username:       michal
xsession_errors: 

backtrace:      Text file, 21340 bytes
build_ids:      Text file, 4756 bytes
dso_list:       Text file, 12922 bytes
maps:           Text file, 52559 bytes

environ:
:XDG_VTNR=1
:XDG_SESSION_ID=1
:HOSTNAME=michaluv
:IMSETTINGS_INTEGRATE_DESKTOP=yes
:GPG_AGENT_INFO=/tmp/keyring-6UUB6u/gpg:0:1
:DESKTOP_STARTUP_ID=gnome-panel-1284-michaluv-gnome-commander-1_TIME193142
:TERM=dumb
:SHELL=/bin/bash
:XDG_SESSION_COOKIE=7e7c32bc18ad1f984ffb1fa600000012-1327737797.946183-1036039405
:HISTSIZE=1000
:GNOME_KEYRING_CONTROL=/tmp/keyring-6UUB6u
:IMSETTINGS_MODULE=none
:USER=michal
:SSH_AUTH_SOCK=/tmp/keyring-6UUB6u/ssh
:SESSION_MANAGER=local/unix:@/tmp/.ICE-unix/1019,unix/unix:/tmp/.ICE-unix/1019
:USERNAME=michal
:DESKTOP_SESSION=gnome
:PATH=/usr/libexec/gnome-commander:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/michal/.local/bin:/home/michal/bin
:MAIL=/var/spool/mail/michal
:QT_IM_MODULE=xim
:PWD=/home/michal
:XMODIFIERS=@im=none
:LANG=cs_CZ.utf8
:GDM_LANG=cs_CZ.utf8
:GDMSESSION=gnome
:HISTCONTROL=ignoredups
:SHLVL=1
:XDG_SEAT=seat0
:HOME=/home/michal
:GNOME_DESKTOP_SESSION_ID=this-is-deprecated
:LOGNAME=michal
:DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-hRXwSSjkNu,guid=79ea46240c546112c9a7bf0200000017
:'LESSOPEN=||/usr/bin/lesspipe.sh %s'
:WINDOWPATH=1
:DISPLAY=:0.0
:XDG_RUNTIME_DIR=/run/user/michal
:XAUTHORITY=/var/run/gdm/auth-for-michal-aauGAi/database

var_log_messages:
:Jan 28 10:21:15 michaluv kernel: [ 4700.790227] gnome-commander[1515]: segfault at 9 ip 000000000045c43c sp 00007fffbc97ca10 error 4 in gnome-commander[400000+fd000]
:Jan 28 10:21:16 michaluv abrt[4109]: Saved core dump of pid 1515 (/usr/libexec/gnome-commander/gnome-commander) to /var/spool/abrt/ccpp-2012-01-28-10:21:15-1515 (39907328 bytes)

Comment 1 Mrchal 2012-02-06 15:23:35 UTC
Created attachment 559658 [details]
File: dso_list

Comment 2 Mrchal 2012-02-06 15:23:37 UTC
Created attachment 559659 [details]
File: build_ids

Comment 3 Mrchal 2012-02-06 15:23:39 UTC
Created attachment 559660 [details]
File: maps

Comment 4 Mrchal 2012-02-06 15:23:42 UTC
Created attachment 559661 [details]
File: backtrace

Comment 5 DaWinChi 2012-03-07 23:05:05 UTC
I just moving some files from Ext4 (/home) to NTFS and when it was done (data was realy transferred),Commander died.
Nautilus doing the same thing, but more often. Sometimes out of nowhere.


backtrace_rating: 4
Package: gnome-commander-1.2.8.15-1.fc16
OS Release: Fedora release 16 (Verne)

Comment 6 DaWinChi 2012-03-07 23:05:10 UTC
Created attachment 568450 [details]
File: backtrace

Comment 7 Fedora End Of Life 2013-01-16 16:02:27 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. 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 '16'.

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 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 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 to click on 
"Clone This Bug" and open it against that version of Fedora.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 8 Fedora End Of Life 2013-02-13 19:20:13 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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.

Thank you for reporting this bug and we are sorry it could not be fixed.


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