Project

General

Profile

Forums » Audacious »

WARNING: Audacious seems to be already running but is not responding. Segmentation fault

Added by Conualfy M. almost 13 years ago

Hello!

I've upgraded the old default Audacious (Ubuntu Oneiric Ocelot) to the one in Webup8 PPA and now I cannot start it anymore. I ran it from terminal and this is what I get.
WARNING: Audacious seems to be already running but is not responding. Segmentation fault

As I could see in another thread, I could see more in gdb audacious:

@*gdb audacious*
GNU gdb (Ubuntu/Linaro 7.3-0ubuntu2) 7.3-2011.08
Copyright (C) 2011 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
For bug reporting instructions, please see:
<http://bugs.launchpad.net/gdb-linaro/&gt;...
Reading symbols from /usr/bin/audacious...(no debugging symbols found)...done.
run
Starting program: /usr/bin/audacious
[Thread debugging using libthread_db enabled]
WARNING: Audacious seems to be already running but is not responding.
[New Thread 0x7fffed2d3700 (LWP 6004)]
[New Thread 0x7fffd3c72700 (LWP 6009)]
[Thread 0x7fffd3c72700 (LWP 6009) exited]
[New Thread 0x7fffd3c72700 (LWP 6010)]
[Thread 0x7fffd3c72700 (LWP 6010) exited]
[New Thread 0x7fffd3c72700 (LWP 6011)]
[New Thread 0x7fffd7c73700 (LWP 6012)]
[New Thread 0x7fffd7472700 (LWP 6013)]
[New Thread 0x7fffd6c71700 (LWP 6014)]
[New Thread 0x7fffd6470700 (LWP 6015)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffd3c72700 (LWP 6011)]
0x00007fffe316450e in ?? () from /usr/lib/libmpg123.so.0
(gdb)@


Replies (1)

RE: WARNING: Audacious seems to be already running but is not responding. Segmentation fault - Added by John Lindgren almost 13 years ago

You are the second person who has reported a libmpg123-related crash lately. I suggest installing the latest version of the library from source. If the problem is still there, we can work with the mpg123 folks to try to figure out what is causing it.

    (1-1/1)