Bug 712633 - [abrt] audacious-2.4.5-1.fc14: _gtk_rbtree_node_find_offset: Process /usr/bin/audacious2 was killed by signal 11 (SIGSEGV)
Summary: [abrt] audacious-2.4.5-1.fc14: _gtk_rbtree_node_find_offset: Process /usr/bin...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: gtk2
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:a53f7f0a251dcead71e81b69403...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-11 23:08 UTC by larissaj2011
Modified: 2012-08-16 14:30 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-16 14:29:57 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (38.21 KB, text/plain)
2011-06-11 23:08 UTC, larissaj2011
no flags Details

Description larissaj2011 2011-06-11 23:08:37 UTC
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 39129 bytes
cmdline: /usr/bin/audacious2
comment: I purchased an album from amazon and saved the music to my secondary drive which is formatted ntfs (I'm dual booting Windows Server 2008 R2).  When I opened audacious to add the music to an existing playlist and browsed to the directory where the music was located (a backup of my documents/music folder on the secondary drive),  audacious crashed. 
component: audacious
Attached file: coredump, 107126784 bytes
crash_function: _gtk_rbtree_node_find_offset
executable: /usr/bin/audacious2
kernel: 2.6.35.13-92.fc14.x86_64
package: audacious-2.4.5-1.fc14
rating: 4
reason: Process /usr/bin/audacious2 was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1307833252
uid: 500

How to reproduce
-----
1. Open audacious
2. click on + to add files
3. browse to a secondary local ntfs drive (music is purchased from Amazon)

Comment 1 larissaj2011 2011-06-11 23:08:39 UTC
Created attachment 504280 [details]
File: backtrace

Comment 2 Michael Schwendt 2011-06-12 06:00:30 UTC
Does it crash reproducibly when browsing that NTFS drive?

It crashes in gtk2, something internal to GtkTreeView:

| #0  _gtk_rbtree_node_find_offset (tree=0x11117d0, node=0x0) at gtkrbtree.c:977
| #1  0x0000003a5765e1fd in gtk_tree_view_update_rubber_band_selection
| (tree_view=0xe63140 [GtkTreeView]) at gtktreeview.c:3920
| #2  gtk_tree_view_update_rubber_band (tree_view=0xe63140 [GtkTreeView])
| at gtktreeview.c:4054
| #3  0x0000003a57666f20 in gtk_tree_view_motion_bin_window (widget=0xe63140
| [GtkTreeView], event=0x108c420) at gtktreeview.c:4122
| #4  0x0000003a5766c7b5 in gtk_tree_view_motion (widget=0xe63140 [GtkTreeView],
| event=0x108c420) at gtktreeview.c:4169
|
| [...]

Comment 3 Fedora End Of Life 2012-08-16 14:30:00 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached 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" (top right of this page) 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


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