Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#8584 - Audacious process causes 100 % CPU load but never comes to GUI mode

Attached to Project: Arch Linux
Opened by Kimo Lee Faste (KimTjik) - Friday, 09 November 2007, 15:54 GMT
Last edited by Travis Willard (Cerebral) - Friday, 09 November 2007, 18:47 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture i686
Severity High
Priority Normal
Reported Version 2007.08-2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: From command line there's no extra output. I have removed and reinstalled Audacious several times, but without any change of its behavior. As it it now Audacious doesn't work at all.


Additional info:
* package version(s)

I've tried the combinations I had access to, both giving the same error as described in this report, namely the following:

"audacious-player-1.4.0-1" combined with "audacious-plugins-1.4.0-1"

and

"audacious-player-1.4.0-1" combined with "audacious-plugins-1.4.0-2"

* config and/or log files etc.

When started from command line and then killed I get the following output:

Audacious has received SIGTERM and is shutting down.

[QUOTE](audacious:7947): GLib-CRITICAL **: g_thread_join: assertion `thread' failed
(mowgli_heap.c:195) [mowgli_heap_alloc]: exception mowgli.heap.internal_error_exception thrown[/QUOTE]

Among the logs I can only find this reference to Audacious:

[QUOTE]Nov 9 15:43:23 kimtjik audacious[7716]: segfault at 00000008 eip b78ffd50 esp bfe79d90 error 4
Nov 9 15:43:23 kimtjik audacious[7717]: segfault at 00000008 eip b78ffd50 esp b7065160 error 4[/QUOTE]

Steps to reproduce: Nothing except starting Audacious.
This task depends upon

Closed by  Travis Willard (Cerebral)
Friday, 09 November 2007, 18:47 GMT
Reason for closing:  Works for me
Comment by Travis Willard (Cerebral) - Friday, 09 November 2007, 18:46 GMT
---------
2007-11-09: A task closure has been requested. Reason for request: I can't pinpoint the solution, but after sweeping the system from any saved configuration files belonging to audacious, and starting over from scratch, it does now work. I apologize for the inconvenience.
---------

Hm - I wonder if there might be some incompatibility in the old settings with the new version that they didn't catch which causes this error... thanks for the report in any case - if other people are experiencing the same thing I can recommend they try with new configuration files.

Loading...