Ubuntu
audacious package

audacious2 crashed with SIGSEGV in g_filename_from_uri()

Bug #409580 reported by Gareth Hart on 2009-08-05

14

This bug affects 2 people

Affects		Status	Importance	Assigned to	Milestone
	audacious (Ubuntu)	Fix Released	Medium	Unassigned

Bug Description

Binary package hint: audacious

After installing Audacious to Kubuntu Karmic Alpha 3, I enabled the crossfading audio output. When I clicked the button to configure the plugin, the application crashed. Now it will segfault everytime I attempt to start the program, making Audacious completely unusuable.

Purging the config files and reinstalling Audacious has absolutely no effect, it will still segfault every single time I attempt to start Audacious.

What should have happened:

Audacious should have started with the crossfading plugin working.

Using Audacious 2.1-1ubuntu1.

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Wed Aug 5 23:50:47 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/audacious2
NonfreeKernelModules: nvidia
Package: audacious 2.1-1ubuntu1
ProcCmdline: /usr/bin/audacious2
ProcEnviron:
LANG=C
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-5.24-generic
SegvAnalysis:
Segfault happened at: 0x7f559d3a3021: movzbl (%rdi),%ebx
PC (0x7f559d3a3021) ok
source "(%rdi)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%ebx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: audacious
StacktraceTop:
?? () from /usr/lib/libglib-2.0.so.0
g_filename_from_uri ()
vfs_file_test () from /usr/lib/libaudcore.so.1
open_file ()
?? () from /usr/lib/audacious/Input/timidity.so
Title: audacious2 crashed with SIGSEGV in g_filename_from_uri()
Uname: Linux 2.6.31-5-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Tags:

Revision history for this message

Gareth Hart (tghe-retford) wrote on 2009-08-05:

#1

Audacious log file Edit (4.3 KiB, text/plain)
Dependencies.txt Edit (3.4 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (572 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (87.0 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (774 bytes, text/plain; charset="utf-8")
Registers.txt Edit (961 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (921 bytes, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (1.7 KiB, text/plain; charset="utf-8")

visibility:

private → public

Revision history for this message

Apport retracing service (apport) wrote on 2009-08-05: Stacktrace.txt (retraced)

#2

Stacktrace.txt (retraced) Edit (4.6 KiB, text/plain)

StacktraceTop:has_case_prefix (haystack=0x0,
IA__g_filename_from_uri (uri=0x0, hostname=0x0,
vfs_file_test (path=0x0, test=G_FILE_TEST_EXISTS)
open_file (name=0x7fffd64aed07 "gravis.cfg")
read_config_file (name=0x0)

Revision history for this message

Apport retracing service (apport) wrote on 2009-08-05: ThreadStacktrace.txt (retraced)

#3

ThreadStacktrace.txt (retraced) Edit (6.3 KiB, text/plain)

Changed in audacious (Ubuntu):
importance:	Undecided → Medium
tags:	removed: need-amd64-retrace

Revision history for this message

MMarking (cpt-mocha) wrote on 2009-11-22:

#4

Running Karmic final 32 bit here. Audacious2 would just keep seg faulting when run. I found out the problem is with the timidity.so input plugin in "/usr/lib/audacious/Input". Actually the same thing happens when compiled from source, so I guess there is a problem upstream in the code for the timidity plugin.

Revision history for this message

Benjamin Drung (bdrung) wrote on 2010-06-16:

#5

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner.
There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test Audacious 2.3 from the latest stable Ubuntu version (10.04) or the current Ubuntu development version (10.10). If you can test it, and it is still an issue, we would appreciate if you could upload updated logs by running apport-collect #409580, and any other logs that are relevant for this particular issue.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

Changed in audacious (Ubuntu):
status:	New → Incomplete

Revision history for this message

Benjamin Drung (bdrung) wrote on 2010-09-23:

#6

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

Revision history for this message

Gareth Hart (tghe-retford) wrote on 2010-09-23:

#7

Since this bug was filed, Audacious 2.1 is now Audacious 2.4 in Maverick and this bug does not occur, so I suspect it's been fixed elsewhere along the line.

Revision history for this message

Benjamin Drung (bdrung) wrote on 2010-09-23:

#8

Thanks for your reply. This bug report is being closed due to your last comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

Changed in audacious (Ubuntu):
status:	Incomplete → Fix Released

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

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