Audacious not launching (Segmentation Fault)

Bug #208425 reported by James Schriver
18
This bug affects 1 person
Affects Status Importance Assigned to Milestone
audacious (Ubuntu)
New
Undecided
Unassigned
Nominated for Hardy by Forest Bond
xmms-crossfade (Ubuntu)
Confirmed
Undecided
Unassigned
Nominated for Hardy by Forest Bond

Bug Description

Binary package hint: audacious

Recent updates to audacious unable to launch. When opened from terminal (audacious Segmentation fault (core dumped)).

Revision history for this message
Tom Kiesel (tom-nonotyet) wrote :

I can confirm this.

Uninstalling and reinstalling Audacious through apt doesn't fix it.

I moved ~/.config/audacious/ to a backup and started audacious to see if corrupted settings were to blame

tom@gecko:~$ audacious
Segmentation fault (core dumped)

A new ~/.config/audacious/ had been created. Its contents:

playlists (empty directory)
config (empty file)
log (non-empty file, attached to this post)

/var/log/messages contents:
------------------------------------

Mar 29 01:26:24 gecko kernel: [ 626.613389] audacious[7003]: segfault at 519fc381 eip b79b985c esp bff53bf0 error 4

Revision history for this message
William Pitcock (nenolod) wrote : Re: [Bug 208425] Re: Audacious not launching (Segmentation Fault)
  • unnamed Edit (189 bytes, application/pgp-signature; name=signature.asc)

Hi,

Do you use audacious-crossfade?

If so, audacious-crossfade needs to be rebuilt against 1.5 due to it not
doing things the right way.

William

On Sat, 2008-03-29 at 06:30 +0000, Tom Kiesel wrote:
> I can confirm this.
>
> Uninstalling and reinstalling Audacious through apt doesn't fix it.
>
> I moved ~/.config/audacious/ to a backup and started audacious to see if
> corrupted settings were to blame
>
> tom@gecko:~$ audacious
> Segmentation fault (core dumped)
>
> A new ~/.config/audacious/ had been created. Its contents:
>
> playlists (empty directory)
> config (empty file)
> log (non-empty file, attached to this post)
>
> /var/log/messages contents:
> ------------------------------------
>
> Mar 29 01:26:24 gecko kernel: [ 626.613389] audacious[7003]: segfault
> at 519fc381 eip b79b985c esp bff53bf0 error 4
>
>
> ** Attachment added: "log"
> http://launchpadlibrarian.net/12959949/log
>

Revision history for this message
James Schriver (dashua) wrote :

Yep, I just figured that out. Thanks.

Revision history for this message
James Schriver (dashua) wrote :

Just rebuilt crossfade from source and all is working fine again.

Revision history for this message
Tom Kiesel (tom-nonotyet) wrote :

I uninstalled audacious-crossfade, and audacious now works properly.

I'm using the one from the repository, not compiling my own.

So is there a way to get the audacious-crossfade package updated, or move this bug to that package?

Revision history for this message
seagle (seagle0128) wrote :

Yes. I encountered the same problem, and I uninstalled crossfade plugin. It works.
In repository the package is bad. Maybe should rebuild or remove it, or many people will have trouble.
Please fix it as soon as possible.

Revision history for this message
Tom Kiesel (tom-nonotyet) wrote :

Seems to me that this bug does exist.

Changed in audacious:
status: New → Confirmed
Revision history for this message
Tom Kiesel (tom-nonotyet) wrote :

We're shipping a plugin that breaks the parent program today.

There's a simple solution listed here by William Pitcock roughly one month ago: rebuild the plugin with updated source so that the program and plugin are on the same page.

I tested this again today. Installing audacious-crossfade causes audacious to segfault on startup. Removing audacious-crossfade makes audacious work again.

I wish I knew what to do to accelerate the process. Attach a checkinstall .deb? :)

Revision history for this message
Forest Bond (forest-bond) wrote :

Nominating this bug for SRU. Only a rebuild of audacious-crossfade is necessary to fix this.

Revision history for this message
Forest Bond (forest-bond) wrote :

Not attaching a debdiff as it would contain a changelog entry only.

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

Other bug subscribers

Bug attachments

Remote bug watches

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