Bug 554029 - [abrt] crash detected in nautilus-2.28.4-1.fc12
Summary: [abrt] crash detected in nautilus-2.28.4-1.fc12
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-desktop
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:0965d622fe390f0217d0d31ecf0...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-01-10 04:55 UTC by John Brier
Modified: 2013-08-14 23:05 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-12-04 00:38:05 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (23.52 KB, text/plain)
2010-01-10 04:55 UTC, John Brier
no flags Details

Description John Brier 2010-01-10 04:55:08 UTC
abrt 1.0.0 detected a crash.

How to reproduce
-----
1. Right click on directory within nautilus while in browser mode to get context menu
2. immediately click again a with right click or left click
3. nautilus crashes

Comment: I believe I accidentally clicked "open" in the context menu very very soon after right clicking the conext menu. it was kind of an accident due to the mechanics of my mouse. I'm not totally sure what happened thought because the mouse did some things I wasn't intending.
Attached file: backtrace
cmdline: nautilus
component: nautilus
executable: /usr/bin/nautilus
kernel: 2.6.31.9-174.fc12.x86_64
package: nautilus-2.28.4-1.fc12
rating: 4
reason: Process was terminated by signal 11

Comment 1 John Brier 2010-01-10 04:55:11 UTC
Created attachment 382750 [details]
File: backtrace

Comment 2 John Brier 2010-01-10 05:12:33 UTC
I was just looking at the backtrace and I think it does look like all i clicked was "open" so essentially I opened a directory that contained a video file. 

This file happened to be a partially copied over Xvid file.. I think it was 20 MB of 700 MB. The transfer was aborted when i accidentally disconnected the network earlier. In the backtrace you can see some functions trying to open that file:

#3  0x00000032ff8136df in gnome_desktop_thumbnail_factory_generate_thumbnail (

I am theorizing that because the file was incomplete that whatever video libraries were trying to generate the thumbnail from it crapped out.

I do have rpmfusion enabled for multimedia(VLC) but I apparently don't have any extra non fedora gstreamer plugins

[root@laptop ~]# yum repolist
Loaded plugins: presto, refresh-packagekit
repo id                   repo name                              status
fedora                    Fedora 12 - x86_64                     enabled: 19,122
rpmfusion-free            RPM Fusion for Fedora 12 - Free        enabled:    432
rpmfusion-free-updates    RPM Fusion for Fedora 12 - Free - Upda enabled:    176
rpmfusion-nonfree         RPM Fusion for Fedora 12 - Nonfree     enabled:    139
rpmfusion-nonfree-updates RPM Fusion for Fedora 12 - Nonfree - U enabled:     71
updates                   Fedora 12 - x86_64 - Updates           enabled:  4,096
repolist: 24,036
[root@laptop ~]# rpm -qa  | grep gstreamer
gstreamer-plugins-good-0.10.17-3.fc12.x86_64
gstreamer-tools-0.10.25.1-2.fc12.x86_64
gstreamer-plugins-flumpegdemux-0.10.15-8.fc12.x86_64
gstreamer-plugins-base-0.10.25.1-2.fc12.x86_64
gstreamer-python-0.10.16-1.fc12.x86_64
PackageKit-gstreamer-plugin-0.5.5-1.fc12.x86_64
gstreamer-0.10.25.1-2.fc12.x86_64

Comment 3 Tomáš Bžatek 2010-01-11 14:18:22 UTC
(In reply to comment #2)
> #3  0x00000032ff8136df in gnome_desktop_thumbnail_factory_generate_thumbnail (

This could be the reason. Any chance of getting the corrupted video file? Can you try making one? It would really help debugging here.

Comment 4 John Brier 2010-01-19 18:41:55 UTC
(In reply to comment #3)
> (In reply to comment #2)
> > #3  0x00000032ff8136df in gnome_desktop_thumbnail_factory_generate_thumbnail (
> 
> This could be the reason. Any chance of getting the corrupted video file? Can
> you try making one? It would really help debugging here.    

Sorry I just now saw this. Unfortunately before I realized this was probably the cause I had already recopied the file over so I don't have the file as it was when it generated the bug anymore. Additionally I tried copying the original file partially and reopening it and Nautilus did not crap out. I suppose I could try copying it partially many more times hoping to get the same results..

Is the back trace we already have not enough to tell why things crashed?

Comment 5 Bug Zapper 2010-11-04 01:24:04 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  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 '12'.

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 12'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 12 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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 6 Bug Zapper 2010-12-04 00:38:05 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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.