Ubuntu
audacious package

Segmentation Fault when editing ogg metadata

Bug #939551 reported by Guiu Rocafort
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
audacious (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Audacious Version: Audacious 2.4.4 (Ubuntu package)

uname -a: "Linux guiu-N50Vc 3.0.0-16-generic #28-Ubuntu SMP Fri Jan 27 17:50:54 UTC 2012 i686 i686 i386 GNU/Linux"

Summary: Every time I try to edit an ogg file metadata, I get a segmentation fault when clicking the "Save" button on the menu. This bug seems only to happen with ogg files.

Is it repeatable ? :Yes

Steps for reproducing it:
1. Fire up audacious.
2. Select any ogg track.
3. Edit the metadata.
4. Click "Save".
Audacious crashes at this point.

I've atached a file with the output of executing "audacious --verbose". I also tried to disable all the plugins except the ogg one without any success.

Revision history for this message
Guiu Rocafort (neandertalspeople) wrote :
Revision history for this message
PedroVilchezBlanco (pedrovilchezblanco) wrote :

Same bug at Lubuntu 11.04 natty 2.6.38-13-generic
With audacious, editing track information of a .ogg format (alt+i), do a segmentation fault after pressing "save".

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in audacious (Ubuntu):
status: New → Confirmed
Revision history for this message
Guiu Rocafort (neandertalspeople) wrote :

I've done some backtracking with gdb. The problem seems to be caused by vfs_fread() at vfs.c

Revision history for this message
Guiu Rocafort (neandertalspeople) wrote :

Sorry, I uploaded the wrong file, these is the right one:

Revision history for this message
Guiu Rocafort (neandertalspeople) wrote :

I've made some progress on this. The problem at vfs_fread() seems to be caused by a bad prameter "VFSFile* file". I tracked back where does this pointer comes from. I found that it is initialised in vfs_fopen(). It seems like this function is not initializing the pointer correctly. In vfs_fopen the name of the pointer is "file".

What is the meaning of the vfs_fopen_impl() ? It doesn't make any sense for me, it does just return NULL. I am missing something here ?

The bad pointer passing through functions and its names:

file_write_tuple() [ handle ] -> vorbis_update_song_tuple() [ fd ] -> vcedit_open() [ in ] -> vcedit_open_callbacks() [state.in] -> vfs_fread() [file]

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.