Audacious - OLD, PLEASE USE GITHUB DISCUSSIONS/ISSUES

I'm sorry for the first listing (http://pokazywarka.pl/asbfsf/), it should be just
[mk@linux ~]$ export LANG=en_US.UTF-8
[mk@linux ~]$ audacious

Please attach a backtrace (Google "gdb backtrace").

https://wiki.archlinux.org/index.php/Debug_-_Getting_Traces

I run into problems installing glibc. I really do hope non-stripped audacious will be enough:

[mk@linux glibc]$ gdb audacious 
gdb: warning: error finding working directory: Nie ma takiego pliku ani katalogu
GNU gdb (GDB) 7.5.1
Copyright (C) 2012 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-unknown-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/bin/audacious...done.
(gdb) r
Starting program: /usr/bin/audacious 
shell-init: błąd przy określaniu katalogu bieżącego: getcwd: niemożliwy dostęp do katalogów nadrzędnych: Nie ma takiego pliku ani katalogu
warning: Could not load shared library symbols for linux-vdso.so.1.
Do you need "set solib-search-path" or "set sysroot"?
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
Traceback (most recent call last):
  File "/usr/share/gdb/auto-load/usr/lib/libgobject-2.0.so.0.3400.3-gdb.py", line 9, in <module>
    from gobject import register
  File "/usr/share/glib-2.0/gdb/gobject.py", line 3, in <module>
    import gdb.backtrace
ImportError: No module named backtrace
(bootstrap.c:60) [mowgli_init]: mowgli_init() is a deprecated function, provided only for backwards compatibility with Mowgli-1.  You should remove it if you no longer support using Mowgli-1.
[New Thread 0x7fffec5f0700 (LWP 2907)]
Failed to load plugin (/usr/lib/audacious/Container/cue.so): libcue.so.1: nie można otworzyć pliku obiektu dzi@@elonego: Nie ma takiego pliku ani katalogu
pulseaudio: Failed to connect to server: Connection refused
[New Thread 0x7fffd85d5700 (LWP 2909)]
[New Thread 0x7fffd7dd4700 (LWP 2910)]
[New Thread 0x7fffd75d3700 (LWP 2911)]
[New Thread 0x7fffd6dd2700 (LWP 2912)]

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff608283b in g_object_newv () from /usr/lib/libgobject-2.0.so.0

This isn't a backtrace. Read http://www.cs.cmu.edu/~gilpin/tutorial/ and then try again.

Any chance this could be more helpful?:
http://wklej.org/id/941107/

Well, it's a backtrace at least, but not really any more helpful. It's unlikely that any Audacious developer will be able to fix a crash 8 levels deep into GTK+/GLib without being able to reproduce it.

So there is no hope? The stupid thing is that my system is not very different from well-maintained Linux box and this crash just happens with default empty config. I suspect there might be some kind of problem with localization but... any suggestion where I can dig to get more info? I have this crazy idea to give you a remote access :>

If the crashes only started happening recently and you can reliably reproduce them, then it is likely that a recent update to either Audacious or GTK+/GLib is to blame. I would try downgrading each of those packages to see if the problem still happens with an older version.

Okay, first of all, 3.3.2 works as expected!

I suspected there is something wrong with translation but reverting /usr/share/locale/pl/LC_MESSAGES/audacious-plugins.mo and /usr/share/locale/pl/LC_MESSAGES/audacious.mo back to 3.3.2 version with 3.3.3 installed didn't fix the problem.

Setting LANG variable to en_US.UTF-8 also doesn't help. The only thing I can say for sure is that 3.3.2 is now playing on my computer without any problems.

Core dumped again. I'll prepare a backtrace again...

Here you have: http://wklej.org/id/943087/

Let me summarize what we have so far:
1. Version 3.3.3, unpatched, crashes in g_object_newv(): http://wklej.org/id/941107/.
2. Version 3.3.3 + the g_thread_init() patch crashes in plugin2_unload(): http://wklej.org/id/943087/.
3. Version 3.3.2 does not crash.

Is that right?

Yeah... but the first one as far as I remember happened while starting, and the second occured while closing audacious, that's why you can be confused. In the evening I'll try to provide something better methodologically organized :)

3.3.3 patched, no settings in home dir present, added some files to playlist, crashed while quiting
plugin2_unload (loaded=0x6d4a70) at pluginenum.c:105
http://wklej.org/id/944080/

3.3.3 patched, it's just a next run after attempt above, basic settings in home directory present:
[Inferior 1 (process 4388) exited normally]
http://wklej.org/id/944083/

Then I wanted to break it very badly but couldn't, with settings present audacious exits normally ;)

3.3.3 unpatched, no settings present: it started normally, I added some files to playlist and played, crashed when quitting:
0x0000000000418c57 in _start ()
http://wklej.org/id/944091/

3.3.3 unpatched, no settings present, started normally, I just clicked quit button and got the same:
0x0000000000418c57 in _start ()

3.3.3 unpatched, settings present, started and closed normally

3.3.3 unpatched, complex settings present, crashed while quitting:
#0 0x0000000000418c57 in _start ()
http://wklej.org/id/944097/

After that last crash I can't repeat it with the same settings. Strange.

If you ask me where the g_object_newv() crash came from... sorry, couldn't reproduce it this time. This bugreport is even more odd thanks to that ;]

So, sporadic and varying crashes. It's beginning to sound like memory corruption (which can unfortunately be very difficult to debug).

See if you can capture a crash while running under valgrind:

$ valgrind --track-origins=yes audacious 2>valgrind.log

Based on the wide variety of backtraces, the fault probably does not lie in those areas of the code but in some other area that is overwriting memory they use. Sometimes Valgrind can detect that memory corruption but unfortunately did not in this case.

Try using audacious 3.3.3 with audacious-plugins 3.3.2 for a while, and vice versa. That way we can determine whether the problem lies in Audacious core or in some plugin.

This commit could be a fix:
https://github.com/audacious-media-player/audacious-plugins/commit/ce77b1bb7d32a8deca274b5a2f67a9a1ab20cfa1

Thank you for your hard work! :) I hope it actually works because I haven't had time to test it yet (exams and so on). I'll let you know as soon as archlinux have the new package in repo.

Fixed for me :)